Skip to content
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

Open
eh2k opened this issue Nov 18, 2024 · 4 comments
Open

Internal routing of gates and CV signals between engines #108

eh2k opened this issue Nov 18, 2024 · 4 comments

Comments

@eh2k
Copy link
Owner

eh2k commented Nov 18, 2024

@koswir mentioned here: #100 (comment)

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.

@rootapprox
Copy link

yes that would be great ! so no need to use the IO the outputs specially to save them for stereo proccesing .

eh2k added a commit that referenced this issue Nov 30, 2024
eh2k added a commit that referenced this issue Nov 30, 2024
@eh2k
Copy link
Owner Author

eh2k commented Nov 30, 2024

@koswir @rootapprox

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...

@rootapprox
Copy link

@eh2k thanks a lot dear !
i will try it now and report if anything .
I hope you fixed storing patches and loading them problem,
Cheers!

eh2k added a commit that referenced this issue Nov 30, 2024
@koswir
Copy link

koswir commented Dec 2, 2024

Awesome! @eh2k
I haven't tested it yet, but I have a thought about this:

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.

Wouldn't be more logical to do A1, A2, B1, B2...?
I see the problem with C but honestly I always find C kinda confusing - maybe V like volts could be easier to understand?

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...

For sure $ won't say anything to a new user without a manual.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants