Eloquencer V1.3.0 Firmware Update
I found a easy way to reproduce the bug :
In CV key rec mode, hit some keys except a C or in a user scale without a C .You have to record in two or more loops of the track. It will record some ties. Go to gate & tie and remove the ties. C1 apperars on the track.
I haven't understood the "rule" of the bug yet.
I hope it will help
And, as you say, an otpion to decide for longer notes or not would be great.
Now I understand ! Create a TIE requires a start step, and an end step. If you record a sequence and then you remove the TIE in the first step, the step that is supposed to end the track is still there, so you have to remove it too.
I will try to add the option so this behavior can be avoided.
Is there a manual for v1.3.2?
Thanks for the updates!
Hi Multigrooves !
It is the same as 1.3.0
I have release a new version
It solves a couple of bugs. External clock unsynced with long pulses (responding to fall not to rise), no possibility to change the CV step value with tempos <60bpm
Additionally we have added a couple of things that you suggested. Option to enable/disable the TIE record, show the current pattern while being in LIVE REC mode.
Link please 🖐️
New version installed. All works perfectly.
Great job !
Hello forum! Thanks again to Winter Modular for the massive firmware update and all the hard work.
Possible bug or is this the new way
: it seems the CV inputs and assigning Rachets has changed. Previous to the new firmware, you didn't have to manually set Rachet Probability per track after assigning Rachet to the CV input. Now it seems you have to.
Before I simply assigned CV2 input to Rachet to say all Tracks in the menu, without having to press the Rachet button and set probability.
Now when I assign ratcheting to either CV input via the Mod selection, nothing happens until I additionally set the probability by also pressing the rachet button.
Bug or new way ?
Hello sunfalls !
Thanks to you and all the user that keep that thing going giving ideas and feedback!
When I first read your message I didn't understood and I thought that it was a bug. But reading a second time, if I'm understanding it right, I think it is the normal behavior. When you start a blank project the RP (ratcheting probability) is at 100%, so as soon you assign the CV input to Ratcheting (and a group of tracks) the value of ratcheting will change in relation of incoming CV. I have downgrade my Eloquencer to 1.2.0 and tested it, and I think the behavior is the same.
is there an option to prevent sending Midi-Clock from input to output if in midi clock slave mode?
I didn't find, please implement to if it's not existing to prevent midi loops.
Hi @digi , it is not possible right now.
Makes sense, I put it on the list 🙂
thanks for the feedback!
i think the individual track multiplier would be an awesome addition to the sequencer. At least twice the speed for fast arpeggios 🙂
Thx for this massive update, keep up the good work.
Now we can control others midi devices, it would be awesome to be able to do at least one polyphonic track to send to a poly midi synth.