If you're warping audio in live realtime it takes a certain amount of cpu - quite a significant chunk if it's complex mode.
Live still seems to cpu spike for no apparent reason on my AMDX2 - unless I assign it affintiy to one core - that seems to sort that problem out.
As far as I'm aware there are no SSE2 optimisations etc. in Live - I could be wrong though.
Live is so slow with plug-ins-- stats tell the truth
-
- KVRAF
- 3617 posts since 26 Sep, 2003 from Bradford - The Armpit of Britain
-
- KVRian
- Topic Starter
- 503 posts since 28 Mar, 2005 from Annapolis, MD
Does anyone have ILOK? If so, try out this plug-in in Live 5 or in Cubase (PSP Neon HR) and see how your CPU consumption is for 44.1KHz, 2048 sample rate on your card, 24 bit. All 8 filters turned on in Neon HR. Tell me what your CPU consumption is with High resolution. Does Max res crash the program?
-
- KVRAF
- 2938 posts since 18 Jul, 2005
My CPU usage in live and eXT with audio running through the same plugins is pretty much the same, as far as I can discern from guessing the value of eXT's curious CPU meter.
-
- KVRian
- Topic Starter
- 503 posts since 28 Mar, 2005 from Annapolis, MD
I changed the plug-in buffer size using Live 5 preferences to 2048 and now the CPU consumption is about 20% with Neon HR. Still more than Sound Forge, but very acceptable.
Funny, I thought I had changed this to 2048 yesterday and still crashed Live 5. I guess not. Turns out it seems you have to close whatever set you have going in Live 5 in order for the plug-in buffer size to actually change.
I had my soundcard set to 2048 and thought that was fine. I also needed to change the plug-in buffer size within Live preferences. Learn something new every day. I am humbled.
I apologize to the Abes for calling their program slow.
The CPU usage at max with FAT mode is 18%.
By the way, Neon HR is really a fantastic equalizer.
Funny, I thought I had changed this to 2048 yesterday and still crashed Live 5. I guess not. Turns out it seems you have to close whatever set you have going in Live 5 in order for the plug-in buffer size to actually change.
I had my soundcard set to 2048 and thought that was fine. I also needed to change the plug-in buffer size within Live preferences. Learn something new every day. I am humbled.
I apologize to the Abes for calling their program slow.
The CPU usage at max with FAT mode is 18%.
By the way, Neon HR is really a fantastic equalizer.
-
- KVRian
- 624 posts since 22 Jan, 2003 from USA
feyshay, what is the impact of changing the plug-in buffer size? What is the trade off?
-="I beat the Internet...the end guy is hard"=-
-
- KVRian
- Topic Starter
- 503 posts since 28 Mar, 2005 from Annapolis, MD
No real trade-off as far as I see. Neon is designed for mastering. (And it is a great mastering equalizer--the best I've heard. At least if you want transparent.)drez wrote:feyshay, what is the impact of changing the plug-in buffer size? What is the trade off?
The only problem with changing plug-in buffer size to something like 2048, is that it could not be used on individual tracks because delay compensation would not be adequate (and your tracks would be out of synch).
If you are going to use this plug-in within a track or in a sub-mix, you would use the regular Neon and run it at a lower buffer (with your delay compensation activated).
In my mind, this equalizer is the perfect compliment to MasterComp (for transparent compression/limiting) or Vintage Warmer (for a little coloring compression/limiting)
-
- KVRAF
- 3617 posts since 26 Sep, 2003 from Bradford - The Armpit of Britain
I alwasy have the plug in buffer set to be the same as the soundcard buffer - someone explained why that 's optimal onetime - but I forget the reasons etc.
-
- KVRian
- Topic Starter
- 503 posts since 28 Mar, 2005 from Annapolis, MD
You will have some big problems with sound if you have them set very differently. I tried that last night. Don't feel like thinking about why right now and explaining it.