Major BUG, Update...

For those who have followed the PANNING LAW bug ( http://forum.cakewalk.com/tm.asp?m=560199&mpage=1&key=򈱇 ), here is an update...

With -3db center laws:

1. I found that once a punch in has been done with Sound on Sound, the clip is "broken", If you chose to undo and re punch in with overwrite to avoid the volume bug, even in overwrite mode the punched in part is 3db louder.

2. If you record any track. Select it and right mouse click. Then select bounce to clip. The new wave form will now be "3db" smaller (except for the punched in part). I would think that the wave form should have been correclty drawn from the beginning.


Ron - have you guys been able to duplicate this? So far I have had a few people who have and I don't think it's a setup issue, I am pretty positive it's a bug in SONAR, and a pretty major one since you can have tracks that change levels on you without knowing it and if you have large projects you could have a mess in your hands (I am in the middle of tracking a band with many punch ins and tracks and now I have to go through every track which used punch-ins and make sure they are not all screwed up, 10 songs, a lot of my non-paid time wasted).


Regards,

did you report this problem to customer support? hope so, because they don't track
bugs in the forum (or don't make a policy of it that is).
jeff

Verified that this behaves exactly as Taz described on the -3db setting. I don't use the punch in function myself much but I know he does since he is recording bands and I just record myself. I also tried recording with the pan law set to 0 and then punching in. It recorded ok but when I switched to -3db pan law and bounce the track it is off by 3 db on the new track. I set it back to 0 on the pan law and bounce to another track and it is fine.

with a stereo track and it works perfectly no matter how the pan law is set

the pan law only affects mono tracks ... in stereo, the pan just attenuates the L/R
levels.

i'm glad you reported it to them 'cause sometimes people don't and they get
frustrated when there's no activity on their problem.

i guess the only work around is to use process->audio->+-/3db to correct
the punch in?

jeff

I read your original thread, as well as this one, and I'm not certain that what you're seeing is a bug. I can't check it at my DAW right now, but looking at the screen captures and reading the descriptions, it looks like it may just be proper application of the various pan laws. Keep in mind that certain pan laws can affect the apparent, perceived, or rendered center level, and the screen captures show mono waveforms in tracks, but with track interleave set to stereo. I believe I saw a post elsewhere on this forum that indicated that there were updates to SONAR 4's handling of interleave, to accomodate certain routing needs in the FX bin. It's possible that by having the track interleave set to stereo, you're feeding "dual-mono" signals instead of a true "center" signal, which could be affected by pan law.

Try setting your mono tracks' interleave to mono (one speaker in the track header, instead of two), and see if you still get the same problem.

If that's not it, then perhaps there is indeed something fishy going on; but first make sure it isn't just interleave / pan law interaction.

I understand that; but in the screenshots I looked at in the other thread, the tracks were set to stereo interleave, even though their content was mono.

When you say that you are testing "with mono tracks," do you mean that the content is mono, the interleave setting is mono, or both?