Re: [PD] OSC limitations in Vanilla

2021-04-27 Thread Martin Peach
On Mon, Apr 19, 2021 at 6:51 PM Christof Ressi wrote: > > so what i'm really suggesting to "fix" the timestamps in [packOSC] is to use > logical time for *advancing time* (and add some offset to put the timestamps > into the same calendar as NTP) > > This corresponds to 2) in my previous mail.

Re: [PD] OSC limitations in Vanilla

2021-04-19 Thread Christof Ressi
so what i'm really suggesting to "fix" the timestamps in [packOSC] is to use logical time for *advancing time* (and add some offset to put the timestamps into the same calendar as NTP) This corresponds to 2) in my previous mail. While this sounds simple in theory, in practice you will

Re: [PD] OSC limitations in Vanilla

2021-04-19 Thread IOhannes m zmoelnig
On 4/18/21 10:32 PM, IOhannes m zmölnig wrote: i checked and double checked the specs but could not find anything about this. where do you get the idea that the OSC specs mandate wall clock time? OSC-1.0 speaks about "NTP format" (but this is just the structure of the 64 bits data chunk) and

Re: [PD] OSC limitations in Vanilla

2021-04-18 Thread Christof Ressi
Both of you are right. The basis for OSC timetags are of course the (NTP) system time, because that's usually the only shared time source between different apps. However, if you schedule several events in a DSP tick, you don't want to get the current ystem time for each event, because this

Re: [PD] OSC limitations in Vanilla

2021-04-18 Thread IOhannes m zmölnig
On 4/18/21 17:06, Martin Peach wrote: On Sun, Apr 18, 2021 at 6:06 AM IOhannes m zmölnig wrote: I don't really like the timestamp implementation in mrpeach (as it uses real time, rather than logical time), but better this than nothing... Logical time timestamps would only be accurate

Re: [PD] OSC limitations in Vanilla

2021-04-18 Thread Alexandre Torres Porres
Em dom., 18 de abr. de 2021 às 09:15, mitchell turner < mmturner2...@gmail.com> escreveu: > Alexandre, > I rewrote the TouchOSC templates using only vanilla (at least I think it > is vanilla). > It is :) cool Not sure this is what you are looking for but thought I’d reply. > not really, but

Re: [PD] OSC limitations in Vanilla

2021-04-18 Thread Martin Peach
On Sun, Apr 18, 2021 at 6:06 AM IOhannes m zmölnig wrote: > > I don't really like the timestamp implementation in mrpeach (as it uses real > time, rather than logical time), but better this than nothing... Logical time timestamps would only be accurate inside of the Pd instance. It could be

Re: [PD] OSC limitations in Vanilla

2021-04-18 Thread mitchell turner
Alexandre, I rewrote the TouchOSC templates using only vanilla (at least I think it is vanilla). These templates allow one to easily use the TouchOSC program on an iPhone/iPad and Pd. Not sure this is what you are looking for but thought I’d reply. If you are interested, you can take a look at

Re: [PD] OSC limitations in Vanilla

2021-04-18 Thread João Pais
I think I had problems in the past for not having [routeOSC] and [packOSC] when sending/receiving from other software such as reaper, but I can't confirm anymore. Other softwares will work with mrpeach, but not necessarily with vanilla. It's also convenient to use routeOSC for a cleaner patch

Re: [PD] OSC limitations in Vanilla

2021-04-18 Thread IOhannes m zmölnig
Am 18. April 2021 09:21:57 MESZ schrieb Alexandre Torres Porres : > I asked this on the facebook group, thought I'd ask it here as well. > Who > cannot be happy with vanilla's OSC support and still needs mrpeach and > stuff? I mean, really really need as in there's no way to deal with > such >