Edsko de Vries

Question as in the title: how should I load samples from the Ableton Factory Packs into a buffer~ in a Max for Live device? One option is to add a live.drop object, have the user select and drag a sample into that, and then use that. This works, but requires the user to set up the device. I'm working on a device that will use quite a few samples, so having the user select each and every one seems unnecessary -- especially given that the device is designed to work with a specific factory pack.

Trying to do this without a live.drop object results in two problems:

1. Path to the sample. On my machine, these samples are stored in /Users/edsko/Music/Ableton/Factory Packs/pack/.../sample.aif, but of course this will be different for everyone. Apart from the absolute path, however, every other suffix of this path (just "sample.aif", just "Ableton/Factory Packs/.../sample.aif", or any other combination, does not seem to work.

 find the file (when I specify the absolute path), it refuses to load it, "cannot open parser for this file" -- even though the very same sample works just fine when I drag it into a live.drop. (Whilst trawling the forums to find solutions to this problem, I came across 

https://cycling74.com/forums/buffer-could-not-parse-aif-err-1

 which seems to suggest this might be because the .aif files have some kind of protection that they cannot be used outside of Live..? But I am trying to use this in a Max for Live device..

Any help and/or pointers would be appreciated,

1. Path to the sample. On my machine, these samples are stored in /Users/edsko/Music/Ableton/Factory Packs/pack/.../sample.aif, but of course this will be different for everyone. Apart from the absolute path, however, every other suffix of this path (just "sample.aif", just "Ableton/Factory Packs/.../sample.aif", or any other combination, does not seem to work. 

2. Even when buffer~ can find the file (when I specify the absolute path), it refuses to load it, "cannot open parser for this file" -- even though the very same sample works just fine when I drag it into a live.drop. (Whilst trawling the forums to find solutions to this problem, I came across https://cycling74.com/forums/buffer-could-not-parse-aif-err-1 which seems to suggest this might be because the .aif files have some kind of protection that they cannot be used outside of Live..? But I am trying to use this in a Max for Live device..

Any help and/or pointers would be appreciated,

-Edsko

Hi,
Question as in the title: how should I load samples from the Ableton Factory Packs into a buffer~ in a Max for Live device? One option i

how-to-load-sample-from-ableton-factory-packs-into-buffer~

Protected Ableton aif samples won't load into buffer-
You would first need to "unprotect* and repack them


It works just fine with a live.drop though; so I guess that must be doing that "unprotection" implicitly? So does that mean impossible to write a M4L device that uses samples from Live packs directly? :(

If the sample is protected aif, you can find out by simply trying to open it in another app.
like audio editor or max sfplay etc.
It will not work.

What restriction to live devices is, I don't really know.
But at least in Live 10, one can't use any
protected aif sample to load into buffer,
being max standalone app or in max4live device.


I want to bump this a bit as I have the same issue. In response to the previous post: it seems the Live.drop object does create some kind of temporary address (I'm not sure the exact method or term) for protected samples such as in factory packs so that buffer~ is able to load them. I can confirm that you CAN load protected samples into the buffer~ if using Live.drop

My issue (maybe similar to OP) is that I am making a device that you can drop 1000's of samples and so I store the names in a dict and can't use Live.drop and therefore the users cannot load in protected samples in my device (ie from factory packs)  :(

I've done some tests and it seems when you send a "clear" message to live.drop, the temporary address it creates is lost, the same happens when you drop subsequent samples into Live.drop (it releases the previous dropped samples' temp address).  So unless I want to have 1000's of live.drop objects in my device I cannot use it (and similar projects wont be able to).

Is there any way to load protected samples into the buffer without live.drop? Does anyone have any more info about this? Thanks!!

I found elsewhere on the forum Source Audio said this:

"... some samples from Live packs are copy protected, mans are not real aif files but some encoded format only live can cope with. You can try to open it with any other audio player, or even with hex editor to look for valid aif header in the code."

This makes it seem a bit grim to do this without live.drop , unless their final sentence holds a possibility

This is quite problematic thema.
What I believe is - this TEMP- etc string, having sample name at the end is only a reference to that protected sample.

Sample itself gets loaded into buffer without getting written to disk.
At least this is so with short samples I used for testing.
This unique TEMP id for each sample - it matters where sample is installed,
if you digg one sample from the pack an copy it elsewhere,
id will differ from original one.

If you drop on both live.drop and dropfile, you get both : TEMP string and absolute path to protected sample ...
which can be used to send write message to buffer~ and so make the sample free.

Another idea is to autopopulate umenu with absolute paths to samples and load them through set message to live.drop
and into buffer. 


Hmm ok I think from what you said I might be able to do this when loading a preset (non presets work fine because they can go through the live.drop when loaded, its preset recalling that is the real issue) because I am working with 100's of samples going into a polybuffer:

1. Store all the paths in a dict that can be recalled correctly as absolute paths
2. When preset loads don't just send them all to the polybuffer directly, but instead go through a live.drop object internally with the set message as mentioned

I think that should work in my device (??) because once loaded in the buffer doesn't matter if the live.drop releases the reference. Thanks for the spark!

If you need to use several samples at the same time, how about droping a live.drop inside of a poly~ patcher? One sample per voice that can be played simultaneously. But you would be limited to 1024 samples (the maximum amount of voices a poly~ can handle).

I think I'd definitely prefer what I described in my last response (a single instance of live.drop that is used just before appending samples to a single polybuffer) over having 100's or 1000s of live.drop instances. Actually having 100s or 1000s of any GUI object is something id personally avoid

If it works that way, then good!
I agree about avoiding using too much UI objects when possible, but I believe there is no performance loss compared to non-GUI objects when they are simply not dispayed, which would be the case with what I had in mind.


A while go I tested loading of protected aif samples from live packs into polybuffer~  using live.drop -> append $1 message.
It allways crashed after loading few samples.

On the other hand, loading into single buffer to rewrite thousands
of samples in a batch processing manner, worked without problems.



How to load sample from Ableton Factory Packs into buffer~?

Dylan Perez

I am new to Max for Live, Been searching around for a while through old forum posts, tutorials, youtube videos, etc and so far haven't come across anything that actually implements a solution to the following problem:

I've been trying to figure out a way to use a microsoft xbox wireless controller for pc as a control surface for Ableton Live 11 (Suite). For clarity when I say a control surface, what I mean is using it to activate controls in Ableton Live that you would normally map to midi cc or computer keyboard, I do not mean using the controller to play a synth plugin through a Max for Live script.

I've been able to find a multitude of examples on how to use the controller as a midi instrument to play a synth through Max, I have not been able to find a single example on Windows of anyone being able to use the controller to actually control Live's UI.

The issue I'm personally running into is this: While I can easily get the controller connected and transmitting data into a Max patch, I have not found a way to use that data to control UI parameters.

Even after filtering the button presses, and converting the data messages into the correct midi cc messages, and passing those into midiout in a max patch, they have no effect on Live's UI.

I believe the issue here is that in order to use midi cc to control Live, you have to setup a control surface and here is our first major issue - there is no control surface for an Xbox Controller.

So it seems there is a simple solution: Create a control surface script.

Then we run into the second problem, even if we have a control surface script, when we go into Live's preferences to assign it, there is no way to select the xbox controller as input or output for it, because Live doesn't recognize the xbox controller at all (I imagine because it isn't a midi device by default).

Can any of you point me in the right direction to resolving this? 

I've been trying to figure out a way to use a microsoft xbox wireless controller for pc as a control surface for Ableton Live 11 (Suite).  For clarity when I say a control surface, what I mean is using it to activate controls in Ableton Live that you would normally map to midi cc or computer keyboard, I do not mean using the controller to play a synth plugin through a Max for Live script.

I've been able to find a multitude of examples on how to use the controller as a midi instrument to play a synth through Max, I have not been able to find a single example on Windows of anyone being able to use the controller to actually control Live's UI.  

I believe the issue here is that in order to use midi cc to control Live, you have to setup a control surface and here is our first major issue - there is no control surface for an Xbox Controller. 

Can any of you point me in the right direction to resolving this? 


I am new to Max for Live, Been searching around for a while through old forum posts, tutorials, youtube videos, etc and so far haven't come ... 

using-a-gamepad-as-a-hardware-control-surface-in-ableton-live

you mentioned all problems allready.
I see 2 options as non live user.
1 make max app that acts as xbox hid to midi and create c.surface script
you'll need some virtual midi to link both apps in windows.
2 make max4live device to receive xbox and control what you want
using usual LOM scripting etc


P.S.
if you send midi from m4live device out to
virtual midi port and use loop back into live,
then it will get accepted for midi mappings.
What silly games one has to play with this 
so called live software

Using a gamepad as a Hardware Control Surface in Ableton Live.

Julien Bayle

Creating an array of LiveAPI objects, I'd like to know if objects are really killed if I splice all elements of that array.

It doesn't seem from a performance/efficiency point of view.

Indeed, my liveset is ok, no lag nothing.

I put the device, if I build a lot of callback, it lags a very bit (only the audio meters)

If I click on my button which splices ALL object in the array, it still lags.

If I delete the device, then undo, no more lags.

Creating an array of LiveAPI objects, I'd like to know if objects are really killed if I splice all elements of that array.
It doesn't seem from a performance/efficiency point of view.

Indeed, my liveset is ok, no lag nothing.
I put the device, if I build a lot of callback, it lags a very bit (only the audio meters)
If I click on my button which splices ALL object in the array, it still lags.
If I delete the device, then undo, no more lags.

are-liveapi-objects-instantiated-in-js-garbage-collected

I would imagine that a formal declaration of array to be null (as opposed to calling methods to remove objects from the patcher) might help. 

Problem is:
I have an array with a length of n.

I decide to activate this or that parameters to be listened (= create the corresponding LiveAPI object w/its callback)
It puts it inside the array at the index 3 for instance.

Then, I want to remove the object in 3 (= I don't want max to listen a specific parameter anymore)

I still think my suggestion is worth a try.


problem isn't the array but the objects which seem to remain in memory/cpu cycles or whatever.
sounds strange.
first time I experiment that


Live API objects aren't going to get collected, I think.  Id's are persistent, even if no longer assigned (I asked someone about this before, but perhaps something has changed since then).  I don't know how this figures into memory management within js, though.

One thing you can do is remove the callback from the API by assigning the object.property = 0.  This generally gets rid of any overhead I have.  Just removing the js object's assignment does NOT remove the API object itself, afaik.

After rereading your post, I think that's what you are after:  reassign the .property of the object to 0.

btw, assignment of the array to null will lead to api errors (or at least it used to, the last time I tried it).


for sure, it only remove the reference and garbage collection can happen but of course doesn't free the placeof the LiveAPI objects.
removing the callback doesn't help a lot as far as I tested.

I asked to Andrew who probably answer here.

if you are interested by the purpose, you can check this :
http://julienbayle.net/2012/01/25/my-video-generator-global-architecture/


I know this is an old post but I'm actually having a similar issue. I am instantiating a lot of LiveAPI objects in my javascript code, and eventually it starts to lag my ableton set. The problem is that I am also using lots of observers as well (and also Task objects), so it is hard to narrow down the exact cause of the lag in the code so far. The only way to fix it is to delete the max plugin and then undo, as Julien mentioned in his original post. 
@JulienBayle, did you ever come up with a solution to the problem? Or does anyone else know?

@zack 
you could call this simple function i wrote.

It works well. To call after any "new LiveApi" instance

function DestroyLiveApiObject(t)
{
    t.property = '';
    t.id = 0;
    t = null;
}

Are LiveAPI objects instantiated in JS garbage collected ?

Benjamin Zakharenko

Apologies if any of this is basic knowledge, I'm still a relative newcomer to Max/MSP after being introduced to it in a college class last semester. I've been searching for a low (sub 10ms, sub 5ms if possible) latency autotune solution that could be implemented on Push 3 Standalone for live performance—which means I can't use externals or the vst~ object either. All of the solutions online I've found so far use retune~ under the hood, but unfortunately whenever I test the latency of this object it's always at least around 50 milliseconds. Is there any way to lower the latency of retune~ to make it more functional for live performance? Or is there another object anyone would recommend I use instead?

Hi there,
Apologies if any of this is basic knowledge, I'm still a relative newcomer to Max/MSP after being introduced to it in a college ... 

lower-latency-of-retune-push-3-autotune-solution

Lower latency of retune~?  Push 3 Autotune solution

Trevor being Trevor

Ableton 12 was announced today! I am curious to see if there are new possibilities in regards to Max and the API. Figured I'd create a place to point out cool stuff it as it rolls out. Cheers!

Ableton 12 was announced today! I am curious to see if there are new possibilities in regards to Max and the API. 

whats-new-in-ableton-12

I'm so excited for Live 12. I'm coming from Bitwig and the grid, just recently fell in love with Max. Can't wait to see if there are new possibilities. 

I know! It's so exciting to see the new stuff we'd be able to do with the object model. 

Also, it's not very often that you see somebody migrating from bitwig to ableton. Hopefully you can get over the relative instability of the software...

in the patch notes they mentioned stuff about a few new objects in max 8.6, including "Array and String objects". Once I get beta access i'm excited to see what these will unlock. Theres also live.modulate~ which im excited to mess with. 

oh and ofc the new m4l stuff for midi tools. i'm very hopeful that there'll be an explosion of super creative devices taking advantage of the new format. if only they added similar tools for audio clips as well...

Thanks for the good news! I'm excited to see where things go :-)

What's New in Ableton 12!

jbone1313

Is there a reliable way to get Live's audio buffer size in Max or the LiveAPI?

I searched the entire internet, and I still cannot find an answer.

adstatus with a "latency" argument does not work.

I assume my RME audio driver does not support this.

I searched the Live object model, but I cannot find anything there.

Is there a reliable way to get Live's audio buffer size in Max or the LiveAPI?

I searched the entire internet, and I still cannot find an answer.

adstatus with a "latency" argument does not work. 

latency: If supported by the audio driver, reports the input and output latencies of the driver in samples.

I assume my RME audio driver does not support this. 

I searched the Live object model, but I cannot find anything there. 

Is there a reliable way to get Live's audio buffer size in Max or the LiveAPI?

I searched the entire internet, and I still cannot find an ... 

how-to-get-lives-audio-buffer-size

The signal vector size is always 64. I've never heard of being able to get the output buffer, sorry!

Might there be an easy and inexpensive way to calculate it? By, say, passing a signal across some objects and measuring?

How to get Live's audio buffer size?

Anyone knows how to send a message to ableton live's status bar at the bottom?

Sounds like such a simple thing one would want to do using M4L...

Anyone knows how to send a message to ableton live's status bar at the bottom?
Sounds like such a simple thing one would want to do using M4L...

Anyone knows how to send a message to ableton live's status bar at the bottom?
Sounds like such a simple thing one would want to do using M4

ableton-live-status-bar

Hi OCH !

Did you find ? 
I seem to remember seeing someone do this before but I don't remember who or how...

From memories it was something simple, involving a print object or a max message with semicolon...

Ableton Live status bar

Stephen Schmidt

OK so i've been working on a patch with live 10.0.1 and max 8 and I noticed that when I change the values of the live user interface knobs quickly the final value output by the objects is not always the one that's displayed. At first I thought I was overloading max or something as my patch was pretty cpu heavy but then I made a test with only the m4l.bal2~ object and the different ui objects and the same thing happened.

Is it just my computer or something? Am I doing something wrong? This didn't seem to happen before.

abletonuiobjecttest.amxd

OK so i've been working on a patch with live 10.0.1 and max 8 and I noticed that when I change the values of the live user interface knobs quickly the final value output by the objects is not always the one that's displayed. At first I thought I was overloading max or something as my patch was pretty cpu heavy but then I made a test with only the m4l.bal2~ object and the different ui objects and the same thing happened. 

Is it just my computer or something?  Am I doing something wrong? This didn't seem to happen before.

OK so i've been working on a patch with live 10.0.1 and max 8 and I noticed that when I change the values of the live user interface knobs q

problem-with-live·dial-live·numbox-and-live·slider

I got exactly the same issue you are describing, checked same patch on Live 9, no problem. Any news on this one? 

but see, it has "node" now, which lets you post your bugs directly on facebook and twitter (and the prism and tempora project of the GCHQ)

not sure what you mean Roman, but I don't know anything about "node", facebook and twitter. 

i'm just trying to use live 10, and it's unusable for me because of this bug

Seems to be incorrect behavior, but are you totally sure it's new to Live 10?

1)  Firstly, for the sake of making a more "fair" test patch: live.numbox/slider/dials that are automated as floats but display as 'Int' have a display number that is always rounded to nearest integer.  So if the value in your live.dial is 25.7 the dial will display '26' and your max integer will display 25.  In the original patch it would be better to include a max float box too, to keep things honest.  I don't believe there's any change here from Live 9 to 10.

2) Just helping isolate this a little more.. if you record a clip with automation from the live.dial in Stephen's initial patch and you induce the bug while recording automation (e.g. live.dial shows 0 but the max integer box shows 3), when you play back the clip, you'll see that the 3 got recorded into the clip rather than the 0.  During clip playback, the live.dial shows 3 (as the 3 is what got recorded into Live) too.  The fact that the mouse movement to 0 never got recorded seemed interesting to me...

 3) Turns out the problem is quite easy to reproduce with a buffer size of 2048, and quite difficult to reproduce (I only succeed once) with a buffer size of 32.  It seems progressively easier to reproduce at higher buffer sizes.

   3b) And after isolating the impact of buffer size on this issue...  I can reproduce similar behavior in Live 9 at buffer size of 2048.

This doesn't technically mean that it didn't get worse in Live 10, but if it did it may be much harder to quantify how much worse.  So, Stephen, do you see the same thing I do when changing buffer size?

thank you for your reply, this thing is driving me nuts. 

 1) the int vs float issue is not part of the problem, because i'm doing the test using the mouse on a live.slider that is set to int both on Type and Unit Style parameters. 

2) it is interesting, might lead to a solution?

3) the audio buffer size seems to make the difference. I've not been able to reproduce with buffer size 64, but with 256 I can (in Live 10).

3b) I can confirm that the issue arises with buffer set to 2048 in Live 9

