Messages

It definitely happens more often on the extreme DB filters but it happens nearly as often on the standard low pass filter. It typically occurs near the point where the cutoff silences the voice altogether or sooner if the resonance is high. It is also seems  to happen consistently with pulse LFO waveforms. I can see why all this would overload it but it handles almost everything else I throw at it like a champ.

On the original Atmegatron (V 2.4 I believe) the filter LFO tends to malfunction when the parameters are really pushed. If the resonance is high, the LFO rate is above 12 or so, and the cutoff is low (or high depending on the filter) the sound becomes distorted for a moment (relatively speaking lol) and then cuts out completely. Sometimes it can be brought back if the parameters are dialed down but sometimes it just will just stay silent unless you either restart the unit or load a preset.

Oh good! I'm glad this was sorted out, I'm a big fan of Strings. Thanks again!

Great thank you. I gotta say it's pretty great that you make yourself so available to help your customers out. Keep up the excellent work!

I should add that the arpeggiator is also out of phase.

It does respond to tempo when I hit start on the electribe. But it is definitely out of phase with the start of the bar.

I've been using my electribe 2 to sequence my Atmegatron and several of its software versions without issues of any kind until Strings. Its tempo refuses to sync rendering the waveform cycler, phaser, and LFO largely unusable for anything beyond subtle modulation. I'm controlling it with my electribe through a Midi Solutions quadra thru box. I haven't had any latency issues using this method thus far but maybe I've just been lucky.

Has anyone else had this issue with Strings or any other version? Suggestions for a fix?