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

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?

Loukas Perreault

Currently, I'm sorting all my samples into two categories: those with a duration of 3 seconds or less, and those with a duration greater than 3 seconds, using the sfinfo object.

In my "master folder," which includes subfolders, I have approximately 16,000 samples. To gather their filenames, I employ a recursive search using JavaScript, resulting in an array of filenames. Subsequently, I feed this array into the sfinfo object to retrieve the length of each sample.

The process of obtaining the array of filenames takes around 3-4 seconds, which is efficient. However, the subsequent step, where sfinfo analyzes the files, is notably slow, taking approximately 3-4 minutes. During this time, Max appears unresponsive, with the spinning wheel suggesting a potential crash.

My query is whether there's a method to execute this task in the background or optimize the process for speed. Essentially, I'm looking for a way to offload this heavy-duty analysis to another thread or improve its efficiency to eliminate the unresponsive behavior.

optimizing-large-soundbank-parsing

Optimizing Large "Soundbank" Parsing

Hi! Is anyone aware of the Function create_audio_clip (class Clipslot). It's listed in the LOM manual but don't seem to work (also for class Track) :

live.object: 'ClipSlot' object has no attribute 'create_audio_clip'

At first I tought it was because I was using it under Ableton 11, so I installed Ableton 12 trial and still don't work.

My guess is that 12 trial is version .0.1 and the LOM manual refers to .0.5

I was wondering if anyone using 12.0.5 tried create_audio_clip function because I don't think I can update from the trial version... or maybe I'm wrong... Thanks!

Function "create_audio_clip" (class Clipslot and Track) missing (LOM)

function-createaudioclip-class-clipslot-and-track-missing-lom

Nick O

Hey guys. Complete beginner here. I was wondering if it possible to incorporate a selection knob into the stock Ableton multimapper that toggles each mapper on and off in series, such that only one is selected to be active by the knob at a time? The goal is to have each mapper premapped to a target in a project and to cycle through mapping targets with a macro knob so only one of my choice is modulated at a time.

I figured I'd use toggles and connect them to a knob somehow, I'm assuming there are if/then objects I can use for this? I'd have the knob have a range of 1-8 for example and use an "if knob = x" then "toggle on and the rest off" kind of logic. But being a complete beginner I have no idea if this is how it would be done nor do I know where to connect the toggles in this salad of routings

Hey guys. Complete beginner here. I was wondering if it possible to incorporate a selection knob into the stock Ableton multimapper that...

adding-toggle-knob-to-abletons-multimapper

Adding toggle knob to Ableton's Multimapper

Exit Only

Hi. I'm trying to traverse the LOM from the current device in an arbitrarily nested drum rack and find the drum pad that the device belongs to. If I traverse upwards I end up hitting DrumChains and RackDevices but there doesnt seem to be an association where a device knows it's own drum pad. The main thing I'm trying to get here is the note assigned to trigger the device, which is only in the drum pad. 

It's kind of odd that a DrumChain lists the choke group and out note but does not list the note received

Hi. I'm trying to traverse the LOM from the current device in an arbitrarily nested drum rack and find the drum pad that the device belongs...

find-drum-pad-for-a-given-device

Find drum pad for a given device

I'm using MIDI envelope for internal and also external  processing (CV) with Ableton

Anyone knows, or can help about how creating an option to have a join transition instead of having a complete restart for the envelope at each start command ?

MIDI Envelope with join transition point at trig restart ?

midi-envelope-with-join-transition-point-at-trig-restart

Rot Drei

I'm trying to create a shortcut that show the browser and select the "Current Project" place.

Using the LOM, I can focus the browser but I can't select the "Current Project".

In the older LiveAPI 11, I think that live.app had a browser property, but is missing in the 12.

Anyone knows a way to access to the "Browser" class.

I'm trying to create a shortcut that show the browser and select the "Current Project" place.

Using the LOM, I can focus the browser but I...

show-the-browser-and-focus-on-current-project

Show the Browser and focus on Current Project

Daniel Semmelrock

I'm trying to figure out how to loop a sequence of samples (Round Robin) playing a single MIDI drum pad repeatedly.

I also need to be able to reset the sequence via another Drum Pad (MIDI mapped) so next time I hit the other pad the sequence starts on the first sample again.

So far, I found 3 different methods of achieving that effect (almost) in Ableton:

Problem: none of these methods allow to reset the sequence via MIDI mapping.

Unfortunately I don't know Max4Live, to fix this myself.

Maybe  someone here  can help me achieve the desired effect :)

Hello,

drummer and Max4Live noob here.

I'm trying to figure out how to loop a sequence of samples (Round Robin) playing a single MIDI...

Cycling '74 Forums

@EVAN, Were you ever able to find documentation explaining the changes that are relevent to Push 3 takeover? I'm hoping to update some...

Good to know, enjoy!

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

I truuuuly don't mind, your tips are awesome!! I will implement this method right away! Thanks a lot!

https://ableton.centercode.com/welcome/

Thanks again for the help, I really appreciate it 😊. So I tried the previous one and it does remove the mapping, going to try working with...

Hi. I'm trying to traverse the LOM from the current device in an arbitrarily nested drum rack and find the drum pad that the device...

MIDI Envelope with join transition point at trig restart ?

I'm trying to create a shortcut that show the browser and select the "Current Project" place. Using the LOM, I can focus the browser but...

I am not Live user and so maybe I placed a text button that can't be mapped ? try this one with replaced live.textbutton