Hauppauge HD-PVR2

[christheman]

This section puts a smile on my face.  Thanks to all involved for making this happen with Linux!

I have been using Linux Mint now for about 4 or 5 years and basically use it for all my internet-facing computers, so this is very interesting to me.

There is a situation I have wondered about, though in typical fashion for me, I am probably the only one who ever thought of it.  Could it be practical for one to compile and load the "test" application in Linux for the Hauppauge HD-PVR2 on this platform? 
https://hauppauge.com/pages/support/supp...tml#hdpvr2

I do have a couple of these and use one connected to a sat tuner box on a regular basis, though using Windows XP and a much-outdated version of NextPVR on a HP DC7900 USDT with an E8400 Duocore processor.

I intend to upgrade to a more recent computer in that rack (an HP 8300 USDT with 4 core i5-3470s processor - Linux Mint seems to like these so I have a couple extra), so this might be a path I could go down, otherwise I am probably looking at loading it with Windows 7.

Thanks
Chris

[mvallevand]

I use the original HDPVR 1212 with Debian daily using firewire tuning and the only issue I have is I lose AC3 every once in a while. I could not get the built in IR blaster on mine working though but I also have an iguana works blaster (I have 3 STBs) and that is very reliable.

You don't need to compile anything if you have a supported HDPVR2 they should just show up as v4l devices. Once you see the vl4 device I can help you with creating an extra device.

Martin

[christheman]

Hi Martin

Sounds good. I'll post back when I get to that point.

Thanks
Chris

[shspvr]

I use the original HDPVR 1212 with Debian daily using firewire  tuning and the only issue I have is I lose AC3 every once in a while.  I could not get the built in IR blaster on mine working though but I also have an iguana works blaster (I have 3 STBs) and that is very reliable.

You don't need to compile anything if you have a supported HDPVR2 they should just show up as v4l devices.  Once you see the vl4 device I can help you with creating an extra device.

Martin

That funny only original HD-PVR show up as v4l devices as far I know of not the HD-PVR 2 nor Colossus 2 as the driver that from Hauppauge are in forum of user mode application when did sub support it ?.

[mvallevand]

Ok after more checking maybe didn't help enable v4l support for these devices. I see there is a command line tool that might work as a command line extra if it supports stdout and can graciously shutdown

Martin

[christheman]

Well I've been busy this week but I did get a chance to load the Linux version of NextPVR and got to the point where the device could be added.  In addition I compiled the small program linked above in the thread, in case I might need it.  It causes the HD-PVR2 lights to change.  Have there been any further thoughts on adding the HD-PVR2 since the two of you last posted?  Basically this is going to replace the Windows device driver that ships with the unit, except I may need to connect the dots yet somewhere?

Chris

[shspvr]

Well I've been busy this week but I did get a chance to load the Linux version of NextPVR and got to the point where the device could be added.  In addition I compiled the small program linked above in the thread, in case I might need it.  It causes the HD-PVR2 lights to change.  Have there been any further thoughts on adding the HD-PVR2 since the two of you last posted?  Basically this is going to replace the Windows device driver that ships with the unit, except I may need to connect the dots yet somewhere?

Chris

I ask brad if has any plan on converting the Linux HD-PVR 2 / Colossus 2 drivers in to a reg package

[mvallevand]

If the command line pipes to stdout it would be matter of creating an extra that look like

Code:

<extras>
  <channel name="{channel-name}">
    <command>bash</command>
    <args>-c "/var/opt/nextpvr/scripts/hdpvr.sh {channel}"</args>
  </channel>
</extras>

and then hdpvr.sh look like

Code:

blaster.sh $1
hdpv2app parameters | ffmpeg -v panic -i pipe: -vcodec copy - acodec (copy or aac) -

test with

/var/opt/nextpvr/scripts/hdpvr.sh 100 | ffplay -i pipe:

Martin

[christheman]

Ok, I got the files created. I created the "extras-hdpvr2.xml" file with "extras" tag into the "/var/opt/nextpvr" directory (along with the main NextPVR config file), as per the Windows version of the wiki help. Then that comes up as an extra device in NextPVR.

I then created the "HDPVR2.sh" file into the "/var/opt/nextpvr/scripts" directory. That file is referenced by the "extras-hdpvr2.xml" file.

I am assuming that the "blaster.sh $1" line is for a remote blaster? If so I can safely comment that out for now.

Also it looks like you are using FFMPEG only to properly form the video file, and nothing else. So is "-v panic" used to indicate file termination? Also I see you are using "-i pipe:" in two different places, so that must be the correct format to form the filenames from Schedules Direct? Finally what does the "100" do in "/var/opt/nextpvr/scripts/hdpvr.sh 100 | ffplay -i pipe:"? Is this command used to play back the video in NextPVR, or just watch live?

P.S, I am still using the NEWA add-on on the Windows XP version of NextPVR. Is that still an add-on, or has it been integrated into the base of the current version of NextPVR? I haven't fully implemented it all quite yet to find out.

Thanks
Chris

[mvallevand]

-v panic is to stop ffmpeg text output from going to stdout

-i pipe is indicating reading stdout, you see it twice only in the test because ffplay is mimicking how NextPVR will read the stdout from the .sh file.

the 100 is a fake channel number, the real one will be passed from NextPVR for your blaster script. Playing a recording will be be from a file created using this script. For testing your can comment out the line yes.

NEWA web browser is gone and replaced by the new browser interface.