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
So, I’ve done a little further investigation. I’ve found out that I can use track select and transport functions in Mode 0, but when I try to assign either mixer, DJ or device functions to Mode 0, then the script wont work.
Hi,
Yes it looks like mode 0 is missing mixer code which these controls rely on.
We’ve found the cause of this but need to run some tests before implementing the fix.
Should have it fixed tomorrow.
Also, yes there was a bug with mappings on mode0 being changed to mode 1 when importing back into the app. This has now been fixed.
Thanks
John
Nice, thanks. Really looking forward to that 🙂 After some more experimentation I’ve come across another weird issue. If I assign track select to Mode 0 and then assign a session box to Mode 6 for example, and then enter Mode 6 to use the session box, the track select stops working. I’m using different buttons for the track select and the session box.
The track select works just fine when I switch between modes that contain mutes and solos and things like that. So it looks like there’s an issue with the session box.
Thanks for quick replies and a steady stream of improvements and new features btw.
Hey,
We’ve now fixed the issue with mixer code. The mixer component is now added outside all modes so they all have access to 1 global mixer.
Track select is pretty self contain, doesn’t rely on session box or anything else to work.
Maybe the issue with the mixer component was causing an error in your script.
Try downloading a new version and see if you still have the same problem.
John
Sign up
User registration is currently not allowed.