Scenarist error : Audio garp larger than 1 frame (seamless branching ?)

Hi. I am trying to backup Metallica's S&M disk 1. When compiling in Scenarist I get the following error : Info Multiplexing VOB Main Stream Error Audio Gap is 3 frames "D:\METALLICA\VTS01\VTS__01_V001-80-448K-[0ms]-ch6.AC3". Error Please use longer audio file if you want to play VOBs seamlessly. Error dvd_mux : DoMux Multiplexing Error Error Terminated Multiplexing (Metallica-VTS01_002_Track_t.vob.0). Error Audio Gap in the previous track is larger than 1 audio frame. Please use a longer audio stream in the previous track when you playback VOBs seamlessly. Error Multiplex is failed. Error Multiplexing failed, Track "VTS01_002_Track" Error MuxFromDB:MuxVTS failed Error Multiplex failed Error DVD Video files could not be created FYI, VTS01_001_Track contains contains 20 minutes of video (1-angle), VTS01_002_Track contains 4 minutes of multi-angle footage (streams VTS01_002 to VTS01_006) and then VTS01_007_Track contains another 8 minutes of 1-angle fottage. 1) Is it seamless-branching ? 2) Assuming the answer to the first question is yes, is there any way to fix the audio gap, so that Scenarist will compile without errors without losing the seamless transition from 1 scene to another ? 3) If seamless branching cannot be achieved, how can I overcome the audio gap error, so that Scenarist will compile even non-seamlessly ? I am willing to try to see if non-seamless branching is really THAT annoying.

Did you demux by vobid and use dummy audio streams? If so, this is most probably the cause of it.

It's not so much that it's seamless branching but that's it's seamlessly connected to another vobid in the layout.. 3 frames short is actaully quite common, i usually find 6-10 is average. If you used ScenAid on this title (or want to), you can activate the "Add silence......vob vobid demux" under "Audio Options" which will add in this case about 6-8 frames of silence to the end of you audio allowing scenarist to except this. - I add 2x the number of frames in case of misreporting (IMO It's actually a good idea to let it do this for most of you demuxes including PGC as this routine not only adds silence to the end of the file but if there's errors in the ac3 file, this corrects them.. the down side is yes it'll check/fix every ac3 file in that demux so the time to scan goes way up... however it'll only do this once, if the 'fixed' asset exists, it skips it)