DON’T UPDATE YOUR MIDIFIGHTER TWISTER’s FIRMWARE BEFORE A GIG
They new firmware for the twisty came out last night, I guess? Anyway I had just finished my setup when I noticed it, did the update, took off for my gig only to find out that the whole thing was fudged up big time. The update had reset all my settings thus rendering the whole controller utterly useless. I’m still (at this very moment) trying to fix the whole thing…
Some switches are sending different midi than before and the left upper corner led (ch. 3 CC0) starts doing this this blinking rainbow animation everytime I connect the fighter. So far I’ve only managed to turn it off by sending a separate midi command from Traktor to turn it off.
I can confirm the animation is on for CC.000 by default… However, I don’t see any midi is changed. Did you have exported your settings before updating Twister?
*edit:
I’ve disabled an OFF STATE color in all four bank and that seemed to stop the rainbow animation (probably at random color in given time) but pressing a side button bank #1 seemed to restore the scale. perhaps something’s with midi bank change.
Okay, it looks like the wrong midi messages was just a personal fuckup of mine with utility. I had accidentally changed the midi’s on the 2nd row of knobs, so it was just a matter of setting up the correct channels for the encoders and switches (or buttons?). The switches need to be set to the same channel, even if you’re using them for a basic note hold action.
Anyway the led still won’t stop blinking despite my efforts to suffocate it with traktor and it does kind of suck not knowing the firmware update will reset the twister to factory settings.
The cycling LED rainbow on the first encoder is caused by a bug in the current build in the MF Utility, the new firmware exposes it. This kind of behaviour will surface whenever you update changes to the device using the utility but should go away if you reconnect your Twister after closing the MFU.An update will be issued later this week to address it.
I updated the new firmware aswell.. The only issue i’m facing is that in the main twister page where you select your samples, patterns, volume, filter. The LED output on this page is behaving weird, Its just become the opposite of how it used to be. On state is low Brightness & Off state is full brightness. Example when I have a particular remix cell playing the volume encoder should be brightened up & when i mute it the led brightness should be low as per the original mapping, the way I was using it before the update.
Now, its just become the opposite. When i play the remix cell the brightness is low & when i mute the brightness is high. This applies to all the 16 encoders. However Pattern Edit mode & Snapshot mode are fine.
Hey lothar, I’m glad to see you pick one of the Twisters!
To solve your issue you first need to ensure that the latest firmware version is properly installed. To do so download and Import the latest V3 of sequencer mapping.
Thanks mate, Probably the first in India. Anyway thanks for the tip, Its working fine now. Didn’t realise that with every Firmware update I gotta look for the updated mapping as well.
I can say mine was one of the first models in Europe. I loved it with red encoders and remember that I was pretty lucky to get them packed on time
This can happen in case when new update is addressed to the actual Sequencer side of firmware. It’s always good idea to subscribe Maps by adding the MF Twister to your myDJTT > controllers section of the profile and the system will automatically send a notification in to your inbox when new mappings for The Twister are created.
Not too sure if this is relevant to this thread but posting it here rather than opening a new thread. On the main page of the twister the top 4 encoders turn on the 4 fx slots for the remix cells & FX Unit 4 on Deck D. How do I change it to turn on FX Unit 3 instead of 4. Tried looking through the mapping file, Couldn’t find any commands for that.
This hasn’t approved to be the real issue which can affect live performance and so I would close the thread.
I suggest you to keep this thread in mind for any other firmware and mapping related questions to help keep this forum organized.
Your mapping request is something that can be completed inside the controller manager. The commands you should look for are “Deck Effect On” and can be found in the “Seq Deck Controls” part of mapping. This 4 command are currently set to work on the Focused Deck and all you really need to do is to change the deck assignment to deck C.
There are no real issues with the last update except for exposed rainbow animation on the CC.000 of bank one. It’s caused by plugin which will be fixed in the utility update in the next week. Note that you can revert back to an older firmware if you want to. To learn how, refer to the post #6 of this thread and follow the link posted by Matias.
Sloppy work DJTT … There’s another bug besides the Rainbow bug (which even the most basic QC before deploying firmware should have exposed) and now two weeks with no patch?
Anyway, rant over. Here’s another bug that the 30 May 2014 Firmware introduces:
If you set an encoder state by sending MIDI to the Twister, the knob becomes permanently locked into that encoder state. The MIDI messages still change correctly as you turn the knob, but the white indicator dots stop moving until you reboot the Twister.
Rolling back to the recovery .hex file I guess…
rs
Since the may 30 update The LED ring feedback when an encoder is mapped to a parameter in Ableton has become very laggy. It used to be totally smooth, but now turning a mapped encoder causes the LED ring to jump every 1000ms or so, looks bad…please fix!
DJTT’s is far from sloppy. They are a great company, and great to its customers! Tons of electronics get updated and have things go wrong. I know that it is not good that stuff gets screwed up, but DJTTs has always provided a temporary fix when stuff like this happens. Just roll it back, not the end of the world. It still works fine.
In my book, releasing a firmware update that’s clearly broken, then letting it sit out there for weeks, is sloppy. I know that’s what my clients would tell me if I did something like that. (I’ll try that line about “just rolling back” sometime though for a laugh.)
Statement stands: DJTT, this is sloppy. QC your software before deployment and if it’s broken, roll it back within a day or two of when you find out. Far from the first time I’ve seen this and I’ve owned every product they ever made.
Not upset? You seem pretty upset with what you wrote. Things get overlooked. My godamn MacMail hasn’t worked properly since the Mavericks 10.9.1 release. You think Apple cares? Nope. At the very least someone from DJTTs comes on the boards explaining how to temporarily fix it, but rest assured they will fix the problem. Their stuff is solid and they stand by their products always. 2 weeks really isn’t a long time, especially when everything still works. Either don’t do the upgrade or roll it back. Seems very simple to me… maybe I am missing something.
