Be honest about your Sonar X1 "bugs"

The metronome switching itself on when you enter the preferences page is absolutely a bona fide bug...

And I hate the metronome!

(I find it funny that even if you delete the metronome buss the thing still comes to life from beyond the grave!)

Oh there's plenty of user ignorance out there, which is why there's a lot of furore here, ignorance being put down as bugs or some sort of X1 failing. But........there's also a fair smattering of bugs. I've probably reported about 9 or 10 now in total. 6 or 7 of those are now "submitted to development".

Not to mention the long standing bugs that haven't been fixed.

Well I admit I have been very pro - Sonar X1 but I think I've run into somethings that are bugs that I find very annoying... 

Audiosnap being broken sucks

the snap settings seem to change on me and I've gone into preferences to change the magnetic strength and stuff for using the PRV view and working with MIDI has been so annoying at times that I've started using the Step sequencer some more.. perhaps someone could enlighten me as to if this is a bug
Notes in the PRV don't snap to where I want them and I have to "fine tune" to put them exactly where they're supposed to go. 

Other than that.. things are generally ok

Dale Aston


I have found that the majority of what I first thought were bugs/problems have turned out to be me not knowing how the program works.  I've been around Cakewalk since the beginning and this version is almost a complete paradigm shift.

True, there ARE flaws in the code however most of my problem reports have not panned out to be real bugs. 

I can chalk up mine to around 75% = user ignorance.  What about you?

I'm not going to stay in this thread for various reasons, but I think one would first have to ask if a user knows the difference between a bug and a user error.
 
For those who don't bother to read the manual and are coming from previous versions of Sonar, a LOT could "look" like a bug.   Just look at all the intial posts about "where did my keybindings go!?!" ....  this to me is all about not taking the time to "learn" about the changes in THIS version.     I bet CW got a bunch of bug reports on that one alone.
 
So to ask others to be honest about what they consider a bug makes some assumptions that I don't think are fully (and honestly) answerable, even if sincere.
 
I assert that one has to know HOW something is "supposed to work" (ie, "working as intended/designed") before one can call something a bug.
 
Whether one agrees with the implementation of a feature or not, is also questionable as to whether the developers would consider it a bug.
 
I'm in the camp along with others who feel a lot of the 'issues' raised around here lately might fall into the category of "unfamiliar" moreso than "real bug."
 
That is not to say there aren't REAL bugs (and a bunch of them lol).  CW has admitted openly to some;  users have identified quite a few with corroberation from other users, and CW is expected to release a few patches along the way at any rate.
 
Software has bugs.  So do humans
 
Okay - I'm outtie, as they say ;)  Have fun in this thread. 
  
Oh and I reserve the right to duck back in :O
 
 

Ok - I've filed probably close to a dozen problem reports.  Way way more than I ever did before.  There was one - I'll have do admit - that wasn't necessarily a Cakewalk issue.  I discovered the solution shortly after I submitted the report and wished I could go in and edit or withdraw the report because I didn't want Cake to waste time on it.  But I don't know if we can do that?

What I thought was a bug was the absence of "New Drum Map" on the output dropdown of a midi track.  During installation I skipped the part about installing the factory drum maps.  I only use a couple and don't need 100 of them on a drop down.  Apparently X1 creates its own Folder for Drum maps (different from 8.5 or other previous versions), so I had to copy my maps into that folder.  Once the folder was populated the "New Drum Map" item comes up on the drop down.  I would still prefer to see this item regardless if the folder is empty or not.  It would have saved me from filing the report and wasting Cake's time.

ba_midi

Dale Aston


I have found that the majority of what I first thought were bugs/problems have turned out to be me not knowing how the program works.  I've been around Cakewalk since the beginning and this version is almost a complete paradigm shift.

True, there ARE flaws in the code however most of my problem reports have not panned out to be real bugs. 

I can chalk up mine to around 75% = user ignorance.  What about you?

I'm not going to stay in this thread for various reasons, but I think one would first have to ask if a user knows the difference between a bug and a user error.
 
For those who don't bother to read the manual and are coming from previous versions of Sonar, a LOT could "look" like a bug.   Just look at all the intial posts about "where did my keybindings go!?!" ....  this to me is all about not taking the time to "learn" about the changes in THIS version.     I bet CW got a bunch of bug reports on that one alone.
 
So to ask others to be honest about what they consider a bug makes some assumptions that I don't think are fully (and honestly) answerable, even if sincere.
 
I assert that one has to know HOW something is "supposed to work" (ie, "working as intended/designed") before one can call something a bug.
 
Whether one agrees with the implementation of a feature or not, is also questionable as to whether the developers would consider it a bug.
 
I'm in the camp along with others who feel a lot of the 'issues' raised around here lately might fall into the category of "unfamiliar" moreso than "real bug."
 
That is not to say there aren't REAL bugs (and a bunch of them lol).  CW has admitted openly to some;  users have identified quite a few with corroberation from other users, and CW is expected to release a few patches along the way at any rate.
 
Software has bugs.  So do humans
 
Okay - I'm outtie, as they say ;)  Have fun in this thread. 
  
Oh and I reserve the right to duck back in :O
 
 

Excellent post..

Shoot the messenger again - I've been on the phone and email with CW over real bugs that I worked studiously to resolve down to 2 - count em - 2 - complete clean installs of Windows and X! on a powerful computer with all the latest drivers. They last advised me to experiment. X1 has tons of problems and it will be a blessing when they get the code hardened enough for users.

