Ceton Infinitv4, Windows 10

[st0rmcat]

Do either of you know if its tuners are accessible via the same web interface as the Ethernet tuner?

From memory yes, they still show as a network interface.

Cool then it might work out of the box.

Question for you, I had to make my app listen on port 80, because NextPVR appears to only look for lineup.xml on that port for HDHR devices (at least for my app pretending to be one). Should NextPVR be paying attention to the port that is provided in lineup URL of its HDHR discovery response?

[sub]

Question for you, I had to make my app listen on port 80, because NextPVR appears to only look for lineup.xml on that port for HDHR devices (at least for my app pretending to be one).  Should NextPVR be paying attention to the port that is provided in lineup URL of its HDHR discovery response?

I guess it probably should - I'd never thought about it though, because every HDHR I've encountered had it on port 80. I can look to make this change though.

Can you post the beginning of your nrecord.log, where it shows the HDHR discovery?

[st0rmcat]

Sure.  I know it's not something that really matters in practice, since of course real devices have their own IP.  But in my case, having my proxy app listen on port 80 while trying to share with a bunch of other apps on the same computer can be a little problematic.

FYI The log shows two devices.  I do have a real 2-tuner device on the network (and SiliconDust drivers installed in Windows).

[sub]

Is this the Ceton?

2020-01-17 15:03:53.483 [DEBUG][1] got discovery response
2020-01-17 15:03:53.485 [DEBUG][1] ...
2020-01-17 15:03:53.485 [DEBUG][1] HDHOMERUN_TAG_DEVICE_TYPE: 1
2020-01-17 15:03:53.485 [DEBUG][1] HDHOMERUN_TAG_DEVICE_ID: 8E128E16
2020-01-17 15:03:53.485 [DEBUG][1] HDHOMERUN_TAG_DEVICE_AUTH_STR
2020-01-17 15:03:53.485 [DEBUG][1] HDHOMERUN_TAG_TUNER_COUNT: 6
2020-01-17 15:03:53.485 [DEBUG][1] HDHOMERUN_TAG_BASE_URL: http://192.168.1.10:5004
2020-01-17 15:03:53.485 [DEBUG][1] HDHOMERUN_TAG_LINEUP_URL: http://192.168.1.10:5004/lineup.json

[st0rmcat]

Yep

[sub]

Do you have a xml version of the url? Normally NextPVR looks at lineup.xml, which isn't what is listed here. I guess I could always assume I can replace .json with .xml

[sub]

Ok, I think this change is in place for the next build.

[st0rmcat]

I've only ever seen my real HDHR device respond with a json lineup URL. I was surprised when I saw NextPVR looking for the XML, honestly. I wasn't sure if one was deprecated or what, so I just respond to both. Anyway, you could substitute in the lineup URL or just take the base URL and add the XML doc. Doesn't matter I imagine. Thank you!

[videolog]

I moved from WMC and jumped into NextPVR very recently.  I have an InfiniTV 6 network tuner and wrote a Windows app that sits in front of the Ceton and emulates an HD HomeRun device, specifically so I could get it to work with NextPVR v5.  It's a quick and dirty app written in Delphi (I know..), but so far it's working for me.  I felt bad just keeping it to myself, so I put it up here in case it might work for someone else:  https://github.com/craigmox/cetonproxy

I don't actually know if it works for a PCI Ceton card.  Do either of you know if its tuners are accessible via the same web interface as the Ethernet tuner?

I have been following this thread as I have the InfinTV 6 Pci, that has served me well using SageTV. I would like to use NextPvr v5, and your utility looks very interesting. I tried running the file as you outlined but I get a fastMM4 memory error. I have no idea what that is or how to remedy it.

I also believe your little utility would benefit many as you can't buy any cable card tuners at the moment. The HD HomeRun prime 6 is delayed.

[mvallevand]

@videolog if you are running SageTV then you already have OpenDCT running so the extra method should work, if you want to run unmodifed without replacing the jar file just use tuner 1

Martin