jsg


Apparently the people posting above don't use the staff view.

Same bugs since X1c:  Snap-to functions do not work when entering notes on staff view.
                                    Track pane in staff view doesn't switch active tracks, as in all 
                                    previous versions of Sonar.

                                    Often piano roll view and staff views do not refresh properly, 
                                    remnants of old view still present

These bugs (and others in event list) keep me from using it.  I've always upgraded, this time no way.  Cakewalk is simply not listening to users who spend a lot of time in the staff view when sequencing.

JG
www.jerrygerber.com

Which version are you using now?


You're right about the assumption of staff view for me here anyway. Never use it, so if you're having troubles I hear you for having frustration. I used to use staff view a lot in Logic and Sonar. Just less and less midi work there now.

Have you made the install like it was supposed to (roll ,back to the unfixed patch)

in the browser when previewing loops...i used to be able to use my up and down arrows to cycle up and down to preview the different loops..an example is..i click a loop and it plays as normal..then if i hit the down button,it goes to the next loop and preview that one,an so on..well no the up and down arrows have no effect what so ever...dude..this stinks..that was my meat and potatos for browsing loops..could be something maybe i need to set(something in cakewalk.ini ??? or maybe in preferences..but for right now..i cant figure it out...anyone else?

Thks for the rap Bud ;)

Seems solid as a rock here. Not one crash or glitch. I don't use staff view very much (and not for entering notes anyhow). I think the new Pro channel EQ is a big improvement! Still checking it all out, but no issues so far.

Getting some freezing behaviour if I use the mouse to locate a node in the new EQ. Sometimes after you make an adjustment, the EQ just freezes and you can no longer adjust the frequency curve. You can then adjust the knobs but their settings don't reflect in the frequency curve area above. This is channel specific as one channel will stay frozen, but others will work fine.

"inaheartbeat"
I presume the fix will be in the next Softube release.

Be careful what you wish for...

"Softube Plug-Ins Changelog - version 1.3.5"

All changes up to 1.3.4

VST3: Fixed latency compensation

Windows: Graphics issues when using multiple displays fixed

Windows 64-bit: Fixed a bug causing crashes when using lots of memory

Active EQ: Fixed a problem causing audio spikes when changing values

Love X1d!

The only niggle I have is that my old(er) eyes have a hard time reading the tiny frequency label fonts on the new EQ. But hovering over the knob makes it better.

I'm sure all you youngsters out there are laughing!  

Well that's good to know! Now I can make obscure references to Beverly Hillbillies episodes..

Bub


I recently installed X1 Expanded. That started a string of BSOD's which I've never seen before. I also had several tracks go silent that I had been working on and had to scrap the project.

Then I installed X1D for Expanded last night ...

The very first thing I do is try to use my shiny new Saturation Knob. I adjusted it up, went too far, and turned the knob back down, but unfortunately it wouldn't back down. In other words, if I turned it all the way up, then turned it all the way back down, it was stuck all the way up. I can turn the module off and back on and it's still stuck. Plus ... the tracks that I used it on, crackle and pop now, even after a reboot. Another project scrapped.

I wasn't paying close attention but I could swear the comp module turned on by itself which has been a nasty bug in X1 since day 1. Oddly, I got an email a couple days before the D patch was released stating that the problem had been fixed.

I've pretty much given up all hope of this mess getting straightened out. Like the song says, "Three steps forward and two steps back." (See link below)

Bub, at this point it's pretty obvious your computer is all sorts of messed up. There has to be some sort of hardware issue.

musicroom

jsg


Apparently the people posting above don't use the staff view.

Same bugs since X1c:  Snap-to functions do not work when entering notes on staff view.
                                   Track pane in staff view doesn't switch active tracks, as in all 
                                   previous versions of Sonar.

                                   Often piano roll view and staff views do not refresh properly, 
                                   remnants of old view still present

These bugs (and others in event list) keep me from using it.  I've always upgraded, this time no way.  Cakewalk is simply not listening to users who spend a lot of time in the staff view when sequencing.

JG
www.jerrygerber.com

Which version are you using now?


You're right about the assumption of staff view for me here anyway. Never use it, so if you're having troubles I hear you for having frustration. I used to use staff view a lot in Logic and Sonar. Just less and less midi work there now.

I'm using Sonar 7.0.2 in 64-bit mode with Win 7 -64 bit and 16GB RAM.  It works as expected in all the audio and midi functions I use.   I've been studying X1 since the beginning on my office computer (not my DAW) and continue to have much trouble with it.    I cannot justify inheriting a bunch of new bugs when sonically, musically and ergonomically I see no benefit.   IF the developers of X1d had fixed the bugs in the staff view so that the track pane changes active tracks, and IF they had left the color customization intact and IF the note values selected in the floating control bar consistently were congruent with the note value placed on the staff and IF the screensets refreshed properly, I'd probably upgrade just to stay current, but would still not gain any real sonic, musical or ergonomic advantage in doing so.   Sonar 7 is already 64 bit and my hardware is the best available (Adam S3A speakers, Yamaha DM2000 mixing console, Big Ben digital clock) so sound-wise there's no gain. 
 
I actually like some of the ergonomic changes of X1.  I don't however understand why the developers created extra steps in creating audio volume envelopes, unless you have the right color scheme, the wave image becomes too faint to see it when selecting that track and using nodes on the envelope to fine-tune dynamics.  Doesn't make sense to me.  Simplifying the interface is not a bad idea, as so long as it doesn't cause a lot of extra steps (keystrokes) in getting common things done.  I see the trade-off, also I understand the financial necessity of issuing new versions, otherwise they'd go out of business!  But still, I want to see the developers focus on repairing what's already there rather than introduce new features while leaving old ones broken.  
 
I'll continue using Sonar 7 until I can't use it anymore.  But this time I am totally open to looking at Digital Performer for Windows and Cubase, when for many years I would not, and had no need to, consider other DAWS.  My real hope is that the developers at Cakewalk address the issues I've been seeing.  But if not, Sonar 7 on my new system is more than good enough for quite some time.   
 
JG
www.jerrygerber.com
 

For me, X1D has finally severed the psychological umbilical cord to 8.5.

edited for clarity

I think the Bakers have cooked us up something special here.
 
Before X1D, when I tweaked FX such as the LP64_MultiBand_64 I would get an instant audio engine stop.
 
Now I just get momentary audio silence when adjusting the frequency, and no loss of audio if I am altering just the level.
 
Often when opening a new project and triggering a soft synth for the first time the audio engine would stop. Now this doesn't happen.
 
Big thumbs up here, my compliments to the chefs

I think X1-D is great! Been using it straight for three days and no problems yet.  I love the new key bindings updates-I use them all the time.