the Live 9 vs Live 10 issue is real, because the exact same patch in both versions behave differently. But that is with buffer length higher that 64. Unfortunately, I cannot keep the buffer length at 64 all the time, unless i'm doing fairly simple synthesis and compositions.

Stephen can you confirm the buffer length condition?

Yes I can confirm the buffer length condition! Sorry I've been away from my computer for a few days.

With Live 10 it doesn't happen until i get to 512 buffer size and above.

With live 9 it seems to only happen on 2048. 

This all makes a lot of sense. I recently switched from mac to pc and downgraded my interface so I've been running Ableton and Max at higher buffer sizes than before.

I'm surprised no one else has reported this issue, certainly people just aren't noticing right?

Are you using PCs? I could've sworn I've run M4L (Live 9) on a mac at 2048 and have never had this problem.  My Mac is toast or I would test it.

Hey guys, from another thread:  "Answer I got for the bug report (posting for others who run into this): this is a known bug with no workarounds. But lowering the audio buffer size will reduce the problem."

https://cycling74.com/forums/live-numbox-bug-it-doesn't-send-the-value-it-displays/replies/1#reply-5aede0ee0cac2704f3405db0

this issue is bringing back the Mac / PC polarization, because it seems to be something that affect only PC's. I need to get my hands on a Mac again to test it, unfortunately my current Mac is 10 years old and I suspect it won't run well TouchDesigner and Ableton Live with Max at the same time.

