NEXTPVR Server Acer AM3910-UR10P Intel Core i3-540 3.06GHz Desktop, Windows 8.1 Pro. 64bit, 2 HdHomerun units(OTA Tuners) , 1 HD Homerun Prime , for a total of 7 HD Tuners , LinkSYS 16 port Gigabyte Switch.
D-link 857 Router
I tried the patched file against my setup that uses the Hauppauge DCR-3250 3-tuner network box and it didn't appear to catch the one channel that uses H.264. What can I look for in the log files to help me understand what may have happened? Should this patch work for the Hauppauge box?
2leftfeet Wrote:I believe this patch is only relevant for HDHomerun tuners
The DCR-3250 is a rebranded HDHomeRun.
jcole, I'm not sure if it's firmware has been updated to include this new information in lineup.xml, where they report what type of channel it is. If it's the old firmware, then it just assumes it's MPEG2, and you'll have to manually update the channels.
I'm not sure if the most recent SiliconDust windows download will still update the DCR devices, but you could try installing it in hope that does.
I checked on the Hauppauge site and found that the firmware on my DCR is at the latest level. Rats. I think that trying to update a DCR with HDHomeRun firmware is risky so I'll just move on.
Using my browser to view the DCR status shows a file of Lineup.HTML, not Lineup.XML as has been suggested. Could this be the problem?
There is, indeed, a lineup.xml file created by the DCR-3250 but it lacks the extended information that is in the .xml created by the HDHomeRun that helps with what encoding is used on a channel. I contacted Hauppauge Computer Works about this. There reply was prompt. The responding engineer was aware of Silicon Dust's later firmware version and wrote that he will have new firmware ready to install next week. This should make HCW DCR-2250 and DCR-3250 devices better suited to autodetect.