Tweaking your system??

robert_e_bone
About the only other thing I did was to set the Minimum Processor State to 100%.

robert_e_bone
I am a bit unclear on a couple of things:
 
1.  Are X2 and any other prior versions of Sonar also installed on the same computer that is running X3c under Windows 8?
Yes but not running.
 
2.  It looks like the latest drivers for the FireWire 800 came out in November of this year.  Are you running with this version?  It also indicates that for this version to run correctly that you need to update the firmware, as well.
All my drivers are up to date 


This is the text snippet from the downloads page for your FireWire 800 interface:
 
"Windows 7/8 32/64 bit PnP driver for Fireface 400, 800, UCX, UFX, version 3.081. Requires the latest firmware version! 11/22/2013"
See #2
 
3.  Do you have all Windows 8 maintenance applied?
Not sure.. Do you  mean updates? if so than yes 


4.  You have multiple interfaces listed.  Which one are you using?
All 3 are used in Sonar.  


5.  Are you using ASIO as your Sonar Driver Mode?
 No WDM/KS


6.  What happens if you create a new project in X3c, with some 64-bit soft synths and perhaps some audio?  (does it also stop playing?)
I actually have not done that yet. Have not gotten that far. Need to get the program functioning first.
 
At first GUESS, I would imagine there to be some issues from 32-bit plugins present in these older projects, where something slightly different in X3c is exposing an issue with one or more of those 32-bit plugins, causing your issues.
Good point! I had not thought of that. Tho I do not have some of the plugs anylonger.
 
It seems to me that there have been a pretty good number of threads where one or more 32-bit plugin has had trouble in some version of 64-bit Sonar.
 
Many folks have moved to limit or even eliminate use of 32-bit plugins in a 64-bit Sonar installation.  
 
I have made a deliberate choice to ONLY allow a small number of 32-bit plugins to be even present in the search path for 64-bit Sonar (X1d, X2a, and X3c).  I DO keep 32-bit versions of all 3 of those Sonar releases, and those have access to all of my 32-bit plugins.
 
On my system, running as above, I have no issues such as you are having.
 
Perhaps you could do some experimenting with either swapping out your 32-bit plugs for 64-bit ones, or work in a 32-bit install of X3c, or finish those projects in X2a, and move to either limit or eliminate 32-plugins moving forward.
Is there a tutorial on how to seek out all 32bit plugs in Sonar? I will do research and figure it out. Wierd that it worked in X2 tho.... Go fig?

Thank you all so much for all of your helpful input & feedback! I welcome it. Keep it coming.

Kevin
 
 
 

4.  You have multiple interfaces listed.  Which one are you using?
All 3 are used in Sonar. 

Five0SixBand
I opened X2 and played my soft synths and played a couple old projects everything played fine moved tracks from interface to interface. Closed it out opened the projects in X3 raised my buffers in Sonar and played with my bit settings and finally getting one of my projects to play but you can still feel my audio drivers stuttering a bit. Still trying to figure things out. So many battles to fight to get this set up functioning the way I need it to do what I need it to do.

robert_e_bone
I believe your issues ARE the result of the WDM drivers being used, rather than ASIO.
 
To TEST that, I was hoping you would drop to a single interface, get its drivers squared away, with you selecting ASIO for a driver mode, an ASIO Buffer Size to start with of 128, a recording bit-depth of 24, and a Sample rate (both Sonar and the interface must match) of either 44.1 k or 48 k.
 
I just want to try to isolate the dropouts, and the above is a pretty simple test.
 
So, if you don't mind - please try the above and post back on the results on your dropout situation.
 
Thanks, 
 
Bob Bone
 

robert_e_bone
Don't give up on us just yet.
 
There is no reason I can think of why using a single audio interface and setting things up for it should end up with no sound, so I think that deserves revisiting.
Agreed
 
Please detail any and all steps in making and testing your testing of the use of the single interface.
I am going try this again shortly. Just getting in for the evening. 


Also, when you made those changes - did you test it using a new project? (A nice simple import and playback of a WMA/MP3 audio file to an audio track, perhaps)
Actually no. I will try it that way this go around.
 
And, did you make sure to power cycle your audio interface after making the ASIO Buffer Size change to 128?  (It is recommended to do so after making settings changes).
Again no I did not think of that either. I did however reboot the system if that matters.
 
Thanks for hanging in there - we will collectively do our best to help you figure this out.  My rationale in asking for the single interface ASIO testing is to get to a place where the dropouts are gone, and I believe it likely that the use of a single interface, configured with Sonar for ASIO driver use, should be able to do that.
I understand that and believe me when I say that I sincerely appreciate you guys help with getting my system running!
 
I look forward to hearing back from you with the details on your ASIO test of the single interface.
Will report back