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

Separate midi configs for multiple instances #18

Open
1 task
mattorp opened this issue Nov 3, 2021 · 0 comments
Open
1 task

Separate midi configs for multiple instances #18

mattorp opened this issue Nov 3, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@mattorp
Copy link
Owner

mattorp commented Nov 3, 2021

make it easy to store midi configs for multiple instances running in parallel and have each instance have its own default. as it is now on mac, a backup needs to be imported to each 2nd instance. would be good to decouple saving the midi configs from the backup process as well, to make file management easier

by: yroc

https://discord.com/channels/729824270913503374/752022203205287936/754907077448564796

Note: Team Syn is working on official multi shader support: https://discord.com/channels/729824270913503374/752022203205287936/755627072176783481

Workarounds

(Windows) Script to launch two instances of Synesthesia with two sets of MIDI bindings by @headstash:
https://gist.github.com/headstash/242a61afeefc5c477c70cf4a31f41e27

This should also be doable with https://github.com/mattorp/syn-server if midi capture is implemented, https://github.com/mattorp/syn-server/issues/6

Then each instance can listen to individual virtual devices, that have custom mappings to them. Compared to pointing to separate binding files, this allows dynamic updating after the instances have launched. Even if Syn will support multiple shaders, custom routing to instances should allow some creative solutions.

@mattorp mattorp added the enhancement New feature or request label Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant