Ableton Forum

For recursive things like this I'm using JavaScript with the LiveAPI() object, but it is somewhat tricky trial & error in detail, here an excerpt from such a script for the next version of my BCR2000 Control devices: // Use a singleton, as LiveAPI is an external resource with performance implica...

To clarify things up regarding priorized event scheduling and CPU resources in general: High priority threads regularly interrupt low priority threads, for audio with a frequency of sampling rate divided by buffer size, e.g. for 44.1kHz / 256 samples you get a frequency of roughly 172Hz. Each time a...

Live - as any real time software application - already has thread priority management built in. I don't know anything about the VST or AU API, but for M4L, I can testify that it is the responsibility of the device developer to use "deferlow" objects where appropriate, as e.g. incoming MIDI...

On my research I've found M4L MIDI Lib also, but on OS X lh_midiinout definitely was easier:
http://cycling74.com/forums/topic/m4l-m ... d-midi-io/
http://beatwise.proboards.com/thread/1394

Live filters out consecutive identical MIDI CC messages as redundant. If you're on OS X, you can circumvent that behaviour with the lh_midiinout external by Leigh Hunt. I've made an utility device for that exact purpose for my BCR2000 Control device set at http://www.maxforlive.com/library/device/14...

Still on Live 8 32Bit / OS X 4GB, I'm used to sporadic crashes when modifying a Live set with many M4L devices or also memory-intensive devices like Looper. In that case, I tend to be in a "construction mode, precarious, don't worry" state of mind, as Live's after-crash file recovery is qu...

As the topic "Ableton Live and BCR2000" came up lately here: I've just released version 1.2 of the BCR2000 Control M4L device set, now accompanied by a video tutorial in 6 parts: http://www.maxforlive.com/library/device/1416/bcr2000-control http://vimeo.com/t0n1/bcr2000control-1 (1-6) As a...

In your cycling74 post you state that you're editing the device, then parameter values get lost. This has to do with preview mode, for more details see viewtopic.php?f=35&t=204700#p1609050 about workflow in M4L.

I'm still on Live 8.4.2. Parameter pesistence behaves differently when editing devices in preview mode (see http://cycling74.com/docs/max5/vignettes/core/live_preview.html) where parameters often get lost upon saving or in normal m4l mode when just the device files are updated without editing them i...

BCR2000Control itself has no concept of banks, these are used internally by the hardware to send different CC numbers for the same knob for each bank, making it look like different knobs for Live. For the input part (hardware<->BCR2000Control), the m4l device only receives CC number/value pairs and ...

It works with any MIDI controller sending/receiving MIDI CC in parallel to bluehand control (which overrides it), and overcomes its limitations: The controlled device (or its track) doesn't need to be in focus, thus distinct devices can be controlled simultaneously. Not restricted to 8 controls: Use...

If you have Max for Live, you can try my http://www.maxforlive.com/library/device/1416/bcr2000-control devices. Setting all up is a bit tedious, but it was designed exactly for that purpose, see the chapters "Multiple Layers" and "Total Recall" on the project page. I recommend to...

If you have M4L, you can try my Latency Meter device(s) / Live Set to measure the latency of individual audio or MIDI plugins or specific plugin chains. It was created with Live 8 / Max 5.

http://www.maxforlive.com/library/devic ... ency-meter