I am currently running windows 7 with Two Ceton InfiniTV 6 PCIe cards.
I have setup two different NICs and assign one cetonproxy on 192.168.1.50 and another on cetonproxy 192.168.1.51.
The second instance with a custom configuration folder (C:\cetonproxy\cetonproxy.exe -config "C:\Users\HTPC\AppData\Roaming\cetonproxy2") so that I can have different settings for the second instance.
Both cetonproxy applications run fine and dont report any IP binding issues (now that you made the port 80 optional).
I am able to access the lineup and stream from each card/cetonproxy application:
However, when I try to detect my devices via NextPVR, both cards show up as the same 6 devices. I confirmed this by running one Cetonproxy application and then detecting devices. If no cetonproxy app is running, the 6 devices are unavailable. If either cetonproxy application is run, NextPVR reports the same 6 tuners (never 12 tuners as I would like or expect).
I believe the problem is that the device name generated by both cetonproxy apps are the same (HDHomeRun 13154FED-0). @craigmox can we add a command line or configuration option to specify a custom HDHomeRun ID? Do you have any ideas how to get this resolved?
Appreciate you help! Thank you!
I manually edited the NextPVR DB to add the 6 other devices to the CAPTURE_SOURCE and HDHR_RECORDER tables. I added the other device as HDHomeRun 13155FED. Unfortunately, it shows up as unavailable and wont be found:
@craigmox - does the SSDP Multicast port or IP need to change? or just the device ID?
Weirdly enough, I cleared the configuration directory for the second ceton card/cetonproxy. I then reconfigured from scratch and now the devices show up!
I am currently running windows 7 with Two Ceton InfiniTV 6 PCIe cards.
I have setup two different NICs and assign one cetonproxy on 192.168.1.50 and another on cetonproxy 192.168.1.51.
The second instance with a custom configuration folder (C:\cetonproxy\cetonproxy.exe -config "C:\Users\HTPC\AppData\Roaming\cetonproxy2") so that I can have different settings for the second instance.
Both cetonproxy applications run fine and dont report any IP binding issues (now that you made the port 80 optional).
I am able to access the lineup and stream from each card/cetonproxy application:
However, when I try to detect my devices via NextPVR, both cards show up as the same 6 devices. I confirmed this by running one Cetonproxy application and then detecting devices. If no cetonproxy app is running, the 6 devices are unavailable. If either cetonproxy application is run, NextPVR reports the same 6 tuners (never 12 tuners as I would like or expect).
I believe the problem is that the device name generated by both cetonproxy apps are the same (HDHomeRun 13154FED-0). @craigmox can we add a command line or configuration option to specify a custom HDHomeRun ID? Do you have any ideas how to get this resolved?
Appreciate you help! Thank you!
I manually edited the NextPVR DB to add the 6 other devices to the CAPTURE_SOURCE and HDHR_RECORDER tables. I added the other device as HDHomeRun 13155FED. Unfortunately, it shows up as unavailable and wont be found:![NextPVR_Devices](https://user-images.githubusercontent.com/9253870/97581843-78c27f00-19cb-11eb-8595-e34ee0f46ff8.PNG)
@craigmox - does the SSDP Multicast port or IP need to change? or just the device ID?