Re: [PD] vanilla replacement for mrpeach/routeOSC

2019-04-30 Thread Daniel Iglesia
In case it's of use, I had this problem as well, and did the fiddly arcane method for pure vanilla. See this patch, and look in the abstractions 'oscparse-mobmuplat' and 'oscformat-mobmuplat'. They take the oscparse/oscformat message convention (i.e. spaces) and turn it into an address with

Re: [PD] vanilla replacement for mrpeach/routeOSC

2019-04-30 Thread Christof Ressi
Thanks. The idea really came from zexy's l2s and s2l objects which I use so often that I thought I have to reimplement them for Pd vanilla. > String processing is one area that Pd doesn't exactly lead the pack, I'm secretely dreaming about regex support for [text] :-) > Gesendet: Dienstag, 30.

Re: [PD] vanilla replacement for mrpeach/routeOSC

2019-04-30 Thread Christof Ressi
> [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

[PD] vanilla replacement for mrpeach/routeOSC

2019-04-30 Thread Philip Stone
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

Re: [PD] music DSP job, Fender, Scottsdale, AZ, USA

2019-04-30 Thread Julian Brooks
(looks on slightly enviously from afar) That'll be a nice gig for some lucky soul. As an aside -- I went to NY in my early 20's and ended up in Manny's (famous guitar shop). Had a go on a '58 Fender Precision, all the paint worn off the back of body and neck, still had the bell over the bridge -

Re: [PD] [keyname] for space bar toggles upper/lowercase

2019-04-30 Thread IOhannes m zmoelnig
On 30.04.19 15:49, Peter P. wrote: > Hi, > > I just found out that the keyname for space bar is spelled > Space > or > space > depending on if it is a key up or down. Can anyone confirm this on a > non-Linux OS? on windows you always get "Space". afaict, this is related to the

Re: [PD] get keyboard events without repeats (in 2019)

2019-04-30 Thread IOhannes m zmoelnig
On 30.04.19 15:41, Peter P. wrote: > Katja, > > I am trying to use your idea about holding back key ups. However it > seems that [keyup] outputs 0 for letter keys, and numbers for the number > keys. I can't seem to figure out why. i would say that this is a bug. (it works as epxected on windows

[PD] [keyname] for space bar toggles upper/lowercase

2019-04-30 Thread Peter P.
Hi, I just found out that the keyname for space bar is spelled Space or space depending on if it is a key up or down. Can anyone confirm this on a non-Linux OS? cheersio, P ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and

Re: [PD] get keyboard events without repeats (in 2019)

2019-04-30 Thread Peter P.
Katja, I am trying to use your idea about holding back key ups. However it seems that [keyup] outputs 0 for letter keys, and numbers for the number keys. I can't seem to figure out why. But it has the consequence that your nice idea will possibly not work if two or more keys are held down

Re: [PD] get keyboard events without repeats (in 2019)

2019-04-30 Thread Peter P.
Christof, I am not sure if your abstraction behaves on my OS as you conceived it. Key entries in the table do not get reset. Subsequent key downs hang therefore indefinitely... * Christof Ressi [2019-03-18 17:44]: > for non-control keys this can be easily done in an abstraction (see >

Re: [PD] 'Find externals' under Wine

2019-04-30 Thread IOhannes m zmoelnig
On 29.04.19 19:23, Roman Haefeli wrote: > I > wonder if extracting fails because the downloaded file is renamed: > > osc[v0.2~git20181006](Windows-amd64-32).dek -> > osc[v0.2~git20181006](Windows-amd64-32).dek.zip > > Somewhere a .zip extension is appended to filename, .zip files end up > with