leaozinho

I have a M4L device that I built to be able to send different data to multiple MIDI channels.  Stupidly, I didn't realize that when you put a device on a channel in Live, that channel can only output MIDI to one MIDI channel.  I've heard there are M4L devices that can send out data to multiple channels without using multiple instances on different tracks - does anyone know how to do this?

I have a M4L device that I built to be able to send different data to multiple MIDI channels.  Stupidly, I didn't realize that when you put 

using-a-m4l-device-to-send-data-to-multiple-midi-channels

use send or forward and receive without "---" 

Thanks, Double_UG, though I can't really figure out what you mean here - could you elaborate a little more?

Maybe I should be more clear: my M4L device outputs different MIDI data on 4 different channels that will be routed to 4 different instruments (e.g. Channel 10 outputs data to Instrument 1, Channel 11 outputs data to Instrument 2, etc.).  The problem is that all this MIDI data from M4L gets routed through one channel in Ableton, so it's impossible to split it into separate streams to get to the individual instruments.

send your Midi with "send" or "forward" to the  a receiver m4l device. Put the receiver device in front of the instrument.  The midi is send in Max from sender to reciver device. 

@DOUBLE_UG  Oh man, thank you so much for those devices. I couldn't find anything on maxforlive.com. The're so useful. Have a nice day :)

Using a M4L device to send data to multiple Midi channels

johannes

hello, 
anyone knows if there already is a arm64 compatible version of the  shell external  available?
best, johannes

shell-external-arm64-compatible-version

https://github.com/jeremybernstein/shell/releases/tag/1.0b3

shell external - arm64 compatible version?

Jean-Philippe Jullin

I'm looking to dynamically load sounds into a buffer using poly~ during a live performance. I don't want to use polybuffer~ because I want several hundred sounds to be accessible, but as they last between 30sec and 10min each, the total is about ~30GB.

The thing is that I use a coll to know whether a sample is already in one of the instances. When an instance is free, it gets the sample ID I want to play, write in a coll that this sample is loaded (I just add 0 to the entry to close a gate for the next time this number is seen). When the sample has been played, it is supposed to delete the entry in the coll.

And here is the sub patch used in poly~ (you can name it _player)


The thing is that everything seems to be working fine, until I start to be frenetic (which will obviously be the case live). Some weird numbers get inside the coll, some entry are numbered by numbers never sent, and I often even have multiple entries with the same identifier: 
40, 0;
40, 0;
40, 0;
40, 0;

To replicate, you can drop an audio folder and click Play Random. If you wait for the sample to finish playing, the corresponding ID in the coll should be deleted. But if you click Play Random several times, some entries remain in the coll. If you check whether some numbers have been sent or not, this is usually not the case.

Am I facing a threading problem? Where are these numbers coming from?

Hi everyone,
I'm looking to dynamically load sounds into a buffer using poly~ during a live performance. 

dynamic-buffer-loading-using-poly~


i suppose you didnt take into account that readong from disk and/or freeing the buffer is not thread safe and then at some position message order gets lost. did you debug it yet?


you should redesign the whole thing.
replace random with urn and it will not repeat genearted number till all
get output.



@Roman Thanks. I didn't know about the thread safety issue. 

@Source Audio The thing is that random here is just for demonstration purpose. The sample request will come from a pre-analyzed map of all the samples that I navigate.  The idea is to load in buffer the 10 nearest points only, and once a sample is loaded I don't want it to be loaded again. 

I tried to get out from the poly~ the availability checker, and simplified the patch but with no success. Still unseen numbers getting inside the coll. 

How would you keep track of loaded samples inside a poly~, while knowing if it has been freed or not?

get all colls out of poly subpatchers and keep only 1 coll in main patch.
send all messages to poly instances using target messages, which will then be stored in coll,
like index 3 means target 3 (poly voice 3), then insert sample name to know it was loaded
into that voice.
when target finishes playing you do whatever you want with that information.
it is trivial task to do so.
To exclude samples from "available" list - there are soo many ways to do that,
but I won't go into options without knowing exact & simple
layout of what you want to achieve.
I can't really follow the whole logic and what should be random etc