Rui, I'm running on a Mac and still encounter the issue.

not saying it's pretty, but this could be a workaround if you're desperate.
It uses an invisible 'vanilla' number on top of a live.number

The same occurs with live.dial for the Pitch used in OscA an OscB of Oscillot by Ableton. Meaning: if used with Live 9/M4L 7 everything is working fine. If used with Live 10/M4L 8 the knobs are displaying wrong values when changed from Semi to Free. The knob seems to be frozen. I might has to do something with integer an float and the parameter shows up different in the inspector window. Reported this to Ableton support.

Any news on this? I'm using Live 10 and can't run lower than a 1024 buffer size and this is getting pretty annoying. 

The problem really lies in the interaction with Live, because I'm not encountering that problem when creating a new live.dial or live.slider. Only when the file has been saved and therefore the new objects integrated with Live will they start outputting wrong values.

Tried to deferlow the automation output ? 

live.numbox/slider/dials that are automated as floats but display as 'Int' have a display number that is always rounded to nearest integer.  So if the value in your live.dial is 25.7 the dial will display '26' and your max integer will display 25.  

Do you happen to know if that is documented anywhere? Or is that just what people have observed?

For peace of mind, I would like to get some precise information on this, as my patch depends on how this works. 

In my observations, it does, indeed, seem to be the case, although even when display is set as "float" it still displays a rounded float number, when the actual number is an unrounded float. 

