No issues at all, everything worked from the start, although not recorded any big projects yet just low track count basic roughs for tracks I am working on. But then I had no issues with X1 that were not down to me.

So far happy.. I'm thinking more like X1 patch 'e' = X2.

Very pleased so far, though I've not given it a thorough thrashing yet, but using it daily working through the vids and its given me no problems.

Roy 

I be had one crash so far , I was doing something with a bus

Im definitely working faster now , I love the aim assist as I was 
Always turning it on. 

I'm using mostly  Sonars modules and staying away from
3rd party. 

All I really need is more time …

A few little issues for me, but the patch fixed them all. Not a single crash since. I gotta get used to lasso with right click instead of left...I'm dropping notes in midi tracks like mad. LOL! Auto-zoom is fantastic and pro channel capabilities as well as adding whatever you want in PC is such a great thing. We don't really need fx bins now. However....I just gotta mention this because it annoys me to no end.

Maybe we can all team up and do a feature request if you guys feel the same? I actually have a hard time understanding how the bakers allowed this to be as it is. But anyway, when you create your own FX chains, the % values it gives us as opposed to the REAL value a knob may be putting out in a plug, definitely needs to change. When I drop a threshold on a compressor, I'd like to know where I'm dropping it without seeing a number with a %.

I know we use our ears, but I would like the effects chain values I create to correspond with the actual effects values in the plug. This is huge for me and stops me from using effects chains as often as I'd like to. I can give/show so many examples where the current system fails.

For example, create a new fx chain. Put a Sonitus eq in the chain and hook it up so one of the knobs controls the frequency value. See if you can even make the knob go slow enough to control it and know what frequency you're looking at without the plug being visible. That doesn't help me looking at a % and no frequency value. It's useless to me.

Now do it with a Q setting. If the plug isn't visible, you have no clue what you're listening to or what you're numerically looking at. I just think this is a really bad system visually speaking that needs to be fixed so it shows correct plug values at all times. Try it and see what I mean. You get so lost at what you're looking at, you're better off double clicking the plug and adjusting it like you normally would.

Other than that, X2 is amazing in my opinion and is purring like a kitten. Way to go Cake!

-Danny

Bristol_Jonesey

Heroics


Midi timing could be much better ,also the thang crashes 2 much .....and I do have the Pro audio PC -----fresh setup

But we are used to this at start of a new sonar , no biggy


but thanx anyways

What's wrong with Midi timing?

I was going to ask that same question, Jonesey. If there is a midi timing issue, it's usually a matter of experimenting with a few options in Sonar. Especially with X2 as this has been improved. The only time I've had issues with midi timing, they were things I needed to adjust on my end.
 
1. In Sonar x64, I get a little midi drift if I use an ASIO buffer size that is too high. I have to be at 256 or lower and the midi is perfect. This is only when using softsynths though. My midi hardware is spot on no matter what. In Sonar 32 bit, it doesn't matter where my ASIO buffer is. I can leave it at 2048 buffers and midi never drifts.
 
2. The midi playback buffers need to be adjusted. On some of my pc's, 500 works. On others, 800-1000 works better. My midi is spot on with my audio metronome at all times. Sonar X2 has been the most reliable so far for me midi wise.
 
-Danny

Loving it.... a tad less stable than X1 (audio loop browsing) but it just carries on with the workflow enhancements that X1 started. I should add that X1 was stable as a rock for me so it couldn't get more stable....

Noel Borthwick [Cakewalk
]

But anyway, when you create your own FX chains, the % values it gives us as opposed to the REAL value a knob may be putting out in a plug, definitely needs to change. When I drop a threshold on a compressor, I'd like to know where I'm dropping it without seeing a number with a %.

Here is the thing. Fxchains were designed to allow a single chain parameter to control many effect params within the chain (parameter grouping). As such we can't use the target parameter name in general since there may be many of them.
That said perhaps we could special case the one to one parameter case and display the single target param name. I'd have to check how feasible this is to actually do.

I'm totally with you, Noel. But I'm sure you can see my point too. Depending how one would use this....dictates how helpful or hurtful it can be.
 
