David

https://cycling74.com/forums/getting-around-coll-not-saving-w-set

has an example of how to save a coll to a pattr object and reload the data with a loadbang. I think I can see vaguely how it works. Would this reload device colls from saved sets and from saved device presets? I'm using Live 8/Max5. Does Live 9/Max6 make this much easier?

save-coll-contents-with-live-set-and-as-presets

Hi David . good question
In later versions [coll] still need some tricks .
In new version we have got [Dict] object that is used for storing and managing Data structures . And from measuring it is operating faster than [coll] object . Its way more efficient for dynamic data flow .
You can pattr'ize its content as you would wish .

Additionally , you are able to transfer [coll] data to [Dict] structure back and forth (with one message) if you still want to use [coll] object in that pattr'able fashion .
So you dont need any old tricks anymore i guess .


Thanks for that. I find it hard to understand how the pattr object works, despite reading the reference and looking at the tutorial. I am loading my colls from files so a better way to maintain state between sessions might be to use pattr to save the filename instead of all the data. I tried binding the pattr to opendialog but it says its not supported. Can anyone point me to an example of using pattr to save filenames please?


This is my effort so far but it doesn't seem to restore the previously loaded file into the coll. 


Save coll contents with Live set and as presets

AlexG

In the File menù of Max 7 there is an item named "Export Max for Live Device...". How does it work? Is there any documentation?

export-max-for-live-device

I'm curious about this feature as well as I am unable to click on it.


I am wondering how to build a max midi effect in that way (or choose what kind of m4l device I want). I worked on a project with midi in and out, and absolutely no audio, but when I export this project as a m4l device, it always comes as a max instrument in live. Any idea?


Hi,
Same request here. Is there a way to force max to create a midi device instead of an audio? Or any other way to force live to use the project local files inside a m4l midi effect?


Yes. Click on the "show containing project" on the bottom toolbar, then on "Project settings" and finally on "Project inspector": You'll see a "Max for Live Device" Option.
And from the same project window you can define which files (local or non-local) to use. You can specify a file searchpath too.


Ok, thank you LSKA for that suggestion. Should have known, there's an inspector for everything :)


with this solution, can we make a device which run without Max ?


Finally I tinkered with a synchro (snapshot on time_ms argument). This is ugly but it works.

Export Max for Live Device...

LDMdesign

I am using fixed colors in my device, and yet when I change the Live theme, it changes the fixed colors. Light theme is forces light grey elements to black. 

I would expect dynamic colors to change, but not fixed colors.

Also, when I shared my device with a friend (both using Live 11), the off-white elements turned to black when he is using a dark theme, thus making it unreadable.

I am using fixed colors in my device, and yet when I change the Live theme, it changes the fixed colors. Light theme is forces light grey...

theme-changing-fixed-colors

Theme changing fixed colors

Blair

Is there any way to get the value of the zoom display? I thought it would just be the zoom factor in max but its an independent thing, I'm wondering if anyone's been able to get it via LOM or something else?

Is there any way to get the value of the zoom display? I thought it would just be the zoom factor in max but its an independent thing, I'm...

m4l-get-zoom-display-ui-scaling-control

M4L get Zoom Display (UI scaling control)

Pole One

I have reached stalemate in the project I am currently working on. The idea is to use a XBOX controller that will trigger notes. For that, I want to create a sort of instrument fingering (like a flute or oboe woud have to seal the holes) with the buttons on the right of the controller. This idea would correspond to use a kind of a """standard""" fingering for a digital instrument.

I figured that maybe it would be playable to set C on the A button, E on the X, G on the Y and B on the B (to make an arpeggio). To make the middle notes (D, F and A) I was wondering if it could be possible to assign them with multiple button pressed. To do so, A and X would trigger D, X and Y would trigger F & Y and B would trigger A.

I tried multiple stuff to achieve this idea, and the most convicing one was to use the [if] object. You can check the patch atached to this post to look at what I tried. 