Thank you for the reply. That is a nice demonstration of how floats are dealt with, but what I am still missing is whether live.numbox/slider/dials that are automated as floats output with consistency.

See this patch. To reproduce the issue, add the device to an audio effect rack, and map the dial to the audio effect rack's first macro.

On my machine at a buffer size of 2048 and a sample rate of 48000, when I set the audio effect rack's dial to 2047, the number displayed in the Max patch's number box is 2046.999878.

What I want to find out is whether the numbers Max gets in these cases always round to the value shown in the mapped macro. From what I can tell, that seems to be the case, but some more clarity and certainty would be nice. If that is the case, then I can simply round the value in Max, and I will know that the rounded value will match the value shown in the mapped macro.

seems its only a problem is when the macro is set by mouse.

but its perfect when you set the Steps to the Steps of the Dial

Well, I'll be darned, that did the trick! THANK YOU.

I looked at the Steps parameter, but it never occurred to me that it would be necessary for this, as I assumed the default would be one step per range value. 

FTR, the "issue" happened to me even when I set the dial's value with my keyboard. 

Problem with live.dial, live.numbox, and live.slider

chapelier fou

I've been toying with this idea of a "contextual mapper" in M4L. 

The basic concept is to store and recall presets of bindings from a single MIDI CC to different parameters in Live. So depending on the context the same controller encoder would control this or that parameter.

