🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left... mailtimers.com
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Your shopping cart is empty.

multiple Devices onof states

Submitted by Marcus on Thu, 12/21/2017 - 17:43
Marcus
Pro User
Control Surface Studio User

Hello,

I have tried to make a script for my Launchpad, where the first grid-button controls the on/of state of the first device, the second button the on/of state of the second device, etc.

(like the second row of buttons from the top in device mode on the Push controller).

I failed, the result I get is that only the first button works, and only on the selected device, this is what I did,,,

On the app I activate the "add new mapping" button, then the "Device on/of " state button, and on that page I activate "specific" for track state, Specific track number "1", and then for the first grid knob I use Device chain number "1", the second Device chain number "2", etc.

(And of-course the name, the led on/of states, and midi-learn for the grid-buttons)

What am I doing wrong, can you help me out ?

Marcus

4 Responses

Comments

JohnC
Forum Admin
#1

Hi Marcus,

Could you post up your script's .json file here (or email me the script).
I'll take a look and see if I can figure out the problem here. Could be a setting, could be a bug, its hard to say at the moment.

Thanks

John

Marcus
Pro User
#2

Hi John, thanks for taking the time to look in to it.
I've put the .json file in the attachement.

upload files: 
Marcus
Pro User
#3

STOP THE PRES !!
(As in, don't waist time helping me)

It WORKS !!!
(I don't know what happened)

I just made an other script, which also partly did not work (nudge up and down not responding), so I loaded the previous script again, and suddenly it works flawlessly, weird, but I'm very happy.

Thanks for making this App John, solves lots of my headaches,, :)

JohnC
Forum Admin
#4

Hi Marcus,

Was just about to download your file lol, that's great news!
We have added a couple of fixes around bugs with devices in the last few days which could have fixed your problem.
Glad you're up and running again :)

John