jvalkon

Ok i found some time. It is unrelated to stderr usage. It looks as though the remote @I statusmessage has 2 new entries which the client's parser did not (yet) expect: @I { and @I } In older versions of mpg123 these were not present (i tried, see below). I relaxed the parser function in the clientcode and now it works again. I leave it up to you to decide to call this a 'regression' :) For my part this issue can be closed. v1.29 06-10-2021, 17:47:48 ===== rr player started ===== 06-10-2021, 17:47:48...

Ok i found some time. It is unrelated to stderr usage. It looks as though the remote @I statusmessage has 2 new entries which the client's parser did not (yet) expect: @I { and @I } In older versions of mpg123 these were not present (i tried, see below). I relaxed the parser function in the clientcode and now it works again. I leave it up to you to decide to call this a 'regression' :) For my part this issue can be closed. v1.29 06-10-2021, 17:47:48 ===== rr player started ===== 06-10-2021, 17:47:48...

Yes i can and i will, but not immediately, maybe next weekend

Ok, user error, i missed out on the --remote-err option. There's still something different than before (i.e. playing doesn't start) but i think i can handle that on the front-end part. Maybe some change in the sequence of msgs, i'll check the logging. Issue can be closed, thanks for your reply

-R / --remote option regression

Caret pos after rectagular select, regression