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

Accessing to a single SuperDirt instance/node #87

Closed
cannc4 opened this issue May 23, 2018 · 4 comments
Closed

Accessing to a single SuperDirt instance/node #87

cannc4 opened this issue May 23, 2018 · 4 comments

Comments

@cannc4
Copy link

cannc4 commented May 23, 2018

The idea is to control a synth from SuperCollider while using Tidal.
Usually in SC, I store Synth_ids to be able to change the parameters on the fly without having to re-allocate the voice. e.g syntharray[0].set(\coarse, 2);

Is there any way to access the synth_ids within the sclang?
If I can access globaleffect_ids, that would be super useful too.

@telephon
Copy link
Contributor

There is no place where dirt stores any synth ids (for efficiency), apart from the global effects ones.

But, maybe this is what you want:

  • set the synth parameters of a dirt orbit by ~dirt.orbits[0].set(\paramname, param, \paramname2, param2 ...)
  • set the parameters of global effects of an orbit by ~dirt.orbits[0].setGlobalEffects(\paramname, param, \paramname2, param2 ...).

@cannc4
Copy link
Author

cannc4 commented May 24, 2018

That makes sense.
Will definitely explore .setGlobalEffects
What's the scope of the ~dirt.orbits[0].set? All the synth params going through the specified orbit?

@telephon
Copy link
Contributor

telephon commented May 25, 2018

What's the scope of the ~dirt.orbits[0].set? All the synth params going through the specified orbit?

yes. They will be overridden from tidal, if you send them. You can use functions as parameter value if you want something to be called at each event.

@telephon
Copy link
Contributor

(just closed because this is not really an issue)

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

No branches or pull requests

2 participants