LinuxMCE - User contributions [en]

Skinning Engine

2011-06-25T18:54:16Z

Mandingo:

skinning_engine

*
Skinning Engine
o
Summary and Rationale
o
Requirements
o
Skinning Engine Proposals
o
How QT Quick and QML might be used in QT 4.7.x
o
Ideas for Skinning Engines
o
Qt 4 based Skinning Engine

Skinning Engine
Summary and Rationale

Status: This specification is in drafting. Please feel free to add comments.

Supported Widgets

*
Push-buttons
*
Multi-state push buttons
*
Sliders
o
horizontal or vertical
*
Text labels
*
Knobs
*
VU meter
*
Embed library widget
*
Status
*
Datagrid widget
*
Video widget

Requirements

Metadata/Manifest

*
Include the following metadata:
o
author
o
title
o
description
o
language
o
skin version
o
license
o
update-URL
o
suggested screen resolution
o
min screen resolution

Base Widget

*
Nameable
*
Position, Size
o
Potentially offer absolute positioning mode for legacy support, but in general deprecate absolute positioning.
o
Use size-hints (max-min size) instead of single size.
*
Tooltip
*
Connections
o
EmitOnDownPress and EmitOnRelease properties (to obviate need for double-connections)
o
Choose mouse button.
*
Tab ordering?

Widget Layout

*
Widget Grouping
o
Nameable
o
Have a size hint and optionally an absolute position.
o
Provide a hide/show-control. Uses the group's name.
*
Layouts
o
Allow a widget group to have a layout assigned to it.
*
Windows
o
Windows are the root of each hierarchy of widgets
*
Widget Templates
o
Ability to specify some template for a widget for saving time, sanity.

Widgets

*
Buttons
o
Allow multi-state button or push-button.
o
Support pixmaps for each button position
o
Allow non-pixmap buttons. Use QSS to styling.
*
Slider
o
Allow vertical or horizontal orientation
o
Separate image for slider and knob
o
Allow non-pixmap sliders. Use QSS for styling.
*
Drop-down Chooser
o
Allow styling via QSS.
o
No pixmap option, as it's text-only.
*
Knobs
o
Single knob image that is rotated plus background image.
o
Allow specification of 'translation' function (i.e. log-potmeter or potmeter)
o
Allow non-pixmap knobs. Use QSS for styling.
*
Library Widget
o
Still a monolithic widget. Don't think it adds value to allow much customization here.
o
Use QSS for all appearance styling.
*
Text labels
o
Make use of Controls to display text instead of hard-coding text.
o
Potentially allow scripts to dynamically affect what is shown.
o
Allow Marquee effect so you can read text that goes out of the control.
*
VU Meter
o
Allow QSS styling (how???) or pixmaps.
*
Status
o
Connects to a control and dynamically switches its pixmap or QSS property based on the control's value
*
Datagrid Widget
o
Requirements unknown.
*
Video Widget
o
Requirements unknown.

Skinning Engine Proposals

Given the above requirements, list various proposals for skin formats here:

*
Qt4, Qt Style Sheet-based approach
*
Qt 4.7 QML/Kinetic-based approach
*
HTML/CSS Based Skins

The current ideas are:
Qt 4 based Skinning Engine

Qt 4 is the cross-platform framework.

For the creation of a skinning system, Qt supports many things: layouts, style sheets, vector graphics, raster/OpenVG/OpenGL rendering, useful low-level painting system, XML, animation framework (since 4.6 or as official add-on), declarative UI technology (since 4.6)…

By combining some of these technologies it should be possible to create an advanced skinning engine for LMCE.
To investigate

*
Explore QWidget versus QGraphicsView for layout.
o
How does the performance stack up?
o
QWidgets can be rendered in a QGV, but how does this affect performance?
+
But when the visualization is rendered in OpenGL, we'll probably have to render the whole QGV in OpenGL
o
QGV will give us a really cool and flexible UI in combination with the Animation/DUI framework
o
QGV will give us fast software-based UI rendering, as well as support for rendering the UI through OpenGL and since Qt 4.6 also OpenVG
*
Explore if and how style sheets can help
o
Style sheets are very useful to skin stuff like scrollbars and other default widgets
o
The more important stuff like buttons should probably be skinned by reimplementing paintEvent, because this gives more possibilities
+
Style sheets may be slower than reimplementing paintEvent - although it has to be investigated to be sure
+
More advanced animations (besides simple hover/overroll effects) cannot be created with style sheets only

Skinning Engine

2011-06-25T18:50:33Z

Mandingo:

skinning_engine

*
Skinning Engine
o
Summary and Rationale
o
Current System
o
Requirements
o
Skinning Engine Proposals
o
How QT Quick and QML might be used in QT 4.7.x
o
Forum discussion
o
Ideas for Skinning Engines
o
Qt 4 based Skinning Engine

Skinning Engine
Summary and Rationale

Status: This specification is in drafting. Please feel free to add comments.

Supported Widgets

