lchiu7
22nd February 2009, 04:59
Wasn't sure if this was an issue with megui or x264 but I will start at the foundation so to speak.
I backed up a HD-DVD I have and ended up with two files - a vc1 file and ac3 file.
I then wanted to compress the vc1 file to something smaller to put on the server to which I would later mux the ac3 audio.
So my avisynth script I just had
directshowsource("name.vc1)
LanczosResize(1280,720)
converttoyv12()
Load this file into megui and it seemed fine. But when I went to the bitrate calculator it showed a movie as being 9 hours long (it's actually only 2h34min) and offered some really low bit rate
Then when I started encoding the processed time/time to process showed 3 minutes/9 hours! I quickly killed that.
Then out of interest muxed the VC1 file with the AC3 file and re-ran megui pointing to the new .ts file created (using tsmuxer)
Now the times were correct and the encode went properly.
Is there an issue with VC1 files as direct input to x264 or is this some subtle megui issue?
Just wondering
I backed up a HD-DVD I have and ended up with two files - a vc1 file and ac3 file.
I then wanted to compress the vc1 file to something smaller to put on the server to which I would later mux the ac3 audio.
So my avisynth script I just had
directshowsource("name.vc1)
LanczosResize(1280,720)
converttoyv12()
Load this file into megui and it seemed fine. But when I went to the bitrate calculator it showed a movie as being 9 hours long (it's actually only 2h34min) and offered some really low bit rate
Then when I started encoding the processed time/time to process showed 3 minutes/9 hours! I quickly killed that.
Then out of interest muxed the VC1 file with the AC3 file and re-ran megui pointing to the new .ts file created (using tsmuxer)
Now the times were correct and the encode went properly.
Is there an issue with VC1 files as direct input to x264 or is this some subtle megui issue?
Just wondering