First to say I really love my Gemini, and will say more about how I’m using it and share some patches and such in good time.
Here I have a few questions about functions I have either misunderstood or are perhaps not working, I thought I’d start a thread before preparing an email to support in case any of my fellow forum-goers manage to help me resolve or clarify anything (for instance whether it’s just me or not!) …
I cannot get LFO 1 to function in Direct Parameter Mapping. The manual states: “To increase the potential of LFO 1, this method applies to the button labelled LFO 1” - this leads me to believe I should be able to hold it, move one of the sliders corresponding to an available modulation destination, and then have LFO 1 acting as a modulation source. Doesn’t work for me.
Modulation of DDS 2 Pulse Width. I am led to believe this should also be possible. What I find is that, while I can create a direct parameter mapping using the above method, in practise this only effects the DDS 1 Detune parameter.
Playing over the Sequencer. The manual states I should be able to use remaining voices to play along with the sequence while SEQ REC is flashing. I can only do so by activating another layer, I was under the impression - although it isn’t precisely clear - this referred to being able to play over the sequence with the available remaining voices on the same layer?
Wave Morphing algorithm. Curious what’s going on here - sounds quite close to crossfading. Don’t know if anything more “interesting” is possible there? Still sounds great just somehow a bit more “vanilla” than I was expecting. Perhaps it is just the static nature of the waves, and I have distorted expectations based on wavescanning?
That’s all I can think of just at the minute, although another question I have concerns interoperability of Gemini & Super 6 patches (although obviously not Gemini performances). I tried loading some Super 6 patches, once as they were and once just by changing the .s6 suffix to .usg, to no avail. Do I remember reading of a converter somewhere? That would be really cool! (Obviously not all patches would transfer with 100% fidelity, but still a nice option to have.)
Lastly just to say that it sounds really great, and goes to some quite interesting experimental places. I’m really enjoying exploring!
I have a question regarding „hold“ while Keyboard is in „single mode“:
If i play a note or an arpeggio and activate „hold“ in the upper layer, „hold“ gets turned off when i switch to the lower layer (and vice versa)!
I don‘t think it‘s an error in my SG (but i may be wrong). In „split mode“ everything with „hold“ works as excpected, „hold“ can work simultanuosly on both layers. So it shouldn‘t be a problem with processing power.
Does someone know why it is this way or how to use „hold“ in keyboard „single mode“ on both layers?
Thanks for the link, @MonsterGemini - so it seems the passage regarding LFO 1 as modulation source was left over from an early draft of the manual, but we can hope that UDO may implement it at some point in the future - would add a few possibilities, especially in combination with “battwave” (the ability to use the additional waveforms also as LFO shapes, as seen in the Super 6).
Regarding the hold function, I would guess the problem is that in single mode only one of the layers is active at any one time.
You may be right with the hold function.
But i find the “split mode” limiting (you just don’t have the whole keyboard to play for each layer and you basicly have to use the lower layer for low frequency/bass sounds and the upper layer for higher frequency sounds/leads, because they are assigned that way on the keyboard).
For a “performance instrument” i was hoping not to be limited like this!
I had a helpful response from support (a while ago now!) and they answered my questions.
As mentioned, LFO 1 assignable via direct parameter mapping was planned but is as yet unimplemented.
DDS 2 Pulse Width is modulated via the dedicated controls and not the modulation matrix.
Inability to play over the sequencer is a known bug that should be fixed in the next firmware update.
Wave morphing more or less corresponds to crossfading. I seem to remember stumbling across something a little more interesting (definitely more morph than fade) when looking into phase modulation but I’ll get back to them on this.
and post it in the Feature Wishlist corner.