X2a Core balancing

Page: < 12 Showing page 2 of 2
Author
Swiller
Max Output Level: -88 dBFS
  • Total Posts : 110
  • Joined: 2012/04/25 16:19:21
  • Location: West Wales UK
  • Status: offline
Re:X2a Core balancing 2012/12/30 07:46:30 (permalink)
Also worth ensuring that you have no cores parked. Check by using task manager, performance tab, resource monitor, cpu tab. to the right there should be a vertical bar which shows all of your processors. If any are marked parked, then...

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

:)





I7 3700k 3.5-3.9ghz, 16gb 1600 ddr3, 240gb ssd sata3, 2tb sata 3 hd,  2gb gt640 nvidia graphics, win 7 he, sonar x2 prod, a500pro, jd800,the magnificent juno 106, virus c, basstation rack, mpx1, xv5050, maschine mikro 1.8 with massive, kontakt,reaktor, mc505 groovebox, tlaudio 5021, 01x, Scarlett 8i6, prs ce24, squire classic vibe 60s.... tele,strat,jazz bass, blues jr 3 navy vintage 30 edition, orange ad5, line 6 ld15 bass amp, akg condenser mic, krk rokit 5, ns10s. Lots of thatchers gold.
#31
cclarry
Max Output Level: 0 dBFS
  • Total Posts : 20964
  • Joined: 2012/02/07 09:42:07
  • Status: offline
Re:X2a Core balancing 2012/12/30 08:53:46 (permalink)
Here's my experience...

Core usage appeared to be more balanced initially with X2...and this was also "touted" by 
Seth and Brandon during the initial "preview"

My initial experience was good....


After opening some of my older X1 projects in X2 there were some issues...primarily with the 
insertion of a Waves plugin into an X1 project opened under X2, which cause the system to 
crash.  This was resolved by saving the X1 project under a new name in X2 and re-opening 
the project, which resolved the "Crash" issue and allowed the Waves Plugins to function properly.
Not a big deal...but it really shouldn't be like that...

Core usage under X2 seemed to be "ok".

Core usage is WORSE for me now with X2a.  If I open a simple project with only 3 tracks and just
a few plugins, Core 1 goes red.  THAT is a marked degradation of performance, even worse then X1.

Couple this with other issues associated with X2a, and I'm off looking for alternatives.  While I dearly love Sonar, they seem to prefer "fluff" over substance when it comes to "enhancements"
And that just won't work for me.  

I'm test driving other programs at the moment and who knows where I'll end up...

But if simple projects cause "redline" in X2a that did not cause it in X1 with far larger projects, then I really need to look elsewhere...

this is purely "for me"...the experience for others may be "great"

I'm sure the vast majority of you in the fanbase will disagree and site "this" "that" and "the other" as the problem...and that is your prerogative...but there are obviously "problems" with X2 that I simply don't have time for...and "toughing it out" till the next update has ceased to be an option...

I will continue to use X2...just not as my main DAW as I have been...the benefits of other programs are coming clearly into view...nothing is perfect..but there IS better..

If Sonar makes a stride back in the "right direction" it may become my main again...just not now...

I don't know if their issues are related to "Touch" support, but, if they are, I really have NO USE for "Touch" at the moment, or, for that matter, in the near future...so "Touch", to me, is a 'detriment" if it renders the program unusable for me...


#32
Page: < 12 Showing page 2 of 2
Jump to:
© 2025 APG vNext Commercial Version 5.1