Matteo Marson

once in a while, looking inside jitter shaders, I discover some new GL3 built-in uniforms never saw before. Sometimes, they provide the answer to problems I didn't know how to address before. I looked inside the jitter documetation, but I didn't find an exhaustive list of all the avaiables built-in uniforms. I know many of them can be found in the GLSL documentation out there, but i'd love to have a comprehensive list of what Max and GLSL can offer to let the users build their own shaders. Here there are the uniforms i met so far and what i understood about them:

type="mat4" state="MODELVIEW_PROJECTION_MATRIX" 

type="mat4" state="PREV_MODELVIEW_PROJECTION_MATRIX"

 == the previous frames modelview-projection matrix

type="mat4" state="VIEW_PROJECTION_MATRIX == 

type="mat4" state="CAM_PROJECTION_MATRIX"

gl3 only) Provides the current rendering cameras projection matrix; in most cases is equivalent to PROJECTION_MATRIX except in cases where a full-screen quad is rendering, e.g. in a jit.gl.slab/pix (or jit.gl.pass)

== Transforms normalized texture coordinates into rect coordinates

 == scene seen from the light position???

 == the spotlight cutoff in degrees (=spotlight angle)

 == exponent implied in the reflected light calculation

gives the values from the @mat_X attributes of the 3Dobj to which the shader is attached.

== (where "n" is an integer number) Nth custom vertex attribute

These are the built-in uniforms i know. I ignore the meaning of some entries in this list and I guess I'm still missing some of them. Could you please integrate the list with the uniforms you know? I will edit this first post adding the entries you provide, so to keep everything compact.

It would be very usefull if an analogue list were done with built-it variables.

Hope this could be usefull to you as much as it is to me. 

once in a while, looking inside jitter shaders, I discover some new GL3 built-in uniforms never saw before. Sometimes, they provide the answer to problems I didn't know how to address before. I looked inside the jitter documetation, but I didn't find an exhaustive list of all the avaiables built-in uniforms. I know many of them can be found in the GLSL  documentation out there, but i'd love to have a comprehensive list of what Max and GLSL can offer to let the users build their own shaders. Here there are the uniforms i met so far and what i understood about them:

MATRICES:
type="mat4" state="MODELVIEW_PROJECTION_MATRIX" == P * V * M
type="mat4" state="PREV_MODELVIEW_PROJECTION_MATRIX" == the previous frames modelview-projection matrix
type="mat4" state="VIEW_PROJECTION_MATRIX == P * V
type="mat4" state="MODELVIEW_MATRIX" == V * M
type="mat4" state="VIEW_MATRIX" == V
type="mat4" state="WORLD_MATRIX" == transforms into world coordinates
type="mat4" state="PROJECTION_MATRIX" == P
type="mat4" state="CAM_PROJECTION_MATRIX" == (gl3 only) Provides the current rendering cameras projection matrix; in most cases is equivalent to PROJECTION_MATRIX except in cases where a full-screen quad is rendering, e.g. in a jit.gl.slab/pix (or jit.gl.pass)
type="mat3" state="NORMAL_MATRIX" == it orients the normals in eye space
type="mat4" state="TEXTURE0_MATRIX" == Transforms normalized texture coordinates into rect coordinates

CAMERA:
type="float" state="FAR_CLIP" == Camera far clipping distance
type="float" state="NEAR_CLIP" == Camera near clipping distance
type="vec3" state="FAR_CORNER" == far corner of the view frustum
type="vec3" state="CAMERA_POSITION" == camera position in world space
type="vec3" state="CAMERA_DIRECTION" == camera direction in world space
type="vec2" state="VIEWPORT" ==  the pixel size of rendering window
type="vec2" state="INVERSE_VIEWPORT" == the inverse of the viewport dims