I can chalk up mine to around 75% = user ignorance. What about you?

Does this make for only 25% real bugs?

That would be a relief...

I don't know about you, but I consider getting a BSOD (blue screen of death) as a bug somewhere... Error messages and GUI glitches I can accept, but not BSOD.

And since the only thing that changed was going from 8.5.x to X1...

sdpate


Shoot the messenger again - I've been on the phone and email with CW over real bugs that I worked studiously to resolve down to 2 - count em - 2 - complete clean installs of Windows and X! on a powerful computer with all the latest drivers. They last advised me to experiment. X1 has tons of problems and it will be a blessing when they get the code hardened enough for users.

 
Its amazing how there are VAST differences between those who have X1 working and those that don't.  Since there are so many systems that are working and so many that arent, I have a difficult time believing that its a problem with X1 itself. I mean how can 1000 people NOT have metronome problems nor all of the bugs listed.

Are you running X1 as an administrator? Right click X1a /select properties / Compatability tab - select run as administrator.   When I'm not running 8.5.3 or X1a without being an administrator, I have issues but they aren't BUGS.  
 
I also noticed for some reason that when I don't run either as administrator,  8.5.3 shows up with a lower process ID number than X1a within my OS.  In other words 8.5.3 takes priority over many more programs than X1a does on my laptop.  However when I run them as administrator, both programs now show up with a process ID number in the 100's  or lower (the lower the number the higher the priority).  I'm not sure if this means that X1 is not as much of a bully to the OS as 8.5.3 or what.  I always run ALL of my Audio programs (Cakewalk / Motu ASIO Driver, etc....)as "an administrator" to make sure my OS is paying more attention to those programs than lets say "print spooler or apple quicktime, etc".  
 
Speaking of Quicktime - I actually had to turn Apple Quick time OFF and keep it from running in the background because I couldn't export MP3 files for some reason out of either 8.5.3 or X1a along with my MOTU ASIO software running. I also had to completely uninstall itunes.  Itunes automatically took over my audio interfaces as it ran in the background.  For instance, I always start my MOTU ASIO software before starting Sonar.  Itunes automatically showed my MOTU as an optional output and then I started SONAR and it said "No ASIO drivers found".  I'm not sure if ITUNES hijacked my ASIO driver or what, but when I uninstalled ITUNES........Sonar has been happy ever since.  Itunes ALWAYS had a much lower prioirty number (which is actually higher priority in essence) than most anything else - even without running as an administrator. I suppose Apple products like Quicktime and Itunes just have 1st/top priority built into their coding somehow.
I'm thinking that X1a should by default be more of a system priority bully like its older brother 8.5.3, but thats just me.  
 
 
This might not do the trick for you,  but maybe it will help someone.
 
I'm running Vista x64 with / 2 Raid0 64GB SSD's / 16GB ram / nVidia Quadro FX 3700M in a Dell M6400 laptop.  It runs both 8.5.3 and X1a just fine.  

Dale Aston


I have found that the majority of what I first thought were bugs/problems have turned out to be me not knowing how the program works.  I've been around Cakewalk since the beginning and this version is almost a complete paradigm shift.

True, there ARE flaws in the code however most of my problem reports have not panned out to be real bugs. 

I can chalk up mine to around 75% = user ignorance.  What about you?

I'd like to be honest about my Sonar X1 bugs, unfortunately I'm not enough of a computer whiz to actually say it's Sonars fault, the OS's fault, the users fault, software conflict or a hardware incompatibility issue. Until I am, I guess I'll just **** like everyone else.

Making a Sonar version where we can't find anything and you have to use the manual all the time has to be a bug.

IE, going from user friendly, to unfriendly = bug.

Kroneborge


Making a Sonar version where we can't find anything and you have to use the manual all the time has to be a bug.

IE, going from user friendly, to unfriendly = bug.

Maybe they should not have marketed this as a Sonar version AT ALL, but a completely new DAW...with all the problems/crashes/glitches still attached.


Megh.


I still think that I'm going to attribute those with no issues as just having plain old DUMB LUCK...

Bristol_Jonesey

trimph1


When someone has EXACTLY the SAME platform and they have issues and you do not...attribute this to PURE LUCK....

there was a post last week by a member who's name escapes me, and his system was virtually identical to mine in terms of Ram, CPU, OS, Interface etc.
 
He was running X1a with absolutely zero problems.
 
I, on the other hand, have had to uninstall X1 due to it's total instability and crashing to the desktop, and subsequently have had to completely uninstall 8.5.3 & reinstall it again, due to X1 totally trashing it.
 
Go figure.

I think I read that one too...and I am kind of dumbstruck...all I can think of is just that...


I have it as well...I have CM and X1...no issues....YET....so I am starting to think that "chance" has a role in here....


...huh...


Maybe there is a 'placebo' effect going on and I am overlooking something....

lorneyb2

g_randybrown


perhaps someone could enlighten me as to if this is a bug 
Notes in the PRV don't snap to where I want them and I have to "fine tune" to put them exactly where they're supposed to go.  


Oh yeah, I forgot...I did run into a similar issue today: if I had snapping on and moved a note over to a beat (1/8 note I think) it would snap to just in front of the beat. This may just be a graphic thing because when played back it sounded dead on.

In the snap settings right click and select Move to  and not Move by.  That may be the problem you are running into.  Also under Preferences(P) - Customization -Snap and Nudge being set to off may also need to be done.

Well I pretty much assumed it was user error...thanks Lorney that was the "problem"