@source audio Thanks. I think I finally found it.

The problem seems to come from the delete message sent to coll. I don't know why, but it seems that it adds random numbers inside the coll when there is a lot going on.

Here is some kind of solution, pre-adding all samples ID and turning them to 0 when they are loaded.

Dynamic buffer loading using poly~

David Zicarelli

Early next month Cycling ‘74 will publish our second book, Generating Sound and Organizing Time: Thinking with gen~ Book 1 by Graham Wakefield and Gregory Taylor. I sat down with Graham and Gregory to talk about what’s included in the book and the collection of patches that accompany it.


Let’s start by talking about how this book project happened. What were your goals in writing it?

Graham: Personally, most of all I wanted to write the kind of book I wish had existed when I was learning about making computer music. For example, in my graduate studies I learned a huge amount about programming synthesis processes, but I also realized that a lot of the immense possibilities of digital signal processing is often obscured in writing and inaccessibly black-boxed in most music software -- in fact that's part of why creating gen~ became my doctoral research; gen~ opens up access to live edit sonic algorithms right down to the sample level, kind of like an atomic structure of DSP. And we think it can be a lot simpler and more insightful that way, and for the most part it doesn’t require learning higher mathematics or coding.

Gregory: gen~ is now over ten years old, and with a thriving community, but it's still unfamiliar to many, and we wanted to change that. As our friend Luke DuBois said, it's "one of Max's secret weapons hidden in plain sight." We thought the best way was to start from this idea of a bestiary of simple and reusable ideas that can be recombined to make new things.

Graham: Right–it's not always obvious, since not a lot of music software lets you work at this level–but so many synthesis and sound processing techniques come down to a pretty small number of common circuits and patterns operating at the sample level that are then reapplied in a variety of different ways. This book (and gen~ itself) is all about the amazing things you can create when you can patch at this level.

In that spirit, we wanted to present the repeated application of a few simple ideas to many different musical tasks. All kinds of things from filters and delay effects to oscillators and granular synthesizers and chaos generators and so on that sometimes look like black boxes or magical plugins. But when patched in gen~ these are just arrangements of the same small number of simple operations – which means you can dig into them and insert other stuff in there and experiment wildly. In the book we build upon these to create a set of abstractions that we use again and again throughout the book to do all of these interesting things from really simple beginnings.

Reading the book as a Max user, I definitely felt like I was getting a gen~ education but at the same time, I’m being exposed to a completely new way to think about musical DSP applications. Can you talk about the intended audience(s) for the book? Would it make sense as a textbook?

Gregory: One of our early readers put it really well: They said it was "for composers, musicians, sound designers, and experimentalists of all kinds.” We’ve tried to provide a wealth of things that people will find interesting and engaging and to create a book that can serve equally well as a kind of patching companion for self-study or as a text for educational situations. I think that using the book as a classroom text with a bunch of curious and creative students would be a lot of fun.

And inside of a classroom or out, there wouldn’t be a lot you’d need to get started. It could be helpful to review the gen~ for Beginners tutorial series.

Tell me about the phrase "Thinking with gen~” – I’d be interested in hearing your perspective on the software as something you think with.

Gregory: Glad you noticed that preposition there! It’s really about developing ways of thinking and building that solve problems or lead you into new territories of signal processing.

Graham: On the one hand, it’s building up habits to let you ‘think out loud’ through patching, leaning on the ability to edit and hear the results right away, like a notebook that makes sound. That means you can try out ideas on a whim, and maybe discover something amazing and unexpected. But it’s also about getting to be thinking with the behaviors of signals, and how they can be wrangled, morphed, and interwoven, chopped and regurgitated at the sample level. That means designing subcircuits such that a momentary idea of “why not plug B into C” is more likely to lead to something interesting. So along the way it’s also about thinking with little circuits as building blocks, building a lexicon of reusable ideas with a huge range of capabilities. Inserting one process into the midst of another is such a common habit of thought for the book.