LIGHT:
type="mat4" state="LIGHT_VIEWPROJ_MATRIX0-7" == scene seen from the light position???
type="float" state="LIGHT_RANGE0-7 " == distance reached by the light
type="vec3" state="LIGHT0-7_POSITION" == position on the light
type="vec3" state="LIGHT0-7_DIRECTION" == direction of the light
type="vec4" state="LIGHT0-7_AMBIENT" == ambient light color
type="vec4" state="LIGHT0-7_DIFFUSE" == diffuse light color
type="vec4" state="LIGHT0-7_SPECULAR" == specular reflection color
type="float" state="LIGHT0-7_CUTOFF" ==  the spotlight cutoff in degrees (=spotlight angle)
type="float" state="LIGHT0-7_EXPONENT" == exponent implied in the reflected light calculation

MATERIAL:
type="vec4" state="DIFFUSE" == material diffuse color
type="vec4" state="AMBIENT" == material ambient color
type="vec4" state="SPECULAR" == material specular color
type="vec4" state="EMISSION" == mterial emission color
state="FRONT_MATERIAL" == gives the values from the @mat_X attributes of the 3Dobj to which the shader is attached.

VERTEX:
type="vec3" state="POSITION" == XYZ Position
type="vec4" state="COLOR" == RGBA Color
type="vec3" state="NORMAL" == Normal vectors
type="vec3" state="TANGENT" == Tangent vectors
type="vec3" state="BITANGENT" == Bitangent vectors
type="vec3" state="VERTEX_ATTR" == Custom vertex attribute
type="vec3" state="VERTEX_ATTRn" == (where "n" is an integer number) Nth custom vertex attribute
type="float" state="EDGEFLAG" == unused, ignore

TEXTURES:
type="vec2" state="TEXDIM0" == XY Dimension of texture 0 type="vec2" state="TEXCOORD" == XY texture coordinates

These are the built-in uniforms i know. I ignore the meaning of some entries in this list and I guess I'm still missing some of them. Could you please integrate the list with the uniforms you know? I will edit this first post adding the entries you provide, so to keep everything compact.

It would be very usefull if an analogue list were done with built-it variables.

Hope this could be usefull to you as much as it is to me. 
Thank you very much!

Hi everyone,
once in a while, looking inside jitter shaders, I discover some new GL3 built-in uniforms never saw before. Sometimes, they pro

exhausting-list-of-all-the-built-it-uniforms-avaiable-in-jitter-shaders

Thank you for this Matteo! 
You are right, the MODEL_MATRIX doesn't exist. The Model Space is just the position of the vertices as they come from inside the model, in which usually the 0,0,0 is the center of the model itself. 
If you need the coordinates in WORLD SPACE you can use the WORLD_MATRIX built-in.  

FRONT_MATERIAL will give you the values from the @mat_X attributes of the 3Dobj to which the shader is attached. 
layout (std140) uniform FrontMaterialParameters {
				MaterialParameters frontMaterial;
			};
Check the shader generated by the jit.gl.material object with the get_gl3_shader message to see how this works. 
You probably know this already but maybe can be useful for others: in the Max documentation "Appendix C: The JXS File Format" one can find all the built-in variables for the GLSL jxs shader format.  

Thank you very much Federico!
I honestly missed that appendix...I added the missing entries in the original post, but some are still a bit obscure to me:

type="mat4" state="PREV_MODELVIEW_PROJECTION_MATRIX" == ???
type="mat4" state="CAM_PROJECTION_MATRIX" == This one doesn't exist in the documentation, but i found it in mrt.ssao.render.gl3.jxs
type="vec3" state="FAR_CORNER" == far corner of the view frustum???
type="vec2" state="VIEWPORT" == ???
type="vec2" state="INVERSE_VIEWPORT" == ??? 
type="float" state="LIGHT0-7_CUTOFF" ==  spot light falloff???
type="float" state="EDGEFLAG" == ???

