Wow - love the changes, but last night I had the first freeze in years, and it was back to back, meaning I could replicate it.  The system locks and says sonarp something .exe has stopped working (sorry, I am at work and do not recall the exact message). I followed the installation instructions - even taking care to dot the lower case j's  (simpson humor).

I need to do further testing because there were a lot of things happening - BUT - in the broad view of this case, I went into an old project that did not have midi in it - I added a dimension pro synth, accepting the basic prompts, and went to work creating a very simple chord progression.  I worked through about half the song in about 20 minutes - recording, not liking, deleting, recording again, and got the first freeze (sonar not working). I restarted Sonar and got back into the project - the next time it took about 10 minutes, same thing - but when I tried to launch sonar again by double clicking, it wouldn't - looked into the running apps, and sonar was still running.  There was one new addition to my setup - a M Audio Axiom keyboard.  I used it before this update and it was working perfectly creating a new song before this update, but this problem came from working on an older project - so its a different test case.

Odd - but then again, I need to really hone in on the specifics.  -I will try to figure out the exact steps - document my exact setup, and send it in.  We will get it figured out.

Still - love the update Cakewalk and your support. 

L      

And I didn't realize how much I missed indented folders until I got them back.

 
Ditto.  That and the new EQ are my current faves, with the ehnanced quick groups in a close second.   Then again, I haven't had the opportunity to play with the new FX Chains so that may change...   
 

LLyons


Wow - love the changes, but last night I had the first freeze in years, and it was back to back, meaning I could replicate it.  The system locks and says sonarp something .exe has stopped working (sorry, I am at work and do not recall the exact message). I followed the installation instructions - even taking care to dot the lower case j's  (simpson humor).

I need to do further testing because there were a lot of things happening - BUT - in the broad view of this case, I went into an old project that did not have midi in it - I added a dimension pro synth, accepting the basic prompts, and went to work creating a very simple chord progression.  I worked through about half the song in about 20 minutes - recording, not liking, deleting, recording again, and got the first freeze (sonar not working). I restarted Sonar and got back into the project - the next time it took about 10 minutes, same thing - but when I tried to launch sonar again by double clicking, it wouldn't - looked into the running apps, and sonar was still running.  There was one new addition to my setup - a M Audio Axiom keyboard.  I used it before this update and it was working perfectly creating a new song before this update, but this problem came from working on an older project - so its a different test case.

Odd - but then again, I need to really hone in on the specifics.  -I will try to figure out the exact steps - document my exact setup, and send it in.  We will get it figured out.

Still - love the update Cakewalk and your support. 

L      

Hey LLyons, you mentioned that you added Dimension Pro to the project. This may or may not be your issue but there are certain patches in Dimension Pro that will crash Sonar (Reaper as well, and I assume other DAWS) in the same manner that you speak of. Just something you may want to rule out as when this first happened to me I was pulling my hair out for a while. 

Post #18 of this thread has a solution if in fact it's DP that is crashing your project:  http://forum.cakewalk.com/tm.aspx?m=2055768&mpage=1


Anyway, on the topic of X1D. Thumbs up :) 
Since the last quickfix for X1C things have been going well for me and thankfully X1D continues to be solid. It's nice to see some of the smaller bugs get weeded out as well. Hats off to the Cakewalk devs on this one.

I had a small issue yesterday and I'm not sure if it was a one-off.  I switched screensets and a small band of graphics remained from the previous screenset.  I switched back and forth a few times after that and the issue did NOT re-appear.  As I wrote...'small issue.

amiller


I had a small issue yesterday and I'm not sure if it was a one-off.  I switched screensets and a small band of graphics remained from the previous screenset.  I switched back and forth a few times after that and the issue did NOT re-appear.  As I wrote...'small issue.

