@ you're a riot!!
 
Ok, My biggest issues with my RME giving me warnings or Sonar giving issues comes when I pop open RME DigiCheck to use it for the Spectral Analyzer or the Vector Scope or the EBU Meter. It will save and force to a particular sample rate. I use WorkSpaces to save all the instances the way I like them on the screen. Then I have different work spaces depending on the sample rate.
 
For example, I'll have Totalyzer and EBU for 48, same for 96... etc.
 
The RME Tools tend to win over Sonar when flipping the sample rate to the device. Then Sonar gives a message about whether to reset. Before I click ok, I flip the DigiCheck instances to the right rate (matching the Sonar project). Then I flip back to Sonar and it won't matter which button I click (yes or no) everything will be fine.
 
Space to restart playback and I'm good.
 
I have no troubs watching anything on the interweb while working in Sonar. For that matter, can use DigiCheck to record a song off youtube/youporn haha while mixing a separate project using Sonar without having any problems. (Of course, if there were probs I could just do it again). But the idea is there. You can record using digicheck while using Sonar and your same RME for other purposes as long as the rates align. You still have only one clock. Stopping and starting Sonar doesn't seem to have any impact on the recording you are making in DigiCheck. I sometimes even bounce tracks while capturing some other input.
 
A recent real world example was a friend from work gave me 2 90 minute cassettes and asked me to record them into the computer. I did so while mixing tracks on computer.
 
@ is right to point out that if some other program on your computer is pushing your RME to a different sample rate, that this could be your problem. For me, that thing is almost only ever DigiCheck. I have never had a problem with a web browser doing this.
 
As an aside, I almost always run at least one instance of DigiCheck while I mix in Sonar. For that matter, I've learned a lot by watching the Totalyzer while watching Netflix.
 

AT
What is broken?  SONAR, total mix, your computer?  You need to go through and make sure in your SONAR project there are no busses sent to nowhere.  Same w/ totalmix.  If you look at the far right of the mixer in SONAR you'll find the hardware outputs (ie., your RME).   Those might not be obvious, but you can slide it open just like the busses pan.
 
Since I"ve been using 2 interfaces I will sometimes get this w/ the master output - I then find the correct ASIO driver and everything is hunky dory.
 
Finally, if you are connected to the internet and running youtube/youporn and MS sound through the RME, SONAR sometimes doesn't connect right after all the various bit depths and sample rates that are involved.  Or at least my TC Konnekt can get disconnected from SONAR.  And if you reinstall any RME software it may revert to the main output for those computer sounds.  It did for me when I installed drivers for the new interface.  It is quite a surprise to get extra loud error beeps through my mains when I'm mixing etc.
 
@

There are too many oddities, too many inconsistencies when only running sonar that do not appear when running Samplitude.  System and interface have been rock solid for 4-5 years.
 
I am not going to write a dissertation every time I get a bug in Sonar.  I just throw out my experience in hopes that someone else may have experienced it and know a workaround. 
 
Its amazing to me, the group of people who do not seem to understand my explanations.  My descriptions suffice for the people who are not making apologies for the software.
 
That said, its what I'm using now, I accept that its not as solid as Samplitude as long as I can find workarounds. 

We try to help for no pay or for anything other then simply sharing our knowledge with others so they can have a great time using Sonar. 
 
You came to us this year I and many have been here since day one doing for others. For you to see us as nothing more than apologists for CW is patently wrong.
 

How to Get Help Here

Originally Posted by John. John thank you for the wonderful post.

This is meant for new members of this forum. Welcome! 

When posting a question please incorporate this information in your post. The more information you include the better your chances of getting the help you need. 

1. SONAR version. This should include whether it is the Producer Edition or the Studio Edition. It is very important to also include what version number as well i.e. Ver 1.00 or Ver. 6.2.1. Without this information we will have to ask you what you are using. This will delay an answer to your question. 

2. Audio gear. List any and all audio cards or audio interfaces you are using. Include driver version too. 

3. MIDI gear. List all pertinent MIDI interfaces you have in your system. The brand and drivers also. Any outboard MIDI gear may be useful as well to include in your post. 

4. System specifications. Processor, memory, hard drives.The operating system with any service packs should be noted. 

5. Judgement will help you to decide just how detailed you are in giving your specs. But more information is better then not enough. 

6. What you include will of course be dictated by the type of question. 

This section is from members that have added to the 6 points above. 

From Houndawg 

Subjects like "HELP ME!!!" or "My Sonar Sucks!" (or anything all caps) will or often should go ignored by the forum. 

I spent many years as a repair/upgrade tech and tech trainer. One of the most valuable lessons I learned and taught was this: "The more accurate and detailed the description of problem, the better the chance of it getting fixed quickly and right the first time." 

From Phrauge 

Don't start a new thread in reply to a previous thread. 

Don't post the same question in several forums. 

Read the furnished materials. 


From Me 

And to add to your post above . Please try a search on the forum first. Often your problem has already been asked and answered. 

From Cryophonik 