Ok so I think I can only add my contribution with VIEWPORT, which is simply the size in pixels of the rendering window. 
Keep it up Matteo! GLSL needs to be demystified

PREV_MODELVIEW_PROJECTION_MATRIX - the previous frames modelview-projection matrix, used for velocity based effects (e.g. jit.gl.pass @fxname motionblur)

CAM_PROJECTION_MATRIX - gl3 only, provides the current rendering cameras projection matrix, which in most cases is equivalent to PROJECTION_MATRIX except in cases where a full-screen quad is rendering, e.g. in a jit.gl.slab/pix (or jit.gl.pass). used in the gl3 engines ssao effect

FAR_CORNER == far corner of the view frustum??? - yup. used for depth rebuilding i think, can't quite remember. ssao shader maybe?

VIEWPORT - as federico says above, the pixel size of rendering window
INVERSE_VIEWPORT - just as it sounds, the inverse of the viewport dims

LIGHT0-7_CUTOFF - the spotlight cutoff in degrees, another name for the spotlight angle

Thank you so much, Federico and Rob!
I updated the list in the first post. 
I'll soon indicate for each built-it uniform a .jxs file in which it gets used, so that each variable can be seen in action in a reference patch.

btw, I wanted a "PREV_MODELVIEW_PROJECTION_MATRIX"-like variable so bad, and it was right under my nose...

cool, thanks much for taking the initiative here!

btw the PREV_MODELVIEW_PROJECTION_MATRIX is not yet implemented in gl3, but I hope to fix that sooner than later


Insane help here, and some example of code in action would indeed be of enormous value :o, I'm following you guys : )

Hi Riccardo, this tutorial I made today should be a fitting example of code in action:
https://youtu.be/gKIVuVCfBws 

Oww, I felt like being halfway to convert it and here you come. Thanks for the enlightening coding.

texture2D became texture... what about texture2DRect? If textureRect is the solution, this wasn't my real problem :o

I've been feeding a shader with two textures, the first for extrusion purpose, the second is the texture to be applied over the distorted shape. If i use "outColor = color" I can see my grey shape being distorted from the first texture, but when I'm trying to use my second texture, I'm getting this...

I'm hoping the problem lies here, if it is not, I can share the full code attached to a simple patcher as example.

Hi Riccardo, I think you get this error because you are using a vec4 as a second argument to the function "texture",  which takes a vec2 as a second argument. 
I think you mixed up multiplying the texcoord by the texture matrix, for which you need a vec4, and using the texcoord to read the texture with the "texture" function. 

It totally make sense. Still I'm playing with an invisible shape ohoh.
I'll give it some more tries.

I found another one:
state="BACK_MATERIAL"
What is this? I guess it something related/opposite to FRONT_MATERIAL

undocumented and unsupported at this time

ah ok, thanks!
I found this in one of the gl3 example patches

quick note to say that as of 8.2 (and the bundled gl3), PREV_MODELVIEW_PROJECTION_MATRIX should now be functioning as expected in a gl3 context.

Exhaustive list of all the built-it uniforms avaiable in Jitter shaders

michelefiori

Hi everyone, I encountered a problem when starting script on node.js on MAX on Mac M1 : modules are not loaded due to an architecture problem: this is the error message :"Error dlopen ... "have 'x86_64', need 'arm64e'". The module is wrtc.node, but when I open the same through node.js installed directly on the mac, everything works fine ..

Hi everyone, I encountered a problem when starting  script on node.js on  MAX on Mac M1 : modules are not loaded due to an architecture problem: this is the error message :"Error dlopen ... "have 'x86_64', need 'arm64e'". The module is wrtc.node, but when I open the same through node.js installed directly on the mac, everything works fine ..

Hi everyone, I encountered a problem when starting  script on node.js on  MAX on Mac M1 : modules are not loaded due to an architecture prob

node-js-max-on-mac-m1

