INTERACT FORUM
Windows => Television => Topic started by: 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?
-
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.
-
I guess I still don't understand. Can you explain how to use it? Example of what it does?
-
I'm guessing it uses the http interface instead of the bda architecture?
-
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.
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).
-
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
-
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)?
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)
-
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
-
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.
-
Is Media Network turned on in MC settings?
-
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
-
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
-
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.
-
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?
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.
-
Hi Yaobing,
I found this out from looking at an Emby log.
Regards, Mike
-
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
-
We are working on DLNA devices that show up under Playing Now. Hopefully we can get channels by querying the device like yours.
-
Hi Yaobing,
That sounds good. Let me know if you need anything tested.
Regards, Mike
-
Hi Yaobing,
Any chance that this could be looked at in MC27?
Regards, Mike
-
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?
-
Hi Yaobing
Details as follows
"FriendlyName": "Beyonwiz T4", "ModelNumber": "beyonwizt4",
Regards, Mike
-
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?
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:
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.
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.
-
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
-
Manufacturer Silicondust
Interesting. No wonder I saw some familiar elements. MC discovers devices via SSDP. Why does it not see it :(
-
Interesting. No wonder I saw some familiar elements. MC discovers devices via SSDP. Why does it not see it :(
Firewall?
SSDP uses port 1900.
-
Allow JRiver Media Center through your firewall.
Enable Media Network settings in Tools > Options > Media network (see attached screenshot).
-
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
-
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.
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.
-
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
-
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.
-
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.
-
so something is falling in the cracks somewhere.
Yep. I was running the "Developer Tools for UPnP (https://www.meshcommander.com/upnptools)" "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.
-
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)
-
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.
-
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.
-
Is your tuner on a different subnet from your computer?
-
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
-
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.
-
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."
-
Maybe the T4 device just does not present itself as a DLNA device?
-
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.
-
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.
-
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.
-
No there is no Port Forwarding in place
-
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?
-
I am still thinking about it.
-
Okay. Thanks for giving it some consideration Yaobing
-
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.
-
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"?
-
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.
-
We came to the conclusion that it is wrong for a device to advertise itself as a "upnp:rootdevice" when it is a media server. Maybe you can talk to the device maker about it?
-
Hi Yaobing,
I've just replaced my Beyonwiz T4 with their latest model Beyonwiz V2 and updated to JRiver 2727.0.18 and log now picks up the Beyonwiz V2. Please see attached log
Regards, Mike
-
Yes Beyonwiz V2 shows up in the log as a Media Server device.
Does it show up in Playing Now? If it does, right-click on it and choose Load. If it loads, go to Video and see if there are anything. It probably will not have any channels listed there because the device does not support ContentDirectory service (in fact it does not support any service, like T4).
I hope http://192.168.1.18:6082/discover.json, and http://192.168.1.18:6082/lineup.json exist. If these do exist, I think we can support this device in spite of it having no ContentDirectory service.
-
Hi Yaobing,
Beyonwiz V2 is not showing up in Playing Now but I can confirm that both discover.json and lineup.json exist.
-
Build 20 is out.
27.0.19 (10/2/2020)
4. NEW: (Experimental) MC allows "Beyonwiz V2" device to be treated as a DMS TV tuner.
-
Thanks Yaobing. Will check it out later on today when I get a chance
-
Hi Yaobing
Gave this a try and see the following in the log, but device doesn't appear to be added
0005699: 6668: TV: CTVManager::AddDLNATVDevice: Start
0005699: 6668: TV: CTVManager::AddDLNATVDevice: Creating a device array
0005700: 6668: Reader: CWinINetReader::Open: Start
0005700: 6668: Reader: CWinINetReader::Open: Opening http://192.168.1.18:6082
0005700: 6112: Reader: CWinINetReader::Thread: Start
0005700: 6112: Reader: CWinINetReader::Thread: url: http://192.168.1.18:6082
0005700: 6112: Reader: CWinINetReader::Connect: Start
0005700: 6112: Reader: CWinINetReader::Connect: Finish (0 ms)
0005700: 6112: Reader: CWinINetReader::DownloadFromHTTPURL: Start
0005700: 6112: Reader: CWinINetReader::DownloadFromHTTPURL: HttpOpenRequest successful
0005710: 6112: Reader: CWinINetReader::DownloadFromHTTPURL: HttpSendRequest successful
0005710: 6112: Reader: CWinINetReader::DownloadFromHTTPURL: Success
0005710: 6112: Reader: CWinINetReader::DownloadFromHTTPURL: Finish (9 ms)
0005710: 6112: Reader: CWinINetReader::Thread: Finish (10 ms)
0005710: 6668: Reader: CWinINetReader::Open: Finish (10 ms)
0005710: 6668: Reader: CWinINetReader::Read: InternetReadFile returned true with zero bytes read: EOF
0005710: 6668: Reader: CWinINetReader::Close: Start
0005711: 6668: Reader: CWinINetReader::Close: Finish (0 ms)
0005711: 6668: TV: CTVManager::AddDLNATVDevice: Finish (11 ms)
0005711: 6668: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x291ec00fd30
0005711: 6668: TV: CTVManager::AddDLNATVDevice: Start
0005711: 6668: TV: CTVManager::AddDLNATVDevice: Michael-PC (Generic DLNA) not TV device. DeviceURL , manufacturer JRiver, Inc., UUID uuid:1b792fbf-ded9-4429-8d33-20e85a5cbfdd
File that is read is as follows
<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.1.18:6082</URLBase>
<device>
<deviceType>urn:schemas-upnp-org:device:MediaServer:1</deviceType>
<friendlyName>Beyonwiz V2</friendlyName>
<manufacturer>Silicondust</manufacturer>
<modelName>BEYONWIZV2</modelName>
<modelNumber>beyonwizv2</modelNumber>
<serialNumber></serialNumber>
<UDN>uuid:066c42c0-07c9-4d30-be91-3218e9074d1e</UDN>
</device>
</root>
-
After waiting for a couple of minutes upon MC startup, go to Television, right-click, Manage Devices. Do you see the device there? As you did not see the device in Playing Now last time you sent a log, you do not expect to see it there this time either. You should see it in TV's Device Manager.
-
When MC picks up the device through SSDP, it sends the device to its TVManager, where you should see either of the following two lines of logging:
TV: CTVManager::AddDLNATVDevice: <devicename> not TV device...
or
TV: CTVManager::AddDLNATVDevice: Adding device <devicename>
-
Hi Yaobing,
Beyonwiz V2 is not showing up in Manage Television Devices. Logfile attached
Thanks, Mike
-
This is weird indeed. In the last log you provided, the device was clearly detected. This time there is no sign of it. Could the device have gone to sleep?
-
Hi Yaobing,
Device is switched on and I started the DLNA server in the Beyonwiz V2 just to assist in verifying that the device is active on the network. MiniDLNA shows up in Playing Now but no device in Manage Television Devices. Logfile attached
-
There are four references to the Beyonwiz V2 in that latest log file, based on the IP Address and Port:
Line 807: 0002984: 11176: Reader: CWinINetReader::Open: Opening http://192.168.1.18:6082
Line 809: 0002993: 7636: Reader: CWinINetReader::Thread: url: http://192.168.1.18:6082
Line 2590: 0005093: 11176: Reader: CWinINetReader::Open: Opening http://192.168.1.18:6082
Line 2592: 0005093: 9000: Reader: CWinINetReader::Thread: url: http://192.168.1.18:6082
Looking at the log lines around those, the URL is opened successfully, but nothing is done with it.
Maybe it is time to use Device Spy to see what it finds for the Beyonwiz V2. You have only run it for the T4 so far haven't you?
Developer Tools for UPnP Technologies (https://www.meshcommander.com/upnptools)
Or maybe AndrewFG's Digital Media Renderer Analyser (DMRA) would shed some light on what the Beyonwiz V2 can do. Of course, it only tests for Renderers, but may show something.
Whitebear DRMA (https://www.whitebear.ch/dmra)
-
The log on October 2 showed that the device was tested and was determined to be not a TV tuner. That was the kind of event we need, but I did not see any other events that led to it being treated as a DLNA device. It just suddenly appeared. The opening of the URL http://192.168.1.18:6082 happened almost two minutes before the device was discovered in that log, and therefore may not be related. I would expect to see something like http://192.168.1.18:6082/device.xml (or http://192.168.1.18:80/device.xml or something similar) being opened, but nothing like that happened.
Maybe the miniDLNA is interfering? The October 2 log did not have the miniDLNA in it.
-
Hi Yaobing
Gave this a try and see the following in the log, but device doesn't appear to be added
0005699: 6668: TV: CTVManager::AddDLNATVDevice: Start
0005699: 6668: TV: CTVManager::AddDLNATVDevice: Creating a device array
0005700: 6668: Reader: CWinINetReader::Open: Start
0005700: 6668: Reader: CWinINetReader::Open: Opening http://192.168.1.18:6082
0005700: 6112: Reader: CWinINetReader::Thread: Start
0005700: 6112: Reader: CWinINetReader::Thread: url: http://192.168.1.18:6082
0005700: 6112: Reader: CWinINetReader::Connect: Start
0005700: 6112: Reader: CWinINetReader::Connect: Finish (0 ms)
0005700: 6112: Reader: CWinINetReader::DownloadFromHTTPURL: Start
0005700: 6112: Reader: CWinINetReader::DownloadFromHTTPURL: HttpOpenRequest successful
0005710: 6112: Reader: CWinINetReader::DownloadFromHTTPURL: HttpSendRequest successful
0005710: 6112: Reader: CWinINetReader::DownloadFromHTTPURL: Success
0005710: 6112: Reader: CWinINetReader::DownloadFromHTTPURL: Finish (9 ms)
0005710: 6112: Reader: CWinINetReader::Thread: Finish (10 ms)
0005710: 6668: Reader: CWinINetReader::Open: Finish (10 ms)
0005710: 6668: Reader: CWinINetReader::Read: InternetReadFile returned true with zero bytes read: EOF
0005710: 6668: Reader: CWinINetReader::Close: Start
0005711: 6668: Reader: CWinINetReader::Close: Finish (0 ms)
0005711: 6668: TV: CTVManager::AddDLNATVDevice: Finish (11 ms)
0005711: 6668: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Checking TV devices. TVManager 0x291ec00fd30
0005711: 6668: TV: CTVManager::AddDLNATVDevice: Start
0005711: 6668: TV: CTVManager::AddDLNATVDevice: Michael-PC (Generic DLNA) not TV device. DeviceURL , manufacturer JRiver, Inc., UUID uuid:1b792fbf-ded9-4429-8d33-20e85a5cbfdd
File that is read is as follows
<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.1.18:6082</URLBase>
<device>
<deviceType>urn:schemas-upnp-org:device:MediaServer:1</deviceType>
<friendlyName>Beyonwiz V2</friendlyName>
<manufacturer>Silicondust</manufacturer>
<modelName>BEYONWIZV2</modelName>
<modelNumber>beyonwizv2</modelNumber>
<serialNumber></serialNumber>
<UDN>uuid:066c42c0-07c9-4d30-be91-3218e9074d1e</UDN>
</device>
</root>
Reading your previous post. Are you saying that the URL http://192.168.1.18:6082 opens the XML file? If that is the case, it should have detected it. The only problem I see here is still that the device does not support any service. Why did it show up on October 2, but not today? :(
-
Hi Yaobing,
Have attached doc with Device Spy output in it, Whitebear DMRA doesn't pick up the Beyonwiz V2. I don't know why the behaviour would be different to Oct 02. Only thing I have noticed is that UUID has changed after reconfiguring HRTuner Proxy and is now as shown in attached doc
Don't understand why CWinINetReader says zero bytes read for xml file at 192.168.1.18:6082 as the file opens when I click on the hyperlink in the logfile and is as shown in attached doc.
Have turned off miniDLNA on V2 so have attached new logfile
-
Unfortunately I don't see any other clues from your latest attachment. It feels like we are back to square one. The V2 device now behaves just like the T4. Maybe there are ways to change the configuration of the devices?
-
Hi Yaobing,
Spent a bit of time looking at this and noticed the following.
One of the first accesses in the log from JRiver to another machine is looking at device.xml on the Beyonwiz V2.
0002992: 7280: Reader: CWinINetReader::Open: Start
0002992: 7280: Reader: CWinINetReader::Open: Opening http://192.168.1.18:6082
0003014: 10672: Reader: CWinINetReader::Thread: Start
0003014: 10672: Reader: CWinINetReader::Thread: url: http://192.168.1.18:6082
0003015: 10672: Reader: CWinINetReader::Connect: Start
0003016: 10672: Reader: CWinINetReader::Connect: Finish (1 ms)
0003016: 10672: Reader: CWinINetReader::DownloadFromHTTPURL: Start
0003016: 10672: Reader: CWinINetReader::DownloadFromHTTPURL: HttpOpenRequest successful
0003060: 10672: Reader: CWinINetReader::DownloadFromHTTPURL: HttpSendRequest successful
0003060: 10672: Reader: CWinINetReader::DownloadFromHTTPURL: Success
0003060: 10672: Reader: CWinINetReader::DownloadFromHTTPURL: Finish (44 ms)
0003060: 10672: Reader: CWinINetReader::Thread: Finish (45 ms)
0003060: 7280: Reader: CWinINetReader::Open: Finish (68 ms)
0003061: 7280: Reader: CWinINetReader::Read: InternetReadFile returned true with zero bytes read: EOF
0003061: 7280: Reader: CWinINetReader::Close: Start
0003061: 7280: Reader: CWinINetReader::Close: Finish (0 ms)
What is CWinInetreader looking for in device.xml and why does it end with "InternetReadFile returned true with zero bytes read: EOF" which to me implies an empty file, yet this is what device.xml contains
<root>
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.1.18:6082</URLBase>
<device>
<deviceType>urn:schemas-upnp-org:device:MediaServer:1</deviceType>
<friendlyName>Beyonwiz V2</friendlyName>
<manufacturer>Silicondust</manufacturer>
<modelName>BEYONWIZV2</modelName>
<modelNumber>beyonwizv2</modelNumber>
<serialNumber/>
<UDN>uuid:8e7df9e4-16ab-4f67-bd17-b6ceb751625c</UDN>
</device>
</root>
If I look at some of the other CWinInetReader actions for other network device accesses they look like
0003180: 4484: Reader: CWinINetReader::Open: Start
0003180: 4484: Reader: CWinINetReader::Open: Opening http://192.168.1.5:8200/rootDesc.xml
0003180: 7148: Reader: CWinINetReader::Thread: Start
0003180: 7148: Reader: CWinINetReader::Thread: url: http://192.168.1.5:8200/rootDesc.xml
0003180: 7148: Reader: CWinINetReader::Connect: Start
0003180: 7148: Reader: CWinINetReader::Connect: Finish (0 ms)
0003180: 7148: Reader: CWinINetReader::DownloadFromHTTPURL: Start
0003181: 7148: Reader: CWinINetReader::DownloadFromHTTPURL: HttpOpenRequest successful
0003188: 7148: Reader: CWinINetReader::DownloadFromHTTPURL: HttpSendRequest successful
0003188: 7148: Reader: CWinINetReader::DownloadFromHTTPURL: Success
0003188: 7148: Reader: CWinINetReader::DownloadFromHTTPURL: Finish (7 ms)
0003188: 7148: Reader: CWinINetReader::Thread: Finish (8 ms)
0003189: 4484: Reader: CWinINetReader::Open: Finish (8 ms)
0003189: 4484: Reader: CWinINetReader::Close: Start
0003190: 4484: Reader: CWinINetReader::Close: Finish (0 ms)
I've attached the latest logfile
Thanks for your help
Regards, Mike
-
0003061: 7280: Reader: CWinINetReader::Read: InternetReadFile returned true with zero bytes read: EOF
This generally does not indicates error. It just says it has read the entire file (reached EOF).
-
Hi Yaobing
Firstly just wanted to say that I really appreciate your help in trying to get this working, frustrating for both of us I guess. Although I have seen this working in both Emby and Plex the picture quality in JRiver with Red October HQ is just miles better. I have been using JRiver for music since V18 and so I jumped at the chance to try and get TV via JRiver as well.
I just thought I'd give this one more shot, I ran a Wireshark trace on 2 Devices the Bwiz V2 and a Panasonic DVR that I have. I see SSDP broadcasts for both of them, the Panasonic Diga gets picked up by CTVManager but the Bwiz V2 isn't. So what's the difference in the handling of the SSDP message?
Simple Service Discovery Protocol
HTTP/1.1 200 OK\r\n
CACHE-CONTROL: max-age=1800\r\n
DATE: Sun, 11 Oct 2020 05:24:40 GMT\r\n
EXT:\r\n
LOCATION: http://192.168.1.14:61118/A81374A9E3B4/dial_srv/ddd/dial.xml\r\n
SERVER: Linux/4.0 UPnP/1.0 Panasonic-UPnP-MW/1.0\r\n
ST: urn:schemas-upnp-org:device:Basic:1\r\n
USN: uuid:4D454930-0600-1000-8000-A81374A9E3B4::urn:schemas-upnp-org:device:Basic:1\r\n
\r\n
[HTTP response 6/9]
[Prev response in frame: 194]
[Next response in frame: 277]
Simple Service Discovery Protocol
HTTP/1.1 200 OK\r\n
USN: uuid:8e7df9e4-16ab-4f67-bd17-b6ceb751625c::upnp:rootdevice\r\n
SERVER: SSDP Server for HRTunerProxy\r\n
last-seen: 1602239969.87\r\n
EXT: \r\n
LOCATION: http://192.168.1.18:6082/device.xml\r\n
CACHE-CONTROL: max-age=1800\r\n
ST: upnp:rootdevice\r\n
DATE: Sun, 11 Oct 2020 05:26:56 GMT\r\n
\r\n
[HTTP response 6/6]
[Prev response in frame: 922]
Logfile also attached
Thanks, Mike
-
This time the log does not even show any instance of "192.168.1.18:6082" and it looks very much like how it behaved with your old T4.
In any case, when build 22 comes out, make sure you test again.
-
Hi Yaobing,
Done more investigation and some reading. I have found out that in general Linux machines
do not do SSDP and that it only occurs when a UPNP Server is implemented on the machine. I was able to confirm this by
removing HRTuner Proxy from the V2 and then running a Wireshark trace where I only saw MDNS and NBNS messages from the V2.
I have reinstalled the HRTuner Proxy plugin and can now see SSDP broadcasts
Simple Service Discovery Protocol
HTTP/1.1 200 OK\r\n
USN: uuid:8e7df9e4-16ab-4f67-bd17-b6ceb751625c::upnp:rootdevice\r\n
SERVER: SSDP Server for HRTunerProxy\r\n
last-seen: 1602746352.32\r\n
EXT: \r\n
LOCATION: http://192.168.1.18:6082/device.xml\r\n
CACHE-CONTROL: max-age=1800\r\n
ST: upnp:rootdevice\r\n
DATE: Thu, 15 Oct 2020 07:21:54 GMT\r\n
\r\n
[HTTP response 1/3]
[Next response in frame: 186]
Are you able to pick up this so-called device from this broadcast? You then have access to Beyonwiz V2 details from device.xml
<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.1.18:6082</URLBase>
<device>
<deviceType>urn:schemas-upnp-org:device:MediaServer:1</deviceType>
<friendlyName>Beyonwiz V2</friendlyName>
<manufacturer>Silicondust</manufacturer>
<modelName>BEYONWIZV2</modelName>
<modelNumber>beyonwizv2</modelNumber>
<serialNumber/>
<UDN>uuid:8e7df9e4-16ab-4f67-bd17-b6ceb751625c</UDN>
</device>
</root>
and can go straight to discover.json and lineup.json
I can see these SSDP broadcasts being sent on a regular basis to my PC
3232 275.611141 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
3233 275.611141 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
3667 319.033220 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
3738 323.247787 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
3778 325.210640 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
3985 335.388782 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
3986 335.388782 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
3991 335.389847 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
4043 335.498329 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
4047 335.498636 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
4048 335.499358 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
4106 335.612678 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
4107 335.612678 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
4108 335.612678 192.168.1.18 192.168.1.9 SSDP 331 HTTP/1.1 200 OK
Don't know if this is a possibility but thought I'd run it by you anyway
Regards, Mike
-
Done more investigation and some reading. I have found out that in general Linux machines
do not do SSDP and that it only occurs when a UPNP Server is implemented on the machine. I was able to confirm this by
removing HRTuner Proxy from the V2 and then running a Wireshark trace where I only saw MDNS and NBNS messages from the V2.
I don't think that's quite right. SSDP is a protocol, like HTTP is a protocol. Any application (not just a UPnP Server) can implement it.
https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol
-
Hi Yaobing,
I saw when 27.0.26 came out that you had made logging changes for DLNA so I thought that I would check out if anything had changed re discovering Beyonwiz V2 but again the V2 wasn't picked up.
However I did download JRiver Bingo SSDP and found that it manages to find and give all the details of the Beyonwiz V2 so how come JRiver Media Center doesn't pick it up?
Regards, Mike
-
At some point MC did pick up V2 (at least once). But then somethings changed. Maybe something configured the V2 server aspect? Right now my suspicion is that something changed the SSDP type to "rootdevice" which MC ignored.
Please grab a log file for me anyway. Make sure logging is on, then restart MC. Wait for a couple of minutes and grab the log file.
-
Hi Yaobing,
Logfile attached. Also screenshot from Bingo SSDP. It must be something other than rootdevice that is tripping this up as looking at the screenshot the Panasonic also has rootdevice yet that is always picked up in JRiver Media Center.
Thanks for your help
Regards, Mike
-
Hi Yaobing,
Downloaded V27.0.34 over the weekend and ran it and found that it now picks up the Beyonwiz V2, so thanks very much for those changes.
I ran the TV Setup and it shows the V2 with the 4 Tuners so I just configured one tuner at this stage with no EPG. When I ran the Scan however it finds no channels.
I have attached the logfile from this test.
Thanks for your help
Mike
-
Did you get any error messages (either in a popup window or in status text area on the channel scan wizard window)?
-
I think I got it. I added this change for a future build:
Changed: When MC fails to get DMS TV channels using the device's "urn:schemas-upnp-org:service:ContentDirectory" service, an alternative method of using a channel lineup JSON file (if available) will be attempted.
-
Thanks for that Yaobing. Will check it out when it's available and let you know
Mike
-
Hi Yaobing,
Loaded up JRiver 2727.0.37 and ran Television setup, added in Ice TV for the EPG, ran Scan and then Next. TV Channels populated and EPG downloaded. An excellent result. Two minor problems at the moment I have 2 channels where I have the wrong EPG, so just have to figure out how to correct that. Also on SD channels I have a green bar across the bottom of the screen. If I manually feed in the channel URL to JRiver I get a fullscreen display and no green bar.
All in all a great outcome, thanks for your perseverance. When I have checked it out a bit more I will let the BWiz users forum know that they have another option for using their machine
Regards, Mike
-
Good to know.
I have 2 channels where I have the wrong EPG, so just have to figure out how to correct that.
Run Load Program guide... manually and see whether these channels are mapped to the correct XMLTV IDs. Try manually change the mapping.
Also on SD channels I have a green bar across the bottom of the screen. If I manually feed in the channel URL to JRiver I get a fullscreen display and no green bar.
This is a known issue.
-
Hi Yaobing,
I've got a problem when trying to record. The recording fails with the following message in the TV Logs "Failed to start recording, either because there is no idle tuner or a matching tuner did not work properly"
Logfile and Filter info attached
Regards, Mike
-
Sorry, recording does not work yet. I have been working on it and it should be available soon.
-
OK no worries.
-
Hi Yaobing,
Just to let you know that recording is working fine using V2727.0.43 with BWIZ
Thanks, Mike
-
Great!