- get the value, the min and the max of the new grabbed param

- scale the value to the 0-127 for the MIDI controller

- scale the MIDI controller value to the param min/max. 

here's a patch that seem to work on edit mode, but can act weirdly in "normal" mode when the editor is closed. 

To test, first map two different params with the store messages. Then you can toggle between the two controls with the toggle box. The dial controls the param. 

PROBLEM : if you store two params with different ranges, e.g. a send (0. 1.) and a pan (-1. 1.), and stupidly click several times on the toggle and don't even touch the control dial, you'll see the pan increasing by itself. The problem does not occur in edit mode.

grab_and_control 0.01.amxd

I've been toying with this idea of a "contextual mapper" in M4L. 
The basic concept is to store and recall presets of bindings from a single MIDI CC to different parameters in Live. So depending on the context the same controller encoder would control this or that parameter. 

basic function under the hood would be : 


- get the value, the min and the max of the new grabbed param
- scale the value to the 0-127 for the MIDI controller
- scale the MIDI controller value to the param min/max. 
- control the param from the controller. 

here's a patch that seem to work on edit mode, but can act weirdly in "normal" mode when the editor is closed. 
To test, first map two different params with the store messages. Then you can toggle between the two controls with the toggle box. The dial controls the param. 
PROBLEM : if you store two params with different ranges, e.g. a send (0. 1.) and a pan (-1. 1.), and stupidly click several times on the toggle and don't even touch the control dial, you'll see the pan increasing by itself. The problem does not occur in edit mode. 

