-
Notifications
You must be signed in to change notification settings - Fork 78
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
Allow tidal to query superdirt for a list of samples / synths / effects? #199
Comments
FWIW, on the SuperDirt end of things you can get samples, effects, and global effects with something like
I expected
to list all the "synth" instruments but they don't seem to show up here, maybe I'm not registering them properly? Usually I just make a SynthDef, and I think SuperDirt doesn't necessarily keep a lookup of every SynthDef since many of them may have nothing to do with SuperDIrt. In the past to try to find all the "synths" I've defined I use this, but I think it may still grab things that are unrelated to SuperDirt
|
Yes, defining a synth event is optional, you just do it when you need specific parameters or transformations of parameters. The rest is just normal SynthDefs. As you show, you can easily get a list of all SynthDefs ( So some explicit bookkeeping is necessary for this. |
This is related to tidalcycles/Dirt-Samples#15 then. A general way of cataloguing samples and synths metadata, including #122 . |
I'm talking with @lwlsn about this sort of thing.. Particularly how to make use of metadata about samples in Tidal patterns. E.g. lets say I had a folder of short sounds, and wanted to play them in order of 'brightness':
This could make use of pre-calculated (or calculated on-the-fly and cached) sound analysis data stored in a different yaml file for each sample. There's different ways of achieving this..
We're leaning towards the first option, as in some ways the most flexible, and probably easiest to implement (at least for me as someone less sclang proficient), but perhaps more than one approach could be taken. |
for sound analysis, tidal could use supercollider as engine, and write the data to disk which can then used following your first suggestion. Then it is up to everyone on what side they want to use the data, so you could also read them from sclang. |
These would be the potential sources for information:
It seems to me the question how we want to account for this open ended information. Should it be user extendable or is it fixed? |
As per this forum thread, it would be nice for tidal to be able to now the duration of each sample, so that it could timeshift it so that it ends, rather than starts at a certain point. This raises a couple of questions
The first option implies that Tidal is on the same host as SuperDirt, which might not be the case. The second option seems better, and perhaps with all such info coming from metadata files - then we could e.g. 'trim off' trailing silence from samples from freesound.org based on that metadata. |
The direct implementation of 2. is of course very easy. The question is – if tidal wants to inspect any data that is in the Questions:
|
We now have the
rms
capability, could we add a way for tidal to ask which samples / synths are available? Maybe effects too?The text was updated successfully, but these errors were encountered: