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

Yaobing · « **Reply #50 on:** October 01, 2020, 12:53:09 pm »

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?

Aardvark · « **Reply #51 on:** October 02, 2020, 03:35:27 am »

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

Yaobing · « **Reply #52 on:** October 02, 2020, 08:00:03 am »

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.

Aardvark · « **Reply #53 on:** October 02, 2020, 08:07:34 am »

Hi Yaobing,
Beyonwiz V2 is not showing up in Playing Now but I can confirm that both discover.json and lineup.json exist.

Yaobing · « **Reply #54 on:** October 04, 2020, 09:39:47 am »

Build 20 is out.

Quote

27.0.19 (10/2/2020)
4. NEW: (Experimental) MC allows "Beyonwiz V2" device to be treated as a DMS TV tuner.

Aardvark · « **Reply #55 on:** October 04, 2020, 07:22:58 pm »

Thanks Yaobing. Will check it out later on today when I get a chance

Aardvark · « **Reply #56 on:** October 05, 2020, 02:29:10 am »

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>

Yaobing · « **Reply #57 on:** October 05, 2020, 07:53:02 am »

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.

Yaobing · « **Reply #58 on:** October 05, 2020, 07:59:19 am »

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>

Aardvark · « **Reply #59 on:** October 05, 2020, 02:43:50 pm »

Hi Yaobing,
Beyonwiz V2 is not showing up in Manage Television Devices. Logfile attached

Thanks, Mike

Yaobing · « **Reply #60 on:** October 05, 2020, 03:12:05 pm »

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?

Aardvark · « **Reply #61 on:** October 05, 2020, 06:30:00 pm »

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

RoderickGI · « **Reply #62 on:** October 05, 2020, 09:29:25 pm »

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

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

Yaobing · « **Reply #63 on:** October 05, 2020, 10:19:56 pm »

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.

Yaobing · « **Reply #64 on:** October 05, 2020, 10:36:10 pm »

Quote from: Aardvark on October 05, 2020, 02:29:10 am

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?

Aardvark · « **Reply #65 on:** October 06, 2020, 12:05:04 am »

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

Yaobing · « **Reply #66 on:** October 06, 2020, 05:40:17 pm »

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?

Aardvark · « **Reply #67 on:** October 08, 2020, 12:34:16 am »

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

Yaobing · « **Reply #68 on:** October 08, 2020, 07:48:03 am »

Quote

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).

Aardvark · « **Reply #69 on:** October 12, 2020, 02:19:14 am »

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

Yaobing · « **Reply #70 on:** October 12, 2020, 08:53:33 am »

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.

Aardvark · « **Reply #71 on:** October 15, 2020, 02:35:46 am »

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

JimH · « **Reply #72 on:** October 15, 2020, 08:06:15 am »

Quote from: Aardvark on October 15, 2020, 02:35:46 am

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

Aardvark · « **Reply #73 on:** October 29, 2020, 01:53:08 am »

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

Yaobing · « **Reply #74 on:** October 29, 2020, 08:07:30 am »

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.

Aardvark · « **Reply #75 on:** October 29, 2020, 11:31:45 pm »

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

Aardvark · « **Reply #76 on:** November 22, 2020, 05:59:41 pm »

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

Yaobing · « **Reply #77 on:** November 23, 2020, 07:53:05 am »

Did you get any error messages (either in a popup window or in status text area on the channel scan wizard window)?

Yaobing · « **Reply #78 on:** November 23, 2020, 11:00:37 am »

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.

Aardvark · « **Reply #79 on:** November 23, 2020, 01:44:44 pm »

Thanks for that Yaobing. Will check it out when it's available and let you know

Mike

Aardvark · « **Reply #80 on:** November 29, 2020, 10:55:34 pm »

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

Yaobing · « **Reply #81 on:** November 30, 2020, 01:33:12 pm »

Good to know.

Quote from: Aardvark on November 29, 2020, 10:55:34 pm

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.

Quote

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.

Aardvark · « **Reply #82 on:** December 06, 2020, 08:51:22 pm »

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

Yaobing · « **Reply #83 on:** December 06, 2020, 10:19:36 pm »

Sorry, recording does not work yet. I have been working on it and it should be available soon.

Aardvark · « **Reply #84 on:** December 07, 2020, 12:01:23 am »

OK no worries.

Aardvark · « **Reply #85 on:** December 13, 2020, 12:48:29 am »

Hi Yaobing,
Just to let you know that recording is working fine using V2727.0.43 with BWIZ

Thanks, Mike

Yaobing · « **Reply #86 on:** December 13, 2020, 08:44:41 am »

Great!

INTERACT FORUM

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