hey hello,
first up, i extremely happy with the livid code, and if you guys would not have built that thing, i would be lost.
i am using it quite excessively with ableton 9 now since 4 months, and so far everything was perfect.
all started a week ago when i made a major reassignment for all the nobs, suddenly some leds and also the potentiometers started to act a litte wiggy (jumping chaotically in the value)
i realized that in the editor there was a problem by saving to a preset, when i renamed the preset, this problem got solved (allthough i had to give the preset everytime saving a new name otherwise the jumping would start again)
so i updated to the newest firmware, and all seemed good, but now, when i load the liveset it only updates the led values for active bank!
and all the others stay blank, aslong as i turn them (but the value will jump to zero then) ore i press the "midi" button from ableton, then it updates them.
also if i turn on the computer the values on the active bank will change, but not on inactive, which means than then all the infos are incorrect later on.
please, PLEASE tell me that my bad feeling that there is something wrong with the internal flash storage is wrong, and that i just overlooked a simple setting that fixes this problem
i do not have long to a quite important concert and without my fully functional code i am fu**ed
grazie mille for your answers!
*update
when i want to change the led ring number in the editor i get the message ""js: error calling function UI" in Max
and all the ledring numbers are automatically equal than to the one i changed
*update2
when i run the the firmware on on the code (both old and new) it sais complete, but in the log i can find these messages
** Skipping ff at 00000000 - not in Flash range.
until
** Skipping ff at 00000fff - not in Flash range.
*update3
same problem on a different computer :(
Comments
I am quite nervus, time is a factor :( Does that mean i have to buy a new one?
Are you using the online editor?
I did try it, no difference ..
Sent you an email - perhaps a video of the problem would help me troubleshoot.
hi there,
What is the other application you're using? Are you on Mac or PC?
hi aum—
oh and it's a Mac I use.
when I deactivate and then re-activate LOCAL CONTROL in the Code Editor while Live is running it shows me where all the knobs are at (the actual values of the encoders of Code), and apart from those I have already turned, all LED rings are zero, which means that their current value is zero and they do not switch to their auto-mapped or assigned parameter, which they should of course, though on loading up Live the rings suggest they values are hooked up… something in the scripts perhaps sets them all to zero, although the LEDs suggest they are at the value of the assigned parameter. Just what could it be??
"Well, what has happened is that, yet again, my personal assignments to the Code's knobs and buttons has been overwritten by some chaotic values"
I'm looking into this from my end, sorry for leaving you hanging. You're setup is made more complicated by the fact that there are several semi-unique things going on; not that it's "bad", but it takes a little extra effort to wrap my brain around what's happening here.
Hi Pete,
hey aum,
oh and another thing (sorry!!) :::
»when opening a project in Ableton the assignments of macros in the 'encoders'-Mod don't have the parameters affixed to them«
First: glad that got you sorted :) I was hoping that was the root of the problem.
yes, it was the root of the problem and those exact issues have since not occurred, so great work!