Rivanni

"live_set tracks 113 devices 22 chains 7 devices 8"

"live_set tracks 45 devices 22 chains 7 devices 18 chains 0 devices 7 return_chain 2"

So they can vary in length and the pattern is not always 'word number word number etc.'. 

I want to add leading zeros so all numbers are 3 or 4 digits long.

I used the OR syntax to find numbers of different lengths, but how do I use these to add the correct number of zeros in the Substitute?

I have symbols like the following ones

"live_set tracks 113 devices 22 chains 7 devices 8"

"live_set tracks 66"

"live_set master_track...

how-to-use-the-results-from-or-syntax-in-substitute-part-of-regexp

How to use the results from OR syntax in substitute part of regexp?

paul robinson

so about three years ago i found someone on this forum to write a custom m4l device for me:

https://cycling74.com/forums/uimacro-for-creating-new-tracks-and-assigning-input-channels

sadly, it stopped working after the new Live 12 update, and i can't get a hold of the person who originally made it for me, Patrick_K.

So - is there anybody willing to have a look at this for me?

The devices input lists are still beeing populated according to my hardware, but when i "Add" a track, nothing happens.

Hey there,

so about three years ago i found someone on this forum to write a custom m4l device for...

update-a-m4l-device-that-ceased-working-in-live-12

Update a m4l device that ceased working in Live 12

Ian Dicke

Has anyone had any luck taking control of the buttons on Push 3? The same code I've attached works fine on Push 2. I'm guess this is a bug, as the Push 3 is incredibly unstable. I'm running the current firmware (1.1.2).

Push 3 API Test.amxd

Has anyone had any luck taking control of the buttons on Push 3? The same code I've attached works fine on Push 2. 

push-3-live-api-problems

Update: I sent a report to Ableton and they confirmed it is a bug. 

What kind of unstabe behavior - apart from not getting control over the buttons - you experience with Push 3?

Is it about running Max for Live devices on the Push 3 standalone in general, only calls to the Live API or even the entire performance / behavior of Live on Push 3 standalone?

Or do you even got problems with a "normal" Push 3, while Live is running on a desktop machine?


Too many little bugs to list here, but the most problematic are the hardware freezes and crashes, which happen fairly frequently in my short experience with it. Max for Live device stability is definitely an issue too, although some things that I expected not to work (like sending MIDI between devices via udp send and receive) actually functions. Many of my commercial devices ship with custom Push grid layouts, and I'm having mixed luck getting those to work on Push 3 thus far. I'm fairly confident most of these things will be resolved in future firmware updates.

Despite bugs, is the Push 2 API supposed to be similar for Push 3?

From what I can see, it appears that all Push 3 button and encoder names are the same as Push 2.

I use my Push 2 with only Max/MSP and route MIDI message towards custom MIDI ports. I do this without Live and I ignore the "User Mode" button. I basically detect input from the Push 2 and then send messages to other software.

Do you know, even theoretically, if the same should apply to the Push 3? I'm debating getting it.

If you post a test patch, I'm happy to try and run it on my Push 3 unit.

Hi Ian glad to see you are diving into push also. Are you using in it in Standalone mode? 

I am actually in the same jam, taking over buttons and reassigning them and it feels very random when the max4live device fails to work. Everything is fine when tethered, but in standalone mode i get problems with the observer take over - but not always. 

I've made manual initialization buttons, resets, take over controls in case its something to do with [live.thisdevice] or live.path or live.object, but they also fail to consistently work.

One of the first devices I slapped together I actually have a delayed bang to initialize it since it wouldnt do it on set load or device add - so this made me think I need to try manual init buttons but with this particular device its just not behaving well at all.
I wonder if its something super weird like - send receive failing sometimes, or encapsulated parts of patches or wrong placements of deferlow for the standalone version.

I have only carried out some basic standalone tests of my devices and was surprised by how much of ran as expected. But, until they fix the observing buttons issue, I can't really move forward with officially porting things to Push 3. I am hoping the update comes soon...

I've made some more devices and did some observing and it seems like live.observer on the control surface (push 3) can fail sometimes (after initial boot and first time adding the device) but observing live related functionality seems to consistently work.

...a lot about the standalone and m4l still feels pretty beta, I got to say.
also, the standalone crashed on me will playing my first gig with it, actually we had an audience of exactly one person so nevermind.
anyway. I also didn't get any observing of buttons done via the API, the only thing that works is 'call grab midi' --- for now, you can get the push's buttons like that.
and it does work! in standalone - mode.
--- UPDATE  -- but not reliable at all.
patch based on Ian's work attached.
cheers
R

I am able to receive the button and dial values via "call grab midi", but I wonder why MIDI notes from the grid are excluded? 

And for me, the grab midi method works on standalone mode. I just updated to firmware 1.1.13.

I've been playing around over the last week porting a m4l device that takes control of the entire matrix and some of the buttons. One thing I did notice is that you have to grab_control before the live.observer (or callback in javascript) will report. This is NOT the case with Push2. Unfortunately, that doesn't work well for me, so I had to resort to the 'grab_midi' call and filtering to observe buttons without grabbing them first