Just in case you may be wondering my use....there are times where once I get all my effects settings in order, it may come down to just tweaking one thing in each effect. Say a Q on a high pass on a bass guitar, a frequency adjustment or a threshold on a compressor or maybe the values of one knob on another plug. In THAT situation, it's really hard to use this without physically looking at the plug to see the effects of the knob. Not to mention, it's near impossible to select a frequency that is mapped to a knob. That one is a nightmare. So I guess for how you intended this to work, it's as it should be. But for guys like me that may be using it a bit differently, the only benefit I get is the ability to create the chain of effects I'm using...which of course is a wonderful thing. But the custom abilities within the knobs (buttons for on/off are fine of course) are more of a hinderance than a help.
 
Yeah if you can look into this and see what can be done, I'd be extremely greatful as I feel this is an awesome capability. It just hurts when you can't put that % or how the knobs react, into the real scheme of things without plug visibility. At that point, it's better to just double click and edit normally, ya know? Who knows...maybe I'm the only one that uses it this way because I've never read anything where anyone else has complained or made a mention of it. I thank you for at least taking a look at it for those of us who may be in the situation I'm in with it. :)
 
-Danny

I think X2 has some niggles, but no actual big issues. On the whole it's very impressive. I was skeptical about the smart tool changes at first, but I now think they're very good. And automation copy / past finally being fixed is great. My one big issue, which I've griped about elsewhere, is that v700 support is really broken (again).

No issues so far, many hours of use.

 I put X2 through a few test mixes on my system. A few of the things I really like are: The new ways to size tracks and the clips header feature,track lanes are awesome especially that they can be different kinds of lanes, The refinements to the PC are awesome especially the ability to add other plugs into it. The pre built effects chains are pretty much set for the application with only minor adjustments needed. Breverb is a great addition.

 I tried some of the new audio snap features and it seems much easier to work with now.Synth replacement is a great addition although I find myself experimenting a little too much.

  Since X1 I have been relying more and more on Sonar and its plug-ins/PC instead of aftermarket. I had a decent aftermarket compressor on my master the other day and one in Sonar sounded better than it did. In some cases I look at aftermarket purchases as a waste in light of what can be done in Sonar now.

 I have only one small niggle so far. I wish that the modules in the transport cluster could be undocked from one another. I use dual monitors and when I have the transport up some of it is missing in the space between the monitors.

My consensus is its awesome! X2 's workflow is vastly improved , editing , arranging , time line enhancements , smart grid ,Prv view, the addition of rmix, and the console emulators are just to name a few things I love. Also the search feature in the browser is great. Right clicking on a sample in the browser now gives you options. Also I love the auto zoom feature. Just wish lanes exploded as large as tracks do. All in all there's so many neat usable features I'm still finding.:)
 As far as stability , I had a few crashes but , we figured it out , it was the concrete limiter , so I just don't use that, I also had crashes were clicking back and fourth between tracks and buses , I am also experiencing that some key binding don't work . Such as snap on and off, snap to measure,and a bunch others.
 Other than that x2 is very stable, and freaking fun to use!

Piangio - that's GREAT news on you getting past your earlier set of issues!!!

GREAT STUFF there.

Bob Bone

rscain


I had a lot of problems when I first installed X2, crashes every 15-20 minutes.
Then, last week I got a new interface (Focusrite Saffire Pro) and since then I've had no crashes at all.
I really had no idea how bad the drivers where on my old interface but that seems to have been my major problem.
I'm happy as a pig in slop now!

Now that reminds me:


http://forum.cakewalk.com/tm.aspx?m=2688836

Noel Borthwick [Cakewalk
]

But anyway, when you create your own FX chains, the % values it gives us as opposed to the REAL value a knob may be putting out in a plug, definitely needs to change. When I drop a threshold on a compressor, I'd like to know where I'm dropping it without seeing a number with a %.

Here is the thing. Fxchains were designed to allow a single chain parameter to control many effect params within the chain (parameter grouping). As such we can't use the target parameter name in general since there may be many of them.
That said perhaps we could special case the one to one parameter case and display the single target param name. I'd have to check how feasible this is to actually do.

expect one or more, use the first one, and if there's more than one then prefix the label wth an asterix or something?