Reverb tails bounce to front of clips/mixes if 'play reverb tails after stop' is not check

I've always had 'play reverb tails after stop' un-checked.... and now with X1c when I bounce a mix, track, or anything involving a bounce, the reverb tails that are in the buffer from where I stopped before bouncing will then pasted them selves mixed in to the front of the bounced mix or track. un-checking that option is the current work around. This happened in front of a client and I had no good explanation as to why there was verb singing mixed in to the front of a piano only intro..... :(

Blogman


I've always had 'play reverb tails after stop' un-checked.... and now with X1c when I bounce a mix, track, or anything involving a bounce, the reverb tails that are in the buffer from where I stopped before bouncing will then pasted them selves mixed in to the front of the bounced mix or track. un-checking that option is the current work around. This happened in front of a client and I had no good explanation as to why there was verb singing mixed in to the front of a piano only intro..... :(

Myolpal, on occasion I have had that happen.



FWF, after playing a song I typically wait about 5 seconds or before a bounce. So far I've lost 6 minutes and 35 second of my life to that wait time.

Hi, Blogman--That's an interesting glitch/bug.  

I'm not understanding, though, why you've always had "play reverb tails" un-checked.  If you use reverb, and it's pretty rare when reverb isn't needed - you have to have that option checked.  

What's supposed to happen with it un-checked, is the project will stop at the literal end of the last clips, unnaturally truncating the reverb tail.  Of course it's not supposed to skew the results, with the reverb ending up at the start!--

But - keeping that option engaged-checked, isn't the "work around" (which indicates a routine one is forced to adapt in order to get around a program's problems)--it's the only way to use reverb successfully.---

Randy B.

ba_midi


This is a long-standing bug with a few versions of Sonar where after a mixdown/bounce, subject to system settings, there is still data in the audio buffer.

I just got so used to it, and my 'fix' is to simply hit play, then stop once to clear it - then continue on.

Whether that "play tails" setting truly affects this or not, I haven't checked.

But regardless, I consider it a bug (a never-fixed one).

One man's bug is another man's annoyance.^TM

bitflipper


Yup, it's one of those been-around-forever bugs. Not all reverbs exhibit this behavior though, so I'm not sure it's actually a SONAR bug or not. The Sonitus reverb and delay are two that are prone to it.

UAD EMT 140 does it.

---I still don't get it. If you use a reverb, you want the tails to be recorded - so why aren't you guys turning that option on?--Or are you saying this weirdness happens even with the right setting-? I've never seen anything like what you're talking about, I always use reverbs, leave the "record tails" option on, since it's necessary. Randy B.

pianodano


I don't recall ever printing reverb nor would I ever want to. That type of effect would be added post recording except for the  talent cue which would be in the phones only.

Right, of course - But I thought we were talking about reverb on a final master mix - My wrong assumption I guess.  You mean this has been about rendering a reverb on just a clip before the 2 track master-?!--


Randy B.

bapu

ba_midi


This is a long-standing bug with a few versions of Sonar where after a mixdown/bounce, subject to system settings, there is still data in the audio buffer.

I just got so used to it, and my 'fix' is to simply hit play, then stop once to clear it - then continue on.

Whether that "play tails" setting truly affects this or not, I haven't checked.

But regardless, I consider it a bug (a never-fixed one).

One man's bug is another man's annoyance.^TM

Too true :P

OK, I guess I finally get why this buggish behavior is something I've never noticed - I haven't printed reverb to a clip since I first started using Pro Audio 9 and didn't know (for a little while) that there was any other way to do it.  I think I get it--this is all about printing reverb to clips prior to mixing--right?  - Why is anyone still doing that--?

Randy B.

I have this happen to me when bouncing down a complete mix for export  (and not, as some suggested, for printing reverb to clips).

Funny thing is, there was one song where I had this echo/decay reverb sound print at the beginning of my mixdown and it kind of sounded cool.  So I decided to keep that part.

It was a happy bug, but a bug nonetheless...

yes I meant to say 'checking the box' is the workaround. I think you smelled what I meant. As far as the reverb box being un-checked: Even when this is unchecked, the reverb/delay tails still go to the master mixdown. This box is just the option for when you stop the playback. Personally when I'm starting and stopping a song, editing or comping or jumping around checking section I don't want to hear the reverb/delay tails. If I want to hear 'em I wouldn't have hit the stop button. When I say 'stop', I mean 'Stop'.... that means you to hybrid vienna verb, and mr. ping pong delay. This is happening on final mixdown export, track bounce, freeze synth, all leftover audio buffer stuff (verb, delay, etc..) May not be a new bug, but it never affected me until X1C.

Tis an interesting thread. I always noticed the "noise" in front of my next play but never thought it could be tied to a specific plugin... once it started in a project it was part of the project.

Need to investigate how I have the play reverb tail checked or not checked.

Thanks
Jim

Bristol_Jonesey


I've noticed this in X1 & 8.5

My workaround is to simply slip-edit the length of a clip - any clip (but it makes sense for it to be the clip containing the reverb tail) so that the project only stops when the tail's volume has dropped to zero.

That is somewhat of a different issue I think.

If an "audio clip" ends before the FX tail completes, then slip-editing is definitely the solution to that scenario (and I do it all the time before final mixing).

I don't think the setting of "play tails" has any effect on this at all.

Bristol_Jonesey


I think you're right Billy.

I've got into the habit of doing this routinely on every project.

One good thing -- if you forget to do it and start mixing, Sonar reminds you quickly by NOT playing the tails

rbowser

ba_midi


That is somewhat of a different issue I think.

If an "audio clip" ends before the FX tail completes, then slip-editing is definitely the solution to that scenario (and I do it all the time before final mixing).

I don't think the setting of "play tails" has any effect on this at all.

Yes--and OMG - throughout this thread I have been totally in la-la land about the topic.  I was thinking that the "play tails" setting was about having reverb ring out at the end of a song during the final mix down.  Totally wrong - hehe, look at my old posts.  Over and over I was confused - I think anybody who could see I was out to lunch was politely ignoring me.  


OK, so what's being talked about here is an issue that's never effected or bothered me.  So I'll shut up now.  


--well, I do want to add that instead of slip editing clips at the end of a song, I just select how much I want in the time line.  Somehow that works for me.


Randy B.

Randy - if you are doing a mixdown, as example -- and the very last clip that can play reaches its 'end boundary' before the time range you select, I think you'd see this bug.

Let's say you have a brass hit as the very last event in the project and the boundary of that hit ends at  bar 150 beat 3 tick 180 -- but your time range is through bar 152 ...  the clip will stop sounding any FX or notes at 150:3:180 since there is no more clip to play.  And no more data following it, so the track rendering shuts off, so to speak.

Try it, you'll see.

However, if you slip edit that last clip (the hit) to bar 152 (ie, the right boundary edge) it will continue to sound any FX through that time range.

If working with a groove clipped loop, sometimes it's necessary to first flatten it (depends on a few conditions).