Mark Durham

So I'm building a M4Live drum machine at the moment which is using polybuffer~ to handle the sample storage side of things. It's a bit unusual in that I need the polybuffer~ to be track specific, so only drum players on each track have access to the samples from polybuffer~. My original plan was to get the track number from Live and rename sends etc using this, but I'm now stuck as it seems like polybuffers cannot be renamed on the fly.

renaming-polybuffer-for-individual-live-tracks

One more small thing - am I right that #0 arguments don't function in Live? (M4Live noob btw)

do i understand correctly ? u want to share your polybuffer content across FEW devices ?

. as for #0 , in M4L u would use three dashes "---name" ;

HI mark .
do i understand correctly ? u want to share your polybuffer content across FEW devices ? 

. as for #0 , in M4L u would use three dashes "---name" ;


Specifically, I want to be able to put in a live device as a midi effect containing a polybuffer~ (midi passes through) before a drum rack , then have individual drum rack devices access the polybuffer~, but only for that track. So then the user could have a separate system on another track doing the same thing and they won't interfere.

I've seen the --- thing around, that makes sense. So if I name my polybuffer [Polybuffer~ ---drumserver] then it will generate a unique id for that device?, perhaps then I could send that to every device on the track? I'll try it out. I've got dict working across devices so that could do it.

yes exactly . once u retrieve your instance number (in rack devices) u will be able to address that polybuffer from your midi device .

ps: i just wondering how u will send these id's forward . Will u target it with LOM ?

Maybe you could prepend the track number to the sound names for each "space" of the polybuffer~ using sprintf to format them and use that to route the different drummer notes ?

This is nice solution unless u move/reorder 

So maybe its track number could be used for the init stage as a flag for the devices . Dont know

This is nice solution unless u move/reorder session channels right ?
So maybe its track number could be used for the init stage as a flag for the devices . Dont know


I hadn't thought about reordering channels. That would mess it up. The auto-naming seems to be s digits before the buffer name (see pic). So I'm thinking to initialise the buffer, strip the first 3 characters from the first filename, assign that to forwards and receives on that track, then take it from there. This is getting horridly complex though...

Stephane proposed to use channel number for the naming part . maybe u can use #1 as a argument for the buffer name ? .

it could work in both ways .. devices could ask Midi device for identification if reverse setup order matters .

As i understood midi rack will respond only to one buffer ? So yeah , u have to make this feedback initialization .

this would not mess up while moving/reordering channels , as channel number would be required on initialization time only for the first communication/identification part.

main Midi device initialize itself , and stores channel number

After that you would send [channel#,M4Linstance#] to all the devices in session

Then only those rack devices will set buffer names if channel number matches

#edit:
it could work in both ways .. devices could ask Midi device for identification if reverse setup order matters .
As i understood midi rack will respond only to one buffer ? So yeah , u have to make this feedback initialization .

#edit2:
this would not mess up while moving/reordering channels , as channel number would be required on initialization time only for the first communication/identification part.


 do work in Max for Live devices but it's a different behaviour than the 

. The --- gives a uniq id for the entire device (across sub patches / abstraction). while the 

FWIW, #0 do work in Max for Live devices but it's a different behaviour than the ---. The --- gives a uniq id for the entire device (across sub patches / abstraction). while the #0 gives a uniq id in abstraction.


Renaming Polybuffer~ for individual Live tracks