Threaded Mode | Linear Mode

simoncn · (This post was last modified: 03-01-2013 14:49 by simoncn.)

(03-01-2013 09:52)Mike48 Wrote: Simon, thanks for the reply.

I'll be glad to report it to PS once I understand the situation. Are you saying that the Minim log include strings (i.e., including character translations) originated by the renderer? If so, does it also include strings from the control point?

The UPnP protocol works as follows:
1) MinimServer sends URLs to the control point in response to browse requests from the control point.
2) The control point sends one or more of these URLs to the renderer when the user selects Play.
3) The renderer sends one of these URLs back to the server each time it starts streaming and playing a track.

The MinimServer log you sent me is showing 3) with incorrect URLs. By opening the log window using MinimWatch and setting the logging level to Trace, you can also see 1) showing correct URLs. This proves that MinimServer is functioning correctly. The part you can't see in the MinimServer log is 2), but having used UPnPlay myself without a problem, I am confident that it is sending correct URLs to the renderer.

Quote:I really like the idea of sanitizing the URLs. I'd have to infer that J.River is doing that, too, because everything works OK here with J.River as the server.

I wouldn't describe this as "sanitizing". The original URLs sent in step 1) are legal and correct, and they would work properly if it weren't for elementary bugs in other software. Perhaps "dumbing down" is a more appropriate term.

Alekz · 03-01-2013, 15:04

(03-01-2013 09:40)simoncn Wrote: Can you post a link to this forum discussion?

http://www.psaudio.com/vanilla/discussio...an-psa-emm

Mike48 · 03-01-2013, 22:00

(03-01-2013 14:49)simoncn Wrote: I wouldn't describe this as "sanitizing". The original URLs sent in step 1) are legal and correct, and they would work properly if it weren't for elementary bugs in other software. Perhaps "dumbing down" is a more appropriate term.

No debate there. I will be filing a formal bug report with PS Audio today. It is unfortunate, in a way, that most other servers do something to avoid such problems, as it will make it harder for the fix to seem urgent.

Most for-profit companies are far less determined to ferret out bugs than those who develop software out of pure enthusiasm.

Alekz · 03-01-2013, 23:10

Most likely this is how Rygel works and since the major UPnP server support this method it will not be considered a bug.

simoncn · 04-01-2013, 10:34

(03-01-2013 22:00)Mike48 Wrote:
(03-01-2013 14:49)simoncn Wrote: I wouldn't describe this as "sanitizing". The original URLs sent in step 1) are legal and correct, and they would work properly if it weren't for elementary bugs in other software. Perhaps "dumbing down" is a more appropriate term.

No debate there. I will be filing a formal bug report with PS Audio today. It is unfortunate, in a way, that most other servers do something to avoid such problems, as it will make it harder for the fix to seem urgent.

Most for-profit companies are far less determined to ferret out bugs than those who develop software out of pure enthusiasm.

Thanks very much. As you say, it's not likely to be considered an urgent issue, and when MinimServer provides a workaround, the priority will probably drop even further. I'll be interested to hear how PS Audio responds.

There's also the similar bug with percent encoded Chinese characters described in this post. It's probably best to focus on the apostrophe problem first.

bubbleguuum · (This post was last modified: 04-01-2013 12:48 by bubbleguuum.)

Using encoded characters in URLs is a recipe for failure with some Control Point and renderers that utterly fail at URL decoding / encoding. And I do not even speak of XML encoding / decoding along the way in which these URL are embedded possibly adding more fail...

Mike48 · 28-01-2013, 08:03

This is just to say, I did file a formal bug report with PS Audio regarding this problem. Thanks to help from Simon and the output from the MinimServer log file, PS acknowledged the problem and logged it as a bug. I would not be surprised to see this fixed in a future firmware release, but there's no saying how long that will take. If a workaround came in Minim Server in the meantime, it would be welcome by PS Audio owners.

(Until there is a fix or work-around, I've returned to using J.River as DLNA server, to my disappointment.)

simoncn · 28-01-2013, 08:39

(28-01-2013 08:03)Mike48 Wrote: This is just to say, I did file a formal bug report with PS Audio regarding this problem. Thanks to help from Simon and the output from the MinimServer log file, PS acknowledged the problem and logged it as a bug. I would not be surprised to see this fixed in a future firmware release, but there's no saying how long that will take. If a workaround came in Minim Server in the meantime, it would be welcome by PS Audio owners.

(Until there is a fix or work-around, I've returned to using J.River as DLNA server, to my disappointment.)

Thanks for doing this. I'm hoping to be able to provide a workaround in the not too distant future.

magister · 28-01-2013, 12:43

Let me offer a different perspective. Simon, if providing a workaround for the apostrophe issue will take up time needed for other things or be likely to introduce additional problems, I suggest you not do it--especially since the problem does not seem to lie with MinimServer to begin with. (BTW, I own a PS Audio DAC.) If a file with an apostrophe in its name won't play, it's simple to rename the file; are there so many files out there with apostrophes? Maybe there are . . . but it's a bad idea.

When I get new music I always have to clean up the tags anyway, so I get rid of everything in the filenames except A-Z, a-z, 0-9 and spaces. I think this is still the safe route even though nowadays we can theoretically use other characters except: / and \. And of course in the title (i.e., the metadata field) one can have Frédéric Chopin, Tannhäuser, or "It Ain't Me, Babe" with no problems.

David

Alekz · 29-01-2013, 04:21

(28-01-2013 12:43)magister Wrote: Maybe there are . . .

Yes, there are. And renaming the files is a bad idea. This bug/issue must be fixed by PSA, but I really doubt that it will be done. See my posts in the PSA forum. GUPnP and Rygel are two year old and must be upgraded, but it can't be done without recompiling and upgrading other libraries and most likely the kernel. That's way too much work with no guaranteed result. I did suggest that in several threads, but got no response from PSA.

So, the only reliable and (I hope) quickest way is to tweak the Minim code.