Page 1 of 1

[Solved] 5.1.2 J8 Accepts then Rejects Renderer, Files

Posted: Tue Apr 21, 2015 9:02 am
by michaelt
--- This is a dup with the log file attached ---
Edited: reran and captured bad and good logs (times don't match the code inserts).

More testing and looking at the log file turned this up - after successfully ID'ing the renderer - it marks it unrecognized:

Code: Select all

TRACE 16:03:25.830 [cling-11] Matched media renderer "Samsung C/D Series" based on address /10.0.1.89
DEBUG 16:03:25.832 [cling-11] Reading UpnpDetailsSearch: "Samsung , [CD]S?\d{3}\d? , AllShare" (default: "")
DEBUG 16:03:25.832 [cling-11] Reading MediaInfo: true (default: false)
DEBUG 16:03:25.832 [cling-11] Marking upnp renderer "TV-55C8000" at /10.0.1.89 as unrecognized
DEBUG 16:03:25.833 [cling-11] Purging renderer Samsung C/D Series as invalid
After packing the debug file, I selected "Restart Server" and all the error messages went away and the file played:

Code: Select all

04-20 16:04:31  Media renderer was not recognized. Possible identifying HTTP headers:User-Agent: DLNADOC/1.50
04-20 16:05:12  Started playing Absolute Power.mkv on your TV-55C8000
04-20 16:05:16  Media renderer was not recognized. Possible identifying HTTP headers:User-Agent: DLNADOC/1.50
04-20 16:05:18  Media renderer was not recognized. Possible identifying HTTP headers:User-Agent: DLNADOC/1.50
04-20 16:05:18  Media renderer was not recognized. Possible identifying HTTP headers:User-Agent: DLNADOC/1.50
04-20 16:05:18  Media renderer was not recognized. Possible identifying HTTP headers:User-Agent: DLNADOC/1.50
04-20 16:05:18  Media renderer was not recognized. Possible identifying HTTP headers:User-Agent: DLNADOC/1.50
04-20 16:05:19  Media renderer was not recognized. Possible identifying HTTP headers:User-Agent: DLNADOC/1.50
04-20 16:05:19  Checking shared folder: /Users/umsmkv/aML/Video/Index
04-20 16:05:19  Media renderer was not recognized. Possible identifying HTTP headers:User-Agent: DLNADOC/1.50
04-20 16:05:19  Media renderer was not recognized. Possible identifying HTTP headers:User-Agent: DLNADOC/1.50
04-20 16:05:19  Checking shared folder: /Users/umsmkv/aML/Video/Index
04-20 16:46:06  Sending BYEBYE...
04-20 16:46:06  Stopping server on host 10.0.1.50 and port 5001...
04-20 16:46:07  Using address /10.0.1.50 found on network interface: name:en0 (en0)
04-20 16:46:07  Created socket: /10.0.1.50:5001
04-20 16:49:56  Checking shared folder: /Users/umsmkv/aML/Video/Index
04-20 16:50:10  The file /Users/umsmkv/aML/Video/Index/Blu-ray/M*A*S*H (MASH| 1970).mkv could not be parsed. It will be hidden
04-20 16:50:20  Started playing Absolute Power.mkv on your TV-55C8000

Re: 5.1.2 J8 Accepts then Rejects Renderer, Files

Posted: Tue Apr 21, 2015 10:26 am
by infidel
michaelt wrote: after successfully ID'ing the renderer - it marks it unrecognized
In renderers/Samsung-CD.conf try changing

Code: Select all

UpnpDetailsSearch = Samsung , [CD]S?\d{3}\d? , AllShare
to

Code: Select all

UpnpDetailsSearch = [CD]S?\d{3}\d? , (Samsung|AllShare)
Your 55C8000's upnp device details are formatted in a way that's new to UMS (probably due to Samsung firmware changes) and causing UMS to doubt its initial recognition.

Re: 5.1.2 J8 Accepts then Rejects Renderer, Files

Posted: Wed Apr 22, 2015 12:45 am
by michaelt
infidel wrote:Your 55C8000's upnp device details are formatted in a way that's new to UMS (probably due to Samsung firmware changes) and causing UMS to doubt its initial recognition.
I'll give it a try although this set has never had a firmware update since I bought it.
Yup - seems to be good now.
Thanx

Re: [Solved] 5.1.2 J8 Accepts then Rejects Renderer, Files

Posted: Wed Apr 22, 2015 1:20 am
by infidel
michaelt wrote:although this set has never had a firmware update since I bought it.
I should have said its upnp details aren't consistent with other Samsung c/d tvs we've seen before and left it at that :). There's no real standard for how devices present their identifying info, so recognition is a big headache.

Re: [Solved] 5.1.2 J8 Accepts then Rejects Renderer, Files

Posted: Wed Apr 22, 2015 2:02 am
by michaelt
infidel wrote:I should have said its upnp details aren't consistent with other Samsung c/d tvs we've seen before and left it at that :). There's no real standard for how devices present their identifying info, so recognition is a big headache.
Now that sounds more like the real world - trial & guess.

Edit:
Real reason was the in the .conf file: changed "UpnpDetailsSearch" to:

Code: Select all

[CD]S?\d{3}\d? , (Samsung|AllShare)
and it worked.