Gregory: … and there are a few other habits and techniques we use again and again, like translating a problem into some other representation that makes it way easier to tame and control, or using the behaviors of harmonic and inharmonic ratios to create complexity in sequences, smoothed quantizers, and timbre shapers, and so on.

Gregory: We wanted to encourage thinking of cyclical “time” as having a modular nature: by using ramp functions instead of individual triggers. Starting from a ramp, we show how to create sample-accurate rhythms, modular patterns, swing, divisions and ratchets, polymeter and phasing, beat chopping, deriving rhythmic LFOs, and so on, all being sample (or even sub-sample) accurate, in a way that triggers never can be. So, time is just another flowing signal to process.

We also see the same basic crossfader algorithm–one of the simplest little circuits really–used to create linear interpolators, filters, smooth step generators, antialiased oscillators, LFO shapes, envelope generators, and many more. And since everything is editable, it’s also explorable. For example, you have a filter algorithm or chaos generator, and you wonder what might happen if you stuck a waveshaper or a delay inside one of the feedback loops — well, you can just crack that patch open and try it.

Graham: Another example is moving calculations into a different space to solve challenging problems. For example, we’re always pre- and post-scaling a signal so you can work with a zero-to-one range, and apply a huge range of what we’re calling “unit shapers” to warp and morph this range as desired, whether for an oscillator or LFO, or for more expressive pitch glides or waveshapers, or for a funky swing to time, all in an algorithmic way that means you can parametrically morph things and derive more variations. And of course you can modulate the modulators and shape the shapers and so on.

Another is making a discrete set appear continuous by crossfading the two nearest neighbors – to make a quantizer or a bitcrusher modulate smoothly, or to make an FM algorithm generate only harmonic tones, or to create morphing multidimensional antialiased wavetable oscillators, or a variable delay without pitch drift, it’s all the same trick. You’ll notice other similar bits of patching like this used in very different situations throughout the book.

Gregory: Along with these ideas, there are a lot of abstractions (including the unit shapers) that we walk through creating and re-use throughout the book. You can think of them as a “next level” of gen~ tools built on the basic operator set. The specific tools in the software we’re releasing to accompany the book extends the modest gen~ operator set in ways that assist users in customizing and making their own abstractions.

I’m sure you’ve seen Forum requests to add a certain feature to a Max external or to set the default state or mode of an object to a user’s personal preference. Leveraging the ability to create abstractions in gen~ provides readers with a simple way to do just that. You can open up the abstractions and examples we’ve provided and easily customize them to meet your own needs.


Maybe this is a good point to mention that the book isn’t just explanatory text and diagrams. What really blew me away is the collection of examples that you’ve created. Can you talk about a few of the treasures people will discover?

Gregory: It’s hard to know where to start. Complex shift-register sequencers – something that Step by Step readers might find interesting — Euclidean rhythms and LFO generators, wave terrains and polygonal synthesis, and a positively insane variety of amplitude, ring, frequency, and phase modulation algorithms that include blended harmonics and chaotic feedback.

Graham: And a wide variety of filters and delay effects, algorithmic quantizers with glides, noise and randomization algorithms, harmonic distortion waveshaping and modulated bitcrushing, band-limited virtual analog and wavetable oscillators, pulsar and other granular synthesis techniques, and more.

Gregory: And you won’t be surprised that I’m excited about the collection of chaotic algorithms…

One of the topics I was surprised to see covered was FM synthesis. I’ve had the impression there isn’t really anything more to say about FM that hasn’t been covered before. Can you give readers a little preview of how you approached this topic?

