• SONAR
  • Possible effect bug
2013/11/21 23:41:33
Splat
Can anybody repro?
 
X3C
 
Steps
 
Middle of a project song...
Short audio Audio clip approx 3 secs.
Right click audio clip add vst2 effect that will last 3 times as long as the clip (has to be longer anyway) such as a delay or reverb.
Effect now assigned to single clip.
Play
 
Expected
 
Audio plays. Effect plays for 9 seconds
 
Actual
 
Effect only plays as long as the clip itself.
 
Cheers.
 
 
2013/11/22 02:42:45
brundlefly
Yes, I can reproduce this and the Ref. Guide says,
 
The Track view Clips > Bounce to Clip(s) command follows clip boundaries—effects tails are cut
off, unless you slip-edit the end of the clip to leave space.
 
which implies that tails will play out live without extending the clip. Slip-editing the clip out is an effective workaround for the live playback issue, but shouldn't be necessary by my reading.
 
 
 
2013/11/22 07:51:07
stevec
I've always slip-edited for clip FX for exactly that reason - "effects tails are cut off, unless you slip-edit the end of the clip to leave space."
 
2013/11/22 12:28:33
John
It seems to me it is a good feature. It allows control on the time the effect is heard. Also I don't read it as it will play without an increase in the clip length. 
2013/11/22 13:51:44
brundlefly
John
It seems to me it is a good feature. It allows control on the time the effect is heard. Also I don't read it as it will play without an increase in the clip length. 



If the clip already has to be extended to hear an FX tail non-destructively, why even mention that it has to be done before bouncing?
 
It makes some sense to me that the output of clip FX would be bounded by the clip in real time as well as when bounced, but that's not clearly stated.
2013/11/23 11:50:31
Splat
All good comments here thanks, I've logged it here (referring to this thread): CWBRN-21845.
2013/11/24 00:52:25
Anderton
IIRC it's always been like this with Sonar and is not a bug, but I think it flows from the structure of clips vs. tracks.
 
The clip length defines the totality of the clip. Therefore, clip length takes precedence over something that's a subset of the clip, which is the case with a clip effect.
 
However with a track, the clip is a subset of the track. Therefore, an effect applied to the track takes precedence over the length of a clip, and the effect tail will continue after the clip has ended.
 
I prefer this protocol because when adding clip effects, I'm interested solely in having something happen to that clip. If I do want an effect to have a "tail," then I can slip-edit to make the clip longer but I would not want this to be the default.
2013/11/24 01:13:47
Splat
Seems pretty clear to me that both behaviours should be available and should be set in the preferences area after this discussion.
2013/11/24 01:51:30
Anderton
CakeAlexS
Seems pretty clear to me that both behaviours should be available and should be set in the preferences area after this discussion.


 
I understand where you're going with this, but I don't know whether making this change would be trivial or difficult. If it's trivial, sure, why not? But (and remember I don't know coding!!) I get the sense it would require re-defining a clip to include that which happens when there's no longer a clip, or somehow divorcing the plug-in from the clip so it can have a "tail" that exists independently of its relationship to the clip...that seems like it might be hard to pull off. It's easy to have the tail exist independently of the clip when its frame of reference is a track instead of a clip.
 
It's like when I asked the guys at Ableton why when you recorded a performance it didn't record solo button presses. They said they considered the solo button a diagnostic feature for the studio, not something used in live performance (although I'm not the only one who uses it live). I said "so why not just make a preference where the solo button could either be recorded or not?" Seems simple, right? They replied that the solo button functionality was buried so far down in the code it would take a huge amount of effort to change something that was more or less hard-wired into the program's DNA, and they didn't know what might get broken in the process.
 
Seems to me that what defines a "clip" in Sonar might be equally immutable. But again, that's not based on anything other than a gut feeling.
2013/11/24 20:33:28
shmuelyosef
If you loop a clip, or replicate (i.e. multiple copies like is always done), does the effect carry over from copy to copy? Or does it clip any effects that run across the clip2clip boundary? I'll probably just go try this in a couple of hours when I get back to work.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account