Using BeSweet to split loses sync?

[TorgoGuy]

I'm doing some DVD backups. I'm using Besweet to convert from AC3 to MP3. I've not had any problems with sync, but on my current DVD I want to cut a bit of stuff off from the front and back of the D2V project. So in AVISynth I added my "trim(1134,222042)" and it looks like AVISynth trimmed it at the correct frame.

Next I have to trim the corresponding audio, so converting 1134 frames to seconds, I did the calculation 1134/29.97:

Cut 1134 frames divided by 29.97 fps = 37.838 seconds

This is 29.97fps material--not a telecined movie. So in my besweet command line I added "-split( -start 37.838 -end 7408.809 )"

When I mux it together (I've tried two different muxers) the audio sync is off. I can manually adjust it (the audio seems to be about 160ms early), but anybody know why this is happening? If I encode this same DVD without trimming in AVISynth and BeSweet the audio sync is fine.

I've used search, but so far haven't been able to find any help. Anybody know why this is happening? Is it maybe a playback problem? (I've tried a couple of different computers).

[TorgoGuy]

Whoops. Forgot to give y'all my log:
===================================================================
BeSweet v1.5b23 by DSPguru.
--------------------------
Using azid.dll v1.8 (b825) by Midas (midas@egon.gyaloglo.hu).
Using lame_enc.dll v1.32 (8/8/2003), Engine 3.90 <http://www.mp3dev.org/>.

Logging start : 01/21/04 , 09:31:51.

C:\AudEnc\BeSweet.exe -core( -input M:\Proj\OSTER\OSTER_DELAY_0ms.ac3 -output M:\Proj\OSTER\OSTER_DELAY_0ms.mp3 -logfile M:\Proj\OSTER\OSTER_DELAY_0ms.log ) -ota( -hybridgain -d 0 ) -split( -start 37.838 -end 7408.809 ) -azid( -L -3db -c normal ) -lame( --alt-preset 64 -mm -q0 )

[00:00:00:000] +------- BeSweet -----
[00:00:00:000] | Input : M:\Proj\OSTER\OSTER_DELAY_0ms.ac3
[00:00:00:000] | Output: M:\Proj\OSTER\OSTER_DELAY_0ms.mp3
[00:00:00:000] | Floating-Point Process: Yes
[00:00:00:000] | PostGain normalize to : 0.97
[00:00:00:000] +-------- AZID -------
[00:00:00:000] | Input Channels Mode: 2/0, Bitrate: 192kbps
[00:00:00:000] | Total Gain: 0.000dB, Compression: Normal
[00:00:00:000] | LFE levels: To LR -3.0dB, To LFE 0.0dB
[00:00:00:000] | Center mix level: BSI
[00:00:00:000] | Surround mix level: BSI
[00:00:00:000] | Dialog normalization: No
[00:00:00:000] | Rear channels filtering: No
[00:00:00:000] | Source Sample-Rate: 48.0KHz
[00:00:00:000] +-------- LAME -------
[00:00:00:000] | 'abr 64' preset is used
[00:00:00:000] +---------------------
[02:02:50:976] Conversion Completed !
[02:02:50:976] Actual Avg. Bitrate : 60kbps
[00:08:14:000] <-- Transcoding Duration

Logging ends : 01/21/04 , 09:40:05.
===================================================================
Everything is synced just fine if I don't do any trimming in AVISynth and BeSweet. 160ms is about 5 frames difference so it is quite a bit.

[TorgoGuy]

A bit of additional information--As I stated before, if I don't do any trimming they sync is OK. Going on the premise that BeSweet isn't cutting at the proper point I decided to encode the whole thing to MP3 (using BeSweet) without any cutting and then cutting the MP3 with another tool, so...

I used MP3Trim to trim to the MP3 frame nearest to my cut points. It isn't exact cutting in this fashion, but the audio sync was much better than before, so it *seems* like BeSweet is at fault, but I don't know how that could be since others don't seem to be having this problem.

Any ideas?