Hi Guys. I need some help with this
In the first video, I map Transit to a CV generator switching phases on Entrian Melody. Then I map to the sequence select on Impromptu Foundry. Transit snapshots 1 to 12 correspond with phases 1 - 12 in Entrian and sequence 1 - 12 in Foundry. I am shifting using Midi-Gate trigging the transit snapshots to move forward.
In the second video is the problem. I hope you can see with the resolution. But, the numbers are off as soon and I start moving through snapshots (SS). For example, SS 1 and 2 are now both phase 3 on Entrian and all the ss seem to have shifted forward one. The last ss shows 11 on Foundry sequence when it should be 12.
This is a good example of what happens, but it has gone wild. Showing sequence numbers like 46 and 23, when I have not even mapped those numbers.
I think it has something to do with the way these knobs are valued. I’m not an expert. Also, it does not seem to happen on mute switches. Something about these types of knobs.
Any ideas and help would be greatly appreciated.
To be honest, TRANSIT is the wrong tool for your purpose. It is not designed to be used for that and it is kind of counter-intuitive to map it to a knob for generating a specific voltage.
Why don’t you sequence the Entrian module directly from Foundry? Or the other way around, sequence Foundry using the Entrian module? Or any other sequencer which outputs quantized voltages?
Quantised voltages eh? Sound promising.
My goal is to have a one button system to shift phases and settings in all modules. Honestly, I am not a fan of song modes, as I prefer to record tacks by moving things myself live and naturally. I was hoping to achieve this first with 8Face, then with Transit.
Maybe using VCV Quanitzer may help in this setup?
Thanks so much for your help.
Try this one, it should help:
Some things to think about:
- Foundry’s CV2, SEQ and PHRASE knobs are infinite encoders (differential encoders), so there is no precise absolute knob position correspondance to the internal number we’re trying to control
- for Foundry you might get better results using the Foundry expander’s CV inputs
- as Ben said, your approach is probably more trouble than it’s worth and perhaps you can get better if you use the modules’ built-in song modes; they might take a bit longer to learn, but they might work better
Excellent info. Thanks a million. mapping infinite encoders sounds like the issue here.