It sounds like the version of wrtc.node is x86_64 (searching online it sounds like there are ways for you to build for M1, but relatively cumbersome to accomplish). The version of node you have installed on your system, independent of Max, is in all likelihood also x86_64, if it is working fine in that instance.

Under Max 8.2.0, we bundle a universal binary version of Node 16.6.0. If you run Max as native M1 arm64, node.script will by default launch a child process using this version of node as M1 native ARM code.

If you run Max using Rosetta, the child process will be launched using x86_64 architecture, and your x86_64 node modules should work. This may be enough for your purposes. 

If you need to run Max as native M1 arm64, but want to use an x86_64 node process, you will need to specify an external x86_64 only node binary, via the @node_bin_path and @npm_bin_path attributes as described in the Node for Max documentation.

thanks Joshua for the clarification! But if I understand correctly Max's new release also works natively on M1 .. this is great .. I have not found any announcements on this ..


Yes, it is Apple Silicon native! Thanks for letting us know that it wasn't immediately clear.

We've got that info on the home page, forum announcement thread, and social media, but I notice that it's absent from the actual release notes page and the download page doesn't have any special mention of it. 

node.js - MAX - on Mac M1

jamie

I'm in the process of porting one of my PD externals to Max/MSP, and

I've run into what seems to be a strange problem. In the PD object, the

first inlet and and first outlet are for control data, the others are

used for audio data. I try doing this in Max/MSP, and when I connect the

rightmost outlet to the inlet of another audio object I get:

error: ugen_connect dssi~ dac~ -1 1 (2 2)

dsp_setup((t_pxobject *)x, x->plugin_ins);

for(i = 0;i < x->plugin_outs; i++) outlet_new((t_pxobject *)x,

x->control_outlet = outlet_new ((t_pxobject *)x, "control");

The external works fine if outlet_new((t_pxobject *)x, "control") is

called first, but of course this results in the rightmost outlet being

the control outlet which is not what I want.

Is it a Max/MSP convention to have the in/outlets in a specfic order, or

I'm in the process of porting one of my PD externals to Max/MSP, and
I've run into what seems to be a strange problem. In the PD object, the
first inlet and and first outlet are for control data, the others are
used for audio data. I try doing this in Max/MSP, and when I connect the
rightmost outlet to the inlet of another audio object I get:

for(i = 0;i < x->plugin_outs; i++) outlet_new((t_pxobject *)x,
"signal");

The external works fine if outlet_new((t_pxobject *)x, "control") is
called first, but of course this results in the rightmost outlet being
the control outlet which is not what I want.

Is it a Max/MSP convention to have the in/outlets in a specfic order, or
am I doing something wrong in my code?

outlet-creation-order

Jamie Bullock wrote:
> Dear Max/MSP dev'ers,
>
> I'm in the process of porting one of my PD externals to Max/MSP, and
> I've run into what seems to be a strange problem. In the PD object, the
> first inlet and and first outlet are for control data,

In Max you have to create the outlets the other way round (right to 
left), not left to right as in Pd.

On Mon, 2007-02-05 at 12:08 +0100, Olaf Matthes wrote:

>
> In Max you have to create the outlets the other way round (right to 
> left), not left to right as in Pd.
>

Yes, but my question is: is it possible for the outlets to be of
arbitrary type "signal"/"control"? My problem occurs if I try to make
the leftmost outlet a control outlet, and the rest signals. The other
way round, things work fine.

Just to confirm, I had the same experience.  I gave up, and placed my  
message outlet last (rightmost) instead.

On Feb 5, 2007, at 3:36 AM, Jamie Bullock wrote:

> On Mon, 2007-02-05 at 12:08 +0100, Olaf Matthes wrote:
>
>>
>> In Max you have to create the outlets the other way round (right to
>> left), not left to right as in Pd.
>>
>
> Yes, but my question is: is it possible for the outlets to be of
> arbitrary type "signal"/"control"? My problem occurs if I try to make
> the leftmost outlet a control outlet, and the rest signals. The other
> way round, things work fine.
>
> Jamie
>


On Mon, 2007-02-05 at 09:35 -0800, Joshua Kit Clayton wrote:
> On Feb 5, 2007, at 3:36 AM, Jamie Bullock wrote:
>
> Your findings are correct and described in the SDK documentation.  
> First paragraph of "Writing MSP Code":"New Instance Routine":
>

Ooops. Thanks for the info. I should have RTFM :)

