Just downloaded the Toxic III demo and the sounds are amazing but for one thing. Whenever I play a sustained sound like a pad or led sound, I get this prominent constant chugging click, click, click, click, click,click,click sound on and on and on for as long as I hold down the key/keys. It almost sounds like a clipped signal, but it's not clipping anywhere.
I'm just talking about presets mind you, so there shouldn' t be any filters or oscilator settings causing this.
Has anyone had this probelm?
Toxic III Clicking?
-
- KVRAF
- 7315 posts since 7 Mar, 2003
-
- KVRist
- 151 posts since 5 Jul, 2004
Yes, it looks like your audio buffer is too short... what is your host, samplerate, and buffer size? Can you see a CPU usage in your host?
EDIT: and what's your CPU also.
EDIT: and what's your CPU also.
-
- KVRist
- Topic Starter
- 217 posts since 19 Oct, 2005 from Philly
I tried changing my buffer settings and that seemed to do the trick. Still, as nice as this synth sounds I don't see how I could ever use it. It's quiet and smooth as long as I don't hold down more than 3 keys at a time. Press down a fourth key and it starts clicking. What's worse is that I had to set my buffer size as HIGH as my card would go , 2048, to get this level of performance. Is there such a thing as an app being "buffer size hungry"?
I usually keep my setting at 512 with no problems.
Anyway, even if I lived with the only three notes down at any time rule, I can't record at that buffer setting. The latency from when I press a key to the time I hear it, at that setting, is so high that it's annoying to even play, much less try overdubbing some pads onto a composition. The toxic track would be horrible out of time to the rest of the composition.
Shockingly, EVEN WHEN I set the buffer size to a measly 64 samples, which should give me zero latency, there was still an annoying latency. Not bad, but enough to notice and be irritating to the point where I would use a patch in Reason before Toxic. It's ashame realy.
Unless there's some way that I'm overlooking to compensate for this, I don't see how I could use this synth.
Mind you, I'm fairly new to the world of MIDI, so I could be overlooking a very basic and simple fix or workaround to such a problem.
In case this offers any insight, my host is Live 6. I've got 1 Gig of system memory. I'm running XP with an Athlon 3000xp cpu. For my trials with this plugin, I'm only using ONE midi track in Live, that's it. My controler is an M-Audio Radium 49 through USB and my card is an M-Audio Delta 44.
I usually keep my setting at 512 with no problems.
Anyway, even if I lived with the only three notes down at any time rule, I can't record at that buffer setting. The latency from when I press a key to the time I hear it, at that setting, is so high that it's annoying to even play, much less try overdubbing some pads onto a composition. The toxic track would be horrible out of time to the rest of the composition.
Shockingly, EVEN WHEN I set the buffer size to a measly 64 samples, which should give me zero latency, there was still an annoying latency. Not bad, but enough to notice and be irritating to the point where I would use a patch in Reason before Toxic. It's ashame realy.
Unless there's some way that I'm overlooking to compensate for this, I don't see how I could use this synth.
Mind you, I'm fairly new to the world of MIDI, so I could be overlooking a very basic and simple fix or workaround to such a problem.
In case this offers any insight, my host is Live 6. I've got 1 Gig of system memory. I'm running XP with an Athlon 3000xp cpu. For my trials with this plugin, I'm only using ONE midi track in Live, that's it. My controler is an M-Audio Radium 49 through USB and my card is an M-Audio Delta 44.
-
- KVRist
- 151 posts since 5 Jul, 2004
Ok, thanks. I'm checking it and will try to resolve this problem if it's a ToxicIII bug (still a chance it's connected to your system).
Author and support for ToxicIII, Morphine and PoiZone VSTi's.
-
- KVRist
- 151 posts since 5 Jul, 2004
IRBY: plz checkout your pm, I've sent you a message there.
-
- KVRAF
- 1707 posts since 15 Aug, 2003 from Indianapolis
My setup is very similar to yours, and I have no problems with Toxic. Only differences: Host, I'm using Tracktion 2. Midi controller (shouldn't matter).IRBY wrote: In case this offers any insight, my host is Live 6. I've got 1 Gig of system memory. I'm running XP with an Athlon 3000xp cpu. For my trials with this plugin, I'm only using ONE midi track in Live, that's it. My controler is an M-Audio Radium 49 through USB and my card is an M-Audio Delta 44.
Hope Maxx gets it sorted for you.
-
- KVRer
- 17 posts since 28 Nov, 2003
I am getting the same issue in Logic on OS X.... If i play a 4 fingered chord on a pad (long decay), then play my next chord the sound breaks up and disappears... not getting CPU over load though, CPU stops DEAD at about 25% on one of the CPUs.... Buffer is set to 1024
Mac OS X 10.4.8
G5 PPC Dual 2Ghz
Logic Pro 7.4.3
3Gb RAM
PS - Plug-in is wrapped with FXpansions VST2AU v2
Mac OS X 10.4.8
G5 PPC Dual 2Ghz
Logic Pro 7.4.3
3Gb RAM
PS - Plug-in is wrapped with FXpansions VST2AU v2
-
- KVRist
- 151 posts since 5 Jul, 2004
It's fixed in 1.4 update, this update is now in testing process... to be released soon.
Author and support for ToxicIII, Morphine and PoiZone VSTi's.
-
- KVRer
- 17 posts since 28 Nov, 2003
Thanks Maxx 