brconflict

Muziekschuur at home


What is NOT working in X2A? X2A was an amazing update and a great gift to us Cakewalk Sonar customers. As we we are now able to use touch screens. Where that functionality was not there in X2 and not really asked for. We got an awesome bonus and means X2 is quite future proof... So I am not quite grasping where the X2B is needed for?

I think you may just be one of the fortunate ones that hasn't run into any problems, or probably utilize the power of X2 in other areas more than users like me. If you peruse the forum, you can quickly find people having issues that go unexplained, and the worst thing about many of these issues is that a majority of them aren't always reproduce-able. This means that the bug-submission form Cakewalk requires doesn't really encompass bugs that people find and can't recall the steps, or can't get it to happen again while trying to reproduce such issues.

Like I said, Sonar is VERY powerful in all it can do, and looking at the competition, it still wins me over, even though there's features in others I'd pay money for if they could be brought into Sonar. But all that power quickly is foreshadowed when you run into bugs or issues that Support can't work out or that you can't reliably reproduce.

X2 feels like a solid DAW, but with some new code that drops the ball fast when it breaks. I fear this is exactly what X2b will be like: more features, and less bug fixes. I also fear Take Lanes won't get much love from the bakers, either. But I don't know. They don't indicate anything either way until the next update comes out and I read the "fixed" portion of the Readme. I'm nearly always disappointed by what wasn't addressed. 

you have a very fair enough complaint.
and I agree with you on somethings.
what are the actual bugs that you think, drop the ball?
im not asking for all of them, but in your opinion, the three, that really interrupt your work flow ?
being totally serious here,
 
ive been another one of the very lucky ones to be having great success with it.
id like to think I use a lot of its features as well.
 
honestly do feel for you though.
 
and in no way is this me trying to justify my work flow is great and your is not.
that could be me in your shoes. I think you've explained it fair enough

pbognar

fooman


X2a was a pretty darn good update, not cause of touch-screen in my opinion, but for the bug fixes.
X2 is fairly quick compared to X1 after the update to X2a.  X2 had a lot of little bugs that forced me back to X1.  X2a allows me to mix without many bugs.  And all of the bugs I do see are all pretty much one of two plugins that aren't playing nice with X2 (Voxengo or Steven Slate VCC).

I still don't track in X2 due to take lanes.  I also refuse to edit anything in it if it requires intense editing because I can't get the hang of take lanes.  There are one or two main issues that stop me from using them altogether.  So I basically stick with X2 for pure mixing because it feels smoother.

Fix take lanes (or take a look at a much-requested 'rebuild' ability) and I'll be a happy camper for sure.
I don't need new features.  I don't think anyone here really does as seen by a lot of the threads.

If you don't track in X2 due to take lanes, then "Houston, we have a problem".


I would seek out the help of the experts on the forum.  Perhaps there is a configuration issue, or just something which you could approach from a different angle.


The first thing I would expect to be able to do in a DAW application is track.

I totally agree.  X1 crashes with these same exact plugins, but more often.  No idea why.  I send in crash report(s) every time.  This is why I have started to at least mix in X2a.



To be honest, I'm just too busy to come on here and figure out why the crashes are happening.  It takes more time to sift through topics, ask, reply, experiment, etc.  I could re-open Sonar and work in that time.   I will end up getting the same replies "open session in safe mode, disable the plugs, see if crashes happen" and "did you send in crash reports?", so to get help with a seemingly random crash is too time consuming to be worth it.

Regarding Take Lanes, I have started at least one topic on it.  All of those topics on take lanes tend to fizzle out once everyone realizes nobody really can answer the issue at hand (whatever that may be in that particular take lane thread).


Take lanes is honestly the best idea and two steps away from being great, however right now I can't even use it because it's impossible to fold the track and automate on it if you have muted clips.  This is the biggest issue I have with it.


I think only active, un-muted clips/lanes should be visible when folded.  If that happened, you could automate so much more easily and do edits a lot quicker with the folded parent track.

chuckebaby

brconflict

Muziekschuur at home


What is NOT working in X2A? X2A was an amazing update and a great gift to us Cakewalk Sonar customers. As we we are now able to use touch screens. Where that functionality was not there in X2 and not really asked for. We got an awesome bonus and means X2 is quite future proof... So I am not quite grasping where the X2B is needed for?

I think you may just be one of the fortunate ones that hasn't run into any problems, or probably utilize the power of X2 in other areas more than users like me. If you peruse the forum, you can quickly find people having issues that go unexplained, and the worst thing about many of these issues is that a majority of them aren't always reproduce-able. This means that the bug-submission form Cakewalk requires doesn't really encompass bugs that people find and can't recall the steps, or can't get it to happen again while trying to reproduce such issues.

Like I said, Sonar is VERY powerful in all it can do, and looking at the competition, it still wins me over, even though there's features in others I'd pay money for if they could be brought into Sonar. But all that power quickly is foreshadowed when you run into bugs or issues that Support can't work out or that you can't reliably reproduce.

