Another Feature Request or Expansion Question...
Hi there, I hope this is an appropriate place to request features in new firmware, or ask about expanders.
I've built a drum machine within my case. 8 tracks runs out pretty quickly for me with four oscillators, 3 drums, and an 8-track sampler. I started looking at adding a Metron but it just seems ridiculous. Any plan for firmware + expander since the new drum machine was released? I know the Eloquencer and I don't want to add another machine.
Hi @davedied !
It is the place 🙂
Do you mean if there is any plan to add a new expander that will add more outputs / tracks ? or if there will be more firmware updates in the future ?
Since we are talking about extra features, here are some that I would like 🙂
1. CVP input
The manual says that the voltage will be added to the curret CV variation probability, but from my testing this doesn't seem to be what it's doing. The voltage at the input replaces whatever probability is set in the sequencer. Is this a bug or is this a mistake in the manual?
Anyway, I think that screen could be used to give a better feedback of what is happening when using the CVP or any other probability cv input. I would change it so that when looking at the probability page, the bars for each step should
- all be replaced by a single number if the CV value replaces the internal value or
- change height if the CV value is added to the internal value
Also, if we set both inputs to the same parameter and the same channel, the eloquencer ignores CV2 and only uses CV1. I think that the interface should prevent you from doing that by greying out or marquing by an X the channels that are already being modulated
2. Mute Bin
If both CV inputs are set to mute bin, only CV2 works, even if the CV inputs are assigned to different tracks. I don't have any use for this personaly, but it feels like a bug.
3. Many CV inputs parameters can't be assigned to tracks
NONE, PREV PATT, NEXT PATT, PREV PART, NEXT PART and PATT CHANGE can all be assigned to specific tracks, even if it doesn't make any sense for those parameters. This doesn't effect the behavior of the eloquencer but it makes for a messier interface. I think track assignment should be removed for those parameters.
4. PATTERN CHANGE using cv
Once you use CV to select which pattern to play, pattern mode isn't really usefull anymore. Trying to move to another pattern will breifly change the next pattern on the screen and revert back to the pattern selecting by the cv input. I would change it so that when PATTERN CHANGE via cv is used, pressing a pattern would change the pattern to edit instead of trying to change the pattern in play.
5. Part change at the end of the part doesn't seem to work?
When I am in play parts mode, the parts always change at the end of the current pattern, no matter the option that I selected for Part change. Maybe I'm doing something wrong but I can't tell
6. PART CHANGE using cv (pls)
I really would like to change Parts via cv the same way that PATTERN CHANGE via cv works. This would open so many doors in my opinion. Pattern via cv is already powerfull but parts via cv would be next level.
7. So many cool features that are only available using CC values!
There are so many parameters that can be changed by CC values buy not by the CV inputs, such as
- Track lenght start and stop
- Step mode
- Step mode rep
- All the LFO parameters
- Randomising 1 or 3 layers
- Freeze and Revert
And I am sure I am missing a few
I really would like to have acces to those without having to buy CV to MIDI converter and then using the EME to make it work.
8. CV input expander
As you can probably tell by now, I'm a big fan of the controlling the eloquencer via CV, and two inputs just isn't enough (for me anyways haha)! I am already using MUTE BIN and PATT CHANGE all the time, and I would really like to have acces to more.
I my wildest dream I would like another expander similar to the EME : 6hp with four custom buttons, but with something like 10(!) extra CV inputs instead of the midi connections.
Thanks for reading through all this! I hope I was clear
Hi @vefjvexen !
Thanks for the exhaustive and detailed feedback ! 🙂
1) Wow, I'm not sure but I think you are the first one to notice this 😲 , it should work as an addition but it does not. Will note it for an upcoming FW release.
Regarding the feedback. During design phase we discussed the possibility to show the CV IN variations in the step edition displays (the bars), but at the end as those are values that add an amount to the nominal value, it does not make sense to modify the visualization of the nominal value. In other cases that the nominal value is modified the bars change, an example could be when you modify a parameter using a MIDI controller ( EME is needed).
Some CV input parameters follow a priority when one parameter is assigned to both inputs.
2) Similar to the question above.
4) Makes sense
5) Need to check this one, you are not the first to ask, but it must be some parameter that changes the behaviour because I wasn't able to reproduce it consistently.
6) Will study, it is partially implemented to work with EME (where the custom buttons can be used to do next_part previous_part)
7) I know, someone could think it is a commercial strategy to make you buy the EME :), but it is not ! I promise.
It is just a question of time. Will study the possibility to add some of them for the next FW update.
8) I think I don't feel well, I think I'm dizzy 🤣 Joking apart, that was one of the original future uses when I decided to add the SV1 and SV2 expansion ports.
Thanks again for the detailed and useful feedback, I will try to add those mentioned in the next FW update, regarding this it has been a while since I have to release a FW update but working on the new module ZAPS have consume all my time. I expect that after Zaps release (1st quarter 22) I will focus on the fw update.
@wintermodular Hi, thank you for the reply! I'm wondering if there will be an expander for drum triggers. I use a Squid Salmple and love it paired with the Eloquencer. But there are eight tracks and the Eloquencer has eight gates out. If I was to use all eight gates for the sampler I cannot use anymore voices in my rack. I have three voices in my rack... So I wonder if you will add a trigger expander to pair with the new drum module you just released? That way we can use few voices alongside the drums etc.
Thanks for the time!
Hi to the forum,
as I don't know if it is appropriate to open a new topic I just hook up here with a feature request/question.
Would it be possible to implement a sub-step feature where you have, let's say 8 sub-steps per step? I am thinking here in gate context, not in CV context.
It could be attached to the ratcheting-menu? This would enhance the ability for complex and more natural rhythms.
I am excited to hear from you.
@gish-gallop You can open as many topics as you need.
It is not on the roadmap right now, it could make the interface far more complicated that just ratcheting configuration.
The only workaround is to increase the clock and use patterns as steps, and then chain them using 'quick pattern chain' or song parts. For example: use 16 8-step-length patterns and chain it in a song part