Gregory: As you might imagine, we spent some time researching the academic literature and community knowhow when we embarked on the project — we knew that nearly everyone was familiar with Max’s Swiss Army Knife abstraction SimpleFM~, and we wanted to go deeper and follow some different paths. Lo and behold, we found a really interesting reply on an old Max Forum posting that FM pioneer John Chowning himself responded to. His advice was — for me, anyway — the start of it all. Graham’s investigations, based on Chowning’s insight and other more current scholarship on frequency modulation and its synthesis cousins, produced a collection of patches that had my jaw on the floor with amazement.

Graham: Well, there’s this general perception that FM is somehow complex or shrouded in a mystique of confusion, but really it’s a lot simpler than that, and we heard from some quite experienced readers that we managed to get several new insights across to them. A lot of existing material on FM does sometimes treat it as a “done topic” and repeats the same old DX algorithms, even though there is so much more that’s possible.

For example, if you AM a carrier with the right window shape, you can get perfectly asymmetric spectra out of an FM or PM patch. Or, one of my favorite examples is a pair of FM oscillators acting as modulators to each other, each going through a low pass filter first – the range of amazing sounds and behaviors that come out of this can sound really analog and is like some kind of more organic chaos to my ears. And yet the patch is so simple. And the bigger point is that there’s nothing stopping you trying sticking other things into these feedback loops to discover something new!

I have to ask one more question – what’s with the “Book 1” in the title?

Gregory: There was so much we wanted to cover, and not all would fit into a single book! I kind of don’t want to be the spoiler here. Graham, what do you feel like revealing?

Graham: In the second book we delve much deeper into some common and uncommon aspects of band-limited oscillators, microsound, reverberation and physical modeling. But we also look at some more unusual and powerful generative algorithms — including a few processes inspired by biological and natural phenomena that are often absent from computer music materials. Stay tuned!

image.png

newcover.png

Early next month Cycling ‘74 will publish our second book, Generating Sound and Organizing Time: Thinking with gen~ book 1” by Graham Wakefield and Gregory Taylor. I sat down with Graham and Gregory to talk about what’s included in the book and the collection of patches that accompany it.

generating-sound-and-organizing-time-an-interview-with-graham-wakefield-and-gregory-taylor-1

Very exciting news! Not long after gen~ came out I stopped using Max, and it always seemed a little daunting to me. Recently I've been feeling nostalgic, and I think this might be the perfect opportunity to rekindle my love for Max, and its community :) 

OMG I want this now! gen just complements other parts of Max. The visual programming style of Max makes glueing UI object and other built-in objects simple and intuitive while the text programming style of gen makes writing complex logic possible.

Generating Sound and Organizing Time: An Interview with Graham Wakefield and Gregory Taylor

Nicolas Hume

Hi,  
How can I send a buffer to arduino by the serial port and then transcribe it to a screen? 
Thank you in advance,


send-a-buffer-to-arduino

[peek~] allows you to get each sample value from a buffer. 
The rest is Arduino stuff I guess, you should look to some Arduino example code probably included in your screen's Arduino library. 

Send a buffer to Arduino

Paolo Piaser

I am experiencing a problem with fold in gen~. If I set feedback values larger than 1.01, the fold object seems to not work anymore. 

Is this expected behaviour or found a bug? 

Hello,
I am experiencing a problem with fold in gen~. If I set feedback values larger than 1.01, the fold object seems to not work anymore. 

"fold"-behaviour

If you wish to use the fold operator with non-vanilla ranges, you'll need to specify them as arguments (e.g fold 0 1.01).

I think I did that. I set "fold -1 1", so it should work, but it doesn't on my side. If I set the feedback > 1, sooner or later the system will "explode" ignoring the fold

"Fold" behaviour

Piet Somville

Hi people ! 
I really want to learn max so, besides watching/reading tutoriel I'm trying to make my own first synth (to have some king of goal). 

So, as you can guess, I've some trouble x) 

