On Thu, 2016-01-14 at 11:10 -0500, Martin Peach wrote: > ...although OSC 1.0 says that any sequence of non-null ASCII > characters can be a string. The unpackOSC implementation may be > rejecting it because Pd doesn't like such characters in its symbols.
Indeed, the ASCII 10 character seems to be causing the error message of [unpackOSC]. However, Pd deals with such symbols just fine, it seems. Try this: [10 ( | [makefilename %c] | [symbol this$1isa$1symbol$1with$1line$1breaks( | [print] The OSC specifies OSC-strings as follows (from [1]): "OSC-string: A sequence of non-null ASCII characters followed by a null, followed by 0-3 additional null characters to make the total number of bits a multiple of 32." [1]: https://code.google.com/p/osc-midi-bridge/wiki/OSCSpecification#Atomic_Data_Types There is no mention of disallowing newline characters. Roman > On Thu, Jan 14, 2016 at 11:06 AM, Martin Peach <chakekat...@gmail.com> > wrote: > > > On Thu, Jan 14, 2016 at 11:03 AM, Martin Peach > <chakekat...@gmail.com> wrote: > Actually it's because the string is terminated with an > ASCII Carriage Return (decimal 10), which is not > allowed by the OSC spec, so it gets rejected. > > > > Sorry, Line Feed, is ASCII 10. > > > Martin > > > > _______________________________________________ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list