Asher Bay

The docs for MaxobjListener, ParameterListener, ParameterInfoProvider, and the Require/Include Guide are each missing from the JavaScript in Max page. Are these features being removed from Max's JS library or will the docs be restored at some point? 

The docs for MaxobjListener, ParameterListener, ParameterInfoProvider, and the Require/Include Guide are each missing from the JavaScript in Max page. Are these features being removed from Max's JS library or will the docs be restored at some point? 
Thanks 

The docs for MaxobjListener, ParameterListener, ParameterInfoProvider, and the Require/Include Guide are each missing from the JavaScript in

missing-javascript-documentation

@ASHER I see all of these listed on the JavaScript in Max page in the Max 8.2.0 documentation. What version are you running?

https://docs.cycling74.com/max8/vignettes/javascriptinmax 

I see that we have some issues with rendering the online documentation (which we are looking into), but these should be available in-app.

Missing JavaScript documentation

billyanok

I'm looking for anyone on the list who is using AppProtect or QuickLicense from Excelsoftware?

I've been a satisfied user for a few years now but have a few questions regarding standalone apps use with OSX Catalina and Big Sur.

Hey, 
I'm looking for anyone on the list who is using AppProtect or QuickLicense from Excelsoftware?
I've been a satisfied user for a few years now but have a few questions regarding standalone apps use with OSX Catalina and Big Sur.
Thank You,
Bill

Hey, 
I'm looking for anyone on the list who is using AppProtect or QuickLicense from Excelsoftware?
I've been a satisfied user for a few ye

excelsoftware-copy-protection-users

Hi @BILLYANOK,
we would try the Excelsoftware protection for our software . You write you are "a satisfied user" did you use the Excel with new version of max - 8.1.8 for example ?
And did you find the answers for your questions about OSX Catalina and Big Sur?

Excelsoftware copy protection users?

darkInteger

Is there a way to resize panel in presentation mode with a message?

Hi guys!
Is there a way to resize panel in presentation mode with a message?

resize-panel-in-presentation-mode

Yes, it is possible: use "Presentation Rectangle" attribute (via the attrui).

resize panel in presentation mode

Ena Brennan

I am looking for the correct Arduino code to send two BPMs to Max. I am using two pulsesensors and require the BPM of each of them. I have found useful info to connect one sensor correctly but having difficulty connecting two. My setup is identical to this one: https://pulsesensor.com/pages/two-or-more-pulse-sensors and I am using Max For Live to create FX on audio files using the heart rate data.

I am looking for the correct Arduino code to send two BPMs to Max. I am using two pulsesensors and require the BPM of each of them. I have f

reading-data-from-2-pulsesensors-via-an-arduino

upload that working code for 1 sensor.
Usually one can simply double the code for single sensor
using for example pulseSensor1 and pulseSensor2


Reading data from 2 pulsesensors via an Arduino

nick toe

I just learned that it's possible to use max inside of Ableton Live. 

I decided to make a simple patch that has one dial with an option to map it to a parameter in Ableton.

I spent an entire day in the search of the solution but could not find anything how it can be mapped.

I just learned that it's possible to use max inside of  Ableton Live. 
I decided to make a simple patch that has one dial with an option to map it to a parameter in Ableton.
I spent an entire day in the search of the solution but could not find anything how it can be mapped.
Any ideas how it can be done?

Thanks

hey there
I just learned that it's possible to use max inside of  Ableton Live. 
I decided to make a simple patch that has one dial with an 

map-button-plus-dial

You'll have to spend a little time learning Max, and some particular time working out how the Live Object Model lets you access and control Parameters in Ableton Live. That's not necessarily an "I did it on my lunch hour" undertaking. 

That said, here's a patch that demonstrates one way of doing it, based on the work of my genius colleague Manuel Poletti, whose example patches in the Max for Live tutorials built into the Live Application you should already be studying. 

I'll leave it as an exercise for you to work out what's going on as you study Max and the Live Object Model. Good luck!



Hello Gregory,
I tried to understand the patch you gave, and it seems to work. But when i use it in Live 10, i've got a problem. The patch is working in boolean "style". When i turn the patch's knob, the mapped one is only going min or max. And when the knob is over 1, the other one is just stuck to max.
Could you help me please ? Thanks :) 

