Brando

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?

Also - if I don't set the Now Time before hand, and just double click in the Midi clip, the PRV comes up with the edit marker at the point where the Now Time is set in the project in Track view (the time where I double clicked in the MIDI clip in Track View) - this behavior seems right to me.

kevo

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.
       

Not doubting what you are seeing, just not seeing that here. I have "None" as first option, then "All inputs", "Audiobox Midi In", "Oxygen 61 Midi in", "Casio USB- MIDI in", then "studio1" (control surface).
Both the Oxygen and the Casio are USB. 
Maybe a function of number of Midi Inputs? 
(On Edit) - I confirmed (again) that when I select "none" from the pulldown, "None" is displayed in the MIDI input both in Track View and in the MIDI view of the inspector.  

kevo


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.

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.
 

I checked Freeze synth in the Synth rack, and in Track View - both seem to work as expected here. I suspect this has more to do with the issues you identified that are having with the browser more generally. I just confirmed with an instance of Alchemy in my project, and the same short 17 measure MIDI clip I used previously. I can select Freeze in either the Synth rack or in Track view, and the freeze/unfreeze process seems to work the same, regardless. I have never noticed the button being missing from the Synth Rack. Again, as before I am not doubting that you are seeing this - I am just letting you know I am not. It may be more intermittent than I have ever noticed before.


On Kontakt 5, I use it all the time, and it is a synth in my default new project template (26 tracks, incl 16 drum tracks and some soft synths and basic audio tracks). Never had an issue with Kontakt 5. My issues tend to be known or expected - 32 bit synths or effects that I haven't figured out a way around yet, or where I push the CPU hard in larger projects. 
I have heard of project import issues from earlier versions of SONAR, from other users. I lost a hard drive between X1 and X2, and made a decision to not re-install X1 or 8.5.3 when I upgraded my OS to win 8. All I can say is I have not noticed this as an issue. 

 For what it's worth - I hope this helps.

Have you reported it to cakewalk? (Problem reporter) Thanks for your help.

Brando

kevo

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.
     

Not doubting what you are seeing, just not seeing that here. I have "None" as first option, then "All inputs", "Audiobox Midi In", "Oxygen 61 Midi in", "Casio USB- MIDI in", then "studio1" (control surface).
Both the Oxygen and the Casio are USB. 
Maybe a function of number of Midi Inputs? 
(On Edit) - I confirmed (again) that when I select "none" from the pulldown, "None" is displayed in the MIDI input both in Track View and in the MIDI view of the inspector.  

http://screencast.com/t/55sR7lgpjw
 
 

kevo

http://screencast.com/t/55sR7lgpjw

 
 

If you go to Edit-Preferences, under MIDI - Playback and Recording - Playback Do you have "Always Echo Current MIDI Track" selected, by any chance?
If I select that, I get the same behavior you are seeing (from your vid clip above). 

Brando

kevo

http://screencast.com/t/55sR7lgpjw

 

If you go to Edit-Preferences, under MIDI - Playback and Recording - Playback Do you have "Always Echo Current MIDI Track" selected, by any chance?
If I select that, I get the same behavior you are seeing (from your vid clip above). 

Great catch, Brando.  I've just tried it and you're dead right.
 
It makes perfect sense.

jb101

Great catch, Brando.  I've just tried it and you're dead right.

It makes perfect sense. 

This is a capability that I use somewhat regularly without issue so I was surprised to see it listed as a "bug". (To be fair the OP said "problems and bugs") FWIW, I also looked at a lot of the rest of the list. IMO, there are interface/GUI issues that complicate using X2 - a lot of the visuals tend to be "fiddly" and are more complicated than they need to be. But I don't have the specific issues identified (but I would support some fixes/enhancements to some of the processes currently required to do these functions) - even the Pro Channel has been fine for me after the initial fix for the vanishing PC modules. I have all ProChannel modules including the new C2A. The inability of X2 to remember its video state is a minor annoyance for me as well - I think screensets help that a lot and some of FBB's videos can help to resolve a lot of the issues.
I don't know if the OP is going to come back in to acknowledge the setting selection for 'always echo'. Maybe it's something else? Just offering that it seems to be working here as expected, and if he needs any additional help to check out or verify, or can offer up a more repeatable formula for the other items on the list I would be happy to look into them.

@Brando.
 
I agree with everything you said there.
 
I found X1d solid as a rock, and since X2a have found it just as good.  I also have all the PC modules and have no issues with any of them, apart from a lack of talent on my side..
 
I have found that everything I use in Sonar works as expected.  It is strange that people can have such different experiences of the same software.  I KNOW it works here, but have been accused of lying/ working for Cakewalk for saying so by people who seem to be having a terrible time with it.
 
I wish I knew why.  Often it is pilot error, but not, I think, always.

jb101


@Brando.
 
I agree with everything you said there.
 
I found X1d solid as a rock, and since X2a have found it just as good.  I also have all the PC modules and have no issues with any of them, apart from a lack of talent on my side..
 
I have found that everything I use in Sonar works as expected.  It is strange that people can have such different experiences of the same software.  I KNOW it works here, but have been accused of lying/ working for Cakewalk for saying so by people who seem to be having a terrible time with it.
 
I wish I knew why.  Often it is pilot error, but not, I think, always.

I think sometimes it is the need for self-validation of a DAW choice. Like the God Particle thread. (Paraphrased - 'I made the switch to a DAW I like better, please agree with me that I made the right choice').
Also - I think many people have strong views and clear expectations and for what someone calls a "bug", someone else may find a "workaround" - and find an alternative way to use a workflow better suited to the app. It may be user unfamiliarity with the features of the DAW - especially where they may have a long history with the product line and aren't comfortable with the changes made. 
I like X2 and it works well here and I don't look for validation for my choice. When the Reaper/Studio One/(and Mixcraft) threads start and people begin to look elsewhere for DAW Nirvana I weigh the value of SONAR to me and so far I am very happy with the choice I made. (Like you, the only issue I have is when someone calls me out for my choice or calls me a liar because my experience doesn't match theirs.)
I will say that I genuinely believe that there are many SONAR users, especially X1 and X2 who are having real performance problems - including crashes, severe freezes, dropouts, etc. 
Maybe we're just lucky.
LOL.