I'm not sure I understand what you mean. There are no effects send MIDI envelopes in SONAR. On MIDI tracks you can have vol, pan, or MIDI param envelopes.

On the instrument track you will see MIDI Velocity clip envelopes as well as all the AUDIO related envelopes. You cannot see the track automation for the MIDI data since there are no widgets for MIDI track parameters available on an instrument track. Instrument tracks are intended to be a very simple interface for manipulating synths.

If you want to manipulate the MIDI track envelopes, then simply split the instrument track back into its MIDI and Audio components, make your edits and combine them back. The envelopes are not lost, just hidden. i.e they will be rendered as before.

Instrument tracks are primarily a simpler user interface to dealing with synths nothing more.

ORIGINAL: Noel Borthwick [Cakewalk]

Yes the metronome bug with Multiprocessing has been addressed along with other known metronome issues.

ORIGINAL: Noel Borthwick [Cakewalk]

Real programming, what's that? <g> Seriously what was unprecedented for us, was the amount of work that was done this time on internals - i.e. features that are not directly user visible or stuff that looks very simple on the surface. Myself and Keith spent the greater part of this year staring at code in the audio engine. When you see code permanently etched on your retina you know you have a problem :-)

Overall I hope this explanation helps makes the case to our users for optimizations and internals being treated as equal to other user visible features. I've seen posts where users feel that they shouldn't have to pay for optimizations.
If anything optimizations are far more costly to implement and test than many normal features. Why? Because they potentially require very extended testing. For a case in question - the feature I worked on to allow dynamic reloading of the audio engine. This was required to allow making dynamic configuration changes. Though it was implemented early this year it took many months of tweaking to get the bugs out and make it work right. There were hundreds of little exception cases to cover. The same applied to dynamic arm and the innocent looking "MinimizeDriverStateChanges" feature (required to keep ASIO/WDM devices independently running from the transport). Both these exposed a ton of driver incompatibilities that we had to work around and/or work with hardware vendors to help them resolve their problems.

Our beta testers sure had their work cut out for them this time round and we're grateful for their help and patience while we worked through all of this.

ORIGINAL: Rothchild

If you'd had said that the first time I'd have ordered it on Monday! ;-)

Thanks Noel, this really is far more interesting and shows that ya'll have been doing some real programing and not just negotiating license deals on soft synths! :-p

Ta
Child