PDA

View Full Version : iPod 640x480 megui problems


Eeker
21st October 2006, 22:26
After a lot of trial and error, I discovered that megui (with the help of Sharktooth's iPod 5.5G profile) is capable of producing beautiful videos that are very customizable, which will transfer properly to the iPod (http://mewiki.project357.com/Guides:Ipod_Conversion_Guide). Unfortunately, certain DVDs seem to have some sort of anti-copy measures put into them, which is spoiling the megui conversions. This includes DVDs of the TV show "24" (at least the ones produced here in Japan), as well as other DVDs. I've made the deduction that if the AC3 file produced by the "DV2 Creator" in megui produces an ac3 file (from VOB) which is not a perfect 0 ms sync, the final muxed video will be many times longer (2~3 hours for a 45 minute video), and after the first 45 minutes will just be blank white video. Also, the audio makes it sound like everyone who talks is a robot. If, on the other hand, the AC3 file produced in the first step is a perfect 0 ms sync, then everything comes out perfect. Certain discs I try work fine, and others have this issue. Has anyone found a way to get around this?

Eeker
23rd October 2006, 14:59
It seems nobody has any clue what I'm talking about since 100 people have looked at my post and nobody has replied. Just FYI to everyone... I found a workaround by using dgmpgdec to extract the audio to WAV instead of using megui's d2v creator to get the AC3 file. I can use this WAV file as the input audio file when converting to .mp4 audio, so this method works perfectly fine as it gets around these odd issue with certain AC3 streams.

On a side note, it looks like PQDVD updated their software to do 640x480 iPod h264 vids, but it doesn't work very well for individual VOBs as opposed to entire DVD structures, and it only does one-pass encoding and limits your encoding options severely including basic resolution settings, cropping, etc. Hopefully Nero will update their recode software soon.

blutach
23rd October 2006, 16:03
Thanks for the info Eeker. Not sure it was a decrypting issue either :)

Regards