help-m4l-patch-working-when-in-edit-mode-acting-weird-when-loaded

Wouldn't there be some rounding errors from floats/int infinitesimal stuff not visible on a side but growing fast on another?!

Yeah I suspected that but : 
- the first value jump can be quite big
- this doesn't explain why it's working ok in the editor.

I get Error
live.remote~: "normalized" is not a valid attribute argument, in Max 8.5.6.
Is the patch for Live 12?


@double_UG 
sorry for this, I'm using L12 indeed. I'll post an updated version asap. I'm not even sure why I used the normalized attribute, but maybe simply removing it works...
Edit : removed the attribute, patch still functional, updating the first post.

Well, 
I'm really sorry, I realize that the patch also uses [live.map] so it's not possible to test if you're not using Live 12 beta. 
I'll try to make it work on L11 and come back here. Sorry for the bother. 

UPDATE : 
To understand my issue I've made the simplest patch possible that illustrates it, and also posted a video. 
My guts say that the problem comes from the fact that there are timing issues between  [sig~] and the switching of targets. Any thoughts ? 

check your order of execution, you set the new value while remote~ is still mapped to prev parameter.
A simple fix would be to reset the remote~ before switching. Generally you could filter the output to remote~ when you are only updating the visual state of your dial. 

Thanks ! 
It does indeed fix the value changing when switching targets...
However, if I save the set while something is mapped, then reloaded, it still loads with the wrong value.

