Mobile Zombie
Is it possible by scripting to include a code in the track name for example "SAMPBANK1" which makes the sample bank named "SAMPBANK1" pop up in the sampler view?
That means I could create track specific samples which are called up automatically when loading a certain track.
Or perhaps include the name of the samplebank somewhere else in the MP3 tag area?
That means I could create track specific samples which are called up automatically when loading a certain track.
Or perhaps include the name of the samplebank somewhere else in the MP3 tag area?
geposted Tue 18 Apr 17 @ 6:09 am
locoDog
Yeah possible. I told someone how ages ago, something like a repeat start script waiting for a load pulse, when the load pulse is triggered query the track name if it matches call the sample bank.
It all gets a bit lengthy though once you're querying for one of a possible lots.
What would be cool would be a database entry for related sample bank, query and call from there.
Actually just thinking for a second... just a action poi on your track right on the loadpoint to call the bank, a quick jab of cue and job's a goodun.
It all gets a bit lengthy though once you're querying for one of a possible lots.
What would be cool would be a database entry for related sample bank, query and call from there.
Actually just thinking for a second... just a action poi on your track right on the loadpoint to call the bank, a quick jab of cue and job's a goodun.
geposted Tue 18 Apr 17 @ 7:00 am
klausmogensen
locodog wrote :
Actually just thinking for a second... just a action poi on your track right on the loadpoint to call the bank, a quick jab of cue and job's a goodun.
That would also be my suggestion
Go to the POI editor of the track and add an ACTION POI at the very beginning of the track with something like:
sampler_bank "<the name of the sample bank>"
as the macro
Then the sample back should change to the one you want as soon as you start playing the track
geposted Tue 18 Apr 17 @ 7:15 am
Adion
locodog wrote :
Yeah possible. I told someone how ages ago, something like a repeat start script waiting for a load pulse, when the load pulse is triggered query the track name if it matches call the sample bank.
It all gets a bit lengthy though once you're querying for one of a possible lots
It all gets a bit lengthy though once you're querying for one of a possible lots
Instead of storing all the possible track names and sample banks in the script, you could still store it in a tag field.
On load, the script could query the 'user1' field for example, use param_contains to check if it includes some part of a common sample_bank name, and if so, load the sample bank based on that field.
geposted Tue 18 Apr 17 @ 7:31 am
locoDog
Thanks for that, I wasn't sure about querying the user# tags.
I may use this my own setup.
I may use this my own setup.
geposted Tue 18 Apr 17 @ 7:54 am
Mobile Zombie
Thanks for all ideas.
I realize there will be conflict between the two decks. Playing sample 1 on bank A, and loading another track to Deck 2, will change the sampler bank.
Then one have to assign certain "slots" on the sampler exclusive for Deck 1 and Deck 2. Getting messy...
I realize there will be conflict between the two decks. Playing sample 1 on bank A, and loading another track to Deck 2, will change the sampler bank.
Then one have to assign certain "slots" on the sampler exclusive for Deck 1 and Deck 2. Getting messy...
geposted Tue 18 Apr 17 @ 8:24 am
locoDog
Maybe, maybe not, a pad page could query the deck & user field & call the bank & call the sample.
There could be other ways to avoid the conflict.
There could be other ways to avoid the conflict.
geposted Tue 18 Apr 17 @ 8:59 am