Poll: How many.....

How many bugs annoy/stop you in X2a?
 
How many bug reports have you submitted for those?
 
 
FYI Cakewalk: This is not meant as a snarky nor baiting thread. This is a serious question as outlined later (post #29) in this thread by me (in response to Beepster).

Score so far
 
Bugs: 1
Reports: 0
 

im with brando.
 
biggest gripe is also take lanes.
no show stoppers here or bugs, more annoying little things like the aim asst bar reads incorrect values,
though some would say this is a bug, I don't usually look at the values anyway, I look at the timline or clip im snapping to.
 
bugs: 0
reported: 0

No show stopping bugs for me. A minor annoyance with the now time disappearing occasionally which I thought was me accidentally hitting a short cut key but its been reported by others.
 
I have had one crash since using X2 I sent a crash dump.
 
One bug
Zero Reports
One Crash
One Crash dump sent.

I can always count on Sonar and it's bug count. What will be the count I do not know but I can always count on a bug or two, or three, count them and see. The Count is always counting ant that's something you can count on.
 
I like the magical pointer bug. Sometimes when you select in collapsed folders the highlight doesn't go away until you move the magical pointer over them.

benjaminfrog
No showstoppers. 5 bugs. 4 reports. Tons of crashes. Tons of crash report submissions.

if you'd like, you can list your bugs so others can try them so we can possibly cross reference them.
it might be nice also for you to know as well.
what might be a bug on your machine ,it might not on someone elses.
and that might yield some results that cake might find interesting because I know ive had an issue before and posted it but it was hard for others to repro it.
 
this was helpful to me because I knew either A- I was missing something, or B- this bug has a make up of my systems configuration= RAM, processor, soundcard, exc.
 
I was able to post "with anyone using a focusrite usb safire 6 and an i7 can you try this"
and low and behold that was it.

My most recent "bug" was the "Sample xxx.xxx not found." window was hiding behind the main Sonar window.
 
I did not know it was there so I kept closing Sonar which kept generating a bug report that wanted to be sent to Cakewalk.
 
I thought the "bug" was Sonar not opening properly.
 
The "bug" was actually the main window hiding the warning window.
 
All warning windows should open over the main window so they can be seen.
 
I did not send a bug report but the auto bug reporter sent one when I forced Sonar to close.
 
(Sometimes the biggest "bug" is the one with the "mouse" in his hand!)

No bugs here,
uuuupppssss, you´re not asking for bedbugs,or?
 

Not sure if I filled out any reports in X2. Maybe a few when I could. My crashes were from Kontakt and teleport server in x64. The Kontakt issues magically stopped as of 2 months ago but x64 is still not quite right. I'm not sure these are bugs...but these are my issues.
 
1. Template run in X2 (x86) at 32 or 64 buffers via ASIO will have latency in Sonar X2 x64. The same exact template....and it has latency. Gotta be bitbridge.
 
2. Take lanes drive me nuts. Same issues everyone else has with them.
 
3. V-Vocal ghosted clips after bounce to clip. Sometimes they auto-mute the original and the VV clip is on top, other times the auto-mute is on top of the VV clip yet it still plays the VV clip. Add this sort of thing to take lanes where you use the K key to mute clips if necessary and you are in for a nightmare with ghost clips playing even when muted.
 
4. Sometimes Console emulator speeds up to double speed when inserted and put into post mode.
 
5. Paste doesn't always paste clips where I want them. They either say they pasted and I can't find them, or they end up 8 minutes deep into the track on the wrong track.
 
6. The snap to grid is horrible for me unless I just don't know how to use it. Sometimes it won't even snap for me even when it's on. I have to mess with it in order for it to kick in correctly.
 
7. Right click and drag to lasso drives me nuts. Not a bug, just a nuisance because I prefer left click and drag. This really sucks when doing midi. I drop notes all over like a bird dropping on a black car thinking it's water. 
 
8. Plugin manager is weird. Sometimes it shows my custom plugs for the fx bin but won't show the right plugs in the side bar menu.
 
9. I really hate HATE HATE our audio engine compared to our DAW competition. In a big project with low buffers (32 or 64 buffers) it dies on me every time I stop playback during a recording. 3 competitors DAWS do not do this at the same buffer settings.
 
10. I'm astonished we don't have colors back for X2. I made up my mind if they didn't come back for X2, there would not be another X for me. Sorry, that's a major peeve of mine.
 
11. Midi notes literally move by themselves at times. It's the weirdest thing. I can't make it happen, it just does it whenever it wants. So here I am with a client tonight....I ran Sonar on the same project from 6:30 pm until 3 am. Not a single crash or problem. But we recorded drums using V-Drums tonight. As we were editing and quantizing the midi notes, we literally saw the entire grid of notes drift by themselves. I wasn't even touching my mouse. I'm not talking a major move...I'm talking an increment...but enough to where the client saw it too. I've seen this several times and have noticed that after I quantize a project perfectly and save/close it, the next day I come back, I'll need to quantize a few more notes. I didn't miss them....I'm a machine, trust me. They moved on their own like they have been doing for me. Now I know what causes that.
 
No show stoppers for me, but some things that are annoying enough for me to see what else is out there. Crashes are just about 0 so that's a good thing, but the same can be said for the other DAW software I use. To this day I've not crashed 2 of them while 1 has only crashed one time. I notice I have to be very careful with Sonar. Like...make sure I stop playback...don't drop in synths while audio is playing...don't do this, don't do that. I'm walking on eggshells and have always felt this way since I began using Cakewalk and had to learn how to configure my machine correctly for it.
 
I don't feel that with other DAWs at all. I beat them, they work and don't crash for how *I* use them. If I beat on Sonar like that, rest assured it will have a hissy fit. As long as I respect it and treat it with kid gloves, it will work for weeks or months without a crash. It's a great DAW...it just needs a little work and I'd totally happy. Right now I'm content. But I honestly don't believe another X is in the works for me at this point. We'll see.
 
-Danny

Sometimes Concrete Limiter and PC2A disappear and the project has to be re-loaded. Appears to be random. Can't repeat. Bug report submitted but as I can't re-produce it, Cake said they can't do a lot about it (fair enough).
 
To give a little confidence to people, I submitted this report maybe a few months ago and they sent me an email 2 weeks ago asking if I had noticed any further information that could assist them in troubleshooting the issue (I have not yet). So as of two weeks ago, they were certainly looking at bug reports and working to fix them. If that's for X2b or X3, who knows, but it certainly tells us that they are working on SOMETHING.
 
I work primarily on X1 for current projects (X2 for all new projects) still but will be moving to X2 exclusively in about 2 weeks. I haven't really used X2 enough or mixed seriously on it yet. I'm really hoping it plays nice, but I'm a little scared. Hopefully if I just try to stick with Cake plugs only I'll be safe. Though I do need my Pultec and my RVerb...
 
Bugs: 1
Reports: 1

I know this was meant to be snarky but the bulk of the broken things I've found don't really get in my way. The three things that do are, in order of nuisance...
 
The random selection bug.
 
Audiosnap being quirky as all heck.
 
The general wackiness of the graphics in regards to things disappearing, appearing highlighted when they're not, flashing, waves sometimes becoming invisible when moving clips, etc...
 
These have been well documented on the forum so I'm sure they've got a pile of reports on them already so I haven't bothered. I was just assuming that a patch would be coming and those things might get better. They got slightly better after installed the A patch and are somewhat intermittent so it seems to me it's just the core stability of the program. Not really anything specific that can be done.
 
Cakewalk is likely to get a phone call at some point because I want to wipe my system and start from scratch following their directions. Unfortunately I am probably going to be freaking moving yet again (ugh) so I'm holding of until I'm in my new place. There might be a patch by then anyway... I hope. Otherwise Reaper is getting installed and I'll probably do all my editing there. Mixing seems to be okay in X2a so far but I haven't really done anything in depth since I patched.

Submitted several for x1, none of which were fixed so didn't bother getting x2 and now primarily use s1 as my daw.

I am always amazed at folks who gripe about a version they don't even own.

Sometimes I crash when closing all projects. Sometimes, when importing a pro channel preset I have to import it twice. Those are the kind of bugs that are clearly sonar. The biggest bug sits between the chair and the keyboard.

Nothing is causing me to rethink my primary daw at this time.

Beepster
I know this was meant to be snarky 

Beeps. That is so untrue. And it's an unfair assertion.
 
This thread as a serious spawn of the other thread where Ryan/Andrew (can't remember which one) said many complain about problems but don't always submit a bug report.
 
So far many (not all, but many) have seem to have proven that assertion. I asked if as a X2a user there are bugs/annoyances and were bug reports submitted.