X2 feels like a solid DAW, but with some new code that drops the ball fast when it breaks. I fear this is exactly what X2b will be like: more features, and less bug fixes. I also fear Take Lanes won't get much love from the bakers, either. But I don't know. They don't indicate anything either way until the next update comes out and I read the "fixed" portion of the Readme. I'm nearly always disappointed by what wasn't addressed. 

you have a very fair enough complaint.
and I agree with you on somethings.
what are the actual bugs that you think, drop the ball?
im not asking for all of them, but in your opinion, the three, that really interrupt your work flow ?
being totally serious here,
 
ive been another one of the very lucky ones to be having great success with it.
id like to think I use a lot of its features as well.
 
honestly do feel for you though.
 
and in no way is this me trying to justify my work flow is great and your is not.
that could be me in your shoes. I think you've explained it fair enough

Thanks! What seems to happen for me the most is, Clip Views aren't updating to the correct View when I change them from Automation vs. Clips. Sometimes Take Lane's will paste into the wrong Take Lane when editing (I figured a workaround, but it's really odd); importing data into a Take Lane imports only into the first lane, which is really a carryover issues from Layers, and collapsing Automation (and sometimes Take) Lanes will occasionally collapse all tracks and folders. One cosmetic bug is that once you expand Take Lanes, the button turns blue-ish, but doesn't correctly indicate whether there are more than one Lane or not, typically. I've had a couple of Take Lanes audio disappear altogether. Even re-drawing the picture doesn't bring them back )they're completely gone).
Lastly, I've had an issue where a Take Lane will "un-Mute itself after it was collapsed. I've only seen this twice, though. 
My biggest workflow gripe is that the overall track takes up so much real-estate when Take Lanes are expanded. There's some wasted space in the track. 

To be fair, I have good days, too. Not many, but they do happen. When things are working without issues, the only problem I have is getting visually lost in the tracks and Take Lanes and that slows me down big time. This was way worse with the X2 color scheme before switching back to the X1 color scheme. I would get seriously lost, until I figured out that minimizing the Track doesn't collapse the Take Lanes. 

Anyway, thanks for asking. 

fooman

I think only active, un-muted clips/lanes should be visible when folded.  If that happened, you could automate so much more easily and do edits a lot quicker with the folded parent track. 

+1; +2 actually, because this could easily be fixed if we did this with the Take Lane Solo button. Or EVEN BETTER, change "Solo" to "Select" or "Choice" and give it a different color as giving the Mutes a different color. This would help navigation confusion a lot! 

Jimbo 88


Yea I heard 2xb was on its way and 2 major improvements...

1) staff view
2) Video

both get major overhauls.

Wait...what day is it??

where you get that from? heard it through the grapevine?
more vine than grapes over here ... maybe that's why I don't get to hear much ;-)
 
 

FreeFlyBertl

Jimbo 88


Yea I heard 2xb was on its way and 2 major improvements...

1) staff view
2) Video

both get major overhauls.

Wait...what day is it??

where you get that from? heard it through the grapevine?
more vine than grapes over here ... maybe that's why I don't get to hear much ;-)
  

hahaha - late to that april fool's gotcha.  


my bet is in the next 3 weeks because i just had a good handful of problem reports submitted to development today - so, my guess is they're done with b and testing it for the next week or 2.    

I must say there are four things (could be more but can't remember now) that interrupt my work flow:

1. Can't clone MIDI tracks (confirmed bug in Essential)
2. Grouping the Solo buttons of simple instrument tracks doesn't work properly (current ticket status: "Submitted To Development")
3. Inline PRV fails to display gridlines for triplets (current ticket status: "Under Investigation")
4. Dragging a MIDI clip to another MIDI track sometimes fails to move the clip to the position it's supposed to land on (done nothing to this issue yet) 

There are other issues but they aren't really workflow-interrupting (except for one or two known take lane issues).

When copying tracks, removing them from folder, creating new folder, storing them in the new folder.... I get a "ghost" dark line in the track view that stays in the same position on screen regardless of my scrolling position in track view.  This happens every time I do this process.  It goes away when I close/open the session.

Is this a known tiny bug?

but it lost it's connection too often,and something to do with "it"

I found out that the K.A.6 is very power hungry, 
it will hang, even BSOD your computer if lacking USB power. 


try on a desktop rather than a laptop (if possible)
avoid sharing the USB ports with other devices
avoid plugging it to a USB3 port (with the blue plastic inside)
use a nice powered USB hub for the KA6, this should help, 

My grips with teh K.A.6 is the SPDIF that is broken, it does not work as it should. 
it's written in the manual that you must have a "compatible SPDIF device" ... never heard of such crap ... 
only you get to read that once you opened the KA6 box, and can't return it to the store. 

I hope that helps ! 

Cheers ! 

V

PT 11 is announced today. There are huge improvements. 64 bit performance, new audio engine and playing/editing HD video formats..

So Sonar needs a HUGE update to keep eyes on it. I think just fixing bugs is not enough for that right now. We also need new and unique features.