1) why does the [sel 0 1] object coming from the X buttons bang the two outlet at the same time everytime I try to do a D ?

2) did I missed an object that would simplify what I'm trying to do ?

3) I have the strange feeling that everytime I am close to the answer, I missed something and everything seems to be nonsens afterall. Like I can finally press A and X to trigger D BUT the A triggers the C at the same time which leads to hear two notes at the same time... 

If someone has a clue that might help me solving this problem I'd be thankfull !! (please excuse my english, I'm a foreigner)

How to get one note from various bang inputs ?

how-to-get-one-note-from-various-bang-inputs

mike fonte

I see from the LOM and other forum posts that it is possible to observe which scene is "selected". 

Is there a way to observe which scene has been "triggered" (or "fired" or "is playing")?

I see from the LOM and other forum posts that it is possible to observe which scene is "selected".   

Is there a way to observe which scene has been "triggered" (or "fired" or "is playing")?  

how-to-observe-"triggered"-scene

No.  But one pretty easy solution would be to take is a “dummy” track with no clips and to observe it’s fired slot index.  At least I think there is such a property and it should work…

How to observe "triggered" scene

Asher Bay

I'm trying to send notes to a vst instrument in Live via midiout. When I click to bang the kslider, the note triggers properly. However when I send bangs to the kslider via metro, no notes are played in Live. 

It works fine when I send notes via noteout, but noteout only works for the same track that the device is on. I want to be able to send notes to any instrument track. 

I'm trying to send notes to a vst instrument in Live via midiout. When I click to bang the kslider, the note triggers properly. However...

sending-notes-via-midiout-only-works-when-i-manually-click-not-when-i-send-bangs-via-metro

Sending notes via midiout only works when I manually click, not when I send bangs via metro

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

11OLSEN

Please someone take a look. I never noticed this before. A very simple js to observe the "mute" button state of a track. Add device to multiple tracks, everything works as expected, mute state is printed to Max window. Now as soon as one of the devices is deleted, all other js observers stop working. I even tested it with 2 different devices observing different path and property, they break each other when one is deleted.

mute_js_fr.amxd

JS is frozen into it and looks like this:

    var obj = new LiveAPI(callback,"live_set this_device canonical_parent");

        post(obj.path, args, "\n")

The same thing with Max object works as expected. Is there something wrong with the JS? How can removing one break another one in a completely different device and js? 

Please someone take a look. I never noticed this before. A very simple js to observe the "mute" button state of a track. Add device to multiple tracks, everything works as expected, mute state is printed to Max window. Now as soon as one of the devices is deleted, all other js observers stop working. I even tested it with 2 different devices observing different path and property, they break each other when one is deleted.
Here is a device:

JS is frozen into it and looks like this:

function bang ()
{
	var obj = new LiveAPI(callback,"live_set this_device canonical_parent");
	obj.property = "mute"

	function callback(args) 
	{
  		post(obj.path, args, "\n")
	}
} 

The same thing with Max object works as expected.  Is there something wrong with the JS? How can removing one break another one in a completely different device and js? 


Please someone take a look. I never noticed this before. A very simple js to observe the "mute" button state of a track. Add device to multi

js-observers-stop-working-if-another-devicejs-with-observer-is-removed-from-the-set

I can reproduce in both Live 11 and Live 10 (using 10.1.41, with whatever Max is bundled).   I thought there might be something funny with the scoping in the callback, but then I wrote the code like this and get the same result:

function bang ()
{
	var obj = new LiveAPI(function(args) {
		post("mute2", this.path, args, "\n") 
	} ,"live_set this_device canonical_parent");
	obj.property = "mute"
}

The below works fine -- the observers are appropriately isolated in their scope.  But it does nothing to explain how the function-scoped variable initialization you use gets graduated into a global scope...

var obj = null
function bang ()
{
	obj = new LiveAPI(function(args) {
		post("mute2", this.path, args, "\n") 
	} ,"live_set this_device canonical_parent");
	obj.property = "mute"
}
This is closer to how I do my observers (though often its in an array of observers or encapsulated in some other object.)  

