tiago morais morgado

bearing in mind this simple code in processing:
https://bpa.st/4FEA?fbclid=IwAR0FZp07o2Q-ltwPaW1sN0DIbv0uia6Z7cqbnzRpolow9qpLWCxP4nzWuFI

and this simple code in maxmsp
why am i not being able to receive osc messages in maxmsp?

bearing in mind this simple code in processing:
https://bpa.st/4FEA?fbclid=IwAR0FZp07o2Q-ltwPaW1sN0DIbv0uia6Z7cqbnzRpolow9qpLWCxP4nzWuFI
as ... 

need-help-problems-with-opensoundcontrol-communication-in-between-processing-and-max-in-windows

udpreceive gets out of function if you enter ip address.
it takes it as if it were port number, but all is wrong ...
 

i tried both ways, actually, and it still doesn't work

use simple udpreceive with correct port set, and add print object or a message to it.



why do you need CNMAT attribute set ?
do you know if whatever lib you use from processing sends fullpacket messages ?
Did you set correct ports in processing  ?


I already figured out the solution to the problem. what was wrong was the port in max. rather then receiving on port 12000 i should be receiving on port 57120
cheers

[NEED HELP] - Problems With Opensoundcontrol Communication In Between Processing And Max In Windows

rklem

I'm pretty new to Max, so please bare with me.

Is there a way to completely remove the value from a dict key while keeping the key?

I only found the messages "remove" (which also removes the key) and set.
When I try "set key_name" without any value, the key shows the value "" . Since I'm filling up an array with MIDI SysEx messages ("append key_name $1") the array would always start with "". Is there a way to completely empty the value?

Hey everyone,
I'm pretty new to Max, so please bare with me.
Is there a way to completely remove the value from a dict key while keeping ... 

remove-value-from-dict-key

remove the key to wipe it togeher with pevious data,
reuse the key to append new sysex string if you need same key again.
why is that problematic ?


For instance when loading a new sysex string triggers a "remove" (to erase the previous stored string), but the key was removed manually already (by clear or whatever), than this results in an error message.

Of course I can work around that. I was just surprised that set key_name produces key_name : "" and that I couldn't find a way to completely empty the value without erasing the key.

dict is behaving so, if you have a key than it will have either some data or not, in which case ""   =  empty is added to a key.

you must have means of recognising sysex message as such,
an than want to store specific message under a specific key in dict.
Is that correct ?
once message is received and assigned to a key, receiving it again should wipe old one and insert it new.
What is your difficulty to achieve that ?

set message replaces old key AND data or insert it new if it does not exist.  To do so you need to collect sysex message into a list,
instead of appending byte by byte.

Maybe you have difficulties with logic arround messages to dict,
to get any help with that you need to post the patch. 


I understood that I can either use append (byte by byte) or set (collecting entire message in a list). Currently I'm using append, but I'll explore if there are any benefits using set instead.

As said: Right now the only problem with my patch are error messages when the "Load" action tries to wipe a key that has been deleted manually already, but that is an easy fix.

I just thought I'd miss something and tried to understand the mechanics of dict a little better. 

Thanks again for your help, I really appreciate it!

[dict] has a @quiet attribute you can use to stop the error messages (such as from "remove" on a non-extant key).

If you wanted, you could also use "contains <key>" message to test whether a key exists.  If it returns 0 (out third outlet), then you'd use a "set", if it returns 1 then you'd use an "append".

Remove value from dict key?

Jonatan Krogh

Hi! 

I'm trying to figure out how to remember and later recall midi mappings automatically when closing and opening a standalone.  I'm trying to send read/write to the "mappings" object, but i can't get it to load the file it by itself. I'm quite sure my search path is correct,  and a file is already in place, but still i get a popup for making a new one instead of loading the one i specify. 

How do i do this best? I can't find anything about this on the forums, if anyone has some resources or examples please let me know! Thanks in advance!

Hi! 

I'm trying to figure out how to remember and later recall midi mappings automatically when closing and opening a standalone.  I'm tryi

