craigmox / cetonproxy

An app that allows a Ceton InfiniTV PCI/network tuner to appear as a SiliconDust HDHomeRun to DVR apps like NextPVR, Plex, and Emby.
GNU General Public License v3.0
23 stars 7 forks source link

Streams not working with Hyper-V installed #2

Open kcsoft33 opened 4 years ago

kcsoft33 commented 4 years ago

First off awesome app, when I found this I was so happy I could finally retire my WMC and move to nextpvr. I got this running on my Win7 based device, upgraded to W10 and all working great. A few days later with some downtime I decided to add WSL and Hyper-V to fully turn this into a server. Much troubleshooting later (I also installed new HW) I finally figured it was something to do with the networking that got added with the Hyper-V install. I removed Hyper-V but it didn't remove the virtual networking so with a network reset and one more reboot it is back to working!!

Here is a log snippet

[2020-04-14 18:16:53.755] Getting av\TransportState for tuner 3
[2020-04-14 18:16:53.934] Received av\TransportState for tuner 3: "STOPPED"
[2020-04-14 18:16:53.935] Starting stream on tuner 3 to 192.168.200.2:55728
[2020-04-14 18:16:54.283] Setting channel on tuner 3 to 113
[2020-04-14 18:16:54.377] Getting tuner\Frequency for tuner 3
[2020-04-14 18:16:54.438] Received tuner\Frequency for tuner 3: "231000"
[2020-04-14 18:16:54.438] Getting mux\ProgramNumber for tuner 3
[2020-04-14 18:16:54.480] Received mux\ProgramNumber for tuner 3: "1"
[2020-04-14 18:16:59.480] No video data on tuner 3 for channel 113
[2020-04-14 18:16:59.480] Stopping stream on tuner 3
[2020-04-14 18:16:59.666] Finished tune request from 192.168.0.211: /tuner3/v113
[2020-04-14 18:16:59.666] Service handler error: No video data

Might be just a network config wasn't correct but I ran out of downtime to keep troubleshooting and wanted to make sure this got flagged for others that might run into this problem as well. Thx!

craigmox commented 4 years ago

Hey. The automatic networking detection in cetonproxy is not great. I haven't been able to land on a solid way to decide which adapter to use for the Ceton, which to listen for HDHomeRun requests, handle UPnP, etc etc that would work in all cases. That extra Hyper-V adapter probably did confuse it.

In your particular case, it doesn't look like it was listening on the right adapter to receive video from the Ceton, so if you were to manually set the "Listen IP for Ceton" in the advanced settings, you may have been able to get it to work.

Anyway, I'm glad you were able to figure something out!