https://www.linuxtv.org/vdrwiki/api.php?action=feedcontributions&user=Dude&feedformat=atomVDR Wiki - User contributions [en]2024-03-28T23:49:03ZUser contributionsMediaWiki 1.39.6https://www.linuxtv.org/vdrwiki/index.php?title=Remote_control&diff=2584Remote control2005-10-24T17:19:37Z<p>Dude: </p>
<hr />
<div>One of the most important items for [[VDR]] is the remote control. No one really wants to control his TV set with a cable bound computer keyboard.<br />
<br />
One can distinguish between radio and infrared remote controls.<br />
<br />
radio remote controls<br />
* ATI USB Remote Wonder (works under [[LIRC]])<br />
<br />
Infrared remote controls<br />
* MD6461|Tevion / Medion MD6461 und MD46XX<br />
<br />
{| border=0 cellpadding=2 cellspacing=0<br />
| [[Image:remote control(Hauppauge nova-t).jpg|thumb|50px|''RC of Nova-T'']]<br />
| [[Image:remote control(Hauppauge black).jpg|thumb|50px|''RC of old Nexus'']]<br />
| [[Image:remote control(URC-7040).jpg|thumb|50px|''One-for-All 7040'']]<br />
|}<br />
<br />
nearly every codes of IR remote controls can be leared with ''irrecord'' for [[LIRC]]. Configuration file for many of them can be downloaded from the LIRC homepage. One exception is the IR input for Hauppauge DVB-s cards with IR input. Communication for these is accomplished directly using the<br />
linux DVB driver and vdr, after initialization with the <b>av7110_loadkeys</b> utility application. <br />
<br />
To use ac7110_loadkeys you need an rc5 initialization file (supplied with the application) and then you run<br />
<br><code>av7110_loadkeys hauppauge_grey.rc5 &gt; /proc/av7110_ir</code> <br><br />
to initialize the IR driver.<br />
<br />
<br />
==Links==<br />
{|<br />
| [1]<br />
| [http://home.swiftdsl.com.au/~tmccoy/index.php?option=content&task=view&id=11&Itemid=26 http://home.swiftdsl.com.au/~tmccoy]<br />
| Construction manual for a infrared receiver<br />
|-<br />
| [3]<br />
| http://www.lirc.org<br />
| LIRC homepage<br />
|}<br />
<br />
[[Category:Hardware]]<br />
<br />
<!-- Link to the german VDR Wiki --><br />
[[de:Fernbedienung]]</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=Remote_control&diff=1305Remote control2005-10-24T17:19:10Z<p>Dude: </p>
<hr />
<div>One of the most important items for [[VDR]] is the remote control. No one really wants to control his TV set with a cable bound computer keyboard.<br />
<br />
One can distinguish between radio and infrared remote controls.<br />
<br />
radio remote controls<br />
* ATI USB Remote Wonder (works under [[LIRC]])<br />
<br />
Infrared remote controls<br />
* MD6461|Tevion / Medion MD6461 und MD46XX<br />
<br />
{| border=0 cellpadding=2 cellspacing=0<br />
| [[Image:remote control(Hauppauge nova-t).jpg|thumb|50px|''RC of Nova-T'']]<br />
| [[Image:remote control(Hauppauge black).jpg|thumb|50px|''RC of old Nexus'']]<br />
| [[Image:remote control(URC-7040).jpg|thumb|50px|''One-for-All 7040'']]<br />
|}<br />
<br />
nearly every codes of IR remote controls can be leared with ''irrecord'' for [[LIRC]]. Configuration file for many of them can be downloaded from the LIRC homepage. One exception is the IR input for Hauppauge DVB-s cards with IR input. Communication for these is accomplished directly using the<br />
linux DVB driver and vdr, after initialization with the <b>av7110_loadkeys</b> utility application. <br />
<br />
To use ac7110_loadkeys you need an rc5 initialization file (supplied with the application) and then you run<br />
<br><code>av7110_loadkeys hauppauge_grey.rc5 &gt; /proc/av7110_ir</code> to initialize the IR driver.<br />
<br />
<br />
==Links==<br />
{|<br />
| [1]<br />
| [http://home.swiftdsl.com.au/~tmccoy/index.php?option=content&task=view&id=11&Itemid=26 http://home.swiftdsl.com.au/~tmccoy]<br />
| Construction manual for a infrared receiver<br />
|-<br />
| [3]<br />
| http://www.lirc.org<br />
| LIRC homepage<br />
|}<br />
<br />
[[Category:Hardware]]<br />
<br />
<!-- Link to the german VDR Wiki --><br />
[[de:Fernbedienung]]</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=Remote_control&diff=1304Remote control2005-10-24T17:18:34Z<p>Dude: </p>
<hr />
<div>One of the most important items for [[VDR]] is the remote control. No one really wants to control his TV set with a cable bound computer keyboard.<br />
<br />
One can distinguish between radio and infrared remote controls.<br />
<br />
radio remote controls<br />
* ATI USB Remote Wonder (works under [[LIRC]])<br />
<br />
Infrared remote controls<br />
* MD6461|Tevion / Medion MD6461 und MD46XX<br />
<br />
{| border=0 cellpadding=2 cellspacing=0<br />
| [[Image:remote control(Hauppauge nova-t).jpg|thumb|50px|''RC of Nova-T'']]<br />
| [[Image:remote control(Hauppauge black).jpg|thumb|50px|''RC of old Nexus'']]<br />
| [[Image:remote control(URC-7040).jpg|thumb|50px|''One-for-All 7040'']]<br />
|}<br />
<br />
nearly every codes of IR remote controls can be leared with ''irrecord'' for [[LIRC]]. Configuration file for many of them can be downloaded from the LIRC homepage. One exception is the IR input for Hauppauge DVB-s cards with IR input. Communication for these is accomplished directly using the<br />
linux DVB driver and vdr, after initialization with the <b>av7110_loadkeys</b> utility application. <br />
<br />
To ac7110_loadkeys you need an rc5 initialization file (supplied with the application) and then you run<br />
<br><b>av7110_loadkeys hauppauge_grey.rc5 &gt; /proc/av7110_ir</b> to initialize the IR driver.<br />
<br />
<br />
==Links==<br />
{|<br />
| [1]<br />
| [http://home.swiftdsl.com.au/~tmccoy/index.php?option=content&task=view&id=11&Itemid=26 http://home.swiftdsl.com.au/~tmccoy]<br />
| Construction manual for a infrared receiver<br />
|-<br />
| [3]<br />
| http://www.lirc.org<br />
| LIRC homepage<br />
|}<br />
<br />
[[Category:Hardware]]<br />
<br />
<!-- Link to the german VDR Wiki --><br />
[[de:Fernbedienung]]</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=Sat_antenna&diff=2726Sat antenna2005-10-23T19:20:32Z<p>Dude: </p>
<hr />
<div>The Sat antenna you use it totally dependent on the kind of sat card you have. Almost all DVB cards can be used with a generic sat dish of as little as 12" diameter, if all you want to aim at is a single sat at a time. An 18" "elliptical" disk can be used to pick up multiple sats's without re-aiming. Several DVB cards also support driving a pointing motor to allow the dish to be mechanically steered to different sats.<br />
<br />
A related issue is the LNB, the electronic device that takes the concentrated microwave signal from the dish and sends it down the wire as an electrical signal. Multiple LNB's can be used if you use a DisEqC box to switch between them; this kind of switch is directly supported by many DVB cards without any extra wiring.<br />
vdr supports the management of multiple LNB's (and this multiple dishes) via DisEqC.</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=VDR_Wiki:Suggestions_for_improvement&diff=2728VDR Wiki:Suggestions for improvement2005-10-21T21:56:12Z<p>Dude: </p>
<hr />
<div>I would love to see a section for VDR developers and hackers. Since the VDR code seems to be<br />
mostly devoit of comments, a roadmap to the main classes and hope they interact would be very useful.<br />
For example, what is the relationship between EPG scanning (implemented in eitscan and the Set commands use for filtering)?<br />
<br />
:You can construct such a documentation with doxygen or have a look at http://vdr.computer-wiki.de/doxygen/vdrdoxy-1.3.31/ (German) and http://vdr.computer-wiki.de/doxygen/ <br>[[User:Wirbel|Wirbel]] 20:41, 21 Oct 2005 (CEST)<br />
<br />
<br />
doxygen is a really cool tool, but it's not really the same as<br />
genuine human-written documentation. There are lots of nice tidbits and<br />
knowledge for VDR developers hidden all over the web, <br />
but it's quite hard to find and quite incomplete.<br />
<br>[[User:Dude]] 21:41, 21 Oct 2005 (CEST)</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=VDR_Wiki_talk:Suggestions_for_improvement&diff=2727VDR Wiki talk:Suggestions for improvement2005-10-21T21:55:20Z<p>Dude: </p>
<hr />
<div></div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=VDR_Wiki_talk:Suggestions_for_improvement&diff=1287VDR Wiki talk:Suggestions for improvement2005-10-21T21:54:54Z<p>Dude: </p>
<hr />
<div>doxygen is a really cool tool, but it's not really the same as<br />
genuine human-written documentation. There are lots of nice tidbits and<br />
knowledge for VDR developers hidden all over the web, <br />
but it's quite hard to find and quite incomplete.</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=VDR_Wiki:Suggestions_for_improvement&diff=1285VDR Wiki:Suggestions for improvement2005-10-21T18:18:24Z<p>Dude: </p>
<hr />
<div><br />
I would love to see a section for VDR developers and hackers. Since the VDR code seems to be<br />
mostly devoit of comments, a roadmap to the main classes and hope they interact would be very useful.<br />
For example, what is the relationship between EPG scanning (implemented in eitscan and the Set commands use for filtering)?</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=Syntax_of_channels.conf&diff=1286Syntax of channels.conf2005-10-21T18:05:00Z<p>Dude: /* Parameters of VDR channel config file */</p>
<hr />
<div>==Parameters of VDR channel config file==<br />
Note that older versions of VDR (e.g 1.2.x) use a slightly different format of this file, and switching between vdr 1.2.x and vdr 1.3.x with the same channel file can lead to problems, see below under Differences (this caused me a lot of grief). This document is for VDR version 1.3.x.<br />
<br />
In the example below there are three different channel definitions: <br />
* digital satellite TV channel<br />
* digital terrestrian TV channel<br />
* digital cable TV channel<br />
* analog TV channel<br />
{| border=1 cellpadding=5 cellspacing=0<br />
|- bgcolor=#efdead<br />
![[#Name|Name]]<br />
![[#Frequenz|Frequenz]]<br />
![[#Parameter|Parameter]]<br />
![[#Quelle|Quelle]]<br />
![[#SRate|SRate]]<br />
![[#VPID|VPID]]<br />
![[#APID|APID]]<br />
![[#TPID|TPID]]<br />
![[#CA|CA]]<br />
![[#SID|SID]]<br />
![[#NID|NID]]<br />
![[#TID|TID]]<br />
![[#RID|RID]]<br />
|-<br />
| RTL || 12188 || h || S19.2E || 27500 || 163 || 104 || 105 || 0 || 12003 || 0 || 0 || 0<br />
|-<br />
| Das Erste || 522000 || I0C23D0M16B8T8G8Y0 || T || 27500 || 1401 || 1402 || 1404 || 1 || 14 || 0 || 0 || 0<br />
|-<br />
| FS HH || 402000 || C0M64 || C || 6900 || 2401 || 2402 || 2404 || 0 || 28225 || 1 || 1073 || 16387<br />
|-<br />
| VHF K10 || 210250 || C0D45B6 || C || 0 || 301 || 300 || 0 || A0 || 28106 || 0 || 0 || 0<br />
|}<br />
The [[VDR]] reads at startup all channel definitions from the config file '''$CONFIGDIR/vdr/channels.conf''' and writes any changing back to the file.<br />
{{Box Hint|<br />
Changings on channels.conf are useless if VDR is running, VDR has to be stopped if you want to edit this file!<br />
}}<br />
<br />
===Name===<br />
Name of that channel. If the name includes a ":" it will be automatically replaced by "|".<br />
If you use VDR version 1.2.x please do NOT include commas or semicolons. Starting with VDR version 1.3.12 this field also includes the service providers name(aka "bouquet"), separated by a semikolon.<br />
<br />
===Frequency===<br />
Transponder Frequency as Integer<br />
;DVB-S : Frequency in MHz.<br />
;DVB-C : Frequency in MHz, kHz or Hz.<br />
;DVB-T : Frequency in MHz, kHz or Hz.<br />
;analogue TV : Frequency in MHz. (analogTV plugin)<br />
The values here will be multiplied by 1000 until it's bigger than 1000000.<br />
<br />
<br />
===Parameters===<br />
The Parameters in this field depends on the type of DVB you use: [[DVB-S]], [[DVB-C]] ,[[DVB-T]] or analogue TV.<br />
Each Parameter starts with an letter, followed by an Integer which represends the value of that parameter. <br />
<br />
Valid identifiers and their ranges:<br />
<br />
'''Identifier (Values) Meaning'''<br />
<br />
'''I''' (0, 1) Inversion (for DVB-T always 0, please do NOT use 999)<br />
<br />
'''C''' (0, 12, 23, 34, 45, 56, 67, 78, 89) Data rate high priority<br />
for analogue TV is C the capture device:<br />
C0 = /dev/video0<br />
C12 = /dev/video1<br />
C23 = /dev/video2<br />
C34 = /dev/video3<br />
C45 = /dev/video4<br />
<br />
'''D''' (0, 12, 23, 34, 45, 56, 67, 78, 89) Data rate low priority<br />
for analogue TV is D the video source used:<br />
D0 = Television (bttv)<br />
D12 = Composite Video1 (bttv)<br />
D23 = Composite Video2 (bttv)<br />
D34 = S-Video (bttv)<br />
D0 = S-Video ext. (Hauppauge PVR150/PVR250/350-cards only)<br />
D45 = Composite Video (Hauppauge PVR150-cards only)<br />
D45 = Tuner 0 (Hauppauge PVR250/350-cards only)<br />
D56 = Composite ext. (Hauppauge PVR250/350-cards only)<br />
D67 = TV Tuner (Hauppauge PVR150-Karten only)<br />
<br />
'''M''' (0, 16, 32, 64, 128, 256) Modulation<br />
<br />
'''B''' (6, 7, 8) Bandwidth in MHz<br />
for analogue TV is B the Video norm:<br />
B6 = PAL<br />
B7 = NTSC<br />
B8 = SECAM </pre><br />
<br />
'''T''' (2, 8) Transmission mode<br />
<br />
'''G''' (4, 8, 16, 32) Guard intervall<br />
<br />
'''Y''' (0, 1, 2, 4) Hierarchy<br />
<br />
'''H''' Horizontal Polarization<br />
<br />
'''V''' Vertical Polarization<br />
<br />
'''R''' Circular Polarization right<br />
<br />
'''L''' Circular Polarization left<br />
<br />
The Polarisation Parameter is NOT followed by an value for compatibility reasons.<br />
<br />
The value ''999'' is used for automatic. If possible the driver will find the best settings, this is default.<br />
<br />
Example for DVB-T:<br />
<br />
'''I'''0'''C'''23'''D'''0'''M'''16'''B'''8'''T'''8'''G'''8'''Y'''0<br />
Inversion off,<br />
Data Rate High=23,<br />
Data Rate Low=0,<br />
QAM16,<br />
Bandwidth 8MHz,<br />
Transmission Mode 8,<br />
Guard 1/8,<br />
Hierarchy 0<br />
<br />
===Source===<br />
Signal source of the channel, as defined in [[sources.conf]].<br />
Sxxxx, C, T<br />
<br />
For compatbility reasons numeric values are accepted here, but preferred are literals.<br />
<br />
===Symbol Rate===<br />
Symbol Rate of the channel. Valid only for DVB-S and DVB-C, as DVB-T uses another modulation COFDM (Coded Orthogonal Frequency Division Multiplex).<br />
<br />
===VPID===<br />
Video PID (Program Identification).<br />
* 0 for Radio channels<br />
* 1 for encryted channels (pay tv)<br />
If that channel uses a separate PCR PID this PCR PID follows the Video PID, separated by "+" (e.g. ...:164+17:...)<br />
<br />
For analogue TV: mostly 301(ivtv > 0.1.9) or 160(ivtv <= 0.1.9, bttv)<br />
<br />
===APID===<br />
Audio PID. Either one or more numbers separated by a comma. Each value stands for a language or two-channel audio. If that channel has AC3 (''Dolby Digital Sound''), the Dolby PIDs follows the mpeg audio PIDs, both lists are separated by semicolon (e.g.:...:101,102;103,104:...). <br />
<br />
For analogue TV: mostly 301(ivtv > 0.1.9) or 160(ivtv <= 0.1.9, bttv)<br />
<br />
The development VDR 1.3.x (but not VDR 1.2.x) accepts language markers like ''APID=eng'', ''APID=deu'', ''APID=2ch''.<br />
<br />
===TPID===<br />
Teletext PID.<br />
<br />
===CA - Conditional access===<br />
This integer describes how to access the encrypted channel.<br />
* '''0''' Free To Air<br />
* '''1'''..'''4''' use DVB-Karte with that number.<br />
* '''5'''..'''100''' use this method for decrypting.<br />
* '''32001''' analog TV (VDR-1.2.x)<br />
* '''A0''' analog TV (VDR-1.3.x)<br />
The methods are described in ca.conf.<br />
<br />
===SID===<br />
Service ID of channel.<br />
<br />
For analogue TV: see ChannelMap.h from [[Analogtv-plugin]] source package.<br />
<br />
===NID===<br />
Network ID. Placeholder for future development. Currently 0. (VDR-1.2.x only)<br />
<br />
===TID===<br />
Transport Stream ID. Placeholder for future development. Currently 0. (VDR-1.2.x only)<br />
<br />
===RID===<br />
Radio ID. Typical 0. Can be used to differentiate between channels having the same [[#SID|SID]], [[#NID|NID]] and [[#TID|TID]].<br />
<br />
==Differences==<br />
; VDR-1.2.x : NID=0, TID=0, RID=0<br />
; VDR-1.2.x with AutoPID-Patch : NID<>0, TID<>0, RID<>0 valid<br />
; VDR-1.3.x : NID<>0, TID<>0, RID<>0 valid, starting from version 1.3.12 also service provider included in Name, in Audio-PID also language marker valid.<br />
<br />
==Links==<br />
{|<br />
| [1]<br />
| http://www.zwez.com/sat/vdr<br />
| Sorted Lists for VDR => www.zwez.com<br />
|-<br />
| [2]<br />
| http://free.pages.at/cleditor<br />
| Channel Editor<br />
|-<br />
| [3]<br />
| http://fchannels.plagge.net<br />
| Frank's Channel Editor for Windows 2000/XP<br />
|-<br />
| [4]<br />
| http://free.pages.at/cleditor/cle4vdr.htm<br />
| Channel List Editor for Linux<br />
|-<br />
| [5]<br />
| http://www.vdrwapmin.formativ.net/dl.php?download=vdr-channels<br />
| VDR Channel Listings for Astra 19.2East and Hotbird 13.0East - VDR 1.3 Format only<br />
|-<br />
| [6]<br />
| [[DVB-T]]<br />
|<br />
|}<br />
<br />
[[Category:Configuration files]]<br />
<br />
<!-- Link to german wiki page --><br />
[[de:Syntax der channels.conf]]</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=Syntax_of_channels.conf&diff=1284Syntax of channels.conf2005-10-21T18:04:12Z<p>Dude: /* Parameters of VDR channel config file */</p>
<hr />
<div>==Parameters of VDR channel config file==<br />
Note that older versions of VDR (e.g 1.2.x) use a slightly different format of this file, and switching between vdr 1.2.x and vdr 1.3.x with the same channel file can lead to problems, see below under [[Differences]] (this caused me a lot of grief). This document is for VDR version 1.3.x.<br />
<br />
In the example below there are three different channel definitions: <br />
* digital satellite TV channel<br />
* digital terrestrian TV channel<br />
* digital cable TV channel<br />
* analog TV channel<br />
{| border=1 cellpadding=5 cellspacing=0<br />
|- bgcolor=#efdead<br />
![[#Name|Name]]<br />
![[#Frequenz|Frequenz]]<br />
![[#Parameter|Parameter]]<br />
![[#Quelle|Quelle]]<br />
![[#SRate|SRate]]<br />
![[#VPID|VPID]]<br />
![[#APID|APID]]<br />
![[#TPID|TPID]]<br />
![[#CA|CA]]<br />
![[#SID|SID]]<br />
![[#NID|NID]]<br />
![[#TID|TID]]<br />
![[#RID|RID]]<br />
|-<br />
| RTL || 12188 || h || S19.2E || 27500 || 163 || 104 || 105 || 0 || 12003 || 0 || 0 || 0<br />
|-<br />
| Das Erste || 522000 || I0C23D0M16B8T8G8Y0 || T || 27500 || 1401 || 1402 || 1404 || 1 || 14 || 0 || 0 || 0<br />
|-<br />
| FS HH || 402000 || C0M64 || C || 6900 || 2401 || 2402 || 2404 || 0 || 28225 || 1 || 1073 || 16387<br />
|-<br />
| VHF K10 || 210250 || C0D45B6 || C || 0 || 301 || 300 || 0 || A0 || 28106 || 0 || 0 || 0<br />
|}<br />
The [[VDR]] reads at startup all channel definitions from the config file '''$CONFIGDIR/vdr/channels.conf''' and writes any changing back to the file.<br />
{{Box Hint|<br />
Changings on channels.conf are useless if VDR is running, VDR has to be stopped if you want to edit this file!<br />
}}<br />
<br />
===Name===<br />
Name of that channel. If the name includes a ":" it will be automatically replaced by "|".<br />
If you use VDR version 1.2.x please do NOT include commas or semicolons. Starting with VDR version 1.3.12 this field also includes the service providers name(aka "bouquet"), separated by a semikolon.<br />
<br />
===Frequency===<br />
Transponder Frequency as Integer<br />
;DVB-S : Frequency in MHz.<br />
;DVB-C : Frequency in MHz, kHz or Hz.<br />
;DVB-T : Frequency in MHz, kHz or Hz.<br />
;analogue TV : Frequency in MHz. (analogTV plugin)<br />
The values here will be multiplied by 1000 until it's bigger than 1000000.<br />
<br />
<br />
===Parameters===<br />
The Parameters in this field depends on the type of DVB you use: [[DVB-S]], [[DVB-C]] ,[[DVB-T]] or analogue TV.<br />
Each Parameter starts with an letter, followed by an Integer which represends the value of that parameter. <br />
<br />
Valid identifiers and their ranges:<br />
<br />
'''Identifier (Values) Meaning'''<br />
<br />
'''I''' (0, 1) Inversion (for DVB-T always 0, please do NOT use 999)<br />
<br />
'''C''' (0, 12, 23, 34, 45, 56, 67, 78, 89) Data rate high priority<br />
for analogue TV is C the capture device:<br />
C0 = /dev/video0<br />
C12 = /dev/video1<br />
C23 = /dev/video2<br />
C34 = /dev/video3<br />
C45 = /dev/video4<br />
<br />
'''D''' (0, 12, 23, 34, 45, 56, 67, 78, 89) Data rate low priority<br />
for analogue TV is D the video source used:<br />
D0 = Television (bttv)<br />
D12 = Composite Video1 (bttv)<br />
D23 = Composite Video2 (bttv)<br />
D34 = S-Video (bttv)<br />
D0 = S-Video ext. (Hauppauge PVR150/PVR250/350-cards only)<br />
D45 = Composite Video (Hauppauge PVR150-cards only)<br />
D45 = Tuner 0 (Hauppauge PVR250/350-cards only)<br />
D56 = Composite ext. (Hauppauge PVR250/350-cards only)<br />
D67 = TV Tuner (Hauppauge PVR150-Karten only)<br />
<br />
'''M''' (0, 16, 32, 64, 128, 256) Modulation<br />
<br />
'''B''' (6, 7, 8) Bandwidth in MHz<br />
for analogue TV is B the Video norm:<br />
B6 = PAL<br />
B7 = NTSC<br />
B8 = SECAM </pre><br />
<br />
'''T''' (2, 8) Transmission mode<br />
<br />
'''G''' (4, 8, 16, 32) Guard intervall<br />
<br />
'''Y''' (0, 1, 2, 4) Hierarchy<br />
<br />
'''H''' Horizontal Polarization<br />
<br />
'''V''' Vertical Polarization<br />
<br />
'''R''' Circular Polarization right<br />
<br />
'''L''' Circular Polarization left<br />
<br />
The Polarisation Parameter is NOT followed by an value for compatibility reasons.<br />
<br />
The value ''999'' is used for automatic. If possible the driver will find the best settings, this is default.<br />
<br />
Example for DVB-T:<br />
<br />
'''I'''0'''C'''23'''D'''0'''M'''16'''B'''8'''T'''8'''G'''8'''Y'''0<br />
Inversion off,<br />
Data Rate High=23,<br />
Data Rate Low=0,<br />
QAM16,<br />
Bandwidth 8MHz,<br />
Transmission Mode 8,<br />
Guard 1/8,<br />
Hierarchy 0<br />
<br />
===Source===<br />
Signal source of the channel, as defined in [[sources.conf]].<br />
Sxxxx, C, T<br />
<br />
For compatbility reasons numeric values are accepted here, but preferred are literals.<br />
<br />
===Symbol Rate===<br />
Symbol Rate of the channel. Valid only for DVB-S and DVB-C, as DVB-T uses another modulation COFDM (Coded Orthogonal Frequency Division Multiplex).<br />
<br />
===VPID===<br />
Video PID (Program Identification).<br />
* 0 for Radio channels<br />
* 1 for encryted channels (pay tv)<br />
If that channel uses a separate PCR PID this PCR PID follows the Video PID, separated by "+" (e.g. ...:164+17:...)<br />
<br />
For analogue TV: mostly 301(ivtv > 0.1.9) or 160(ivtv <= 0.1.9, bttv)<br />
<br />
===APID===<br />
Audio PID. Either one or more numbers separated by a comma. Each value stands for a language or two-channel audio. If that channel has AC3 (''Dolby Digital Sound''), the Dolby PIDs follows the mpeg audio PIDs, both lists are separated by semicolon (e.g.:...:101,102;103,104:...). <br />
<br />
For analogue TV: mostly 301(ivtv > 0.1.9) or 160(ivtv <= 0.1.9, bttv)<br />
<br />
The development VDR 1.3.x (but not VDR 1.2.x) accepts language markers like ''APID=eng'', ''APID=deu'', ''APID=2ch''.<br />
<br />
===TPID===<br />
Teletext PID.<br />
<br />
===CA - Conditional access===<br />
This integer describes how to access the encrypted channel.<br />
* '''0''' Free To Air<br />
* '''1'''..'''4''' use DVB-Karte with that number.<br />
* '''5'''..'''100''' use this method for decrypting.<br />
* '''32001''' analog TV (VDR-1.2.x)<br />
* '''A0''' analog TV (VDR-1.3.x)<br />
The methods are described in ca.conf.<br />
<br />
===SID===<br />
Service ID of channel.<br />
<br />
For analogue TV: see ChannelMap.h from [[Analogtv-plugin]] source package.<br />
<br />
===NID===<br />
Network ID. Placeholder for future development. Currently 0. (VDR-1.2.x only)<br />
<br />
===TID===<br />
Transport Stream ID. Placeholder for future development. Currently 0. (VDR-1.2.x only)<br />
<br />
===RID===<br />
Radio ID. Typical 0. Can be used to differentiate between channels having the same [[#SID|SID]], [[#NID|NID]] and [[#TID|TID]].<br />
<br />
==Differences==<br />
; VDR-1.2.x : NID=0, TID=0, RID=0<br />
; VDR-1.2.x with AutoPID-Patch : NID<>0, TID<>0, RID<>0 valid<br />
; VDR-1.3.x : NID<>0, TID<>0, RID<>0 valid, starting from version 1.3.12 also service provider included in Name, in Audio-PID also language marker valid.<br />
<br />
==Links==<br />
{|<br />
| [1]<br />
| http://www.zwez.com/sat/vdr<br />
| Sorted Lists for VDR => www.zwez.com<br />
|-<br />
| [2]<br />
| http://free.pages.at/cleditor<br />
| Channel Editor<br />
|-<br />
| [3]<br />
| http://fchannels.plagge.net<br />
| Frank's Channel Editor for Windows 2000/XP<br />
|-<br />
| [4]<br />
| http://free.pages.at/cleditor/cle4vdr.htm<br />
| Channel List Editor for Linux<br />
|-<br />
| [5]<br />
| http://www.vdrwapmin.formativ.net/dl.php?download=vdr-channels<br />
| VDR Channel Listings for Astra 19.2East and Hotbird 13.0East - VDR 1.3 Format only<br />
|-<br />
| [6]<br />
| [[DVB-T]]<br />
|<br />
|}<br />
<br />
[[Category:Configuration files]]<br />
<br />
<!-- Link to german wiki page --><br />
[[de:Syntax der channels.conf]]</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=Syntax_of_channels.conf&diff=1283Syntax of channels.conf2005-10-21T18:03:15Z<p>Dude: /* Parameters of VDR channel config file */</p>
<hr />
<div>==Parameters of VDR channel config file==<br />
Note that older versions of VDR (e.g 1.2.x) use a slightly different format of this file, and switching between vdr 1.2.x and vdr 1.3.x with the same channel file can lead to problems (this caused me a lot of grief). This document is for VDR version 1.3.x.<br />
<br />
In the example below there are three different channel definitions: <br />
* digital satellite TV channel<br />
* digital terrestrian TV channel<br />
* digital cable TV channel<br />
* analog TV channel<br />
{| border=1 cellpadding=5 cellspacing=0<br />
|- bgcolor=#efdead<br />
![[#Name|Name]]<br />
![[#Frequenz|Frequenz]]<br />
![[#Parameter|Parameter]]<br />
![[#Quelle|Quelle]]<br />
![[#SRate|SRate]]<br />
![[#VPID|VPID]]<br />
![[#APID|APID]]<br />
![[#TPID|TPID]]<br />
![[#CA|CA]]<br />
![[#SID|SID]]<br />
![[#NID|NID]]<br />
![[#TID|TID]]<br />
![[#RID|RID]]<br />
|-<br />
| RTL || 12188 || h || S19.2E || 27500 || 163 || 104 || 105 || 0 || 12003 || 0 || 0 || 0<br />
|-<br />
| Das Erste || 522000 || I0C23D0M16B8T8G8Y0 || T || 27500 || 1401 || 1402 || 1404 || 1 || 14 || 0 || 0 || 0<br />
|-<br />
| FS HH || 402000 || C0M64 || C || 6900 || 2401 || 2402 || 2404 || 0 || 28225 || 1 || 1073 || 16387<br />
|-<br />
| VHF K10 || 210250 || C0D45B6 || C || 0 || 301 || 300 || 0 || A0 || 28106 || 0 || 0 || 0<br />
|}<br />
The [[VDR]] reads at startup all channel definitions from the config file '''$CONFIGDIR/vdr/channels.conf''' and writes any changing back to the file.<br />
{{Box Hint|<br />
Changings on channels.conf are useless if VDR is running, VDR has to be stopped if you want to edit this file!<br />
}}<br />
<br />
===Name===<br />
Name of that channel. If the name includes a ":" it will be automatically replaced by "|".<br />
If you use VDR version 1.2.x please do NOT include commas or semicolons. Starting with VDR version 1.3.12 this field also includes the service providers name(aka "bouquet"), separated by a semikolon.<br />
<br />
===Frequency===<br />
Transponder Frequency as Integer<br />
;DVB-S : Frequency in MHz.<br />
;DVB-C : Frequency in MHz, kHz or Hz.<br />
;DVB-T : Frequency in MHz, kHz or Hz.<br />
;analogue TV : Frequency in MHz. (analogTV plugin)<br />
The values here will be multiplied by 1000 until it's bigger than 1000000.<br />
<br />
<br />
===Parameters===<br />
The Parameters in this field depends on the type of DVB you use: [[DVB-S]], [[DVB-C]] ,[[DVB-T]] or analogue TV.<br />
Each Parameter starts with an letter, followed by an Integer which represends the value of that parameter. <br />
<br />
Valid identifiers and their ranges:<br />
<br />
'''Identifier (Values) Meaning'''<br />
<br />
'''I''' (0, 1) Inversion (for DVB-T always 0, please do NOT use 999)<br />
<br />
'''C''' (0, 12, 23, 34, 45, 56, 67, 78, 89) Data rate high priority<br />
for analogue TV is C the capture device:<br />
C0 = /dev/video0<br />
C12 = /dev/video1<br />
C23 = /dev/video2<br />
C34 = /dev/video3<br />
C45 = /dev/video4<br />
<br />
'''D''' (0, 12, 23, 34, 45, 56, 67, 78, 89) Data rate low priority<br />
for analogue TV is D the video source used:<br />
D0 = Television (bttv)<br />
D12 = Composite Video1 (bttv)<br />
D23 = Composite Video2 (bttv)<br />
D34 = S-Video (bttv)<br />
D0 = S-Video ext. (Hauppauge PVR150/PVR250/350-cards only)<br />
D45 = Composite Video (Hauppauge PVR150-cards only)<br />
D45 = Tuner 0 (Hauppauge PVR250/350-cards only)<br />
D56 = Composite ext. (Hauppauge PVR250/350-cards only)<br />
D67 = TV Tuner (Hauppauge PVR150-Karten only)<br />
<br />
'''M''' (0, 16, 32, 64, 128, 256) Modulation<br />
<br />
'''B''' (6, 7, 8) Bandwidth in MHz<br />
for analogue TV is B the Video norm:<br />
B6 = PAL<br />
B7 = NTSC<br />
B8 = SECAM </pre><br />
<br />
'''T''' (2, 8) Transmission mode<br />
<br />
'''G''' (4, 8, 16, 32) Guard intervall<br />
<br />
'''Y''' (0, 1, 2, 4) Hierarchy<br />
<br />
'''H''' Horizontal Polarization<br />
<br />
'''V''' Vertical Polarization<br />
<br />
'''R''' Circular Polarization right<br />
<br />
'''L''' Circular Polarization left<br />
<br />
The Polarisation Parameter is NOT followed by an value for compatibility reasons.<br />
<br />
The value ''999'' is used for automatic. If possible the driver will find the best settings, this is default.<br />
<br />
Example for DVB-T:<br />
<br />
'''I'''0'''C'''23'''D'''0'''M'''16'''B'''8'''T'''8'''G'''8'''Y'''0<br />
Inversion off,<br />
Data Rate High=23,<br />
Data Rate Low=0,<br />
QAM16,<br />
Bandwidth 8MHz,<br />
Transmission Mode 8,<br />
Guard 1/8,<br />
Hierarchy 0<br />
<br />
===Source===<br />
Signal source of the channel, as defined in [[sources.conf]].<br />
Sxxxx, C, T<br />
<br />
For compatbility reasons numeric values are accepted here, but preferred are literals.<br />
<br />
===Symbol Rate===<br />
Symbol Rate of the channel. Valid only for DVB-S and DVB-C, as DVB-T uses another modulation COFDM (Coded Orthogonal Frequency Division Multiplex).<br />
<br />
===VPID===<br />
Video PID (Program Identification).<br />
* 0 for Radio channels<br />
* 1 for encryted channels (pay tv)<br />
If that channel uses a separate PCR PID this PCR PID follows the Video PID, separated by "+" (e.g. ...:164+17:...)<br />
<br />
For analogue TV: mostly 301(ivtv > 0.1.9) or 160(ivtv <= 0.1.9, bttv)<br />
<br />
===APID===<br />
Audio PID. Either one or more numbers separated by a comma. Each value stands for a language or two-channel audio. If that channel has AC3 (''Dolby Digital Sound''), the Dolby PIDs follows the mpeg audio PIDs, both lists are separated by semicolon (e.g.:...:101,102;103,104:...). <br />
<br />
For analogue TV: mostly 301(ivtv > 0.1.9) or 160(ivtv <= 0.1.9, bttv)<br />
<br />
The development VDR 1.3.x (but not VDR 1.2.x) accepts language markers like ''APID=eng'', ''APID=deu'', ''APID=2ch''.<br />
<br />
===TPID===<br />
Teletext PID.<br />
<br />
===CA - Conditional access===<br />
This integer describes how to access the encrypted channel.<br />
* '''0''' Free To Air<br />
* '''1'''..'''4''' use DVB-Karte with that number.<br />
* '''5'''..'''100''' use this method for decrypting.<br />
* '''32001''' analog TV (VDR-1.2.x)<br />
* '''A0''' analog TV (VDR-1.3.x)<br />
The methods are described in ca.conf.<br />
<br />
===SID===<br />
Service ID of channel.<br />
<br />
For analogue TV: see ChannelMap.h from [[Analogtv-plugin]] source package.<br />
<br />
===NID===<br />
Network ID. Placeholder for future development. Currently 0. (VDR-1.2.x only)<br />
<br />
===TID===<br />
Transport Stream ID. Placeholder for future development. Currently 0. (VDR-1.2.x only)<br />
<br />
===RID===<br />
Radio ID. Typical 0. Can be used to differentiate between channels having the same [[#SID|SID]], [[#NID|NID]] and [[#TID|TID]].<br />
<br />
==Differences==<br />
; VDR-1.2.x : NID=0, TID=0, RID=0<br />
; VDR-1.2.x with AutoPID-Patch : NID<>0, TID<>0, RID<>0 valid<br />
; VDR-1.3.x : NID<>0, TID<>0, RID<>0 valid, starting from version 1.3.12 also service provider included in Name, in Audio-PID also language marker valid.<br />
<br />
==Links==<br />
{|<br />
| [1]<br />
| http://www.zwez.com/sat/vdr<br />
| Sorted Lists for VDR => www.zwez.com<br />
|-<br />
| [2]<br />
| http://free.pages.at/cleditor<br />
| Channel Editor<br />
|-<br />
| [3]<br />
| http://fchannels.plagge.net<br />
| Frank's Channel Editor for Windows 2000/XP<br />
|-<br />
| [4]<br />
| http://free.pages.at/cleditor/cle4vdr.htm<br />
| Channel List Editor for Linux<br />
|-<br />
| [5]<br />
| http://www.vdrwapmin.formativ.net/dl.php?download=vdr-channels<br />
| VDR Channel Listings for Astra 19.2East and Hotbird 13.0East - VDR 1.3 Format only<br />
|-<br />
| [6]<br />
| [[DVB-T]]<br />
|<br />
|}<br />
<br />
[[Category:Configuration files]]<br />
<br />
<!-- Link to german wiki page --><br />
[[de:Syntax der channels.conf]]</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=Sat_antenna&diff=1302Sat antenna2005-10-21T18:00:51Z<p>Dude: </p>
<hr />
<div>The Sat antenna you use it totally dependent on the kind of sat card you have. Almost all DVB cards can be used with a generic sat dish of as little as 12" diameter, if all you want to aim at is a single sat at a time. An 18" "elliptical" disk can be used to pick up multiple sats's without re-aiming. Several DVB cards also support driving a pointing motor to allow the dish to be mechanically steered to different sats.<br />
<br />
A related issue is the LNB, the electronic device that takes the concentrated microwave signal from the dish and sends it down the wire as an electrical signal. Multiple LNB's can be used if you use a DisEqC box to switch between them; this kind of switch is directly supported by many DVB cards without any extra wiring.</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=CPU&diff=2568CPU2005-10-21T17:54:30Z<p>Dude: /* Introduction */</p>
<hr />
<div>==Introduction==<br />
VDR may use CPUs with clock frequencies starting from 200MHz. But how much is really needed?<br />
A short overview.<br />
<br />
* '''200 MHz Pentium''' => absolute minimum<br />
* '''600 MHz Coppermine Celeron or Via C3 up to 1GHz''' => DivX possible, low power and heat (only 10..12 Watts), possibility for cooling with low noise<br />
* '''~ 800MHz''' => DivX with MPlayer via tv out of graphics card is possible (''not'' with DVB card, too slow for this; see below re. MPEG2 only )<br />
* '''~ 1 GHz''' => output of DivX files via DVB card possible (medium power consumption, about 30 Watts)<br />
* '''>= 2 GHz''' => power users, compiling software, high power consumption (>=60 Watts), difficult for noiseless cooling<br />
<br />
==Absolute Minimum Requirements==<br />
VDR should run starting from 200MHz if a DVB tuner with embedded hardware MPEG-2 decoder is used, a so called Full-Featured [[linuxtv:DVB Standard|DVB]] card. The processor is only used to give the data from DVB card to hard disc and/or from disc to DVB card. The data transfer rate from and to the hard disc is relatively low (~500Kbyte/s) and slow computer does not have problems with that.<br />
<br />
On the other hand, if you don't want to use only MPEG-2 (DVB, DVD), but also MPEG-4 (DivX), the hardware decoder is not able to do that. The CPU has to do this job. In case you bought a DVB tuner without hardware MPEG-2 decoder, a so called Budget DVB card, the main CPU has to decode MPEG bit data stream, even MPEG-2.<br />
<br />
* '''600 MHz''' => too slow for MPEG4/DivX or MPEG-2 software decoding<br />
* '''1 GHz''' => might be sufficient in some cases<br />
* '''2 GHz''' => ok<br />
<br />
Encoding or transcoding of video needs CPU power. This is valid also when producing VCDs, SVCDs<br />
out of DVB records or audio MP3 encoding. Either the PC used for VDR is fast enough or it should be connected to a faster server computer which does this job.<br />
<br />
==Choosing the right CPU for you==<br />
<br />
In general: <br />
<br />
* slow clock frequency => noiseless, because of no cooling problems<br />
* high clock frequency => noisy, because of cooling problems<br />
<br />
Passive cooling is possible up to approx. 1GHz (depending on CPU type) or in dissipated power up to 10 Watts, with very big and heavy CPU coolers and case coolers up to 25 Watt is possible. More needs very sophisticated cooling solutions like heatpipes or water cooling.<br />
<br />
Helpful in this question might be the dissipated power, which you can find here (German only)<br />
*http://www.faqs.org/faqs/de/comp/hardware/cpu+mainboard/kapitel_3/<br />
*http://users.erols.com/chare/elec.htm<br />
<br />
Beside clock frequency the core voltage and cpu stepping is interesting for you. The Celeron 600 Coppermine has only half of the dissipated power compared to Celeron 400 Mendocino.<br />
<br />
[[Category:Hardware]]<br />
<br />
<!-- Link to the german VDR Wiki --><br />
[[de:Prozessor]]</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=CPU&diff=1281CPU2005-10-21T17:52:59Z<p>Dude: /* Introduction */</p>
<hr />
<div>==Introduction==<br />
VDR may use CPUs with clock frequencies starting from 200MHz. But how much is really needed?<br />
A short overview.<br />
<br />
* '''200 MHz Pentium''' => absolute minimum<br />
* '''600 MHz Coppermine Celeron or Via C3 up to 1GHz''' => DivX possible, low power and heat (only 10..12 Watts), possibility for cooling with low noise<br />
* '''~ 800MHz''' => DivX with MPlayer via tv out of graphics card is possible (''not'' with DVB card, too slow for this, unless the DVB card has hardware MPEG (like the Nexus-S) )<br />
* '''~ 1 GHz''' => output of DivX files via DVB card possible (medium power consumption, about 30 Watts)<br />
* '''>= 2 GHz''' => power users, compiling software, high power consumption (>=60 Watts), difficult for noiseless cooling<br />
<br />
==Absolute Minimum Requirements==<br />
VDR should run starting from 200MHz if a DVB tuner with embedded hardware MPEG-2 decoder is used, a so called Full-Featured [[linuxtv:DVB Standard|DVB]] card. The processor is only used to give the data from DVB card to hard disc and/or from disc to DVB card. The data transfer rate from and to the hard disc is relatively low (~500Kbyte/s) and slow computer does not have problems with that.<br />
<br />
On the other hand, if you don't want to use only MPEG-2 (DVB, DVD), but also MPEG-4 (DivX), the hardware decoder is not able to do that. The CPU has to do this job. In case you bought a DVB tuner without hardware MPEG-2 decoder, a so called Budget DVB card, the main CPU has to decode MPEG bit data stream, even MPEG-2.<br />
<br />
* '''600 MHz''' => too slow for MPEG4/DivX or MPEG-2 software decoding<br />
* '''1 GHz''' => might be sufficient in some cases<br />
* '''2 GHz''' => ok<br />
<br />
Encoding or transcoding of video needs CPU power. This is valid also when producing VCDs, SVCDs<br />
out of DVB records or audio MP3 encoding. Either the PC used for VDR is fast enough or it should be connected to a faster server computer which does this job.<br />
<br />
==Choosing the right CPU for you==<br />
<br />
In general: <br />
<br />
* slow clock frequency => noiseless, because of no cooling problems<br />
* high clock frequency => noisy, because of cooling problems<br />
<br />
Passive cooling is possible up to approx. 1GHz (depending on CPU type) or in dissipated power up to 10 Watts, with very big and heavy CPU coolers and case coolers up to 25 Watt is possible. More needs very sophisticated cooling solutions like heatpipes or water cooling.<br />
<br />
Helpful in this question might be the dissipated power, which you can find here (German only)<br />
*http://www.faqs.org/faqs/de/comp/hardware/cpu+mainboard/kapitel_3/<br />
*http://users.erols.com/chare/elec.htm<br />
<br />
Beside clock frequency the core voltage and cpu stepping is interesting for you. The Celeron 600 Coppermine has only half of the dissipated power compared to Celeron 400 Mendocino.<br />
<br />
[[Category:Hardware]]<br />
<br />
<!-- Link to the german VDR Wiki --><br />
[[de:Prozessor]]</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=VDR_Wiki:Sandbox&diff=1293VDR Wiki:Sandbox2005-10-21T17:50:14Z<p>Dude: /* Sandbox */</p>
<hr />
<div>==Sandbox==<br />
Here you can test the wiki syntax!!<br />
<br />
<br />
VDR is really neat, but it is sometimes unstable. [[ [[VDR Wiki:Sandbox]] ]] That said, i love it.<br />
<br />
The end.</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=VDR_Wiki:Sandbox&diff=1279VDR Wiki:Sandbox2005-10-21T17:49:14Z<p>Dude: /* Sandbox */</p>
<hr />
<div>==Sandbox==<br />
Here you can test the wiki syntax!!<br />
<br />
<br />
VDR is really neat, but it is sometimes unstable. [[ If killed while timer<br />
is running, I have seen it "get wierd". ]] That said, i love it.<br />
<br />
The end.</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=VDR_Wiki:Sandbox&diff=1278VDR Wiki:Sandbox2005-10-21T17:48:58Z<p>Dude: /* Sandbox */</p>
<hr />
<div>==Sandbox==<br />
Here you can test the wiki syntax!!<br />
<br />
<br />
VDR is really neat, but it is sometimes unstable. [ If killed while timer<br />
is running, I have seen it "get wierd". ] That said, i love it.<br />
<br />
The end.</div>Dudehttps://www.linuxtv.org/vdrwiki/index.php?title=VDR_Wiki:Sandbox&diff=1277VDR Wiki:Sandbox2005-10-21T17:47:56Z<p>Dude: /* Sandbox */</p>
<hr />
<div>==Sandbox==<br />
Here you can test the wiki syntax!!<br />
<br />
<br />
VDR is really neat, but it is sometimes unstable. That said, i love it.<br />
<br />
The end.</div>Dude