Topic: What is "Tuner Stream" hdhrp for? (Read 9037 times)

tzr916 · « **on:** February 10, 2020, 09:44:18 am »

https://yabb.jriver.com/interact/index.php/topic,124149.0.html

26.0.21 (2/6/2020)
1. NEW: A new television channel type - "Tuner Stream", for playing streaming video from HDHomeRun Prime tuners. Right now only live streaming is supported. No time-shifting, no recording. EPG is supported.
2. Fixed: HD Channel streaming from HDHomeRun Prime tuners could not be played via File > Open URL...

I thought SiliconDust abandoned/discontinued their streaming channel service? What is this MC feature for exactly? Examples?

Yaobing · « **Reply #1 on:** February 10, 2020, 09:47:27 am »

It is probably a different thing. The streaming is from the tuner device and is only on your own network. So it is not useful for Windows users who can get the channels directly through the MC TV engine.

tzr916 · « **Reply #2 on:** February 10, 2020, 10:27:18 am »

I guess I still don't understand. Can you explain how to use it? Example of what it does?

jachin99 · « **Reply #3 on:** February 10, 2020, 02:17:59 pm »

I'm guessing it uses the http interface instead of the bda architecture?

Yaobing · « **Reply #4 on:** February 10, 2020, 04:39:30 pm »

Quote from: jachin99 on February 10, 2020, 02:17:59 pm

I'm guessing it uses the http interface instead of the bda architecture?

For HDHomeRun Prime, we do not use bda anyway. It is HTTP vs. RTSP.

Quote from: tzr916 on February 10, 2020, 10:27:18 am

I guess I still don't understand. Can you explain how to use it? Example of what it does?

If the device has already worked fine for you, you have no reason to use it.

Here is how you use it:

Type the ip address of your HDHRP in a browser address window. Click Channel Lineup. Your channels are displayed, with channel numbers shown as live links. Right-click a channel link, and choose "Copy link". You get something like this:

http://192.168.###.###:5004/auto/v159

This is the streaming URL of channel 159. Two ways to use this stream:

1. You can stream this channel in MC by using File > Open URL...

2. You can set up channels like this in MC as "Tuner Stream" channels.

Run TV Setup. Choose "Streaming from a network tuner" on Service Type page. On the next page type "http://192.168.###.###:5004/auto/" in the Base URL box. Enter a range of channel numbers, like 2 - 200. MC will append "v2", "v3", ... , "v200" at the end of base URL to form URLs of each channel. You can enter disjoint sets of channel ranges. For example, you type 2, and 200, and click "Add Range", then you enter 250, and 350 and click "Add Range". Now you have two ranges: 2-200, and 250-350.

Click Next to finish the rest of Setup as usual. With these channels setup, you can play them the same way as other types of channels. Currently they are played only as streams (i.e. no time-shifting, no recording).

Aardvark · « **Reply #5 on:** May 06, 2020, 10:06:52 pm »

Hi Yaobing,

I was quite interested to see this announcement and also to see the followup item for V26.0.73

23. NEW: The "Tuner Stream" type of TV channels can now be manually added or edited.

I run a Beyonwiz PVR which is Linux based running Enigma2 and supports Network Streaming so I was hoping to be able to use this. Variants of this software on different boxes seem to be used in Europe quite a bit

It runs a Plugin called HRTunerProxy which broadcasts on port 6082. I can get access to Live Tv via this plugin in both Emby Server and Plex and also thru Kodi using a plugin called Enigma2 Client

I can feed the following Streaming URL into JRiver and it plays but can't see how I would setup all the channels in Streaming from a Network Tuner

http://beyonwizt4:8001/1:0:19:624:602:1014:EEEE0000:0:0:0:?bitrate=400000?width=854?height=480?aspectratio=2?interlaced=0

Presumably the first thing would be for JRiver to actually recognise the device.

Any ideas as to whether this might be possible for JRiver?

Regards, Mike

Yaobing · « **Reply #6 on:** May 07, 2020, 10:06:01 am »

Maybe we can work out something.

Your example URL is more complicated than what I have implemented for so far. What we have now identifies channels by a single channel number, so we can use a "base URL" and a channel number to construct a channel URL. Also I am not sure how we can detect the kind of device your have. Does your device show up under Playing Now list of servers in MC? If you turn on logging, restart MC, and check log file after a few minutes, do you find entries in the log file like the following (you have to turn on TV feature first)?

Code: [Select]

0011796: 22624: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x1eb284af590
0011796: 22624: TV: CTVManager::AddDLNATVDevice: Start
0011796: 22624: TV: CTVManager::AddDLNATVDevice: Venus (Generic DLNA) not TV device
0011796: 22624: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)

Aardvark · « **Reply #7 on:** May 07, 2020, 06:06:48 pm »

Hi Yaobing,
My device doesn't show up under Playing Now. I also ran Logging with TV Feature turned on but there were no entries of Type 22624 in the Log.

Any ideas as to what else I can try to get you some more information.

Regards, Mike