Much more likely to be a graphics glitch amiller. It sometimes happens if another process wants display time rather than just processing time. I often get it on my non DAW studio system when shrinking a full screen YouTube video back into the YouTube browser window whilst Skype is active on my other monitor. Its a bit random, I am sure its nothing to do with X1, I have noticed, along with many others, that screensets actually seem to operate quicker and smoother with this update.


Garry

Sorry for the long paragraph above but CW forum is not allowing for paragraphs I redone this post 7 times and it stills jumbles it all up wtf! Sorry Guys..

strikinglyhandsome1


It does in Firefox. You have to use 'br' between the less than and greater than symbols.

Then you get this.

Ahh Thanks I normally post from either my Mac, or my Iphone,, This morning I used my Pc Laptop which has Internet Explorer.. Never noticed that,, 

 Ahhh Thanks .. 

As far as "turning off the floppy drive controller", perhaps some people haven't realized new machines and their BIOS don't even come with a floppy drive or controller any more, so that can be ruled out.

My apologies................ my psychic ability to deduce the age of people's systems from a forum post is on the blink.

I can assure you that slow screenset changing is not the norm on my machines, including my old machine with a lowly 256mb graphics card, something else on your system eating graphics memory perhaps?

FastBikerBoy

As far as "turning off the floppy drive controller", perhaps some people haven't realized new machines and their BIOS don't even come with a floppy drive or controller any more, so that can be ruled out.

My apologies................ my psychic ability to deduce the age of people's systems from a forum post is on the blink.

I can assure you that slow screenset changing is not the norm on my machines, including my old machine with a lowly 256mb graphics card, something else on your system eating graphics memory perhaps?

I know my memory gets eaten up by other things.....

trimph1

FastBikerBoy

As far as "turning off the floppy drive controller", perhaps some people haven't realized new machines and their BIOS don't even come with a floppy drive or controller any more, so that can be ruled out.

My apologies................ my psychic ability to deduce the age of people's systems from a forum post is on the blink.

I can assure you that slow screenset changing is not the norm on my machines, including my old machine with a lowly 256mb graphics card, something else on your system eating graphics memory perhaps?

I know my memory gets eaten up by other things.....

Mine too. Mainly by......er....sorry..... I've forgotten.

 I love X1D!

I get a white screen that last alittle longuer than in X1c. I know this issue has been debated in some other threads but I stil don't know what causes sonar to go into that stat before it loads the project. any thoughts will be welcomed. other than that it seems to run nicelly. awal

Bub

Ryan Munnis [Cakewalk]

Just so you know I'm not trying to be argumentative. I just want people to know that we didn't update all of CWBRNs to "Fixed" as a joke.

Believe me, I'm not laughing, and take this very seriously for several reasons. One, I have very limited time and I need it to work when I use it, and two, I didn't get your software off some hack site.

This particular report has two attached project files that have automation snapshots for ProChannel parameters. One of the project files is from your system that you sent is in CWBRN-5546, the other project is a project file I created myself to clearly identify the bug more easily.

The problem myself and others have seen with the PC turning modules on/off have had no automation in the project.

Your project from CWBRN-5546 did. I have the project. I was just commenting on the report we closed as fixed since you got notification of it. You said we updated it to fixed but suggested it wasn't actually fixed. I was just providing clarity on why that particular report was fixed in case it seemed confusing or misleading. 

 We've told you that over and over again but you keep latching on to the automation bug. It's great that you got that fixed, but that's not the only scenario were PC modules will behave erratically. 

I know. We had other reports from people who provided some really good specifics. It's two completely different issues. This has nothing to do with tunnel vision, I worked on the other reports as well and told you I believed you from the beginning. I try not to take things on here personal, but that comment sort of was. I'm just trying to gather details, not challenge anyone. In any case, I was just commenting on CWBRN-5546 because I didn't want you to think we were careless with the report since you seemed disappointed the report was closed.

Anyhow, if you're still experiencing some weirdness I'd be more then happy to look into it again. We haven't been getting any other reports internally of this for a while now but if you've stumbled onto something else, as always my ears are listening.

Best regards,