Ableton provides a free M4L pack with lessons and example devices for learning from (when you leave presentation mode the devices have notes telling what stuff does):

https://www.ableton.com/en/packs/max-live-building-tools/

Hi, there's a map boutton on some patch, that allows to grab a parameter from live and assign it to an m4l Fonction, but on live 10 some old patches using this funtion don' t work anymore, coud someone post a mapping boutton update? or any infos to make it work?
thanks a lot !


For others stumbling into this thread - open the inspector for the live.dial - you can change the range and unit style to whatever you need (on this pasted patch the range is 0. - 1. and the unit style is float)

(whoo I finally got to contribute something to these forums!)

Hey fam!

This was so much more complicated to nail down than I wished for. I always kept coming back to this article without leaving with any new insights. I decided to make a tutorial on exactly this after lots of help. How to build your own working M4L mapping button doesn't have to be a mystery anymore.

I really hope this helps anyone who found themselves in a similar position to me last year. Ideally as a beginner, it is much easier to be able to explore the techniques and device ideas you want to without getting hung up on an issue like this... Happy patching!

https://www.youtube.com/watch?v=Wy3SYumK5Vg

Hello,
for those who need a vey cheap and easy way to achieve that, there is the "view selected_parameter" in the LOM. It's working for every device and track parameter.

Just click on a parameter in your live.set
move the dial.

If the parameter you want to control doesn't have a 0. 1. range, 
you can use this another version.

map button plus dial

schlam

Sorry, I have some lack in some basic maths...

how to dynamically select only the outputs of the slider that are the division of 128./X

If I change X to 3, the slider only outputs : 0. / 64. / 127.

the "step" attribute seems to do not be a solution here because I need that each value can be triggered several times. 

This slider is mapped to an expression pedal.

If the slider has 3 positions, the pedal should trigger an event when it is totally down / totallu up / at middle position. And only at these positions.

With the "step" attribute, it's working but if I hit several time the 0 position of the pedal (and never go after 64) the sound is triggered only the first time because the slider "don"t understand" as a change a value which is not 0 , 64 or 127..

a/ I divide 128 by X and create a list where this value is added to itself X times

b/ the slider feed a scale object with the max output value set to X

c/ a zl sect object is feed with a/ and b/

I am sure it's easy but I find only not very elegant solution..

- I have a dynamic value X,
- a slider (range 0.127.)

how to dynamically select only the outputs of the slider that are the division of 128./X


If I change X to 3, the slider only outputs : 0.  /  64.  /  127.

the "step" attribute seems to do not be a solution here because I need that each value can be triggered several times. 
This slider is mapped to an expression pedal.
If the slider has 3 positions, the pedal should trigger an event when it is totally down / totallu up / at middle position. And only at these positions.
With the "step" attribute, it's working but if I hit several time the 0 position of the pedal (and never go after 64) the sound is triggered only the first time because the slider "don"t understand" as a change a value which is not 0 , 64 or 127..

Not sure if it's very clear.. sorry



for now
a/   I divide 128 by X and create a list where this value is added to itself X times
b/  the slider feed a scale object with the max output value set to X
c/  a zl sect object is feed with a/ and b/





 I am sure it's easy but I find only not very elegant solution.. 

Sorry, I have some lack in some basic maths...
- I have a dynamic value X,
- a slider (range 0.127.)

how to dynamically select only the out

noob-math-question

For now it's working, but it seems a bit complicate...


In case I understand what you want ...
which might not be the case without seeing the patch and
understanding the purpose of output values .

This theoretical thing will never work well in practice,
because you will produce too many unwanted "hits"
if really using expression Pedal with more divisions.
What if you want to hit top (127)  and then bottom (0), without executing the middle value ?
Trust me, it is going to stress you to get the values right with the pedal.
Even if you set up some rules, like pedal has to remain for 100 ms
in the range to trigger the value, it will stress you to get the timing right.
In theory one could make a multy switch out of a slider, but one would need
a clever division of ranges, safe areas of values between the trigger
ranges, and some sort of speed of movement detector to allow
crossing of trigger ranges without executing them, to be able to 
jump instead of slide between the trigger points.