recall-mapped-midi-in-standalone

post what you exactly send to mappings object.
I hope you use absolute path and not just name...


Your path is broken.
read Macintosh HD:/Applications//LastMappings.maxmap

read "Macintosh HD:/Applications//LastMappings.maxmap"

because there is a space between Macintosh and HD

Also issuing the path to patch or standalone is all but efficient
and does not work on my mac with max 6.1

try this...


Just spent about 15 hours fighting with this issue again, and when searching for help all i found was my  own thread here from two years ago, so I'll leave some important notes for other people (or myself in the future)

- The "Enable for Mapping" states of each control is NOT saved in the mappings object. It is saved in the patcher itself.

- It is also NOT saved in the top level patcher, or project. For any bpatcher you need to open it up, enable all controls for mapping, and save. 

- If you try to load mappings for controls that are not "enabled for mapping", for example because you just enabled them in the built application, not before building, those controls are simply erased from the mappings list.

Some documentation on this would be great! A checkbox in the mappings object to also store the "enabled for mapping"-states in the .maxmap file would be even greater!

I would never use midi mappings, because they can't
distinguish between midi ports or devices, which makes it useless
in any serious midi environment.




If by serious you mean large, then I'd agree, but i can think of many situations where it can still be useful. I agree though that the current implementation is far from optimal.  Is there some good example floating around on how to DIY a midi/key mapping solution? I have a feeling it should be possible to make something relatively clean with pattrstorage but haven't really given it a shot yet.

you can address elements which you want to control from central place, either by patchcord, send - receive, forward, or scripting.

That was the usual procedure in pre - mappings, pattr or dict days.
one can for example make jit.cell containing list with elements to assign
control sources, and assign midi input there, including also midi ports or devices if needed.

needs a bit of work, but at the end you have something 100% reliable.

If you prefer to keep max mappings, then it is a matter to test and see how to overcome limitations you discovered, in first place with bpatchers,

to map adhoc , object needs varnme, parametr mode and visible to mapping attributes enabled, in that order, which can be done using messages.
after that mappings object recognises it. 


it is a great feature for quick live coding, but i also would not use something like this in a standalone.

invest once in your own midi mapping system made of rudimentary max objects, and it´ll will work like you planned.

and yes, "enable mapping" on/off is a property of the objects and not stored elsewhere.

the only thing what remains a bit difficult is that getting the data from [midiinfo] at startup is not thread safe. you always have to wait until the data is present before you refer to it from somewhere else.

and of course you can not have a contextmenu shown to the user to set a controller number or enable a learn mode, rather you need an extra button for this.

@SOURCE AUDIO
Could you elaborate on
"...one can for example make jit.cell containing list with elements to assign control sources, and assign midi input there, including also midi ports or devices if needed."

I about to add DMX control to quite a large existing patch with 100's of parameters.  Looking for the most efficient way to distribute a large amount of incoming control data to objects params.

I've attached a very small example, I'm assuming there is a simpler way???

what you ask for is quite different from the topic here.

you want to send large list of values to dedicated destinations. 

Recall mapped midi in Standalone 

Roberto 