@JoshuaKitClayton What did you say here? your comment was erased. This paragraph doesn't seem to be in the documentation and I'm getting the same error (and crashes)

This seems to be outlined here:
http://peabody.sapp.org/class/350.838/read/WritingMax_MSPExternals.pdf 

Bottom of page 209.

I know I'm reviving a four year dead thread, but @AudioMatt came back after 10 years, so maybe somebody else will too.

This seems also to be the case in the min-devkit. Max 8 shows the ugen_connect issue and follows with a complaint about infinite recursion.


Outlet creation order

André Rangel

An audiovisual experiment, that implements spatio-temporal synchronisation between visible and audible events, happened. This experiment was materialized with light – array of LEDs, and digital sounds widespread by an array of four loudspeakers. A computer program, based on a video white noise generator, calculates in real time unpredictable rhythmic sequences that are perceived as precisely located audiovisual events.

Max (and Jitter) is used to generate and control all visible and audible events in this installation.

An audiovisual experiment, that implements spatio-temporal synchronisation between visible and audible events, happened. This experiment was

sail-synchronous-as-in-life

Sail -  Synchronous As In Life

Ricardo Thomasi

This is part of my PhD research on musical structuring based on emergence theories, called Ecos Studies, in which I handle with the Audible Ecosystems paradigm as experimental territory. Max supported us by providing the modelling environment for our acoustic-digital feedback-loop control engine, which we are calling Spatial Instrument. Spatial because it is a hybrid instrument (acoustic and digital) that relies on the physicality of the acoustic environment, the equipment (microphones, speakers, cables, dsp, etc.), the distances between the components, and therefore space. We are developing several tools, theoretical and technical, seeking strategies for the realization of audible ecosystems.

Nodes object helped to implement the matrix where we control the topology of simultaneous feedback loops and feedback layers. No external object was used.

This is part of my PhD research on musical structuring based on emergence theories, called Ecos Studies, in which I handle with the Audible Ecosystems paradigm as experimental territory.  Max supported us by providing the modelling environment for our acoustic-digital feedback-loop control engine, which we are calling Spatial Instrument. Spatial because it is a hybrid instrument (acoustic and digital) that relies on the physicality of the acoustic environment, the equipment (microphones, speakers, cables, dsp, etc.), the distances between the components, and therefore space.  We are developing several tools, theoretical and technical, seeking strategies for the realization of audible ecosystems. 

Nodes object helped to implement the matrix where we control the topology of simultaneous feedback loops and feedback layers. No external object was used. 

This is part of my PhD research on musical structuring based on emergence theories, called Ecos Studies, in which I handle with the Audible 

spatial-instrument

Oh Man Great Step of Echo Sound... Best of Luck for Your PHD Research on it. Unique and Technology Based.

Spatial Instrument

fraction

On macOS, i have no problem to disable the runtime console when building a standalone, but i can't manage it on Windows OS.

"statusvisible" is uncheck in the standalone object, but it doesn't seem to do anything for windows. I need to find a way to disable the console on windows OS as well,

Hi,
On macOS, i have no problem to disable the runtime console when building a standalone, but i can't manage it on Windows OS.

"statusvisible" is uncheck in the standalone object, but it doesn't seem to do anything for windows. I need to find a way to disable the console on windows OS as well,

Hi,
On macOS, i have no problem to disable the runtime console when building a standalone, but i can't manage it on Windows OS.

