@ingox said:

@oid No question. I just wanted to show this way of implementing recursion in Pd. Isn't that a technical issue?

Oh yes it is, and a really badass one too. Thanks for letting me know that there are different kinds of recursive functions. I'm looking forward to learning your patch when my current show closes.

@KMETE You could also make a 10 track wav file and play that back.

Hi, I just wanted to report a related discovery. When REAPER loads a Camomile VST3 on an M2 Mac, it runs it via an x86 bridge process because they are compiled for Intel processors (so says the internet). With my plugins, this bridge process almost doubles their CPU overhead and causes REAPER to load quite slowly. Rewriting my plugins for PlugData addressed both issues--PlugData is apparently ARM processor-compatible.

edit: that said, I've seen REAPER crash twice now as I've edited patches in PlugData when it's hosted as a VST3. So be careful.

@FFW BWAH HA HA HA HA HA ... I just tested this insane version with Qlab and it worked:

Note to self: must get a life

Edit: a more modern version:

@FFW He he he....or since the backslash is always at a fixed position in the complete OSC control message, take the output of [oscformat] and just remove the byte at that position Oh wait, no, I think I'd have to also add some padding to the end to meet some message length requirement.

@whale-av said:

@jameslo There can be spaces in the address.... the [oscformat] help is full of them between symbols.

Between symbols is different from what I'm asking--I'm asking about within a symbol (i.e. "Container"). [oscformat patch 1] outputs "/patch/1" but what the Qlab OSC dictionary seems to imply it wants is ".../patch 1/...". From their documentation:
and the default name for the one uneditable audio patch you are allowed in the free version is "patch 1". (Did that sound like a complaint? In no way am I looking a gift horse in the mouth! Technically you have to buy a license to be able to adjust that level in the GUI, but for some reason it's adjustable via OSC and it works. I guess their license fee is a tax on non-hackers )

I'm trying to write an OSC control message for Qlab and one of the nodes in the path is supposed to be "patch 1". Yes, that's a space between the 'h' and the '1'. Is that legal OSC, and if so, how do you coax [oscformat] to emit it?

edit: Oh duh, I can just change the name of the patch to not have spaces. I'd still like to know if spaces are legal and possible with [oscformat] though.

@AndreasA I've never used Pduino or firmata, I've always just coded the Arduino-Pd interface using [comport] or TCP/IP. Here's my comport method: https://forum.pdpatchrepo.info/topic/13086/arduino-to-pd-vanilla/8

@AndreasA I'm assuming that the numbers you are seeing in the Arduino IDE are timings you captured on the Arduino, not using [realtime], is that correct? If so I think @alexandros is suggesting that you send those timings to Pd, instead of trying to measure the times between Arduino messages on the Pd side.

I'm guessing what you are measuring with [realtime] is when the OS schedules the Pd process to handle the next Arduino message, not when the message actually arrived at your computer, so that could explain the apparent rounding to the nearest 10 mS. I first saw this kind of rounding while investigating this problem: https://forum.pdpatchrepo.info/topic/13489/realtime-detecting-lack-of-correct-delay-in-the-delay-object

@fishcrystals said:

I'm curious tho - pretty sure opening the pd doc for the camomile VST3 with plugdata would fix the midi problem....

YESSSS! PlugData solved the issue. Thanks for bubbling that option to the top of my list.

@whale-av But I used PlugData as a VST3 in REAPER, so VST3 doesn't support MIDI except when it does?