unpack list with variable numbers. I have a list that always varies (it's never the same). How can I unpack the list? The list can have 10 numbers or 100

unpack list with variable numbers. I have a list that always varies (it's never the same). 

unpack-variable-numbers

It depends on how you want to further process each list item. [iter], for instance, is a very simple solution. It will unpack each item 1 by 1 whatever the total number of items is, but  they will all be processed sequentially.

You can unpack a list of 10 numbers with an [unpack] with 100 outlets. Simply only the 10 leftmost outlets will be updated. A combination of [zl.iter 1] and [cycle] also work, or just a [zl.iter 1], depending on what you want to achieve with those numbers.

if receiving side of unpacked list is not entirely reachable by patch cords,
you can split the list using zl.slice or use listfunnel -> forward.







Unpack variable numbers

mikkelm

Hi There.

Any ideas on how to get a curve in Function to interpolate at audio-rate / MSP signal.

Hi There.

Any ideas on how to get a curve in Function to interpolate at audio-rate / MSP signal.
Cheers
Mikkel
 


function-to-interpolate-at-audio-rate

Function to interpolate at audio-rate

david

I saw it on YouTube.
https://www.youtube.com/watch?v=spUNpyF58BY&t=524s

Part of the .
It's in the same context as the photo attachment.

The fft~, pfft~ object was not found or the contents of the MSP Tutorial.
I want to separate the triangle wave or square wave waveform into a number of sine waves, which often appears in the basic signal processing book, but it's blocked in the implementation method.

I'm asking for your help on how to implement it with max.

It doesn't matter if it works as real-time or non-real-time.

I just want to implement that a combined waveform with three different Hz is separated into three.

fourier.png

I saw it on YouTube.
https://www.youtube.com/watch?v=spUNpyF58BY&t=524s

Part of the .
It's in the same context as the photo ... 

i-want-to-separate-the-sample-from-max-msp-into-a-sine-wave

I want to separate the sample from Max Msp into a sine wave.

jon snow

Hello! I am having troubles launching Max on mac os 14.1 (sonoma beta).

I have already tried:
reinstalling max at the latest version 
deleting preferences 
deleting 32 bit vst
rebooting...

Is there anybody else puzzling with this?

Hello! I am having troubles launching Max on mac os 14.1 (sonoma beta).
I have already tried:
reinstalling max at the latest version ... 

max-not-running-in-mac-os-sonoma-141-beta

Max 8.5.6 works perfectly fine on my M2 MBP with Sonoma installed. Do you have a particular patch I can test?

The problem occurred on Sonoma 14.1 Beta, which I have installed by mistake. There is no way I can run MaxMSP, it always fail. I can't open no patch or setups.

I know this is a wild suggestion, and maybe time consuming. But ever since I got an m1 16” I have been completely wiping it every six months. 

yes, that means keeping track of every single file that I make in any program and moving them to an external dive before wipe. 

yes that mean reinstalling every max plugin and making sure to not forget all the RNBO externals that I made.

I have not tried to go backward from 14.1 to 14.0, but when you do a full reset it should work.

Yes, resetting the machine should work. But I have neither the time or the will to do it.

Uh… sorry, I missed most important part of your message - of course I’m not running 14.1 beta. 

Max not running in Mac os Sonoma 14.1 beta

keepsound

Queue Size, double name (number) - Last version of Max/MSP

Schermata 2023-09-28 alle 10.19.47.png


 
Queue Size, double name (number) - Last version of Max/MSP

preferences-bug

Hopefully this is fixed asap. Why don't you fill a bug report because otherwise you can only hope that a c74 employee reads this and fills it out for you?

Preferences bug

James Kogane

Hi--Have a basic polybuffer granulator here and controlling which samples are chosen by a multi-slider but haven't been able to implement a successful method for overlapping the grains, which in this case I guess are buffers? Plan to implement volume control per grain/buffer from the multi-slider next but the overlapping is the thing that's getting me.

Hi--Have a basic polybuffer granulator here and controlling which samples are chosen by a multi-slider but haven't been able to implement a ... 

overlapping-grains-buffers-in-polybuffer-granulator

I am not sure to understand what the multi-slider is there for : randomly choose a subset of the sound files stored in the poly buffer ? But why a range of values for each individual slider in this case ?

As far as "overlapping" is concerned, if you mean playing  several grains at the same time so that triggering a new grain does not stop playing the previous one, then you should use poly~ or even better mc.groove to get each grain assigned a specific voice/channel. If my reading is correct, and if not already done, it may be a good idea for you to watch  FEDERICO-AMAZINGMAXSTUFF's wonderful video series on this topic (https://www.youtube.com/watch?v=YnROTQAQW_I). It made a lot of concepts clear to me when I was trying to understand better granular synthesis and mc.

yeah planning on making it on or off instead of a range for the multisliders but know how to do that. goal is to be manipulating folders rather than a single buffer without using flucoma. There's a well known patch in supercollider called "mulitgranulator" which granulates a folder of samples and controls them based on weights in a multislider, so trying to recreate that here. I guess mc would be better.

So each sample/sound file is granulated individually with it's own parameters and the "relative density" is controlled by the slider, right ? But why randomization, then ? Sounds like ruining the efforts made to select the weights individually ?
Interesting project, though. Thanks for sharing the idea. And yes, from what I understand, you definitely need to go mc.

i may be doing it wrong but idea is to pull out certain samples and then have them "granulated" in a random series rather than linearly

here's the supercollider version in action in case anyone is curious:

https://drive.google.com/file/d/1BAW2uN2ys--giB6EwKJI-tTnxCP2Wh_3/view?usp=sharing

Overlapping grains (buffers?) in polybuffer granulator

JAMES

Hello everyone! I have gone through several posts about audible clicks in groove~ and didn't see an option that pertains to my case. My patch is very simple, its a sequencer changing random start points. Of course, each trigger has an audible click, most likely due to the zero crossing.

Envelopes didnt seem to help after a few sessions trying them.

I would love to use groove~ because i love the sound of the timestretching. So grooveduck~ isn't an option for this patch.

I am looking to ideas on how to fix this on my own. I actually tried to delay the start point bang and simultaneously have a reverse envelope that would "silence" the clicks but it didnt quite turn out how I liked. I suppose before I actually post the patch I would love to hear any theoretical  ideas on remedies for this situation. I have a feeling I might have to start from scratch and implement this from the ground up.

Hello everyone! I have gone through several posts about audible clicks in groove~ and didn't see an option that pertains to my case. My patc

groove~-start-point-audible-clicks-ideas

Hi, you could use curve~ or line~ to ramp-down amplitude before a change,then its right outlet can bang the actual change, followed by its own ramp back up in amplitude... i've done this before, it works, but here's a switch-and-ramp technique in gen~ which can sound faster.. the only probs it might have is that sometimes it can miss if your scheduler is not in overdrive(plus audio-interrupt with smaller vector sizes can help even more), and depending on the size of the change at the point of change, it can still sound like a 'bump' even if not an altogether 'click'... this bump can also be tricky to deal with when mastering(compressors/limiters will get tripped up too exaggeratedly), so it's also better to use it with a little headroom left over... i employed a bit too much here, you could probably get away with less than 4%(0.96 or so, instead of the 0.88 value i use here), anyways hope it helps:

Thank you! This does help! I implemented it in the patch and seems to work. Sometimes it can be tricky to understand where the clicks are coming from with this and an envelope. Appreciate your time on this

Hello! 
I am from the future (2023) and tried to use the solution of 👽R∆J∆ The Resident ∆lien👽 but is clicking like crazy. 

Did something change in the meantime in Max and it does not work as it use to be (ah those good old days)? 
Any insight? 

To recap, the issue is every time I try to instantly restart the sample with groove~ it clicks. I also tried to implement a ramp, but did not work as expected. 



because you don't know how to implement it ?
you need to fade out, then start from new position and fade in.
fading length depends on audio material and acceptance threshold for abrupt changes in audio stream.

or use 2 players an crossfade them.


hmmm... that old 'switch-and-ramp' often had problems, and now it does seem as though it's reacting differently. i don't feel like investigating it either because i don't like de-clicking that is dependent on linear slopes(and i always found strange cases where 'switch-and-ramp' wouldn't work nicely)...

instead, nowadays, i'm just using this which may feel less exact since it's not sample-accurate in terms of the reaction-time for control, but it feels pretty perfect for general usage, and also, is probably not as cpu-intensive as using an all-gen~ or all-signal based solution:

here's that same patch simplified with the above:

hope this helps a bit(groove~ has timestretch with quality sound anyways now, and there's also the phasegroove~ object to help synchronization with de-clicking better: someone(not me) should try using phasegroove~ with groove~ within poly~ to get proper/efficient crossfaded granular detail)
🍻

in theory it is simple.  a "click" is only how you perceive the presence of a a short time period which contains very high frequencies, so you can get rid of it by lowpassfiltering the audio during that short moment.

in practice you will find that it is impossible to find a perfect setting which works with any material: sometimes a click won´t matter at all, sometimes you can still hear a decent, unwanted "plop" after you applied a fade-in of 10 ms.

however, as a starting point the [slide~] object should be it.

and while not beeing ideal, i would suggest to use a buffered envelope for it, which you can read from with interpolated values (play, wave, cycle), because you really want to use a curved fade-in and not a linear, "trapezoid" fade-in which again contains a "corner" at its end, which produces a click again (which is why raja uses curve~ and not line~), and writing it into a buffer is for sure cheaper than to calculate it live

in opposite ot poles and zeros slide~ cannot explode, but to modulate it with a ramp from 0 to 22 khz you needed to transform its "sample" arguments into hertz first.

some people would say that you should modulate both the frequency and the steepness (use 4 slide in a row and mix their output level against the unfiltered signal), but for me it is an either/or case.


of course my statement is wrong. if you use frequency filtering, you need to fade-in the amplitude, too. if you do not, it stops working when the sound event (and the fade-in) is retriggered. but you can use only amplitude modulation without filtering.

Groove~ Start point audible clicks, ideas

Ben Bracken

We are happy to announce the release of Max 8.5.6 and RNBO 1.2.1. 

On the Max side, we have a number of bug fixes, with improvements to fullscreen jit.window / thispatcher behavior, among other things. 

On the RNBO side, this release features many new improvements and bug fixes, with a focus on the Raspberry Pi target (can upload and manage the active patch), new ease objects, messages to the rnbo~ object for managing manual target exports, new integer utilities for codebox, among many other things.

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

For a list of all Max 8.5.6 and RNBO 1.2.0 improvements, check out the change logs below, or here:
Max:
https://cycling74.com/releases/max/8.5.6 

RNBO:
https://cycling74.com/releases/rnbo/1.2.1 

udpreceive: 'defer' attribute to set message output to the low-priority queue

curve~ / line~: pending ramps are appropriately cancelled if interrupted

jit.dx.grab: support for outputting at device max framerate

jit.gl.handle: autohandle works with jit.gl.mesh

jit.gl.pix: fixed dim variable breakage with codebox

jit.gl.sketch: fixed usage of vertex colors

jit.gl.text: fixed draw errors on visiblity change

jit.window/jit.pwindow: fixed visibility in Max for Live

jit.world: fixed crash when enabling/disabling fullscreen or floating

live.menu: svg files are included as dependencies in Projects

Max for Live Editor: fixed issues when multiple Max instances are running

Max for Live: fixed crash when setting 'is_mpe' attribute

MIDI: improved support for multiple devices of the same type (Windows)

scala: fixed default scale "B" from 1200 to 1100 cents

thispatcher / jit.window: improved manual fullscreen behavior / fixed regressions

accum: added gen~ style features (resetmode, min, max)

C++ source code export: option to disable export of RNBO Engine

codebox: imod/iadd/imult integer operators

ease: new objects a la Max Package (ease, ease.list, ease.listinterp, ease~, ease.xfade~)

Max External Target: set default buffername for buffer attributes

number~: displaymode option (first / average)

oscquery runner: report if/when a preset was loaded

Raspberry Pi Target: add a device to the sidebar by address

Raspberry Pi Target: support for cloud compiling

Raspberry Pi Target: upload and manage multiple patches (hot swap)

Raspberry Pi Target: upload patcher without loading it

rnbo.remote: 'launchwebinterface' message to launch web interface from rnbo.remote

rnbo.remote: @patchername attribute to change current patch on device

rnbo~: dumptargetconfig message for getting the configuration dictionary for an export target (defaults c++)

rnbo~: export message for triggering a target export (defaults to c++)

codebox: allow const values in param declarations

codebox: fixed Int cast of bitwise operators

codebox: fixed parameter visibility in user defined functions

codebox: improved let/var declaration parsing

codebox: simplified Fixed Array initialization

counter/counter~: fixed crash when adding or removing ~ in object box

env2~: fixed an issue with release in hold mode

Export Sidebar: improved device add and delete UI

Export Sidebar: improved error message when Max is unauthed / authed via Live

Gen in RNBO: parameter with the name "t60" works

lockedphase~: removed (can still be used in codebox)

Max External Target: data can use Max buffers

Max External Target: overwrite warning references ‘external’

Max External Target: refpages in search path are not overwritten by new version of object

message: left inlet input always triggers output

param~: fixed issues when used in polyphonic top-level patchers

RNBO Object Inspector: shows enum attrs in a dropdown menu

RNBO patcher title bar: right-click title bar shows patcher filepath

samplerate: updates in the context of Max for Live

silencedetector~: fixed issues with cut off notes

silencedetector~: threshold and length options have some constraints

Themes: improved RNBO patcher legibility in non-default themes

VST Target: parameter automation improvements

We are happy to announce the release of Max 8.5.6 and RNBO 1.2.1. 

max-856-released

Max 8.5.6 Released

Andrew Benson

With this latest Max release (8.1.6), we've added a long list of new features to mtr that support more creative usage of this classic Max object. To celebrate the release, we put together a video and patcher that uses mtr to drive a granular sound engine with looping parameters.

In addition to the expansive looping and overdubbing features, mtr now supports dictionary access, event editing via messages, pattr-style binding, and transport sync. We look forward to seeing and hearing what you make with it.

With this latest Max release (8.1.6), we've added a long list of new features to mtr that support more creative usage of this classic Max ob

-sharing-looping-gestures-with-mtr

its my first update since my purchase of full max licence so im not sure do I have to uninstall previous max version and then install the update OR do I just install the update into the same old folder and It automatically deletes the older version?

and do my snippets and libraries remain intact?

Hiya, Max updates are always a full install so there is no need to pre-install other versions. Your snippets and Preferences shouldn't be affected in any way.

I am aware that you don't need previous versions, but if you have them: do you need to first uninstall them yourself or does the new installation do that for you?

just install the update into the same old folder and It automatically deletes the older version

👆this(you'll be given a choice when running the installer to either 'replace' the old version of Max, or install alongside(allowing you to keep newer versions alongside older ones)... but either way, as long as you open and work within the 8.1.6 version of Max, you'll have access to the latest/8.1.6 version of the 'mtr' object - you don't need to uninstall anything first)

I try to adapt [mtr] for parameter recording for non real time rendering in Jitter.
This means recording with 60 frames per second and output of recorded parameters on bangs that are send from the rendering logic (meaning not equidistant intervals).
How to achieve that?

The "next" message unfortunately doesn't work, because it is event based instead of time step based and so will not work with parameters that are not updated every frame during recording.

([mtr] would help  to overcome limitations of the Non-real time 4K recording patch in  https://cycling74.com/tutorials/best-practices-in-jitter-part-2-recording-1 ).

Edit: I mean my attempt with "playatms" followed by "stop" feels clumsy.


Cycling '74 Forums

We are happy to announce the release of Max 8.5.6 and RNBO 1.2.1.

Hello Andrew, I recently created a problem report about the MTR new version, but maybe I should have done it ...

Thank you both for replying. I didn't put any 32bit object but it didn't work. I asked to cycling74 then they told me that they will not ...

I already figured out the solution to the problem. what was wrong was the port in max.

[dict] has a @quiet attribute you can use to stop the error messages (such as from "remove" on a non-extant key). If you wanted, you could ...

Hey, thx for that, interesting! B

if receiving side of unpacked list is not entirely reachable by patch cords, you can split the list using zl.slice or use listfunnel -> ...

Merciiiii.

I saw it on YouTube. https://www.youtube.com/watch?v=spUNpyF58BY&t=524s Part of the . It's in the same context as the photo ...

@Jon Uh… sorry, I missed most important part of your message - of course I’m not running 14.1 beta.

Hopefully this is fixed asap.

figured it out will post soon

of course my statement is wrong. if you use frequency filtering, you need to fade-in the amplitude, too.