*
Push-buttons
*
Multi-state push buttons
*
Sliders
o
horizontal or vertical
*
Text labels
*
Knobs
*
VU meter
*
Embed library widget
*
Status
*
Datagrid widget
*
Video widget

Requirements

Metadata/Manifest

*
Include the following metadata:
o
author
o
title
o
description
o
language
o
skin version
o
license
o
update-URL
o
suggested screen resolution
o
min screen resolution

Base Widget

*
Nameable
*
Position, Size
o
Potentially offer absolute positioning mode for legacy support, but in general deprecate absolute positioning.
o
Use size-hints (max-min size) instead of single size.
*
Tooltip
*
Connections
o
EmitOnDownPress and EmitOnRelease properties (to obviate need for double-connections)
o
Choose mouse button.
*
Tab ordering?

Widget Layout

*
Widget Grouping
o
Nameable
o
Have a size hint and optionally an absolute position.
o
Provide a hide/show-control. Uses the group's name.
*
Layouts
o
Allow a widget group to have a layout assigned to it.
*
Windows
o
Windows are the root of each hierarchy of widgets
*
Widget Templates
o
Ability to specify some template for a widget for saving time, sanity.

Widgets

*
Buttons
o
Allow multi-state button or push-button.
o
Support pixmaps for each button position
o
Allow non-pixmap buttons. Use QSS to styling.
*
Slider
o
Allow vertical or horizontal orientation
o
Separate image for slider and knob
o
Allow non-pixmap sliders. Use QSS for styling.
*
Drop-down Chooser
o
Allow styling via QSS.
o
No pixmap option, as it's text-only.
*
Knobs
o
Single knob image that is rotated plus background image.
o
Allow specification of 'translation' function (i.e. log-potmeter or potmeter)
o
Allow non-pixmap knobs. Use QSS for styling.
*
Library Widget
o
Still a monolithic widget. Don't think it adds value to allow much customization here.
o
Use QSS for all appearance styling.
*
Text labels
o
Make use of Controls to display text instead of hard-coding text.
o
Potentially allow scripts to dynamically affect what is shown.
o
Allow Marquee effect so you can read text that goes out of the control.
*
VU Meter
o
Allow QSS styling (how???) or pixmaps.
*
Status
o
Connects to a control and dynamically switches its pixmap or QSS property based on the control's value
*
Datagrid Widget
o
Requirements unknown.
*
Video Widget
o
Requirements unknown.

Skinning Engine Proposals

Given the above requirements, list various proposals for skin formats here:

*
Qt4, Qt Style Sheet-based approach
*
Qt 4.7 QML/Kinetic-based approach
*
HTML/CSS Based Skins

The current ideas are:
Qt 4 based Skinning Engine

Qt 4 is the cross-platform framework.

For the creation of a skinning system, Qt supports many things: layouts, style sheets, vector graphics, raster/OpenVG/OpenGL rendering, useful low-level painting system, XML, animation framework (since 4.6 or as official add-on), declarative UI technology (since 4.6)…

By combining some of these technologies it should be possible to create an advanced skinning engine for LMCE.
To investigate

*
Explore QWidget versus QGraphicsView for layout.
o
How does the performance stack up?
o
QWidgets can be rendered in a QGV, but how does this affect performance?
+
But when the visualization is rendered in OpenGL, we'll probably have to render the whole QGV in OpenGL
o
QGV will give us a really cool and flexible UI in combination with the Animation/DUI framework
o
QGV will give us fast software-based UI rendering, as well as support for rendering the UI through OpenGL and since Qt 4.6 also OpenVG
*
Explore if and how style sheets can help
o
Style sheets are very useful to skin stuff like scrollbars and other default widgets
o
The more important stuff like buttons should probably be skinned by reimplementing paintEvent, because this gives more possibilities
+
Style sheets may be slower than reimplementing paintEvent - although it has to be investigated to be sure
+
More advanced animations (besides simple hover/overroll effects) cannot be created with style sheets only

Skinning Engine

2011-06-25T18:22:21Z

Mandingo:

skinning_engine

*
Skinning Engine
o
Summary and Rationale
o
Current System
o
Requirements
o
Skinning Engine Proposals
o
How QT Quick and QML might be used in QT 4.7.x
o
Forum discussion
o
Ideas for Skinning Engines
o
Qt 4 based Skinning Engine

Skinning Engine
Summary and Rationale

Status: This specification is in drafting. Please feel free to add comments.

Supported Widgets

*
Push-buttons
*
Multi-state push buttons
*
Sliders
o
horizontal or vertical
*
Text labels
*
Knobs
*
VU meter
*
Embed library widget
*
Status light

Requirements

Metadata/Manifest

*
Include the following metadata:
o
author
o
title
o
description
o
language
o
skin version
o
license
o
update-URL
o
suggested screen resolution
o
min screen resolution

Base Widget

*
Nameable
*
Position, Size
o
Potentially offer absolute positioning mode for legacy support, but in general deprecate absolute positioning.
o
Use size-hints (max-min size) instead of single size.
*
Tooltip
*
Connections
o
EmitOnDownPress and EmitOnRelease properties (to obviate need for double-connections)
o
Choose mouse button.
*
Tab ordering?

