Version 5.1.0 is released

[Paradox]

Ooooo
"Fixed filename bug on Sony Bravia TVs"
Subjunk what magic have you done here would love to know a bit more about this. Please tell me its related to the weird DLNA PN bravias use for some files.

[michaelt]

"\" is not acceptable char on Windows so I suppose it is hidden as UMS code can't handle with it (also in case you are on Linux)

I'll try changing it to a semicolon ';' and see if no one notices.

I changes the '\' to ';', logged out, logged back in, launched UMS.
Same issues:

• title "M*A*S*H (MASH; 1970; Blu-ray).mkv" not parsed
  "Not Supported File Format" reported for all titles

Quit UMS, relaunched UMS - works fine!

Next: changed '*' to '-' and repeated test.
It seems to work ok on the first try. I'll try more later.

I'll post the logs in Support:

• ums_dbg_510J6_NotSupportedFile-3
  ums_dbg_OK

Edit: "M-A-S-H (MASH; 1970; Blu-ray)" works ofter logout-login and long idle times between launches. Someone, somewhere has a problem with the asterisk '*' in pathnames! If it pops up again later, I'll start bug post.
From the prolific use of '*' it might be worthwhile to root cause this.

However, why is the '*' behavior not consistent??

[ExSport]

In Windows world "*" is also forbidden but definitely weird that behavior is so erratic and not consistent.

[michaelt]

In unix land '*' can be used but needs to be "escaped" ('\*') in shell scripts. It is a valid character as are almost all special characters.

It is the random nature of this which bothers me and that it affects the file recognition.

[Paradox]

Windows filenames can not use...

\ / : * ? " <> | any of them will give issues in filenames and foldernames with many applications. I suspect there are similar characters on OSX which perform (or rather do not) in a similar fashion.

[andreos11]

Here I found Java 8 version ?

[Paradox]

Here I found Java 8 version ?

There are versions available for all java variants...
http://sourceforge.net/projects/unimedi ... 0Releases/

[Paradox]

Bad form to double post i know but a couple of minor little things for the devs.............

1. The Bravia slow browsing of files issue i reported for versions 5.0.0 and 5.0.1 are gone This 5.10 version everything is back to its snappy self, nice work.

and more of a little forgetfulness than anything.......

2. Default.conf renderer does not have any mention of the "ThumbnailSize = " option, it was also forgotten in the prior 5.xx versions

Other than that nothing really to report everything thus far for me seems to be functioning fine. Still itching to find out more about "Fixed filename bug on Sony Bravia TVs" though.

[Matt]

Still itching to find out more about "Fixed filename bug on Sony Bravia TVs" though.

Probably this discussion viewtopic.php?f=9&t=2963

And these closed issues from GitHub
Android https://github.com/UniversalMediaServer ... issues/490
Bravia https://github.com/UniversalMediaServer ... issues/499

[michaelt]

Windows filenames can not use...

\ / : * ? " <> | any of them will give issues in filenames and foldernames with many applications. I suspect there are similar characters on OSX which perform (or rather do not) in a similar fashion.

Because I derive my Titles from the UPC's, I have no control over the characters used.

I did a complete scan of all printable characters in file names and found only one "problem": '/' and ':'.
OSX allows a slash in pathnames but actually stores them internally as colon ':'. There is no way to get around it, slash is the only printable character not allowed in unix land, hence the colon fudge.

UMS bottom line: all printable characters handed to UMS behaved properly except for one: ampersand '&'. I'll post a support/bug report elsewhere.

I do have one Windows XP machine and will try later the same character scan there as well for general information.