- As you can see on my patch, I would like to apply a filter enveloppe (in the right down corner), the think is i would like to choose the intensity of the enveloppe on the filter (as the Env. Mod. on the TB303 but i find no way to do it). 
I think that right now, the enveloppe is playing at 100% on the filter all the time, I want this to be optional. 

- On the top of the patch, I added the object : / 127. on "midi-in" velocity out, I did it without understanding why I did this... If someone can give me more details ? 

- Last, if you have any other suggestion of how making this patch better, I will be really happy to read you ! 

Thanks a lot ! 
Regards, 
Piet 



MyTB303.amxd

Hi people ! 
I really want to learn max so, besides watching/reading tutoriel I'm trying to make my own first synth (to have some king of ... 

my-first-tb303

MY FIRST TB303

Megan Hung

Hi, I really need help. I bought MAXMSP few days ago and tried to authorize it. However, when i click the authorize button, the screen appears blank. I've tried to reinstall several times, and still get the problem. 
Any solution? Thanks

畫面截取 2022-09-30 at 1.10.55 PM.png

Hi, I really need help. I bought MAXMSP few days ago and tried to authorize it. 

i-can't-authorize-maxmsp

Please get in touch with our support to resolve your authorization issues as they will be able to help you in the best way with this problem.

Hi! I’ve sent mail to cycling support several times, they  replied the solution last week. Since none of the way they said can be solved, they started to going in circle…..

if you expect to get better help from forum then from cycling support team ????
at least post more details and what you allready tried.

It could be as simple as internet connection, privileges etc

did you try to open package manager ?
I see you are on mac, run executable in Max.app/Contents/MacOS directly,
maybe terminal will post some infos


it seems that max starts to rebuild database and probably either fails or needs long time to do so.
I remember that being reported here in the forum,
where Max app would not seem to start up at all.
Did you get package manager to open and connect to remote packages?

that paceap.eden bla bla errors are irrelevant, you seem not to try to authorise using ilok dongle, or ?

https://support.cycling74.com/hc/en-us/articles/360050780833-iLok-Authorization

Oh, and  any solution for this in that forum? 
Well, I cannot connect to package manager. I've tried to open it, but it shows blank screen.
Yes, I didn't authorize from ilok, though I've downloaded it(But it shows unavailable message). Is it necessary to authorize by ilok?

I can't authorize MAXMSP

Owen Fender

Hi everyone. I'm a complete newb when it comes to Max, and sensors and stuff. I'm using a BITalino (r)evolution Plugged Kit BT and at the moment I'm just trying to use a breath sensor at 100Hz to control a sine wave in Max. I have this patch:

I have also tried importing the raw data in .txt format, using this patch:

Can someone help get me started. It would be much appreciated.

bitalino.maxhelp

Perf_Patch_1.0.maxpat

Hi everyone. I'm a complete newb when it comes to Max, and sensors and stuff. I'm using a BITalino (r)evolution Plugged Kit BT and at the mo

using-bitalino-sensors-with-max

Hi Owen 
Im struggling with the same problem but from few weeks.Did You come up with any solution?
Cheers,Luke

post what exactly you struggle with.
do you have that ircam external load  and - into which OS / Max version
does it recognise the board and so on



Using Bitalino sensors with Max

Per Frances

First, I would like to say that I'm a new Max user, and while I love working with the program there is plenty that I don't understand.

I downloaded a set of audio patches created by a Max user, and when I went to open them in Max I found that the UI for each of the patches seemed to be missing their inlets/outlets. I have been trying to find a way to connect these patches to other devices, like synths and effects, so I can use them (even to output to gain/ezdac) but I have not figured it out. (The creator has a series of youtube videos demonstrating the patches where they seem to connect to other patches with no problem)

Confusingly, a little while I tried again to open one of the patches with bpatcher and suddenly, the inlets and outlets were there. I went to open the other patches and only found an empty box in the patcher window, with no programming outside of the 'presentation' view. This now happens whenever I try to open any of the patches with bpatcher, just an empty space. I've tried to create the situation that let me open the patch with its inlets/outlets that one time, but I can't figure that one out either. (I can 'open' the patches into their own patcher window and control the UI but, again, there seems to be no way to connect it to anything)

