Daniel Craig

Hello
Since upgrading from 8.3.1 to 8.5.1 I have noticed a change in the behaviour of textedit.
Upon banging the object, the text output now adds a backslash before all apostrophes.

For example, in the following patch;   
Test.json "Test Sound" "" """    
becomes.  

Does anybody know how I might be able to stop this from happening?
I have messed around with the attributes with no luck.
Alternatively, is there a neat way to later on remove all backslashes?

TexteditExample.maxpat

Hello
Since upgrading from 8.3.1 to 8.5.1 I have noticed a change in the behaviour of textedit.
Upon banging the object, the text output ... 

text-edit-changed-behaviour-8-5-1

Text Edit changed behaviour 8.5.1

This has been bugging me for the past few days, I am trying to make a device that preserves the formants while still maintaining pitch and I have gotten stuck. Here is the circuit I am trying to replicate in max: 

And here is my circuit (please note that "?" is a replacement for a "Spectral envelope (via cepstrum)" as I am not sure what I should put there):


If anyone would be able to make a circuit so that I would be able to go in and learn and explain what everything means and why it is circuited that way you will be thanked immensely, I've seen some people using pfft~ and carpol and I am completlely lost as to how I will fix this problem. Any help much appreciated.  -Kind Regards, Leo :))

Circuit.PNG

TRASH.PNG

This has been bugging me for the past few days, I am trying to make a device that preserves the formants while still maintaining pitch and ... 

pitch-shifting-while-maintaining-formants-from-scratch

wasn´t it tom erbe who suggested that you could perform some kind of logarithmic spectrum shift inside the FFT to do this kind of thing? 

but i´ve never seen it anywhere and pfft still has that harsh frame count limit.

nothing in that patch makes any sense. 
pitchshift~.maxhelp asap!

Hi! So i checked maxforlives manual and the pitchshift is working as intended, shifting the pitch up one octave. :)

Update! I reworked some the patch and now it's starting to work as intended and sound like a formant shifter, although it sounds very choppy and robotic. 

Is there anything I can do to get it sounding more natural? And is there anything in the circuit that should be reworked? If so please answer or upload an altered AMXD of my patch. - Kind regards, Leo :)

Also one more thing: Im not sure where the subtracted signal from the pitchshift should go? If anyone has any answers please leave them bellow. Anything is greatly appreciated! :))

Pitch shifting while maintaining formants from scratch

Faranak Hosseini

how can I make a visual music in max which is transmodal ( animations are acting with some neats of the music with using fffb~)

make-a-visual-music

make a visual music

Cephas Teom

Super excited about RNBO. Found it ridiculously simple to build a synth, build it the integrate into a web page. So many possibilities!

I've built a basic FM patch that sounds as you would expect when played in MAX. However, when I export it and included it in my webpage it sounds completely different - almost like the modulation is not happening and, instead we're hearing two tones.

Here's my RNBO patch:

import { createDevice, MIDIEvent } from '@rnbo/js'

let rawPatcher, patcher;
let device, modi, harm;
let WAContext = window.AudioContext || window.webkitAudioContext;
let context = new WAContext();

window.addEventListener('click', () => context.resume() );

function playNote(pitch) {
    let midiChannel = 0;

    let noteOnMessage = [ 144 + midiChannel, pitch, 100];

    let noteOffMessage = [ 128 + midiChannel, pitch, 0 ];

    let midiPort = 0;
    let noteDurationMs = 250;

    let noteOnEvent = new MIDIEvent(context.currentTime, midiPort, noteOnMessage);
    let noteOffEvent = new MIDIEvent(context.currentTime * 1000 + noteDurationMs, midiPort, noteOffMessage);

    device.scheduleEvent(noteOnEvent);
    device.scheduleEvent(noteOffEvent);
}

const fm = async () => {
    rawPatcher = await fetch("/json/fm2.export.json");
    patcher = await rawPatcher.json();
    
    device = await createDevice({ context, patcher });
    modi = device.parametersById.get("modi");
    harm = device.parametersById.get("harm");

    device.node.connect(context.destination);
};

fm()

window.addEventListener('click', () => {
    harm.value = 2
    modi.value = 1
    playNote(60)
});

In Max, the same synth with a harmonicity of 2 and a mod index of 1 create an open, concordant tone. The web export sounds like a bell, as if you're hearing both the carrier and the modulator and they are not multiples of each other.

This may not be a bug - there may be something obvious that I'm doing wrong - but it's odd that the same synth behaves differently when compiled.

Screenshot 2022-11-10 at 18.11.10.png

Hi there!
Super excited about RNBO. Found it ridiculously simple to build a synth, build it the integrate into a web page. 

rnbo-fm-patch-export-to-web-results-in-a-different-sounding-synth

Hi there. Would you mind copying the patcher  content compressed? (Select all the objects and then select copy compressed from the edit menu). 

This way it’s easier to reproduce without having to duplicate the patch from your screenshot.  

One debugging step would be to check the values of all of the parameters using for exampleconsole.log(device.parametersById.get("harm").value);
for each of your parameters, just to check that they are all set correctly.  

Florian - alas, I'm just trying out RNBO and haven't bought a license yet. So, it doesn't let me copy the code. If I do, I'll paste it here...

Is the synth polyphonic? Maybe there is a param that is not initialized correctly in some voices?

It is polyphonic yes. I've rebuild it as simple as possible to illustrate the issue - sorry I can't export more easily:

But when exported to web, same values sound completely different - unharmonious, despite the modulator being at the same frequency as the carrier!

One thing I notice is that you have an [out~ 0] (which I am surprised compiles). Does it change anything if you use [out~ 1] and [out~ 2] instead?

Changed and exported. Still the same issue. I wonder if the harm and modi inputs in JS are getting scaled somehow?

Even simpler - have removed any parameter inputs and just left the internal calculation:

import { createDevice, MIDIEvent } from '@rnbo/js'

let device;
let WAContext = window.AudioContext || window.webkitAudioContext;
let context = new WAContext();

window.addEventListener('click', () => context.resume() );

function playNote(pitch) {
	let midiChannel = 0;

	let noteOnMessage = [ 144 + midiChannel, pitch, 100];

	let noteOffMessage = [ 128 + midiChannel, pitch, 0 ];

	let midiPort = 0;
	let noteDurationMs = 250;

	let noteOnEvent = new MIDIEvent(context.currentTime, midiPort, noteOnMessage);
	let noteOffEvent = new MIDIEvent(context.currentTime * 1000 + noteDurationMs, midiPort, noteOffMessage);

	device.scheduleEvent(noteOnEvent);
	device.scheduleEvent(noteOffEvent);
}

const fmSimple = async () => {
    const rawPatcher = await fetch("/json/fm-simple.export.json");
    const patcher = await rawPatcher.json();
    device = await createDevice({ context, patcher });
    device.node.connect(context.destination);
};

fmSimple()

window.addEventListener('click', () => {
    playNote(48)
});

It's as if the math being applied to the signal is incorrect.

Just experimented with the Synth Building Blocks package and it behaves in the same way:
https://rnbo.cycling74.com/explore/synth-building-blocks-intro 

Here's the exported FM Synth JSON file - no changes made to the patch:

import { createDevice, MIDIEvent } from '@rnbo/js'

let device;
let WAContext = window.AudioContext || window.webkitAudioContext;
let context = new WAContext();

window.addEventListener('click', () => context.resume() );

function playNote(pitch) {
	let midiChannel = 0;

	let noteOnMessage = [ 144 + midiChannel, pitch, 100];

	let noteOffMessage = [ 128 + midiChannel, pitch, 0 ];

	let midiPort = 0;
	let noteDurationMs = 250;

	let noteOnEvent = new MIDIEvent(context.currentTime, midiPort, noteOnMessage);
	let noteOffEvent = new MIDIEvent(context.currentTime * 1000 + noteDurationMs, midiPort, noteOffMessage);

	device.scheduleEvent(noteOnEvent);
	device.scheduleEvent(noteOffEvent);
}

const fmSimple = async () => {
    const rawPatcher = await fetch("/json/ssb-fm.export.json");
    const patcher = await rawPatcher.json();
    device = await createDevice({ context, patcher });
    device.node.connect(context.destination);
};

fmSimple()

window.addEventListener('click', () => {
    device.parametersById.get("ratio").value = 3;
    device.parametersById.get("index").value = 5;
    playNote(48)
});

Again, odd behaviour when changing the values. For example, if you change the modulation index value, the pitch changes, rather than just the timbre.

if you look at the json, you can see it looks like you have some kind of per voice parameters setup 

"paramId": "poly/1/index",
 "paramId": "poly/2/index",
 "paramId": "poly/3/index",
 "paramId": "poly/4/index",

as well as ..
"paramId": "index",
"paramId": "poly/index"


it'd be interesting to see the source code to see how this is actually being used...


have you tried exporting as max externals/vst... do you get a similar behaviour?
it would be useful to know if this is solely web export related issue or a more general code generation rnbo issue.
(it'd also be easier to 'debug' if it exists in the c++ code export) 


(Ive been focusing on monophonic rnbo suff at the moment, so haven't been looking at much poly c++ code... though I did see one oddity early on when I tried the poly code export)

Still looking into this but as an aside - I assume you are exporting with per-voice parameters enabled either on the [rnbo~] object or in the export configuration?

Yes, that is correct. I've done it with and without to the same effect. Going to have a go exporting some even simpler patches with isolated operators and see if I can find the one that's at fault.

So, it's not to do with the polyphony or any of the parameter inputs. Here's a patch with a constant carrier frequency, harmonicity and mod index.

I just recreated the patch in max/rnbo, and in Max, mine sounds exactly like the second example (which. you label web ) .. not the first.

I also exported the c++ code, and ran against my template/host , and it sounded identical.


so, from what I hear, your first example in max is the issue, not the second.


edit for those that want to try the rnbo patch... 


Thank you for sharing this with us. I think there's at least a few things here that are worth greater investigation.  
In my local testing related to your minimal example with audio recording, a Max (not RNBO version) sounds like your first audio recording. A RNBO version running in Max sounds like your second audio recording (I believe the same as @technobear). I haven't had a chance to dig into the RNBO in Max vs RNBO as wasm in web browser yet, but there are some interesting things to note here, which may also relate to the RNBO in Max vs RNBO as wasm in browser. 

First, there are possibilities of differing sounds with this type of dsp based on where the phase of the two oscillators are with respect to one another. The way in which that might work out might be dependent on a variety of factors like vector size, the ways in which various parameters might update differing parts of the graph (e.g. if multiple parameters are meant to be set simultaneously, but perhaps happen in two different vectors for some reason), the way in which phase is initialized, and or drift across differing oscillators. 

Second, the cycle~ oscillator in gen and RNBO uses a combination of floating point and fixed point arithmetic in a different way than Max, and there could be aspects of this implementation that relates to these issues, especially when multiplying the output of these oscillators with very large numbers as you are doing in your patch. I've isolated a very simple example this is difference between RNBO and Max below. When initially turning on dsp there is minimal difference which noticeably grows over time when scaling with a large factor like 6600 or more like your example does. It could be that this is really pushing some of the boundaries of RNBO cycle's 32bit fixed point phase increment (as opposed to Max cycle's double precision floating point phase increment).

I can do some deeper investigations, but likely won't get much further until sometime later this week. In the meantime, perhaps it gives you and others some additional starting points to scrutinize. I would suggest further analysis by elimination, paying close attention phase, math precision and what results you are expecting. There of course could be other issues at play here, and only now that RNBO is released some very subtle issues for us to improve may come to light. Thank you for helping us track them down. 

ah, indeed... I assumed the OP was testing the rnbo patch, not a 'similar' patch written as max.

(thats comparing apple's n' oranges in my mind)


yes, if I use Max/MSP objects, I hear the first example.
but, if its Max RNBO or C++ RNBO then I hear the second example.

so it not web related at all (which was my suspicion) , rather  RNBO vs Max.

in this case, as @Joshua says, either 32bit vs 64bit , 
or perhaps order of evaluation of initialisation or processing... this could cause phase differences.


Thanks so much for your considered replies here. Interesting that I only hear the unwanted outcome once I've exported the RNBO patch. Sounds fine when I'm using a RNBO patch within Max - which points to some additional environmental factors that could be affecting the signal processing. 

It also makes sense that the multiplication by large values inherent in FM synthesis would expose small phase artefacts. I'll carry on investigating based on the suggestions here, and if I have any further insight, I'll share it.

Once again, thanks so much for your contributions and time.

just a quick note that after further debugging we identified an issue with modulating cycle~ that led to the discrepancies you are experiencing between the Web / WASM Export and running the patch inside rnbo~ in Max or within other exports targets.

We have a fix for this that will be released with the next update to RNBO.
Thanks again for your report and helping us to track this down.

That's great news. I'll look forward to the update. I've been enjoying RNBO in the meantime. Thanks for such an excellent piece of technology.

If you haven't already, it may be worth checking the other oscillators in the same context. I swapped out cycle for 'saw', 'tri', and 'pulse'. Saw appeared to work as expected, whilst tri and pulse exhibited similar behaviour to cycle.

RNBO FM patch export to Web results in a different sounding synth

pol olory

Hi folks !! I've been making a kind of Arduino controller to create a buffer sample synth in max 8.
But I have a big problem... Arduino is always sending information so when I push a button to trigger the buffer, Arduino sends a , but it sends it a lot of times and that makes the buffer sound horrible... the buffer is triggered several times at a very high speed. It does the same when using AUsynth (Yes ! I'm a Mac user )... a kind of growling horrible sound ! I've tried several objets to avoid this : <change> and <sel> but it does not seem to change anything... it's like if I had a metro triggering <makenote> indefinitely until the button is released.
Does anyone know how to avoid this ? Thanks for your answers :-) !

Hi folks !! I've been making a kind of Arduino controller to create a buffer sample synth in max 8.
But I have a big problem... 

avoid-repeated-numbers

in arduino send button press only when value changes.
either use some ready made library like bounce,
or create 2 button states, current and past and then
if button is HIGH, and not same as EXbutton then send
and declare EXbutton = button
something like

int button; int EXbutton;
void setup() {Serial.begin(9600);}

void loop(){
int button = digitalRead(2);
if (button != EXbutton and button == HIGH)
{Serial.Println('a'); EXbutton = button;}
delay(10);  // debounce  bit
}

even better woud be to pull input high and react to LOW state when 
shorted to ground


Thank you all for all these precious advices ! I'm checking all that... It might take time because my Arduino and max knowledge is so poor .... ;-) 

you could also post maxpatch showing how you receive that 'a'
from arduino through serial object.
Maybe you also trigger playback on newline or other things ...


Here is my patch to connect Arduino to max : 

And this is one of my Arduino codes to connect instruments : They all use the same structure than this, and what is really important for me is that the sensor values go through the Serial monitor in order to retrieve the information in max ...

Serial.begin(9600);  // Initialise la série de communication à 9600 bits par seconde

int etatbouton10 = digitalRead(bouton10);

int etatbouton11 = digitalRead(bouton11);

int etatbouton12 = digitalRead(bouton12);

why don't you insert change object in Max after unpacking button state ?

the way you did that Arduino code, you send 1 list of ALL read inputs, so there in no way to send one item in the list only if it changes.
P.S.
You use interrupts, no interrupts, don't know what exactly do you want do with that, but at the end you use slow overal loop rate of 150ms becuse of that delay ???

Débitmètre  is water flow senor, but it is not implemented.
//Accéléromètre are simply 3 analog inputs.

All this can be done much better, with faster
sensor reports, but less data sent.




Avoid repeated numbers

tyler mazaika

I'm crashing Live multiple times a day while developing and testing a device which is using ease to generate some (ok, lots) of MPE data.  All the crashes are happening with similar backtrace pointing to the 'ease' external.    The crash happened with both ease 1.2.2 and 1.2.3.


Do 'ease' bugs go to the normal cycling74 support channel?

Process:               Live [11322]
Path:                  /Applications/Ableton Live 11 Suite.app/Contents/MacOS/Live
Identifier:            com.ableton.live
Version:               11.2.6 (2022-10-26_5ce91bbb60) (11.2.6 (2022-10-26_5ce91bbb60))
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2022-11-30 18:15:04.3429 -0500
OS Version:            macOS 12.5.1 (21G83)
Report Version:        12
Anonymous UUID:        A2A819DC-C3C7-E9C3-419B-2AC9C890EA7E

Sleep/Wake UUID:       2679F014-2A2B-4D43-8EDB-05A0C7CFF4F7

Time Awake Since Boot: 4100000 seconds
Time Since Wake:       36819 seconds

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [11322]

VM Region Info: 0 is not in any region.  Bytes before following region: 4302209024
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      1006e8000-104748000    [ 64.4M] r-x/r-x SM=COW  ...ts/MacOS/Live

Kernel Triage:
VM - Compressor failed a blocking pager_get
VM - Compressor failed a blocking pager_get
VM - Compressor failed a blocking pager_get
VM - Compressor failed a blocking pager_get
VM - Compressor failed a blocking pager_get

Thread 10 Crashed:: AudioCalc
0   ease                          	       0x2d72a9584 ease_base<ease>::apply_easing_function(double) + 300
1   ease                          	       0x2d72a9580 ease_base<ease>::apply_easing_function(double) + 296
2   ease                          	       0x2d72a93b4 std::__1::__function::__func<ease::number_message::'lambda'(std::__1::vector<c74::min::atom, std::__1::allocator<c74::min> > const&, int), c74::min::atom<std::__1::vector<c74::min::atom, std::__1::allocator<c74::min> > const&>, std::__1::allocator<c74::min> (std::__1::vector<c74::min::atom, std::__1::allocator<c74::min> > const, int)>::operator()(std::__1::vector<c74::min::atom, std::__1::allocator<c74::min> > const, int&&) + 40
3   ease                          	       0x2d72aae70 c74::min::message<(c74::min::threadsafe)2>::operator()(std::__1::vector<c74::min::atom, std::__1::allocator<c74::min::atom> > const&, int) + 156
4   ease                          	       0x2d72ac9d8 void c74::min::wrapper_method_float<ease, c74::min::wrapper_message_name_float>(c74::max::object*, double) + 176
5   MaxPlugLib                    	       0x2afac1780 outlet_float + 1428
6   line                          	       0x2d27035f0 line_tick + 152
7   MaxPlugLib                    	       0x2afaf3e44 scheduler_run_flags + 508
8   MaxAudioAPIImpl               	       0x128109a14 plugrunner_servicescheduler + 392
9   MaxAudioAPIImpl               	       0x1280ff540 plugrunner_process + 200
10  patcher                       	       0x128185df0 Wires::Process(plug_DeviceRef*, int, int const*, int const*, float const* const*, float* const*, __t_epii_REChunk*, __t_epii_REChunk*, __t_epii_MEChunk*, __t_epii_MEChunk**, __t_epii_REChunk**) + 856
11  Live                          	       0x1028df6fc 0x1006e8000 + 35616508
12  Live                          	       0x1028deda0 0x1006e8000 + 35614112
13  Live                          	       0x1018abad8 0x1006e8000 + 18627288
14  Live                          	       0x1018c6914 0x1006e8000 + 18737428
15  Live                          	       0x1018aeef0 0x1006e8000 + 18640624
16  Live                          	       0x1018af228 0x1006e8000 + 18641448
17  Live                          	       0x1011a55e8 0x1006e8000 + 11261416
18  Live                          	       0x1011a6100 0x1006e8000 + 11264256
19  libsystem_pthread.dylib       	       0x1ab73826c _pthread_start + 148
20  libsystem_pthread.dylib       	       0x1ab73308c thread_start + 8

{
    "source" : "P",
    "arch" : "arm64",
    "base" : 12199755776,
    "CFBundleShortVersionString" : "1.2.3",
    "CFBundleIdentifier" : "com.cycling74.ease",
    "size" : 147456,
    "uuid" : "4d509f87-041c-3da7-87a9-c45ffc9a56ee",
    "path" : "\/Users\/USER\/Library\/Application Support\/Cycling '74\/*\/ease",
    "name" : "ease",
    "CFBundleVersion" : "1.2.3"
  },

I'm crashing Live multiple times a day while developing and testing a device which is using ease to generate some (ok, lots) of MPE data. 

ease-external-sometimes-crashing-in-live

ease external sometimes crashing in Live?

pdelges

I discovered that an old patch of mine stopped working. After the infamous recent changes in [line] that break almost all my old patches (since Max2) I was afraid to discovered something similar.

Now it's buffer~'s read message that doesn't work correctly anymore with raw files. The readraw message has been introduced since Max8.2 or 8.3 and does work as expected, but I would hope that changes in Max don't break working patches.

I discovered that an old patch of mine stopped working. 

buffer~'s-read-behavior-changed

buffer~'s read behavior changed

Samuel Hvozdík

Hello, recently I made my first m4l device with which I was trying to simulate AudioMulch 10Harmonics Instrument.  And here comes the problem: every time I add the device to Ableton, the huge pop comes out. I don't know what I missed and I've tried to find some advice but with no success.  This is my first time with M4L so I don't know if this is usual problem or not. 

Turn off your speakers when adding the device. Thank you very much for response.

15Harmonics.amxd

Hello, recently I made my first m4l device with which I was trying to simulate AudioMulch 10Harmonics Instrument. 

max-for-live-device-pops-when-added

you are probably hard switching audio on / off,
or abruptly setting frequencies.
that can cause such pops and clicks.
init of that many cycle~ objects should be performed 
while output is muted.
all audio switches must be smoothed.




Thank you very much for the answer but sorry, I don't understand. For me it seems like I have all cycle~ objects already enabled when adding the device, but I don't get why it pops as I have every live.gain~ down. Is there any way to set up the toggle object automatically on device's start up? Because it looks like I need to turn off all cycle~ objects by default somehow.

I am not using Live, sorry.
I only listed few things that might cause that pops.
You can not turn off cycles by default, only enter some
default value, that could also be 0. 



Max for live device pops when added

matteo massimiliani

Funny enough I have not found any solutions/topics similar that had an answer. I am just seeking for the directory of the users prototypes which i cannot find!


Funny enough I have not found any solutions/topics similar that had an answer. 

prototypes-folder-directory

That directory lives inside of the Max application (or, rather, the Max "Package"). On a Mac, Control-click on the Max 8 icon and select Show Package Contents.
 
You'll find it in Contents > Resources > C74 > object-prototypes > (there will be folders for max, and m4l)

Prototypes folder directory?

Johannes Regnier

The display part of a patch I'm working on makes use of several jit.gl.text3d objects. When the graphic engine is set to "glcore", it suffers from a rather massive memory leak, making the patch unusable after a couple hours running. I traced back the problem to the  jit.gl.text3d objects (getting rid of them solve the issue).
Apparently this leak doesn't happen when setting the engine to "gl2".
Is there anything I should be aware when using glcore, that I maybe overlooked?

The display part of a patch I'm working on makes use of several jit.gl.text3d objects. 

jit-gl-text3d-memory-leak-with-glcore-graphic-engine-max-v-8-5-1

please send along the patch that exhibits the leak along with some instructions to get it running, and your system specs (About Max -> Copy support information to clipboard), and we'll check it out.

You can send to me directly if you prefer, or file an issue with support 

jit.gl.text3d memory leak with glcore graphic engine ( MAX v.8.5.1)

Ben Bracken

We have just released Max 8.5.1 and RNBO 1.0.1, which focuses on fixing crashes and other issues affecting OSes with certain language settings, and crashes in the Text Editor window when RNBO is not authorized. 


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

For a list of all Max 8.5.1 and RNBO 1.0.1 fixes, check out the change log below, or here:
https://cycling74.com/releases/max/8.5.1
https://cycling74.com/releases/rnbo/1.0.1

Enjoy!
Cycling '74

curve~: fixed list received during pending lists

Patches: fixed issues with saving / recalling invalid patchlines from patcher dictionary

Startup: fixed crash on machines with language settings that use extended characters

Text Editor: fixed crash on save in editor when RNBO is not authorized (coll, js, dict, etc)

param: Export no longer fails when extended characters are used for name

Plugin Target: handle spaces and extended characters in sample dependency file names

We have just released Max 8.5.1 and RNBO 1.0.1, which focuses on fixing crashes and other issues affecting OSes with certain language ... 

Cycling '74 Forums

Max 8.5.1 / RNBO 1.0.1 Released

We have just released Max 8.5.1 and RNBO 1.0.1, which focuses on fixing crashes and other issues affecting OSes with certain language ...

Text Edit changed behaviour 8.5.1

Hello Since upgrading from 8.3.1 to 8.5.1 I have noticed a change in the behaviour of textedit. Upon banging the object, the text output ...

Pitch shifting while maintaining formants from scratch

boost! .....

make a visual music

how can I make a visual music in max which is transmodal ( animations are acting with some neats of the music with using fffb~)

RNBO FM patch export to Web results in a different sounding synth

Hi Florian, If you haven't already, it may be worth checking the other oscillators in the same context.

Avoid repeated numbers

why don't you insert change object in Max after unpacking button state ? the way you did that Arduino code, you send 1 list of ALL read ...

ease external sometimes crashing in Live?

I'm crashing Live multiple times a day while developing and testing a device which is using ease to generate some (ok, lots) of MPE data.

buffer~'s read behavior changed

I discovered that an old patch of mine stopped working.

Max for live device pops when added

I am not using Live, sorry. I only listed few things that might cause that pops. You can not turn off cycles by default, only enter ...

Prototypes folder directory?

That directory lives inside of the Max application (or, rather, the Max "Package").

jit.gl.text3d memory leak with glcore graphic engine ( MAX v.8.5.1)

please send along the patch that exhibits the leak along with some instructions to get it running, and your system specs (About Max -> Copy ...

Cycling '74 Forums

.css-lq0bf2{font-size:18px;line-height:24px;font-weight:700;color:var(--theme-ui-colors-accent);-webkit-text-decoration:none;text-decoration:none;}.css-lq0bf2:visited{color:var(--theme-ui-colors-dark30);}.css-lq0bf2:hover{color:var(--theme-ui-colors-accent);}Max 8.5.1 / RNBO 1.0.1 Released

We have just released Max 8.5.1 and RNBO 1.0.1, which focuses on fixing crashes and other issues affecting OSes with certain language ...

Hello Since upgrading from 8.3.1 to 8.5.1 I have noticed a change in the behaviour of textedit. Upon banging the object, the text output ...

boost! .....

how can I make a visual music in max which is transmodal ( animations are acting with some neats of the music with using fffb~)

Hi Florian, If you haven't already, it may be worth checking the other oscillators in the same context.

why don't you insert change object in Max after unpacking button state ? the way you did that Arduino code, you send 1 list of ALL read ...

I'm crashing Live multiple times a day while developing and testing a device which is using ease to generate some (ok, lots) of MPE data.

I discovered that an old patch of mine stopped working.

I am not using Live, sorry. I only listed few things that might cause that pops. You can not turn off cycles by default, only enter ...

That directory lives inside of the Max application (or, rather, the Max "Package").

please send along the patch that exhibits the leak along with some instructions to get it running, and your system specs (About Max -> Copy ...

Max 8.5.1 / RNBO 1.0.1 Released