User:Seagullarity

2011-07-07T00:38:38Z

Seagullarity:

User:Seagullarity

2011-07-07T00:37:26Z

Seagullarity:

2011-04-22T23:23:44Z

Seagullarity: /* Crashing During Channel Changes */

[[Category: Hardware]]
[[Category: Video]]
{{versioninfo|810Status=works|810UpdatedDate=6th November 2010|810UpdatedBy=esev}}
[[Image:Hauppauge_Hdpvr_front.jpg|350px|center]]
<br />

[[Image:Hauppauge_hdpvr_back.jpg|250px|thumb|right|Back side of HD PVR showing Component Video, Stereo Audio, and Optical S/PDIF audio inputs and outputs]]

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 anticipated 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 un-capturable HD sources such as satellite and premium television will now be fully accessible in Linux. 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 muxed into a slightly modified MPEG-2 Transport Stream container. Capture resolution is dependent on the source (ie 720p video with be captured as such, 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. If not using VDPAU, even systems which easily play back US broadcast HD are likely to fail altogether when playing back recording from the HD-PVR. 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.

This description is from the [http://www.mythtv.org/wiki/Hauppauge_HD-PVR MythTV wiki page for the HD PVR]. See their site for more details about this device.

== Enabling S/PDIF audio ==
In all HD-PVR firmwares later than 1.0.3.53, AC-3 muxing via S/PDIF is available, allowing one to mux 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 video port device data settings under the port you are using. Modify the '''Extra Parameters''' and add a third argument. The third argument should be one of the following: 0=RCA Back, 1=RCA Front, 2=S/PDIF. Be sure not to modify the first two arguments. If, for example, your '''Extra Parameters''' contains "''<%=BLOCK%> 1''" and you'd like to use the S/PDIF audio input, modify your parameters to look like "''<%=BLOCK%> 1 2''"

[[Image:Hdpvr_port_device_details.gif|600px|center]]

== Crashing During Channel Changes ==

If rapidly changing the channels causes your HD-PVR to crash, lock your cable box to output at 720p instead of 1080p. This is a problem that exists with HD-PVR firmware 0xf and earlier.

2010-10-06T01:44:51Z

Seagullarity: New page: LinuxMCE uses the [http://subversion.apache.org subversion] revision control system (similar to CVS) to manage changes to the code base. This guide provides a few basic subversion commands...

LinuxMCE uses the [http://subversion.apache.org subversion] revision control system (similar to CVS) to manage changes to the code base. This guide provides a few basic subversion commands that will help the user to post their first patches, without having to read the [http://svnbook.red-bean.com/ subversion handbook].

We'll assume that the user has already installed subversion. For more information about installation read [[Source Code (SVN Repository)]].

==Updating Source==

Before submitting your patch to the repository, update your local copy of the source code to reflect any changes that might have occurred since your initial svn checkout. Your patch will not be accepted if your local code conflicts with the most recent version on the repository.
svn update

If you receive the message
Skipped '.'
that means you aren't currently in the directory where you checked out the source.

==Add your changes==

Place any new code files into the proper directories on your system and add them individually:
svn add filename.cpp
svn add scriptname.sh

You can review the additions that you have made to the tree by typing
svn status
The letter 'A' indicates additions, a '?' indicates unknown files that have not been added.

==Create a Diff File==

Create a .diff file, which lists the files that have been changed or added to the source. This way the developers who audit your work can easily find the changes you have made.
svn diff > ../patchname.diff
It is good practice to place the .diff file outside of the source tree or else it will show up itself as an addition to the code base. Finally, look at the .diff file to make sure it only has the changes you intended.

==Submit a Patch==

At this point, if you have been given an svn account by the devs, type
svn commit
However, the LinuxMCE developers are busy so until you have submitted your first few patches, you won't be given an account. Instead, submit your .diff file and the new or altered code files as attachments to a [http://svn.linuxmce.org/trac.cgi/report trac ticket]. Make sure to read the rules about [[Bug Reporting]] as well, if this is your first time.