SLATE FGX > on i7 (2600k) more hungry than on old quad (

dcb

nerd
Dec 7, 2008
1,350
0
36
anyone else experienced something like this ? :

moving from your old system (32 bit, cubase 6 32 bit, quad e6600 or similar)
to an i7 system (64 bit, cubase 6 32 bit)

>> fgx now takes up 40-60% asio power.

i cant use fgx on my mixes anymore, while i could easily on my old (slower) system... im talking to slate atm. about this, hopefully well find an answer.
but : anyone else on i7/i5 systems with fgx eating up THAT much cpu?

is this common?
thanks guys!
 
which OS is it, i guess it's W7!?
if so, go to the "energieoptionen"
and set "höchstleistung"

the options "energiesparmodus" and "ausbalanciert" choke everything down.


cheers
S.
 
erergyoptions, ernergymanagement...must be something like that.
there are three options, balanced, energy saving and full performance.

cheers
S.
 
thanks guys, but i already did all that... :-(
its really only fgx...

anyone else with win7 64bit , i7 2600k and fgx?
 
Im on almost that system.. I7 win64 and cubase 5 32bit.
Not sure if it takes as much, but my meter does take a big hit everytime.

Is there a way in cubase to find out how much load a single plugin is taking on your system in % (have seen you can get a list of that in other daws.. but never found it in cubase)
 
Im on almost that system.. I7 win64 and cubase 5 32bit.
Not sure if it takes as much, but my meter does take a big hit everytime.

Is there a way in cubase to find out how much load a single plugin is taking on your system in % (have seen you can get a list of that in other daws.. but never found it in cubase)

can you try this for me?

open a new project > insert one stereo audiotrack > instert fgx

does your asio meter jump up to 40-60 % too?
thanks!
 
Think I´m a little bit late ;-).........but anyway.
Is it normal that only one FG-X takes so much cpu???
Solution?
 
I got similar problem with a particular video capture software. I set w7 for the best performances but I had problems.
I had to delete useless processes and programs to improve a little the performances.
What about the bios? Did you try to change cpu settings there? There should be some kind of Turbo mode
 
i still think its an win 7 64 bit problem, never had these problems on win xp...
though i never got any real help from slate, they just told me they forwarded that problem to fabrice i think.
never heard back from them (2 months ago). now i use ozone again most of the time and think about selling fgx....
 
I got similar problem with a particular video capture software. I set w7 for the best performances but I had problems.
I had to delete useless processes and programs to improve a little the performances.
What about the bios? Did you try to change cpu settings there? There should be some kind of Turbo mode

i did try a lot of settings. nothing really helped.
 
anyone else experienced something like this ? :

moving from your old system (32 bit, cubase 6 32 bit, quad e6600 or similar)
to an i7 system (64 bit, cubase 6 32 bit)

>> fgx now takes up 40-60% asio power.

i cant use fgx on my mixes anymore, while i could easily on my old (slower) system... im talking to slate atm. about this, hopefully well find an answer.
but : anyone else on i7/i5 systems with fgx eating up THAT much cpu?

is this common?
thanks guys!

Im running the same system...but on pt 9! It's jumping between 22-24%!
 
i just switched to an i7 system and i get some similar issues. i instantly get asio spikes as soon as i load up FG-X.
the asio meter is about 1/5 full so it actually should not come to any overloads.

danny, did you get any response from fabrice yet!?

cheers
S.
 
i just switched to an i7 system and i get some similar issues. i instantly get asio spikes as soon as i load up FG-X.
the asio meter is about 1/5 full so it actually should not come to any overloads.

danny, did you get any response from fabrice yet!?

cheers
S.

they got back to me a few days ago, im part of the beta team now.
but have no solution yet... still the same problem.

i will have to try 64 bit to see if there is problems with that..