TRACK VIEW
1. MIDI INPUT Cannot select "NONE" defaults to OMNI 
Brando Remedy: Untick "Always Echo Current MIDI Track"
 
2. MIDI KEY   Cannot enter a value - not a bug - crappy design decision 
FBB Remedy: Put "MIDI key" in focus and press F2 for direct entry.
 
3. MIDI KEY   Changes by value of 13 instead of 12
 
4. MIDI KEY   TOO Difficult to use mouse to change value- You have to fiddle with it for a while to try to get to the value you want.
 
5. Double clicking on a midi clip will open the PRV but not to the Now Time. Usually opens PRV to begining  of project.
 
6. Browser does not display correctly when first opened.  If plugins/Intruments is selected only audio plugins are displayed. Must toggle plugins and then instruments to have the list populated properly.
This is also visa versa.
 
7. Prochannel EQ Plot does not update when knobs are moved.
 
8. Copy and paste clips does not always work correctly
 
9. Moving a clip - Some clips will not move. Some clips random unpredictable behavior.  Sonar selecting and moving clips on random tracks.
 
10. Cannot always slip edit a clip that has a fade in or a fade out. The fades must be removed first.
 
PIANO ROLL VIEW (PRV)
1. Sometimes will open zoomed all the way out and must be zoomed in to work on data.
 
GENERAL
1. SONAR CRASH on opening a project.
  Projects load in Sonar X1 without problem.
  Same Project will Crash Sonar X2a every time if it is the first project loaded.
  If it is not the first project open, Sonar X2a loads it just fine.
  Plugin which Sonar chokes is Kontakt 5 - Freezing this synth in the project cured  the problem. This was not a project specific problem. A new project was created which exhibited the same behaviour in Sonar X2a.
  NOTE: Sonar 8.5, Sonar X1 do not exhibit this problem.
2. Sonar cannot remember the video state of a project.  A project is closed while working in Track View.
The project will open with Multi-Dock maxed and Piano Roll View open.
 
3. Goes along with #2 above.  Load another project having 2 projects open and switch back to the previous project, same result as #2 above.
 
4. Freeze Synth not avaiable in Synth Rack but is available Via the syth track in Track View. Closing and reopening Sonar fixed problem.
As stated in the thread title this is not a comprehensive list.
You can add your own findings, and I'll update this post to reflect them. 
 

2. MIDI KEY   Cannot enter a value - not a bug - crappy design decision

Put "MIDI key" in focus and press F2 for direct entry.

+1000 for MIDI key. How anyone in development could have test driven that horrible little widget and given it the go-ahead is beyond me. You have to "home in" on the value that you want and nearly always overshoot the first time. Same with the slider widgets in the arpeggiator module. 

"Expected behavior" would be to have the option of entering a value numerically. But there's lots of aspects of the Sonar GUI which don't follow expected behavior, for instance the inability to rearrange tabs in the Multidock. I'd dearly like to know which GUI library they used, or whether they coded the widgets themselves from scratch. 

FastBikerBoy

2. MIDI KEY   Cannot enter a value - not a bug - crappy design decision

Put "MIDI key" in focus and press F2 for direct entry.

Well gee! LOL! Thanks.....


However it really should do that with a double click. There are certain ways in which people instinctively approach a GUI that are the result of experience with common software standards.

sharke

FastBikerBoy

2. MIDI KEY   Cannot enter a value - not a bug - crappy design decision

Put "MIDI key" in focus and press F2 for direct entry.

Well gee! LOL! Thanks.....


However it really should do that with a double click. There are certain ways in which people instinctively approach a GUI that are the result of experience with common software standards.

No worries. Not arguing about the logic, just providing answers where I can.....

FastBikerBoy

2. MIDI KEY   Cannot enter a value - not a bug - crappy design decision

Put "MIDI key" in focus and press F2 for direct entry.

 
Thanks!  At least we're not totally stuck.
The only thing is, I'll have to try to remember this for the next time I need it.
That is asking an awful lot from an old guy!
 
I am not even going to ask why on God's green earth anyone would think this is a logical and better design.
 
 

kevo


TRACK VIEW
1. MIDI INPUT Cannot select "NONE" defaults to OMNI
       

I am not seeing this - If I click on the input pull-down arrow for a MIDI track, or for a Simple Instrument track, the first option on the pull-down is "None" (X2A). When I select "None", I confirm that MIDI is not routed to the soft synth it is connected to. 

kevo


TRACK VIEW
  
6. Browser does not display correctly when first opened.  If plugins/Intruments is selected only audio plugins are displayed. Must toggle plugins and then instruments to have the list populated properly.
This is also visa versa.
 

 

Do you have a more specific recipe for this? I don't see this behavior. I normally open a default project template configured the way I like for a particular project. I have the Track View typically on my right monitor, Console view in the multidock on my left monitor, beside the browser, and the inspector floating on the same (left) monitor. By default I have the synth rack in the browser, but switching back and forth seems to have the correct behavior.

Brando

kevo


TRACK VIEW
1. MIDI INPUT Cannot select "NONE" defaults to OMNI
     

I am not seeing this - If I click on the input pull-down arrow for a MIDI track, or for a Simple Instrument track, the first option on the pull-down is "None" (X2A). When I select "None", I confirm that MIDI is not routed to the soft synth it is connected to. 

 
I have Sonar installed on 2 systems, and it exhibits this problem on both.
 
None is toggled, but Omni is shown after the selection.
The workaround is to select a midi channel or port not in use.
 

kevo


TRACK VIEW
 
5. Double clicking on a midi clip will open the PRV but not to the Now Time. Usually opens PRV to begining  of project.
 

I can't get this behavior either. I import a MIDI file into a MIDI track. My timeline is set to M:B:T format. My Midi clip is 17 measures long.
I click in the ruler at 12:1:00 to set the Now Time for the project at that point. I then move away to 2:1:00 in the Midi clip and double click. The PRV opens, with a marker at the upper left corner of the Midi to be edited, at 12:1:00.
Is this maybe a function of snap settings?