--------------------------------                                                        

Thanks double_UG ! 
I didn't think of just automatically releasing the parameter, that's so simple en brilliant. 
(Also tried to remove persistent mapping before, didn't make any difference). 

or use live.object with set value, if you don´t need audio rate.

Help : Dynamically changing live.remote targets problems

benniy

i have a patch with multiple instances of the same bpatcher.

i'm trying to give a [live.dial] in each of these bpatchers a unique name (such as "dial 1" for a dial in the first instance, "dial 2" for a dial in the second ...).

Cycling '74 Forums

A while go I tested loading of protected aif samples from live packs into polybuffer~ using live.drop -> append $1 message. It allways ...

you mentioned all problems allready. I see 2 options as non live user. 1 make max app that acts as xbox hid to midi and create c.surface ...

@zack you could call this simple function i wrote. It works well.

Hi there, Apologies if any of this is basic knowledge, I'm still a relative newcomer to Max/MSP after being introduced to it in a college ...

Thanks for the good news! I'm excited to see where things go :-)

Might there be an easy and inexpensive way to calculate it? By, say, passing a signal across some objects and measuring?

Hi OCH ! Did you find ? I seem to remember seeing someone do this before but I don't remember who or how... From memories it was ...

but its perfect when you set the Steps to the Steps of the Dial Well, I'll be darned, that did the trick! THANK YOU. I looked at the Steps ...

Edit : nevermind, getting tired.

what do you mean "pass to a thispatcher"? I don't think you can send "varname" to a thispatcher