Widget Layout

*
Widget Grouping
o
Nameable
o
Have a size hint and optionally an absolute position.
o
Provide a hide/show-control. Uses the group's name.
*
Layouts
o
Allow a widget group to have a layout assigned to it.
*
Windows
o
Windows are the root of each hierarchy of widgets
*
Widget Templates
o
Ability to specify some template for a widget for saving time, sanity.

Widgets

*
Buttons
o
Allow multi-state button or push-button.
o
Support pixmaps for each button position
o
Allow non-pixmap buttons. Use QSS to styling.
*
Slider
o
Allow vertical or horizontal orientation
o
Separate image for slider and knob
o
Allow non-pixmap sliders. Use QSS for styling.
*
Drop-down Chooser
o
Allow styling via QSS.
o
No pixmap option, as it's text-only.
*
Knobs
o
Single knob image that is rotated plus background image.
o
Allow specification of 'translation' function (i.e. log-potmeter or potmeter)
o
Allow non-pixmap knobs. Use QSS for styling.
*
Library Widget
o
Still a monolithic widget. Don't think it adds value to allow much customization here.
o
Use QSS for all appearance styling.
*
Text labels
o
Make use of Controls to display text instead of hard-coding text.
o
Potentially allow scripts to dynamically affect what is shown.
o
Allow Marquee effect so you can read text that goes out of the control.
*
VU Meter
o
Allow QSS styling (how???) or pixmaps.
*
Status light
o
Connects to a control and dynamically switches its pixmap or QSS property based on the control's value
*
Datagrid Widget
o
Requirements unknown.
*
Video Widget
o
Requirements unknown.

Skinning Engine Proposals

Given the above requirements, list various proposals for skin formats here:

*
Qt4, Qt Style Sheet-based approach
*
Qt 4.7 QML/Kinetic-based approach
*
HTML/CSS Based Skins

The current ideas are:
Qt 4 based Skinning Engine

Qt 4 is the cross-platform framework.

For the creation of a skinning system, Qt supports many things: layouts, style sheets, vector graphics, raster/OpenVG/OpenGL rendering, useful low-level painting system, XML, animation framework (since 4.6 or as official add-on), declarative UI technology (since 4.6)…

By combining some of these technologies it should be possible to create an advanced skinning engine for LMCE.
To investigate

*
Explore QWidget versus QGraphicsView for layout.
o
How does the performance stack up?
o
QWidgets can be rendered in a QGV, but how does this affect performance?
+
But when the visualization is rendered in OpenGL, we'll probably have to render the whole QGV in OpenGL
o
QGV will give us a really cool and flexible UI in combination with the Animation/DUI framework
o
QGV will give us fast software-based UI rendering, as well as support for rendering the UI through OpenGL and since Qt 4.6 also OpenVG
*
Explore if and how style sheets can help
o
Style sheets are very useful to skin stuff like scrollbars and other default widgets
o
The more important stuff like buttons should probably be skinned by reimplementing paintEvent, because this gives more possibilities
+
Style sheets may be slower than reimplementing paintEvent - although it has to be investigated to be sure
+
More advanced animations (besides simple hover/overroll effects) cannot be created with style sheets only

Pro