I guess really my intuition is that the observer initialized in your original bang() ought to cease to exist after it's function scope since it's not explicitly retained elsewhere.  Then the fact that your code worked in the first place would've been a memory bug in Live.


Interessting, I have not seen it written like that. So instead of a function name I can write the callback directly into the LiveAPI( parameters)? I followed this doc . And 

Technical note: you cannot use the LiveAPI object in JavaScript global code.

doesn't sound like I have to retain the obj in global scope. Further when you look at the example at the bottom of this page it looks like it's the recommended way to put the callback into the function scope.
btw: support just confirmed it as a bug

I really lost some hair today trying to find the mistake.
 🦲 

I always took "you cannot use the LiveAPI object in JavaScript global code" to be about the initialization and function calls where writing them directly into the global code would imply you're trying to do things before [live.thisdevice] has notified that the Live API is ready.  For instance in the example code at the end of the page I would expect that code could only be happy living inside another function call (as in your bang() ), and that's sort of backed up by them having a 'return' statement in there.

As for the inline syntax format: I don't normally do that, either, as it's hard to read.  (It also comes with an  issue where it triggers with "id nn" before you've assigned the property name you want to observe).  It was just for me to test because I thought having a functional reference to 'obj' inside the callback was maybe a little questionable as I assumed the callback() would go away outside of your bang() scope. **

And now if it's confirmed as a bug -- and I assume you mean that your initial code should work and persist observers as written -- I guess I'm also surprised the implied behavior is that once you instantiate an observer it stays alive indefinitely.  Seems like that would be bad for memory/performance.  I normally track observer lifespan and aggressively try to unassign their observed property and null them out when they are no longer needed.

** I didn't intend to confound the two differences (inline callback AND variable outside of function) in the second example.  Sorry!

Yes it makes sense to track the lifespan. I had a few situations today where it seems like callbacks were called from memory so that I had 3 messages from one api object. But that may also be caused by opening and closing the editor. Anyways I'm waiting for the fix. Thanks for looking at it Tyler!

Is there something like free(obj) in js? Setting obj.property ="" doesn't feel like obj will be garbage collected. But the global scope will help to reuse it without creating new LiveApis all the time. I can see that!

there is for... only jitter objects:
myJitterObject.freepeer();

I think I just borrowed that obj.property = "" practice from elsewhere in this forum.  For some reason in my Favorites list is now marked as spam!:


In effect what I've been doing (maybe without satisfactorily answering your question for all JS) has been:

obj.property = ""
obj = null

And it seems to work... certainly no more redundant callbacks getting fired for me?

I would love to see an official JS LiveAPI best practices guide.  There is a decent amount of not-very-intuitive stuff that goes on, IMHO.

To conclude here and for future reference: Putting the obj variable in global scope seems logical and fixes the problem of my first post. I'm no longer convinced it's a real bug, maybe just some confusing example code in the live js documentation.

var obj;
function bang ()
{
	obj = new LiveAPI(callback,"live_set this_device canonical_parent");
        obj.property = "mute";
        
 	function callback(args) 
	{
  		post(this.path, args, "\n");
	}
}

JS observers stop working if another device/js with observer is removed from the Set

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

Thanks @DP.WHILE for the dict object hint, hurra! The dict object remembers the last saved state whilst in Live (provided the dict's...

I tried this method but the option to choose the type is greyed out, does anyone has any idea?

I also researched this and posted at discord 2 days ago. I wanted fixed colors for live.* UI objects and noticed that switching the colors...

Not in the moment you change it but probably when you quit Live.

No prob ! thanks for the reply anyway :))

Why you post it if you already noticed that it's rubbish? You know the LOM doc page ? What about observing scene / is_triggered ?

try to send proper note on and off, not only note on.

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...

They don't even consider it necessary to update the code example. So there will always be people who fall into this trap.

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