Specify sample name

[AlessandroAnnini]

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

[kindohm]

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 <notifications@github.com

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

[AlessandroAnnini]

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

[john-d-murphy]

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 ?

[claudeha]

I just pushed commit f065a53 to the 1.1-dev branch that should fix this:

allow specifying paths in sample names

if a sample name contains a '/', it will be treated as a path (and no index added), otherwise previous search algorithm applies

paths can be relative (to the samples root directory) or fully absolute paths (with leading '/'), but they must resolve inside the samples root directory unless the flag --allow-unsafe-sample-paths is enabled (in which case any file on the system can be accessed)

path resolution is done with realpath() (POSIX 2008 variant)

note: not yet tested on Windows or Android

examples for Tidal and similar (use pure to make a pattern of strings instead of invoking mininotation parser):

s (pure "bd") # n "6"                -- searched as before
s (pure "bd/BT3A0D0.wav")                      -- relative
s (pure "../samples/bd/BT3A0D0.wav")           -- relative
s (pure "/media/Dirt-samples/bd/BT3A0D0.wav")  -- absolute

this works as expected on Debian Linux sending messages from my Tidal-ish system Godwit, haven't tested original Tidal

Leaving the issue open until it's been tested on Android (it now works in Wine with some later commits so Windows might be ok).