• SONAR
  • Odd Region FX issue (p.2)
2015/04/02 13:57:08
Keni
I seem to remember that bounced clips appear with no name and I'm guessing that is to avoid confusion with the original... Though I would think an edited name with a marking to show it is a modified version would be a more elegant solution?
2015/04/02 18:29:31
Zargg
I would agree with Keni. I would use the "freeze track" button. That way you could always ""un - freeze" the tracks if needed.
2015/04/03 00:45:20
Lord Tim
The workarounds (archived original in case I need to get access to unmodified files and frozen effected track) are great, but they're definitely things that can slow a session down dramatically when you're doing a lot of tuning work.
 
If I've got, say, 50 takes of a backing vocal choir that I'm tightening things up on, and I'm working through each layer to see what needs fixing (if anything - choirs are often best left untuned) then this is something that'd take forever to archive/freeze when it should be a case of "let's fix this quickly" and not worry that what you're doing is the last opportunity you have to work on it in that manner.
 
The other thing is too, if I've finished working on a tuned lead vocal track and I've bounced it all down, and then decide to do a vocal double and use VocalSync to tighten the timing up, then I'm kind of stuck if Region FX is busted.
 
Semi-related to this: I'm actually surprised that bounced clips have no name. Is that a normal thing? I've never noticed that before. It would make sense that it should say SOMETHING in there (Record nnn (bounced) or something?)
 
Anyway, really hoping this is just my installation that's the problem rather than a bug or a design choice because it's a bit annoying.
2015/04/03 02:59:04
Sanderxpander
I've definitely re-Melodyned bounced clips (though like you I obviously try to avoid having to) so it's not a "general bug".
2015/04/03 12:42:51
mcstringer413
yeah, I've noticed since Melodyne was introduced with Sonar, that bounced Melodyne clips never had a name. i got in the habit of re-naming them right away so I could identify them correctly.
 
2015/04/03 15:08:02
Rob[at]Sound-Rehab
Hi!
 
I've had something similar happening today but haven't had to the time to follow up / test again ...
 
I used the new "Vocal Sync" on 2 lead vox tracks ... worked fine ... then I clicked the "Render" button on the "Vocal Sync" GUI and it bounced the clips (I usually used freeze/unfreeze up to now but thought if the button is there I give it go) ... then continued mixing but later could not get another instance of VocalSync to open on any of the BackVox tracks (i.e. which only had original recorded clips but no edits s far) ...
 
Anyone seen something like that? Anyone can reproduce this is in a small project???
2015/04/04 03:05:41
Lord Tim
Just tested it then.
 
The rendered VocalSync file does indeed lose its clip name, however I'm able to start a new instance of VocalSync on it.
 
I'm NOT able to get Melodyne to activate on it though. If I undo back until it was its original Record nnn clip name, any Region FX works as expected.
 
Really weird!
2015/04/04 03:11:06
Lord Tim
Further testing - it appears only Melodyne is affected for me. VocalSync works on bounced Melodyne clips too.
 
And here's the big one (and a workaround!) - if I go into the clip properties and actually give the unnamed clip a name, Melodyne does indeed activate correctly after it's been bounced.
 
So a test for you, FreeFlyBertl: Try using VocalSync as you would normally do, render it, and then on that newly rendered clip, double click it to open up the properties in the Clip Inspector and then give it a name. Then try and VocalSync the rendered clip again. I suspect it'll work. 
 
EDIT: Sanderxpander - you nailed it in your earlier reply, re: naming the clip. I must have missed that in all of the other replies! 
 
2015/04/04 05:22:35
jb101
I guess there is a reason that bounced clips don't have a name. What would you call it if you bounced several clips together into one clip, which I often do?

Best to leave it blank, IMO, and leave it up to the user.
2015/04/04 05:26:29
Lord Tim
Sure, but following that logic why name recorded takes either? To me it'd make more sense to come up with a naming convention much like each recorded take has, eg: TrackName (Bounced nnn)
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account