PDA

View Full Version : AC3 and M2V lengths don't match after ripping.


Stebet
22nd September 2006, 03:43
Here's the case. Using DVD Decrypter i'm ripping a DVD. I did not use stream processin, just plain ripping. The length of the selected vob series is about 50 minutes and DVD Decrypter says that part of the DVD is indeed 50 minutes long. After ripping the vobs and opening up Dgdecode and Demuxing both the m2v and ac3's i find out that the video is 44 minutes long but the AC3's are 50minutes long?

This is the first time i stumble upon a DVD with discrepancies like this. This is the main video on the DVD i'm ripping. I have ripped several others with the same setting and everytime the AC# length matches the m2v length.

Has anyone seen this before? And should this even be possible?

neuron2
22nd September 2006, 04:13
Do Parse D2V and tell me what running length is reported at the bottom of the parse log output. Make sure you have Honor Pulldown Flags for the project creation.

Mug Funky
22nd September 2006, 06:34
you could try a rip with stream processing... it's possible that there's a slideshow in the same VTS. in this case it'd play back to the correct length, but the video itself will be much shorter.

it could be something completely different though...

setarip_old
22nd September 2006, 08:43
@Stebet

Hi!

What is the Title of the DVD?

blutach
22nd September 2006, 11:17
Mug Funky is correct, you can make a still last for minutes with just one frame and a heap of navpacks ("an animated still"). When demuxed, the M2V will appear shorter.

Regards

Stebet
22nd September 2006, 11:35
Do Parse D2V and tell me what running length is reported at the bottom of the parse log output. Make sure you have Honor Pulldown Flags for the project creation.

[EOF]
Running time = 0 hours, 50 minutes, 37 seconds

you could try a rip with stream processing... it's possible that there's a slideshow in the same VTS. in this case it'd play back to the correct length, but the video itself will be much shorter.

it could be something completely different though...

I have tried stream processing taking only the main Video (which is 720x576 @ 25 FPS interlaced) as well. Same results.

@Stebet

Hi!

What is the Title of the DVD?

Nine Inch Nails - And All That Could Have Been (Live).

Thanks for the responses guys. Although i've been encoding stuff for some time i'm still a bit of a noob on all the technical terms. Any help is greatly appreciated :)

neuron2
22nd September 2006, 14:35
[EOF]
Running time = 0 hours, 50 minutes, 37 seconds
Then DGMPGDec is seeing the entire video, so probably the demuxed M2V is OK and your subsequent tools are getting confused. My guess is that there is a spurious sequence end code at the 44 minute mark. You can use Restream to remove the sequence end codes. You can also use a binary editor to remove it. :)

Stebet
22nd September 2006, 15:10
Then DGMPGDec is seeing the entire video, so probably the demuxed M2V is OK and your subsequent tools are getting confused. My guess is that there is a spurious sequence end code at the 44 minute mark. You can use Restream to remove the sequence end codes. You can also use a binary editor to remove it. :)

What do you mean by restream? I think that sending the m2v through Avisynth (just as a pure mpeg2source, no processing) and playing it back in WMP resulted in a 44 minute video as well :/. I'll make sure once i get home though.

Do you think it might be my decoder? I have been using Nvidias PureVideo decoder simply because i love it's deinterlacing quality and of course it's hardware accelerated to boot. I'm feeding this all into Windows Media Encoder (WMV isn't perfect but it's a format that my Xbox 360 understands since i use it as a Media Center Extender). This is by the way the only video i've had these problems with. I've encoded some other footage (720x480, 29.97 FPS interlaced, taken from Radiohead - 7 Commercials DVD) and that comes out perfect.

I used to use Avisynth but i found it's deinterlacing quality not to be up to par with PureVideo (at least for this piece of footage) and Windows Media Encoder's deinterlacer is just horrible. It might be my noobishness though that's having an effect on that.

Edit: Found the Restream app. I'll try that once i get home and get back with the results :) Thanks for the hints.

neuron2
22nd September 2006, 16:52
I think that sending the m2v through Avisynth (just as a pure mpeg2source, no processing) and playing it back in WMP resulted in a 44 minute video as well :/. I'll make sure once i get home though. It's critical to verify that. Make sure you have Honor Pulldown Flags in your DGIndex project.

Do you think it might be my decoder? That depends on the answer to the above test.

Stebet
22nd September 2006, 20:56
Ok. Testing done (made sure Honor Pulldown was on).

demuxed m2v = 44:48 minutes
demuxed m2v thourhg Restream with "Clear Sequence End Codes" on = 44:48 minutes
demuxed m2v through AviSynth with no processing = 50:37 (correct time).

I'd guess that it's the Nvidia Decoder who is unable to read this video correctly then. Too bad i'll lose it's deinterlacer. So, the question now stands, any good tips for a good deinterlacer? Note that this is not the typical 29.97 -> 23.976 FPS transformation. This is a 25 FPS video and i'm totally inexperienced with deinterlacing those.

neuron2
22nd September 2006, 22:18
There are MANY deinterlacers for Avisynth. Why don't you make a small range select in DGIndex of a part that you think is particulary problematic to deinterlace and then demux that and post it for us to experiment with?