TranceAddict Forums (www.tranceaddict.com/forums)
- Production Studio
-- What kind of performance boost can I expect with this upgrade?
Pages (9): [1] 2 3 4 5 6 7 8 9 »
What kind of performance boost can I expect with this upgrade?
I'm just sick and tired of not being able to finish my best tracks because right now I have a Pentium D 3.0 (passmark of 768 from cpubenchmark.com)(not overclocked)
On one project I have the following instances running:
Gladiator (bass)mono
FireBird (lead) mono
Toxic Biohazard (pad)2 keys/octaves
Z3ta (bass) mono
Albino (arp)2 keys/octaves
Nexus (lead layer) 4 keys/octaves
and I'm hitting 80% prob a good 15% is coming from fxs alone.
I have the core2duo E7400 2.8ghz coming with new mobo that I can overclock so I'll be hopefully getting up to 3.4ghz with it. Its rated 1833 on cpubenchmark.com
My question now, because the passmark is more then double, AND I'll be overclocking, does that = a more then double performance increase?
Like double the amount of vsts? Relatively speaking of course, or no am I way off?
Thanks, I'm excited so any help I'd appreciate.
Using FL Studio btw.
It depends on the latency you are going to use.
I have a CPU that is the equivalent of the one you are getting at a speed of 2.5 GHZ, i use 1024 samples latency and have never runned out of CPU yet.
I havent tested the limit yet, but i loaded about 30 VST instruments for a project once, without even breaking the 50% barrier.
Oh and you are running FL Studio which means you will only be using one core, which then means that what i just wrote prolly does not mean shit.
But yeah i`d say that roughly you will double the performance.
The Pentium D was never a great CPU.
New version 8.5 of Fl is in beta, I believe it has multithread supported. Not 100% sure though.
Well the multicore already works in 8 for vsts and honestly thats all I care about.
I never understood how people whored out on fxs alone, and even when I have a lot going on in my sends/mixer its still only like having one z3ta open.
I really hope its as powerful as you say subtle, I start with the lowest latency I can in the begining and adjust it as the I use up the cpu.
If I get 20 total I'll be happy as a pig in shit. Then maybe I can finally finish the countless decent tracks I was forced to stop over the years! Thanks guys, and if anyone else has comments please let me know, especially if you have a comparable cpu.
http://www.image-line.com/documents...5-public-beta-3!&entry_id=1237563404
I just looked here, and they also added multithread to effects, so you should be set man. I been using dual core 2.0 ghz for a while now, and I don't run out of cpu, depends though how many tracks too I guess. I would say that you should be pretty safe.
| quote: |
| Originally posted by Lucidity http://www.image-line.com/documents...5-public-beta-3!&entry_id=1237563404 I just looked here, and they also added multithread to effects, so you should be set man. I been using dual core 2.0 ghz for a while now, and I don't run out of cpu, depends though how many tracks too I guess. I would say that you should be pretty safe. |
you can bounce to audio your set-in-stone instrument tracks or patterns so that you can rid of generators (vsti). Audio playback is much more generous on the CPU than realtime synthesis.
i doubt u need to overclock man. i have a 2,4Ghz and i never had issues with CPU overload since i got that. Its a Quad but Reason only uses one core anyway.
Dude, Honestly, why the fuck arn't you using 2048 samples? Are you play live? I don't know, but if not, your latency should be as high as humanly possible. Anything less is....just less. 
| quote: |
| Originally posted by cronodevir Dude, Honestly, why the fuck arn't you using 2048 samples? Are you play live? I don't know, but if not, your latency should be as high as humanly possible. Anything less is....just less. |
No
I use 2048 samples in ASIO. And I never get clicks or pops. Do you have some reason NOT to set your sound card to a high latency?
Its only 47 ms that is a reasonable time to wait to hear sound when I push "play". Its not even a whole second's wait :P
| quote: |
| Originally posted by cronodevir No I use 2048 samples in ASIO. And I never get clicks or pops. Do you have some reason NOT to set your sound card to a high latency? Its only 47 ms that is a reasonable time to wait to hear sound when I push "play". Its not even a whole second's wait :P |
If you have something to say, say it.
I want to see if your going to bring up the point I specifically didn't mention just so you would call me on it. And I will show you were I already mentioned it :P
Using 2048 leads to an consistent annoying latency when recording, playback and etc etc.
Maybe it works for you, but im sure it does not work for alot of others.
When you eventually upgrade your CPU to be able to use lower latencies you will probably understand why lower latency is much more convenient.
I use 512 or 1024 samples (20 something ms) , im sure some people prefer even lower latencies than that.
Cept that I already mentioned this is a setup without hardware. :P So recording isn't an issue. And I don't plan on ever having to record. And playback...00o0o...2/3 of a second wait. Not that big of a deal. Its not like it goes out of sync.
Recording and playing MIDI, or maybe you dont use a keyboard ?
Is there a difference between 25 and 45 milliseconds ?
YES, huge difference, especially when you are pressing stop and play hundreds of times within a session.
When working on a song and not in a jam session, I only play keyboard to build the melody then I open the piano roll/key editor and input the melody with the mouse. Its much easier. Then playing the melody and trying to even out each note and make them all uniform. Plus half the time I cannot even play the melody. Because I further refine it in the key editor, to a point beyond my playing skill.
When I'm in a jam session I go to 1024 samples because then it actually matters. Even still, regardless to what the latency is, my keyboard has its own sounds, and those don't lag. So I can still record a melody, with my keyboard, at very high latency. Because the midi information is still going to be on time if you play on time, regardless to if the actual sound is late.
The only hard part about recording midi information with high latency is the late sounds throw alot of people off and they can't play properly.
You seem to think that everything within production that works for you is the law of how things are and should be done, you seem to be unable or unwilling to understand how people could prefer something different that what works for you.
Even if you can live with 2048 samples, you could at least try and understand why lower latencies in any case are better when it does not sacrifice performance.
To me anything over 25 millisecond is an annoyance in recording or playback.
Some people may even swear to latencies as low as 5 or 10 ms.
But i get it, this is one of your opinions, great.. 2048 samples is not a problem for you, but it is to me.
| quote: |
| Originally posted by Subtle you seem to be unable or unwilling to understand how people could prefer something different that what works for you. |
| quote: |
| Originally posted by Subtle Using 2048 leads to an consistent annoying latency when recording, playback and etc etc. Maybe it works for you, but im sure it does not work for alot of others. When you eventually upgrade your CPU to be able to use lower latencies you will probably understand why lower latency is much more convenient. I use 512 or 1024 samples (20 something ms) , im sure some people prefer even lower latencies than that. |
| quote: |
| Originally posted by Subtle Recording and playing MIDI, or maybe you dont use a keyboard ? Is there a difference between 25 and 45 milliseconds ? YES, huge difference, especially when you are pressing stop and play hundreds of times within a session. |
| quote: |
| Originally posted by Subtle You seem to think that everything within production that works for you is the law of how things are and should be done, you seem to be unable or unwilling to understand how people could prefer something different that what works for you. Even if you can live with 2048 samples, you could at least try and understand why lower latencies in any case are better when it does not sacrifice performance. To me anything over 25 millisecond is an annoyance in recording or playback. Some people may even swear to latencies as low as 5 or 10 ms. But i get it, this is one of your opinions, great.. 2048 samples is not a problem for you, but it is to me. |
This is why i said "Here we go again"
Because i knew that if i explained it you would go on for 3 pages how it works so well for you.
What you said is that you DONT understand how people could use something else than 2048.
Ive already explained it to you several times.
I never said you were wrong.
Or, you could have not said anything at all because I already know this, I already explained it. And that is that. You felt like you needed to say something even though you didn't read the thread. In my first post I said if people aren't playing live. That covers all hardware, recording, playback everything that latency effects.
| quote: |
| Originally posted by cronodevir No I use 2048 samples in ASIO. And I never get clicks or pops. Do you have some reason NOT to set your sound card to a high latency? Its only 47 ms that is a reasonable time to wait to hear sound when I push "play". Its not even a whole second's wait :P |
Yep, that along with my first post clarified that i meant without using hardware. Or live play. Keep up man :P Take my words in the context of the whole thread, not the individual posts.
Just for the record. I didn't push this off topic.
Do you *like* to argue with me?
| quote: |
| Originally posted by cronodevir Yep, that along with my first post clarified that i meant without using hardware. Or live play. Keep up man :P Take my words in the context of the whole thread, not the individual posts. Just for the record. I didn't push this off topic. Do you *like* to argue with me? |
Dude, Why are you still talking?
My first two posts answered all this. Before you even said anything, WOW that's some preemptive shit!
Powered by: vBulletin
Copyright © 2000-2021, Jelsoft Enterprises Ltd.