@ Evan, this is fixed... but in the current beta that's been and still is in beta for several months.

Yeah I saw that - I an coming across a lot more things that are breaking some of my other  Push centric devices that depend on the control surfaces API to function. Will be opening another thread about that, as it seems like it might be intentional. 

Push 3 Live API Problems

max doe

Hello! live 12 here. i'd like to make a patch that normalizes an audio clip after its been consolidated. 

in live, after consolidating a clip, it is automatically normalized, but the gain is turned down to match the level it was at before consolidating. i would like to (if possible) find the most recently selected or consolidated clip, get it's gain level,  and if gain < 0, set the gain to zero.

clips have get/set for gain parameters. so the getting/setting gain should be possible. the tricky part might be finding the clip though. i the path for audio clips is "

".  how could i go about doing this? any suggestions?

Hello! live 12 here. i'd like to make a patch that normalizes an audio clip after its been consolidated. 

in live, after consolidating a...

normalize-consolidated-clip

Normalize Consolidated Clip

spin lud

Hi, I would like to know if it is possible to have a Max midi audio device that also can receive audio from an audio track in Ableton. So basically I can access both the midi data received on the midi track where the Max device is and the audio data coming from the other audio track. I am not interested in outputing anything from this device, no midi and no audio should come out from this device. I just need the midi and audio signals to control some Jitter visualizations.

Hi, I would like to know if it is possible to have a Max midi audio device that also can receive audio from an audio track in Ableton. So...

m4l-midi-device-that-also-receives-audio-from-a-specific-track

[M4L] Midi device that also receives audio from a specific track?

LSka

I was toying around with a morse code generating patch for a project, and I took the occasion to dive into Live 12's new feature, MIDI Tools.

So here's a Morse code generating device for Live 12:

I'd be happy if someone could test it and report any issues.

I was toying around with a morse code generating patch for a project, and I took the occasion to dive into Live 12's new feature, MIDI...

sharing-experimenting-with-midi-tools-for-live-12-morse-generator

[Sharing] experimenting with MIDI Tools for Live 12: Morse Generator

patrickkidd

I am trying to workaround some behavioral nuances (*cough* crashes *cough*) between running/saving a device in Max and in Live, and could workaround them if I were able to detect which environment my js object was running in.

detect-if-running-in-max-or-live-from-js

Detect if running in Max or Live from js?

Dalmazzo

I have some chords where I need to adjust each MPE pitch in some cents. 

How can I access the info displayed in Ableton Live in the MPE tab? I haven't found anything to control that from M4L yet. 

https://cycling74.com/articles/what's-new-in-live-11-part-1

However, there is no information on each MIDI note controlling its own MPE. 

I have some chords where I need to adjust each MPE pitch in some cents. 
How can I access the info displayed in Ableton Live in the MPE...

control-mpe-of-each-note-independently-from-m4l

Control MPE of each note independently from M4L

truc trc

I have a long Live project, containing several locators, I would like to find a way to export the content between each locator.

Each export would also have to be in a folder whose name would be the name of the locator.

is there a solution with M4live (I don't know at all the possibilities and limits of M4Live) or other for this robot? or the only solution is a character recognition  script similar to :

https://github.com/hankijord/ableton-export-bot?tab=readme-ov-file

Ableton

hello everyone, 

I have a long Live project, containing several locators, I would like to find a way to export the content...

auto-audio-export

Auto Audio Export

Marc Villanueva Mir

I am building a M4L device that should translate the audio input into a value in the range of 0-255, which will be used for controlling a DMX external. The problem is that the device doesn't work at all when attached to any audio or return track (in return tracks, it even blocks all sound), but when I enter the editing mode from Live, it works perfectly fine: the audio is coming in and flowing to the speakers, and the values are properly calculated. As soon as I close the editor and return to Live's running mode, the device plays dead again.

Might I be missing just something very basic?

Hello!

I am building a M4L device that should translate the audio input into a value in the range of 0-255, which will be used for...

Cycling '74 Forums

I don't know if it is possible in one regexp but surely if you divide into single steps

Hey @TFL I'm trying to get in touch with you but I cannot get the contact link on your website to work :(

@ODDEO - The issue that launched this thread (not being able to observe Push 3 buttons) has been resolved in the current Push...

Hello! live 12 here. i'd like to make a patch that normalizes an audio clip after its been consolidated. in live, after consolidating a...

Max instrument (midi input) + routing object for audio was the perfect solution for me. Thank you guys!

Good to know, enjoy!

Here's one way... var api = new LiveAPI(null, "live_set") if ( ! api || ! api.id ) { // You're in Max standalone }

Thanks for the response. I started to see the idea. The most direct way to resolve the issue I'm trying to do is actually in the following...

Thank you for that answer. I suspected that it wasn’t feasible. indeed, retyping would be a solution but users of this setup mainly know...

Aha! I just restarted Live and now it works well!