hi i want to play a long sound file and while it is playing, be able to cut it in several parts that i later can load/play on tables. the way i would do it is to arbitrarily record stuff onto tables whenever i want to "cut" one of these sections. but i need an effective, smart and modular approach to the many tables situation (ie i dont know how many of these cuts i wanna make, so i should be able to create tables on the fly), i reckon using variables in the tables names. i bet there is a good example somewhere, but i could not find it. help?
Hi,
On Mon, May 17, 2010 at 04:53:22PM +0200, PF wrote:
i want to play a long sound file and while it is playing, be able to cut it in several parts that i later can load/play on tables. the way i would do it is to arbitrarily record stuff onto tables whenever i want to "cut" one of these sections.
If the file is played from a table, you could alternatively register the sample locations that you are playing, which is much cheaper to do that copying around table data.
Then later you can still save the sections with [soundfiler] by using the "-skip" and "-nframes" options with your registered numbers.
If the file you are playing is too big for a table and you are playing with readsf~ or so, then you could still register locations. Alternatively just record chopped sections with writesf~ and name files with numbers counting up or so. Creating tables dynamically is a bit of a pain that I would avoid here.
Ciao
Frank Barknecht Do You RjDj.me? _ ______footils.org__
If the file you are playing is too big for a table and you are playing with readsf~ or so, then you could still register locations. Alternatively just record chopped sections with writesf~ and name files with numbers counting up
it will be quite large, so readsf~ might be the better way out. thanks, frank.
or so. Creating tables dynamically is a bit of a pain that I would avoid here.
even if it's not perfect for this, i wouldnt mind if someone can point me to some examples of dynamic tables. thanks, ----pf
On Tue, May 18, 2010 at 03:33:38AM +0200, PF wrote:
If the file you are playing is too big for a table and you are playing with readsf~ or so, then you could still register locations. Alternatively just record chopped sections with writesf~ and name files with numbers counting up
it will be quite large, so readsf~ might be the better way out. thanks, frank.
or so. Creating tables dynamically is a bit of a pain that I would avoid here.
even if it's not perfect for this, i wouldnt mind if someone can point me to some examples of dynamic tables.
You create them with the "usual" dynamic patching approach: Send an "obj"-creation-message to a subpatch-receiver like this:
[obj 10 20 table tablename( | [s pd-$0-subpatch]
[pd $0-subpatch]
Replace "tablename" with for example "$1-tablename" and feed it with a number to create more tables, probably you will also want to change the y-coordinate accordingly to something like like 20*<tablenumber>.
Ciao
Frank Barknecht Do You RjDj.me? _ ______footils.org__
Frank Barknecht wrote:
On Tue, May 18, 2010 at 03:33:38AM +0200, PF wrote:
If the file you are playing is too big for a table and you are playing with readsf~ or so, then you could still register locations. Alternatively just record chopped sections with writesf~ and name files with numbers counting up
it will be quite large, so readsf~ might be the better way out. thanks, frank.
or so. Creating tables dynamically is a bit of a pain that I would avoid here.
even if it's not perfect for this, i wouldnt mind if someone can point me to some examples of dynamic tables.
You create them with the "usual" dynamic patching approach: Send an "obj"-creation-message to a subpatch-receiver like this:
[obj 10 20 table tablename( | [s pd-$0-subpatch]
[pd $0-subpatch]
Replace "tablename" with for example "$1-tablename" and feed it with a number to create more tables, probably you will also want to change the y-coordinate accordingly to something like like 20*<tablenumber>.
Another approach could be to simply append samples in one big table and save the indexes. (but this depends a lot on how many chopped samples and how long they are)
I've used a similar approach for a piece where I wanted to trigger certain samples: in that case the 'chunks' were small files already existed on disk, but I wouldn't have known how many files I would have finally, so using a fixed number of tables wouldn't have worked. I can point you to the piece and share the patches if you are interested.
Kind regards, Lorenzo.
Ciao
Am 17.05.2010 um 17:18 schrieb Frank Barknecht:
On Mon, May 17, 2010 at 04:53:22PM +0200, PF wrote:
i want to play a long sound file and while it is playing, be able to cut it in several parts that i later can load/play on tables. the way i would do it is to arbitrarily record stuff onto tables whenever i want to "cut" one of these sections.
If the file is played from a table, you could alternatively register the sample locations that you are playing, which is much cheaper to do that copying around table data.
let's say you are storing the snippets of the wave in the form <index> <startpoint sample> <length in samples>
would you use tables, datastructures, a textfile or lists to store and access these cue lists?
mn.
Hi,
On Tue, May 18, 2010 at 06:20:04PM +0200, Max wrote:
let's say you are storing the snippets of the wave in the form <index> <startpoint sample> <length in samples>
would you use tables, datastructures, a textfile or lists to store and access these cue lists?
Or a message box? :)
I'd probably use a [textfile] for simplicity.
Ciao
Frank Barknecht Do You RjDj.me? _ ______footils.org__
-
Frank Barknecht -
Lorenzo -
Max -
PF