Yaobing · « **Reply #8 on:** May 07, 2020, 07:37:52 pm »

22624 was not a type. It was a thread ID, and thus was quite random. What you need to look for in a log file is " TV: CTVManager::AddDLNATVDevice: Start". Wait a minute after you start MC to allow MC to go through the process of DLNA device discovery before you check the log file.

JimH · « **Reply #9 on:** May 07, 2020, 09:33:17 pm »

Is Media Network turned on in MC settings?

Aardvark · « **Reply #10 on:** May 08, 2020, 12:29:30 am »

Hi Yaobing,
Sorry about giving you wrong info in my last reply. Will try and give as much info that I have uncovere

1. Media Network is up and running. Don't know if there would be any further items within that I might need to activate

2. Ran Logging again and the following shows up, basically everything except the BWIZ

0398953: 8524: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Start
0398953: 8524: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Device Control enabled
0398953: 8524: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x2a91d6210a0
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Start
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Michael-PC (Soundtouch DLNA) not TV device
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0398953: 8524: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x2a91d6210a0
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Start
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Michael-PC (JRiver Default DLNA) not TV device
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0398953: 8524: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x2a91d6210a0
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Start
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Michael-PC (Library Server) not TV device
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0398953: 8524: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x2a91d6210a0
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Start
0398953: 8524: TV: CTVManager::AddDLNATVDevice: NAS1676D8 not TV device
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0398953: 8524: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x2a91d6210a0
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Start
0398953: 8524: TV: CTVManager::AddDLNATVDevice: SoundTouch Wireless Link Adapter not TV device
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0398953: 8524: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x2a91d6210a0
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Start
0398953: 8524: TV: CTVManager::AddDLNATVDevice: DMR-BWT955 not TV device
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0398953: 8524: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Finish (0 ms)

3. The Beyonwiz doesn't show up in Playing Now. However the BWIZ does have a MiniDLNA Server which when active shows up in Playing Now and allows me to replay the TV programs recorded on the BWIZ

4.Running Device Spy from "Developer tools for UPnP Technology" tells me that the Base URl for BWIZ is http://192.168.1.16:6082/
urn:schemas-upnp-org:device:MediaServer:1
Remote Endpoint is 192.168.1.16:6082
Unique Device Name is 1a66cb56-fad8-4cdc-8d73-ad5b8eaa5a2a

Thanks for your help

Regards. Mike

Aardvark · « **Reply #11 on:** May 08, 2020, 08:56:25 am »

Hi Yaobing,
Discovered a bit more after digging about in logs.

http://192.168.1.16:6082/discover.json contains the following

{"DeviceAuth": "NN2iD8AYUDuUCFBnQ8tOAbpt", "DeviceUUID": "1a66cb56-fad8-4cdc-8d73-ad5b8eaa5a2a", "BaseURL": "http://192.168.1.16:6082", "FriendlyName": "Beyonwiz T4", "ModelNumber": "beyonwizt4", "DeviceID": "KCB3A8O9", "TunerCount": 4, "LineupURL": "http://192.168.1.16:6082/lineup.json", "FirmwareName": "beyonwiz", "FirmwareVersion": "20180416", "Manufacturer": "Silicondust"}

And http://192.168.1.16:6082/lineup.json contains the Channel list

