BeSweet GUI Question: Affect of checking DVD2AVI delay setting

[FulciLives]

Hello :)

I am using BeSweet (Beta ver 1.5b15) along with the BeSweet GUI (Beta ver v 0.6.b69) and I am attempting to go from a 5.1 AC-3 to a 5.1 AC-3 with the built in PAL -> NTSC (25.000 to 23.976) preset and so far everything is working correctly BUT here is my question:

I used DVD2AVI to demux the AC-3 file so I have checked that option in the BeSweet GUI so how does that affect the newly created AC-3 file? Is the new file 0.0ms now or is it still -80ms which is the value given in the file name that DVD2AVI created. I intend to use this AC-3 with an authoring program (haven't decided which one yet) to create a DVD so I guess I kinda need to know the correct delay value for the new AC-3 file. It would seem that BeSweet is correcting the new file to have a delay of 0.0ms ... can someone verify this for me please :)

Thank you!

- John "bubthezombie" Coleman

P.S.
A note to DSPguru if you are reading this ... in the past the aforementioned preset for PAL -> NTSC (25.000 to 23.976) always resulted in many errors such as tapping or clicking noises but that seems to be fixed and it appears to be working just fine now so THANK YOU very much!

[frank]

Demuxing AC-3 stream doesn't effect the delay value. All AC3 frames stay unchanged!

The delay is only corrected on WAV decoding to 0 ms.

[FulciLives]

Hello :)

I know if you demux the AC-3 using DVD2AVI that the delay value (given in the file name created by DVD2AVI) is the correct delay value but I am using BeSweet to convert that demuxed AC-3 into an AC-3 file (due to the conversion of PAL -> NTSC as I am converting a PAL DVD to NTSC) and in doing THIS step I haved checked the DVD2AVI delay option present in the BeSweet GUI so my question is does doing that then create a new AC-3 with a "fixed" 0.0ms delay or does the newly created AC-3 still have the same -80ms delay that the original demuxed DVD2AVI AC-3 had?

Thanks!

- John "FulciLives" Coleman

[frank]

Oh, sorry for misunderstanding.

I think that delay is a muxer parameter referring to the video stream, and not included in the header of AC3 streams.
Only file name shows it.

But let's ask DSPGuru.

[DSPguru]

if you compensated the delay when transcoding (even to ac3), the delay will now be 0.

the a/v delay can be found originally in the pts (timestamps of audio, video) in the vob.

@FulciLives
issue is indeed solved :)