Owning the Gemini for some months now, I am keen on UDO addressing these issues in a future update. What do you think?
Modulation AT → VCF slider does not work
Hold Button: held notes are often stopped randomly after some time
User Waves are not loaded into LFO1
Modulation Matrix Velocity → Attack of ADSR is sometimes wrong when A is set to 10s.
White Noise Waveform of LFO2 has often no effect on parameters like DDF or filter, I would expect Rate should LFP filter and boost the low frequency noise.
I’d like to see an accelerate function for the mod amount button
LFO1 LR Phase slider does not behave as described in the user manual: phase of Pi is at slider position of around 75%, not at 50%
The AT to VCF slider does not work on my unit either. Another issue is the polyphony-note stealing issue. When switching between binaural and regular mode on occasion the Super Gemini will steal notes when playing only 6-8 in binauaral and 14-18 in regular mode. Seems to happen after switching binauaral to regular mode on layered or split patches.
LPF always open on Note On, even when not modulated
Playing over Sequence not working
Velocity response hard to master
Micro-tuning
I’ve noticed and reported most of the bugs you listed too, and they answered the same thing as most on this forums, that it’s actually fixed on their test version and will be deployed shortly to us.
But point 7 imho is the consequence of a broader issue. As I reported it almost right when I started using the synth, I was answered it was because of the exponential response of the controller. They did not acknowledge an issue. I had the same answer when arguing about the wrong labeling of the DDS2 tuning knob (not the +1/-1 inversion). Always this “finely tuned exponential curve”. I gently tried to express that exponential curve serves a purpose, that not all controls should be applied this kind of function. To no avail. But it seems at the root of some of the most discussed problems, like the velocity response or this phase issue - why pushing phase exponentially? What do you think?
To add to the discussion, I find it worrying to see documented features piling up that aren’t implemented or don’t behave as expected, i.e. “morphing” does not equal “cross-fading”, buggy sequencer, unsettling controller or modulator response…
I do hope 1.27 will fixed most of it, and that UDO will at least acknowledge those issues and talk about it with the community of users. I was able to afford one poly-synth, and won’t be able again. I’m not mad at UDO, it seems they are working on it. And it still sounds stellar at its core. But if the reviews nor the manual can not be trusted about a flagship 4k “sound-design workhorse” synth, it makes me feel weird. Already the .26 revision of firmware.
For the DDS2 tuning, this is an appropriate feature to control the beating without the use of a second fine tune knob. This is ok with me.
Possibly they reused this exponential curve function to the phase knob, but this does not make any sense, as you said. Phase control shall be linear.
UDO is a small company, I guess they are overloaded with other topics, working for the monthly income always has priority one.
Any idea when these bugs will be addressed? The unadjustable velocity curve and vcf slider not working are particularly troublesome. This won’t be replacing my nord in a live setting any time soon.
I respectfully do not agree @skerjanc , as you have to activate NRPN mode to actually be able to tune the oscillator. Otherwise the function puts DDS2 always out of tune. And activating NRPN cuts your synth from any MIDI integration without computers or niche MIDI hardware.
It actually does not send any MIDI NRPN messages at all because of the bandwith, so no MIDI out in “high precision” mode…
Beating only appears around the same note, when DDS2 is slightly out of tune and it’s working around -/+1. But I can’t get a fourth, a third, any kind of just interval, because the function and/or the resolution of the controller is not properly calibrated and intervals are always out of tune if NRPN is not activated. One or the other, it’s the first time I have to choose between control and fine tuning on any hardware. And it’s switching globally, so no automation play for filter, envelopes, etc. Is the enclosing only a MIDI controller of a sound engine? How is it a parameter to activate and not the default and advertised behavior, as without it it simply does not work as intended, and NRPN as I said is niche in this aspect? Tuning is tuning.
It should have been a regular Tuning function on the tuning knob, so we can actually trust the label, and a Detune or Fine Tune with the unused Shift button for added subtlety. So we can record and use MIDI CC like in any other synth in any price range.