-----------
But let's take it the way it is.
you can't divide range 0 - 127 with equal slices of arbitrary divisions,
because you use ints and not floats.
So you would prefill a list with closest "hits"
for selected division.
let's take 5 for example :
you want 0 and 127 to be lowest and highest "hits", and so need equaly positioned 3 more
"hits" in the middle 32, 64 , 96 (128 / 4 = 32)
now your list is 0 32 64 96 127.
as you say you use zl sect, then it should output the values when you
match them with the pedal.
To the next problem - retriggering same "hits"
simply go a bit above or under the "hit" value and cross it again...
No need for scale object...

thank you !
It's not a problem here for me if "64" is eachtime triggered when I go from 0 to 127 and vive versa.
Did you see the patch I posted just before ? It's almost working...



some random bits:

 - mapping a range to an integer range in practice often involves either truncation or rounding at one point. 

 - this is can (like probably here, too) involve truncation or rounding in steps of more than just "1".

 - when i need to do something like that i usually start with 2 messageboxeswith some example values for the desired in- and output so that you see it side by side. the algorithm is not far then.

 - you called it a "math" problem. in fact there is a lot of logic and data formatting involved in this kind of jobs.



"you can't divide range 0 - 127 with equal slices of arbitrary divisions"

this often happens to people when you come from midi.

the solution i usually implement is to clip the original range.

example: how to divide up a 7-bit controller range into 5 equal spaces? - by simply not using 125, 126, and 127.

0-127
split 0 124
/ 5.
* 1, * 2, ....

all unavoidable-in-int inaccuracies are now shifted f.e. to the upper end of the physical modwheel - but you code is clean: all sections are of the same range.

p.s.: 
and in schlam´s original patch you should at least do all calcualtions in float, then round to integer, in order to get nearer to the best possible values.


No, I did not see the patch before responding.
What is not working for you in the patch you posted ?

I don't use live , so can't say much about it's problems.
I see you inserted that everynumber thing, is it because live.slider sucks ?
And... if you don't want to recalculate that values all the time,
you can fill umenu with premade lists .


round used that way is a perfect choice to
split the slider range.
But to pick only selected values one needs
sel or zl sect.
Round can be well used to create the list
for zl sect


thank you all. I, thought my patch was too complicated for that purpose and that I missed something essential.. but it seems not =)
All is working as expected , just sometimes there is a problem after the thresh where the list sometimes is doubled "0 64 127 0 64 127" for example. So I choose to replace it with a dynamical [zl group].

The final device is here.
It allows to choose any clip in Live and the slider will "scrub" it all the way long. It can be fun
The main idea was to use that with a drum clip and to play this clip only with one foot for a human band project. Of course it's  fun with melodies too, there is interesting results when the slider is mapped to an LFO wave or random..

for information the [p everynumber] in this patch was created by Chris Muir and found in this forum, it's a great little utility that never skips a value even if you move a controller very quickly.

... but it does not let you click directly and output only clicked value.
if you click 127 and then 0 , you will get all 128 numbers from 127 - 0 out.
Which might cause trouble if recipient is some heavy loaded stuff.
It won't output number if input unchanged.
So take care when inserting such things in the path.


Yes !  Thank you for your advice. I only use that when the slider is controlled by an hardware knob or pedal when I need to select a precise value of the course which can be skip without that if I move it quickly. 

Actually midi input should not drop a single int from a stream.
Only Max GUI objects like sliders or numboxes etc produce drops
when moved by mouse.
Maybe even worse with Live  objects ?
Uzi to midi out and back in does not drop a single number.
Not with IAC Bus


And also not with old Motu midi interface


one could build a patch which fills the missing numbers back into the stream. 
but i´ve never did that because for what? ;)

if you do it, you will rather do it by an interpolation function over time.


Does this do what you want, in a simpler way?

Voila !
Yes ! I was sure it should have a very easier way to achieve that ! Thank you Nick
The only problem is that the slider is continuously outputting the current data when you move it.

In my case a simple [change] cannot be a solution because I need that each value can be triggered several time even if it doesn't change...



If you decide to use round  and change object,
then you need some retrigger option.
A simpe one would be to use inc - dec split to reset change object
whenever Pedal changes direction within same range.
Example :
you use 7 numbers - actually 6 ranges
0 21 42 64 85 106 127 
you move pedal from 0 to 28, and  so trigger 0 and 21
now every time you change pedal direction and remain between 21 - 41
you will retrigger 21.


