A few months ago, I decided to give x264 recoding a try, and utilize the MeGUI collection of programs as the reviews were 'top notch' and etc.
The best machine I had at the time was a Vista32 (4core), which was also 'tasked' for some other 'stuff', but I picked up what looked like a good guide at ribolabs, read up on the pieces that made it all 'work' (I started doing DVD recoded just about 10 years ago, and the early hoops one jumped through seemed LOTS more complex...!), and forged ahead.
No real problems. Worked (and still does) like a champ. Found the 'sharktooth' x264 presets, and MeGUI program has updated itself 2-3 times, and everything looks great.
But like I said, I use that particular machine for other 'tasks' in the world, and setting it off on multi-day excursions to x264 land was getting to be a hassle. So, off to the pc shop I went to have a new, hopefully faster, machine built, that I would 'dedicate' to x264. Top-line 6core, fastest ram and new SATA3 drives.
That's been done, and although I fought Win7 for several weeks (not just with MeGUI problems but with just about everything on that OS), and two different shops couldn't figure out the Win7 problems, I called a halt to that nonsense and had Vista64 installed instead.
This time, everything (appeared) to go as smooth as silk. The install of all the pieces went without fail, and it MeGUI appeared to work fine. I did all my tests of different HD video input types (VC-1, Mpeg4, Mpeg2) and MeGUI and it's associated pieces didn't complain whatsoever in leading them up, creating AVISynth scripts, all the way to the point where one would start the encode. Even did a couple, using the fastest (low quality) presets from the sharktooth presets. Everything looks like it was working.
So, I decided to try something 'full bore', and loaded up a full (short, 90min) movie, and set it on it's way. Grind. Damn fast. Too fast. The results were just short little 'clips' like I had put a 'trim' command in the script. I hadn't.
So, re-run it again, making absolutely sure I followed the guide to the letter. Did the exact same steps on my original V32 machine as I did on the V64. Note please, I'm not running ANY of the new 64-bit pieces on the new machine. From what I read they aren't that stable, so...
But still, only what appears to be a very short (<1GB) piece of what was supposed to be a 15+ GB (from 25+GB original) MKV recode.
I'm at a loss. I don't see why this is happening. The steps are very simple, and they are the same exact steps I used in my other machine, that happily (but somewhat slowly) grinds away next to it. Does not make sense.
Anyone have any ideas? What is really weird is that if I use a low-quality preset like 'DXVA-HD-Fast', it appears to work (but even I can pick out the lossy parts) but if I ramp up the quality level to 'Extra Quality' or 'Insane', it goes off the traces and produces these very small MKV's.
at this point.
Bit of an update:
Yes, I deleted all the x264/sharktooth presets, and reloaded them from the download 'package' I got from Doom9.
Did a couple of short tests, and it appeared that things were running more 'in line' with what I had calculated, i.e., where the x4 machine (3.2G) was figuring about 30 hrs for first pass, the x6 (3.2G) is saying about 16+, so that is 'maybe' about right.
Of course, won't know (for sure) for about 2-3 days.... My extremely rough calculations (!?) told me that having the additional 2 extra cores, plus ram about twice as fast, plus the 'super SATA' would come out to around 50-70% faster. BTW, I thought about going with a ram-disc, the really super ones are pci-x based rather than sata, and my MOBO in that machine has a slew of x16 slots, so I may decide to 'give that a try' after things get 'stable'. But those new WD SATA3 drives (twin 1TB WD), are screamers already.
Cross both my fingers. Light some incense. Bang a gong.
Bookmarks