Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Capturing and Editing Video > Avisynth Usage

Reply
 
Thread Tools Search this Thread Display Modes
Old 1st August 2021, 23:48   #1  |  Link
cockpit
Registered User
 
Join Date: Mar 2004
Location: Long Island, NY
Posts: 73
Avs2yuv maxed out my hard drive

So I wanted to give x265 another try and since I don't remember how I got it working last time I had to google quite a bit and finally landed on Avs2yuv to feed my Avisynth script into the x265 cli.

However, it started writing a massive file and aborted when my hard drive was full after 150 GB was written.

Isn't it supposed to work like frameserving so it's just a small intermediary file?

This is the command I used: avs2yuv64 "D:\Avisynth scripts\eye.avs" -o out.y4m
cockpit is offline   Reply With Quote
Old 2nd August 2021, 00:24   #2  |  Link
qyot27
...?
 
qyot27's Avatar
 
Join Date: Nov 2005
Location: Florida
Posts: 1,419
You specified a real file for it to output to, so it's going to output to it. The yuv4mpeg container only holds uncompressed video, so it's going to write the full-sized uncompressed frames if you tell it to output to a real .y4m file. But it's uncompressed video wrapped in basic metadata to tell receiving applications what the framerate, resolution, pixel format, etc. are. Those applications can take either the actual .y4m files or they can accept y4m data over a pipe, just like avs2yuv can write to a real file, or write to a pipe.

Piping doesn't write any file to the hard drive, it connects program A's standard output (stdout) with program B's standard input (stdin).

Code:
avs2yuv input.avs -o - | x265 --y4m <x265 options> -
(those solitary '-' characters are the instruction to output to a pipe or accept from one, and the '|' is the connector; x265 also requires the --y4m parameter to tell it that the pipe is in y4m format)

Although, honestly, it would be easier to:
A) Use a patched x265 build that supports AviSynth input directly.
B) Use FFmpeg (assuming it has AviSynth enabled; virtually all the common Windows builds do) and just tell it to use the libx265 encoder.
qyot27 is offline   Reply With Quote
Old 2nd August 2021, 04:12   #3  |  Link
cockpit
Registered User
 
Join Date: Mar 2004
Location: Long Island, NY
Posts: 73
I see. I totally misunderstood what piping meant.

So I downloaded the modified file linked here instead and it seems to be working, thanks.

Also, is there anything in my settings that stands out as nonsensical? It's encoding video game footage.
cockpit is offline   Reply With Quote
Old 2nd August 2021, 04:18   #4  |  Link
patul
Registered User
 
Join Date: Sep 2005
Posts: 130
I spotted 2.5 years old AVS+ is in use

Consider updating it.. But yeah, use what works for you.
patul is offline   Reply With Quote
Old 3rd August 2021, 00:22   #5  |  Link
StainlessS
HeartlessS Usurer
 
StainlessS's Avatar
 
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
cockpit, use this one:- https://github.com/AviSynth/AviSynthPlus/releases
__________________
I sometimes post sober.
StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace

"Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???
StainlessS is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 03:02.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.