Pops and clicks.....
-
- KVRian
- 966 posts since 28 Sep, 2002 from UK
hi
Giving Zebra 2 a good workout tonight.
I notice bad pops 'n' clicks on many patches, even those with fairly modest cpu usage
e.g. BAS Alienated
This is especially apparent when fast trilling.
The cpu meter in Cubase SX2.2 is flickering between 40 & 50 % so is not near maxed out.
If I drop my latency to 6ms they disappear.
Obviously an audio card / buffer related issue.
However many other VSTi's are happy at this setting, even relatively thirsty ones like z3ta+, Octopus etc.
Is there a reason why Z2 should behave like this ?
Spec: P4 3.06 533, Asus P4PE, 1 GB pc2700, rme dsp9652, sw1000xg + plugstation, poco FW, win xp home sp2, Podium, Cubase SX2, FLS 6, Reason 3, Abelton Live 5 etc etc.
BC
Giving Zebra 2 a good workout tonight.
I notice bad pops 'n' clicks on many patches, even those with fairly modest cpu usage
e.g. BAS Alienated
This is especially apparent when fast trilling.
The cpu meter in Cubase SX2.2 is flickering between 40 & 50 % so is not near maxed out.
If I drop my latency to 6ms they disappear.
Obviously an audio card / buffer related issue.
However many other VSTi's are happy at this setting, even relatively thirsty ones like z3ta+, Octopus etc.
Is there a reason why Z2 should behave like this ?
Spec: P4 3.06 533, Asus P4PE, 1 GB pc2700, rme dsp9652, sw1000xg + plugstation, poco FW, win xp home sp2, Podium, Cubase SX2, FLS 6, Reason 3, Abelton Live 5 etc etc.
BC
If God did exist (and he doesn't) he would answer to the name of Maurizio
-
- KVRAF
- 4229 posts since 9 Apr, 2003 from Right here, in front of my computer...
-
- KVRian
- Topic Starter
- 966 posts since 28 Sep, 2002 from UK
OK - I hope so.beej wrote:Is this the version posted yesterday? Urs said there may be clicks and pops in that version, and not to worry about i, he's still working on it...
Actually if it's just related to attack then changing the buffer size shouldn't make any difference..?
Last edited by basic channel on Wed Mar 22, 2006 11:40 pm, edited 1 time in total.
If God did exist (and he doesn't) he would answer to the name of Maurizio
-
- KVRAF
- 4229 posts since 9 Apr, 2003 from Right here, in front of my computer...
- u-he
- 30215 posts since 8 Aug, 2002 from Berlin
Well, if it's a new bug it might be solved soonishly. The official version from January 31st should not have any problems with buffersizes.
Urs
-
- KVRian
- Topic Starter
- 966 posts since 28 Sep, 2002 from UK
It's weird...
After playing around some more tonight, it seems to affect some patches and not others.
e.g. playing some patches which bounce around at 40 - 60 % cpu causes glitches @ 3ms but not at 6ms
Others with similar highish xpu use play without glitches...
Again I would say that many other high cpu VSTi's do not cause this problem e.g. glitches only occur when really pushing cpu 80% +
BC
After playing around some more tonight, it seems to affect some patches and not others.
e.g. playing some patches which bounce around at 40 - 60 % cpu causes glitches @ 3ms but not at 6ms
Others with similar highish xpu use play without glitches...
Again I would say that many other high cpu VSTi's do not cause this problem e.g. glitches only occur when really pushing cpu 80% +
BC
If God did exist (and he doesn't) he would answer to the name of Maurizio
-
- KVRist
- 31 posts since 19 Jul, 2003
Sorry to necro this thread, but I'm trying out Zebra and getting the same behavior in the latest demo version. Reading the 2.3.3 beta thread, I see something about a 16 sample buffer. Could that be causing the pops and clicks when using a 3ms buffer in Cubase? As 'basic channel' stated, dropping to 6ms fixes the problem...
Is this being addressed with the "low-latency" feature?
Cheers ~ jp
Is this being addressed with the "low-latency" feature?
Cheers ~ jp
- u-he
- 30215 posts since 8 Aug, 2002 from Berlin
I don't know if these things are related. I think teh old issue was due to some poor load balancing feature in Cubase combined with a lesser optimized version of Zebra's oscillators. Which might not be a problem nowadays anymore.
Are you using the low-latency feature in Z2.3.3?
In the patches involved, does changing the Oscillator's "Resolution" parameter affect the amounts of pops and clicks?
Another thing, do you get an error message when you open a new instance of Zebra?
Are you using the low-latency feature in Z2.3.3?
In the patches involved, does changing the Oscillator's "Resolution" parameter affect the amounts of pops and clicks?
Another thing, do you get an error message when you open a new instance of Zebra?
-
- KVRist
- 31 posts since 19 Jul, 2003
I'm a PC. So not yet.Urs wrote:Are you using the low-latency feature in Z2.3.3?
Just got into work, so I'll update this post after I get home and can further investigate the issue. I do know that several of the DX7 patches exhibited this behavior. Many patches did not.Urs wrote:In the patches involved, does changing the Oscillator's "Resolution" parameter affect the amounts of pops and clicks?
No error messages.Urs wrote:Another thing, do you get an error message when you open a new instance of Zebra?
On a separate note, I'm quite impressed with the intimacy and response time that you offer your users. That alone is worth adding this piece of kit next pay period.
Cheers ~ jp
-
- KVRist
- 31 posts since 19 Jul, 2003
Well... I failed miserably as a scientist. One of the ADAT ins on my RME Hammerfall was not working, so I a) took the card out b) removed the TOSLink jack that was now only partially connected to the circuit board c) installed two UAD-1 cards d) disabled the 16 ADAT ins/outs that were not available and e) enabled 16 instances of the UAD Neve 88RS plug... no more pops and clicks at 3 ms with Zebra. So much for modifying one variable at a time, eh?
I really look forward to becoming a paid customer in the following weeks
I really look forward to becoming a paid customer in the following weeks

