Menu
▾
▴
liblo-devel — Discussion of liblo library and application development
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
(7) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(7) |
| 2006 |
Jan
(1) |
Feb
(2) |
Mar
(3) |
Apr
(3) |
May
(5) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
(4) |
Oct
(17) |
Nov
(18) |
Dec
(1) |
| 2007 |
Jan
|
Feb
|
Mar
(8) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(6) |
Dec
(1) |
| 2008 |
Jan
(17) |
Feb
(20) |
Mar
(8) |
Apr
(8) |
May
(10) |
Jun
(4) |
Jul
(5) |
Aug
(6) |
Sep
(9) |
Oct
(19) |
Nov
(4) |
Dec
(35) |
| 2009 |
Jan
(40) |
Feb
(16) |
Mar
(7) |
Apr
(6) |
May
|
Jun
(5) |
Jul
(5) |
Aug
(4) |
Sep
(1) |
Oct
(2) |
Nov
(15) |
Dec
(15) |
| 2010 |
Jan
(5) |
Feb
(20) |
Mar
(12) |
Apr
|
May
(2) |
Jun
(4) |
Jul
|
Aug
(11) |
Sep
(1) |
Oct
(1) |
Nov
(3) |
Dec
|
| 2011 |
Jan
(8) |
Feb
(19) |
Mar
|
Apr
(12) |
May
(7) |
Jun
(8) |
Jul
|
Aug
(1) |
Sep
(21) |
Oct
(7) |
Nov
(4) |
Dec
|
| 2012 |
Jan
(3) |
Feb
(25) |
Mar
(8) |
Apr
(10) |
May
|
Jun
(14) |
Jul
(5) |
Aug
(12) |
Sep
(3) |
Oct
(14) |
Nov
|
Dec
|
| 2013 |
Jan
(10) |
Feb
(4) |
Mar
(10) |
Apr
(14) |
May
(6) |
Jun
(13) |
Jul
(37) |
Aug
(20) |
Sep
(11) |
Oct
(1) |
Nov
(34) |
Dec
|
| 2014 |
Jan
(8) |
Feb
(26) |
Mar
(24) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
(28) |
Oct
(4) |
Nov
(4) |
Dec
(2) |
| 2015 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(13) |
Jul
|
Aug
(3) |
Sep
(8) |
Oct
(11) |
Nov
(16) |
Dec
|
| 2016 |
Jan
|
Feb
(6) |
Mar
|
Apr
(9) |
May
(23) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
(7) |
May
(3) |
Jun
|
Jul
(3) |
Aug
|
Sep
(8) |
Oct
|
Nov
|
Dec
(3) |
| 2018 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
(4) |
Feb
|
Mar
(2) |
Apr
(6) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(31) |
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2021 |
Jan
(2) |
Feb
(2) |
Mar
(5) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
|
2
|
3
|
4
|
5
(2) |
6
|
|
7
|
8
|
9
(1) |
10
|
11
|
12
(1) |
13
|
|
14
|
15
|
16
|
17
(2) |
18
|
19
|
20
|
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
|
28
|
29
|
30
|
|
|
|
|
|
From: Stephen S. <rad...@gm...> - 2019-04-17 16:18:38
|
I sort of "just" did a release of 0.30 so I will probably let this sit
until I have some time to do more thorough comparisons of the current
state of liblo against other OSC implementations.
It is quite a problem however so I can understand wanting it released,
I'm surprised it wasn't noticed previously.
However, especially since this actually changes the behaviour of liblo
under some conditions it will be interesting to see if anyone reports
problems, so I think leaving it for a little while on master would be
precocious.
But I won't leave it as long as the time for the last release.
Steve
On Wed, Apr 17, 2019 at 9:10 AM "Steffen Jäger" <st...@gm...> wrote:
>
> Hi Steve,
>
> thank you very much for your quick answer and actions!
> For me this seems to be fixed as well.
> Is there already a release planned where this fix is going to be part of?
>
> Best regards,
> Steffen
>
> Gesendet: Freitag, 12. April 2019 um 17:29 Uhr
> Von: "Stephen Sinclair" <rad...@gm...>
> An: "liblo development list" <lib...@li...>
> Betreff: Re: [liblo] Part of curly braces command omitted
> Hi,
>
> I believe this is now fixed (and unit tested!) on master, along with a
> couple of other fixes to the pattern matcher. Thanks very much for
> pointing out this problem. Can you let me know if it seems fixed to
> you?
>
> regards,
> Steve
>
> On Wed, Apr 10, 2019 at 12:36 AM Stephen Sinclair <rad...@gm...> wrote:
> >
> > Just an update, I think I have a fix for this, but just working on
> > integrating it into the test suite and spending some time checking it
> > against the spec.
> >
> > regards,
> > Steve
> >
> > On Fri, Apr 5, 2019 at 1:47 PM Stephen Sinclair <rad...@gm...> wrote:
> > >
> > > Hi Steffen,
> > >
> > > Thanks for the bug report!
> > >
> > > I'll try to reproduce as soon as I get a few minutes.
> > >
> > > cheers,
> > > Steve
> > >
> > >
> > > On Fri, Apr 5, 2019 at 1:39 PM "Steffen Jäger" <st...@gm...> wrote:
> > >>
> > >> Hi everyone,
> > >>
> > >> first of all thank you for your very useful OSC library!
> > >> Currently using Liblo 0.28.
> > >> I encountered some (for me) unintended behavior in the pattern_match algorithm from (pattern_match.c) regarding curly braces (which seems to be unchanged in the relevant parts up to version 0.30).
> > >> For example if I send an OSC command like
> > >> /test/mute/{1,2,10,11,12} i 1
> > >> with callback handlers up and ready for paths
> > >> /test/mute/1
> > >> /test/mute/2
> > >> /test/mute/10
> > >> /test/mute/11
> > >> /test/mute/12
> > >> I would expect all of them to be invoked.
> > >> Instead only /test/mute/1, /test/mute/2, /test/mute/11, /test/mute/12 are called.
> > >> The /test/mute/10 is skipped.
> > >> This seems to be due to the fact that for /test/mute/10 in line 227 the statement if (c == *str) is successfully comparing c with value of '1' to '1' from "10" from str and then from here onwards something is going wrong with variable c which becomes ',' in line 241 and from here on is staying on ',' till the pattern match returns false.
> > >> Same behavior seems to happen with e.g.
> > >> /test/mute/{2,20}
> > >> Is there something wrong with my understanding in the usage of the curly braces in OSC or is this some bug?
> > >> Your help is highly appreciated.
> > >>
> > >> Thanks in advance!
> > >>
> > >> Best regards,
> > >> Steffen
> > >> _______________________________________________
> > >> liblo-devel mailing list
> > >> lib...@li...
> > >> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>
>
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
|
|
From: Steffen J. <st...@gm...> - 2019-04-17 07:10:05
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>Hi Steve,</div>
<div> </div>
<div>thank you very much for your quick answer and actions!</div>
<div>For me this seems to be fixed as well.</div>
<div>Is there already a release planned where this fix is going to be part of?</div>
<div> </div>
<div>Best regards,</div>
<div>Steffen</div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Freitag, 12. April 2019 um 17:29 Uhr<br/>
<b>Von:</b> "Stephen Sinclair" <rad...@gm...><br/>
<b>An:</b> "liblo development list" <lib...@li...><br/>
<b>Betreff:</b> Re: [liblo] Part of curly braces command omitted</div>
<div name="quoted-content">Hi,<br/>
<br/>
I believe this is now fixed (and unit tested!) on master, along with a<br/>
couple of other fixes to the pattern matcher. Thanks very much for<br/>
pointing out this problem. Can you let me know if it seems fixed to<br/>
you?<br/>
<br/>
regards,<br/>
Steve<br/>
<br/>
On Wed, Apr 10, 2019 at 12:36 AM Stephen Sinclair <rad...@gm...> wrote:<br/>
><br/>
> Just an update, I think I have a fix for this, but just working on<br/>
> integrating it into the test suite and spending some time checking it<br/>
> against the spec.<br/>
><br/>
> regards,<br/>
> Steve<br/>
><br/>
> On Fri, Apr 5, 2019 at 1:47 PM Stephen Sinclair <rad...@gm...> wrote:<br/>
> ><br/>
> > Hi Steffen,<br/>
> ><br/>
> > Thanks for the bug report!<br/>
> ><br/>
> > I'll try to reproduce as soon as I get a few minutes.<br/>
> ><br/>
> > cheers,<br/>
> > Steve<br/>
> ><br/>
> ><br/>
> > On Fri, Apr 5, 2019 at 1:39 PM "Steffen Jäger" <st...@gm...> wrote:<br/>
> >><br/>
> >> Hi everyone,<br/>
> >><br/>
> >> first of all thank you for your very useful OSC library!<br/>
> >> Currently using Liblo 0.28.<br/>
> >> I encountered some (for me) unintended behavior in the pattern_match algorithm from (pattern_match.c) regarding curly braces (which seems to be unchanged in the relevant parts up to version 0.30).<br/>
> >> For example if I send an OSC command like<br/>
> >> /test/mute/{1,2,10,11,12} i 1<br/>
> >> with callback handlers up and ready for paths<br/>
> >> /test/mute/1<br/>
> >> /test/mute/2<br/>
> >> /test/mute/10<br/>
> >> /test/mute/11<br/>
> >> /test/mute/12<br/>
> >> I would expect all of them to be invoked.<br/>
> >> Instead only /test/mute/1, /test/mute/2, /test/mute/11, /test/mute/12 are called.<br/>
> >> The /test/mute/10 is skipped.<br/>
> >> This seems to be due to the fact that for /test/mute/10 in line 227 the statement if (c == *str) is successfully comparing c with value of '1' to '1' from "10" from str and then from here onwards something is going wrong with variable c which becomes ',' in line 241 and from here on is staying on ',' till the pattern match returns false.<br/>
> >> Same behavior seems to happen with e.g.<br/>
> >> /test/mute/{2,20}<br/>
> >> Is there something wrong with my understanding in the usage of the curly braces in OSC or is this some bug?<br/>
> >> Your help is highly appreciated.<br/>
> >><br/>
> >> Thanks in advance!<br/>
> >><br/>
> >> Best regards,<br/>
> >> Steffen<br/>
> >> _______________________________________________<br/>
> >> liblo-devel mailing list<br/>
> >> lib...@li...<br/>
> >> <a href="https://lists.sourceforge.net/lists/listinfo/liblo-devel" target="_blank"> |
|
From: Stephen S. <rad...@gm...> - 2019-04-12 15:29:57
|
Hi,
I believe this is now fixed (and unit tested!) on master, along with a
couple of other fixes to the pattern matcher. Thanks very much for
pointing out this problem. Can you let me know if it seems fixed to
you?
regards,
Steve
On Wed, Apr 10, 2019 at 12:36 AM Stephen Sinclair <rad...@gm...> wrote:
>
> Just an update, I think I have a fix for this, but just working on
> integrating it into the test suite and spending some time checking it
> against the spec.
>
> regards,
> Steve
>
> On Fri, Apr 5, 2019 at 1:47 PM Stephen Sinclair <rad...@gm...> wrote:
> >
> > Hi Steffen,
> >
> > Thanks for the bug report!
> >
> > I'll try to reproduce as soon as I get a few minutes.
> >
> > cheers,
> > Steve
> >
> >
> > On Fri, Apr 5, 2019 at 1:39 PM "Steffen Jäger" <st...@gm...> wrote:
> >>
> >> Hi everyone,
> >>
> >> first of all thank you for your very useful OSC library!
> >> Currently using Liblo 0.28.
> >> I encountered some (for me) unintended behavior in the pattern_match algorithm from (pattern_match.c) regarding curly braces (which seems to be unchanged in the relevant parts up to version 0.30).
> >> For example if I send an OSC command like
> >> /test/mute/{1,2,10,11,12} i 1
> >> with callback handlers up and ready for paths
> >> /test/mute/1
> >> /test/mute/2
> >> /test/mute/10
> >> /test/mute/11
> >> /test/mute/12
> >> I would expect all of them to be invoked.
> >> Instead only /test/mute/1, /test/mute/2, /test/mute/11, /test/mute/12 are called.
> >> The /test/mute/10 is skipped.
> >> This seems to be due to the fact that for /test/mute/10 in line 227 the statement if (c == *str) is successfully comparing c with value of '1' to '1' from "10" from str and then from here onwards something is going wrong with variable c which becomes ',' in line 241 and from here on is staying on ',' till the pattern match returns false.
> >> Same behavior seems to happen with e.g.
> >> /test/mute/{2,20}
> >> Is there something wrong with my understanding in the usage of the curly braces in OSC or is this some bug?
> >> Your help is highly appreciated.
> >>
> >> Thanks in advance!
> >>
> >> Best regards,
> >> Steffen
> >> _______________________________________________
> >> liblo-devel mailing list
> >> lib...@li...
> >> https://lists.sourceforge.net/lists/listinfo/liblo-devel
|
|
From: Stephen S. <rad...@gm...> - 2019-04-09 22:36:58
|
Just an update, I think I have a fix for this, but just working on
integrating it into the test suite and spending some time checking it
against the spec.
regards,
Steve
On Fri, Apr 5, 2019 at 1:47 PM Stephen Sinclair <rad...@gm...> wrote:
>
> Hi Steffen,
>
> Thanks for the bug report!
>
> I'll try to reproduce as soon as I get a few minutes.
>
> cheers,
> Steve
>
>
> On Fri, Apr 5, 2019 at 1:39 PM "Steffen Jäger" <st...@gm...> wrote:
>>
>> Hi everyone,
>>
>> first of all thank you for your very useful OSC library!
>> Currently using Liblo 0.28.
>> I encountered some (for me) unintended behavior in the pattern_match algorithm from (pattern_match.c) regarding curly braces (which seems to be unchanged in the relevant parts up to version 0.30).
>> For example if I send an OSC command like
>> /test/mute/{1,2,10,11,12} i 1
>> with callback handlers up and ready for paths
>> /test/mute/1
>> /test/mute/2
>> /test/mute/10
>> /test/mute/11
>> /test/mute/12
>> I would expect all of them to be invoked.
>> Instead only /test/mute/1, /test/mute/2, /test/mute/11, /test/mute/12 are called.
>> The /test/mute/10 is skipped.
>> This seems to be due to the fact that for /test/mute/10 in line 227 the statement if (c == *str) is successfully comparing c with value of '1' to '1' from "10" from str and then from here onwards something is going wrong with variable c which becomes ',' in line 241 and from here on is staying on ',' till the pattern match returns false.
>> Same behavior seems to happen with e.g.
>> /test/mute/{2,20}
>> Is there something wrong with my understanding in the usage of the curly braces in OSC or is this some bug?
>> Your help is highly appreciated.
>>
>> Thanks in advance!
>>
>> Best regards,
>> Steffen
>> _______________________________________________
>> liblo-devel mailing list
>> lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/liblo-devel
|
|
From: Stephen S. <rad...@gm...> - 2019-04-05 11:47:57
|
Hi Steffen,
Thanks for the bug report!
I'll try to reproduce as soon as I get a few minutes.
cheers,
Steve
On Fri, Apr 5, 2019 at 1:39 PM "Steffen Jäger" <st...@gm...> wrote:
> Hi everyone,
>
> first of all thank you for your very useful OSC library!
> Currently using Liblo 0.28.
> I encountered some (for me) unintended behavior in the pattern_match
> algorithm from (pattern_match.c) regarding curly braces (which seems to be
> unchanged in the relevant parts up to version 0.30).
> For example if I send an OSC command like
> /test/mute/{1,2,10,11,12} i 1
> with callback handlers up and ready for paths
> /test/mute/1
> /test/mute/2
> /test/mute/10
> /test/mute/11
> /test/mute/12
> I would expect all of them to be invoked.
> Instead only /test/mute/1, /test/mute/2, /test/mute/11, /test/mute/12 are
> called.
> The /test/mute/10 is skipped.
> This seems to be due to the fact that for /test/mute/10 in line 227 the
> statement if (c == *str) is successfully comparing c with value of '1' to
> '1' from "10" from str and then from here onwards something is going wrong
> with variable c which becomes ',' in line 241 and from here on is staying
> on ',' till the pattern match returns false.
> Same behavior seems to happen with e.g.
> /test/mute/{2,20}
> Is there something wrong with my understanding in the usage of the curly
> braces in OSC or is this some bug?
> Your help is highly appreciated.
>
> Thanks in advance!
>
> Best regards,
> Steffen
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>
|
|
From: Steffen J. <st...@gm...> - 2019-04-05 11:39:53
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>Hi everyone,</div>
<div> </div>
<div>first of all thank you for your very useful OSC library!<br/>
Currently using Liblo 0.28.</div>
<div>I encountered some (for me) unintended behavior in the pattern_match algorithm from (pattern_match.c) regarding curly braces (which seems to be unchanged in the relevant parts up to version 0.30).<br/>
For example if I send an OSC command like</div>
<div>/test/mute/{1,2,10,11,12} i 1</div>
<div>with callback handlers up and ready for paths <br/>
/test/mute/1<br/>
/test/mute/2<br/>
/test/mute/10<br/>
/test/mute/11<br/>
/test/mute/12</div>
<div>I would expect all of them to be invoked.<br/>
Instead only /test/mute/1, /test/mute/2, /test/mute/11, /test/mute/12 are called.<br/>
The /test/mute/10 is skipped.</div>
<div>This seems to be due to the fact that for /test/mute/10 in line 227 the statement if (c == *str) is successfully comparing c with value of '1' to '1' from "10" from str and then from here onwards something is going wrong with variable c which becomes ',' in line 241 and from here on is staying on ',' till the pattern match returns false.</div>
<div>Same behavior seems to happen with e.g.<br/>
/test/mute/{2,20}</div>
<div>Is there something wrong with my understanding in the usage of the curly braces in OSC or is this some bug?<br/>
Your help is highly appreciated.</div>
<div><br/>
Thanks in advance!</div>
<div> </div>
<div>Best regards,<br/>
Steffen</div>
</div></div></body></html>
|