10.0.9alvfaria wrote:Some questions folks.
What FL version you are using?
Your CPU are intel or AMD?
Windows XP, Vista or 7?
Intel
Win 7 64-bit thru OSX Mountain Lion bootcamp
FL Studio CPU at 99% but Task Manager is at 30%
-
- KVRist
- Topic Starter
- 103 posts since 25 Jul, 2011
Intel
Win 7 64-bit thru OSX Mountain Lion bootcamp
-
- KVRist
- Topic Starter
- 103 posts since 25 Jul, 2011
Supported by....certain soundcards, or..? I've heard of quite a few producers using Bootcamp for FL.hibidy wrote:Uh oh, bootcamp rings a "ding ding ding" button. It's rarely supported as well.
-
- KVRAF
- 6159 posts since 4 Dec, 2004
Bootcamp is (afaik) just a boot manager. Once you boot into Windows, it's Windows. Running FLStudio, Vegas, Camtasia, all kinds of Win stuff on my MacBook. Actually runs better there than on my Dell laptop.
Even have a VSL 22 and driver instaled on it, whose drivers operate (for the dsp) at the kernel level or something. Works fine.
Even have a VSL 22 and driver instaled on it, whose drivers operate (for the dsp) at the kernel level or something. Works fine.
-
- KVRAF
- 42529 posts since 21 Dec, 2005
No, by support iirc bootcamp isn't supported by FL. Could be wrong. Certainly not suggesting that bootcamp can't run things. Anyways, I'm just confusing people so I'll bow out.alexfsu wrote:Supported by....certain soundcards, or..? I've heard of quite a few producers using Bootcamp for FL.hibidy wrote:Uh oh, bootcamp rings a "ding ding ding" button. It's rarely supported as well.
-
- KVRAF
- 6159 posts since 4 Dec, 2004
Hey Hibidy, I wasn't disagreeing with your comment re: support. I was only saying that booting into Windows there is no different than running Windows on a Win machine, on an Intel mac.hibidy wrote: No, by support iirc bootcamp isn't supported by FL. Could be wrong. Certainly not suggesting that bootcamp can't run things. Anyways, I'm just confusing people so I'll bow out.
I rarely even boot my MacBook into OSX anymore, mostly because some of the Mac software I own (like Studio One) won't even launch on the version of OSX it has and I have no desire to upgrade OSX on it.
Thanks H.
-
- KVRAF
- 1796 posts since 4 Sep, 2011 from England
I know in Ableton Live if one CPU core is at 90% and the other three are at 20% then the CPU meter in Live is shown as 90%. Live tries to run each track on it's own core or virtual core. Maybe FL is the same.
-
- KVRist
- Topic Starter
- 103 posts since 25 Jul, 2011
Bought a Focusrite 2i2 soundcard.
Reinstalled FL Studio.
Ran DPC latency checker, at about 500u - 1000u.
Ran Apple Hardware Check, came back fine.
Still same problem.
If I press one key from an init Massive patch, I get about 25% CPU. Nexus goes up to 99% if I press a triad in quarter note lengths. I have tried everything. Please help if you can. Thank you.
Reinstalled FL Studio.
Ran DPC latency checker, at about 500u - 1000u.
Ran Apple Hardware Check, came back fine.
Still same problem.
If I press one key from an init Massive patch, I get about 25% CPU. Nexus goes up to 99% if I press a triad in quarter note lengths. I have tried everything. Please help if you can. Thank you.
-
- KVRAF
- 2750 posts since 2 Feb, 2005 from Raincoast of Grayland
500u - 1000u seconds is bad news. Unplayably bad news. A good i7 Win7 DAW, should have DPC latency values under 100us and rarely over 150us.
Something is either:
a) wacked with you Win install on boot camp.
or
b) you have a bad mac (sick mac?)
or
c) horrible luck
To eliminate a variable, have you booted into OSX and installed the 2i2 and tested it with another DAW? If you still have horrible CPU usage and audio dropouts it would point to a hardware issue. If not, it would point to a bootcamp/Winuhs issue.
Have you tried turning off non-essential devices when in Winders to see if something is hogging the bus? Turn off WiFi, for example.
What is the buffer size you've set in FL? What happens if you use a really large buffer? What happens when you triple buffer? Have you tried using a fixed buffer size from the processing panel for each instrument? If so, what happens.
My guess is either a hosed driver or bad buss mojo (and not in a good way).
You gotta get the DPC latency under 500 at the very worst. 250 really. Sure seems like a driver/bus issue, which is no fun to hunt down.
Happy troubleshooting. Or at least bearable troubleshooting. And don't pull your hair out. You might need it later.
Something is either:
a) wacked with you Win install on boot camp.
or
b) you have a bad mac (sick mac?)
or
c) horrible luck
To eliminate a variable, have you booted into OSX and installed the 2i2 and tested it with another DAW? If you still have horrible CPU usage and audio dropouts it would point to a hardware issue. If not, it would point to a bootcamp/Winuhs issue.
Have you tried turning off non-essential devices when in Winders to see if something is hogging the bus? Turn off WiFi, for example.
What is the buffer size you've set in FL? What happens if you use a really large buffer? What happens when you triple buffer? Have you tried using a fixed buffer size from the processing panel for each instrument? If so, what happens.
My guess is either a hosed driver or bad buss mojo (and not in a good way).
You gotta get the DPC latency under 500 at the very worst. 250 really. Sure seems like a driver/bus issue, which is no fun to hunt down.
Happy troubleshooting. Or at least bearable troubleshooting. And don't pull your hair out. You might need it later.
perception: the stuff reality is made of.
-
- KVRAF
- 42529 posts since 21 Dec, 2005
Shot in the dark. Does the mac have a bios? (can't remember) I just wonder if maybe speed stepping or similar is doing something.
I also thing you should try reaper (because the demo is uncrippled) and see what happens, but I'm with mandolarian, that is way too high.
I also thing you should try reaper (because the demo is uncrippled) and see what happens, but I'm with mandolarian, that is way too high.
-
- KVRAF
- 42529 posts since 21 Dec, 2005
I just noticed this, "max" isn't any better than too low. I can't read the whole thread but you have tried several buffer sizes, right? Try 512 for stars and see if there is any change.alexfsu wrote: with the buffer size at max
-
- KVRist
- Topic Starter
- 103 posts since 25 Jul, 2011
Thanks for your replies.
Reaper gives me about 200u.
For the Focusrite USB 2.0 Audio Driver, I can only go up to 10ms in the buffer screen when I press "Show ASIO panel." Equals out to 442smp.
Reaper gives me about 200u.
For the Focusrite USB 2.0 Audio Driver, I can only go up to 10ms in the buffer screen when I press "Show ASIO panel." Equals out to 442smp.
-
- KVRAF
- 2750 posts since 2 Feb, 2005 from Raincoast of Grayland
So...the 200us DPC Latency in Reaper, was it in OSX or Windows?
perception: the stuff reality is made of.
-
- KVRist
- Topic Starter
- 103 posts since 25 Jul, 2011
Windows. Tried Ableton in OSX with the Focusrite and everything was fine as well.mandolarian wrote:So...the 200us DPC Latency in Reaper, was it in OSX or Windows?