djkrysr
I have a Akai LPD controller I have mapped to use samples, I also have added a floating window to the default skin to show and activate samples however in the new version, altho the script 'sampler_volume 1' will adjust the volume of the 1st sample, the script 'sampler_pad 1' will activate the sample in slot 9, 'sampler_pad 2' will active slot 10 etc, is this a bug or has everything changed in the new sample layout.
Thanks
NOTE: OK just discovered it depends on what deck is active, if I script 'sampler_pad 2' on to a custom button on the left deck it works, but same script on a custom button in right deck it activates slot 10 not 2.
My Akai doesn't have a deck assigned so is there a workaround to make sure it's slot 2 always not deck dependent.
Thanks
NOTE: OK just discovered it depends on what deck is active, if I script 'sampler_pad 2' on to a custom button on the left deck it works, but same script on a custom button in right deck it activates slot 10 not 2.
My Akai doesn't have a deck assigned so is there a workaround to make sure it's slot 2 always not deck dependent.
geposted 2 days ago @ 9:45 pm
Stephane Clavel
make sure samplerSpanAcrossDecks is set to false in the options
geposted 2 days ago @ 10:24 pm
djkrysr
Stephane Clavel wrote :
make sure samplerSpanAcrossDecks is set to false in the options
I've have tried but that it makes no difference.
Annoyingly on the buttons I've create, script commands such as
sampler_volume, get_sample_name and even get_sample_info all return the info for the actual slot, whereas play, colour, position on the other hand are 8 slots out when deck right is active.
I have tried adding <deck deck='left'> to the floating windows of my skin but that makes no difference.
geposted 2 days ago @ 10:46 pm
djkrysr
I have a 4 deck controller connected, I seem to remember that can effect how sample slots are mapped on the skin, but it was never a problem in the last version when addressing the slots directly via a window or on a controller.
Changing my Akai controller to deck 1 solves the problem on that but my floating windows is still problematic, there must be a way to write the script to force it to deck 1 but the format eludes me.
Changing my Akai controller to deck 1 solves the problem on that but my floating windows is still problematic, there must be a way to write the script to force it to deck 1 but the format eludes me.
geposted 2 days ago @ 10:52 pm
djkrysr
OK sorry if I've wasted anyone's time.
After a lot of experimenting, putting a <deck deck="master"> container in the right place on the floating window solves my problem, obviously my script was lazy the first time around but since it worked I didn't notice.
Anyway, that appears to solve my issues I will test again.
Thanks
After a lot of experimenting, putting a <deck deck="master"> container in the right place on the floating window solves my problem, obviously my script was lazy the first time around but since it worked I didn't notice.
Anyway, that appears to solve my issues I will test again.
Thanks
geposted 2 days ago @ 12:54 am