-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal routing of gates and CV signals between engines #108
Comments
yes that would be great ! so no need to use the IO the outputs specially to save them for stereo proccesing . |
I have just pushed an update. In addition to the hardware inputs T1-T4 & C1-T4, internal outputs $1-$9 can now be selected as SRC everywhere. In the modulations, e.g. it is now possible to control the EF modulation with the audio signal of another engine. Each engine has two signals, the first $1,$2, the second $3,$4 etc. As for the naming, I couldn't think of anything better. There had to be a maximum of 2 letters so that the texts fit in everywhere. The whole thing is even more complex now, I hope it's not too complicated for beginners. In between I only have the clock on the T1, and use the SEQ/Rythm to trigger the drums... |
@eh2k thanks a lot dear ! |
Awesome! @eh2k
Wouldn't be more logical to do A1, A2, B1, B2...?
For sure $ won't say anything to a new user without a manual. |
thanks for your feedback.
This is really what would make sense as the next step after the introduction of the SEQ engines. I've already tried it out, but I wanted to take it one step at a time.
At the moment, the entire clocking is not stable or synchronised in all cases. Sometimes the MIDI clock and reset triggers do not quite match. I am still optimising and testing this.
The text was updated successfully, but these errors were encountered: