Would you consider adding possibilty for the coarse knob position also to be memorized as preset, sometime in the future updates? I know that is useful for the fundamental pitch to be unaffected when, for example, user wants to scroll trough presets while melodic sequence is controling the pitch, but sometimes "coarse" knob functions more as a timbre parameter rather than musical pitch (especially when taking advantage of atonal ratios of various combo modes this module provides), so it woukd be useful to have option of saving it within preset as well... And for those who use it for determining fundamental pitch, it would also allow for making preset sequencing work for making melodies, or for making monophonic rhythms in a percussion mode (switching sequentially between high and low register percussion sounds). I hope i make sense...
Oh man, thanks for making this vid. Huge help! Question/comment on the "Pressing QUANT. twice to make PITCH 2 In become a clock in for Osc Two while in LFO Mode" - when in the blicking QUANT mode, PITCH 2 seems to be a clock in for Osc 2 even if it is NOT in LFO mode. Not sure if this is a documentation mistake or an implementation mistake. I actually prefer it the way it is since that would just be one too many things to keep track of (Why is Osc 2 not acting as a clocked LFO? Quant. is blinking... hmmm oh wait LFO 2 isn't enabled!)
im not getting the QUANT thing myself. clock goes into Pitch2, what is going into Mod A, trying to recreate that demo so i know whats going on...and all i get is garbage
if you want to clock lfo2 (osc2) you have to change the sync mode to off for o2 otherwise lfo2 wil track osc1 and not the clock you have inserted into pitch2
Yes, if you scroll one step left after hitting chord mode, or scroll all the way to the right you should see an * before the chord name. This means that MOD B is now controlling the selected chord so you can set it either with the MOD B knob or the MOD B CV input.
For some reason when i try to sequence chord types with a sequencer, the higher cv added to mod b (to get chord types later in the list), the more strange the detune gets.. if i want a chord type near the end of the list with cv it sounds awful.. anyone else getting this? Any solutions?
There's 2 randomization modes while Preset Mode is active: RndP and RndS. RndP randomly selects a preset each time a gate is received at the SYNC/TRIG input, RndS randomizes all settings each time a gate is received at the SYNC/TRIG input. ModA can also be set to PrstStep to free up the SYNC/TRIG input. At 3:05 I demonstrate RndS mode.
hey intellijel, at the risk of coming off like a moron, could you detail out what you did to get that sound in the QUANT delay portion of the vid? 1:35 when i try to do it, it sounds horrible.
intellijel ah...well that explains its. I was reading it as a pulse had to go in mod a as well. No wonder it wasnt werking. So thats not a sound from SS, its just being used as a delay. Where is it described, other than prst98 that mod a becomes an audio input. Is this detailed in the manual. Or is there somewhere else where this is clearer. are there other updates that could use a little more clarity. Or am i just thick. Thanks for the help! I wanna try this. Your demo is great. Again the update is great!
Sorry for the delayed reply TRaddcliff! No, it's not described very clearly in the manual, but if you check the MOD A options, selecting COMBO1 uses the MOD A input to feed the COMBO function instead of OSC1. This effectively uses MOD A as an audio input to instead of OSC1. With QUANT. flashing from being pressed twice, PITCH2 becomes a clock input and RATIO sets the clock division. Then you can set the amount of delay feedback under DELAY DEPTH and press it again to toggle using MODB to control feedback. I'm not 100% sure, but I think I was using Plonk as the sound source to the MODA input.
You just press the CHORD button, then press CHORD MODE and scroll to select the desired chord. Pressing CHORD DETUNE and adding a slight amount can really fatten it up nicely. I find I usually like between 3 - 15.
@@rolfdubbeld Sorry, I meant the CHORD MODE button to activate chord mode, then CHORD TYPE (the bottom of the left 4 white buttons also labelled MULTI/LOAD) to select the desired chord.
@@ScottMFR Thanks for the help, but I think my module is damaged, no way I get these nice sounds. I get some modular distorted sound. Strange many other features work
@@rolfdubbeld Having the MOD A attenuator up is a common user error that makes people think there's something wrong with their unit. If you think something is faulty you should reach out to support@intellijel.com
Would you consider adding possibilty for the coarse knob position also to be memorized as preset, sometime in the future updates? I know that is useful for the fundamental pitch to be unaffected when, for example, user wants to scroll trough presets while melodic sequence is controling the pitch, but sometimes "coarse" knob functions more as a timbre parameter rather than musical pitch (especially when taking advantage of atonal ratios of various combo modes this module provides), so it woukd be useful to have option of saving it within preset as well... And for those who use it for determining fundamental pitch, it would also allow for making preset sequencing work for making melodies, or for making monophonic rhythms in a percussion mode (switching sequentially between high and low register percussion sounds). I hope i make sense...
thank you for the update! its GREAT. you addressed a couple things i was hoping for too!
again thank you!
I hope that soon there will be a Shapeshifter mk2 version
Great help, cheers!
Oh man, thanks for making this vid. Huge help! Question/comment on the "Pressing QUANT. twice to make PITCH 2 In become a clock in for Osc Two while in LFO Mode" - when in the blicking QUANT mode, PITCH 2 seems to be a clock in for Osc 2 even if it is NOT in LFO mode. Not sure if this is a documentation mistake or an implementation mistake. I actually prefer it the way it is since that would just be one too many things to keep track of (Why is Osc 2 not acting as a clocked LFO? Quant. is blinking... hmmm oh wait LFO 2 isn't enabled!)
im not getting the QUANT thing myself. clock goes into Pitch2, what is going into Mod A, trying to recreate that demo so i know whats going on...and all i get is garbage
MODA should be set to COMBO1 in order for it to be used as an audio input to replace OSC1.
if you want to clock lfo2 (osc2) you have to change the sync mode to off for o2 otherwise lfo2 wil track osc1 and not the clock you have inserted into pitch2
Is it possible to change chords. Ex. Moving from minor to major chords with external gear?
Yes, if you scroll one step left after hitting chord mode, or scroll all the way to the right you should see an * before the chord name. This means that MOD B is now controlling the selected chord so you can set it either with the MOD B knob or the MOD B CV input.
For some reason when i try to sequence chord types with a sequencer, the higher cv added to mod b (to get chord types later in the list), the more strange the detune gets.. if i want a chord type near the end of the list with cv it sounds awful.. anyone else getting this? Any solutions?
Make sure you aren't also modulating the detune parameter with mod b (just tap the detune button until you see detu: XX instead of dt:XX+YY)
Maybe a GOOD manual would be a good idea.
Is there a way to randomise all functions with CV, or just present cycling?
There's 2 randomization modes while Preset Mode is active: RndP and RndS. RndP randomly selects a preset each time a gate is received at the SYNC/TRIG input, RndS randomizes all settings each time a gate is received at the SYNC/TRIG input. ModA can also be set to PrstStep to free up the SYNC/TRIG input.
At 3:05 I demonstrate RndS mode.
ScottMFR oh yes... For some reason I completely missed that. Amazing depth to this oscillator.
Yeah, no kidding! You can keep learning new things for a long time with it...
hey intellijel, at the risk of coming off like a moron, could you detail out what you did to get that sound in the QUANT delay portion of the vid? 1:35
when i try to do it, it sounds horrible.
intellijel i did that. It was not werking as demonstrated. What do you have going into mod a
intellijel ah...well that explains its. I was reading it as a pulse had to go in mod a as well. No wonder it wasnt werking. So thats not a sound from SS, its just being used as a delay. Where is it described, other than prst98 that mod a becomes an audio input.
Is this detailed in the manual. Or is there somewhere else where this is clearer.
are there other updates that could use a little more clarity. Or am i just thick.
Thanks for the help!
I wanna try this. Your demo is great. Again the update is great!
Sorry for the delayed reply TRaddcliff!
No, it's not described very clearly in the manual, but if you check the MOD A options, selecting COMBO1 uses the MOD A input to feed the COMBO function instead of OSC1. This effectively uses MOD A as an audio input to instead of OSC1. With QUANT. flashing from being pressed twice, PITCH2 becomes a clock input and RATIO sets the clock division. Then you can set the amount of delay feedback under DELAY DEPTH and press it again to toggle using MODB to control feedback.
I'm not 100% sure, but I think I was using Plonk as the sound source to the MODA input.
For a beginner it's totally unclear how to get the nice Chords out of OSC1
You just press the CHORD button, then press CHORD MODE and scroll to select the desired chord. Pressing CHORD DETUNE and adding a slight amount can really fatten it up nicely. I find I usually like between 3 - 15.
@@ScottMFR I can find the small black CHORD MODE button, between Coarse and Shape2. But were is the CHORD button ?. It seems there are two buttons ?
@@rolfdubbeld Sorry, I meant the CHORD MODE button to activate chord mode, then CHORD TYPE (the bottom of the left 4 white buttons also labelled MULTI/LOAD) to select the desired chord.
@@ScottMFR Thanks for the help, but I think my module is damaged, no way I get these nice sounds. I get some modular distorted sound. Strange many other features work
@@rolfdubbeld Having the MOD A attenuator up is a common user error that makes people think there's something wrong with their unit. If you think something is faulty you should reach out to support@intellijel.com
Here it is in use with clouds, can you find it? : soundcloud.com/manot-brgr/mod-1
Great update TY