Any advice on how to troubleshoot this problem would be greatly appreciated. Thank you for reading!

Hi everybody,
First, I would like to say that I'm a new Max user, and while I love working with the program there is plenty that I don't ... 

trouble-with-inletsoutlets-on-downloaded-audio-patches

wherever you got that max patches from,
they must be missing structure  patch-subatch-bpatcher,
embeded or not and so on and so on.
maybe some youtube "instructors" need some education themself,
in order to pack example materials into usable form...

one can not understand from what you describe what exactly is missing,
better would be to post some examples.



if inlets are missing it could simply be that they are not found.

do you have the files moved into the max search path before calling their names?

doubleclick the object boxes to open them in order to check if that is the case.

Trouble with inlets/outlets on downloaded audio patches

Ben Bracken

We've just released Max 8.3.2! This update focuses on fixing regressions, OS-related issues, and improving support for newer Jitter features.

As always, you can download the update here: 
https://cycling74.com/downloads

For a full list of all Max 8.3.2 improvements, check out the change log below, or here:
https://cycling74.s3.amazonaws.com/support/version_8_3_2.html

New Features:
• jit.gl.pbr: 'sendinput' message
• jit.gl.pbr: environment texture support
• jit.gl.pbr: more texture support (matrix/texture inputs)
• js/jsui: pattrstorage support
• Packages: install when drag and dropping a .maxpack
• textedit: 'valuemode' attribute to store items as an atom
• vst~: 'midievent' Real-Time message support
• zl: 'fuzzy' attribute

