OK, what about this:
An additional arpeggiator mode called something like “smartarp.” The selected arpeggio pattern will not activate unless there is more than one note to play, ie. an octave range greater than 1 is selected and/or more than 1 incoming MIDI note is played.
This is how the arpeggiator works by default on another synth I’ve used and I’ve found it very useful for playing basslines and leads, then sneaking some arps in there by playing a chord.
Is there anyway to display the original parameter of a patch (the saved parameter) while the parameter value is being edited? Is there room on the LCD for it, or could the value displayed alternate between original/new in a way that makes sense?
I like this feature on other synths that I have.
@herrprof: what would happen before the arp starts to kick in? It’s not a polysynth…
@titus: the shruthi has only one editing buffer, so it’s not possible to keep in memory both the “actual” patch, and a copy of the preset.
@pichenettes: is there enough room somewhere to temporarily store the preset value for the currently selected parameter and display that during editing somehow?
You would not need to buffer the whole preset, just each time a new parameter is changed fetch that parameter value from the preset then dump it and move on…
EEPROM communication is blocking, so the CPU freezes and audio playback is interrupted for 1 or 2 ms when a preset is loaded. You don’t want that to happen all the time.
Have you tried using the LFO > envelope sync? The custom LFO waveforms? Processing a LFO through an operator? You can get something close to that through those approaches…
@curbsitter: the filter mode switch in the 4PM is noisy and clicky – by design. There are better switches than the 4051 / 4053, but they are hard to source / expensive / available only in SMT or a combination of all. So even if you get a CC for that, it won’t mean you’ll be able to sequence it. It’ll work but sound glitchy.
“gwaidan 1 day ago
One suggestion-the current system (0.96) resets channel volume whenever a patch is changed-if you’re using MIDI channel volume to manage output levels then this is a bit of a pain as you have to wiggle the external MIDI volume fader to resend volume levels each time you change a patch. Would it be possible for the next OS version to remember the most recently received channel volume level whenever patches are changed?”
+1
This is not possible without a lot of work.
I thought the midipal could do this. Or is that just clock division?
The MIDIpal does only division, no PLL.
Hmm, OK thanks everyone, I think I’ll have to do this with an external sequencer then. Time to finish my MBSEQv4! :)
@loderbast: I only use computers for recording nowadays, and I don’t really want to go back to making music on the computer again. PD is very nice though, I should play around with it again some time :)
Back to the original question : What do you mean by tempo? The arpeggiator already lets you 2 * the bpm tempo to get 8th notes rather than quarter notes. This doesn’t require a PLL for the midi timeclock as presumably its just triggering at half of the 24ppqn rate – or every 12th pulse.
presumably at the expense of some of the other BPM rates, a *4 and *8 could be added in a custom built firmware version if you wanted to do that. As long as they are based off of the 24ppqn midi clock pulses
The external clock is 24ppqn. The BPM/arpeggiator needs pulses at 4 ppqn. You can thus do x2 without PLL (8 is a divisor of 24), and there is already the x2 option; but you cannot do x4 without PLL because 16 is not a divisor of 24, qed. x3 and x6 could be done without PLL.
Of course. There are 16 steps per bar already without any tempo multiplication. Sorry for confusing things.
+1 CC out!
Just the envelope attack thing.
Any feature that requires new parameters are doomed because a/ the patch datastructure is fulled and this will break the patch format if it is changed (so you’ll have to piggyback on existing params, and it’s hard to do for a 3rd envelope) : b/ seriously, you don’t find the UI too crowded?
You can already control the FM index in the mod matrix, what do you have in mind about FM?
I have a maybe weird questIon. I use the shruthi together with an urzwerg sequencer. I would like to able to use the duo mode on 2 separate sequences. That would require the 2 oscillators to have 2 different midi channels.
I understand if it is a to weird one trick pony future to implement and i should just build another shruthi.
Parameter display hack is in 0.97 beta and will be kept.
@shiftr: the Shruthi-1 was designed to be a monosynth, mono-part synth. All those assumptions are hard-coded. The workaround for the pseudo duophony is not pretty, and I don’t want to do the other modifications. Maybe you could use a MIDI channel remapper from the Urzwerg output to route both tracks to the Shruthi-1 ; or maybe just but the Shruthi-1 in omni mode?
Why should omni-mode be different from merging the two channels together?
The urzwerg sends midi on 4 adjacent channels. So putting it in omni mode will send 4 different sequences sort of randomly to the 2 oscillators. I normally use 2 tracks on the urzwerg for drums. So merging only 2 channels will make the shruthi react only to the firsth 2 sequences. But the 4 sequences together still might be cool!
It looks like you're new here. If you want to get involved, click one of these buttons!