Maybe there are some 'technical' difficulties in implementing this.
Maybe the transport related code is too tied to the now time.
I am a software person and I've come across situations where in order to provide a simple feature, you may have to redesign, reimplement lots of things.

You didn't mean to reply to my post directly, right? -Susan

ORIGINAL: John

I for one have no use for a "pause" in Sonar but, I am most distressed by the few that seem unable to support forum members requests to CW. Having a pause will not harm Sonar for me or disrupt my work flow. Yet having members arguing against a request of another member is bad form in my opinion. We need to stick together in our quest for a better Sonar. This wont happen if we fight each other on features we want. By showing support for features we personally don't see a need for will in the end help us to get those that will. I am a MIDI centric user many of the features in Sonar are of limited use to me. Yet whenever a member wants a new feature that has no current analog I will support their petition. Others have done the same for me.

So you have no need of it. So what. Others do, leave it at that.

Only when something is asked for that will harm Sonar will I be unsupportive.

CW add the pause asap!

Best
John

ORIGINAL: barthowk

Oh, I'm sure this has already been requested, but what about compression for midi events?

ORIGINAL: Susan G

YES, a Pause button would allow the transport to temporarily stop without moving the Now Time.

Lordy, lordy, again with this!

Hi Donald: This has been hashed and re-hashed ad infinitum on this forum, honest! You can probably find explanations of the difference a true Pause would make just within this thread, but if you do a forum search you should find plenty others. In a nusthell: Don't change the Now Time, don't rewind to the Now Time, don't DO ANYTHING except pause playback, period!

-Susan

ORIGINAL: F@KKER

ORIGINAL: barthowk

Oh, I'm sure this has already been requested, but what about compression for midi events?

two ways:
1. use compression on the sampler
2. reduce velocities by percentages

F@KKER

I agree with F@KKER -- that's about all you can do, which is quite a lot, if you consider that you can apply any available Audio effect to an Audio track you're sending MIDI instructions to. Available MIDI FX are quite limited, since the sound generated is totally dependent on what internal or external synth you're using. Most have a Chorus and Reverb, maybe an Arpeggiator, yadda-yadda, but you can't really manipulate the sound the way you can once the MIDI events are translated to Audio. I assume you already know that MIDI sends instructions to an internal or external synth re what to play and when, etc., but doesn't actually produce any sound at all.

-Susan

For example with a midi event compressor you could set a threshold below which no compression of velocity would occur. Nuendo has one that I found to be really cool - it was just like a regular audio compressor, but for midi events!

ORIGINAL: Susan G

Ah, I see! It's already possible to do that in SONAR using Process | Interpolate, correct? Maybe not all that intuitive due to the UI, but certainly possible.

-Susan

• The new snap-to-channel-width feature in the Console was a good idea. However, this is a REAL BUMMER on multiple side-by-side monitors as one track or buss ALWAYS ends up split between monitors. Please somehow make it so that one can switch between infinite-width-variablity and snap-to-track-width modes. [holding down CTRL while adjusting width would be perfect]
  
  
• I absolutely love the X-Ray feature. Real time and tendonitis saver! One improvement would really help: when windows are in X-ray mode, they should be taken out of the CTRL-TAB window list. This is why: I use the X-Ray to keep all my FX up and positioned nicely while I work on the Track and Console views by CTRL-TAB'ing between the two. Then I de-X-ray to use or view the FX. With all the FX still in the CTRL-TAB list while X-rayed, I have to CTRL-TAB MANY times to just get between two open and visible windows.
  
  
• Split stereo busses. In other words 1 buss Fader with two trim controls, two FX bins and two aux sends controls for each aux send. In each case one being for the left channel and the other for the right channel. This allows slightly different or very different FX settings to be used for each channel. Just think of the possiblities!
  
  
• True stereo panning controls throughout: i.e. instead of a single pan control, have one volume control each for left and right. Or something of the Cakewalk innovative way that accomplishes the same thing.
  
  
• One button to bypass the whole FX bin.
  
  
• The FX bin should really be re-sizable -- so you can see all of the FX at the same time without getting tendonitis trying to click on the tiny arrows.
  
  
• Ability to Freeze and unfreeze multiple tracks in one action.
  
  

For example with a midi event compressor you could set a threshold below which no compression of velocity would occur.