Fixed Bugs:
• attrui: mc.gen~ float param is scrollable
• Audio Status: fixed frozen transport / hang with "None" i/o device
• Audio Status: sample rate displayed correctly with Lynx AES16e card
• Color Selector: theme-aware
• comparison operators: support floats in either/both inlets
• crosspatch / matrix~: UI reflects change when gain value is a float
• crosspatch: fixed memory leak
• curve~ / line~: bangs when last duration is 0
• curve~ / line~: does not bang on transport tempo changes
• curve~ / line~: fixed 'stop' message
• curve~ / line~: fixed issues with simultaneous input of different priorities
• dial: fixed attr label typo
• Dynamic Colors: preserved for object box borders
• Dynamic Colors: restored when loaded in a different Live theme
• fullscreen windows: fixed black bar across top of screen
• Gen Autocompletion: improved matching / text replacement
• Help Patches: improved word wrap for JA Translations
• Inspector: misc improvements to colors displays
• jit.cellblock: removed 80 char limit when typing into a cell
• jit.gl.cubemap: mipmap generation fixes
• jit.gl.lua (GL3): supported in GL3
• jit.gl.node/pix/slab (GL3): proper mipmap generation on capture output
• jit.gl.pbr: fixed "blue tint" when rendering (Mac M1 only)
• jit.gl.pbr: fixed crash when enabling rendering
• jit.gl.pbr: fixed metal/roughness maps when parallax enabled
• jit.gl.pbr: retains parallax when jit.world deleted
• jit.gl.pbr: textures are oriented correctly
• jit.gradient.ui: Fixed crash when loading json
• jit.matrix: jpeg imports correct colors
• jit.movie (AVF): fixed 'frame' message
• jit.record: cannot overwrite existing directory
• jit.world /jit.window: resized when exiting fullscreen mode and floating is enabled
• Jitter GL3 lighting: hemishpere flag enabled for default lighting
• js / Projects: require() files are included
• js post(): supports longer arrays
• js: Folder() can find folders in current Project
• jsparamlistener: reports parameter automation
• jsui: fixed crash when abstraction is set with @filename 1
• live.button: drawing improvements
• live.meter~ / live.gain~: fixed drawing when patcher zoomed
• live.object: fixed Live crash on double-clicking an error
• loadbang: fixed recursive loadbang issues
• Max Console: "yellow" dot for warnings
• Max for Live Device: fixed hang when setting Development Path Type
• Max for Live Device: does not save erroneous data in .amxd
• Max for Live: fixed Gen crashing
• mc.poly~: fixed up/down sampling
• midiparse: midievent message comes out first
• midiselect/midiparse/midiformat: improved 14-bit @hires calculations
• New From Clipboard: eliminated extra loadbang
• New From Clipboard: fixed crash when loadbang triggers bpatcher creation
• Package Manager: fixed issues when accent is in user name (Win only)
• Package Manager: refined conditions for 'updates available' notification
• panel: default bgfillcolor is correct in Max for Live
• panel: improved inlet color
• past: fixed list comparison
• pattrstorage: improved speed of writing XML files
• pattrstorage: support dict values in legacy XML files
• pink~: uses xoshiro256 (like noise~)
• playlist~: fixed out of memory error
• plot~: domain set from stored values
• poly~: fixed crash when parallel is enabled in Max for Live
• poly~: fixed crash after changing voice count with no patcher loaded
• poly~: fixed MPE caching off-by-one error when 'mpemode' is enabled
• poly~: improved calculation of sample offset
• ramp~: reduced min value difference and duration
• Reference Sidebar: fixed broken links
• Save Dialog: fixed crash (MacOS 10.11 only)
• sflist~: fixed crash on 'open' message
• sfplay~: file can be loaded with "preload" after delete/undo delete
• sfplay~: fixed crash when playing / seeking high channel count files
• sfplay~: fixed cue initial frame calculation
• sfplay~: fixed sample rate conversion calculation
• sfplay~: seek message works with timestretching enabled
• Sidebar Reference: fixed JA Translations in info pane
• snapshot~: made interval / non-interval bang reporting consistent
• snowfall~: endmode 1 works when input is 0
• standalones: can build on Mac machines factory shipped with OS 12.5
• tri~: fixed right inlet assist
• umenu: fixed duplicated items when there are spaces in items
• updown~: improved behavior with short ramps
• VIDDLL: fixed black output when context is rebuilt
• what~: fixed high value triggering
• Windows: fixed issues with hidden Save dialog when machine is busy
• zl: fixed warnings when performing symbol comparisons
• zl: right inlet list preserved when changing zlmaxsize

We've just released Max 8.3.2! This update focuses on fixing regressions, OS-related issues, and improving support for newer Jitter features

max-8-3-2-released

poly~: fixed crash when parallel is enabled in Max for Live

thanks a lot for the fast response! this will make my Max-life much easier :)