because I need that each value can be triggered several time even if it doesn't change...

It's not completely clear to me exactly when you do want the output to change, so I'm guessing a bit - here is a simple solution that triggers every time the value changes and also (re-)triggers each time the pedal hits either end of the its travel;

Thank you again Nick !
almost that ! I was looking for an easier way than the last patch posted to do exactly what your last patch does, but for each value. It's that but every choosen values (number depending of the number) could be triggered like behave the 0 and 127 in your example.


@Source audio
sorry I didn't see your post.

 another elegant way! 
thank you


noob math question

johnisfaster

I'm having trouble reconciling these two patches so that I can observe the currently playing clip name of whatever track the device is on.

getting-current-playing-clip-name-of-this-devices-track

That device will give you the name of whatever clip is playing in the track the device is on.  That way I can trigger events in my max patch with clip names :)


Sorry to ramble on if no one is interested but I found that naming my clips with a simple number was problematic because the device was converting the number to "1" instead of 1.  So I added a fromsymbol to make it back into an actual number.

This is all because I want to be able to use clip names to select multislider presets.  I'm just sharing it here cause I can't imagine other people wouldn't find it useful.

Heres the version that fixes the number output.

I'm very interested in your patch because i want to convert those clip names into Program change messages...
But I'd like to send those PC without launching the clips, i.e just by selecting the row that goes with each scene. 

Ex: Track 1 and 2 are midi tracks that sends data on channel 1 & 2.
I select the scene 1, it sends automatically the clip names converted in PC into the max patch in the corresponding row.

It would allow me to sends PC without playing any clock...

This is how I do it with JS for the currently selected track.. the function below receives the playing clip index (currentClip) and outputs clipName.

var currentClip = null;

// Get Clip Name
function getClipName (currentClip) {
	var liveSet = new LiveAPI (dummyCallback, 'live_set view selected_track clip_slots ' + currentClip + ' clip')
	var clipName = liveSet.get('name');
	outlet(1, clipName);
}

function dummyCallback (){}

This is the code in my other patcher that sends the currentClip value:

// Get Playing Clip
function getPlayingClip() {
	var selectedTrack = new LiveAPI("live_set view selected_track");
	var playingClipIndex = selectedTrack.get("playing_slot_index");
	outlet(1, playingClipIndex);
}

Thanks for the patch. Realy useful to me ! 

I'm looking for a way to do that in the arrangement view to send OSC trigger to another daw at specifique timings but I don't find the property which gives "the name of the current playing clip" or something like that.  

Maybe you have an idea to help me ? 

getting current playing clip name of this devices track

cpincock

Can anyone tell me how to set the unit style of a live.numbox using scripting messages?

setting-live-numbox-unit-style-via-scripting

Setting live.numbox unit style via scripting

ANDRE SBROCCO

I want to save and retrieve preset files for vst, vst3 and audiounit plugins.

I have made a patch to illustrate my problem. Please follow the steps inside it to see by yourself.

reading_writing_vst_preset_files.maxpat

After several tests, I didn't find a workaround. In fact, it seems to be a bug in the vst~ object. Am I doing something wrong here?

The goal: I want to save and retrieve preset files for vst, vst3 and audiounit plugins.
The problem: VST3s fail to "read" a saved preset.

The goal: I want to save and retrieve preset files for vst, vst3 and audiounit plugins.
The problem: VST3s fail to "read" a saved preset.
I 

problem-with-vst~-preset-writingreading

I think this was fixed in the version 8.20

vst~ not reading .vst3preset file

Brendan McCloskey

My old Focusrite Saffire USB card drivers are not compatible with my 2020 Macbook running Big Sur 11.5.2. Could someone please recommend a few lower end soundcards, that will work under Big Sur:

USB power, works with USB-C converter, maybe 4-in/4-out, must have 5-pin MIDI in out. Old school ;)

Hi Maxers!
My old Focusrite Saffire USB card drivers are not compatible with my 2020 Macbook running Big Sur 11.5.2. Could someone please recommend a few lower end soundcards, that will work under Big Sur:
USB power, works with USB-C converter, maybe 4-in/4-out, must have 5-pin MIDI in out. Old school ;)

