Hadn't used Cakewalk for a week, but it ran smoothly for 6 months. Just tried to open file and waveforms say (busy) and no sound. Loaded Sonar demo file with same result. Loaded all my other files with same result. Tried all remedies I could find on this forum with same result. Using Hammerfall DSP Multiface II which as of this moment works fine with Sony Soundforge. Any ideas? Thanks.

Eddy Yates


Hadn't used Cakewalk for a week, but it ran smoothly for 6 months. Just tried to open file and waveforms say (busy) and no sound. Loaded Sonar demo file with same result. Loaded all my other files with same result. Tried all remedies I could find on this forum with same result. Using Hammerfall DSP Multiface II which as of this moment works fine with Sony Soundforge. Any ideas? Thanks.

Sounds like Sonar couldn't get through the driver.
You didn't have Soundforge open by chance?
 
Also, just for clarification, you say you "loaded" files. All of them. What does that mean?
 
Brian

OK. Nobody around to answer this, so tried a bunch of stuff. Solution was to go into Edit/Preferences/Audio/Drivers, de-select all the RME input and output drivers, close preferences, close Sonar, open Sonar, re-select all the RME input and output drivers. Success....at this point, I don't even care WHY. What a waste of time.

Thanks for weighing in, Brian. Soundforge was not open. I shut the computer off to make sure. Is "loaded" the wrong verb? Sorry. I opened a whole bunch of Sonar projects...old ones, new ones, none of them played, all had no visible waveforms, all clips/waveforms said (busy). Just can't figure out why this would happen without me making any changes...I opened a project I recorded in X1 on my laptop, and that was the start of it. I've done exactly the same process 40 times because I interview people on the laptop and produce the radio show on my main computer.

Be sure that you've checked "share drivers with other programs". Also, sometimes 8.5 will hang on "busy" - as in busy drawing the waveforms. When that happens, I select the offending clip (or track) and then Bounce to Clip which forces a redraw of the screen. Once the waveform is drawn, all is usually well. No need to shut anything down. It also occurs, since you said these are old files, they might be gone from the Pic Cache so Sonar is having to recreate each one and that could choke the system if there are a bunch of tracks' worth, although, from your system specs, that doesn't appear be much of an issue. Just some thoughts.

Thanks, Paul. Using X1(d). Next time will try the Bounce to Clip thing. I tried opening new and old files and the same thing always happened. Never had this problem before with X1. 8.5 did it a few times. Good answers, guys. I appreciate it.

  Hmmm. Sonar X1 ran smoothly all day yesterday. Today I opened the file I was working on and (busy) again on waves, but audio still plays. I let it sit for a minute, then the clips came up and were blank, but audio still played. Not too concerned since I can get the waves back, but wonder if anyone knows why this might be happening now. I believe in preventative medicine rather than bandaids. Also, I'd rather not have to "bounce to clips" until I've finished editing the whole thing, just in case there are some funky edits I hear later...much tougher to fix them blind without seeing the previous edit marks.

I wonder if this could be a case of the picture cache being full or messed up?
http://forum.cakewalk.com/tm.aspx?m=2288776&high=picture+cache
 
It doesn't appear deleting all the cache files could hurt, anyways. I know I've seen BJonesey comment about this issue before.

Thanks, SToons. I delete the Picture Cache before I do any big editing, and usually in the midst of big editing. In fact, the cache was empty when this happened. You said "messed up" picture cache....I don't know what that means. Any thoughts? Thanks.

Eddy Yates


Thanks, SToons. I delete the Picture Cache before I do any big editing, and usually in the midst of big editing. In fact, the cache was empty when this happened. You said "messed up" picture cache....I don't know what that means. Any thoughts? Thanks.

Could this be an issue with the drive the Pic Cache is on, or an issue (as in funky file path) with where the pics are creating?
What happens when you don't delete the Pic Cache?
 
Brian