McMillen QuNeo looks to be everything I want in a controller

[MattKMI]

Just wanted to check if that was something I should look into! Sorry that we can't fix it!

[Korhan]

Matt, how ”insensitive” can the sensors be made? A controller-heavy Ableton Live performance using one or more QuNeos along with an iPad running Lemur with a lot of bouncing balls on it can crash the set in less than an hour.

[Warrior Bob]

Ableton's Undo buffer limitation has been an issue for a long time. If you have controllers that send dense MIDI data (such as wiimotes), your live set will crash once the undo buffer reaches a size of 2GB. Ableton has expressed their indifference to the problem many times. They simply don't care.

Hold on, you can crash Live by filling the Undo buffer? I've never run into this. Do you a reference link handy, or a set of steps that can reproduce the issue?

[MattKMI]

You can make the sensors fairly "insensitive" but that doesn't mean they don't still send a bunch of data...

I'm impressed that Ableton hasn't addressed this issue, what with the plethora of advanced iPad apps and midi controllers... I'm going to do some testing and see if we have any suggestions...

~M

[Korhan]

Ableton's Undo buffer limitation has been an issue for a long time. If you have controllers that send dense MIDI data (such as wiimotes), your live set will crash once the undo buffer reaches a size of 2GB. Ableton has expressed their indifference to the problem many times. They simply don't care.

Hold on, you can crash Live by filling the Undo buffer? I've never run into this. Do you a reference link handy, or a set of steps that can reproduce the issue?

Yes you can. You need a controller that sends data even when it's not in use, such as a Wiimote/nunchuk pair that send data even when you lay them on a table (gravity). In a few hours, Live will crash. This happens when you set your system up, do your soundcheck and then accidentally leave your Wiimotes on while you're away from your computer for the next 1-2 hours. When you come back all seems to be well until that 2GB limit is reached in the middle of your performance. There are definitely ways to avoid this, such as turning the wiimotes off, disconnecting your controllers, etc.

[bartend7]

Matt, how ”insensitive” can the sensors be made? A controller-heavy Ableton Live performance using one or more QuNeos along with an iPad running Lemur with a lot of bouncing balls on it can crash the set in less than an hour.

It might be Lemur causing the crash when combined with QuNeos. I have had some problems running an ios device with other controllers. Does it crash with multiple QuNeos and no Lemur?

[fishmonkey]

Ableton's Undo buffer limitation has been an issue for a long time. If you have controllers that send dense MIDI data (such as wiimotes), your live set will crash once the undo buffer reaches a size of 2GB. Ableton has expressed their indifference to the problem many times. They simply don't care.

that is really poor programming.

[Korhan]

Matt, how ”insensitive” can the sensors be made? A controller-heavy Ableton Live performance using one or more QuNeos along with an iPad running Lemur with a lot of bouncing balls on it can crash the set in less than an hour.

It might be Lemur causing the crash when combined with QuNeos. I have had some problems running an ios device with other controllers. Does it crash with multiple QuNeos and no Lemur?

bartend, this undo buffer problem is independent of the controller(s) used. The above scenario was just an example. You can easily crash Live with only a wiimote/nunchuk pair, which used to happen to me a lot until I learned how to deal with it.

[MattKMI]

Hey Everyone,
Wanted to point out bug I've found and how to resolve it! When you're using our live script for clip launching, try turning off velocity on preset 9 (unchecking the check boxes in grid mode), this makes it a lot easier to launch clips. We liked shipping with velocity on, because it's an advantage over other clip launching controllers, but I've noticed it makes playability a little less dynamic. We've logged it as a bug, but if anyone is noticing the issue, you can fix it by changing preset 9!

Thanks,
M

[LOFA]

Hey,

My buddy has one of these things and he wants me to write him some custom scripts, etc. I am really into the idea, especially since there is python involved- been meaning to learn it for a while.

I have a couple questions though:

Is there an decompiled standard of the remote midi script that people are using to develop for this? I would prefer to be on the same page as others that are trying to get into this. Similarly, is there a forum or thread where people are documenting their work or presenting ideas?

The other question I have is does anyone have a go-to-source for similar inquiries relating to the novation launch pad? I ask, because I would use it to test out scripting before developing for my friend's Quneo.

So far my research has brought up the following resources, in case anyone else is interested:
http://remotescripts.blogspot.com/2010/ ... asses.html
http://modern.dj/app/
http://forum.keithmcmillen.com/viewtopic.php?f=50&t=608

[DasRev]

Has anyone had any luck getting the sequencer to work? I can't switch modes on mine at all

[slowspines]

@DasRev Are you referring to the step sequencer?

On Preset 9 hold the Shift-Button and press the bottom right corner of PAD 1 (the very bottom left drum pad) this should take you to step sequencer mode. This only works if you are on a MIDI track with a MIDI Clip created in the Clip Launch view. If this does not work can you please explain in detail the feedback you are getting or not getting.

Thanks
?

[nmunger]

Is anyone else having this issue?: Using the shift key to change modes works at first, each time it is used there are gradually increasing cpu spikes until the point of almost 300% + audio drop outs (never seen anything like it, just pressing the shift key makes live go insane). Also returning to the clip launch mode everything is out of wack, led feedback is either incorrect or way laggy. Eventually shift key gets stuck and everything goes to shit. WTF. Doesn't seem to be any sort of problem if I don't use shift key but thats kind of like settling for 1/3 of the expected functionality.

[siliconarc]

that is really poor programming.

it's not poor programming, it's just an outdated system. the problem is every movement is recorded to the undo buffer. great for undoing manual tweaks etc (cubase for example just ignores all plugin tweaks so you cant undo them - much worse!) but Live falls flat when external modulators flood the buffer over time. it's croaked on me when using external LFOs as CC mods.

[fishmonkey]

that is really poor programming.

it's not poor programming, it's just an outdated system. the problem is every movement is recorded to the undo buffer. great for undoing manual tweaks etc (cubase for example just ignores all plugin tweaks so you cant undo them - much worse!) but Live falls flat when external modulators flood the buffer over time. it's croaked on me when using external LFOs as CC mods.

the behaviour suggests that there isn't appropriate checking of the absolute limits of the undo buffer. any way you slice it, that is poor programming.

well-designed and written code explicitly and gracefully handles unexpected or unusual events.