Hey im using Psp Neon on a G4 with Pro tools 6.4 and its running extremly slow slow. I mean slow in a way that it takes 2 mjn for it to turn a knob even when theres no audio for it to transform. Some times it even doesnt do that and eventually it just crashes. I already changed the playback engine buffer size and it seems to work a bit better. Now I read on this forum that I may no to change my plugin buffer size. My question is: how do I do that? Any other advice is also appreciated.
Thanks in advance !
PSP Neon running very slow
-
- KVRAF
- 6504 posts since 25 May, 2002 from Bobo-dioulasso\BF__Geneva/CH
Specify what system you've got in more details, maybe it has something to do with it...
-
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
Do you have the Linear Phase (LP) button activated? It's on by default and really eats CPU.
-
- KVRian
- 503 posts since 28 Mar, 2005 from Annapolis, MD
Neon should not take much of a CPU hit. Now, Neon HR is a different beast. You should not have to adjust your plug-in sample buffer size with Neon. With all filters engaged on my machine, in LP and FAT mode, it takes up about 10% of CPU. Are you sure you are not talking about Neon HR. If you are, you just need to research your ProTools manual and find out how to change the buffer size (if you are using medium or max resolution). I'm not familiar with ProTools.
You really want to use LP, FAT mode, High res options, since these are some of the reasons this equalizer is sweet.
You really want to use LP, FAT mode, High res options, since these are some of the reasons this equalizer is sweet.
-
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
That's funny: LP mode introduces a noticeable delay in any track that I insert it in, even with PDC in Cubase, until I turn it off. 
-
- KVRian
- 503 posts since 28 Mar, 2005 from Annapolis, MD
Don't use LP mode on a track. I thought that Neon allowed for PDC, but Neon HR did not. I'll check in Cubase myself. The high res modes, I think, are more meant for mastering. You should still be able to use FAT mode. I'm surprised that PDC does not work with LP mode on the normal Neon. That's too bad.
-
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
It definitely does not work. I'm surprised they released it like this; it's the only pro plug-in I can think of that does this. But I think it sounds great with LP off, too, so it's not a big deal.feyshay wrote:Don't use LP mode on a track. I thought that Neon allowed for PDC, but Neon HR did not. I'll check in Cubase myself. The high res modes, I think, are more meant for mastering. You should still be able to use FAT mode. I'm surprised that PDC does not work with LP mode on the normal Neon. That's too bad.
-
- KVRian
- 503 posts since 28 Mar, 2005 from Annapolis, MD
You were using Neon, Bduffy, and not Neon HR. I know for a fact that PDC does not work in HR. Please clarify.
I think I remember reading in the manual that the PDC did not work in LP mode.
I'll post on the nearly dead PSP forum if I remember.
I think you'll do fine in FAT mode. I also use Master Q within tracks.
I think I remember reading in the manual that the PDC did not work in LP mode.
I'll post on the nearly dead PSP forum if I remember.
I think you'll do fine in FAT mode. I also use Master Q within tracks.
-
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
That's the normal version - not the HR. I'm confused now...FAT is only in the HR version - wouldn't that bog down the CPU as well? I've never used the HR version, so I'm not sure.
MasterQ is an excellent track EQ, I agree; possibly the cleanest EQ out there. Kinda heavy CPU also, I found.
MasterQ is an excellent track EQ, I agree; possibly the cleanest EQ out there. Kinda heavy CPU also, I found.
-
- KVRian
- 503 posts since 28 Mar, 2005 from Annapolis, MD
Yeah, FAT seems to double CPU amount, but it is when you go into medium and max resolution on Neon HR (in LP) that you really have to change your plug-in sample size (not the compensation, but the actual sample size that the plug-in uses). Before I started reducing the plug-in sample size for medium and high resolution, the thing would not work. I remember experimenting with this, and if you adjust the sample size, it is much kinder on CPU--but still could take 18% in FAT, HR, LP (and that's on a dual core 3.2GhZ)
-
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
Do you change that within Neon?feyshay wrote:Yeah, FAT seems to double CPU amount, but it is when you go into medium and max resolution on Neon HR (in LP) that you really have to change your plug-in sample size (not the compensation, but the actual sample size that the plug-in uses). Before I started reducing the plug-in sample size for medium and high resolution, the thing would not work. I remember experimenting with this, and if you adjust the sample size, it is much kinder on CPU--but still could take 18% in FAT, HR, LP (and that's on a dual core 3.2GhZ)
-
- KVRian
- 503 posts since 28 Mar, 2005 from Annapolis, MD
You don't change it within Neon. You shouldn't have to. I'm new to Cubase SX3. To run Neon HR at Max res, I would change the sample rate (recommended rates are in the manual) of the DAW(since lag is not an issue when mastering)and Live 5 allowed you to specifically change the sample rate of plug-ins.
I have not yet combed through the Cubase manual to see how to do change in plug-in buffer size.
You really shouldn't be concerned about that with Neon, though, since CPU consumption shouldn't be that big of an issue. This should only be a requirement of Neon HR.
I'll post when/if I found out how to change-in plug-in sample rate in Cubase.
I have not yet combed through the Cubase manual to see how to do change in plug-in buffer size.
You really shouldn't be concerned about that with Neon, though, since CPU consumption shouldn't be that big of an issue. This should only be a requirement of Neon HR.
I'll post when/if I found out how to change-in plug-in sample rate in Cubase.
-
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
Oh, you're right: there it is in the manual. I RTFM, but I must've skimmed over this bit. I think what we're discussing here is changing the host's buffer size/latency, easy enough to do - that is determined in Cubase by your interface's ASIO buffer; it cannot be set independantly. That's fine: I'm not a mastering engineer, and as much as I love Neon, I won't be shelling out for the HR anytime soon. And the regular Neon without LP sounds fine to me. And yes, CPU is nothing with Neon.feyshay wrote:You don't change it within Neon. You shouldn't have to. I'm new to Cubase SX3. To run Neon HR at Max res, I would change the sample rate (recommended rates are in the manual) of the DAW(since lag is not an issue when mastering)and Live 5 allowed you to specifically change the sample rate of plug-ins.
I have not yet combed through the Cubase manual to see how to do change in plug-in buffer size.
You really shouldn't be concerned about that with Neon, though, since CPU consumption shouldn't be that big of an issue. This should only be a requirement of Neon HR.
I'll post when/if I found out how to change-in plug-in sample rate in Cubase.
-
- KVRian
- 503 posts since 28 Mar, 2005 from Annapolis, MD
It's more than just changing the sample buffer of the DAW. I was changing two things within Live 5--the sample rate of my MOTU Traveler (which was the soundcard running Live 5), and I would also change the plug-in sample rate. (I didn't even know I could do this until I complained about having problems with Neon HR crashing the program when I was using Max Res, or Medium Res in FAT mode.