Re: Version 5.1.0 is released

For help and support with Universal Media Server
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Post Reply
michaelt
Posts: 155
Joined: Tue Feb 03, 2015 11:18 am
Location: lost in the depths of my mind

Re: Version 5.1.0 is released

Post by michaelt »

Initial testing confirms repeat problem with filesystem access, usually on first launch or after renderer off overnight with UMS running:
  • title "M*A*S*H (MASH\ 1970\ Blu-ray).mkv" not parsed
    "Not Supported File Format" reported for all titles
This is the same as the 5.0.1 release.
Attachments
ums_dbg_510J6_NotSupportedFile-2.zip
(25.37 KiB) Downloaded 453 times
ums_dbg_510J6_NotSupportedFile-1.zip
(11.84 KiB) Downloaded 475 times
MacPro5,1 - 2.8 GHz, 32 GB, 20TB, OS X 10.11.6,
. . . . and a few others.
Samsung UN55C8000
Home Theater (WIP): OS X based now, dedicated Linux later.
ExSport
Posts: 595
Joined: Wed Oct 10, 2012 1:57 am

Re: Version 5.1.0 is released

Post by ExSport »

"\" 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)
Rename file and test again. If it will fix your problem, definitely it is connected with it so easier to debug it in UMS.
michaelt
Posts: 155
Joined: Tue Feb 03, 2015 11:18 am
Location: lost in the depths of my mind

Re: Version 5.1.0 is released

Post by michaelt »

michaelt wrote:
ExSport wrote:"\" 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.

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??
Attachments
ums_dbg_510J6_NotSupportedFile-3.zip
(13.08 KiB) Downloaded 482 times
ums_dbg_OK.zip
(10.26 KiB) Downloaded 480 times
MacPro5,1 - 2.8 GHz, 32 GB, 20TB, OS X 10.11.6,
. . . . and a few others.
Samsung UN55C8000
Home Theater (WIP): OS X based now, dedicated Linux later.
michaelt
Posts: 155
Joined: Tue Feb 03, 2015 11:18 am
Location: lost in the depths of my mind

Re: Version 5.1.0: Mac OSX filename characters

Post by michaelt »

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 '&'.
The full name is passed and shows up in the log but the display truncates everything after the '&'. This may be a Samsung problem.

Log shows filename "Chaos;; Head; The Complete Series (DVD & Blu-ray Combo: Limited Edition)"
Screen shows "Chaos;; Head; The Complete Series (DVD &"

Also in the log there are two other names which failed to parse but a "Restart Server" fixed it.
  • "10-Movie America's Favorite Country Stars; Is There Life Out There? : Baron And The Kid : Crazy : ….mkv"
    "10-Movie Collection Featuring Brad Pitt; Too Young To Die? (1990) : The White Raven : Booster : Street Corner Justice : ....mkv"
Attachments
ums_dbg-5_TitleName_Truncated.zip
(51.77 KiB) Downloaded 478 times
MacPro5,1 - 2.8 GHz, 32 GB, 20TB, OS X 10.11.6,
. . . . and a few others.
Samsung UN55C8000
Home Theater (WIP): OS X based now, dedicated Linux later.
Post Reply