[{"GuideNumber": "1", "GuideName": "10 BOLD", "URL": "http://192.168.1.16:8001/1:0:1:621:602:1014:EEEE0000:0:0:0:"}, {"GuideNumber": "2", "GuideName": "ABC", "URL": "http://192.168.1.16:8001/1:0:1:221:221:1010:EEEE0000:0:0:0:"}, {"GuideNumber": "3", "GuideName": "SBS ONE", "URL": "http://192.168.1.16:8001/1:0:1:301:300:3202:EEEE0000:0:0:0:"}, {"GuideNumber": "4", "GuideName": "7 Sydney", "URL": "http://192.168.1.16:8001/1:0:1:520:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "5", "GuideName": "Channel 9 Sydney", "URL": "http://192.168.1.16:8001/1:0:1:421:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "6", "GuideName": "10", "URL": "http://192.168.1.16:8001/1:0:1:625:602:1014:EEEE0000:0:0:0:"}, {"GuideNumber": "7", "GuideName": "10 Peach", "URL": "http://192.168.1.16:8001/1:0:1:628:602:1014:EEEE0000:0:0:0:"}, {"GuideNumber": "8", "GuideName": "10 BOLD", "URL": "http://192.168.1.16:8001/1:0:1:627:602:1014:EEEE0000:0:0:0:"}, {"GuideNumber": "9", "GuideName": "10 HD", "URL": "http://192.168.1.16:8001/1:0:19:624:602:1014:EEEE0000:0:0:0:"}, {"GuideNumber": "10", "GuideName": "ABC HD", "URL": "http://192.168.1.16:8001/1:0:19:225:221:1010:EEEE0000:0:0:0:"}, {"GuideNumber": "11", "GuideName": "ABC", "URL": "http://192.168.1.16:8001/1:0:1:223:221:1010:EEEE0000:0:0:0:"}, {"GuideNumber": "12", "GuideName": "ABC NEWS", "URL": "http://192.168.1.16:8001/1:0:1:220:221:1010:EEEE0000:0:0:0:"}, {"GuideNumber": "13", "GuideName": "SBS ONE HD", "URL": "http://192.168.1.16:8001/1:0:19:306:300:3202:EEEE0000:0:0:0:"}, {"GuideNumber": "14", "GuideName": "SBS VICELAND HD", "URL": "http://192.168.1.16:8001/1:0:19:303:300:3202:EEEE0000:0:0:0:"}, {"GuideNumber": "15", "GuideName": "7HD Sydney", "URL": "http://192.168.1.16:8001/1:0:19:524:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "16", "GuideName": "7 Sydney", "URL": "http://192.168.1.16:8001/1:0:1:521:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "17", "GuideName": "7TWO Sydney", "URL": "http://192.168.1.16:8001/1:0:1:522:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "18", "GuideName": "7mate Sydney", "URL": "http://192.168.1.16:8001/1:0:1:523:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "19", "GuideName": "7flix Sydney", "URL": "http://192.168.1.16:8001/1:0:1:525:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "20", "GuideName": "9HD Sydney", "URL": "http://192.168.1.16:8001/1:0:19:422:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "21", "GuideName": "Channel 9 Sydney", "URL": "http://192.168.1.16:8001/1:0:1:426:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "22", "GuideName": "9Gem Sydney", "URL": "http://192.168.1.16:8001/1:0:1:427:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "23", "GuideName": "9Go! Sydney", "URL": "http://192.168.1.16:8001/1:0:1:428:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "24", "GuideName": "9Life Sydney", "URL": "http://192.168.1.16:8001/1:0:1:424:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "25", "GuideName": "9Go! Sydney", "URL": "http://192.168.1.16:8001/1:0:1:423:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "26", "GuideName": "SBS World Movies", "URL": "http://192.168.1.16:8001/1:0:19:307:300:3202:EEEE0000:0:0:0:"}, {"GuideNumber": "27", "GuideName": "9GemHD Sydney", "URL": "http://192.168.1.16:8001/1:0:19:425:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "28", "GuideName": "SBS Food", "URL": "http://192.168.1.16:8001/1:0:1:304:300:3202:EEEE0000:0:0:0:"}, {"GuideNumber": "29", "GuideName": "7mateHD Sydney", "URL": "http://192.168.1.16:8001/1:0:19:527:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "30", "GuideName": "9Rush Sydney", "URL": "http://192.168.1.16:8001/1:0:1:429:420:1012:EEEE0000:0:0:0:"}]

Hope this helps.

Regards, Mike

Yaobing · « **Reply #12 on:** May 08, 2020, 09:00:59 am »

Thanks. I was hoping to see something that is similar to cable TV tuner in the US. Right now I am not seeing anything that looks like it. However, considering MC can play the channel URL that you manually feed it, it may be possible for me to add an alternative mode in manually adding/editing channels, so you can enter a full URL for a channel directly. That way, you can create your channel list manually even though MC will not automatically set them up. This can be tedious if you have a large number of channels.

Yaobing · « **Reply #13 on:** May 08, 2020, 09:12:17 am »

Quote from: Aardvark on May 08, 2020, 08:56:25 am

http://192.168.1.16:6082/discover.json contains the following

{"DeviceAuth": "NN2iD8AYUDuUCFBnQ8tOAbpt", "DeviceUUID": "1a66cb56-fad8-4cdc-8d73-ad5b8eaa5a2a", "BaseURL": "http://192.168.1.16:6082", "FriendlyName": "Beyonwiz T4", "ModelNumber": "beyonwizt4", "DeviceID": "KCB3A8O9", "TunerCount": 4, "LineupURL": "http://192.168.1.16:6082/lineup.json", "FirmwareName": "beyonwiz", "FirmwareVersion": "20180416", "Manufacturer": "Silicondust"}

I did not see this device in your previous post (MC's DLNA device discovery). Did you find this link in MC log?

Quote

And http://192.168.1.16:6082/lineup.json contains the Channel list

[{"GuideNumber": "1", "GuideName": "10 BOLD", "URL": "http://192.168.1.16:8001/1:0:1:621:602:1014:EEEE0000:0:0:0:"}, {"GuideNumber": "2", "GuideName": "ABC", "URL": "http://192.168.1.16:8001/1:0:1:221:221:1010:EEEE0000:0:0:0:"}, {"GuideNumber": "3", "GuideName": "SBS ONE", "URL": "http://192.168.1.16:8001/1:0:1:301:300:3202:EEEE0000:0:0:0:"}, {"GuideNumber": "4", "GuideName": "7 Sydney", "URL": "http://192.168.1.16:8001/1:0:1:520:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "5", "GuideName": "Channel 9 Sydney", "URL": "http://192.168.1.16:8001/1:0:1:421:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "6", "GuideName": "10", "URL": "http://192.168.1.16:8001/1:0:1:625:602:1014:EEEE0000:0:0:0:"}, {"GuideNumber": "7", "GuideName": "10 Peach", "URL": "http://192.168.1.16:8001/1:0:1:628:602:1014:EEEE0000:0:0:0:"}, {"GuideNumber": "8", "GuideName": "10 BOLD", "URL": "http://192.168.1.16:8001/1:0:1:627:602:1014:EEEE0000:0:0:0:"}, {"GuideNumber": "9", "GuideName": "10 HD", "URL": "http://192.168.1.16:8001/1:0:19:624:602:1014:EEEE0000:0:0:0:"}, {"GuideNumber": "10", "GuideName": "ABC HD", "URL": "http://192.168.1.16:8001/1:0:19:225:221:1010:EEEE0000:0:0:0:"}, {"GuideNumber": "11", "GuideName": "ABC", "URL": "http://192.168.1.16:8001/1:0:1:223:221:1010:EEEE0000:0:0:0:"}, {"GuideNumber": "12", "GuideName": "ABC NEWS", "URL": "http://192.168.1.16:8001/1:0:1:220:221:1010:EEEE0000:0:0:0:"}, {"GuideNumber": "13", "GuideName": "SBS ONE HD", "URL": "http://192.168.1.16:8001/1:0:19:306:300:3202:EEEE0000:0:0:0:"}, {"GuideNumber": "14", "GuideName": "SBS VICELAND HD", "URL": "http://192.168.1.16:8001/1:0:19:303:300:3202:EEEE0000:0:0:0:"}, {"GuideNumber": "15", "GuideName": "7HD Sydney", "URL": "http://192.168.1.16:8001/1:0:19:524:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "16", "GuideName": "7 Sydney", "URL": "http://192.168.1.16:8001/1:0:1:521:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "17", "GuideName": "7TWO Sydney", "URL": "http://192.168.1.16:8001/1:0:1:522:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "18", "GuideName": "7mate Sydney", "URL": "http://192.168.1.16:8001/1:0:1:523:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "19", "GuideName": "7flix Sydney", "URL": "http://192.168.1.16:8001/1:0:1:525:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "20", "GuideName": "9HD Sydney", "URL": "http://192.168.1.16:8001/1:0:19:422:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "21", "GuideName": "Channel 9 Sydney", "URL": "http://192.168.1.16:8001/1:0:1:426:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "22", "GuideName": "9Gem Sydney", "URL": "http://192.168.1.16:8001/1:0:1:427:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "23", "GuideName": "9Go! Sydney", "URL": "http://192.168.1.16:8001/1:0:1:428:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "24", "GuideName": "9Life Sydney", "URL": "http://192.168.1.16:8001/1:0:1:424:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "25", "GuideName": "9Go! Sydney", "URL": "http://192.168.1.16:8001/1:0:1:423:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "26", "GuideName": "SBS World Movies", "URL": "http://192.168.1.16:8001/1:0:19:307:300:3202:EEEE0000:0:0:0:"}, {"GuideNumber": "27", "GuideName": "9GemHD Sydney", "URL": "http://192.168.1.16:8001/1:0:19:425:420:1012:EEEE0000:0:0:0:"}, {"GuideNumber": "28", "GuideName": "SBS Food", "URL": "http://192.168.1.16:8001/1:0:1:304:300:3202:EEEE0000:0:0:0:"}, {"GuideNumber": "29", "GuideName": "7mateHD Sydney", "URL": "http://192.168.1.16:8001/1:0:19:527:502:1013:EEEE0000:0:0:0:"}, {"GuideNumber": "30", "GuideName": "9Rush Sydney", "URL": "http://192.168.1.16:8001/1:0:1:429:420:1012:EEEE0000:0:0:0:"}]

This may allow us to get channels. I will have to think about how to pull info like this into MC.

Aardvark · « **Reply #14 on:** May 08, 2020, 09:30:54 am »

Hi Yaobing,
I found this out from looking at an Emby log.

Regards, Mike

Aardvark · « **Reply #15 on:** May 18, 2020, 07:54:17 am »

Hi Yaobing,
Any idea as to whether you might be able to do something for Beyonwiz devices? It would make it an all in one solution with live play, recording and playback of recorded shows all through JRiver.

Regards, Mike

Yaobing · « **Reply #16 on:** May 18, 2020, 08:24:29 am »

We are working on DLNA devices that show up under Playing Now. Hopefully we can get channels by querying the device like yours.

Aardvark · « **Reply #17 on:** May 20, 2020, 03:53:27 pm »

Hi Yaobing,
That sounds good. Let me know if you need anything tested.

Regards, Mike

Aardvark · « **Reply #18 on:** September 15, 2020, 11:15:29 pm »

Hi Yaobing,
Any chance that this could be looked at in MC27?

Regards, Mike

Yaobing · « **Reply #19 on:** September 15, 2020, 11:42:37 pm »

The .../discover.json and .../lineup.json examples you gave are exactly like the HDHomeRun devices. So I would think this should work as long as MC recognizes the device. Do you know the Friendly Name, Model Name, of the DLNA device?

Aardvark · « **Reply #20 on:** September 16, 2020, 12:31:46 am »

Hi Yaobing
Details as follows

"FriendlyName": "Beyonwiz T4", "ModelNumber": "beyonwizt4",

Regards, Mike

Yaobing · « **Reply #21 on:** September 16, 2020, 07:43:29 am »

Quote from: Aardvark on September 16, 2020, 12:31:46 am

Hi Yaobing
Details as follows

"FriendlyName": "Beyonwiz T4", "ModelNumber": "beyonwizt4",

Regards, Mike

These show up in the /discover.json result. However, we do not find the device in MC's DLNA device discovery.

Could this one be it?

Code: [Select]

0398953: 8524: TV: CTVManager::AddDLNATVDevice: Start
0398953: 8524: TV: CTVManager::AddDLNATVDevice: DMR-BWT955 not TV device
0398953: 8524: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)

I will code in some more logging and see if we can identify the device.

Also, what is the name of this miniDLNA Server:

Quote

3. The Beyonwiz doesn't show up in Playing Now. However the BWIZ does have a MiniDLNA Server which when active shows up in Playing Now and allows me to replay the TV programs recorded on the BWIZ

BWIZ? For some reason I do not see this showing up in the log you posted.

Quote from: Aardvark on May 08, 2020, 12:29:30 am

4.Running Device Spy from "Developer tools for UPnP Technology" tells me that the Base URl for BWIZ is http://192.168.1.16:6082/
urn:schemas-upnp-org:device:MediaServer:1
Remote Endpoint is 192.168.1.16:6082
Unique Device Name is 1a66cb56-fad8-4cdc-8d73-ad5b8eaa5a2a

Maybe you can give me more details as seen in Device Spy. For example what are the services that it supports? ConnectionManager? ContentDirectory? etc.

Aardvark · « **Reply #22 on:** September 17, 2020, 12:36:04 am »

Hi Yaobing,
Tried to get as much info as possible. Below is outut from Device Spy for Beyonwiz T4 and the miniDLNA Server that can be run on it

Base URL   http://192.168.1.16:6082/
Device icon   None
Device URN   urn:schemas-upnp-org:device:MediaServer:1
Embedded devices   0
Expiration timeout   1800
Friendly name   Beyonwiz T4
Has presentation   False
Interface to host   192.168.1.9
Manufacturer   Silicondust
Manufacturer URL
Model description
Model name   BEYONWIZT4
Model number   beyonwizt4
Presentation URL
Product code
Proprietary type
Remote endpoint   192.168.1.16:6082
Serial number
Services   0
Standard type   MediaServer
Unique device name   1a66cb56-fad8-4cdc-8d73-ad5b8eaa5a2a
Version   1.0

Base URL   http://192.168.1.16:8200/
Device icon   Present, 41x48
Device URN   urn:schemas-upnp-org:device:MediaServer:1
Embedded devices   0
Expiration timeout   1810
Friendly name   miniDLNA Server
Has presentation   True
Interface to host   192.168.1.9
Manufacturer   Justin Maggard
Manufacturer URL   http://www.netgear.com/
Model description   MiniDLNA on Linux
Model name   Windows Media Connect compatible (MiniDLNA)
Model number   $(hostname)
Model URL   http://www.netgear.com/
Presentation URL   http://192.168.1.16:8200/
Product code
Proprietary type
Remote endpoint   192.168.1.16:8200
Serial number   12345678
Services   3
Standard type   MediaServer
Unique device name   4d696e69-444c-164e-9d41-001ab0000dce
Version   1.0

Apparently the services supported by Beyonwiz T4 are registered via avahi.

The Beyonwiz T4 isn't showing up in JRiver, here's the items from the JRiver logfile

315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Start
0315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Device Control enabled
0315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x20228b72c00
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Start
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Michael-PC (Generic DLNA) not TV device
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x20228b72c00
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Start
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Michael-PC (Soundtouch DLNA) not TV device
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x20228b72c00
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Start
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Michael-PC (Library Server) not TV device
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x20228b72c00
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Start
0315328: 9364: TV: CTVManager::AddDLNATVDevice: SoundTouch Wireless Link Adapter not TV device
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x20228b72c00
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Start
0315328: 9364: TV: CTVManager::AddDLNATVDevice: NAS1676D8 not TV device
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x20228b72c00
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Start
0315328: 9364: TV: CTVManager::AddDLNATVDevice: miniDLNA Server not TV device
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x20228b72c00
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Start
0315328: 9364: TV: CTVManager::AddDLNATVDevice: DMR-BWT955 not TV device
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x20228b72c00
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Start
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Monitor Service 2 not TV device
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x20228b72c00
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Start
0315328: 9364: TV: CTVManager::AddDLNATVDevice: RBR50 (Gateway) not TV device
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x20228b72c00
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Start
0315328: 9364: TV: CTVManager::AddDLNATVDevice: MICHAEL-PC not TV device
0315328: 9364: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)
0315328: 9364: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Finish (0 ms)

The Beyonwiz T4 does show as a Media Device using File Explorer to view the Network with Discovery Method shown as SSDP.

Hope this helps. Please let me know if you need me to do more checks or provide more info

Regards, Mike

Yaobing · « **Reply #23 on:** September 17, 2020, 08:23:53 am »

Quote

Manufacturer Silicondust

Interesting. No wonder I saw some familiar elements. MC discovers devices via SSDP. Why does it not see it

JimH · « **Reply #24 on:** September 17, 2020, 09:10:20 am »

Quote from: Yaobing on September 17, 2020, 08:23:53 am

Interesting. No wonder I saw some familiar elements. MC discovers devices via SSDP. Why does it not see it

Firewall?

SSDP uses port 1900.

Yaobing · « **Reply #25 on:** September 17, 2020, 04:05:25 pm »

Allow JRiver Media Center through your firewall.

Enable Media Network settings in Tools > Options > Media network (see attached screenshot).

Aardvark · « **Reply #26 on:** September 17, 2020, 09:41:35 pm »

Hi Yaobing,
Port 1900 UDP is open. JRiver Media Center is allowed through firewall and Media Network Options are all set up ( I have been running Audio to DLNA devices for ages)

I can drill down to folder on Beyonwiz T4 via Network in Drives & Devices in Media Center and playback a recorded TV program, but the device just does not show up in Playing Now.

Do I need to look at Wireshark to see what's going on?

Regards, Mike

RoderickGI · « **Reply #27 on:** September 18, 2020, 12:36:59 am »

Quote from: Aardvark on September 17, 2020, 09:41:35 pm

I can drill down to folder on Beyonwiz T4 via Network in Drives & Devices in Media Center and playback a recorded TV program,

The T4 is probably using SMB or a Windows Share to provide access to its internal drive. I don't see DLNA devices under "Drives & Devices > Network" in MC.

Quote from: Aardvark on September 17, 2020, 09:41:35 pm

but the device just does not show up in Playing Now.

That is an ongoing problem for me with my network. Specifically, my Sony TV, but BubbleUPnP is sometimes slow to show up as well, and usually I have to connect BubbleUPnP to my MC Server before it will show up, but not always. It just showed up very quickly when I tested.

Interestingly, since I installed JRiver for Android on the TV it does show up readily under Playing Now in MC as "BRAVIA 4K 2015". But I just tried to play to that and while tracks showed up on the TV, time does not progress and there was no audio. I do have control of the JRiver for Android TV App from BubbleUPnP though, as I can change the position in the track using the seek bar. I think that is a JRiver for Android issue.

Usually, my TV shows up as "KD-65X9300D" when the Sony Music App is installed, and it is visible as that in BubbleUPnP right now, as well as the "BRAVIA 4K 2015", both as Renderers. I can push tracks from BubbleUPnp to the "KD-65X9300D" and audio playback works fine.

EDIT: Note that I do see all my DLNA devices (Servers and Renderers) including the Sony TV as both "KD-65X9300D" (Sony Music App) and "BRAVIA 4K 2015" (JRiver for Android) under "Windows Explorer > Network". That is enabled via Windows Discovery, which shouldn't be required by MC for DLNA devices.

The T4 would be acting as a DLNA Server wouldn't it Yaobing? Serving TV channels to MC? Maybe it needs the miniDLNA Server to be running for MC to see it as a TV Device? Or at least have UPnP turned on in settings somewhere, if it isn't now.

But if Emby can see the T4, so should MC.

As I've said before elsewhere, it may just be my network, but I think for some reason MC just doesn't show some DLNA Devices. Or only shows them under very specific conditions. I used to be able to get my TV to show up as "KD-65X9300D" using the Sony Music App by connecting to a MC Server and then playing some tracks by pulling them from the server. But that isn't working today.

You could try connecting the T4 to your MC Server using the T4 interface, and playing some tracks if it allows it, then see if the T4 then shows up in MC under Playing Now. But the T4 would then be acting as a DLNA Controller and Renderer, and you ned it to act as a DLNA Server for TV channels, if I understand correctly.

PS: I analysed all this with Wireshark and I found that network packets were just being dropped somewhere along the line, probably by my router. I couldn't resolve why or find a fix. You may have more success.

PPS: I see you are in Sydney Australia. I'm in Melbourne. You aren't using Telstra as your ISP, and their Smart Modem Gen2 by any chance? The Arcadyan LH1000? That is the router giving me trouble.

Aardvark · « **Reply #28 on:** September 18, 2020, 01:49:01 am »

Yes I am using Telstra but not using their modem.

When I expand Network I have the Beyonwiz T4 showing as a Computer in WORKGROUP via Discovery Method WSD and as a Media Device via SSDP, I thought this might have confused JRiver. But JRiver logging doesn't even find it when checking for TV Devices. So I will continue looking at the moment

Thanks for your help

Regards, Mike

RoderickGI · « **Reply #29 on:** September 18, 2020, 04:50:41 am »

Try searching your log for the two Unique device names, 1a66cb56-fad8-4cdc-8d73-ad5b8eaa5a2a and 4d696e69-444c-164e-9d41-001ab0000dce, rather than the friendly name. You might find something relevant that way. Although all the "AddDLNATVDevice:" commands seem to use the friendly name. You should at least find that MC is seeing the SSDP packets.

My TV has two Unique device names (UUID) associated with it and they both appear in my logs, but they both have exactly the same friendly name, KD-65X9300D. I'm wondering if MC has trouble when two devices have the same device name. Although in my case, I suspect each UUID corresponds to the two DLNA capable Apps running on the TV, and that should differentiate them. I wonder if the DLNA search for TV devices, which rejects the TV in my case, is also rejecting the device as a server because it has the same friendly name. That would be bad, because the UUID should be used. But it could be possible.

I use Notepad++ to view the logs as it allows you to find all instances of a string and display them together, using the "Find All in Current Document".

It sounds like in your case Windows knows that the T4 is both an accessible storage device and a Media Device. So it should show in MC.

I'm interested to see what comes of your case, as I have tried to solve the issue with my TV several times, and just hit dead ends.

Aardvark · « **Reply #30 on:** September 19, 2020, 01:30:24 am »

Can't see any reference to the UUID for Beyonwiz T4 in JRiver logs, I can however see the UUID for MiniDLNA server when I activate that on Beyonwiz T4 but T4 doesn't show up in playing now.

Wireshark shows lots of SSDP broadcasts from 192.168.1.16:1900 to 192.168.1.9:52962 so something is falling in the cracks somewhere.

RoderickGI · « **Reply #31 on:** September 19, 2020, 03:50:33 am »

Quote from: Aardvark on September 19, 2020, 01:30:24 am

so something is falling in the cracks somewhere.

Yep. I was running the "Developer Tools for UPnP" "Device Spy" and "Device Validator" yesterday, and the latter reported missing NOYIFY packets and a couple of less serious concerns for my TV Renderer. But Device Validator found similar issues with MC Server, and crashed before it completed.

You might want to try some of those tools and see if you can find anything. They are used and recommended by JRiver's UPnP/DLNA expert, Bob, so should be safe.

Yaobing · « **Reply #32 on:** September 19, 2020, 09:29:35 am »

MC27.0.13 is available on MC27 board. Make sure you run this version and check the log again. I added a number of items in the log. For example:

2629562: 30928: TV: CTVManager::AddDLNATVDevice: HDHomeRun Prime Tuner 1317874D-2 ~~not TV device~~. DeviceURL http://192.168.200.19:80/, manufacturer Silicondust, UUID uuid:D36A747F-47B8-3288-B588-4E6F5789FBE3

All devices are said to be "not TV device" because I moved the line out of the TV device test, so I can get these things logged for all devices, but I forgot to remove the words "not TV device". This line not only includes Friendly name, but also URL and UUID, which may help identify devices in case they come in a different friendly name.

Devices that are truly not detected as TV devices get additional lines of logging. For example:

2629562: 30928: TV: CTVManager::AddDLNATVDevice: Start
2629562: 30928: TV: CTVManager::AddDLNATVDevice: 192.168.200.31 - Sonos Bridge not TV device. DeviceURL http://192.168.200.31:1400/, manufacturer Sonos, Inc., UUID uuid:RINCON_B8E9371A30BC01400
2629562: 30928: TV: CTVManager::AddDLNATVDevice: Model name Sonos Bridge, model number ZB100, Type urn:schemas-upnp-org:device:ZonePlayer:1, friendly type UPnP Media Server Device
2629562: 30928: TV: CTVManager::AddDLNATVDevice: Service type: urn:schemas-upnp-org:service:DeviceProperties:1
2629562: 30928: TV: CTVManager::AddDLNATVDevice: Service type: urn:schemas-upnp-org:service:SystemProperties:1
2629562: 30928: TV: CTVManager::AddDLNATVDevice: Service type: urn:schemas-upnp-org:service:ZoneGroupTopology:1
2629562: 30928: TV: CTVManager::AddDLNATVDevice: Service type: urn:schemas-upnp-org:service:GroupManagement:1
2629562: 30928: TV: CTVManager::AddDLNATVDevice: Finish (0 ms)

Yaobing · « **Reply #33 on:** September 19, 2020, 09:34:25 am »

So I am interested to see whether the device Beyonwiz T4 appears in a different name. I guess we might tell if we can identify the device UUID and device URL.

Aardvark · « **Reply #34 on:** September 20, 2020, 01:04:26 am »

Hi Yaobing,
Thanks for the update re logging. JRiver is definitely not showing UUID: 1a66cb56-fad8-4cdc-8d73-ad5b8eaa5a2a in the log.

Running Wireshark I see Host Announcements from Beyonwiz T4 to Local Master Browser and I also find the following SSDP item for HRTuner Proxy running on the Beyonwiz T4

Frame 1062: 331 bytes on wire (2648 bits), 331 bytes captured (2648 bits) on interface \Device\NPF_{0B9683AE-8A6D-430F-99FF-526A734D6DE4}, id 0
Ethernet II, Src: SignalNe_00:0d:ce (00:1a:b0:00:0d:ce), Dst: Giga-Byt_e0:77:91 (50:e5:49:e0:77:91)
Internet Protocol Version 4, Src: 192.168.1.16, Dst: 192.168.1.9
User Datagram Protocol, Src Port: 1900, Dst Port: 50778
Simple Service Discovery Protocol
HTTP/1.1 200 OK\r\n
USN: uuid:1a66cb56-fad8-4cdc-8d73-ad5b8eaa5a2a::upnp:rootdevice\r\n
SERVER: SSDP Server for HRTunerProxy\r\n
last-seen: 1600579409.47\r\n
EXT: \r\n
LOCATION: http://192.168.1.16:6082/device.xml\r\n
CACHE-CONTROL: max-age=1800\r\n
ST: upnp:rootdevice\r\n
DATE: Sun, 20 Sep 2020 05:39:46 GMT\r\n
\r\n
[HTTP response 4/5]
[Prev response in frame: 241]
[Next response in frame: 1151]

Hope this helps.

Yaobing · « **Reply #35 on:** September 20, 2020, 09:55:12 am »

Is your tuner on a different subnet from your computer?

Aardvark · « **Reply #36 on:** September 20, 2020, 07:50:01 pm »

Hi Yaobing,
Beyonwiz T4 is on the same subnet as my PC.

Have attached logfile of JRiver startup, hope it will give you a bit more info

Yaobing · « **Reply #37 on:** September 21, 2020, 08:15:02 am »

The log does not show any UDP from IP address 192.168.1.16. Instead, I see UDP packets originating from 192.168.1.9, which seems opposite of what we are looking for.

Yaobing · « **Reply #38 on:** September 21, 2020, 09:56:19 am »

Here are Bob's inputs on this:

"Some devices do primitive SSDP but it's only for discovery by their own software and don't present the features of a uPNP/DLNA device."

"Running the windows uPNP tools for developer device spy would show more info about what it's ssdp is actually presenting."

Yaobing · « **Reply #39 on:** September 21, 2020, 10:35:15 am »

Maybe the T4 device just does not present itself as a DLNA device?

Yaobing · « **Reply #40 on:** September 21, 2020, 11:04:48 am »

T4 does not show up in Playing Now probably because it does not support any services. That could be a problem. However, I still don't see MC detecting any UDP packets from your device IP. Maybe MC is still blocked by firewall or something.

Aardvark · « **Reply #41 on:** September 22, 2020, 02:10:16 am »

Hi Yaobing,
Please see attached doc for Device Spy for Bwiz T4 and Panasonic BWT 955 and Wireshark captures for both.

UDP from port 1900 on both devices to port 57903 on my PC.

BWT955 gets picked up by JRiver but not Bwiz.

No Services for each of them thus no entry in Playing Now.

JimH · « **Reply #42 on:** September 22, 2020, 07:54:05 am »

Quote from: Aardvark on September 22, 2020, 02:10:16 am

UDP from port 1900 on both devices to port 57903 on my PC.

Are you port forwarding 1900 to 57903? That's not likely to work.

Aardvark · « **Reply #43 on:** September 22, 2020, 08:27:26 pm »

No there is no Port Forwarding in place

Aardvark · « **Reply #44 on:** September 27, 2020, 12:23:56 am »

Hi Yaobing,
Given that there is an SSDP broadcast from HRTuner Proxy (see Device Spy.txt in earlier post) is it possible that it can be used by JRiver to access the Beyonwiz?

Yaobing · « **Reply #45 on:** September 27, 2020, 09:19:51 am »

I am still thinking about it.

Aardvark · « **Reply #46 on:** September 29, 2020, 10:15:49 pm »

Okay. Thanks for giving it some consideration Yaobing

Yaobing · « **Reply #47 on:** October 01, 2020, 11:42:20 am »

This will be a hard one. I don't know how to do this since SSDP search just would not come up with this device. From your log file I can not find any UDP packet coming from the device IP 192.168.1.16.

Yaobing · « **Reply #48 on:** October 01, 2020, 12:01:23 pm »

Quote from: Aardvark on September 20, 2020, 01:04:26 am

ST: upnp:rootdevice\r\n

Maybe this is where the problem is!?

We search for "urn:schemas-upnp-org:device:MediaRenderer", "urn:schemas-upnp-org:device:MediaServer", etc. but maybe we do not search for "upnp:rootdevice"?

bob · « **Reply #49 on:** October 01, 2020, 12:34:44 pm »

Try right-clicking on Playing Now and do
Add Dynamic Zone and put in:
http://192.168.1.16:6082/

I have no idea if that will do anything, just curious.

INTERACT FORUM

Author Topic: What is "Tuner Stream" hdhrp for? (Read 9037 times)