Problem with Mode 0
Hi
I just purchased the Pro version yesterday, and I’ve now started building a rather complicated script for my live performances. I need my volumes and sends to be active at all times, so I’ve assigned them to Mode 0. However, this is causing the script to not work, where as when I assign these functions to Mode 1, it works fine. Any idea of what might cause this problem?
Best regards
Hi,
Welcome to Remotify!
I can’t think of a reason off the top of my head why this could be,
Have you had a look in your log.txt file for errors? (search for remotescripterror)
Or upload your log.txt file
Or your script’s .json file
and we can take a look.
Thanks
John
Hi
Thanks for a quick reply. I’ve just made some very simplified versions of the script, that I’m trying to make.
The one called “tester” is the one that works, because the volume, send and track select are assigned to Mode 1
The one called “tester 2” doesn’t work, where volume, send and track select are assigned to Mode 0
Well, the mystery continues. I just tried to import the “tester 2” .json file, that I just uploaded here. Apparently the volume, send and track select, that I assigned to Mode 0, are now assigned to Mode 1, when I import the json file, while the mode buttons are still assigned to Mode 0 and the solo button also kept the assignment to mode 2.
So far I ‘ve found a pretty tedious work around, where I duplicate the same mapping and assign to the different modes (for example a mapping for volume on track 1 in both mode 1 and 2). But since I’m gonna have 40 mappings that need to be active at all time, and given that I’m gonna need 7 different modes, this isn’t really the smartest solution.
Sign up
User registration is currently not allowed.