*
Support pixmap skins (porting of current skins will be easier this way, and performance will probably be higher than using SVG)
*
Support SVG skins (for those who want, SVG skins should be an option as well
o
Performance may be lower, but we could optionally render SVG as pixmaps to improve performance
*
Possibility to implement a layout system (because interface elements should not stretch)
*
The window itself should be themable/deformable too. Could be achieved by either composite or with a mask (or both)

Skinning Engine

2011-06-25T17:58:18Z

Mandingo: Created page with "skinning_engine * Skinning Engine o Summary and Rationale o Current System o Requirements o..."

skinning_engine

*
Skinning Engine
o
Summary and Rationale
o
Current System
o
Requirements
o
Skinning Engine Proposals
o
How QT Quick and QML might be used in QT 4.7.x
o
Forum discussion
o
Ideas for Skinning Engines
o
Qt 4 based Skinning Engine

Skinning Engine
Summary and Rationale

Status: This specification is in drafting. Please feel free to add comments.

Supported Widgets

*
Push-buttons
*
Multi-state push buttons
*
Sliders
o
horizontal or vertical
*
Text labels
*
Knobs
*
VU meter
*
Embed library widget
*
Status light

Requirements

Metadata/Manifest

*
Include the following metadata:
o
author
o
title
o
description
o
language
o
skin version
o
license
o
update-URL
o
suggested screen resolution
o
min screen resolution

Base Widget

*
Nameable
*
Position, Size
o
Potentially offer absolute positioning mode for legacy support, but in general deprecate absolute positioning.
o
Use size-hints (max-min size) instead of single size.
*
Tooltip
*
Connections
o
EmitOnDownPress and EmitOnRelease properties (to obviate need for double-connections)
o
Choose mouse button.
*
Tab ordering?

Widget Layout

*
Widget Grouping
o
Nameable
o
Have a size hint and optionally an absolute position.
o
Provide a hide/show-control. Uses the group's name.
*
Layouts
o
Allow a widget group to have a layout assigned to it.
*
Windows
o
Windows are the root of each hierarchy of widgets
*
Widget Templates
o
Ability to specify some template for a widget for saving time, sanity.

Widgets

*
Buttons
o
Allow multi-state button or push-button.
o
Support pixmaps for each button position
o
Allow non-pixmap buttons. Use QSS to styling.
*
Slider
o
Allow vertical or horizontal orientation
o
Separate image for slider and knob
o
Allow non-pixmap sliders. Use QSS for styling.
*
Drop-down Chooser
o
Allow styling via QSS.
o
No pixmap option, as it's text-only.
o
Requires Control 2.0, since if you connect it to a text control it must know what values it may take on.
*
Knobs
o
Single knob image that is rotated plus background image.
o
Allow specification of 'translation' function (i.e. log-potmeter or potmeter)
o
Allow non-pixmap knobs. Use QSS for styling.
*
Library Widget
o
Still a monolithic widget. Don't think it adds value to allow much customization here.
o
Use QSS for all appearance styling.
*
Text labels
o
Make use of Controls to display text instead of hard-coding text.
o
Potentially allow scripts to dynamically affect what is shown.
o
Allow Marquee effect so you can read text that goes out of the control.
*
VU Meter
o
Allow QSS styling (how???) or pixmaps.
*
Status light
o
Connects to a control and dynamically switches its pixmap or QSS property based on the control's value
*
Sampler Widget
o
Requirements unknown.
*
Effects Widget
o
Requirements unknown.
o
Potentially with a much better control system we can support neat things

Skinning Engine Proposals

Given the above requirements, list various proposals for skin formats here:

*
Qt4, Qt Style Sheet-based approach
*
Qt 4.7 QML/Kinetic-based approach
*
HTML/CSS Based Skins

The current ideas are:
Qt 4 based Skinning Engine

Qt 4 is the cross-platform framework.

For the creation of a skinning system, Qt supports many things: layouts, style sheets, vector graphics, raster/OpenVG/OpenGL rendering, useful low-level painting system, XML, animation framework (since 4.6 or as official add-on), declarative UI technology (since 4.6)…

By combining some of these technologies it should be possible to create an advanced skinning engine for LMCE.
To investigate

*
Explore the Declarative UI Technology in Qt 4.6 to see if it can help in creating a skinning engine.
o
It looks very promising: http://labs.trolltech.com/blogs/category/labs/graphics/kinetic/declarative_ui/
*
Explore QWidget versus QGraphicsView for layout.
o
How does the performance stack up?
o
QWidgets can be rendered in a QGV, but how does this affect performance?
+
But when the visualization is rendered in OpenGL, we'll probably have to render the whole QGV in OpenGL
o
QGV will give us a really cool and flexible UI in combination with the Animation/DUI framework
o
QGV will give us fast software-based UI rendering, as well as support for rendering the UI through OpenGL and since Qt 4.6 also OpenVG
*
Explore if and how style sheets can help
o
Style sheets are very useful to skin stuff like scrollbars and other default widgets
o
The more important stuff like buttons should probably be skinned by reimplementing paintEvent, because this gives more possibilities
+
Style sheets may be slower than reimplementing paintEvent - although it has to be investigated to be sure
+
More advanced animations (besides simple hover/overroll effects) cannot be created with style sheets only

Pro

*
Support pixmap skins (porting of current skins will be easier this way, and performance will probably be higher than using SVG)
*
Support SVG skins (for those who want, SVG skins should be an option as well
o
Performance may be lower, but we could optionally render SVG as pixmaps to improve performance
*
Possibility to implement a layout system (because interface elements should not stretch)
*
The window itself should be themable/deformable too. Could be achieved by either composite or with a mask (or both)

2010-09-03T23:04:51Z

Mandingo: /* '''ATSC/NTSC Cards (only in US/Canada )''' '''[http://www.mythtv.org/ MythTV]''' */

[[Category:Hardware]]
[[Category:TV Cards]]
{{versioninfo|810Status=Plug N Play|810UpdatedDate=5th May 2010|810UpdatedBy=[[User:Langstonius|Langstonius]]|710Status=apt-get install v4l2-modules and v4l2-firmware, then install card|710UpdatedDate=5th May 2010|710UpdatedBy=[[User:Langstonius|Langstonius]]}}
'''Video Capture Cards/Devices''' are used to get the picture from the cable, aerial, or satellite television source into the PC. They decode and capture the video signal from the channel you want to view or record. Most cards/devices include a tuner to capture an specific TV signal. Video capture cards/devices without tuners do exist, but these are used for mainly security DVR's.

==Current Plug and Play Capture Cards/Devices with LinuxMCE==
Below you will find a running list of Capture Devices that are now Plug and Play with LinuxMCE.
I will add more Cards/Devices as time progresses so if you have a Card/Device that is not listed, Please post your card information here. [http://forum.linuxmce.org/index.php?topic=9354.0 Forum]

Anyone within the USA or CANADA please select and use [http://www.mythtv.org/ MythTV] as your default TV application.

Thanks

Mandingo

== '''RATING SCALE''' ==
'''*''' = '''''WORST''''' Picture/Sound '''DON'T RECOMMEND'''
'''**''' = '''''OK''''' Picture/Sound '''RECOMMEND'''
'''***''' = '''''GOOD''''' Picture/Sound '''RECOMMEND'''
'''****''' = '''''VERY GOOD''''' Picture/Sound '''RECOMMEND'''
'''*****''' = '''''BEST''''' Picture/Sound '''HIGHLY RECOMMEND'''

== '''ATSC/NTSC Cards (only in US/Canada )''' '''[http://www.mythtv.org/ MythTV]''' ==
----------------------------------------------------------------------------------------
'''MANUFACTURE''' '''MODEL''' '''SIGNAL''' '''INTERFACE''' '''RATING'''
----------------------------------------------------------------------------------------
''ATI'' [http://ati.amd.com/products/tvwonderve/gallery.html TV-Wonder VE] NTSC PCI '''*'''
----------------------------------------------------------------------------------------
''DVICO'' [http://www.fusionhdtv.co.kr/eng/Products/RTGold.aspx FusionHDTV5 RT Gold] ATSC/NTSC PCI
[http://www.fusionhdtv.co.kr/eng/Products/RTLite.aspx FusionHDTV5 RT Lite] ATSC/NTSC PCI
----------------------------------------------------------------------------------------
''HAUPPAUGE'' [http://haupauge.com/site/products/data_hdpvr.html HD-PVR] NTSC/PAL/SECAM USB 2.0 '''*****'''
[http://haupauge.com/site/products/data_pvrusb2.html WinTV-PVR-USB2] NTSC USB 2.0 '''**'''
[http://haupauge.com/site/products/data_pvr150.html WinTV-PVR-150] NTSC PCI '''**'''
[http://haupauge.com/site/products/data_pvr250.html WinTV-PVR-250] NTSC PCI '''**'''
[http://www.hauppauge.com/site/products/data_pvr500mckit.html WinTV-PVR-500] NTSC PCI '''**'''
[http://haupauge.com/site/products/data_hvr850.html WinTV-HVR-850] ATSC USB 2.0
[http://haupauge.com/site/products/data_hvr950.html WinTV-HVR-950] ATSC USB 2.0
[http://haupauge.com/site/products/data_hvr950Q.html WinTV-HVR-950Q] ATSC USB 2.0
[http://haupauge.com/site/products/data_hvr1150.html WinTV-PVR-1150] ATSC/NTSC PCI
[http://haupauge.com/site/products/data_hvr1250.html WinTV-HVR-1250] ATSC PCIe
[http://haupauge.com/site/products/data_hvr1600.html WinTV-HVR-1600] ATSC/NTSC PCI
[http://haupauge.com/site/products/data_hvr1500.html WinTV-HVR-1500] ATSC ExpressCard
[http://haupauge.com/site/products/data_hvr1800.html WinTV-HVR-1800] ATSC/NTSC PCIe
[http://haupauge.com/site/products/data_hvr1800MC.html WinTV-HVR-1800 MCE] ATSC/NTSC PCIe
[http://haupauge.com/site/products/data_hvr1850.html WinTV-HVR-1850] ATSC/NTSC PCIe
[http://haupauge.com/site/products/data_hvr1950.html WinTV-HVR-1950] ATSC/NTSC USB 2.0
[http://haupauge.com/site/products/data_hvr2250.html WinTV-HVR-2250] ATSC PCIe
----------------------------------------------------------------------------------------
''PCHDTV'' [http://www.pchdtv.com/hd_2000.html HD-2000] ATSC PCI '''**'''
[http://www.pchdtv.com/hd_3000.html HD-3000] ATSC PCI '''****'''
[http://www.pchdtv.com/hd_5500.html HD-5500] ATSC PCI '''*****'''
----------------------------------------------------------------------------------------
''SILICONDUST'' [http://www.silicondust.com/products/hdhomerun_home_atsc HDHomeRun] ATSC Ethernet '''*****'''
----------------------------------------------------------------------------------------
----

== '''DVB-C Cards (Cable viewing)''' '''[http://www.tvdr.de/ VDR] or [http://www.mythtv.org/ MythTV]''' ==
----------------------------------------------------------------------------------------
'''MANUFACTURE''' '''MODEL''' '''SIGNAL''' '''INTERFACE''' '''RATING'''
----------------------------------------------------------------------------------------
''TECHNISAT'' [http://www.technisat.co.uk/index86cc.html?nav=PC_products,co,76-211 CableStar HD 2] DVB-C PCI
----------------------------------------------------------------------------------------
''TECHNOTREND'' [http://www.tt-pc.com/2917/TT-budget__C-1501.html TT-Budget C-1501] DVB-C PCI
[http://www.tt-pc.com/2916/TT-connect__CT-3650_CI.html TT-Connect CT-3650 CI]DVB-C/DVB-T USB 2.0
[http://www.tt-pc.com/2765/TT-premium__S-2300.html TT-Premium C-2300] DVB-C PCI
----------------------------------------------------------------------------------------
----

== '''DVB-S Cards (Satellite viewing)''' '''[http://www.tvdr.de/ VDR] or [http://www.mythtv.org/ MythTV]''' ==
----------------------------------------------------------------------------------------
'''MANUFACTURE''' '''MODEL''' '''SIGNAL''' '''INTERFACE''' '''RATING'''
----------------------------------------------------------------------------------------
''HAUPPAUGE'' WinTV-NOVA-S DVB-S PCI
WinTV-NOVA-S SE DVB-S PCI
[http://www.hauppauge.co.uk/site/products/data_novasplus.html WinTV-NOVA-S-Plus] DVB-S PCI
WinTV-NOVA-S USB DVB-S USB 1.1
[http://www.hauppauge.co.uk/site/products/data_novasusb2.html WinTV-NOVA-S-USB2] DVB-S USB 2.0
WinTV-NOVA-SE2 DVB-S/DVB-S2 PCI
WinTV-NOVA-CI DVB-S PCI
WinTV-NEXUS-S Rev. 2.1 DVB-S PCI
WinTV-NEXUS-S Rev. 2.2 DVB-S PCI
WinTV-NEXUS-S Rev. 2.3 DVB-S PCI
----------------------------------------------------------------------------------------
''TECHNISAT'' [http://www.technisat.co.uk/index540f.html?nav=PC_products,co,76-174 SkyStar 2 TV] DVB-S PCI
----------------------------------------------------------------------------------------
''TECHNOTREND'' [http://www.tt-pc.com/2701/TT-budget__S-1401.html TT-Budget S-1401] DVB-S PCI
[http://www.tt-pc.com/2763/TT-budget__S-1500.html TT-Budget S-1500] DVB-S PCI
[http://www.tt-pc.com/2920/TT-budget__S2-1600.html TT-Budget S2-1600] DVB-S PCI
[http://www.tt-pc.com/2764/TT-budget__S2-3200.html TT-Budget S2-3200] DVB-S PCI
[http://www.tt-pc.com/2778/TT-connect__S-2400.html TT-Connect S-2400] DVB-S USB 2.0
[http://www.tt-pc.com/2779/TT-connect__S2-3600.html TT-Connect S2-3600] DVB-S USB 2.0
[http://www.tt-pc.com/2780/TT-connect__S2-3650_CI.html TT-Connect S2-3650 CI]DVB-S PCI
[http://www.tt-pc.com/2765/TT-premium__S-2300.html TT-Premium S-2300] DVB-S PCI
----------------------------------------------------------------------------------------
----

== '''DVB-T Cards (Terrestrial viewing)''' '''[http://www.tvdr.de/ VDR] or [http://www.mythtv.org/ MythTV]''' ==
----------------------------------------------------------------------------------------
'''MANUFACTURE''' '''MODEL''' '''SIGNAL''' '''INTERFACE''' '''RATING'''
----------------------------------------------------------------------------------------
''LEADTEK'' [http://www.leadtek.com/eng/tv_tuner/overview.asp?lineid=6&pronameid=220 WinFast DTV1000 T] DVB-T PCI
----------------------------------------------------------------------------------------
''TERRATEC'' Cinergy DT XS Diversity DVB-T USB 2.0 Stick
----------------------------------------------------------------------------------------
''HAUPPAUGE'' [http://www.hauppauge.co.uk/site/products/data_hvr900.html WinTV-HVR-900] DVB-T USB 2.0 Stick
WinTV-HVR-900H DVB-T USB 2.0 Stick
WinTV-HVR-930 DVB-T USB 2.0 Stick
[http://www.hauppauge.co.uk/site/products/data_hvr2200mc.html WinTV-HVR-2200] DVB-T PCIe
[http://www.hauppauge.co.uk/site/products/data_hvr1100.html WinTV-HVR-1100] DVB-T PCI
WinTV-HVR-1110 DVB-T PCI
WinTV-HVR-1120 DVB-T PCI
[http://www.hauppauge.co.uk/site/products/data_hvr1200mckit.html WinTV-HVR-1200] DVB-T PCIe
[http://www.hauppauge.co.uk/site/products/data_hvr1300.html WinTV-HVR-1300] DVB-T PCI
[http://www.hauppauge.co.uk/site/products/data_hvr1700mckit.html WinTV-HVR-1700] DVB-T PCIe
[http://www.hauppauge.co.uk/site/products/data_hvr3000.html WinTV-HVR-3000] DVB-T/DVB-S PCI '''*****'''
[http://www.hauppauge.co.uk/site/products/data_hvr4000.html WinTV-HVR-4000] DVB-T/DVB-S/DVB-S2 PCI '''*****'''
[http://www.hauppauge.co.uk/site/products/data_novatpci.html WinTV-NOVA-T] DVB-T PCI
WinTV-NOVA-T-500 DVB-T PCI
WinTV-NOVA-T USB DVB-T USB 1.1
WinTV-NOVA-T-USB2 DVB-T USB 2.0
[http://www.hauppauge.co.uk/site/products/data_novatstick.html WinTV-NOVA-T-Stick] DVB-T USB 2.0 Stick
WinTV-NOVA-T-CE-Stick DVB-T USB 2.0 Stick
[http://www.hauppauge.co.uk/site/products/data_novatdstick.html WinTV-NOVA-TD-Stick] DVB-T USB 2.0 Stick
[http://www.hauppauge.co.uk/site/products/data_novat500.html WinTV-NOVA-TD-500] DVB-T PCI
----------------------------------------------------------------------------------------
''TECHNOTREND'' [http://www.tt-pc.com/2783/TT-budget__T-1500.html TT-Budget T-1500] DVB-T PCI
[http://www.tt-pc.com/2784/TT-budget__T-3000.html TT-Budget T-3000] DVB-T PCI
----------------------------------------------------------------------------------------

2010-03-24T08:46:50Z

Mandingo: /* Update 2010-03-23 22876 in progress */

LinuxMCE-0810 beta

2010-02-28T18:43:26Z

Mandingo:

2010-01-31T01:36:41Z

Mandingo: /* '''ATSC/NTSC Cards (only in US/Canada )''' '''MythTV''' */

'''Video Capture Cards/Devices''' are used to get the picture from the cable, aerial, or satellite television source into the PC. They decode and capture the video signal from the channel you want to view or record. Most cards/devices include a tuner to capture an specific TV signal. Video capture cards/devices without tuners do exist, but these are used for mainly security DVR's.

==Current Plug and Play Capture Cards/Devices with LinuxMCE==
Below you will find a running list of Capture Devices that are now Plug and Play with LinuxMCE.
I will add more Cards/Devices as time progresses so if you have a Card/Device that is not listed, Please post your card information here. [http://forum.linuxmce.org/index.php?topic=9354.0 Forum]

Anyone within the USA or CANADA please select and use MythTV as your default TV application, outside of these two countries please use VDR

Thanks

Mandingo

== '''ATSC/NTSC Cards (only in US/Canada )''' '''[http://www.mythtv.org/ MythTV]''' ==
---------------------------------------------------------------------
'''MANUFACTURE''' '''MODEL''' '''SIGNAL''' '''INTERFACE'''
---------------------------------------------------------------------
---------------------------------------------------------------------
''ATI'' [http://ati.amd.com/products/tvwonderve/gallery.html TV-Wonder VE] NTSC PCI
---------------------------------------------------------------------
''DVICO'' [http://www.fusionhdtv.co.kr/eng/Products/RTGold.aspx FusionHDTV5 RT Gold] ATSC/NTSC PCI
[http://www.fusionhdtv.co.kr/eng/Products/RTLite.aspx FusionHDTV5 RT Lite] ATSC/NTSC PCI
---------------------------------------------------------------------
''HAUPPAUGE'' [http://haupauge.com/site/products/data_hdpvr.html HD-PVR] ATSC/NTSC USB 2.0
[http://haupauge.com/site/products/data_pvrusb2.html WinTV-PVR-USB2] NTSC USB 2.0
[http://haupauge.com/site/products/data_pvr150.html WinTV-PVR-150] NTSC PCI
[http://haupauge.com/site/products/data_pvr250.html WinTV-PVR-250] NTSC PCI
[http://www.hauppauge.com/site/products/data_pvr500mckit.html WinTV-PVR-500] NTSC PCI
[http://haupauge.com/site/products/data_hvr850.html WinTV-HVR-850] ATSC USB 2.0
[http://haupauge.com/site/products/data_hvr950.html WinTV-HVR-950] ATSC USB 2.0
[http://haupauge.com/site/products/data_hvr950Q.html WinTV-HVR-950Q] ATSC USB 2.0
[http://haupauge.com/site/products/data_hvr1150.html WinTV-PVR-1150] ATSC/NTSC PCI
[http://haupauge.com/site/products/data_hvr1250.html WinTV-HVR-1250] ATSC PCIe
[http://haupauge.com/site/products/data_hvr1600.html WinTV-HVR-1600] ATSC/NTSC PCI
[http://haupauge.com/site/products/data_hvr1500.html WinTV-HVR-1500] ATSC ExpressCard
[http://haupauge.com/site/products/data_hvr1800.html WinTV-HVR-1800] ATSC/NTSC PCIe
[http://haupauge.com/site/products/data_hvr1800MC.html WinTV-HVR-1800 MCE] ATSC/NTSC PCIe
[http://haupauge.com/site/products/data_hvr1850.html WinTV-HVR-1850] ATSC/NTSC PCIe
[http://haupauge.com/site/products/data_hvr1950.html WinTV-HVR-1950] ATSC/NTSC USB 2.0
[http://haupauge.com/site/products/data_hvr2250.html WinTV-HVR-2250] ATSC PCIe
---------------------------------------------------------------------
''PCHDTV'' [http://www.pchdtv.com/hd_2000.html HD-2000] ATSC PCI
[http://www.pchdtv.com/hd_3000.html HD-3000] ATSC PCI
[http://www.pchdtv.com/hd_5500.html HD-5500] ATSC PCI
---------------------------------------------------------------------
''SILICONDUST'' [http://www.silicondust.com/products/hdhomerun_home_atsc HDHomeRun] ATSC Eithernet
---------------------------------------------------------------------
----

== '''DVB-C Cards (Cable viewing)''' '''VDR''' ==
---------------------------------------------------------------------
'''MANUFACTURE''' '''MODEL''' '''SIGNAL''' '''INTERFACE'''
---------------------------------------------------------------------
''HAUPPAUGE'' WinTV-NOVA-C DVB-C PCI
---------------------------------------------------------------------
''TECHNISAT'' CableStar HD 2 DVB-C PCI
---------------------------------------------------------------------
''TECHNOTREND'' TT-Budget C-1501 DVB-C PCI
TT-Connect CT-3650 CI DVB-C/DVB-T USB 2.0
TT-Premium C-2300 DVB-C PCI
---------------------------------------------------------------------
----

== '''DVB-S Cards (Satellite viewing)''' '''VDR''' ==
---------------------------------------------------------------------
'''MANUFACTURE''' '''MODEL''' '''SIGNAL''' '''INTERFACE'''
---------------------------------------------------------------------
''HAUPPAUGE'' WinTV-NOVA-S DVB-S PCI
WinTV-NOVA-S SE DVB-S PCI
WinTV-NOVA-S-Plus DVB-S PCI
WinTV-NOVA-S USB DVB-S USB 1.1
WinTV-NOVA-S-USB2 DVB-S USB 2.0
WinTV-NOVA-SE2 DVB-S/DVB-S2 PCI
WinTV-NOVA-CI DVB-S PCI
WinTV-NEXUS-S Rev. 2.1 DVB-S PCI
WinTV-NEXUS-S Rev. 2.2 DVB-S PCI
WinTV-NEXUS-S Rev. 2.3 DVB-S PCI
---------------------------------------------------------------------
''TECHNISAT'' SkyStar 2 TV DVB-S PCI
---------------------------------------------------------------------
''TECHNOTREND'' TT-Budget S-1401 DVB-S PCI
TT-Budget S-1500 DVB-S PCI
TT-Budget S2-1600 DVB-S PCI
TT-Budget S2-3200 DVB-S PCI
TT-Connect S-2400 DVB-S USB 2.0
TT-Connect S2-3600 DVB-S USB 2.0
TT-Connect S2-3650 CI DVB-S PCI
TT-Premium S-2300 DVB-S PCI
---------------------------------------------------------------------
----

== '''DVB-T Cards (Terrestrial viewing)''' '''VDR''' ==
---------------------------------------------------------------------
'''MANUFACTURE''' '''MODEL''' '''SIGNAL''' '''INTERFACE'''
---------------------------------------------------------------------
''LEADTEK'' WinFast DTV1000 T DVB-T PCI
---------------------------------------------------------------------
''TERRATEC'' Cinergy DT XS Diversity DVB-T USB 2.0 Stick
---------------------------------------------------------------------
''HAUPPAUGE'' WinTV-HVR-900 DVB-T USB 2.0 Stick
WinTV-HVR-900H DVB-T USB 2.0 Stick
WinTV-HVR-930 DVB-T USB 2.0 Stick
WinTV-HVR-2200 DVB-T PCIe
WinTV-HVR-1100 DVB-T PCI
WinTV-HVR-1110 DVB-T PCI
WinTV-HVR-1120 DVB-T PCI
WinTV-HVR-1200 DVB-T PCIe
WinTV-HVR-1300 DVB-T PCI
WinTV-HVR-1700 DVB-T PCIe
WinTV-HVR-3000 DVB-T/DVB-S PCI
WinTV-HVR-4000 DVB-T/DVB-S/DVB-S2 PCI
WinTV-NOVA-T DVB-T PCI
WinTV-NOVA-T-500 DVB-T PCI
WinTV-NOVA-T USB DVB-T USB 1.1
WinTV-NOVA-T-USB2 DVB-T USB 2.0
WinTV-NOVA-T-Stick DVB-T USB 2.0 Stick
WinTV-NOVA-T-CE-Stick DVB-T USB 2.0 Stick
WinTV-NOVA-TD-Stick DVB-T USB 2.0 Stick
WinTV-NOVA-TD-500 DVB-T PCI
---------------------------------------------------------------------
''TECHNOTREND'' TT-Budget T-1500 DVB-T PCI
TT-Budget T-3000 DVB-T PCI
---------------------------------------------------------------------

Capture Cards

2010-01-31T00:50:46Z

Mandingo: /* '''ATSC/NTSC Cards (only in US/Canada )''' '''MythTV''' */

Capture Cards

2010-01-31T00:33:07Z

Mandingo: /* Current Plug and Play Capture Cards/Devices with LinuxMCE */