Pref around 200 £,$,Euro
Thanks
Brendan


Hi Maxers!
My old Focusrite Saffire USB card drivers are not compatible with my 2020 Macbook running Big Sur 11.5.2. Could someone please re

'budget'-soundcard-recommendations-for-big-sur

. . . I mean, is Focusrite Scarlett my ONLY option??

It's an annoying behaviour of companies to refuse to update their drivers, not? It cannot be so demanding. 
I had to trow away perfectly working stuff every now and then just because of those self made "incompabilities". 

Well, Focusrite Scarlett units seem almost ubiquitous, and probably for good reason. I have Scarlett 18i20 and I'm very happy with it. I've used 2i2s and 4i4s and they all seem to get the job done with no fuss. These things are best when you can stop to even think about them, right?

There are other choices; I have a Native Instruments Komplete Audio 6 (which closely matches your requirements, I think). The controls are on top, so for portable desktop use, its maybe more ergonomic than the Scarletts. On the negative side, its in a plastic housing, potentially not as robust as others. Also, the headphone output is a little quiet with high impedance headphones - but this could well be true for any USB powered unit.

Arturia have a new range out too. I haven't come across any yet, but I have other Arturia gear, and its generally well designed made. That said, just checked their website, and the unit you might want doesn't ship until next year.

I don't know if they have new drivers, but I've been really happy with my Steinberg UR22MKII as a cheap, portable usb audio device. I bought it to use when I didn't want to cart by big one around and it's been great.

'Budget' soundcard recommendations. For Big Sur.

Ben Bracken

. The Runner provides plug and play access to a 

 from the Max application, using using OSCQuery for communication with the running code.

This update features a new web-based interface with routing capabilities, expanded hardware support, along with many other improvements and bug fixes. Improvements include:

We've also rolled in direct support for the 

 add-on package, and have included a number of other improvements and bug fixes. Check out the release notes 

We are happy to announce the release of RNBO 1.3.0, available now for download via the Max Package Manager.

With this update, we are...

rnbo-130-released

RNBO 1.3.0 Released

We are excited to announce the availability of our 

 as a public beta. We’ve worked closely with 

. The Eventide H9000 is a rack-sized multi-effects unit with powerful DSP processing capabilities and numerous high quality built-in effects. We’re excited to enable RNBO export for this and open the door to unique custom studio effects and instruments without the strict limitations of other hardware platforms.

RNBO support is similar to the existing Gen support, but more streamlined, and uses the built-in 

, rather than a watcher patcher, to manage the export process. Eventually, all of these changes will be rolled into the standard release versions of RNBO and this package.

Get the preview version of the RNBO package (v1.2.7-eventide.0):

Get the preview version of the "Eventide H9000" package (v1.0.4-beta.3):

We’d love to hear any experiences and feedback from RNBO users with access to an H9000. To join the discussion, use the 

We are excited to announce the availability of our Eventide package for RNBO as a public beta. We’ve worked closely with Eventide to bring...

Cycling '74 Forums

We are happy to announce the release of RNBO 1.3.0, available now for download via the Max Package Manager. With this update, we are...

We are excited to announce the availability of our Eventide package for RNBO as a public beta. We’ve worked closely with Eventide to...

I see that we have some issues with rendering the online documentation (which we are looking into), but these should be available in-app.

Hi @BILLYANOK, we would try the Excelsoftware protection for our software . You write you are "a satisfied user" did you use the Excel with...

Hello Darkinteger Yes, it is possible: use "Presentation Rectangle" attribute (via the attrui).

upload that working code for 1 sensor. Usually one can simply double the code for single sensor using for example pulseSensor1 and...

Hey fam! This was so much more complicated to nail down than I wished for. I always kept coming back to this article without leaving with...

@Source audio sorry I didn't see your post. another elegant way! thank you

Hi :) Thanks for the patch. Realy useful to me ! I'm looking for a way to do that in the arrangement view to send OSC trigger to another...

Can anyone tell me how to set the unit style of a live.numbox using scripting messages?

I think this was fixed in the version 8.20

I don't know if they have new drivers, but I've been really happy with my Steinberg UR22MKII as a cheap, portable usb audio device. I...