"statusvisi

disable-runtime-console-in-standalone-windows

Disable runtime console in standalone (Windows)

personal_username

Just found out the [value] object cannot be dynamically set like [receive] (using "set").

[receive] won't work for me as I might need to recall the value after it has been sent via [send].

Just found out the [value] object cannot be dynamically set like [receive] (using "set").
Is there a workaround to this?
[receive] won't work for me as I might need to recall the value after it has been sent via [send].

Hi guys, 
Just found out the [value] object cannot be dynamically set like [receive] (using "set").
Is there a workaround to this?
[receive]

dynamic-value-or-viable-alternatives

Don't use 'set'.  In Max Reference, the description for value explains what to do:

Shares data with other value objects of the same name. If you send a message (number, list, or anything else) to one value object, it is set for all value objects with the same 'name' argument. You can get the contents out of a particular value object by sending it a bang. 

Sorry for the delay.
I realised dynamically setting a [value] is not really possible unless I *create a new one*.
Here's the example:

As your example shows, you cannot dynamically change the name of a value object.  You are correct, you would have to script a new  value object (possibly after scripting the removal of the one with the wrong name, if that's relevant).

But let's consider the objective more broadly.  If it what you want is to dynamically select between named values or named sets of data, the value object is probably not your best tool.  Have you considered using the coll object or the dict object?  Those are designed for just that purpose.   However, if you want multiple  coll objects or dict objects that can all access the same data, you would have to save the data to file in order to share it.


as i dont like [s] / [r], i use [v] in rare cases to be able to send data across patchers.

but i have never felt the need to rename them, and at least to my understanding it would be a bit strange to rename the handle of a variable.

however, scripting is slow but thread safe.

and to have a "sender" [v] or [pvar] with some 5 different names, you could create all 5 and use a gate to switch between them.

so this type of workaround would also exist.

this reminds me a bit of using dynamic arguments for route/select, which only works when there is only one argument to the object box. then the other day you think "wtf? why does it stop working?"


Thanks for your replies guys! :-)
Even if I still think that it would be a nice touch to have [value] to be set with a message, I agree with both of you on dict/coll or dynamic routing.
I'll see what fits best my patch, again: thanks! 

dynamic [value], or viable alternatives

msnf

Hi, is there the people who works with windows Max UI & touch screen? NOT MIRA!

Max UI is for desktop and I search to help for develop touch screen interface for Max. Maybe somebody did it?

Hi, is there the people who works with windows Max UI & touch screen? NOT MIRA!
Max UI is for desktop and I search to help for develop touch

max-ui-on-touch-screen

I'd love to see a multitouch map like the Lemur multiball. Please!!! :)

Are you talking about designing buttons in a UI way for a desktop hooked up to a  touch monitor? Or do you mean the Max UI in presentation mode doesn't work on a touchscreen? I delivered a project where I had to create a UI for a touchscreen that controlled jitter via openGL and jit.phys.picker. 

From my recollection touch events in this scenario work just like mouse events, however, I don't recall  whether multitouch worked as the interface wasn't designed for any multitouch gestures. 

I stripped this down from a much larger patch on a project I worked on in case it's of any use. 

Thank you very much for your example, but I talk about UI like smartphone or ipad. There are no scroll bars and you move the content of the window with your finger directly. After that the window's velocity descerelate.
Other pb is the numberbox. It's absolutely not user friendly to change the value by moving with finger and it's very very hard to find exactly values...
There are number of difficulties to create an application with interface for touche screen... Max is not ready to do it. it's why I ask if somebody did it and has experience.

 We offer a wide range of touch display solutions that can be customized and directly integrated into touch screen vending machine . BaoBao is already dealing with a major European vending machine producer and cooperates closely with them to develop a tailor made display solution to fulfill specific requirements and features. 

Max UI on touch screen

chapelier fou

Vinyl_Player 2.00.maxpat