Hello,
Has the hyperthreading issue that appeared in 8.2 been fixed in this release? (ie. using a poly~ with the multithread 1 message only used every other virtual core. Affects Windows with Intel and AMD CPUs, don't know if it happens on MacOS too).

Thanks to the team for always keeping the updates coming. 

Great list of bug fixes! I'm particularly pleased to see the M4L gen instability. These kind of things can be hard to fix. But I'm also excited to see a long list of items addressed across different areas. I had also experienced problems with curve~ / line~, so great to have those fixed. 

"js / Projects: require() files are included" seems like an understatement.  I'm happy to see jspainter files getting included in Projects automatically as well.  :)

Wow what an upgrade, super, finally large file support, many thanks

BUT: since Max 8.3.2 I cannot open subpatcher. To be more precise some subpatchers in a big patch open others don't and it stays that way until I quit Max and start again. When I open the main patch all the folders that I tried to open appear open as well. It is not always the same subpatcher that won't open. I can repeat this all the time. Hint: when I double-click a subpatcher that won't open, the top of the main patch blinks, I don't know if that is a helpful info. 

I also copied a non-opening subpatcher into a new patcher and it won't open there either.

Those non-opening subpatcher that have a pcontrol also do not open with message "open"

Hope you have a fix for that, thanks

It is normal that the download link for 8.3.2 (win 64) leads to "Max831_220510.zip" ?

I wonder, could you try clearing your cache or doing a clean reload of the download page (FE shift+cmd +r on Firefox)?

Control + anything shortcuts don't work at all anymore

edit: they sometimes do and sometimes don't

Same issue with some keyboard shortcuts that don't always work. (Windows11)

I confirm.
Windows 10 here.
"A" works
"Ctrl" works.
Ctrl+A doesnt work
.


I'm on Windows 10 and they all seem to work for me.

I'm not sure if it helpful info - for guys who at Windows (10 in my case) - i have suggestion always uninstall older build of MAX, before install new. Ie do not use replacement.
This is my personal observation, not claiming relevance. Just, thus i been avoid some problems that i had couple builds back.
Tnx for update.

even better, don't install max, but extract msi file to external folder.
Then copy all DLL's that land in system into max folder.

That way there is no trace of installed max, and no need to uninstall it, 
or any trouble with running different versions.
I keep several max7 and max8 versions like that and use whatever I want,
modify exe files to my needs if I want etc.

There is a bug with 8.3.2 that we are currently working on. Some patches are opening too high on the screen, while others are opening entirely off-screen. If you have a patch that appears to not open (including subpatches and the "Launch" patch of packages in the Package Manager) it is most likely due to this bug. There are two workarounds you can do:

For patches that are opening too high on the screen (the patcher title bar is under the Max menubar), bring the patcher in focus, then go to Window > Zoom. That will bring the top of the patcher back into view and allow you to resize it.

For patches that are opening  entirely off-screen, go to the Window menu and option-click on the  patch name. This will get the patcher to jump into view.

If you prefer to downgrade to 8.3.1, you can download that version from here.

If you encounter any other bugs with 8.3.2, please reach out to us at support@cycling74.com. 

Hi,

jit.record isn't working anymore after the update.
if I want to write a file I get the message:
jit.record: file /Volumes/Macintosh HD/Users/hello/Documents/test.mov is not a movie file, can't overwrite 

luckily i had an previous Max (8.1.5) version which still work properly

@aartcore Please send a message to Support, support@cycling74.com, with a simple patch that  illustrates the issue, along with steps to reproduce and your Max support information. 

Hi just another minor glitch I've noticed when debugging.

@BARTOK We should have a fix for this in an upcoming release, but in the meantime, you could remove the Lato font from the system using Font Book.

Cycling '74 Forums

Max 8.3.2 Released

@BARTOK We should have a fix for this in an upcoming release, but in the meantime, you could remove the Lato font from the system using ...

Using a M4L device to send data to multiple Midi channels

@DOUBLE_UG Oh man, thank you so much for those devices. I couldn't find anything on maxforlive.com. The're so useful. Have a nice day :)

shell external - arm64 compatible version?

https://github.com/jeremybernstein/shell/releases/tag/1.0b3

Dynamic buffer loading using poly~

@source audio Thanks. I think I finally found it. The problem seems to come from the delete message sent to coll.

Generating Sound and Organizing Time: An Interview with Graham Wakefield and Gregory Taylor

Great news !

Send a buffer to Arduino

[peek~] allows you to get each sample value from a buffer.

"Fold" behaviour

Hi gregory, thank you for the answer I think I did that. I set "fold -1 1", so it should work, but it doesn't on my side.

MY FIRST TB303

Hi people ! I really want to learn max so, besides watching/reading tutoriel I'm trying to make my own first synth (to have some king of ...

I can't authorize MAXMSP

Oh, and any solution for this in that forum? Well, I cannot connect to package manager.

Using Bitalino sensors with Max

post what exactly you struggle with. do you have that ircam external load and - into which OS / Max version does it recognise the board ...

Trouble with inlets/outlets on downloaded audio patches

if inlets are missing it could simply be that they are not found. do you have the files moved into the max search path before calling ...