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

a hack to feed audio from MIDI or VST back into SuperDirt #262

Open
wants to merge 32 commits into
base: develop
Choose a base branch
from

Conversation

kasparsj
Copy link

@kasparsj kasparsj commented Mar 2, 2022

Hi, not sure how useful this is for others, but I tought I had share this SuperDirt MIDI hack.
It basically gives more control over MIDI instruments (hardware and VST) from TidalCycles, by feeding the audio back into the orbit, so that effects/panning can be applied.

@telephon
Copy link
Contributor

telephon commented Mar 2, 2022

Thank you! I think there is no need to make the changes to the class interface. One DirtSoundLibrary can be shared between several instances of SuperDirt.

You can reach the current orbit and the server from within the play function of a synth event, and using the playInside function field, you are passed the DirtEvent (see hacks/function-hacks.scd there are examples that might help)

Or is there something that can't be realised that way?

@kasparsj
Copy link
Author

kasparsj commented Mar 3, 2022

Thank you! I think there is no need to make the changes to the class interface. One DirtSoundLibrary can be shared between several instances of SuperDirt.

You can reach the current orbit and the server from within the play function of a synth event, and using the playInside function field, you are passed the DirtEvent (see hacks/function-hacks.scd there are examples that might help)

Or is there something that can't be realised that way?

Thanks for the comments. Yes, that makes sense. I have updated the hack accordingly. Just 1 little change to DirtEvent class now required.

@telephon
Copy link
Contributor

telephon commented Mar 4, 2022

Ah yes, very much better. Let me know when you need another round of comments.

@telephon
Copy link
Contributor

@kasparsj sorry for not responding – I forgot about it. This is interesting, I would like to find a less intrusive way to do it. I suppose that the best way to run VST Plugins would be in global effects, because they do not need to be started at each onset. But I don't understand everything you are doing here …

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

Successfully merging this pull request may close these issues.

2 participants