Specify sample name about dirt HOT 3 OPEN

Just a comment, not sure if this is constructive....

When writing and composing with Tidal, to ensure that my code uses the same
samples all the time, I usually make a new sample folder dedicated to a
single "song" or project. In other words, my live improvisation sample
library does not match a studio project sample library. I personally expect
my live sample library to be very fluid and would break my projects, so
that's why I do it. This per-project approach uses a lot more disk space,
but it also keeps me sane. After a project is done, I archive the code with
the samples.

I could see how the "bd>filename.wav" approach could be useful for writing
and composing. Seems like it would be very difficult for live improvisation
though. No way I could remember all those file names!

On Wed, Apr 20, 2016 at 8:06 AM, Alessandro Annini <[email protected]

wrote:

In order to better maintain performer work i suggest to add a simple,
optional notation when loading samples:

the current one:

d1 $ sound "bd:1"

the new one:

d1 $ sound "bd>filename.wav"

Those methods can coexist but this way when we add a new sample no
revision of the .tidal file is needed in order to use the previous sounds

Another solution could be specify the root directory for the samples so it
can be shifted on the fly to another soundbank

Thanks

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#51

from dirt.

Thanks @kindohm for sharing your point of view,
I think that giving a meaningful name even during a live impro is easier to pick the right sound but maybe it's just me, i perfectly understand that this can be opinionated.
Anyway i see no harm in giving the chance to use any other notation as long as it is rigorously optional (it couldn't be another way or every project would be ruined)
This way every performer can choose what's the best for himself

from dirt.

Why not set up a different function sounda (sound absolute path) to take in an absolute path of a filename ? That way there's no pollution of functionality ?

from dirt.