• SONAR
  • freeze tracks don't correctly read midi volumes on clips
2016/12/10 16:59:39
JJ9
Have tried exporting audio, freezing audio, even recording real time to a track and bouncing.
 
The crescendos I've put on my midi clips work fine until I try the above. Any idea how to get them to work when creating audio from the midi?
 
Thanks
 
JJ
 
Using Sonar x1 (not got around to loading up my Platinum yet)

2016/12/10 17:32:24
promidi
Maybe try the automating the volume rather than using controller events? (7 or 11).  That way, when you freeze the track, the volume crescendo can be changed even while the track is frozen.
2016/12/10 17:35:22
chuckebaby
promidi
Maybe try the automating the volume rather than using controller events?


Solid advice right there.
This is the way I do it.
2016/12/10 20:25:16
soens
It would still be nice to know why the OP's example happens.
 
Though he didn't say if it's a softsynth or an outboard synth, I would expect an outboard synth to sound the same when recorded in real time as it does playing the MIDI clip.
 
Softsynths I can understand as freezing is a processed algorithmic representation of what's heard when playing the clip, rendering the MIDI data inoperable afterward.
2016/12/10 23:10:32
Rafaway
I was about to create a new thread to a similar problem I'm facing when I found this one.
 
I'm trying to bounce/freeze/export a MIDI Clip I recorded with iZotope Iris 2 (Vst3) and am having no success. All MIDI modulation I recorded (mod wheel, Pitch Bend, etc) work fine when I playback, but they simply disappear when I bounce to audio. Sonar (Platinum) just ignores all this performance related MIDI messages when turning to audio. Oddly, in the same project, lots of others virtual instruments bounce as they should.
 
I have tried a bunch of things to bypass this issue without luck (fast bounce, slow bounce, vst2 version, re-recording, manually drawing midi cc, etc). I remember having a similar problem with an Arturia Synth (SEM V) a couple of years ago but, in that case, simply doing a slow bounce did the work. Assuming JJ9 is having an equal like problem (with another softsynth?) maybe this a Sonar kind of bug... Maybe someone has solved it before? Unfortunately Iris 2 is an essential tool in the project I'm working now and I just can't change it for other options. 
 
Any ideas?
 
Thanks,
2016/12/11 01:34:59
mettelus
Have you tried recording that track output into an aux track or buss? It only works for real-time, but was added to SONAR to do pretty much what you are trying to do.
2016/12/11 03:05:52
rcklln
Sometimes I don't get the results I expect unless I Bounce to Track using the What You Hear preset.
2016/12/11 03:24:41
Rafaway
mettelus
Have you tried recording that track output into an aux track or buss? It only works for real-time, but was added to SONAR to do pretty much what you are trying to do.



mettelus, super thanks! That's a great workaround. I guess I could even call it a "manual bounce", since that's what roughly a bounce would do in this case, record a vst performance to an audio track. Still don't know why Sonar can playback it but fails to bounce it correctly. Nevermind now that I can do it manually with this added patch point feature.
 
For JJ9 however it won't be a solution because this is possible only with Platinum and Professional.
 
Thanks again, mettelus!
 
2016/12/11 07:28:19
bitflipper
I've seen this phenomenon with a couple synths (and because it's specific synths, I don't blame SONAR for it). The first time I ran into it, the workaround turned out to be a realtime (slow) bounce. After that I got into the habit of using slow bounce for everything. That is, until I encountered a different synth that exhibited the same behavior but only worked correctly with a fast bounce. Nowadays, I use fast bounce by default and only switch to realtime if the synth exhibits a problem.
 
As for automating the bounced audio as a workaround, I routinely do that, too. But I like to get swells and fades working the way I want first, before bouncing. The subsequent audio automation is then simpler and cleaner and just for purposes of mixing. Another limitation is that audio automation doesn't address other programmable parameters such as filters.
2016/12/11 09:26:50
JJ9
Thanks for all the replies
 
Have tried everything you all have suggested. the synths are third party Vienna instruments. I have done the automating volume and this is what is not working. I guess the only work round is to take off all the automation when bouncing to audio then remix the audio...very time consuming though.
 
thanks again
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account