burning audio cds - burns tunes half a second into song

[---g---]

Hi guys,

Hoping you can help with something my searching could not find an answer for.

When I burn audio cds as of late, MM doesn't burn the tunes from the tune start, but rather maybe a fraction of a second into the track, thereby kinda starting when the tune has already begun, if just slightly. Since the only reason I burn audio cds is for djing purposes, this really screws things up.

Any thoughts? Thanks in advance!

[---g---]

no takers on this?

i've verified that it's def MM that's the issue here rather than, say, the cd player.

strange and since I rely on MM for dj music organization, more than a tad disconcerting

[nohitter151]

Are you doing any conversion or volume leveling? I could not reproduce.

[---g---]

no conversion, no volume levelling, no processing on the part of MM, just burning cds.

i have to say, it hasn't always done this, but lately, does it fairly often. not every time - so it doesn't surprise me that it might not be reproduced by a test - but often.
and when it does do it, it does it with every track.

huh

[Peke]

Can you make screenshot of your Burn Settings (Last page on BURN Wizard)?

[---g---]

will do, although perhaps the following would be instructive:

i just replicated the problem many times over for almost the entire set of cds I just burned for a gig tomorrow night.
even on the cdj i have here at home you can clearly see/hear that in order to cue the desired track correctly, you must 'negative' cue the track; that is, you can see from the status track display that the first sound occurs anywhere from 20 to 10 milliseconds into the previous track. doesn't sound like much but actually makes correct cueing impossible.

i tried burning at diff burn speeds, same result.

however, upon selecting track-at-once, enabling the 2-second gap, there wasn't an issue with the test cd i just burned now.
and i would like to clarify, it isn't that there is a 2 second 'negative gap' in which to cue the track, but rather the track actually properly cues at time 0.00.00, instead of -0.00.20

anyone care to comment on why this is, and why MM does this in particular.
thanks

[Peke]

It is just the way Audio CD Format is made and to get gapless playback on Normal Players Audio CD RED Book needs to be bent a little.

Result of that is that 1-3 Audio CD buffers (2356 Bytes if I remember it correctly) are preloaded by your DJ hardware and got overlapped
When i was more active as DJ I always burned CDS with Track At Once to ensure that next track is not started prematurely.

[---g---]

^
nice, thanks!

yeah i've verified with some tests that it's all about the track-at-once thing. weird, but at least i now know!

[DJ Nativus]

Hey, I'm having this exact same issue. In one burn, 20 seconds of a song is put at the end of the previous track. This is extremely frustrated and I've burned over 100 CDs with MediaMonkey and only recently discovered this.

I don't use Track-at-Once because I want CDTEXT (which doesn't show on the player anyways but shows in my car wtf)

Please help... I paid for MM and really frustrated.

[rovingcowboy]

Hey, I'm having this exact same issue. In one burn, 20 seconds of a song is put at the end of the previous track. This is extremely frustrated and I've burned over 100 CDs with MediaMonkey and only recently discovered this.

I don't use Track-at-Once because I want CDTEXT (which doesn't show on the player anyways but shows in my car wtf)

Please help... I paid for MM and really frustrated.

How many CPU's are in your computer?

[DJ Nativus]

Oh wow... interesting question. I have an i5 with 4 cores and I do have use multiple cores option checked in MM...

Is the burning getting ahead of itself?

[monkey hi fi]

Yep that's what I'm thinking with the new win 8 os and or faster cores.
rovingcowboy/keith hall/monkey hi fi

[DJ Nativus]

I updated to 4.1beta and disabled on-the-fly encoding and it seems to have fixed it =D

Now to go through 100 CDs and check for cut-offs v.v

[rovingcowboy]

Oh good you at least got it working..