Bug in 2.8.5? or……
I created a script for my BCR 2000 controller. The script has four modes, one of which is the shift mode. The script has always worked well. A few weeks ago, I tried to expand my script. After loading the modified script into Ableton, I noticed that it no longer worked correctly. In particular, I could no longer operate the volume faders properly. Another point that stood out was that I set up my script so that in all four modes, I work with an 8-track session box. I can move the session box through my arrangement, and the volume, pan, and mutes to be controlled are related to the session box.
After modifying and re-exporting my script, not only did the volume faders stop working, but the navigation with the session box also ceased to function. I tried to fix this by using a backup of the script. When I restored this backup script, my volume faders worked normally, but the session box navigation was entirely gone, and the buttons I use for navigating the session box and selecting tracks now trigger entirely different parameters.
The filenames of my scripts indicate they are version 2.8 scripts, yet Remotify shows they are version 2.8.5. I also see on the forum that there are many issues at the moment with script conversion and modification, and I wasn’t aware that there was a version 2.8.5. I couldn’t find any further information about it on the forum either.
My questions are:
- Why are my scripts no longer working, even if I restore an untouched original backup?
- How can I get my scripts working again?
- In what way does Remotify’s development impact the malfunction of existing scripts, and what does the future development of Remotify look like? It took me a lot of time to get scripts working, but if there is insufficient stability in the program and script functionality, creating custom scripts with Remotify isn’t a future-proof path
All errors in your log appear to be coming from script not built using CSS: MiniLab.py and KeyLab88.py.
So I would recommend deactivating these scripts as a starting point.
“I also discovered that when I disconnect the MIDI input to my controller, the volume faders work normally, so it’s clear that the MIDI feedback is causing interference”
Have you used Ableton Live’s internal mapping mode to also map to your volume faders? if so, I would suggest deleting these mappings as they will interfere with functionality coming from your script.
“When I restored this backup script, my volume faders worked normally, but the session box navigation was entirely gone, and the buttons I use for navigating the session box and selecting tracks now trigger entirely different parameters.”
If you restored an old script which used to work but now it doesn’t, this suggests that something else outside of the script has changed.
“Are there additional dependencies (besides the CSS map) necessary to ensure a script functions correctly”
As long as you haven’t altered/deleted Ableton’s default MIDI remote scripts such as _framework, the only dependencies are your custom script and the MIDI device which sends the MIDI messages.
“It seems a migration was made from version 2.7 to 2.8. But the result doesn’t feel fully polished—it resembles an earlier, 0.8 version in terms of look and feel”
I’m not sure what you mean by 0.8 version but 2.8 was a complete rebuild, much of it completely from scratch.
“I’m concerned about stability. Considering the cost, even with a significant discount, stability is essential”
2.8+ is many times more stable than < 2.7 was. That was one of the major reasons for the complete rebuild, there were many app breaking bugs baked deep into 2.7 that a complete rebuild was needed.
“So, could you share your vision for Remotify’s development?”
Well, all I can say is that was have many new features and improvements in development at the moment, but don’t have a public roadmap at present however.
Sign up
User registration is currently not allowed.
Hi John,
I’ve removed the two native Ableton scripts, but unfortunately, this didn’t resolve the issue. It’s odd that this problem has suddenly come up, especially since I don’t actually have one of the two keyboards in question, and the Minilab isn’t linked to any scripts either. I also don’t use Ableton’s native script.
By the way, have you mapped your volume faders using Ableton Live’s internal mapping mode? If so, I’d suggest deleting those mappings, as they could be conflicting with functionality in your script.
However, I haven’t mapped anything on the MIDI channel where my controller is linked to the script, nor on any of the buttons that are part of the controller template linked to the script. This setup has been stable for a while, so it’s strange that it’s now causing issues.
If you restored an older script that previously worked but now doesn’t, it does raise the question of whether some other factor outside the script has changed.
Which brings me to my question: Are there additional dependencies (besides the CSS map) necessary to ensure a script functions correctly? Also, I’m curious about Remotify’s overall stability and how ongoing developments might impact program and script stability.
I ran into a similar issue in an earlier script, where the session navigation box stopped working after a minor script update. I managed to fix this by deleting and re-adding that part of the script. And now this new issue…
It seems a migration was made from version 2.7 to 2.8. But the result doesn’t feel fully polished—it resembles an earlier, 0.8 version in terms of look and feel, and I’m concerned about stability. Considering the cost, even with a significant discount, stability is essential.
I say this with some reluctance, as I do see huge potential in the platform. I’m even willing to invest time in rebuilding a script through Remotify to see if that might work better. However, it’s important for me to feel confident in the platform’s stability.
So, could you share your vision for Remotify’s development? Are we at a point where we can fully rely on Remotify scripts, or do you expect further substantial changes soon? A roadmap or something similar could also be helpful in providing clarity.
Best regards,
Quirien