I'm working on an interactive installation where a turnstile is equipped with a sensor outputting its absolute position in the range [0. 1.].

One thing I'm struggling with is the attempt to make it act as a vinyl deck. Attached is a simple patch illustrating my idea that contains a simulation of the physical turnstile.

At least two things could be currently improved :

2. The ability to "densify" the audio file across the turnstile position. In other terms, to get smaller movements having a more drastic effect. The resolution of the encoder will be 360 steps.

I'm working on an interactive installation where a turnstile is equipped  with a sensor outputting its absolute position in the range [0. 1.].
One thing I'm struggling with is the attempt to make it act as a vinyl deck. Attached is a simple patch illustrating my idea that contains a simulation of the physical turnstile. 

At least two things could be currently improved : 

1. The "vibrato" effect
2. The ability to "densify" the audio file across the turnstile position. In other terms, to get smaller movements having a more drastic effect. The resolution of the encoder will be 360 steps. 


 
Hi there, 
I'm working on an interactive installation where a turnstile is equipped  with a sensor outputting its absolute position in th

help-with-a-patch-simulating-vinyl-deck-type-audio-playing

Help with a patch simulating vinyl deck type audio playing

👽It W∆s ∆lienz👽

this was generated from another all-in-one patch i made(will keep the patch to myself a bit to make an album from, then share later), thought folks might get a kick out of hearing the live.step default MIDI sequence like this, and see the default GL texture dancing to it:

synthesized/generated entirely in max/msp<br />
the default sequence of the live.step object was used for the pitched material of the music(also, the visuals use the default jit.gl.texture as their basis)

petSeviL

also, here’s an extended audio version(i can’t do vid and audio with audio at 96k, only with audio at 48k(my comp is too slow), but synthesizing these sounds end up much more rich at 96k, so i created this separate version to appreciate that, even though soundcloud only allows 48k, it still carries the sound of the higher-sample-rate synthesis):

(Thanks @Cycling74 for making such beautiful music☝️)

this was generated from another all-in-one patch i made(will keep the patch to myself a bit to make an album from, then share later), thought folks might get a kick out of hearing the live.step default MIDI sequence like this, and see the default GL texture dancing to it:


also, here’s an extended audio version(i can’t do vid and audio with  audio at 96k, only with audio at 48k(my comp is too slow), but synthesizing  these sounds end up much more rich at 96k, so i created this separate  version to appreciate that, even though soundcloud only allows 48k, it still carries the sound of the higher-sample-rate synthesis):


(Thanks @Cycling74 for making such beautiful music☝️)
🤘🍻

this was generated from another all-in-one patch i made(will keep the patch to myself a bit to make an album from, then share later), though

riffing-off-cycling74's-defaultz

riffing off Cycling74's defaultz

Ben Bracken

* currently, Windows users will need to install 

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

*NOTE* currently, Windows...

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. NOTE currently, Windows...

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

Great!!! Thanks!

Yes, it is Apple Silicon native! Thanks for letting us know that it wasn't immediately clear. We've got that info on the home page, forum...

This seems to be outlined here: http://peabody.sapp.org/class/350.838/read/WritingMax_MSPExternals.pdf Bottom of page 209. I know I'm...

An audiovisual experiment, that implements spatio-temporal synchronisation between visible and audible events, happened. This experiment...

This is part of my PhD research on musical structuring based on emergence theories, called Ecos Studies, in which I handle with the Audible...

Hi, On macOS, i have no problem to disable the runtime console when building a standalone, but i can't manage it on Windows OS. "statusvisi

Thanks for your replies guys! :-) Even if I still think that it would be a nice touch to have [value] to be set with a message, I agree...

Thank you very much for your example, but I talk about UI like smartphone or ipad. There are no scroll bars and you move the content of the...

Hi there, I'm working on an interactive installation where a turnstile is equipped with a sensor outputting its absolute position in th