1) If/when you solve the problem, please post your solution in the thread. Other users are likely to have the same problem at some point. I can't count how many times I've searched for and found a thread pertaining to a problem that I just encountered, but the final post in the thread is simply "nevermind. i figured it out." 

2) use your spellcheck, especially for any keywords that are pertinent to the problem. When you mispell a word, it makes it impossible for the Search function to find it when the person searching spells the word correctly. 

From Kennywtelejazz 
Excellent point , and a thanks for the help can go a long way also 

From Nick P 

1) Search the forums, especially the Home Studio forums, BEFORE posting a question. From my experience, over 90% of the questions I see on the Sonar Producer and Studio forums and so elementary as to be much more appropriate for the Home Studio forums, which, BTW are EXCELLENT sources of knowledge and information for almost all Sonar users. There are a couple of guys over there who seem to do nothing but help beginners and newbies. Highly recommended. 

4) After doing this if you still can't figure out your problem, go ahead and post to the Sonar Producer and Studio forum. 

From Songcraft 

- Don't flame the situation. Sure, we all have bad days but try and understand there are a lot of good people here who "volunteer" to help. 

Now please feel free to ask away. 


 post edited by Marketing [Cakewalk] - April 25, 08 9:54 AM
 
The above was posted a long time ago.  I think its still relevant today.
 
 
 

I dont give any extra respect, consideration, or fealty to anyone based on post count or "reputation"; either help or don't help.  People who play act as internet police have serious problems.  This place is no more yours than it is mine because I paid for the software just like you.  Don't try to enforce internet hygeine, syntax, spelling, or comprehension.  Don't try to serve as informal PR for Cakewalk, making it seem like bugs are user error or lack of understanding.   Either help or don't help, the rest of the BS do on your own time.
 
 
 
 
 

Here is a screenshot of my project.  The yellow circled busses keep disappearing to "none".  Even once I put them back to what they should be, the project will not play audio until I close and reopen sonar.
 
I am able to recreate this bug by closing this project (when its working), creating a new empty project, then reopening this project.  I get the error dialog saying the busses are missing.  I reset them but sonar won't play audio (at least out the bus that was reset) until I close sonar and reopen the project.
 
****ed sonar forum still won't let me attach image.  YOu will have to use your imagination.
 

PM me the link and I'll replace this post with your image.
 
When you describe a new project and opening your old project is a method to replicate the issue, are both projects at the same sample rate?
 
We all have bad days, but being kind and respectful to the forum members and Cakewalk staff as well is pretty much a requirement.  While you are just in the very beginnings of building your reputation, many have been active contributing members for decades and have indeed built considerable reputations. (Who is that Craig Anderton anyway?)
 
I recognize that the characters and personalities of the forum members are not known to you and that you are frustrated and just seeking help. Everyone posting on your threads is trying to help you. Just so you know, there are hundreds more reading and choosing when to chime in. If they feel they could help you more, they will. Often times when the more expert aren't chiming in it's because they feel you are getting adequate help from the members who are helping you.
 
IMHO, it looks like props are to Boydie who answered you on the first reply.
 
And the talent on this thread! Dude, you've got the right people trying to help you.

I have been having mostly bad days since buying Sonar X3.  Its pretty and a great UI, but I'm starting to reevaluate if its suitable for my needs based on the bugs and inconsistencies.  Next I am going to downgrade my RME UFX drivers to a prior version to see if that helps any.  Seriously, this machine has been rock solid, stable and done everything I asked until I started using Sonar.
 
Here is a video of the Sonar X3 bus drop bug.  This has been a very stable machine for the past 4-5 years, primarily used with Samplitude Pro 11 (no bugs).   
 
https://www.youtube.com/watch?v=eO1EqHxQrNY

So you have some basic problems.

The first project is at 96 K and the second at 44.1 K. Both projects are at 16 bit. This is visible on the control bar at the bottom of the screen (I keep mine there too, nice choice).
 
I suggest you go into preferences and change the File settings to Record at 24 bit.
 
I believe you are not using the ASIO Audio Drivers. That is why Sonar is not dynamically switching back from 44.1 to 96. Please, check preferences driver mode. What is it set to?

I am using ASIO.  
 
In the audio devices menu, project is set to 24bits but it is greyed out.  I have no idea why it is at 16 in this project or why I cant change it.  There is nothing in the UFX ASIO menu that locks the bit rate.  
 
The default was set to 44.1, but I changed it to 96.  Weird stuff going on here...
 
 

See this help file.
http://www.cakewalk.com/Documentation?product=SONAR%20X2&language=4&help=AudioPerformance.06.html
 
Your UFX will ALWAYS work at 24 bit. The question is how many bits will Sonar write when creating the files. The UFX doesn't have a 16 bit setting.
 
Do me a favor, try setting default project setting to 96 K and re-do your test where you create a a new project and switch back. I'm not at home today, so I can't re-execute your test, but I all the time switch between projects of differing sample rates without issue. I will try to replicate when I'm back home.
 
Do you have the Clock set to the device?