Re: [PD] vanilla replacement for mrpeach/routeOSC

Christof,

Your proposed new list methods are excellent, and would be extremely useful in many contexts. String processing is one area that Pd doesn't exactly lead the pack, but your improvements would go a long way towards fixing that.

Phil Stone UC Davis

On 4/30/19, 2:48 PM, "Christof Ressi" christof.ressi@gmx.at wrote:

> [list fromsymbol] -> [convert ‘/’ to space] -> [list tosymbol] -> [route]

that won't work because [list tosymbol] will output a single symbol with whitespace characters. 

what you want is: [list fromsymbol] -> [convert ‘/’ to space] -> [fudiparse]

BTW, I've just recently proposed new list methods for exactly such use cases: https://github.com/pure-data/pure-data/pull/595

Christof


Gesendet: Dienstag, 30. April 2019 um 18:47 Uhr
Von: "Philip Stone" <pkstone@ucdavis.edu>
An: "pd-list@lists.iem.at" <pd-list@lists.iem.at>
Betreff: [PD] vanilla replacement for mrpeach/routeOSC

I had some spare time to go back to my old Pd synthesizers and thought I’d try to see if recent developments in vanilla Pd could help me remove some of my external dependencies.

[oscparse] works great when taking FUDI in from [netreceive], and converting the multi-level OSC message into a list of separate symbols. However, it’s no help when dealing with OSC messages not originating from the network – i.e., ones passed around internally. I use internal OSC messages a great deal in my synthesizers, and need an efficient way to route them.

I can imagine a fairly arcane method: use [list fromsymbol] -> [convert ‘/’ to space] -> [list tosymbol] -> [route].  I fear, however, that this will be much less efficient than [routeOSC], especially the list-drippy [convert ‘/’ to space] part.

Are there any (vanilla) alternatives to this?


Phil Stone
UC Davis
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list