Menu
I wanted to buy one of these, but before I pay my own a. for one please help me with 2 questions:1 - I've heard you need a somewhat powerful PC to be able to use it, so the question is will my laptop be able to use it?: Here's the specs (Asus N53Jq)Intel Core i7 740QM 1,73 GHz, Nividia GeForce GT 425M 1GB, 6GB RAM.Every spec is above the requirements, i'm just not sure about the processor since it asks 2.0 and mine is 1.73.2 - Is there a list out there of recordable/compatible consoles? I can't find it anywhere.
![]()
The box only says Xbox 360 and PS3, but are these the only recordable systems for HD PVR 2? Can't we use the component adapter for the Wii, or use all component cables that comes with the HD PVR 2 to record PS2 too?That's about it, I was hoping you guys could help me out here:)Thank you for your time. Ok I just got the HD PVR 2 in the mail =DNow can you guys give me any tips on installing the required software? I've heard lots of people having trouble with the drivers and stuff, so I wanted to hear your tips on how to make a good installation of it.And also, should I install it from the CD that comes with the HD PVR 2 or should I download the software from the official site? I'm asking because i've heard the software that comes in the CD is outdated, although i'm not sure about it.Thank you for your time. Ok I just got back from 2 hours of testing.and I must say i'm quite satisfied with the product for now =DPS3 testing went brilliantly. I had trouble connecting it to the HDTV, but then I figured out I had to do each step in exact order and then it went fine.
I put 720p on my PS3 settings since 1080p then screws up the output on the HDTV (which I expected), and I loved the recordings i've done. Great quality and sound:DOne thing I noticed is the contrast is a little off, it needs a little more contrast but I figured out you can change that on AcrShowBiz.Then I went to test my Wii (main reason I wanted a PVR) and YES IT WORKED =D Like a charm actually, I thought I was going to have alot of trouble with it but it was just plug-and-play. I was speachless! I tested a Wii game and a few emulated games.
The latest versions of WinTV v10, 8.5 and WinTV v8 and Hauppauge Capture include these drivers. But if you are looking just for the Windows 10 driver, these are updated drivers which can be used with Windows 10. Here i will show you how to setup and use the HD PVR 2 if you have a Mac. I don't know how to do it for Windows, so that is my bad. I had trouble finding tutorials that worked for me on YouTube.
All of it worked like a charm and the recordings were great =D I got synching problems with a Gamecube game I tested, but I know why it happened and it's not the PVR it's my Wii that can't run Gamecube games properly.Then I tried using the component cable to record PS2, and unfortunately it didn't work. After trying simply using it to connect the PS2 to the TV, I realized the cable isn't even compatible with the PS2.
So to record PS2 you really have to buy a component cable specifically for it. If it worked with the Wii, I don't see how it wouldn't with the PS2.I had no trouble with the software or instalation. Pretty simple and straightforward. I really don't get why ArcShowBiz has such a lackluster editor, but that's okay I use another editor anyway.All in all, everything went right and i'm very happy with the results =DThank you for your help Monsieur:D.
Note: As of November 2013, ONLY the Hauppauge HD-PVR models 1212 and 1445 are supported by the Linux TV project. No HD-PVR 2 models are supported in Linux. There is an early, testing version of a HD-PVR 2 driver for Linux available at ftp://ftp.hauppauge.com/Support/Test/Lin/hauppauge_driver_src_ver5.tgz
The Hauppauge HD-PVR Model 1212.
The Hauppauge HD-PVR is the first consumer-level analog HD capture device available. The HD-PVR is a USB device that captures the component video outputs and analog/optical audio outputs of any consumer device (including cable/satellite set-top-boxes, HD disk players, video game consoles, and various other home media devices). The HD-PVR is a highly popular capture device because it captures video via component output, permitting the user to capture high-definition video from most sources and without concern for encryption. In other words, since component video is not and cannot be encrypted, previously uncapturable HD sources such as satellite and premium television will now be fully accessible in MythTV. Prior to this device, component capture devices were cost-prohibitive and were not directly supportable within Linux.
The HD PVR captures at resolutions from VGA/D1 (480i) up to 1080i, and encodes the component inputs in real time using the H.264/MPEG-4 video codec and the AAC audio codec. The streams are multiplexed into a slightly modified MPEG-2 Transport Stream container. Capture resolution is dependent on the source (ie 720p video will be captured as 720p, 1080i as 1080i, etc.) but the bitrate is user-selectable from 1 megabit/second up to 13.5 megabits/second. The H.264 video codec is, bit-for-bit, up to 40% more efficient than the MPEG-2 video codec commonly used in US HDTV broadcasts today. A 13.5 Mb/s H.264 stream is roughly equivalent to a full-channel-bitrate MPEG-2 recording at approximately 19 Mb/s.
The HD-PVR uses modern codecs capable of exceptional compression rates at excellent quality. The tradeoff is that decoding H.264 material is very processor-intensive. Fortunately, using VDPAU or VDA video card hardware acceleration makes H.264 playback easy. By contrast, even systems which easily play back US broadcast/cable MPEG-2 HD are likely to fail altogether when playing back a recording from the HD-PVR without hardware acceleration. Hauppauge recommends a dual-core CPU as a minimum if not using VDPAU; a frequently cited minimum for medium-bitrate H.264 playback is a Core 2 Duo 1.8 Ghz processor. HD Playback Reports acts as a repository for processor requirements to play high definition material. HD-PVR users are encouraged to contribute to the page to ascertain real-world playback requirements without VDPAU or some other form of hardware-accelerated playback with MythTV.
In all HD-PVR firmwares later than 1.0.3.53, AC-3 multiplexing via S/PDIF is available, allowing one to multiplex the original 5.1 channel audio track into the captured stream. To enable this functionality, be sure to set the audio input to S/PDIF by editing the capture card definition in mythtv-setup and setting the preferred input device to S/PDIF.
Hardware versions
Hauppauge sells several h.264 high-definition encoders.
The 1212 HD-PVR is the original product. After the company discovered that many who purchased the HD-PVR did so not for recording high-definition television but to capture their video game play to upload to YouTube, it introduced the 1445 HD-PVR Gaming Edition, with the following minor differences:
If the prices of the 1212 and 1445 are the same buy the 1212, but if the 1445 is cheaper then buy it and get the component and IR cables separately.
The 1414 Colossus is a PCI-based encoder card. It does not have Linux support.
The 1482 HD-PVR2 Gaming Edition is an USB-based external encoder. Along with component video, it can capture HDMI, but does not support HDCP. It does not support 5.1 or greater audio over HDMI, and unlike the 1212/1445 it lacks an S/PDIF input so cannot capture 5.1 sound that way. It does not have Linux support.
Configuring the HD-PVR in MythTV
MythTV includes support for the HD-PVR from v0.22 and up. See below for caveats and setup information.
Caveats
Once the tuner has been added as an encoder in MythTV, it is vital that the user not access the tuner in outside programs such as cat, VLC, and mplayer. This can lead to MythTV's connection with the driver becoming unstable, and subsequent recordings failing until the driver is reloaded and power is cycled on the HD-PVR.
The last sync with libavcodec did greatly improve stability when playing material from the HD-PVR. If you still get playback crashes, try compiling myth with --disable-ssse3.
For Motorola STBs, it is also important to set the '4:3 Override' option to Off or Stretch. For some Motorola STBs, both the aspect ratio settings and output resolution controls can be found by powering down the STB and then pressing the Menu button.
Myth can become non-responsive due to run-away 'mythbackend --generate-preview' processes. If you check your mythbackend logs and see it being flooded with ac3 or faac errors, it is likely the 'generate-preview' process doing it. A 'pkill -f generate-preview' will return your myth system to a usable state. You may even want to add that pkill to a cron job.
The HD-PVR previously had problems gracefully dealing with resolution changes but those issues have been fixed in MythTV. You can now allow your receiver to float between 480i, 480p, 720p and 1080i without causing the HD-PVR or MythTV to hang.
If you have the ir_kbd_i2c module loaded, this can cause the HD-PVR to hang after a short amount of recording (60-120 seconds). Remove this module via 'rmmod ir_kbd_i2c' and try again if this is affecting you.
The HD-PVR is unable to capture closed captioning data while recording, unless the captioning is displayed on the screen at the time of capturing - in which case sub-titles cannot be turned off during playback. A workaround is possible if another tuner is available.
Steps to Add the HD-PVR as a Capture Device in MythTV (0.22 or later)
Assuming you followed the directions carefully, you should now be able to record with the HD-PVR. If you get 'Select Timeout' errors, these can sometimes be overcome by stopping the backend, removing the hdpvr module, cycling the power on the HD-PVR, modprobe-ing the hdpvr module, and restarting the backend.
You can set the bitrate for the HD-PVR by going into Recording Profiles, and editing the profiles associated with HD-PVR encoders. These recording profiles have bitrate settings for low (480i/p), medium (720p), and high (1080i) resolution material, allowing you to set appropriate bitrates based upon the resolution of the material. If the max bitrate is set lower than the average bitrate, the result is CBR (constant bit rate) at the rate specified by the average slider. If you want VBR (variable bit rate), set the max slider to maximum, and then use the average slider to achieve the desired bitrate.
Firmware Version Stability
Firmware is available at Hauppauge HD-PVR Support page under the 'Windows Driver' tab, 'Windows driver for HD PVR' - 'It is also for HD PVR users with third party Mac or Linux applications. Please note: this loads firmware onto HD PVR (it must be run on a Windows PC).'
If you still experience problems with stability, a small kernel module re-load script is included below in the Bitrate and Picture Controls sub section that re-loads the kernel modules and acts like a power cycle on the HD-PVR.
Over-saturation and Color Solution
If you run a firmware version of 1.6.29207 or later, and run a kernel version of 3.2.34 or earlier, you may experience over-saturation and color issues. You have 2 options for avoiding this this issue all-together:
1) Run a firmware version of 1.5.7.0 (0x15) or earlier (not necessarily recommended)
2) Upgrade to a kernel version of 3.3 or later (recommended)
A driver updated was applied to the 3.3 Linux kernel that automatically compensates for the way the firmware handles hue and saturation in different driver versions. If you can't upgrade your kernel version, or run an earlier HD-PVR firmware version, then you can try and work-around the issue as a last resort using one of the following solutions. Only the last one worked for me, but as always YMMV. No matter which route you go, the following command will always need to be run:
The first place you can run this is in a startupScript. Simply have it run when your mythtv backend boots up. Since every distro is different please consult your distro's documentation on how to add it.
The second place you can run this is in your channel change script. I use 6200ch as my channel changer. In order to run the above code I created a script and use that script in mythtv-setup for my channel change program. Here is mine:
/opt/bin/6200-hdpvr.sh
The third option, which worked for me, was to use a script in combination with MythTV System Events. To use this option, create a script:
/opt/bin/setHDPVR.sh
Next, open 'mythtv-setup -> System Events -> Recording started' and give it the path to your new script (/opt/bin/setHDPVR.sh). Repeat for the 'LiveTV started' event. After that, every time a recording starts it will run the fix and your recording should have proper colors.
Firmware Versions
The firmware version reported by the HD-PVR device on Linux is not the same version number as the driver package for Windows. The table below shows the driver package filename for installation on Windows, the date of the driver package (when downloaded directly from Hauppauge's site, this is from the timestamp of the file on their server), the date of the firmware ROM files within the driver package (the hcwhdpvr.rom file), and the version of the firmware reported on Linux. The majority of these driver packages can be downloaded from
http://hauppauge.lightpath.net/software/hd_pvr/ or http://www.shspvr.com/ftp/download/wintv-hdpvr/ .
Firmware Upgrade Process
The firmware on the device cannot be upgraded through a GNU/Linux system at this time. Use the following process within a physical MS Windows installation: (it is known to not work from VMWare Fusion, or with VirtualBox running on OS X)
Hardware Stability and Troubleshooting
While the majority of users have used the HD-PVR trouble-free for years, many users have reported various issues in regards to stability of the HD-PVR device itself. These issues usually materialize either as 0-byte recordings or heavily damaged (i.e., artifacts) within MythTV. There are a few different theories on what can cause these issues, as well as a variety of solutions to try.
A few things known to impact the stability of the device:
A few things to try if you discover you are having intermittent failures of recordings from the HD-PVR:
HD-PVR Driver Compilation Howto
Note: As of Linux Kernel 2.6.30 the driver for the HD-PVR is now included by default. However, the driver may not have the necessary bits to enable the IR transmitter. You only have to follow this procedure if
Note: This how-to has been upgraded to support a more current kernel versions (2.6.32 and greater). The historical Mercurial [instructions] may still work on older kernels.)
The development branch of the HD-PVR Linux driver is available from the LinuxTV project. - http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
Currently, firmware loading is unimplemented in the driver. As a result, if you have a 'rev c1' or newer unit you must install the HD-PVR at least once on a Windows machine to load the firmware into it. If you have a Revision 2 unit (including a sticker marked 'rev c2' on the bottom of the unit) then it will come loaded with a firmware. Once you have done so, you will need a working build environment, git, and kernel headers installed on your system. In Debian and debian-based distros, the following command should install all necessary dependencies to build the driver.
On some systems (e.g. Ubuntu 10.04), it is git-core instead of git, so use:
In RPM based distros such as Mythdora, the following command should suffice, assuming the proper development tools, kernel-headers and kernel-devel have already been installed.
In best case scenarios, the following should be enough to compile and install the driver:
Note: Compilation errors do occur some times:
If compilation and installation succeeded, it should be possible to load the HD-PVR driver with:
If dmesg only shows 'registered new interface driver hdpvr' and no /dev/video# device has been created, you probably have a newer device than your kernel module supports.
If dmesg shows 'wrong firmware version,' and 'device init failed,' then you did not install the device in Windows first and the firmware has not been loaded. Install the HD-PVR on a Windows machine, install the drivers, and after that the device should work fine in Linux.
In Ubuntu, the module may fail to load and refer you to the dmesg command. If this happens, reboot and see if the error resolves itself. It is also possible that Ubuntu is prioritizing another, older copy of the v4l-dvb modules above the one you just installed, and the HD-PVR will fail because the two versions do not match. Try a command like:
This will search for the cx88-dvb kernel module, which is provided in the Hg tree you just built, and also in default Ubuntu installs. If you see more than one copy of this file, you may need to move the older versions out of the way. In at least one case, alternate versions of all the modules were located in '/opt/ltsp/amd64/lib/modules/kernel version number/ubuntu/'. The symbol mismatch was solved by moving the '/opt/ltsp/amd64/lib/modules/kernel version number/ubuntu/media' directory into a backup directory in the user's home, then rebooting.
Testing the Driver
Even if you didn't compile your own kernel module, you should always test your box outside of MythTV before trying inside of MythTV.Once the module has loaded successfully, you can check dmesg for output and to determine which /dev/video node it has created. You can then test the device as with any hardware encoder:
Press your interrupt character (usually ctrl-C) to stop the capture, and play it back with any compatible media player (i.e., mplayer, xine, mythfrontend).
Bitrate and Picture Controls
The HD-PVR driver is compatible with the v4l2-ctl command line utility included in ivtv-tools. To see a list of adjustable controls, use the following command:
Substitute the correct video# in the example above. The following controls are presently supported in the driver:
You can adjust any of these values with a command like:
Or, for example:
This command will set the bitrate to the maximum of 13.5 Mbit/s for the HD-PVR at /dev/video0.
The audio_encoding selection only works for PCM input. If the HD-PVR is fed AC3, then AC3 will always be multiplexed into the H.264.
Note that the picture controls did not have any known effect prior to firmware version 0x16 (1.6.29199).
Firmware 0x16+ Picture Control Defaults
Until a patch that sets the new defaults is committed to the kernel, you can use
to set the proper defaults.
Example startup script
Here is a small script to:
Adjusting Picture Settings Automatically
It seems that the color settings have to be adjusted every time recording starts. The 'Recording Started' event in the MythTV System Events is ideal for this.
Here's a script that you can run as a Recording Started event that iterates over all /dev/hdpvr* devices and sets the picture controls appropriately. Adjust device names or other settings as needed.
The script will not run if the kernel version is not less than 3.4. Supposedly this problem has been addressed in kernel version 3.4 and later. Remove this check if you like.
Put this script in /usr/local/bin or /opt/bin and configure it as an event handler in your MythTV backend setup.
Miscellaneous Kernel Module Options
Several options exist that may be of assistance when troubleshooting or for certain use cases. If the audio output is too low, you can boost the audio signal by adding the following module option for the hdpvr module:
If you wish to see more verbose dmesg output, you can use the following module option:
Where # = an integer between 1 and 7, increasing in level of verbosity.
Sets the device node to /dev/video#
default video input: 0=component, 1=S-Video, 2=composite
default audio input: 0=RCA back, 1=RCA front, 2=S/PDIF.
Note: For firmware 0xf, default audio input must apparently be set to 2 to enable spdif/optical recording. This does not change the encoding default (AAC) and does not up-convert to 5.1 if the spdif/optical input is stereo. Simply edit /etc/modprobe.d/hdpvr.conf to have this info (without quotes): 'options hdpvr default_audio_input=2'. If this doesn't work for you or if you want to be able to easily change it on the fly, try this script.
IR Transmitter Support
As of September 1, 2009 IR Blasting and receiving is tentatively working. Jarod Wilson has created patches for the lirc and hdpvr drivers. He's in the process of having his patches approved and committed.
Note: As of April 2011, numbers of users have reported instability if the HD-PVR is configured as an IR receiver. To workaround this, make sure that 'options lirc_zilog tx_only=1' is set in the modprobe.conf or /etc/modprobe.d/hdpvr.conf depending on the distribution
The HD-PVR, as with many other Hauppauge on-card emitters, only supports a fixed set of IR codes. The HD-PVR includes a wide variety of codes for most common set top boxes, but it may or may not contain codes for special buttons like arrow or menu buttons. See below for more information on codesets and lircd.conf. Compile LIRC Modules for IR Transmitter Support
The HD-PVR's IR Blaster must be supported in both the LinuxTV driver and the LIRC driver. If your distribution doesn't include support for the IR Blaster you may build it yourself. Follow the steps mentioned above to download and compile the hdpvr driver from linuxtv.org (lirc_zilog.ko and lirc_dev.ko are also included in that process).
Steps to Enable IR Transmitter
At this point the IR transmitter should send the codes properly to the STB. Channel changes will still require a channel change script. (In this example, 0_74 was the remote number supported.)
Checking STB Power Status
One issue with using the HDPVR with Component Video is that there's noobvious way to check that the Cable Box is powered on when beginning arecording.
The following script is used as the channel change script. Setup: Cisco STB on TWC, HDPVR using Component Video, Ubuntu 14.04.1 with MythTV 0.28pre.
YMMV
Video Standard
Quoted from a user on mythtv-users
'>Hello,
>
> I have a couple of HD PVR 1212 bought from ebay. One of the devices
> worked out of the box, however I could not get the other device to work.
> Poking with v4l2-ctl i see
>
> For working device:
>
> Video input : 0 (Component: ok)
> Audio input : 2 (SPDIF)
> Video Standard = 0x00000007
> PAL-B/B1/G
>
> For Non-working device:
>
> Video input : 0 (Component: ok)
> Audio input : 2 (SPDIF)
> Video Standard = 0x0000f900
> PAL-M/60
> NTSC-M/M-JP/443/M-KR
>
>
![]()
> HD PVR-1212 doesnt seem to be a multi-PAL device (my video feed is
> PAL-B). This is news to me. The Hauppauge page
> (http://hauppauge.com/site/products/data_hdpvr.html) lists both PAL and
> NTSC formats.
>
> Can the video standard be changed?
>
> Is there a model number specific to the video standard supported?
>
> Thanks
>
I was able to change the Video standard of my non-working device using
![]()
v4l2-ctl -d /dev/video0 --set-standard=6
and now it works. Solved!'
And from Devin Heitmueller 'By the way, you can run 'v4l2-ctl --list-standards' to see the list ofall standards supported by the device.' Limitations
Some UK television providers (notably Virgin and Freesat) have restricted the HD-PVR and similar devices by selectively disabling the component outputs of their set top boxes. In the US, the Motion Picture Association of America has requested that the Federal Communications Commission allow providers to disable the component outputs of their devices when showing recently released movies. In the US, the FCC granted the waiver in specific conditions.
Retrieved from 'http://www.mythtv.org/wiki?title=Hauppauge_HD-PVR&oldid=64839'
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |