I have converted a small number of HD-DVD VC1 movies to h264 with both Ripbot264 and MeGui which both use x264.exe to encode the video. I purchased a half dozen more HD-DVDs (becasue they are like $5 each) and started to convert them and on every single movie the x264.exe will just stop encoding. This is being done on an AMD Phenom 9550 Quad with 4GB of memory. When the encoding stops it just quits making progress and all four processors go from 100% to 0% utilization.
For different movies the encoding stops at differnt places but for a given movie it will always stop on the same frame evert time (Riptbot264 and meGui). With Autox264 it will process the entire movie but it takes longer for some reason.
My process is as follows:
Extract VC1 video (remove pulldown) and EAC3 audio to single m2ts using tsMuxer.
Process VC1 video (convert to h.264) with Riptbot264.
Process EAC3 Audio (convert to AC3) with eac3to.
Mux converted video and audio into m2ts.
Stream to PS3.
Ripbot264 used to work for me... I don't know what I did to cause to to do this. Just for information, I have reinstalled AviSynth 2.5.8 and the Haali Mediasplitter and tried every version of x264.exe since 1109? They all behave exactly the same.
+ Reply to Thread
Results 1 to 9 of 9
Not encoding any audio at all.
The HD-DVD has to be converted from VC1 to H264 in order to stream to PS3. I have also sucessfully done a number of HD-DVDs however, just recently x264 started doing this. Has to be some software interaction wit something I recently installed or upgraded.
Hmmm... long shot here.
Maybe in more recent revisions of x264 some newer implementation somewhere, or re-write, now creates conflict with HD-DvD streams.
Disregarding, and not testing on, HD-DvD streams is more rule than exception at this point in time for pretty much any of the latest code written so labeling it as a "bug" wouldn't be correct. (It would be like saying Ford's cars don't work today because they don't run on steam any more...).
Having said that, it wouldn't hurt to try an older version of x264 (maybe even pre-1000), or older x264 GUI, if you can.Been away for a while and busy with work the last few months so I had no time for forums. My apologies for any emails I couldn't get to in time - missed you all! :-)
I'm guessing, but as both the programs in question use AVISynth I wonder if AVISynth could be the problem rather than x264? Maybe it just stops frameserving for some reason? You could try emptying the AVISynth plugins folder temporarily (stuff in there generally gets loaded by AVISynth automatically and I've had a couple of odd plugin issues in the past). Failing that, maybe try rebooting into safe mode and running an encode to see what happens.
Or try using MeGUI's HD Streams Extractor to extract the video to MKV in case tsmuxer is doing something odd, or remux the m2ts files as MKVs before converting, or use a different eac3to GUI to extract the video. If all else fails, maybe try a different decoding method. If MeGUI/Ripbot is using FFMSIndex to index the m2ts files, maybe try opening one via DirectShow instead to see what happens. FFMSIndex is not always bug free. If it's been updated recently, maybe try rolling back to an older version.
That's my list for the moment of places where I think something could be going wrong.... aside from the x264 encoder being the problem, which seems unlikely.