|
My core2 really just isn't doing it anymore.. I need some recommendations plz (pg. 2)
|
View this Thread in Original format
| DigiNut |
Before you start throwing away money or following a bunch of go-nowhere tweaking tips, have you actually checked your CPU load? Is it pegged at 99% when you produce? If not, it's probably due to a combination of factors, including but not limited to FL Studio's terrible multi-threading support (although I hear it's improved with version 9).
Don't just assume that a performance problem is originating from a particular system component. Measure it. |
|
|
| DJ RANN |
VM not cutting eh? ;)
Do a full format, get the latest drivers for all your kit and this time stop downloading pr0n and h4x0r3d on your computer. Get a banged up little PC to do all that other and leave your audio PC for audio.
There's absolutely no reason why a core2 shoudln't be enough for you to produce with. |
|
|
| DJ Robby Rox |
| quote: | Originally posted by DigiNut
Before you start throwing away money or following a bunch of go-nowhere tweaking tips, have you actually checked your CPU load? Is it pegged at 99% when you produce? If not, it's probably due to a combination of factors, including but not limited to FL Studio's terrible multi-threading support (although I hear it's improved with version 9).
Don't just assume that a performance problem is originating from a particular system component. Measure it. |
No honestly its weird.
Say for instance this last project I have, with everything open and nothing playing, it hovers at exactly 24% cpu.
When I press play it instantly spikes to around 85%-90% then levels out a bit as the track progresses but its very unstable.
Theres not neccessarily synths being added and the CPU will spike, the track freezes, then it might drop back down to 60% then spike right back up. Its almost as if the WANTS to handle it, but can't. I remember on my pentium D is would be pegged at 99% just like you say, and it would stay there and that would be it, the track was done and you couldn't play it.
I'll get back with my specs too, everything I have running, soundcard and all that.
I do have the money so its not an issue (if I needed to throw out another hundred or 2), but I absolutely would rather NOT waste my money on something unless I really need it. I dream about having a computer that could actually handle the tasks I throw at it, and being able to use as many synths as I need while having a fairly stable project still. Hmm, maybe it is just FL Studios terrible support then? Honestly that WOULD make so much sense because I never understood why when the CPU goes crazy its always bouncing up and down rather then just sitting at 99% like you say. Still makes the track unworkable though.
Every question I ask in this forum winds up coming right back to FL, this is getting too funny at this point.
I can't imagine I have a lot of threads like this left before I burn the FL bridge for good. |
|
|
| DJ Robby Rox |
| quote: | Originally posted by DJ RANN
VM not cutting eh? ;)
Do a full format, get the latest drivers for all your kit and this time stop downloading pr0n and h4x0r3d on your computer. Get a banged up little PC to do all that other and leave your audio PC for audio.
There's absolutely no reason why a core2 shoudln't be enough for you to produce with. |
Because I know you and Diginut know more then I'll most likely ever know (I'm not kissing ass Im just stating facts) if you think I should just get rid of the vm tell me thats what you think.
I'll delete that right now honestly because I don't even use it. I got the vmware for obvious reasons, to test software. But I haven't installed 1 crack version of anything since I've had this setup, thus I don't really need the vmware. I wasn't so much an ethical decision as it was a logical one to be honest.
What I read from this post though was too trash my mobo amd everything else and keep my core2? Then save that to build a "banged up pc" with?
Now remember, I'm not that smart lol, but that sounds like going in the opposite direction. Get a new mobo, new soundcard, new everything, leave the processor, but for what? Speed is inherent to the processor no? If I got a new computer and keep the processor I'm just not seeing how thats going to make it any more powerful.
I don't know I think its more important you guys know everything I'm working with now, let me get that info. If anyone has recommendations please, I'd like to get all the parts asap. Don't want to jump into anything stupid though so I just ask for honest opinions please. Thanks everyone!
edit: I'll also take a pic of my taskbar window open and what it looks like with FL open so maybe you guys can get a better idea. brb. |
|
|
| DJ RANN |
| quote: | Originally posted by DJ Robby Rox
Because I know you and Diginut know more then I'll most likely ever know (I'm not kissing ass Im just stating facts) if you think I should just get rid of the vm tell me thats what you think.
I'll delete that right now honestly because I don't even use it. I got the vmware for obvious reasons, to test software. But I haven't installed 1 crack version of anything since I've had this setup, thus I don't really need the vmware. I wasn't so much an ethical decision as it was a logical one to be honest.
What I read from this post though was too trash my mobo amd everything else and keep my core2? Then save that to build a "banged up pc" with?
Now remember, I'm not that smart lol, but that sounds like going in the opposite direction. Get a new mobo, new soundcard, new everything, leave the processor, but for what? Speed is inherent to the processor no? If I got a new computer and keep the processor I'm just not seeing how thats going to make it any more powerful.
I don't know I think its more important you guys know everything I'm working with now, let me get that info. If anyone has recommendations please, I'd like to get all the parts asap. Don't want to jump into anything stupid though so I just ask for honest opinions please. Thanks everyone!
edit: I'll also take a pic of my taskbar window open and what it looks like with FL open so maybe you guys can get a better idea. brb. |
No, I was just joking about the VM thing, but honestly I think something else is wrong with your system as an E7400 shoudn't be freaking out with what you're throwing at it.
Do a backup of all your important stuff, then do a true format (erase any partitions etc.) and reinstall windows. Then only install what you need on it.
I had a PC that just wasn't giving me the performance I needed but it's spec was fine. After a long search I found there were chipset drivers for the mobo (not mentioned anywhere apart from the mobo website) and a processor optimzation driver. I got about 40% more out of that computer after doing that.
So my advice is to wipe, install and get every latest driver for your system and go to the website of each component manufacturer, then only install audio programs - I promise you'll see a really signifgant performance increase that will negate the need for a new computer. |
|
|
| DigiNut |
| quote: | Originally posted by DJ Robby Rox
No honestly its weird.
Say for instance this last project I have, with everything open and nothing playing, it hovers at exactly 24% cpu.
When I press play it instantly spikes to around 85%-90% then levels out a bit as the track progresses but its very unstable. |
That sounds like a buffering/latency issue. Assuming you're using some kind of ASIO driver, what is the latency set to, and have you tried turning it up? |
|
|
| DJ Robby Rox |
| quote: | Originally posted by DigiNut
That sounds like a buffering/latency issue. Assuming you're using some kind of ASIO driver, what is the latency set to, and have you tried turning it up? |
Yeh doing that does give me a bit more processing power, but it literally seems to go back to the same condition if I add just 1 or 2 more synths. (on a past project that has already been maxed out, I can't recreate it which I'm about to explain briefly)
The weirdest part is I'm trying to replicate the problem on FL by opening a patch/synth, adding a melody, opening another etc. I'm up to 14 z3tas lol, and its not doing anything to my CPU. Its not even going past 18%. I'm using heavy patches too and doing a lot of layering. (all synths being used obviously simultaneously)
The ONLY thing I haven't done is a single automation, or opened a single effect in the mixer. This is actually making me think I may be using a specific effect, that for some reason is messing with Fruity.
I never did this before, but I have some monster patches open, and they're fine it seems as long as I stay away from the mixer (havent experimented enough to isolate it)
So I'm def leaning towards something much more specific now. I'm going to open up a whole bunch of fx I normally use, one at a time, then shutting the fx down, and seeing if one seems to be spiking the cpu or making it jump up and down.
It doesn't make sense because the heaviest fx I use is Fruitys native reverb, (no Izotope Ozone or anything heavy from Waves) and thats not doing anything either. So I'm thinking it may be a specific 3rd part effect like glitch or camel space or something else I use regularly.
It actually may be a synth too because I'm only testing with z3ta now which is rather dumb.
But its odd that I can have as many z3tas open as I want with no problems on the CPU. It def has to be a specific synth/effect causing it. Just a matter of isolating it now. Thanks though Digi whatever the case is it actually doesn't seem to be processor the way its behaving.
Wow.. and I was willing to just go buy a processor! Now I'm more curious then ever, gonna go experiment till I figure out what synth/effect my CPU doesn't like, thanks! |
|
|
| DJ RANN |
| quote: | Originally posted by DJ Robby Rox
Yeh doing that does give me a bit more processing power, but it literally seems to go back to the same condition if I add just 1 or 2 more synths. (on a past project that has already been maxed out, I can't recreate it which I'm about to explain briefly)
The weirdest part is I'm trying to replicate the problem on FL by opening a patch/synth, adding a melody, opening another etc. I'm up to 14 z3tas lol, and its not doing anything to my CPU. Its not even going past 18%. I'm using heavy patches too and doing a lot of layering. (all synths being used obviously simultaneously)
The ONLY thing I haven't done is a single automation, or opened a single effect in the mixer. This is actually making me think I may be using a specific effect, that for some reason is messing with Fruity.
I never did this before, but I have some monster patches open, and they're fine it seems as long as I stay away from the mixer (havent experimented enough to isolate it)
So I'm def leaning towards something much more specific now. I'm going to open up a whole bunch of fx I normally use, one at a time, then shutting the fx down, and seeing if one seems to be spiking the cpu or making it jump up and down.
It doesn't make sense because the heaviest fx I use is Fruitys native reverb, (no Izotope Ozone or anything heavy from Waves) and thats not doing anything either. So I'm thinking it may be a specific 3rd part effect like glitch or camel space or something else I use regularly.
It actually may be a synth too because I'm only testing with z3ta now which is rather dumb.
But its odd that I can have as many z3tas open as I want with no problems on the CPU. It def has to be a specific synth/effect causing it. Just a matter of isolating it now. Thanks though Digi whatever the case is it actually doesn't seem to be processor the way its behaving.
Wow.. and I was willing to just go buy a processor! Now I'm more curious then ever, gonna go experiment till I figure out what synth/effect my CPU doesn't like, thanks! |
TBH, frooty is not really coded to the same degree that other sequencers are so it doesn't surprise me that there are strange conflict issues or mystery CPU drains. IIRC, frooty only just got multi processor support and cubase had it integrated what 3 years ago?
Honestly, for the amount of time you spend on production (or at least discussing it), I would suggest switching to cubase, sonar or logic. It will probably be one of the best things you ever do. |
|
|
| DJ Robby Rox |
| quote: | Originally posted by DJ RANN
TBH, frooty is not really coded to the same degree that other sequencers are so it doesn't surprise me that there are strange conflict issues or mystery CPU drains. IIRC, frooty only just got multi processor support and cubase had it integrated what 3 years ago?
Honestly, for the amount of time you spend on production (or at least discussing it), I would suggest switching to cubase, sonar or logic. It will probably be one of the best things you ever do. |
Yeh unfortunately I actually spend wayyy more time on Fruity then I do here lol.
I would have to say since being a loyal customer to FL since 2005 (reason before that) and hearing this as much as I have been hearing recently, I'm closer then I've ever been to making that move.
I'm just not sure honestly what to expect when I make the move. I do feel for a few good few months I won't be making any music at all because I'm gonna want to learn the sequencer as much as possible. With FL I never had that phase because it was all in front of my face.
Honestly I just expect learning anything but Fruity to be like learning Reason (only other sequencer I know) and with Reason it took me 6 months just to learn all the essentials for trance. With FL it was like 2 weeks. So its a commitment thing as the moment.
Another thing if I had a mac I would go for Logic right now (because I have a thing for logic I just love the way it works/looks when I watch tuts or we) but ultimately it will have to be either Sonar or Cubase like you say.
It seems more people here use Cubase, and the one week I tried it was extremely frustrating to say the least. At some point however you are right, and I will have to make that move. Its one thing after another after another with FL and I'm getting sick of it. ESPECIALLY when I got the virus and learned I couldn't do render recording, only realtime. That was bs imo. FLs the only fvcking program like that too. |
|
|
| DJ RANN |
Cubase really isn't that hard to get your head round and since moving to logic, my workflow and enjoyment has increaed dramtically.
The only big difference is that you don't program pattern, instead you just payout the track in a linear manner (which makes more sense to my brain) whilst still combining normal signal flow structure and superb midi implementation.
I think once you begin to outgrow fruity, the advantages of it original attraction (simplicity, layout) become more and more of a hindrance.
Just bite the bullet and go Cubase (or mac + logic if you can) and you won't look back. |
|
|
| RichieV |
| is it possible that as diginut mentioned , the problem is actually an asio buffering issue ? IS it possible your soundcard is not so great ? |
|
|
| Nightshift |
| quote: | Originally posted by DJ RANN
Cubase really isn't that hard to get your head round and since moving to logic, my workflow and enjoyment has increaed dramtically.
The only big difference is that you don't program pattern, instead you just payout the track in a linear manner (which makes more sense to my brain) whilst still combining normal signal flow structure and superb midi implementation.
I think once you begin to outgrow fruity, the advantages of it original attraction (simplicity, layout) become more and more of a hindrance.
Just bite the bullet and go Cubase (or mac + logic if you can) and you won't look back. |
or get the best of both worlds with Ableton :) |
|
|
|
|
