Re: [vdr] Coordinating translations for VDR 2.2.0
Hi Klaus, attached Czech translations. I was waiting with this work as I'm not sure with some translations (especially with adaptive skipping), so please if somebody with Czech language skills is reading this message please review the attachment, thanks. Ales Dne 13.2.2015 v 17:02 Klaus Schmidinger napsal(a): On 13.02.2015 16:52, Klaus Schmidinger wrote: In order to help translators coordinate their work (and avoid duplicate work) for the upcoming VDR 2.2.0, I have set up the directory ftp://ftp.tvdr.de/vdr/Developer/Translations which contains the latest version of all VDR core *.po files. The file "Untranslated" in this directory contains a list of all the *.po files that still contain untranslated texts, each followed by the number of missing translations. These are currently ar.po: 54 ca_ES.po: 54 cs_CZ.po: 54 da_DK.po: 187 el_GR.po: 250 es_ES.po: 54 hr_HR.po: 187 nn_NO.po: 315 pt_PT.po: 82 ru_RU.po: 54 sk_SK.po: 54 sl_SI.po: 55 sr_RS.po: 54 tr_TR.po: 187 uk_UA.po: 3 zh_CN.po: 54 I will update these files as translations come in. If you are considering to contribute translations, please use these files as your starting point. The countdown for VDR version 2.2.0 is running, so translations can only be adopted until next Wednesday, February 19. Sorry, typo. It's of course February 18. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr # VDR language source file. # Copyright (C) 2013 Klaus Schmidinger # This file is distributed under the same license as the VDR package. # VladimÃr Bárta , 2006, 2008 # JiÅà Dobrý , 2008 # Radek Šťastný , 2010 # AleÅ¡ JuÅÃk , 2013 # msgid "" msgstr "" "Project-Id-Version: VDR 2.0.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2015-02-10 13:40+0100\n" "PO-Revision-Date: 2010-05-06 11:00+0200\n" "Last-Translator: AleÅ¡ JuÅÃk \n" "Language-Team: Czech \n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" msgid "*** Invalid Channel ***" msgstr "*** Neplatný kanál ***" msgid "CAM activated!" msgstr "CAM aktivován" msgid "Channel not available!" msgstr "Kanál nenà dostupný!" msgid "Can't start Transfer Mode!" msgstr "Nelze zaÄÃt s pÅenosem" msgid "off" msgstr "vyp." msgid "on" msgstr "zap. " msgid "auto" msgstr "auto" msgid "none" msgstr "žádný" msgid "Polarization" msgstr "Polarizace" msgid "System" msgstr "Systém" msgid "Srate" msgstr "Symbolová rychlost" msgid "Inversion" msgstr "Inverze" msgid "CoderateH" msgstr "CoderateH" msgid "CoderateL" msgstr "CoderateL" msgid "Modulation" msgstr "Modulace" msgid "Bandwidth" msgstr "Å ÃÅka pásma" msgid "Transmission" msgstr "PÅenos" msgid "Guard" msgstr "Ochranný interval" msgid "Hierarchy" msgstr "Hierarchický mód" msgid "Rolloff" msgstr "RollOff" msgid "StreamId" msgstr "StreamId" msgid "Pilot" msgstr "Pilot" msgid "T2SystemId" msgstr "Systémový identifikátor T2" msgid "SISO/MISO" msgstr "Mód SISO/MISO" msgid "Starting EPG scan" msgstr "ZaÄÃná prohledávánà EPG" msgid "Content$Movie/Drama" msgstr "drama" msgid "Content$Detective/Thriller" msgstr "thriller" msgid "Content$Adventure/Western/War" msgstr "dobrodruÅný/western/váleÄný" msgid "Content$Science Fiction/Fantasy/Horror" msgstr "Science Fiction/Fantasy/Horror" msgid "Content$Comedy" msgstr "komedie" msgid "Content$Soap/Melodrama/Folkloric" msgstr "mýdlová opera/melodrama/folklornÃ" msgid "Content$Romance" msgstr "romantický" msgid "Content$Serious/Classical/Religious/Historical Movie/Drama" msgstr "skuteÄný/klasický/náboženstvÃ/historický film/drama" msgid "Content$Adult Movie/Drama" msgstr "film pro dospÄlé/drama" msgid "Content$News/Current Affairs" msgstr "aktuálnà události" msgid "Content$News/Weather Report" msgstr "poÄasÃ" msgid "Content$News Magazine" msgstr "zprávy" msgid "Content$Documentary" msgstr "dokumentárnÃ" msgid "Content$Discussion/Inverview/Debate" msgstr "diskuze/rozhovor/debata" msgid "Content$Show/Game Show" msgstr "zábavné hry" msgid "Content$Game Show/Quiz/Contest" msgstr "soutÄžnÃ/vÄdomostnÃ/soutÄžnà hra" msgid "Content$Variety Show" msgstr "varieté" msgid "Content$Talk Show" msgstr "diskuznà poÅad" msgid "Content$Sports" msgstr "sport" msgid "Content$Special Event" msgstr "zvláštnà událost" msgid "Content$Sport Magazine" msgstr "sportovnà poÅad" msgid "Content$Football/Soccer" msgstr "fotbal" msgid "Content$Tennis/Squash" msgstr "squash" msgid "Content$Team Sports" msgstr "týmové sporty" msgid "Content$Athletics" msgstr "atletika" msgid "Content$Motor Sport" msgstr "motorismus" msgid "Content$Water Sport" msgstr "vodnà sporty" msgid "Content$Winter Sports" msgstr "zimnà sporty" msgid "Content$Equestrian" msgstr "jezdectvÃ" msgid "Content$Martial Sports" msgstr "bojové sporty" msgid "Content$Children's/Youth Programme" msgst
Re: [vdr] RFC: one or many positioners?
On 04/27/2013 04:58 PM, Klaus Schmidinger wrote: ... Of course with chance of source choosing (if more than one tuner is used). I don't understand what you mean here. I thought about the possibility from diseqc.conf: # A line containing space separated integer numbers, terminated with a ':', # defines that any following DiSEqC sequences apply only to the given list # of device numbers. But I'm afraid that this remark was not unnecessary, sry. My second wish is to have possibility to use the new syntax on all tuners available, so only gotoxx command will be send to the/all tuner, to allow simple cooperation with intelligent vtuner devices like NessieDVB. I'm afraid I don't understand this, either. Can you be more specific? I thought about possibility to send gotoxx command to all tuners/cards used, not only to the one which has positioner connected. In this case only gotoxx command should be used in all cases - I don't know if only one new entry in diseqc.conf like * 11700 V 9750 t V W15 P W15 v t * 9 V 10600 t V W15 P W15 v T * 11700 H 9750 t V W15 P W15 V t * 9 H 10600 t V W15 P W15 V T valid for all tuners/cards will be enough. Thanks, Best Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] RFC: one or many positioners?
On 04/23/2013 01:08 PM, Klaus Schmidinger wrote: ... I'm also thinking of allowing something in the form of * 11700 V 9750 t V W15 [E0 10 38 F0] W15 P * 9 V 10600 t V W15 [E0 10 38 F1] W15 P * 11700 H 9750 t V W15 [E0 10 38 F2] W15 P * 9 H 10600 t V W15 [E0 10 38 F3] W15 P (note the '*' instead of, e.g., 'S19.2E'), which could be a shortcut for a (USALS) positioner that could receive any satellite (as long as it's above the horizon). Klaus Hi Klaus, please could it be possible to have functionality of diseqc.conf which allows simple combining of fixed LNB's and motorized dish, so the will it be possible to have in diseqc.conf standard entries like S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W15 A W15 t S19.2E 9 V 10600 t v W15 [E0 10 38 F1] W15 A W15 T S19.2E 11700 H 9750 t V W15 [E0 10 38 F2] W15 A W15 t S19.2E 9 H 10600 t V W15 [E0 10 38 F3] W15 A W15 T followed with the new syntax one * 11700 V 9750 t V W15 [E0 10 38 FC] W15 P * 9 V 10600 t V W15 [E0 10 38 FD] W15 P * 11700 H 9750 t V W15 [E0 10 38 FE] W15 P * 9 H 10600 t V W15 [E0 10 38 FF] W15 P and the standard entries will be prioritized? This will allow to use fixed LNB's as preferable ones in combined diseqc installation. Of course with chance of source choosing (if more than one tuner is used). My second wish is to have possibility to use the new syntax on all tuners available, so only gotoxx command will be send to the/all tuner, to allow simple cooperation with intelligent vtuner devices like NessieDVB. Thanks, Best Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for translations for VDR version 2.0.0: one more string needed
On 03/04/2013 03:30 PM, Klaus Schmidinger wrote: While implementing an option to turn on/off sorting folders first in the Recordings menu, one more string was necessary and needs to be translated: "Always sort folders first" The patch for this new option can be found at http://www.vdr-portal.de/board17-developer/board97-vdr-core/p1130105-feature-request-sortierreihenfolge-verzeichnisse-zuerst-im-osd-unter-aufnahmen/#post1130105 but it would suffice if you could just send me (or post here) the translation of the string shown above. Thanks Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi Klaus, Czech: "Adresáře řadit vždy na začátek" Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] : Positioner and multi-tuner setup?
On 02/21/2013 12:40 PM, Teemu Suikki wrote: ... ... With GotoXX patch, the positioning DiSEqC code is actually just "G" for each satellite, so there is no difference to be found there! ... Hi, your opinion is right for diseqc installations with only motor. But it could be also combined with commited and uncommited switches. I'm using 2 dish installation, one fixed multifeed with 5 LNB's and second dish on motor with one LNB. In my installation there are 3 switches in cascade - first switch is 2 input uncommited with 2 4-input commited switches connected to uncommited switch. The motor is between DVB card and uncommited switch to prevent high current flow through diseqc switches. For any of fixed LNB the diseqc.conf looks like (example for LNB on C input of commited switch connected to 1st input of uncommited switch) S23.5E 11700 V 9750 t v W15 [E0 10 39 F0] W15 [E0 10 38 F8] W15 t S23.5E 9 V 10600 t v W15 [E0 10 39 F0] W15 [E0 10 38 F9] W15 T S23.5E 11700 H 9750 t V W15 [E0 10 39 F0] W15 [E0 10 38 FA] W15 t S23.5E 9 H 10600 t V W15 [E0 10 39 F0] W15 [E0 10 38 FB] W15 T For LNB on motorized dish it could look like S7W 11700 V 9750 t v W15 [E0 10 39 F1] W15 [E0 10 38 FC] V G W15 v t S7W 9 V 10600 t v W15 [E0 10 39 F1] W15 [E0 10 38 FD] V G W15 v T S7W 11700 H 9750 t V W15 [E0 10 39 F1] W15 [E0 10 38 FE] V G W15 V t S7W 9 H 10600 t V W15 [E0 10 39 F1] W15 [E0 10 38 FF] V G W15 V T (remark that output of motorized LNB is connected to D input of commited switch connected to second input of uncommited switch). So practically every combination of switches and motor is possible to use. Best Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] : Positioner and multi-tuner setup?
On 02/21/2013 12:21 AM, Antti Hartikainen wrote: ... I mgot gotoxx working too. For some reason my motor doesn't work with 18V so needed to change it to use 13V. Hi, the reason could be that your DVB card is not able to supply current peak when motor start at 18V and the current fuse was activated. You could try to start motor move at 13V and after some delay (in range of 500ms) switch to 18V if you wish to motor move at higher speed. This is feature of some DVB cards, some other types doesn't have current fuse but current limiter (my old TeVii S470) and some are able to deliver current peak to start motor quickly, but such devices are mostly powered by external supply (NessieDVB). Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for translations for VDR version 2.0.0
On 02/17/2013 04:53 PM, Klaus Schmidinger wrote: Thanks to everybody who helped in translating VDR's texts. The number of untranslated texts has decreased, but there's still quite a few of them. It would be great to have all of them translated for the final version 2.0! Here's a list of the language files that still need some work, together with the number of untranslated texts in each of them: nn_NO.po: 261 el_GR.po: 196 ar.po:138 sl_SI.po: 134 tr_TR.po: 133 sv_SE.po: 133 pl_PL.po: 133 nl_NL.po: 133 hr_HR.po: 133 es_ES.po: 133 da_DK.po: 133 ca_ES.po: 133 ru_RU.po: 130 zh_CN.po: 129 hu_HU.po: 105 sr_SR.po: 52 cs_CZ.po: 34 pt_PT.po: 27 fi_FI.po: 11 sk_SK.po: 2 Please base your work on the latest version of these files in VDR 1.7.38 and send me proper patches. Thanks Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi Klaus, here is Czech translation. Best Regards, Ales --- cs_CZ.po.orig 2013-02-03 16:58:45.0 +0100 +++ cs_CZ.po.patched2013-02-17 23:40:16.863538837 +0100 @@ -4,6 +4,7 @@ # Vladimír Bárta , 2006, 2008 # Jiří Dobrý , 2008 # Radek Šťastný , 2010 +# Aleš Juřík , 2013 # msgid "" msgstr "" @@ -46,16 +47,16 @@ msgstr "Systém" msgid "Srate" -msgstr "" +msgstr "Symbolová rychlost" msgid "Inversion" -msgstr "" +msgstr "Inverze" msgid "CoderateH" -msgstr "" +msgstr "CoderateH" msgid "CoderateL" -msgstr "" +msgstr "CoderateL" msgid "Modulation" msgstr "Modulace" @@ -73,10 +74,10 @@ msgstr "Hierarchický mód" msgid "Rolloff" -msgstr "" +msgstr "RollOff" msgid "PlpId" -msgstr "" +msgstr "PlpId" msgid "Starting EPG scan" msgstr "Začíná prohledávání EPG" @@ -413,13 +414,13 @@ msgstr "Info" msgid "Key$Play/Pause" -msgstr "" +msgstr "Přehrát/Pozastavit" msgid "Key$Play" msgstr "Přehrát" msgid "Key$Pause" -msgstr "Přerušit" +msgstr "Pozastavit" msgid "Key$Stop" msgstr "Zastavit" @@ -648,10 +649,10 @@ msgstr "Složka" msgid "Button$Single" -msgstr "" +msgstr "Bez opakování" msgid "Button$Repeating" -msgstr "" +msgstr "S opakováním" msgid "First day" msgstr "První den" @@ -747,7 +748,7 @@ msgstr "Smazat nahrávku?" msgid "Recording is being edited - really delete?" -msgstr "" +msgstr "Nahrávka je editována - opravdu smazat?" msgid "Error while deleting recording!" msgstr "Chyba při mazání nahrávky!" @@ -849,19 +850,19 @@ msgstr "Složky v menu časovače" msgid "Setup.OSD$Number keys for characters" -msgstr "" +msgstr "Psát písmena pomocí číselných kláves" msgid "Setup.OSD$Color key 0" -msgstr "" +msgstr "Barva klávesy 0" msgid "Setup.OSD$Color key 1" -msgstr "" +msgstr "Barva klávesy 1" msgid "Setup.OSD$Color key 2" -msgstr "" +msgstr "Barva klávesy 2" msgid "Setup.OSD$Color key 3" -msgstr "" +msgstr "Barva klávesy 3" msgid "EPG" msgstr "EPG" @@ -932,7 +933,7 @@ msgstr "Primární DVB zařízení" msgid "Setup.DVB$Standard compliance" -msgstr "" +msgstr "Kompatibilní norma" msgid "Setup.DVB$Video format" msgstr "Formát videa" @@ -987,10 +988,10 @@ #, c-format msgid "Setup.LNB$Device %d connected to sat cable" -msgstr "" +msgstr "Zařízení %d připojeno k sat. kabelu" msgid "Setup.LNB$own" -msgstr "" +msgstr "vlastní" msgid "CAM reset" msgstr "Reset CAMu" @@ -1080,7 +1081,7 @@ msgstr "Délka okamžitého nahrávání (min)" msgid "Setup.Recording$present event" -msgstr "" +msgstr "současná událost" msgid "Setup.Recording$Max. video file size (MB)" msgstr "Maximální velikost nahrávky (MB)" @@ -1101,13 +1102,13 @@ msgstr "Zobrazit režim přehrávání" msgid "Setup.Replay$Show remaining time" -msgstr "" +msgstr "Zobrazit zbývající čas" msgid "Setup.Replay$Progress display time (s)" -msgstr "" +msgstr "Čas zobrazení ukazatele průběhu (s)" msgid "Setup.Replay$Pause replay when setting mark" -msgstr "" +msgstr "Pozastavit přehrávání při nastavování značky" msgid "Setup.Replay$Resume ID" msgstr "ID obnovení" @@ -1131,10 +1132,10 @@ msgstr "Prodleva při volbě kanálu (ms)" msgid "Setup.Miscellaneous$Remote control repeat delay (ms)" -msgstr "" +msgstr "Zpoždění pro začátek opakování stisku klávesy (ms)" msgid "Setup.Miscellaneous$Remote control repeat delta (ms)" -msgstr "" +msgstr "Perioda opakování stisku klávesy (ms)" msgid "Setup.Miscellaneous$Initial channel" msgstr "Kanál po spuštění" @@ -1146,10 +1147,10 @@ msgstr "Hlasitost po spuštění" msgid "Setup.Miscellaneous$Channels wrap" -msgstr "" +msgstr "Přecházet z konce na začátek seznamu kanálů" msgid "Setup.Miscellaneous$Show channel names with source" -msgstr "" +msgstr "Zobrazit kanály se zdrojem" msgid "Setup.Miscellaneous$Emergency exit" msgstr "Nouzové ukončení" @@ -1228,7 +1229,7 @@ msgstr "Nejsou definovány editační značky!" msgid "No editing sequences defined!" -msgstr "" +msgstr "Nejsou definováný žádné editační sekvence!" msgid "Can't start editing process!" msgstr "Nelze začít editační proces!" @@ -12
Re: [vdr] Rotor plugin source?
On 02/12/2013 12:17 PM, Teemu Suikki wrote: Hi! I was trying to find source code for the rotor plugin (not rotorng).. all the links seem to be outdated. Anyone have any version? I'm really only interested in seeing how the GotoX stuff works. I'm trying to send gotox command from diseqc.conf, but the dish doesn't move at all. I have the Eutelsat diseqc 1.2 specification, but the GotoX stuff is marked preliminary and they talk only about terrestrial antennas.. Must be some difference. Here's my non-functioning diseqc.conf entry: #S1.0W - Elevation 17.44, Azimuth 209.62, Motor angle -28.45 S1.0W 11700 V 9750 t W15 [E0 31 6E 0D 07] W15 v t S1.0W 9 V 10600 t W15 [E0 31 6E 0D 07] W15 v T S1.0W 11700 H 9750 t W15 [E0 31 6E 0D 07] W15 V t S1.0W 9 H 10600 t W15 [E0 31 6E 0D 07] W15 V T I actually made a C program that generates these lines for all visible satellites. This might be of interest to people who are waiting for gotox support, if I ever get this working.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi Teemu, I'm using the patch based on patch from Seppo Ingalsuo (see http://patchwork.linuxtv.org/patch/12911/) - this version I'm used now with vdr-1.7.27 together with yaVDR, but have info that it works also with later versions. Patch integrate gotoxx into VDR and works without problems. Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Skystar USB HD + VDR + Astra 23.5E 11817 V / 8psk, fec=5/6
On 06/13/12 10:45, N. D. wrote: > > Hi, > Since recently I have been using Skystar USB HD with my vdr > box. However I have some strange issues with 11817V on Astra 23.5E. > Femon reports that there is a lock and sound comes but the image is > completely garbled. I am starting to suspect that there might be > something wrong with the driver, because I have no trouble with the > other transpoders. Maybe it is the combination of fec=5/6 and 8psk on > the said transponder that is the reason for this. Other transponders > with fec=3/4 and 8psk are OK. The same setup with an HVR-4000 works > fine. > > Kernel: 3.3.4 > > VDR: 1.7.27 > > Could someone who owns a Skystar USB HD and has access to Astra 23.5E > share his experience? Is this a driver issue a problem with vdr or is my card > faulty? > > If someone would be kind enough to test this with his/hers hardware, there is > a FTA channel on the problematic transponder: > > > > Planeta > HD;SatelliteBG:11817:VC56M5O35S1:S23.5E:27500:1001=27:1002=@3:0:0:5410:3:3206:0 > > > > Any help would be greatly appreciated. > > Hi, few months ago on this transponder was nearly 30% of null PID packets broadcasted, but now it seems to be much better (less than 1Mbps). Also multiplexing of this transponder was not equal within time - there was chunks of packets of PlanetHD multiplexed with chunks of other SD channels mixed packets. Maybe the buffers for USB are not big enough to memorize such chunks? But I didn't done measuring for some months, so the situation may be different now. You can see bitrates of this transponder at http://www.digitalbitrate.com/dtv.php?mux=11817&pid=5410&live=70&lang=en . The bitrate of this channel is nothing special, with maximum about 11 Mbps, the peak of 20.2Mbps at 22.5. was maybe a joke. Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Using second tuner on TT S2-6400
On 02/08/12 00:22, Richard Scobie wrote: > I have just managed to get an S2-6400 based vdr sytem up and running and > am trying to work out how I can use the second tuner. > > Currently I have a diseqc switch with two dishes connected to tuner 1, > which works now I use the "-D 0" vdr option. > > I did think that adding "0:" to the top of diseqc.conf file would force > it to use the first tuner, but this does not work. > > In any case, if I add another dish to tuner 2, how do I inform vdr what > sources are available on it? > > I get the impression that a plugin may be required, but I can't see > anything suitable on the Wiki plugin page. > > Any help would be appreciated. > > Regards, > > Richard The dvb card index in diseqc.conf is counted from 1, not from 0, so try change "0:" to "1:". For second tuner add "2:" before lines with sources connected to second tuner. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] diseqc.con question
On 01/14/12 17:49, Arturo Martinez wrote: > Hello, > > I have added a second dvb-s2 card to my vdr 1.7.21 box (for a total of 2 > dvb-s2 cards, and nothing else) > > The first card (adapter0) is connected to a motor and diseqc.conf > reflects this: > > S19.2E 11700 V 9750 t v W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 t > S19.2E 9 V 10600 t v W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 T > S19.2E 11700 H 9750 t V W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 t > S19.2E 9 H 10600 t V W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 T > > S13.0E 11700 V 9750 t v W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 t > S13.0E 9 V 10600 t v W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 T > S13.0E 11700 H 9750 t V W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 t > S13.0E 9 H 10600 t V W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 T > > S5.0E 11700 V 9750 t v W15 [E0 31 6B 05] W25 [E0 31 6B 05] W15 t > S5.0E 9 V 10600 t v W15 [E0 31 6B 05] W25 [E0 31 6B 05] W15 T > S5.0E 11700 H 9750 t V W15 [E0 31 6B 05] W25 [E0 31 6B 05] W15 t > S5.0E 9 H 10600 t V W15 [E0 31 6B 05] W25 [E0 31 6B 05] W15 T > > Now the second card is connected to a diseqc 1.0 switch with 2 feeds > (S5.0E and S0.8W) > > How can I modify diseqc.cond so that vdr is aware that only the second > card can get 0.8W and S5.0E can be accessed by both cards? > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > Try read file diseqc.conf included in vdr-1.7.21 source. There is written: # A line containing space separated integer numbers, # terminated with a ':', defines that any following # DiSEqC sequences apply only to the given list # of device numbers. So your diseqc.conf should be as: 1: S19.2E 11700 V 9750 t v W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 t S19.2E 9 V 10600 t v W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 T S19.2E 11700 H 9750 t V W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 t S19.2E 9 H 10600 t V W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 T S13.0E 11700 V 9750 t v W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 t S13.0E 9 V 10600 t v W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 T ... 2: You new diseqc commands for card 2 BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] GOTOXX patch for vdr-1.7.22 - extension for "smart" DiSEqC algo implemented in last NessieDVB fw
On 12/08/11 12:52, Ales Jurik wrote:
> Hi all,
>
> here is patch for using motor with vdr-1.7.22. As the diseqc subsystem
> changed quite a lot in 1.7.22 please report any problem.
>
Hi,
this is incremental patch to previous GOTOXX patch for NessieDVB users.
It allows usage of only new 'g' command for all LNB positions and gotoxx
motor, so diseqc.conf could be like for all sat positions:
# ONLY SWITCHES
S19.2E 11700 V 9750 t v W30 g W30 v t
S19.2E 9 V 10600 T v W30 g W30 v T
S19.2E 11700 H 9750 t V W30 g W30 V t
S19.2E 9 H 10600 T V W30 g W30 V T
S13.0E 11700 V 9750 t v W30 g W30 v t
S13.0E 9 V 10600 T v W30 g W30 v T
S13.0E 11700 H 9750 t V W30 g W30 V t
S13.0E 9 H 10600 T V W30 g W30 V T
# MOTOR
S1.0W 11700 V 9750 t V W30 g W30 v t
S1.0W 9 V 10600 t V W30 g W30 v T
S1.0W 11700 H 9750 t V W30 g W30 V t
S1.0W 9 H 10600 t V W30 g W30 V T
S9.0E 11700 V 9750 t V W30 g W30 v t
S9.0E 9 V 10600 t V W30 g W30 v T
S9.0E 11700 H 9750 t V W30 g W30 V t
S9.0E 9 H 10600 t V W30 g W30 V T
The original functionality and usage of old 'G' command is not touched.
More about the new "smart" algo in
http://www.nessiedvb.org/forum/viewtopic.php?f=11&t=54&p=219#p219
Regards,
Ales
diff -rupN vdr-1.7.22_gotoxx_patched//diseqc.c vdr-1.7.22_gotoxx_nessiedvb_patched//diseqc.c
--- vdr-1.7.22_gotoxx_patched//diseqc.c 2012-01-08 12:08:20.495922647 +0100
+++ vdr-1.7.22_gotoxx_nessiedvb_patched//diseqc.c 2012-01-08 12:12:37.381918105 +0100
@@ -250,7 +250,8 @@ cDiseqc::eDiseqcActions cDiseqc::Execute
case 'V': return daVoltage18;
case 'A': return daMiniA;
case 'B': return daMiniB;
- case 'G': return daGotoX;
+ case 'G': return daGotoX;
+ case 'g': return daGotoX_Virtual;
case 'W': *CurrentAction = Wait(*CurrentAction); break;
case 'S': *CurrentAction = GetScrBank(*CurrentAction); break;
case '[': *CurrentAction = GetCodes(*CurrentAction, Codes, MaxCodes);
@@ -276,6 +277,7 @@ cDiseqc::eDiseqcActions cDiseqc::TestFor
switch (*(*CurrentAction)++) {
case ' ': break;
case 'G': return daGotoX;
+ case 'g': return daGotoX_Virtual;
default: return daNone;
}
}
diff -rupN vdr-1.7.22_gotoxx_patched//diseqc.h vdr-1.7.22_gotoxx_nessiedvb_patched//diseqc.h
--- vdr-1.7.22_gotoxx_patched//diseqc.h 2012-01-08 12:08:20.495922647 +0100
+++ vdr-1.7.22_gotoxx_nessiedvb_patched//diseqc.h 2012-01-08 12:12:37.381918105 +0100
@@ -50,7 +50,8 @@ public:
daVoltage18,
daMiniA,
daMiniB,
-daGotoX,
+daGotoX,
+daGotoX_Virtual,
daScr,
daCodes,
};
diff -rupN vdr-1.7.22_gotoxx_patched//dvbdevice.c vdr-1.7.22_gotoxx_nessiedvb_patched//dvbdevice.c
--- vdr-1.7.22_gotoxx_patched//dvbdevice.c 2012-01-08 12:10:21.273920511 +0100
+++ vdr-1.7.22_gotoxx_nessiedvb_patched//dvbdevice.c 2012-01-08 12:12:37.383918105 +0100
@@ -460,6 +460,56 @@ bool cDvbTuner::IsTunedTo(const cChannel
return strcmp(channel.Parameters(), Channel->Parameters()) == 0;
}
+void HandleGotox_Virtual(int fd_frontend, int new_source)
+{
+ int gotoXTable[10] = { 0x00, 0x02, 0x03, 0x05, 0x06, 0x08, 0x0A, 0x0B, 0x0D, 0x0E };
+ int satlong;
+
+ if (Setup.UseGotox == 0)
+return;
+
+ // Check if zapped into new source position?
+if ((new_source & 0xFF00) != 0x5300)
+ return; // Fail, not S type source
+satlong = (new_source & 0x0);
+if (new_source & 0x8000) {
+ satlong ^= 0x; satlong++; satlong *= (-1);
+}
+int Long=Setup.GotoxEW ? -Setup.GotoxLong : Setup.GotoxLong;
+int Lat=Setup.GotoxSN ? -Setup.GotoxLat : Setup.GotoxLat;
+double azimuth=M_PI+atan(tan((satlong-Long)*M_PI/1800)/sin(Lat*M_PI/1800));
+double x=acos(cos((satlong-Long)*M_PI/1800)*cos(Lat*M_PI/1800));
+double elevation=atan((cos(x)-0.1513)/sin(x));
+double SatHourangle=180+atan((-cos(elevation)*sin(azimuth))/(sin(elevation)*cos(Lat*M_PI/1800)
+ -cos(elevation)*sin(Lat*M_PI/1800)*cos(azimuth)))*180/M_PI;
+int tmp=(int)(fabs(180-SatHourangle)*10);
+tmp=(tmp/10)*0x10 + gotoXTable[ tmp % 10 ];
+int p2=(tmp%0x0100);
+int p1=(tmp/0x0100);
+if (SatHourangle < 180)
+ p1 |= 0xe0;
+else
+ p1 |= 0xd0;
+
+// Send 1st GotoX command, then wait > 15ms
+uchar gotox_bytes[5] = { 0xe0, 0x31, 0x6e, p1, p2};
+struct dvb_diseqc_master_cmd gotox_cmd;
+memcpy(gotox_cmd.msg, gotox_bytes, 5);
+gotox_cmd.msg_len = 5;
+CHECK(ioctl(fd_frontend, FE_DISEQC_SEND_MASTER_CMD, &gotox_cmd));
+cCondWait::SleepMs(20);
+
+// Send repeated GotoX command, then wait > 15ms
+i
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
On 12/20/11 21:51, Morfsta wrote: > On Tue, Dec 20, 2011 at 9:20 AM, Ales Jurik wrote: >> >> I also had to implement changes into Seppo patch for gotoxx - so maybe >> you could take a look into the latest version of gotoxx patch for >> 1.7.22, it is working without problems, hope it helps. >> >> You could find the patch at >> http://www.linuxtv.org/pipermail/vdr/2011-December/025511.html > > I don't know the previous patch, what did you have to change? > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > The previous version you could find at http://www.linuxtv.org/pipermail/vdr/2011-January/024430.html. I'm not personally sure whether it was working with 1.7.21, but I've heard that it was. I've personally used it with 1.7.16 and 1.7.18. Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
On 12/20/11 09:49, Morfsta wrote: > Hi, > > I have just upgraded my VDR system to yavdr 0.4.0 which uses VDR > 1.7.21 and I notice that the Rotor plugin and my own Rotor-ng plugin > no longer drive the rotor using any of the functions in the menu. > > Is anyone else seeing this too? > > I think that this could be because of recent changes to disecq > handling code within VDR as part of the Unicable update. Klaus could > you point me in the direction of what might have changed such that > these plugins no longer work and I will do my best to implement a fix. > > Thanks very much for your help, > > Regards, > > Morfsta > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > Hi Morfsta, I also had to implement changes into Seppo patch for gotoxx - so maybe you could take a look into the latest version of gotoxx patch for 1.7.22, it is working without problems, hope it helps. You could find the patch at http://www.linuxtv.org/pipermail/vdr/2011-December/025511.html Best Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] GOTOXX patch for vdr-1.7.22
Hi all,
here is patch for using motor with vdr-1.7.22. As the diseqc subsystem
changed quite a lot in 1.7.22 please report any problem.
I'm using/testing it together with vtuner devices (NessieDVB) and
cascade of diseqc switches:
1. DVB device: vtuner(PC) <-> LAN <-> NessieDVB <-> motor <->
uncomm.switch <-> comm. switch)
2. DVB device: vtuner(PC) <-> LAN <-> NessieDVB <-> uncomm.switch <->
comm. switch)
I'm using it together with VDR capability of dedicated and undedicated
sources to some cards and it works for me without problems.
I do not have possibility to test it together with real DVB cards inside
PC, so any remarks are welcomed.
My diseqc.conf looks like:
# ONLY SWITCHES
1 2:
S19.2E 11700 V 9750 t v W30 [E0 10 39 F0] W30 [E0 10 38 F0] W30 t
S19.2E 9 V 10600 t v W30 [E0 10 39 F0] W30 [E0 10 38 F1] W30 T
S19.2E 11700 H 9750 t V W30 [E0 10 39 F0] W30 [E0 10 38 F2] W30 t
S19.2E 9 H 10600 t V W30 [E0 10 39 F0] W30 [E0 10 38 F3] W30 T
S13.0E 11700 V 9750 t v W30 [E0 10 39 F0] W30 [E0 10 38 F4] W30 t
S13.0E 9 V 10600 t v W30 [E0 10 39 F0] W30 [E0 10 38 F5] W30 T
S13.0E 11700 H 9750 t V W30 [E0 10 39 F0] W30 [E0 10 38 F6] W30 t
S13.0E 9 H 10600 t V W30 [E0 10 39 F0] W30 [E0 10 38 F7] W30 T
# MOTOR + SWITCHES
1:
S1.0W 11700 V 9750 t V G [E0 10 39 F1] v W30 [E0 10 38 FC] W30 v t
S1.0W 9 V 10600 t V G [E0 10 39 F1] v W30 [E0 10 38 FD] W30 v T
S1.0W 11700 H 9750 t V G [E0 10 39 F1] V W30 [E0 10 38 FE] W30 V t
S1.0W 9 H 10600 t V G [E0 10 39 F1] V W30 [E0 10 38 FF] W30 V T
S9.0E 11700 V 9750 t V G [E0 10 39 F1] v W30 [E0 10 38 FC] W30 v t
S9.0E 9 V 10600 t V G [E0 10 39 F1] v W30 [E0 10 38 FD] W30 v T
S9.0E 11700 H 9750 t V G [E0 10 39 F1] V W30 [E0 10 38 FE] W30 V t
S9.0E 9 H 10600 t V G [E0 10 39 F1] V W30 [E0 10 38 FF] W30 V T
Enjoy,
Ales
diff -rupN vdr-1.7.22//config.c vdr-1.7.22_gotoxx_patched//config.c
--- vdr-1.7.22//config.c 2011-12-03 16:21:30.0 +0100
+++ vdr-1.7.22_gotoxx_patched//config.c 2011-12-08 12:08:20.482922647 +0100
@@ -389,6 +389,12 @@ cSetup::cSetup(void)
LnbFrequLo = 9750;
LnbFrequHi = 10600;
DiSEqC = 0;
+ UseGotox = 0;
+ GotoxSpeed = 100;
+ GotoxRepeat = 0;
+ GotoxSN = 0; GotoxLat = 613; GotoxEW = 1; GotoxLong = 236; // Somewhere at Tampere, Finland :^)
+ GotoxMaxSwing = 60;
+ GotoxPrevSource = 0;
SetSystemTime = 0;
TimeSource = 0;
TimeTransponder = 0;
@@ -583,6 +589,15 @@ bool cSetup::Parse(const char *Name, con
else if (!strcasecmp(Name, "LnbFrequLo")) LnbFrequLo = atoi(Value);
else if (!strcasecmp(Name, "LnbFrequHi")) LnbFrequHi = atoi(Value);
else if (!strcasecmp(Name, "DiSEqC")) DiSEqC = atoi(Value);
+ else if (!strcasecmp(Name, "UseGotox"))UseGotox = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxSpeed")) GotoxSpeed = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxRepeat")) GotoxRepeat= atoi(Value);
+ else if (!strcasecmp(Name, "GotoxSN")) GotoxSN= atoi(Value);
+ else if (!strcasecmp(Name, "GotoxLat"))GotoxLat = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxEW")) GotoxEW= atoi(Value);
+ else if (!strcasecmp(Name, "GotoxLong")) GotoxLong = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxMaxSwing")) GotoxMaxSwing = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxPrevSource")) GotoxPrevSource= atoi(Value);
else if (!strcasecmp(Name, "SetSystemTime")) SetSystemTime = atoi(Value);
else if (!strcasecmp(Name, "TimeSource")) TimeSource = cSource::FromString(Value);
else if (!strcasecmp(Name, "TimeTransponder")) TimeTransponder= atoi(Value);
@@ -680,6 +695,15 @@ bool cSetup::Save(void)
Store("LnbFrequLo", LnbFrequLo);
Store("LnbFrequHi", LnbFrequHi);
Store("DiSEqC", DiSEqC);
+ Store("UseGotox", UseGotox);
+ Store("GotoxSpeed", GotoxSpeed);
+ Store("GotoxRepeat",GotoxRepeat);
+ Store("GotoxSN",GotoxSN);
+ Store("GotoxLat", GotoxLat);
+ Store("GotoxEW",GotoxEW);
+ Store("GotoxLong", GotoxLong);
+ Store("GotoxMaxSwing", GotoxMaxSwing);
+ Store("GotoxPrevSource",GotoxPrevSource);
Store("SetSystemTime", SetSystemTime);
Store("TimeSource", cSource::ToString(TimeSource));
Store("TimeTransponder",TimeTransponder);
diff -rupN vdr-1.7.22//config.h vdr-1.7.22_gotoxx_patched//config.h
--- vdr-1.7.22//config.h 2011-12-03 15:19:52.0 +0100
+++ vdr-1.7.22_gotoxx_patched//config.h 2011-12-08 12:08:20.494922647 +0100
@@ -248,6 +248,15 @@ public:
int LnbFrequLo;
int LnbFrequHi;
int DiSEqC;
+ int GotoxRepeat;
+ int GotoxSN;
+ int GotoxEW;
+ int GotoxSpeed;
+ int GotoxLat;
+ int GotoxLong;
+ int GotoxMaxSwing;
+ int UseGo
Re: [vdr] [PATCH] GOTOX patch for vdr-1.7.16
On 01/28/11 20:44, Timothy D. Lenz wrote: > I can't try it atm because a relay went bad in my rotor. Only goes one > direction. But looking at the patch, you put the user location in the > patch, not the conf? > > On 1/28/2011 7:40 AM, Ales Jurik wrote: >> Hi, >> >> after some time I've improved the gotox patch for vdr - it is now >> correctly resolving condition for sending diseqc command in >> cDvbTuner::SetFrontend(void) even if diseqc command doesn't change also >> with cascaded diseqc switches. So the diseqc is now sent immediately >> after channel switch and not after frontend tuning is timeouted. >> >> It was tested with diseqc.conf entries like this (cascaded: motor<-> >> uncommitted switch<-> committed switch): >> >> S1.0W 11700 V 9750 t V G [E0 10 39 F1] v W30 [E0 10 38 FC] W30 v t >> S1.0W 9 V 10600 t V G [E0 10 39 F1] v W30 [E0 10 38 FD] W30 v T >> S1.0W 11700 H 9750 t V G [E0 10 39 F1] V W30 [E0 10 38 FE] W30 V t >> S1.0W 9 H 10600 t V G [E0 10 39 F1] V W30 [E0 10 38 FF] W30 V T >> >> S9.0E 11700 V 9750 t V G [E0 10 39 F1] v W30 [E0 10 38 FC] W30 v t >> S9.0E 9 V 10600 t V G [E0 10 39 F1] v W30 [E0 10 38 FD] W30 v T >> S9.0E 11700 H 9750 t V G [E0 10 39 F1] V W30 [E0 10 38 FE] W30 V t >> S9.0E 9 H 10600 t V G [E0 10 39 F1] V W30 [E0 10 38 FF] W30 V T >> >> >> BR, >> >> Ales >> >> >> >> ___ >> vdr mailing list >> vdr@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > No, all parameters are in setup.conf. If you mean initial values, they are in this patch from the first version (http://www.linuxtv.org/pipermail/vdr/2008-March/016164.html). If this is a problem in next version I'll zero it :) . You also could see that all parameters are in config file if you take a look more down in the patch in place where file menu.c is used. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] GOTOX patch for vdr-1.7.16
Hi,
after some time I've improved the gotox patch for vdr - it is now
correctly resolving condition for sending diseqc command in
cDvbTuner::SetFrontend(void) even if diseqc command doesn't change also
with cascaded diseqc switches. So the diseqc is now sent immediately
after channel switch and not after frontend tuning is timeouted.
It was tested with diseqc.conf entries like this (cascaded: motor <->
uncommitted switch <-> committed switch):
S1.0W 11700 V 9750 t V G [E0 10 39 F1] v W30 [E0 10 38 FC] W30 v t
S1.0W 9 V 10600 t V G [E0 10 39 F1] v W30 [E0 10 38 FD] W30 v T
S1.0W 11700 H 9750 t V G [E0 10 39 F1] V W30 [E0 10 38 FE] W30 V t
S1.0W 9 H 10600 t V G [E0 10 39 F1] V W30 [E0 10 38 FF] W30 V T
S9.0E 11700 V 9750 t V G [E0 10 39 F1] v W30 [E0 10 38 FC] W30 v t
S9.0E 9 V 10600 t V G [E0 10 39 F1] v W30 [E0 10 38 FD] W30 v T
S9.0E 11700 H 9750 t V G [E0 10 39 F1] V W30 [E0 10 38 FE] W30 V t
S9.0E 9 H 10600 t V G [E0 10 39 F1] V W30 [E0 10 38 FF] W30 V T
BR,
Ales
diff -rup a/config.c b/config.c
--- a/config.c 2010-06-06 12:06:43.0 +0200
+++ b/config.c 2011-01-28 14:44:30.888676207 +0100
@@ -326,6 +326,12 @@ cSetup::cSetup(void)
LnbFrequLo = 9750;
LnbFrequHi = 10600;
DiSEqC = 0;
+ UseGotox = 0;
+ GotoxSpeed = 100;
+ GotoxRepeat = 0;
+ GotoxSN = 0; GotoxLat = 613; GotoxEW = 1; GotoxLong = 236; // Somewhere at
Tampere, Finland :^)
+ GotoxMaxSwing = 60;
+ GotoxPrevSource = 0;
SetSystemTime = 0;
TimeSource = 0;
TimeTransponder = 0;
@@ -517,6 +523,15 @@ bool cSetup::Parse(const char *Name, con
else if (!strcasecmp(Name, "LnbFrequLo")) LnbFrequLo =
atoi(Value);
else if (!strcasecmp(Name, "LnbFrequHi")) LnbFrequHi =
atoi(Value);
else if (!strcasecmp(Name, "DiSEqC")) DiSEqC =
atoi(Value);
+ else if (!strcasecmp(Name, "UseGotox"))UseGotox =
atoi(Value);
+ else if (!strcasecmp(Name, "GotoxSpeed")) GotoxSpeed =
atoi(Value);
+ else if (!strcasecmp(Name, "GotoxRepeat")) GotoxRepeat=
atoi(Value);
+ else if (!strcasecmp(Name, "GotoxSN")) GotoxSN=
atoi(Value);
+ else if (!strcasecmp(Name, "GotoxLat"))GotoxLat =
atoi(Value);
+ else if (!strcasecmp(Name, "GotoxEW")) GotoxEW=
atoi(Value);
+ else if (!strcasecmp(Name, "GotoxLong")) GotoxLong =
atoi(Value);
+ else if (!strcasecmp(Name, "GotoxMaxSwing")) GotoxMaxSwing =
atoi(Value);
+ else if (!strcasecmp(Name, "GotoxPrevSource")) GotoxPrevSource=
atoi(Value);
else if (!strcasecmp(Name, "SetSystemTime")) SetSystemTime =
atoi(Value);
else if (!strcasecmp(Name, "TimeSource")) TimeSource =
cSource::FromString(Value);
else if (!strcasecmp(Name, "TimeTransponder")) TimeTransponder=
atoi(Value);
@@ -613,6 +628,15 @@ bool cSetup::Save(void)
Store("LnbFrequLo", LnbFrequLo);
Store("LnbFrequHi", LnbFrequHi);
Store("DiSEqC", DiSEqC);
+ Store("UseGotox", UseGotox);
+ Store("GotoxSpeed", GotoxSpeed);
+ Store("GotoxRepeat",GotoxRepeat);
+ Store("GotoxSN",GotoxSN);
+ Store("GotoxLat", GotoxLat);
+ Store("GotoxEW",GotoxEW);
+ Store("GotoxLong", GotoxLong);
+ Store("GotoxMaxSwing", GotoxMaxSwing);
+ Store("GotoxPrevSource",GotoxPrevSource);
Store("SetSystemTime", SetSystemTime);
Store("TimeSource", cSource::ToString(TimeSource));
Store("TimeTransponder",TimeTransponder);
diff -rup a/config.h b/config.h
--- a/config.h 2010-09-12 13:31:21.0 +0200
+++ b/config.h 2011-01-28 14:45:10.882778898 +0100
@@ -229,6 +229,15 @@ public:
int LnbFrequLo;
int LnbFrequHi;
int DiSEqC;
+ int GotoxRepeat;
+ int GotoxSN;
+ int GotoxEW;
+ int GotoxSpeed;
+ int GotoxLat;
+ int GotoxLong;
+ int GotoxMaxSwing;
+ int UseGotox;
+ int GotoxPrevSource;
int SetSystemTime;
int TimeSource;
int TimeTransponder;
diff -rup a/diseqc.c b/diseqc.c
--- a/diseqc.c 2010-02-06 16:43:31.0 +0100
+++ b/diseqc.c 2011-01-28 14:46:03.418659831 +0100
@@ -134,6 +134,7 @@ cDiseqc::eDiseqcActions cDiseqc::Execute
case 'V': return daVoltage18;
case 'A': return daMiniA;
case 'B': return daMiniB;
+ case 'G': return daGotoX;
case 'W': *CurrentAction = Wait(*CurrentAction); break;
case '[': *CurrentAction = Codes(*CurrentAction); return
*CurrentAction ? daCodes : daNone;
default: return daNone;
diff -rup a/diseqc.h b/diseqc.h
--- a/diseqc.h 2010-02-06 16:14:42.0 +0100
+++ b/diseqc.h 2011-01-28 14:46:10.495659376 +0100
@@ -22,6 +22,7 @@ public:
daVoltage18,
daMiniA,
daMiniB,
+daGotoX,
daCodes,
};
enum { MaxDiseqcCodes = 6 };
diff -rup a/dvbdevice.c b/dvbd
Re: [vdr] Request for rotor/actuator support integration to vdr
On 01/23/11 20:37, Timothy D. Lenz wrote: > btw, here is a collection of pdf's on rotor function: > http://www.eutelsat.com/satellites/4_5_5.html > > On 1/23/2011 9:57 AM, Manuel Reimer wrote: >> Hello, >> >>> I would also love to see native rotor support. The plugin crashes all >>> the time with yavdr and is virtually unusable. >> >> IMHO it depends on how those rotors are controlled. If they are >> controlled via DISEQ and VDR, for whatever reason, fails to send the >> required DISEQ commands, then VDR should be fixed to be able to do so. >> >> If rotors have to be controlled using a completely different protocol, >> then this IMHO better should keep in a plugin for one simple reason: >> Just like the plugin, the rotor support in VDR itself will have to be >> fixed and updated in future. Someone will have to do this and as Klaus >> most probably doesn't have or use a rotor, I think he doesn't want to >> do that. >> >> Yours >> >> Manuel > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > There is also patch for vdr-core (http://www.linuxtv.org/pipermail/vdr/2010-March/022561.html) from Seppo Ingalsuo. It is working for me for very long time without any problem, it allows to combine diseqc gotoxx command with standard diseqc commands (switches) in diseqc.conf. If Klaus needs somebody to test any new implementation of gotoxx into vdr-core I'd do my best. Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] GOTOX patch for vdr-1.7.13
On 10/19/10 22:03, Bikalexander wrote: > Hi Ales, > I have 3 dvb cards - one is FF SS1 + 2 budget cards. How can I specify > the dvb card for motor control ? > BR, > Alex > >> Hi, >> >> here you can find new version of gotox patch for vdr-1.7.13. I've added new >> menuentry - GotoxMaxSwing - max possible angle of rotor move. This set >> automatically maximum wait time for rotor move (tohether with rotor speed) >> instead of 60s as it was in previous versions. >> >> BR, >> >> Ales > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > Hi, I'm afraid that this patch is intended only for one card. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] GOTOX patch for vdr-1.7.13
Hi,
here you can find new version of gotox patch for vdr-1.7.13. I've added new
menuentry - GotoxMaxSwing - max possible angle of rotor move. This set
automatically maximum wait time for rotor move (tohether with rotor speed)
instead of 60s as it was in previous versions.
BR,
Ales
diff -rupN a//config.c b//config.c
--- a//config.c 2010-01-31 13:36:36.0 +0100
+++ b//config.c 2010-03-06 11:16:11.0 +0100
@@ -326,6 +326,12 @@ cSetup::cSetup(void)
LnbFrequLo = 9750;
LnbFrequHi = 10600;
DiSEqC = 0;
+ UseGotox = 0;
+ GotoxSpeed = 100;
+ GotoxRepeat = 0;
+ GotoxSN = 0; GotoxLat = 613; GotoxEW = 1; GotoxLong = 236; // Somewhere at Tampere, Finland :^)
+ GotoxMaxSwing = 60;
+ GotoxPrevSource = 0;
SetSystemTime = 0;
TimeSource = 0;
TimeTransponder = 0;
@@ -514,6 +520,15 @@ bool cSetup::Parse(const char *Name, con
else if (!strcasecmp(Name, "LnbFrequLo")) LnbFrequLo = atoi(Value);
else if (!strcasecmp(Name, "LnbFrequHi")) LnbFrequHi = atoi(Value);
else if (!strcasecmp(Name, "DiSEqC")) DiSEqC = atoi(Value);
+ else if (!strcasecmp(Name, "UseGotox"))UseGotox = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxSpeed")) GotoxSpeed = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxRepeat")) GotoxRepeat= atoi(Value);
+ else if (!strcasecmp(Name, "GotoxSN")) GotoxSN= atoi(Value);
+ else if (!strcasecmp(Name, "GotoxLat"))GotoxLat = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxEW")) GotoxEW= atoi(Value);
+ else if (!strcasecmp(Name, "GotoxLong")) GotoxLong = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxMaxSwing")) GotoxMaxSwing = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxPrevSource")) GotoxPrevSource= atoi(Value);
else if (!strcasecmp(Name, "SetSystemTime")) SetSystemTime = atoi(Value);
else if (!strcasecmp(Name, "TimeSource")) TimeSource = cSource::FromString(Value);
else if (!strcasecmp(Name, "TimeTransponder")) TimeTransponder= atoi(Value);
@@ -607,6 +622,15 @@ bool cSetup::Save(void)
Store("LnbFrequLo", LnbFrequLo);
Store("LnbFrequHi", LnbFrequHi);
Store("DiSEqC", DiSEqC);
+ Store("UseGotox", UseGotox);
+ Store("GotoxSpeed", GotoxSpeed);
+ Store("GotoxRepeat",GotoxRepeat);
+ Store("GotoxSN",GotoxSN);
+ Store("GotoxLat", GotoxLat);
+ Store("GotoxEW",GotoxEW);
+ Store("GotoxLong", GotoxLong);
+ Store("GotoxMaxSwing", GotoxMaxSwing);
+ Store("GotoxPrevSource",GotoxPrevSource);
Store("SetSystemTime", SetSystemTime);
Store("TimeSource", cSource::ToString(TimeSource));
Store("TimeTransponder",TimeTransponder);
diff -rupN a//config.h b//config.h
--- a//config.h 2010-02-05 16:38:32.0 +0100
+++ b//config.h 2010-03-06 11:16:11.0 +0100
@@ -229,6 +229,15 @@ public:
int LnbFrequLo;
int LnbFrequHi;
int DiSEqC;
+ int GotoxRepeat;
+ int GotoxSN;
+ int GotoxEW;
+ int GotoxSpeed;
+ int GotoxLat;
+ int GotoxLong;
+ int GotoxMaxSwing;
+ int UseGotox;
+ int GotoxPrevSource;
int SetSystemTime;
int TimeSource;
int TimeTransponder;
diff -rupN a//diseqc.c b//diseqc.c
--- a//diseqc.c 2010-02-06 16:43:31.0 +0100
+++ b//diseqc.c 2010-03-06 11:16:11.0 +0100
@@ -134,6 +134,7 @@ cDiseqc::eDiseqcActions cDiseqc::Execute
case 'V': return daVoltage18;
case 'A': return daMiniA;
case 'B': return daMiniB;
+ case 'G': return daGotoX;
case 'W': *CurrentAction = Wait(*CurrentAction); break;
case '[': *CurrentAction = Codes(*CurrentAction); return *CurrentAction ? daCodes : daNone;
default: return daNone;
diff -rupN a//diseqc.h b//diseqc.h
--- a//diseqc.h 2010-02-06 16:14:42.0 +0100
+++ b//diseqc.h 2010-03-06 11:11:23.296532650 +0100
@@ -22,6 +22,7 @@ public:
daVoltage18,
daMiniA,
daMiniB,
+daGotoX,
daCodes,
};
enum { MaxDiseqcCodes = 6 };
diff -rupN a//dvbdevice.c b//dvbdevice.c
--- a//dvbdevice.c 2010-02-21 18:10:35.0 +0100
+++ b//dvbdevice.c 2010-03-06 11:16:11.0 +0100
@@ -15,9 +15,11 @@
#include
#include
#include
+#include
#include "channels.h"
#include "diseqc.h"
#include "dvbci.h"
+#include "skins.h"
#include "menuitems.h"
#include "sourceparams.h"
@@ -353,6 +355,99 @@ static unsigned int FrequencyToHz(unsign
return f;
}
+void HandleGotox(int fd_frontend, int new_source)
+{
+
+ int gotoXTable[10] = { 0x00, 0x02, 0x03, 0x05, 0x06, 0x08, 0x0A, 0x0B, 0x0D, 0x0E };
+ int satlong;
+ int satprev;
+ float waitseconds = 0;
+ float waitmaximum = 60;
+
+ if (Setup.UseGotox == 0)
+return;
+
+ // Check if zapped into new source position?
+ if (new_source != Setup.GotoxPr
Re: [vdr] [ANNOUNCE] vdr-femon-1.7.7 vdr-iptv-0.4.0 vdr-skinsoppalusikka-1.7.1 vdr-rssreader-1.7.0
On Saturday 06 of March 2010, Timothy D. Lenz wrote: > Not a big deal, but I notice that femon doesn't give as much infor about > the tuner as before. It was listing the tuner chip, now that lower > section is just blank. > In my PC with Conexant CX24116/24118 card (Tevii) it works. BR, ALes ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.12 + reelbox plugin
On Tuesday 09 of February 2010, Josce wrote: > Could someone please tell me what patches I need to apply so that I can > run vdr-1.7.12 and the reelbox plugin. And preferably where to find them. > > Josce > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > You can find patches here - http://www.cssf.cz/showthread.php?t=36345 . These are working as for vdr-1.7.11 as for 1.7.12. Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Fwd: GOTOX patch for 1.7.5
On Friday 05 of February 2010, Bikalexander wrote: > Thanks for the link, now I've finally got the correct version:). > > I am using 2 DVB cards, it can be adjusted in some way that certain > device is being addressed? > AFAIK not. But you are welcomed to improve this patch. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] GOTOX patch for 1.7.5
On Thursday 04 of February 2010, Bikalexander wrote: > Even with last patch does not do it: > > ### > ## g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses > -c -DREMOTE_KBD -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" > -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE > -DVIDEODIR=\"/video\" -DCONFDIR=\"/video\" > -DPLUGINDIR=\"./PLUGINS/lib\" -DLOCDIR=\"./locale\" > -I/usr/include/freetype2 diseqc.c > g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD > -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -DVIDEODIR=\"/video\" -DCONFDIR=\"/video\" > -DPLUGINDIR=\"./PLUGINS/lib\" -DLOCDIR=\"./locale\" > -I/usr/include/freetype2 dvbdevice.c > dvbdevice.c: In function вЂvoid HandleGotox(int, int)’: > dvbdevice.c:227: error: вЂSkins’ was not declared in this scope > dvbdevice.c:227: error: вЂmtWarning’ was not declared in this scope > make: *** [dvbdevice.o] Fehler 1 > make: *** Warte auf noch nicht beendete Prozesse... > # > Which exactly version of patch did you use? What was the output of patching? Was there any rejects? Did you try to patch vanilla version of vdr? Without these basic information people could only guess what happened in your vdr. For me now it works without problem (latest patch is in http://www.linuxtv.org/pipermail/vdr/2010-January/022017.html). Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] can't compile femon 1.7.5 with vdr 1.7.12
On Sunday 31 of January 2010, Goga777 wrote: > /usr/src/vdr/PLUGINS/src/femon# make all > g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -Wall > -march=athlon-xp -pipe -fomit-frame-pointer -fPIC -c > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"femon"' -I../s2-liplianin/linux/include > -I../../../include femonosd.c femonosd.c: In member function ‘bool > cFemonOsd::DeviceSwitch(int)’: femonosd.c:724: error: no matching function > for call to ‘cTransferControl::cTransferControl(cDevice*, tChannelID, int, > const int*, const int*, const int*)’ ../../../include/vdr/transfer.h:33: > note: candidates are: cTransferControl::cTransferControl(cDevice*, const > cChannel*) ../../../include/vdr/transfer.h:28: note: > cTransferControl::cTransferControl(const cTransferControl&) make: *** > [femonosd.o] Ошибка 1 > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > Hi, try this: @@ -721,7 +721,8 @@ cDevice::GetDevice(device)->SwitchChannel(channel, true); if (cDevice::GetDevice(device) == cDevice::PrimaryDevice()) cDevice::GetDevice(device)->ForceTransferMode(); - cControl::Launch(new cTransferControl(cDevice::GetDevice(device), channel->GetChannelID(), channel- >Vpid(), channel->Apids(), channel->Dpids(), channel->Spids())); +// cControl::Launch(new cTransferControl(cDevice::GetDevice(device), channel->GetChannelID(), channel- >Vpid(), channel->Apids(), channel->Dpids(), channel->Spids())); + cControl::Launch(new cTransferControl(cDevice::GetDevice(device), channel)); cStatus::MsgChannelSwitch(cDevice::PrimaryDevice(), channel- >Number()); return (true); } BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] GOTOX patch and vdr-1.7.10
On Sunday 22 of November 2009, Ales Jurik wrote: > Last version of this patch from is applicable and functioning also with > vdr-1.7.10. > See http://www.linuxtv.org/pipermail/vdr/2009-April/020248.html. > > Regards, > > Ales Patch is also applicable without rejects to vdr-1.7.11. Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] GOTOX patch and vdr-1.7.10
Last version of this patch from is applicable and functioning also with vdr-1.7.10. See http://www.linuxtv.org/pipermail/vdr/2009-April/020248.html. Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] gotoX patch & vdr 1.7.8
On Saturday 22 of August 2009, Goga777 wrote: > > have you ideas about how can I see in the log the disecs commands from vdr > to dish ? > You can add dsyslog command to each point in dvbdevice.c where this ioctl with FE_DISEQC_SEND_MASTER_CMD is called (3 times) and print out the cmd buffer. Better is to place syslog into frontend source of your card. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] need help with GOTOX patch.
On Tuesday 09 of June 2009, lucian orasanu wrote: > I did that, i took my position with an gps, putet ther in lnb config, and > afther that changing channels.conf form diferent satelites, but i did > something wrong because i did not manage to get signal, until i setup my > antena manualy again (form left right switches of motor). > > My idea was to use this patch and stored position from my motor!! > This is not how this patch is working. But if your motor is moving when using this patch and you didn't get the signal your motor could be badly oriented to the south. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] need help with GOTOX patch.
On Tuesday 09 of June 2009, Goga777 wrote: > > The patch send this command only when satellite is changing. > > is it possible to have a look in vdr logs on that disecs commands ? > > >You should also use it for motor behind diseqc switch. The next example is > > for 4-input diseqc switch which has diseqc motor connected to input 4. > > did LNB connect to the output of motor ? Yes. I'm using this configuration for nearly 3 years without problem. > > > Please be sure that in > > such way your dvb card will not be overloaded with output current (you > > should use motor which disconnect LNB when moving > > hmm. I didn't know about that feature of motors. Which motors do you mean ? Nothing special, it was only my idea ;) . But if the consumption of moving motor is under 200mA with starting current under 400mA it could be sufficient. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] need help with GOTOX patch.
On Tuesday 09 of June 2009, lucian orasanu wrote: > Hy, > > I want to use this patch, but i dont know how. Only this is necesary to > move the motor: > > S5.0W 11700 V 9750 G v t > S5.0W 9 V 10600 G v T > S5.0W 11700 H 9750 G V t > S5.0W 9 H 10600 G V T > > > or should be like this: > > S1.0W 11700 V 9750 G v t [e0 31 6e 01(this bite should be positon in rotor > ?] S1.0W 9 V 10600 G v T [e0 31 6e 01] > S1.0W 11700 H 9750 G V t [e0 31 6e 01] > S1.0W 9 H 10600 G V T [e0 31 6e 01] > > with settings like this my motor wont move! The first config should be ok. > > And in lnb setup menu at degres what should i put there, my position? Yes, your position. > > How this pach works?? Patch is originaly written by Seppo Ingalsuo (http://www.linuxtv.org/pipermail/vdr/2008-March/016164.html). The patch uses algo from vdr-rotor patch to calculate angle to which motor should move and send then the gotox diseqc command [e0 31 6e p1 p2] where p1 and p2 is calculated angle. If you have dish with closer beam be sure to have position of satellites in sources.conf and channels.conf written in right way (for example satellites at 1.0W are at 0.83W and 0.75W exactly) to be able to receive also weaker transponders. The patch send this command only when satellite is changing. You should also use it for motor behind diseqc switch. The next example is for 4-input diseqc switch which has diseqc motor connected to input 4. Please be sure that in such way your dvb card will not be overloaded with output current (you should use motor which disconnect LNB when moving and card with electronically limited output current to prevent damages). S0.8W 11700 V 9750 t v W15 [E0 10 38 FC] W150 G v t S0.8W 9 V 10600 t v W15 [E0 10 38 FD] W150 G v T S0.8W 11700 H 9750 t V W15 [E0 10 38 FE] W150 G V t S0.8W 9 H 10600 t V W15 [E0 10 38 FF] W150 G V T BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ExtensionHD and VDR 1.7.6
On Sunday 31 of May 2009, Niels Wagenaar wrote: > Currently I use the Reel-VDR fork and it seems to work quite nicely. And > it doesn't require many patches to get it working, only some S2API based > patches. > > Regards, > > Niels Wagenaar Please could you send patches you are using (especially for reelvdr and s2api)? Thanks BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ExtensionHD and VDR 1.7.6
On Thursday 28 of May 2009, Josce wrote: > > When I opened the link and tried to download the script some other > page opened up that wanted me to do something. Sadly I don't know what. > A howto in Czech is totally useless to me. I really can't understand a word > of it. (No offense to the Czech's, I don't think a howto in Finnish would > be terribly helpfull for someone from the Czech republic ...) > > But if the script is the same as I found at > http://reelbox-forum.com/showthread.php?t=16436 it will not help, because > it didn't work for me. > You can go into the script and see what it is doing. I've used it in this way. Then (after understanding the script) you can use patches attached. Or you can go to http://www.vdr-portal.de/board/board.php?boardid=85 - it is german vdr forum. There you can find a lot of patches too and it is not in Czech but in German - I don't know if it is better for you, but could be. I know that Czech is not widely understanded as many other languages ;) . BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ExtensionHD and VDR 1.7.6
On Thursday 28 of May 2009, Luca Olivetti wrote: > En/na VDR User ha escrit: > > On Thu, May 28, 2009 at 7:50 AM, Josce wrote: > >> Reelbox plugin still occasionally freezes, but so it has always done. > >> The reelbox plugin is of course a joke and I deeply regret buying the > >> card from Reel-Multimedia. Hopefully the VDPAU is more promising. > > > > Sorry for OT but just wanted to note that I and many other users I > > know are using VDPAU now and it works great. I believe the devs are > > preparing to submit a patch to Darren Salt so it may become a part of > > vanilla xine-lib. A huge thanks to the devs for their work! > > OTOH with my setup it works poorly (artifacts, banding, freezing, > changes in color, etc.) and I'm not the only one, so I'm not sure vdpau > support is mature enough for inclusion in xine-lib. > > Bye I've installed 2 eHD's. Working for hours daily without problems, but huge patching of vdr and reelbox plugin (and skinreel3 plugin) is necessary. Try to look at http://www.cssf.cz/showthread.php?t=34104 - there is script and patches, also some howto's - but in Czech. It was written for vdr-1.7.5, but I'm now using it with vdr-1.7.7 without problems. The problems you are talking about could also be due to problems in TS stream as reelbox plugin don't test too much incoming data. Distorted data could cause hangup of eHD. If you use vdr-sc update to latest version from mercurial, it could help on some channels. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Status of WinTV-HVR-4000 card!!
On Tuesday 26 of May 2009, Fabio Bordin wrote: > Il 25/05/2009 20:19, Goga777 ha scritto: > >>> I have this card and recently I reinstall my system. > >>> > >>> The card is recognized from kernel 2.6.28 so you don't need to patch > >>> dvb driver. > >>> > >>> My vdr, with recent s2api dvb driver, don't use this card. > >>> Vdr find the card but can't tune any channel. Femon plugin show me > >>> always 0% signal while kaffeine can tune channels. > >>> > >>> Maybe I missed something, I'm investigating. > >>> > >>> Beside, with my older system I never used dvb-t tuner in vdr. > >> > >> I have no problem with this card and dvb-s2 drivers from Igor > >> Liplianin's hg together with vdr-1.7.7. I'm not using dvb-t. > >> > >> I have installed s2-liplianin-2866ecb5e66b.tar.bz2 from > >> http://mercurial.intuxication.org/hg/s2-liplianin/ - it is not current > >> tip, but no need to update. > > > > I have no problem with hvr4000 and dvb-s2/s channels > > I'm using the Igor Liplianin's hg repo and I am not using dvb-t. > > > > Goga > > Last night I understood why I was not able to use the card with VDR: I'm > using a 64-bit. > > I tried the same firmware and drivers in a 32-bit os and everything > worked correctly. No problem here - working for more than one year at 64bit Debian (Sid->Lenny- >Squeeze). ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Status of WinTV-HVR-4000 card!!
On Monday 25 of May 2009, Fabio Bordin wrote: > I have this card and recently I reinstall my system. > > The card is recognized from kernel 2.6.28 so you don't need to patch dvb > driver. > > My vdr, with recent s2api dvb driver, don't use this card. > Vdr find the card but can't tune any channel. Femon plugin show me > always 0% signal while kaffeine can tune channels. > > Maybe I missed something, I'm investigating. > > Beside, with my older system I never used dvb-t tuner in vdr. > I have no problem with this card and dvb-s2 drivers from Igor Liplianin's hg together with vdr-1.7.7. I'm not using dvb-t. I have installed s2-liplianin-2866ecb5e66b.tar.bz2 from http://mercurial.intuxication.org/hg/s2-liplianin/ - it is not current tip, but no need to update. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Newbee questions about HDTV VDR system with TT-budget S2-3200.
On Sunday 24 of May 2009, Carsten Koch wrote: > > * How do I configure LIRC, so it works with the S3-3200 > and the remote control included with it? > > Thanks in advance for any hints, > Carsten. Hi, you don't need lirc, try plugin remote (http://www.escape- edv.de/endriss/vdr/). It seems to be easier to setup and works without problems. BR Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Black screen on some channels with vdr 1.7.6
On Tuesday 05 of May 2009, Klaus Schmidinger wrote:
> On 05/05/09 00:04, Ales Jurik wrote:
...
> >
> > Many thanks, it seems to works (with type of 2), but it is necessary to
> > set "Update channels" to "no".
>
> Please try this:
>
> --- remux.c 2009/05/03 14:43:25 2.20
> +++ remux.c 2009/05/05 07:27:21
> @@ -795,6 +795,7 @@
>scanner <<= 8;
>scanner |= Data[i];
>switch (type) {
> +case 0x01: // MPEG 1 video
> case 0x02: // MPEG 2 video
> if (scanner == 0x0100) { // Picture Start
> Code if (synced && Processed)
>
> With this you should be able to turn "Update channels" on again.
>
> Klaus
Thanks for pointing me to the problem. But for working it it was necessary to
add these two changes more:
--- remux.c 2009-05-05 09:44:01.0 +0200
+++ remux.c 2009-05-05 09:50:56.854167360 +0200
@@ -481,6 +481,7 @@ void cPatPmtParser::ParsePmt(const uchar
for (SI::Loop::Iterator it; Pmt.streamLoop.getNext(stream, it); ) {
dbgpatpmt(" stream type = %02X, pid = %d",
stream.getStreamType(), stream.getPid());
switch (stream.getStreamType()) {
+ case 0x01: // MPEG1
case 0x02: // STREAMTYPE_13818_VIDEO
case 0x1B: // MPEG4
vpid = stream.getPid();
@@ -702,7 +703,7 @@ cFrameDetector::cFrameDetector(int Pid,
newFrame = independentFrame = false;
numPtsValues = 0;
numIFrames = 0;
- isVideo = type == 0x02 || type == 0x1B; // MPEG 2 or MPEG 4
+ isVideo = type == 0x01 || type == 0x02 || type == 0x1B; // MPEG 1,2 or 4
frameDuration = 0;
framesInPayloadUnit = framesPerPayloadUnit = 0;
payloadUnitOfFrame = 0;
Now it seems to works as on older vdr versions (with PES), but video
discontinuities are still present on Spektrum (as on many other channels from
other providers). On STB's these discontinuities are not present in video.
Thanks and BR,
Ales
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Black screen on some channels with vdr 1.7.6
On Monday 04 of May 2009, Klaus Schmidinger wrote: > On 04.05.2009 23:05, Marek Hajduk wrote: > > It's a pity, no answer. > > I would like to note, that with vdr 1.7.7 is result same-NO video but > > audio is OK. Receiving these channels with sat boxes like dreambox or > > triple dragon is without problem. > > '1' is not a known video stream type in VDR. > > Try '2' or '27', as in > > AXN,AXN;UPC > Direct:10921:hC56M2O0S0:S19.2E:22000:651=2:660=hun,661=cze,662=eng:0:D02,18 >15:20352:1:1063:0 > > or > > AXN,AXN;UPC > Direct:10921:hC56M2O0S0:S19.2E:22000:651=27:660=hun,661=cze,662=eng:0:D02,1 >815:20352:1:1063:0 > > Klaus Many thanks, it seems to works (with type of 2), but it is necessary to set "Update channels" to "no". BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.6 + reelbox plugin
On Thursday 30 of April 2009, Josce wrote: > Has anyone started using VDR 1.7.6 with the reelbox plugin. > If so, could you please mail a link to whatever patch you used to do it. > > BR, > > Josce You have more posibilities - I'm using patches from http://www.cssf.cz/showthread.php?t=34104 first entry, there is also readme (in Czech) which explains prerequisities and howto use automatic instal script. This include reelskin plugin, you have to edit the script to use vdr-1.7.6 instead of vdr-1.7.5. Other posibilities are at vdrforum. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Black screen on some channels with vdr 1.7.6
On Tuesday 28 of April 2009, Marek Hajduk wrote: > Hi, > > On some channels I get only audio. Screen is still black without > Picture. There are two encrypted channels from 19.2E, in UPC packet: > > AXN,AXN;UPC > Direct:10921:hC56M2O0S0:S19.2E:22000:651=1:660=hun,661=cze,662=eng:0:D02,18 >15:20352:1:1063:0 >Spektrum,Spektrum;UPC > Direct:11671:hC56M2O0S0:S19.2E:22000:401=1:410=hun,411=cze:420:D02,1815:203 >60:1:1031:0 > > > I am using eHD, but with VDPAU and xine is result same = black screen. > When I try to record thease channels, recording has 0 kB. > > However, I can watch thease channels through streamdev plugin and > popcornhour or vlc, but Picture has lot of errors. Here is recording > through streamdev plugin. > > Download link: http://rapidshare.com/files/226876888/1220.ts > > > If somebody will want to fix it, I can provide some more debug info. I confirm this situation, maybe some more info - up to vdr-1.7.2 it was possible to receive those channels, but Spektrum was receivable with errors (discontinuities) in video, AXN was receivable without visible errors. From vdr version vdr-1.7.4 (1.7.3 I didn't use) those channels are not receivable. Decoding is ok as the sound is receivable without problems. Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] GOTOX patch for 1.7.5
On Monday 27 of April 2009, Goga777 wrote:
> Приветствую, Ales
>
> > On Monday 20 of April 2009, ThE-GuRuZ wrote:
> > > Hi to all, does anybody know if there is a patch for gotox like
> > > vdr-1.7.0?
> > >
> > >
> > > ___
> > > vdr mailing list
> > > vdr@linuxtv.org
> > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
> >
> > Patch gotox for vdr-1.7.0 is also working for vdr-1.7.5. Did you ever try
> > it?
>
> yes, this patch is working well with gotox protocol
>
> could you implement the feature - during of dish moving is it possible to
> write on screen - "please waiting for. The dish is moving to xxx position"
>
> Goga
>
See attached new version - it is possible to apply this patch to vanilla vdr
from vdr-1.7.0 to vdr-1.7.6 without rejects.
Once more thanks to Seppo I. for his first version of this patch.
Regards,
Ales
diff -ruNp vdr-1.7.0.orig/config.c vdr-1.7.0/config.c
--- vdr-1.7.0.orig/config.c 2008-02-17 14:39:00.0 +0100
+++ vdr-1.7.0/config.c 2008-09-02 11:08:39.633819400 +0200
@@ -229,6 +229,11 @@ cSetup::cSetup(void)
LnbFrequLo = 9750;
LnbFrequHi = 10600;
DiSEqC = 0;
+ UseGotox = 0;
+ GotoxSpeed = 100;
+ GotoxRepeat = 0;
+ GotoxSN = 0; GotoxLat = 613; GotoxEW = 1; GotoxLong = 236; // Somewhere at Tampere, Finland :^)
+ GotoxPrevSource = 0;
SetSystemTime = 0;
TimeSource = 0;
TimeTransponder = 0;
@@ -402,6 +407,14 @@ bool cSetup::Parse(const char *Name, con
else if (!strcasecmp(Name, "LnbFrequLo")) LnbFrequLo = atoi(Value);
else if (!strcasecmp(Name, "LnbFrequHi")) LnbFrequHi = atoi(Value);
else if (!strcasecmp(Name, "DiSEqC")) DiSEqC = atoi(Value);
+ else if (!strcasecmp(Name, "UseGotox"))UseGotox = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxSpeed")) GotoxSpeed = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxRepeat")) GotoxRepeat= atoi(Value);
+ else if (!strcasecmp(Name, "GotoxSN")) GotoxSN= atoi(Value);
+ else if (!strcasecmp(Name, "GotoxLat"))GotoxLat = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxEW")) GotoxEW= atoi(Value);
+ else if (!strcasecmp(Name, "GotoxLong")) GotoxLong = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxPrevSource")) GotoxPrevSource= atoi(Value);
else if (!strcasecmp(Name, "SetSystemTime")) SetSystemTime = atoi(Value);
else if (!strcasecmp(Name, "TimeSource")) TimeSource = cSource::FromString(Value);
else if (!strcasecmp(Name, "TimeTransponder")) TimeTransponder= atoi(Value);
@@ -485,6 +498,14 @@ bool cSetup::Save(void)
Store("LnbFrequLo", LnbFrequLo);
Store("LnbFrequHi", LnbFrequHi);
Store("DiSEqC", DiSEqC);
+ Store("UseGotox", UseGotox);
+ Store("GotoxSpeed", GotoxSpeed);
+ Store("GotoxRepeat",GotoxRepeat);
+ Store("GotoxSN",GotoxSN);
+ Store("GotoxLat", GotoxLat);
+ Store("GotoxEW",GotoxEW);
+ Store("GotoxLong", GotoxLong);
+ Store("GotoxPrevSource",GotoxPrevSource);
Store("SetSystemTime", SetSystemTime);
Store("TimeSource", cSource::ToString(TimeSource));
Store("TimeTransponder",TimeTransponder);
diff -ruNp vdr-1.7.0.orig/config.h vdr-1.7.0/config.h
--- vdr-1.7.0.orig/config.h 2008-04-12 15:02:10.0 +0200
+++ vdr-1.7.0/config.h 2008-09-02 11:08:39.633819400 +0200
@@ -215,6 +215,14 @@ public:
int LnbFrequLo;
int LnbFrequHi;
int DiSEqC;
+ int GotoxRepeat;
+ int GotoxSN;
+ int GotoxEW;
+ int GotoxSpeed;
+ int GotoxLat;
+ int GotoxLong;
+ int UseGotox;
+ int GotoxPrevSource;
int SetSystemTime;
int TimeSource;
int TimeTransponder;
diff -ruNp vdr-1.7.0.orig/diseqc.c vdr-1.7.0/diseqc.c
--- vdr-1.7.0.orig/diseqc.c 2008-02-10 15:09:27.0 +0100
+++ vdr-1.7.0/diseqc.c 2008-09-02 11:08:39.633819400 +0200
@@ -114,6 +114,7 @@ cDiseqc::eDiseqcActions cDiseqc::Execute
case 'V': return daVoltage18;
case 'A': return daMiniA;
case 'B': return daMiniB;
+ case 'G': return daGotoX;
case 'W': *CurrentAction = Wait(*CurrentAction); break;
case '[': *CurrentAction = Codes(*CurrentAction); return *CurrentAction ? daCodes : daNone;
default: return daNone;
diff -ruNp vdr-1.7.0.orig/diseqc.h vdr-1.7.0/diseqc.h
--- vdr-1.7.0.orig/diseqc.h 2002-12-07 14:54:02.0 +0100
+++ vdr-1.7.0/diseqc.h 2008-09-02 11:08:39.637817080 +0200
@@ -22,6 +22,7 @@ public:
daVoltage18,
daMiniA,
daMiniB,
+daGotoX,
daCodes,
};
enum { MaxDiseqcCodes = 6 };
diff -ruNp vdr-1.7.0.orig/dvbdevice.c vdr-1.7.0/dvbdevice.c
--- vdr-1.7.0.orig/dvbdevice.c 2008-04-13 16:15:35.0 +0200
+++ vdr-1.7.0/dvbdevice.c 2008-09-02 11:14:19.0 +0200
@@ -17,6 +17,7 @@
#include
#
Re: [vdr] GOTOX patch for 1.7.5
On Monday 20 of April 2009, ThE-GuRuZ wrote: > Hi to all, does anybody know if there is a patch for gotox like vdr-1.7.0? > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Patch gotox for vdr-1.7.0 is also working for vdr-1.7.5. Did you ever try it? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor and vdr
On Saturday 14 of February 2009, Arthur Konovalov wrote: > Ales Jurik wrote: > > Original patch from Seppo (vdr-1.5.16): > > http://www.mail-archive.com/vdr@linuxtv.org/msg05864.html > > > > Patches for 1.6.0 and 1.7.0 (could be used up to 1.7.4): > > http://www.linuxtv.org/pipermail/vdr/2008-September/017637.html > > Do You have any additional hints? > It doesn't compiles with vdr-1.7.4 :( I've just tested it and no problem at all. BR, Ales > > AK > > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor and vdr
On Thursday 12 of February 2009, Ales Jurik wrote: > On Thursday 12 of February 2009, Goga777 wrote: > > Hi > > > > is there any working solution for moving of rotor with vdr ? > > > > Goga > > > > ___ > > vdr mailing list > > vdr@linuxtv.org > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > Hi, > > I'm using vdr-gotox patch. For which version of vdr do you need it? I've > send it to this ml some months (year) ago, but no problem to resend. > > I'm not original author od this patch but I have permission from the author > to change it to newer versions of vdr. Original patch from Seppo (vdr-1.5.16): http://www.mail-archive.com/vdr@linuxtv.org/msg05864.html Patches for 1.6.0 and 1.7.0 (could be used up to 1.7.4): http://www.linuxtv.org/pipermail/vdr/2008-September/017637.html BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor and vdr
On Thursday 12 of February 2009, Goga777 wrote: > Hi > > is there any working solution for moving of rotor with vdr ? > > Goga > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi, I'm using vdr-gotox patch. For which version of vdr do you need it? I've send it to this ml some months (year) ago, but no problem to resend. I'm not original author od this patch but I have permission from the author to change it to newer versions of vdr. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.4 S2API and DVB-C ??
On Wednesday 04 of February 2009, Scott wrote: > On 04/02/2009 19:26, Simon Baxter wrote: > > Hi > > > > Does vdr-1.7.4, ts recordings and and the S2API work under DVB-C? > > > > I can't see why it wouldn't? > > > > Dum question - where can I find the S2API repository? I just pulled the > > latest v4l-dvb from linuxtv.org, but I get vdr compiling errors > > requesting "version 5". > > I think it should compile with that but you need to make sure it is > using those headers. I changed line 24 of my Makefile to this: > > INCLUDES = -I/data/downloads/v4l-dvb/linux/include > -I/usr/src/linux/include -I/usr/include/freetype2 > > Where /data/downloads/v4l-dvb is where you got the latest v4l-dvb tree. > -- Hi, better is to change variable DVBDIR in Make.config, for example: DVBDIR = /usr/local/src/dvb-s2/linux Then it will be used also by plugins. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 & S2API - Channels not Available
On Wednesday 04 of February 2009, Morfsta wrote:
> On Wed, Feb 4, 2009 at 10:58 AM, Klaus Schmidinger
>
> wrote:
> > Well, even using *any* version 1.7.x in a productive environment
> > is a risk ;-)
>
> [SNIP]
>
> > S2API was necessary for HDTV channels, and recording HDTV channels
> > only makes sense in TS. The PES recording of HDTV broadcasts was never
> > officially supported by VDR.
>
> The other problem is that I don't think anyone has got VDR 1.7.4
> working with the eHD yet, which is my output device... :-( So it seems
> everywhere I look at the moment I am stuck. :-(
>
Here are patches for eHD and vdr-1.7.4. I've tested it only for a little time
as I didn't have enough time (now I revert back to vdr-1.7.0 with
multiproto).
Included are two patches - first is for reelbox plugin. In file
ReelBoxDevice.c patch solves the audio problem (vdr is sending audio with
zero trackid and reelbox plugin cancel such streams). In setupmenu.c is
solved the problem with saving config and in VideoPlayerPipHd.c the include
solves for me compile problem in amd64 linux.
In the patch for vdr in part of device.c is patch from Klaus for subtitles and
rest is very quick and dirty patch for osd to compile with reelbox plugin. It
mostly revert the vdr osd to 1.7.0 version of files, but it seems to be
working at minimum with default STTNG skin, other skins are not tested.
Enjoy,
BR,
Ales
diff -ru vdr-1.7.4.orig/config.h vdr-1.7.4/config.h
--- vdr-1.7.4.orig/config.h 2009-01-06 17:56:27.0 +0100
+++ vdr-1.7.4/config.h 2009-02-01 20:47:21.611262480 +0100
@@ -192,11 +192,11 @@
void StoreLanguages(const char *Name, int *Values);
bool ParseLanguages(const char *Value, int *Values);
bool Parse(const char *Name, const char *Value);
- cSetupLine *Get(const char *Name, const char *Plugin = NULL);
void Store(const char *Name, const char *Value, const char *Plugin = NULL, bool AllowMultiple = false);
void Store(const char *Name, int Value, const char *Plugin = NULL);
public:
// Also adjust cMenuSetup (menu.c) when adding parameters here!
+ cSetupLine *Get(const char *Name, const char *Plugin = NULL);
int __BeginData__;
char OSDLanguage[I18N_MAX_LOCALE_LEN];
char OSDSkin[MaxSkinName];
diff -ru vdr-1.7.4.orig/device.c vdr-1.7.4/device.c
--- vdr-1.7.4.orig/device.c 2009-01-25 12:10:56.0 +0100
+++ vdr-1.7.4/device.c 2009-02-01 20:35:04.203264160 +0100
@@ -1304,8 +1304,9 @@
if (!dvbSubtitleConverter)
dvbSubtitleConverter = new cDvbSubtitleConverter;
tsToPesSubtitle.PutTs(Data, Length);
- if (const uchar *p = tsToPesSubtitle.GetPes(Length)) {
- dvbSubtitleConverter->Convert(p, Length);
+ int l;
+ if (const uchar *p = tsToPesSubtitle.GetPes(l)) {
+ dvbSubtitleConverter->Convert(p, l);
tsToPesSubtitle.Reset();
}
return Length;
diff -ru vdr-1.7.4.orig/font.h vdr-1.7.4/font.h
--- vdr-1.7.4.orig/font.h 2007-06-23 12:09:14.0 +0200
+++ vdr-1.7.4/font.h 2009-02-01 20:47:21.611262480 +0100
@@ -36,6 +36,12 @@
private:
static cFont *fonts[];
public:
+ enum { NUMCHARS = 256 };
+ typedef uint32_t tPixelData;
+ struct tCharData {
+ tPixelData width, height;
+ tPixelData lines[1];
+ };
virtual ~cFont() {}
virtual int Width(uint c) const = 0;
///< Returns the width of the given character in pixel.
diff -ru vdr-1.7.4.orig/osdbase.h vdr-1.7.4/osdbase.h
--- vdr-1.7.4.orig/osdbase.h 2007-11-03 15:50:52.0 +0100
+++ vdr-1.7.4/osdbase.h 2009-02-01 20:47:21.611262480 +0100
@@ -84,9 +84,7 @@
class cOsdMenu : public cOsdObject, public cList {
private:
- static cSkinDisplayMenu *displayMenu;
static int displayMenuCount;
- static int displayMenuItems;
char *title;
int cols[cSkinDisplayMenu::MaxTabs];
int first, current, marked;
@@ -97,6 +95,7 @@
bool hasHotkeys;
protected:
void SetDisplayMenu(void);
+ static int displayMenuItems;
cSkinDisplayMenu *DisplayMenu(void) { return displayMenu; }
const char *hk(const char *s);
void SetCols(int c0, int c1 = 0, int c2 = 0, int c3 = 0, int c4 = 0);
@@ -123,6 +122,7 @@
public:
cOsdMenu(const char *Title, int c0 = 0, int c1 = 0, int c2 = 0, int c3 = 0, int c4 = 0);
virtual ~cOsdMenu();
+ static cSkinDisplayMenu *displayMenu;
virtual bool NeedsFastResponse(void) { return subMenu ? subMenu->NeedsFastResponse() : cOsdObject::NeedsFastResponse(); }
int Current(void) const { return current; }
void Add(cOsdItem *Item, bool Current = false, cOsdItem *After = NULL);
diff -ru vdr-1.7.4.orig/osd.c vdr-1.7.4/osd.c
--- vdr-1.7.4.orig/osd.c 2009-01-16 15:34:32.0 +0100
+++ vdr-1.7.4/osd.c 2009-02-01 20:47:21.611262480 +0100
@@ -379,13 +379,14 @@
if (strncmp(Xpm[i + 1], s, c) == 0) {
if (i == NoneColorIndex)
NoneColorIndex = MAXNUMCOLORS;
- SetIndex(x, y, (IgnoreNone && i > NoneColorIndex) ? i - 1 : i);
+ SetIndexFast(x, y, (IgnoreNone && i > NoneColorIndex) ?
Re: [vdr] VDR 1.7.0 & S2API - Channels not Available
On Wednesday 04 of February 2009, Morfsta wrote: > On Wed, Feb 4, 2009 at 10:58 AM, Klaus Schmidinger > > wrote: > > Well, even using *any* version 1.7.x in a productive environment > > is a risk ;-) > > [SNIP] > > > S2API was necessary for HDTV channels, and recording HDTV channels > > only makes sense in TS. The PES recording of HDTV broadcasts was never > > officially supported by VDR. > > The other problem is that I don't think anyone has got VDR 1.7.4 > working with the eHD yet, which is my output device... :-( So it seems > everywhere I look at the moment I am stuck. :-( > Hi, I have it working with some dirty hacks (reelvdr svn 10388 - the latest with hdplayer). But for the problem with sending AC3 sound to ac3dec (with -a ac3dec) I didn't have enough time to solve. With sound over HDMI it could be used. Ales > Should VDR-1.7.0 be reporting my DVB-T frontends as DVBT when it > starts up? Is there perhaps a capability flag in the driver that has > not been setup for the devices that I am using? I compared the channel > settings of BBC ONE in VDR with multiproto version and s2api version > that I am running and they are exactly the same. > > @Niels, which DVB-T devices are you using successfully with VDR-1.7.0 > so that I can compare them with my own drivers? It seems strange > though that scan-s2 successfully finds all the channels but VDR won't > play them. > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can't compile VDR
On Thursday 15 of January 2009, Chris Silva wrote: > Hi. > > I'm having problems compiling VDR 1.7.0 and 1.7.3. > > This is the error: > > /usr/local/src/s2-liplianin/linux/include/linux/videodev2.h:64:28: > error: linux/compiler.h: No such file or directory > In file included from > /usr/local/src/s2-liplianin/linux/include/linux/videodev.h:16, > from dvbdevice.c:13: Hi try with kernel headers installed in /usr/src/linux (or linked there): cd /usr/local/src/s2-liplianin/linux/include/linux ln -s /usr/src/linux/include/linux/compiler.h compiler.h BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.3 + reelbox plugin
On Saturday 10 of January 2009, Josce wrote: > I am currently using vdr-1.6.0 with reelbox plugin and would like to > test the new vdr-1.7.3. I have Checked out revision 10331 from reelbox.org. > Since I am having trouble getting the reelbox plugin to compile with > vdr-1.7.3 I thought I'd check first before continuing: > > - Does the reelbox plugin work with vdr-1.7.3? > (does vdr's switching to TS make the current plugin unusable?) > > - Is there a patch already for vdr-1.7.3 to make it compile with the > reelbox plugin? ( I have tested some patches for vdr-1.7.0, but the ones I > have tested fail ) > > Regards, > > Josce Hi, yersterday I've tried to test it but first problem was S2API drivers - drivers from last versions are unusable for me (kernel 2.6.26, amd64 arch., HVR-4000). I was getting Oops, /dev/dvb was not populated and so on. Totally unusable drivers for my configuration. Then I used S2API from 23.11.2008 - it is necessary to patch this version reg. Klaus need. I've made some patch for reelbox plugin, but I was not able to get sound as well as from eHD as from PC soundcard. It seemed to be that the switching between channels is 2-3 times longer (maybe as syncearly from R.Nissl is not implemented?). So now I'm back at vdr-1.7.0 and last multiproto from Igor. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR/eHD HD Picture Breakup
On Wednesday 19 of November 2008, Ales Jurik wrote: > On Wednesday 19 of November 2008, Morfsta wrote: > > Hi, > > > > I've posted this to the reel multimedia forum but have had no > > response, so thought I'd try here. > > > > This might have been covered in German on the VDR forum or on the Reel > > forum so I'm hoping someone knows about it. > > > > I am using VDR and eHD (SVN 8858) and I get picture break ups (ongoing > > pixelisation and stutter) until I change channel up and down. This > > happens only on HD channels and usually occurs after about 10 minutes > > of completely normal viewing. > > > > Has anyone experienced this and is there any fix? > > > > Thanks, > > > > Morfsta > > Hi, > > I've this problem also observed. When it appers I switch to some FTA SD > channel and back and in most cases the problem doesn't appear more. It > seems that some structure is not reinitialized properly when switching > between HD channels. > > But I've problems also with some other channels, even SD. For example do > you have problems with this channel? > > Planeta > Sport;Globecast:12597:vC34M2O0S0:S13.0E:27500:80:81:0:0:8201:318:9400:0 > > I'm getting few seconds of interrupted video and then the video is stalled. > Interesting is that sound is running without problems. So, yesterday my friend send me info that with hdplayer from svn 8649 (driver and linux.bin could be from latest svn) channel "Planeta Sport" is running. I've just tested it and he was right. Why? BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR/eHD HD Picture Breakup
On Wednesday 19 of November 2008, Morfsta wrote: > Hi, > > I've posted this to the reel multimedia forum but have had no > response, so thought I'd try here. > > This might have been covered in German on the VDR forum or on the Reel > forum so I'm hoping someone knows about it. > > I am using VDR and eHD (SVN 8858) and I get picture break ups (ongoing > pixelisation and stutter) until I change channel up and down. This > happens only on HD channels and usually occurs after about 10 minutes > of completely normal viewing. > > Has anyone experienced this and is there any fix? > > Thanks, > > Morfsta Hi, I've this problem also observed. When it appers I switch to some FTA SD channel and back and in most cases the problem doesn't appear more. It seems that some structure is not reinitialized properly when switching between HD channels. But I've problems also with some other channels, even SD. For example do you have problems with this channel? Planeta Sport;Globecast:12597:vC34M2O0S0:S13.0E:27500:80:81:0:0:8201:318:9400:0 I'm getting few seconds of interrupted video and then the video is stalled. Interesting is that sound is running without problems. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] TT-S2 3200 remote doesn't work properly - wrong keymap?
On Tuesday 04 of November 2008, hudo kkow wrote: > Hi, there. > > My 3200 remote isn't working properly with v4l-dvb current drivers. > Some buttons are switched (power button is 2, 2 is 4, 3 is 5 and so > on) or unresponsive. > > Any ideas as what's going on were? There was a fix for multiproto that > involved patching yourpath/linux/drivers/media/dvb/ttpci/budget-ci.c > with something like: > > break; > case 0x1010: > case 0x1017: > /* for the Technotrend 1500 bundled remote */ > ir_input_init(input_dev, &budget_ci->ir.state, > IR_TYPE_RC5, ir_codes_tt_1500); > > to something like: > > break; > case 0x1010: > case 0x1017: > case 0x1019: > /* for the Technotrend 1500 bundled remote */ > ir_input_init(input_dev, &budget_ci->ir.state, > IR_TYPE_RC5, ir_codes_tt_1500); > > Editing the file on v4l-dvb shows this: > > break; > case 0x1010: > case 0x1017: > case 0x101a: > /* for the Technotrend 1500 bundled remote */ > ir_input_init(input_dev, &budget_ci->ir.state, > IR_TYPE_RC5, ir_codes_tt_1500); > > The third value on v4l-dvb is different. Any ideas? On some markets the TT S2-3200 is sold with remote originally from TT 1500, so in this cases the table from TT 1500 should be used. Edit the code to: break; case 0x1010: case 0x1017: case 0x1019: case 0x101a: /* for the Technotrend 1500 bundled remote */ and everything should be ok. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Syncearly + subtitles problem
On Tuesday 21 of October 2008, Josce wrote: > >> The reason for this is explained here: > >> > >> http://www.linuxtv.org/pipermail/vdr/2008-October/018072.html > >> > >> So now we just have to be patient and hope that someone who knows how to > >> fix it fixes it. > > > >I've read this mail but now I've done test recording 47mins long (National > >Geographic, UPC, 19.2E) and when replaying it (without using any speed > > change within replaying) the dvb-subtitles were in sync for whole 47 > > minutes. > > > >So I do not understand why the problems appears only at specific channels. > > Are you sure that this recording doesn't have the subtitle "burned in"? > What happens when you turn off the dvb-subtitle support in VDR? > Yes, I'm sure. Normally, I'm watching this channel without subtitles as it is broacasted in english and polish languages (no problem for me). For this test I've switch the dvb-subtitles by key on IR :) to "cze". If you want I'll try on another channel too. I'm able to receive sats from 53.0E to 30.0W. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Syncearly + subtitles problem
On Tuesday 21 of October 2008, Josce wrote: > >I'm not sure as I don't have too much time to test but channels with > > problems have only one dvb-subtitles stream and are dvb-s. I didn't found > > dvb-s2 channel with sync subtitles problem. But normally I'm using NatGeo > > (UPC, 19.2E) which is broadcasting also dvb-s and only one dvb-subtitles > > stream and no problems is there. > > > >So it is not necessary to upload the problematic recording for me (but > > maybe someone from reelmutimedia will be interested in). I already have > > such. > > > >BR, > > > >Ales > > The reason for this is explained here: > > http://www.linuxtv.org/pipermail/vdr/2008-October/018072.html > > So now we just have to be patient and hope that someone who knows how to > fix it fixes it. > I've read this mail but now I've done test recording 47mins long (National Geographic, UPC, 19.2E) and when replaying it (without using any speed change within replaying) the dvb-subtitles were in sync for whole 47 minutes. So I do not understand why the problems appears only at specific channels. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Syncearly + subtitles problem
On Tuesday 21 of October 2008, Hannu Tirkkonen wrote: > Ales Jurik wrote: > > On Monday 20 of October 2008, Hannu Tirkkonen wrote: > >>> Josce > >> > >> The subtitles and ttxtsubs are in sync when watching live... but > >> The same problem with too early exists on recordings. > >> > >> vdr 1.7.0 with reelbox plugin 9044: > >> VDR-Extensions-Patch-62/vdr-1.7.0_extensions.diff > >> DR-Extensions-Patch-62/vdr-1.7.0-ext_h264.diff > >> vdr170-ext-h264-rmm-svn8858-patch.diff > >> > >> There's a ReplayDelay option on ttxtsubs, but is it > >> possible to get the (customized) delay also for the subtitles as well? > >> > >> ...hanu > > > > I don't see such problem: > > > > vdr-1.7.0 with reelbox plugin 9044 > > - > > vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup > > - vdr170-h264-rmm-svn8858-patch > > > > BR, > > > > Ales > > Just finished the clean installation of vdr-1.7.0 with same patches: > vdr-1.7.0 with reelbox plugin 9044 > vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup > vdr170-h264-rmm-svn8858-patch > > The subtitles and ttxtsubs appears ~ 6 seconds too early. > I can live with the ttxtsubs, because of the option ReplayDelay (5000), > but watching the recordings with subtitles is quite annoying.. > > The recordings with ttxtsubs and subtitles are from Thor (S1.0W) > (dvb-s/dvb-s2) and local Finnish (dvb-c) broadcaster Welho. (Canal > Digital and Yle stuff...) > > I'll try to get a sample recordings uploaded somewhere tomorrow. > I've tried to record 10mins samples from few channels other than I'm normally watching (with dvb-subtitles). It seems to me that recordings from some channels have problems you've reported, from other channels recordings are replayed without problems. The delay (time dvb-subtitles is displayed earlier) seems to be 0 at beginning od such recording and is increased and within 10 mins it reaches up to 6 secs. I'm not sure as I don't have too much time to test but channels with problems have only one dvb-subtitles stream and are dvb-s. I didn't found dvb-s2 channel with sync subtitles problem. But normally I'm using NatGeo (UPC, 19.2E) which is broadcasting also dvb-s and only one dvb-subtitles stream and no problems is there. So it is not necessary to upload the problematic recording for me (but maybe someone from reelmutimedia will be interested in). I already have such. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Syncearly + subtitles problem
On Monday 20 of October 2008, Josce wrote: > At 11:40 20-10-2008 +0200, you wrote: > >On Monday 20 of October 2008, Hannu Tirkkonen wrote: > >> Josce wrote: > >>> I am having problems with subtitles: > >>> > >>> - vdr 1.6.0 > >>> - > >>> vdr-1.5.18-h264-syncearly-framespersec-audioindexer-fielddetection-spee > >>>dup.diff - vdr-1.6.0-truecolor-compile_fixes.diff - reelbox plugin > >>> > >>> > >>> > >>> The subtitles appear 6-10 seconds too early, which is really annoying. > >>> Tested the recordings on a vdr 1.6.0 + FF without the patches and the > >>> subtitles were displayed correctly. > >>> I imagine it has something to do with the syncearly, but can't say for > >>> sure. Can I somehow disable the syncearly part of the patches to verify > >>> that this indeed is the problem. ( I need the patches because I can't > >>> compile vdr + reelbox plugin without them ) > >> > >> The subtitles and ttxtsubs are in sync when watching live... but > >> The same problem with too early exists on recordings. > >> > >> vdr 1.7.0 with reelbox plugin 9044: > >> VDR-Extensions-Patch-62/vdr-1.7.0_extensions.diff > >> DR-Extensions-Patch-62/vdr-1.7.0-ext_h264.diff > >> vdr170-ext-h264-rmm-svn8858-patch.diff > >> > >> There's a ReplayDelay option on ttxtsubs, but is it > >> possible to get the (customized) delay also for the subtitles as well? > > > >I don't see such problem: > > > >vdr-1.7.0 with reelbox plugin 9044 > >- > > vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup > > - vdr170-h264-rmm-svn8858-patch > > Glad to hear that it works for you :) > > Checked out reelbox plugin 9053 and I still have the problem. > When and where was this fixed? Should I re-install all reelbox files? > > If I want to apply a quick fix, how can I delay the subtitles? > The subtitles seems to be 6-7 seconds too early. > I have recorded a very good German film that I'd like to watch, but > my German is still not good enough so sometimes I need a little > help from the subtitles to be able to follow the plot > > Having said that, a setting that would enable me to always have the > subtitles delayed a little would be a very nice feature. This would > help me improve my German. When watching German films I could always > first try to understand the speech and when there is something that I > don't understand I could read the subtitles. Coul'd you upload part of that problematic recordings (approx. 100MB) somewhere - I could try to test it in my environment. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Syncearly + subtitles problem
On Monday 20 of October 2008, Hannu Tirkkonen wrote: > Josce wrote: > > I am having problems with subtitles: > > > > - vdr 1.6.0 > > - > > vdr-1.5.18-h264-syncearly-framespersec-audioindexer-fielddetection-speedu > >p.diff - vdr-1.6.0-truecolor-compile_fixes.diff > > - reelbox plugin > > > > The subtitles appear 6-10 seconds too early, which is really annoying. > > Tested the recordings on a vdr 1.6.0 + FF without the patches and the > > subtitles were displayed correctly. > > I imagine it has something to do with the syncearly, but can't say for > > sure. Can I somehow disable the syncearly part of the patches to verify > > that this indeed is the problem. ( I need the patches because I can't > > compile vdr + reelbox plugin without them ) > > > > Josce > > The subtitles and ttxtsubs are in sync when watching live... but > The same problem with too early exists on recordings. > > vdr 1.7.0 with reelbox plugin 9044: > VDR-Extensions-Patch-62/vdr-1.7.0_extensions.diff > DR-Extensions-Patch-62/vdr-1.7.0-ext_h264.diff > vdr170-ext-h264-rmm-svn8858-patch.diff > > There's a ReplayDelay option on ttxtsubs, but is it > possible to get the (customized) delay also for the subtitles as well? > > ...hanu I don't see such problem: vdr-1.7.0 with reelbox plugin 9044 - vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup - vdr170-h264-rmm-svn8858-patch BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 170 & multifrontend support
On Sunday 12 of October 2008, Goga777 wrote: > > > which plugin/addons/patch for vdr I have to use for FM radio of my > > > hvr4000 ? > > > > No idea... > > pity :( > > I never tried the FM radio of my card, but for example for > > > analog TV, tvtime works just great (in parallel to VDR). > > as far as I understand you - on vdr ther's not any possibility to see > analog TV with hvr4000 , too ? it's very pity > > Goga I didn't try the analog TV in vdr, but there is one old plugin - http://www.ko0l.de/download/vdr/analogtv/index.html (sw encoding to MPEG-1) and one (also not very new) which is using HW encoding to MPEG-2 for PVR-150 or PVR-250 cards - http://home.arcor.de/andreas.regel/files/pvrinput/. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Syncearly + subtitles problem
On Wednesday 08 of October 2008, Josce wrote: > >Which version of reelbox plugin (i.e. from which svn) are you using? There > > was some changes (from 8072) regarding sublitles. > > > >Did you test it with latest reelbox svn? > > The reelbox-plugin is 8171. > I can test with a newer svn if you think that will help. > > regards, > > Josce As I remember there was another problem - with audio/video sync. The sound was delayed more and more - I've patched the plugin myself to disable the audio/video sync algorithm. But in last versions (I'm now using the 8649 version) it is ok. So it is maybe second reason of your problem. You could test if immediately after switching to the channel the sync of subtitles is good or significantly better then after some time (1-2 minutes) it could be the sync problem. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Syncearly + subtitles problem
On Wednesday 08 of October 2008, Josce wrote: > I am having problems with subtitles: > > - vdr 1.6.0 > - > vdr-1.5.18-h264-syncearly-framespersec-audioindexer-fielddetection-speedup. >diff - vdr-1.6.0-truecolor-compile_fixes.diff > - reelbox plugin > > The subtitles appear 6-10 seconds too early, which is really annoying. > Tested the recordings on a vdr 1.6.0 + FF without the patches and the > subtitles were displayed correctly. > I imagine it has something to do with the syncearly, but can't say for > sure. Can I somehow disable the syncearly part of the patches to verify > that this indeed is the problem. ( I need the patches because I can't > compile vdr + reelbox plugin without them ) > > Josce Which version of reelbox plugin (i.e. from which svn) are you using? There was some changes (from 8072) regarding sublitles. Did you test it with latest reelbox svn? BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.18 subtitles issue
On Wednesday 10 of September 2008, Klaus Schmidinger wrote: > On 09/10/08 22:21, Stefan Lucke wrote: > > On Saturday 06 September 2008, matthieu castet wrote: ... > > In vdr 1.5.12 maximum number of subtitles and audio languages > > could be set to 23. With vdr-1.6.0 I can select one more language > > (24 displayed as 2 boxes due to a font issue). After a vdr restart, > > number of languages is reset to 23 ;-) . > > Does this mean that there is an actual problem in VDR >= 1.6.0 that > needs to be looked into, or was this solved with the fix in softdevice? I don't have any problems with subtitles in vdr-1.7.0 + eHD except timeout for clearing subtitle in eHD OSD, but it doesn't seems to be vdr-related, rather reelbox plugin problem. BR Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] some problem with hdtv channels from Eurobird 9E
On Monday 08 of September 2008, Goga777 wrote: > Hi > > there's several open hdtv channels on Eurobird 9e > > MelodyZen.tv;EUTELSAT:11804:VO0S0:S9.0E:27500:3321:3322=NAT,3323=MUS,3324=e >ng,3326=fra:0:0:332:158:158:0 LUXE.TV > HD;DVL.TV:11804:VO0S0:S9.0E:27500:3011:3013=fra,3014=eng,3015=deu,3016=ita, >3017=rus,3018=esl:0:0:301:158:158:0 LUXE.TV UK > HD;DVL.TV:11804:VO0S0:S9.0E:27500:3041:3044=eng;3043=eng:0:0:304:158:158:0 > > > but with each channels I have the problem on my vdr 170 + xineliboutput + > svn ffmpeg > > On MelodyZen I have jerking pictures with slow motion > > in the log I have > > 200 frames delivered, 78 frames skipped, 0 frames discarded > video_out: throwing away image with pts 10711859 because it's too old (diff > : 4105). 200 frames delivered, 75 frames skipped, 1 frames discarded > 200 frames delivered, 80 frames skipped, 0 frames discarded > 200 frames delivered, 81 frames skipped, 0 frames discarded > 200 frames delivered, 79 frames skipped, 0 frames discarded > 200 frames delivered, 79 frames skipped, 0 frames discarded > > > I tried to record this channels and playback again by vdr - I have the same > problem. But if I will try to play this file by ffplay - I don't this > problem - the video is smoothly. It's seems there's problem with > xineliboutput or xine-lib-1.2 > > > the other hdtv channels > > LUXE.TV > HD;DVL.TV:11804:VO0S0:S9.0E:27500:3011:3013=fra,3014=eng,3015=deu,3016=ita, >3017=rus,3018=esl:0:0:301:158:158:0 LUXE.TV UK > HD;DVL.TV:11804:VO0S0:S9.0E:27500:3041:3044=eng;3043=eng:0:0:304:158:158:0 > > have the problem as well. > > > BUT > > with szap2 & ffplay I can see this channels without any problem > > ./szap2 -c 9 -n4 -r -p > cat /dev/dvb/adapter0/dvr0 | ffplay - > > could someone test these hdtv channels > > > Goga Hi, no problem here with vdr-1.7.0 + h.264 patch +eHD MelodyZen.tv;EUTELSAT:11804:vC34M2O0S0:S9.0E:27500:3321:3322=NAT,3323=MUS,3324=eng,3326=fra:0:0:332:158:158:0 LUXE.TV HD;DVL.TV:11804:vC34M2O0S0:S9.0E:27500:3011:3013=fra,3014=eng,3015=deu,3016=ita,3017=rus,3018=esl:0:0:301:158:158:0 LUXE.TV UK HD;DVL.TV:11804:vC34M2O0S0:S9.0E:27500:3041:3044=eng;3043=eng:0:0:304:158:158:0 BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR Development
On Saturday 06 of September 2008, Davide Cavalca wrote: > Il giorno sab, 06/09/2008 alle 02.58 +0200, [EMAIL PROTECTED] ha > > scritto: > > but vdr has not evolved for years ! > > no real new features, it's still meant to be used with one ff dvb-s > > card. there's a plugin interface but most of the time you don't want > > to hear about bugs when somebody is using a plugin. > > what's the point then ? > > And, what about this blackmail thing ? > > Wouldn't it be simpler to say "i don't have time anymore, my needs won't > > evolve and i don't want to code features i won't use, please carry on !" > > ? > > I'm neither Klaus not a regular of this list, but I think you're not > being fair here: Klaus has every right to say he won't develop on a > community tree; it is, after all, his own free time. BTW, if I remember > well, Klaus has coded several features (i.e. subtitles) he himself said > he didn't use. > Like it or not, VDR is a "cathedral"-style project: this has led to > higher code quality and very good stability, at the expense of a slower > development pace and the lack of some bleeding-edge features in the > mainline. If you want those features, you can use a patch posted on this > list (e.g. for hdtv, sourcecaps) or use a plugin (e.g. for teletext > subtitles). Many distributions include those patches or provide a way > for the user to easily appy them. Of course, you're also free to develop > your own patches for new features: if they're good enough, I'm sure > they'll eventually find their way into the mainline, as it happened, > e.g., with the shutdown handling rewrite some time ago. > > You say you want to fork it: what would you accomplish with that? It's > not as if the code would magically write itself. I've yet to see a > single prospective developer say "if it were forked I'd write X". (And, > BTW, there's nothing forbidding him to write X in form of a patch and > post it on this list.) On the other hand, by forking you'd probably lose > Klaus, who has written by himself the majority of VDR code and knows it > like no one else. > > Finally, I personally fail to see why people switching to MythTV is a > bad thing; VDR is not a religion, I think everyone should use whichever > software he thinks suits best his needs. I'm very happy with VDR and > won't be switching anytime soon. > I wanted to tell my opinion to this list too, but I 100% agree with you Davide and I think I'm not able to tell it better way. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr + gotoXX (USALS) (was - HVR4000)
On Tuesday 02 of September 2008, Goga777 wrote:
> Hi
>
> could you download please this gotoxx-patches for vdr 160 & vdr 170
> somewhere As far as I understand no need to insatll rotor-plugin with these
> patches foe gotoxx/usals thanks
>
> Goga
HI,
ok, I hope that Seppo will not be very disappointed ;) .
Attached diffs are against plain versions of vdr.
So, the goal of this patch is possible to read at
http://www.linuxtv.org/pipermail/vdr/2008-March/016164.html.
The diseqc.conf should be like Seppo wrote in his file
http://www.linuxtv.org/pipermail/vdr/attachments/20080315/ae33847e/attachment-0001.txt.
I'm using it with diseqc switch (EMP S164) and diseqc motor (Stab HH 120).
Motor is at 4th position of the switch. Two weeks ago when I've had the TT
S2-3200 this combination was very unreliable (so sometime I had no feel to
which position my motor is pointing). Now, with HVR-4000 I have no problems.
Maybe new version of Igor Liplianin's multiproto will work also with TT
S2-3200 but I didn't test it.
I'm using for 4th input of the switch and my diseqc.conf entries are like
this:
S0.8W 11700 V 9750 t v W15 [E0 10 38 FC] W150 G v t
S0.8W 9 V 10600 t v W15 [E0 10 38 FD] W150 G v T
S0.8W 11700 H 9750 t V W15 [E0 10 38 FE] W150 G V t
S0.8W 9 H 10600 t V W15 [E0 10 38 FF] W150 G V T
S4.0W 11700 V 9750 t v W15 [E0 10 38 FC] W150 G v t
S4.0W 9 V 10600 t v W15 [E0 10 38 FD] W150 G v T
S4.0W 11700 H 9750 t V W15 [E0 10 38 FE] W150 G V t
S4.0W 9 H 10600 t V W15 [E0 10 38 FF] W150 G V T
for all positions to which I want to move the dish.
BR,
Ales
diff -ruNp vdr-1.6.0.orig/config.c vdr-1.6.0/config.c
--- vdr-1.6.0.orig/config.c 2008-02-17 14:39:00.0 +0100
+++ vdr-1.6.0/config.c 2008-03-24 18:39:14.032327377 +0100
@@ -229,6 +229,11 @@ cSetup::cSetup(void)
LnbFrequLo = 9750;
LnbFrequHi = 10600;
DiSEqC = 0;
+ UseGotox = 0;
+ GotoxSpeed = 100;
+ GotoxRepeat = 0;
+ GotoxSN = 0; GotoxLat = 613; GotoxEW = 1; GotoxLong = 236; // Somewhere at Tampere, Finland :^)
+ GotoxPrevSource = 0;
SetSystemTime = 0;
TimeSource = 0;
TimeTransponder = 0;
@@ -402,6 +407,14 @@ bool cSetup::Parse(const char *Name, con
else if (!strcasecmp(Name, "LnbFrequLo")) LnbFrequLo = atoi(Value);
else if (!strcasecmp(Name, "LnbFrequHi")) LnbFrequHi = atoi(Value);
else if (!strcasecmp(Name, "DiSEqC")) DiSEqC = atoi(Value);
+ else if (!strcasecmp(Name, "UseGotox"))UseGotox = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxSpeed")) GotoxSpeed = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxRepeat")) GotoxRepeat= atoi(Value);
+ else if (!strcasecmp(Name, "GotoxSN")) GotoxSN= atoi(Value);
+ else if (!strcasecmp(Name, "GotoxLat"))GotoxLat = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxEW")) GotoxEW= atoi(Value);
+ else if (!strcasecmp(Name, "GotoxLong")) GotoxLong = atoi(Value);
+ else if (!strcasecmp(Name, "GotoxPrevSource")) GotoxPrevSource= atoi(Value);
else if (!strcasecmp(Name, "SetSystemTime")) SetSystemTime = atoi(Value);
else if (!strcasecmp(Name, "TimeSource")) TimeSource = cSource::FromString(Value);
else if (!strcasecmp(Name, "TimeTransponder")) TimeTransponder= atoi(Value);
@@ -485,6 +498,14 @@ bool cSetup::Save(void)
Store("LnbFrequLo", LnbFrequLo);
Store("LnbFrequHi", LnbFrequHi);
Store("DiSEqC", DiSEqC);
+ Store("UseGotox", UseGotox);
+ Store("GotoxSpeed", GotoxSpeed);
+ Store("GotoxRepeat",GotoxRepeat);
+ Store("GotoxSN",GotoxSN);
+ Store("GotoxLat", GotoxLat);
+ Store("GotoxEW",GotoxEW);
+ Store("GotoxLong", GotoxLong);
+ Store("GotoxPrevSource",GotoxPrevSource);
Store("SetSystemTime", SetSystemTime);
Store("TimeSource", cSource::ToString(TimeSource));
Store("TimeTransponder",TimeTransponder);
diff -ruNp vdr-1.6.0.orig/config.h vdr-1.6.0/config.h
--- vdr-1.6.0.orig/config.h 2008-03-23 11:26:10.0 +0100
+++ vdr-1.6.0/config.h 2008-03-24 18:39:14.020326693 +0100
@@ -215,6 +215,14 @@ public:
int LnbFrequLo;
int LnbFrequHi;
int DiSEqC;
+ int GotoxRepeat;
+ int GotoxSN;
+ int GotoxEW;
+ int GotoxSpeed;
+ int GotoxLat;
+ int GotoxLong;
+ int UseGotox;
+ int GotoxPrevSource;
int SetSystemTime;
int TimeSource;
int TimeTransponder;
diff -ruNp vdr-1.6.0.orig/diseqc.c vdr-1.6.0/diseqc.c
--- vdr-1.6.0.orig/diseqc.c 2008-02-10 15:09:27.0 +0100
+++ vdr-1.6.0/diseqc.c 2008-03-24 18:39:14.068329428 +0100
@@ -114,6 +114,7 @@ cDiseqc::eDiseqcActions cDiseqc::Execute
case 'V': return daVoltage18;
case 'A': return daMiniA;
case 'B': return daMiniB;
+ case 'G': retu
Re: [vdr] HVR4000
On Tuesday 02 of September 2008, Goga777 wrote: > > > Does anyone successfully run the Hauppauge HVR4000 with vdr ? > > > > > > regards > > > > > > Pierre > > > > Hi, > > > > I'm running it with vdr-1.7.0 and some patches (h.264 and gotoX) together > > with diseqc switch and motor. > > > > No problems, Hi, I'm using newer version of a patch which can be found at http://www.linuxtv.org/pipermail/vdr/2008-March/016164.html. I have version for vdr-1.6.0 but now I'm not sure if I downloaded it from somewhere or made it myself, I couln't find vdr-1.6.0-gotox.diff anywhere. When applied this patch to vdr-1.7.0 there are some rejects but there is no problem to fix it by hand. I'll try to make newer version (for 1.7.0) and send it to Seppo to review it, as this is basically not work of mine. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HVR4000
On Monday 01 of September 2008, Pierre-Yves Paranthoën wrote: > Hi, > > Does anyone successfully run the Hauppauge HVR4000 with vdr ? > > regards > > Pierre Hi, I'm running it with vdr-1.7.0 and some patches (h.264 and gotoX) together with diseqc switch and motor. No problems, BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recommended xine settings for Arte HD ?
On Monday 01 of September 2008, Gregoire Favre wrote: > > Edit the source, recompil, install. > > I changed this : > grep BUFSIZE *|grep MEGABYTE > dvbplayer.c:#define PLAYERBUFSIZE MEGABYTE(4) > recorder.c:#define RECORDERBUFSIZE MEGABYTE(20) > transfer.c:#define TRANSFERBUFSIZE MEGABYTE(8) > > My computer has 4Gb of ram so I can be large... Thanks Gregoire for your info. It seems to me that it help me with some stalling at specific channles. My PC has also 4GB :) . BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Is any way to specify specific DVB-S card in channel.conf
On Thursday 07 of August 2008, Vladimir Kangin wrote: > Dear All, > > Is any way to specify specific DVB-S card in channel.conf in a way that > some channels are sourced via /dev/dvb/adapter0 and other channels > sourced via /dev/dvb/adapter1 > > Thanking in advance, > Vladimir Kangin You should look for Sourcecap patch. I'm not using it so I don't know where to get it. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel update on vdr 1.7.0
On Thursday 22 of May 2008, C.Scheeder wrote: > Brian schrieb: > Hi, > there are two versions of lnb's with 4 outputs sold, > one with 4 identical outputs to feed 4 seperate receivers, (or diseq-c > switches) This is labeled QUAD, is a little more expansive > and one with outputs for hi/V lo/V hi/H and Lo/H ment to feed > multiswitches. (like the spaun meintioned in another answer...) This is labeled QUATTRO, is a little cheaper > so beware which version you by, the purpose is always written down on the > box. Christoph > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] open dvb-s2 channel on Hotbird - Eurosport HD Promo
On Tuesday 20 of May 2008, Gregoire Favre wrote: > > My CPU (P-4 3Ghz) is very slow for 1080x1920, but I could see the tennis > > on this channel one hour ago > > Oh nice, mine should be powerfull enough, but I stay for quiete a long > time under ESP HD Intl and it stay black... what's strange is that my > VDR isn't able to tune to those, I can't get a lock : > May 20 23:05:59 vdr vdr: [19468] frontend 1 timed out while tuning to > channel 6511, tp 211278 May 20 23:07:09 vdr vdr: [19468] frontend 1 timed > out while tuning to channel 6511, tp 211278 > > Maybe they don't broadcast now ? Don't you have TT S2-3200 or SkystarHD? The problem is in driver (multiproto) for those cards. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.16
On Friday 07 of March 2008, Seppo Ingalsuo wrote: > But as vdr illiterate I couldn't figure how to check if the zapped > source (diseqc->source?) is a new one to avoid generating unnecessary > DiSEqC traffic and delays, and wondered to get a global variable for > storing the previous position... help! This seems to be already checked in status.c. I've used debug message to show all diseqc commands send and it seems to work fine (for me). BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.5 .17 - release candidate 2
On Thursday 06 of March 2008, Klaus Schmidinger wrote: > > Sorry, I don't speak Czech, so I can't follow what's going on there. > Hi, there is nothing more than I've tried to put into this maillist except discussion. > With the recent change at least the Czech channels should work > properly again. Can you confirm that? > Yes, I confirm that. Similar solution was proposed by bastlir at the forum (he proposed to comment out the line your patch is deleting). > For version 1.6.0 there's nothing more I can do than using the environment > variable. Maybe later I'll introduce a "workaround-provider-stupidity.conf" > ;-) > I agree with you but I'm afraid that such communications with broadcasters will give no results. This maybe will be successfull when big producers of sat boxes will make such pression too. But it seems that for them is more efficient to make localization which is compliant to broadcasters not to sat norms. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.5.17 - release candidate 2
On Wednesday 05 of March 2008, Malte Schröder wrote: > On Wed, 05 Mar 2008 18:10:59 +0100 > > > > > Users in Germany should please test this, too, and do an > > > > export VDR_CHARSET_OVERRIDE=ISO-8859-9 > > > > before starting VDR. > > > > Klaus > > It seems to me as if we would need a per-channel setting for this ... This is exactly the solution which seems to be commonly forced at www.cssf.cz. The solution is to use config file in encoding.conf format (linux enigma boxes). It could be possible to define encoding not for all channels but only for these which encoding is not well recognized and different from default. I think not only I will be very happy to have such a solution as I'm watching not only Czech channels, but also from other countries. And for example I'm very disappointed to have at one channel German epg without problem (RTL, EinsPlus) and at other (Q TV SHOP) epg badly encoded. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.16
On Wednesday 05 of March 2008, Seppo Ingalsuo wrote: > I couldn't repeat that but I didn't find exactly that multiproto driver. Hi, I'm testing it with this one - http://jusst.de/hg/multiproto/archive/4df151d5b3fe.tar.bz2. I've only changed some print and debug options in my tests. > > But I noticed that zapping works reliably with between channels in > different positions with LNB tone off (frequency < 11700, if I got this > right...). V/H polarization didn't matter (13V or 18V LNB voltage). > There should be 15 ms tone off between DiSEqC messages and continuous > tone that might not happen with rotor plugin and this DVB driver. I > wonder if that could be the reason? > Yes, my fault - I've switched between satellites only on lower band. But with newest version of multiproto also this was not possible. But I'm using it with cascade switch/motor, so my tests could have different results. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.5.17 - release candidate 2
On Sunday 02 of March 2008, Klaus Schmidinger wrote: > - Rendering the non-breaking space symbol as a blank (thanks to Tobias > Grimm). - Changed the default character set for SI data from ISO6937 (as > required by the DVB standard ETSI EN 300 468) to ISO-8859-9, in order to > work around the stupidity of some providers, who actually use ISO-8859-9, > but fail to correctly announce that. Hi Klaus, this change is preventing to use vdr for all Czech/Slovak satellite providers as they broadcast epg in ISO6937 (ok, UPC at 19.2E with some minor errors). This problem is now very intensively discussed at Czech and Slovak Satellite forum (www.cssf.cz). Some users from www.cssf.cz are proposing how to solve the situation in the future, but they agreed not to initiate any changes before version 1.7.0 will be released. Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.16
On Thursday 28 of February 2008, Seppo Ingalsuo wrote: > I'm having problems in getting my diseqc motor positioner to work with > multiproto+h.264 patched vdr 1.5.16. It is at the moment very > unreliable. Most of the time it just stays stuck into the old position > so possibly the commands get corrupted. Is a Technotrend S2-3200 > capable to control a positioner? My old budget-s Tecnotrend was very > reliable in driving the same positioner. I've also had such problem. This weekend I've tried to solve which part of sw is making this diseqc unreliability - and today I've tested the result once more. My result is that the problem with stucked motor appears with new multiproto driver. When I'm using multiproto from 21.12. no problem appears at all. My configuration is Debian Lenny, vdr-1.5.14 with rotor-0.1.4 (vdr-1.5.5-rotor.diff and Rotor-0.1.4-vdr1.5.10.diff patches), diseqc in vdr enabled (I've motor at 4th input of 4-input diseqc switch). BTW - Repeat DiSEqC-Commands must be set to enabled (this seems to be related to my diseqc cascade with switch). Hw is TT S2-3200, AMD Athlon 64 X2 - 5200+. Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] dvd-Plugin kompiliert nicht
Hi, it seems that you're using older version of plugin. Try use for example vdr-dvd-0.3.7_pre20070117 or some newer - and your problem should disappear. Regards, Ales On Saturday 23 of February 2008, Siegfried Haas wrote: > Hallo, > > ich weiß, das meine Anfrage hier off topic ist, aber vielleicht kann mir > einer von Euch helfen. > > Ich habe auf vdr1.4.7 "aufgerüstet" (eine SuSE10,3), und da compiliert > das dvd-plugin nicht. > Fehlermeldung siehe mein Thread in VDR-Portal > > http://www.vdr-portal.de/board/thread.php?threadid=74316 > > Es wäre sehr nett, wenn einer mir einen Tip geben könnte! > > Danke > > Siegfried > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Straw poll: stable version 1.6.0 now?
On Sunday 03 February 2008, Klaus Schmidinger wrote: > So, here's the straw poll: > >Should there be a stable version 1.6.0 now, based on what's in >version 1.5.14, but without DVB-S2 or even H.264 support? > > Yes or No? > > Klaus > Hi Klaus, I vote for DVB-S2/H.264 (HDTV) support. But if it is a problem with some distros could it be there time-compile switch to choose which drivers to use? I thing it would be disadvantage to leave at whole such a well prepared part of vdr. Kind regards Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] #error VDR requires Linux DVB driver API > version 3.3! (was - VDR developer version 1.5.14)
On Tuesday 29 January 2008, Matthias Fechner wrote: > I modified now the Makefile and added the following lines after the > include of the conf file: > ifdef DVBDIR > INCLUDES += -I$(DVBDIR)/include > endif > > For plugins which are using the headerfiles from the new driver I had to > add the three lines too. > > Is that a bug in the VDR Makefile? No, for such purposes there is Make.config.template which should be copied to Make.config (see doc). After line ### You don't need to touch the following: add something like (depends on your configuration) DVBDIR = /usr/local/src/dvb/linux and all will ok. This file is included by all Makefiles (also by plugins). Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patch for 1.5.12
On Sunday 13 January 2008, Morfsta wrote: > Has anyone managed to get the signal strength, SNR and lock functions > working with multiproto and rotor 1.5.12? I took a look at menu.c and > compared it with szap2 but couldn't find much difference! > Hi, I've tried to pass through the source code and it seems to me that problem is that multiproto driver for dvb-s2 frontend return SNR and STR in 0.1dB and the value is by vdr-rotor (and by vdr-femon) then recalculated to dB once more. Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Multiproto problem tuning some channels
Hi, there is very difficult (or practically impossible) to tune some stations with nominal values in channels.conf. But if increasing SR it is possible. It was reported by another user in cssf.cz forum, too. Example: No possible: City TV;Telenor:12169:hC78M2S0Z0:S1.0W:28000:512:640:0:0:1901:70:19:0 Possible: City TV;Telenor:12169:hC78M2S0Z0:S1.0W:28005:512:640:0:0:1901:70:19:0 In all reported cases it was used TT S2-3200. Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.5.13 (and earlier)
On Sunday 13 January 2008, Gregoire Favre wrote: > On Sun, Jan 13, 2008 at 05:08:24PM +0100, Tony Grant wrote: > > I noticed that I could no longer see channels with vertical polarisation > > - this used to work must have stopped last week. > > > > Channels: > > > > BBC 2 England;BSkyB:10773:hC56:S28.2E:22000:... etc. works > > > > ITV1 London;BSkyB:10759:vC56:S28.2E:22000:... blanks screen > > I can't test vdr-1.5.13 because a VDR without DVB-S2 isn't fun at all, > but with vdr-1.5.12 with DVB-S2 support I can perfectly tune to : > > ITV1 > London;BSkyB:10758:vC56S0Z0:S28.2E:22000:2305:2310=eng,2314=NAR:2315:0:1006 >0:2:2044:0 > > Maybe your problem is related to your driver, did you change it ? Hi Gregoire, there is no problem - vdr-1.5.13 is vdr-1.5.12-dvbs2-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff compatible. I'm using it just now ;) . Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patch for 1.5.12
On Thursday 10 January 2008, Reinhard Nissl wrote: > Hi, > > lucian orasanu schrieb: > > it is changed after patch with function above and in > > menu.c at line 304 is expecting another function like > > this: > > > > SChannel->cChannel::SetSatTransponderData(RotorPos->R_Code(),Frequenz,Pol > >,Symbolrate,FEC_AUTO); > > > > so i modified this line in menu.c like this: > > > > SChannel->cChannel::SetSatTransponderData(RotorPos->R_Code(),Frequenz,Pol > >,Symbolrate,Symbolrate,Symbolrate,Symbolrate,Symbolrate); > > Try changing it to: > > SChannel->cChannel::SetSatTransponderData(RotorPos->R_Code(),Frequenz,Pol,S >ymbolrate,DVBFE_FEC_AUTO,DVBFE_MOD_AUTO,DVBFE_DELSYS_DVBS,DVBFE_ROLLOFF_UNKN >OWN); > > You'll need to apply the attached VDR patch instead of the one > included with vdr-rotor. > Hi, I've tested it, it seems that it works - but I have motor behind the switch (port D of 4port) and in some cases the dish doesn't went back to east (with SS1, old driver, old rotor, vdr-1.5.12 no such problem detected). In that case I have to switch to channel which is not behind portD and then back to portD and the dish begin to move. I'm using gotoX functionality. I'm using for testing: - Debian Lenny - TT S2-3200 - HH120 - vdr-1.5.13 patched by vdr-1.5.12-dvbs2-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff, vdr-1.5.12-speedup-fix1.diff and vdr-1.5.12-speedup-fix2.diff. - rotor version vdr-rotor-0.1.4-vdr1.5.7.tgz patched by Rotor-0.1.4-vdr1.5.10.diff and vdr-1.5.12-dvbs2-h264-other-rotor.diff and with changes of SChannel->cChannel::SetSatTransponderData proposed above by Reinhard. Reinhard, if you agree I'm ready to cooperate in testing. Ales > Please keep in mind that I cannot test this patch. The suggested > line above will only support DVB-S. For DVB-S2 and H.264 support, > a lot more needs to be changed. > > Bye. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.1 plugin
On Thursday 03 January 2008, Gregoire Favre wrote: > I did have a rm -fr /usr/include/xine* in my script some times ago which > I removed because I thought it wasn't necessary. > Recompiled : no change. > > So I deleted /usr/lib64/xine/ and it works !!! > I've solved the problem by deleting xineplug_inp_vdr.so from /usr/local/lib/xine/plugins/1.1.90/. The file was outdated (6 days older than all others in this directory) - it looks like rest of some previous version of xine I've compiling before. Thanks for pointing me to the right direction. Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.1 plugin
On Wednesday 02 January 2008, Gregoire Favre wrote: > vdr-xine: Client connecting ... > vdr-xine: Client reports unsupported version 712 => disconnecting! > vdr-xine: Client connect failed! > The same problem had I. In xineCommon.h I've changed MIN_XINE_VDR_VERSION to 712 (from 801) and everything seems to be ok. BTW - in xine-0.8.0 the value of MIN_XINE_VDR_VERSION was 711? Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Frontend 0 timed out while tuning ...
On Monday 31 December 2007, [EMAIL PROTECTED] wrote: > Hi! > > I'm running VDR-1.5.10 patched with a DVB-S2+H.264 patch, my DVB-card is > a HVR4000 using the multiproto tree patched with HVR4000 support. > But I cant get any picture when I try to watch A DVB-S2 channel (DVB-S > works) > ... > CANAL+ FILM > HD;Telenor:11421:hC23:S1.0W:25000:10513+513:644=eng;645=eng:0:B00:3306:70:1 >4:0 CANAL+ SPORT > HD;Telenor:11421:hC23:S1.0W:25000:10514+514:648=sve,649=nor:0:B00:1404:70:1 >4:0 SVT > HD;Telenor:11421:hC23:S1.0W:25000:10512+512:640=sve;641=sve:0:0:3801:70:14: >0 > Hi, regarding to my experiences when trying to get initial tuning to DBV-S2 station you have to tell to the vdr to change modulation standard to DVB-S2. I don't have Conax from Telenor, but you should change your :hC23: entry from station line to something like :hC23M5S1Z35: (guessed). The S1 is the most important part of this entry for initial tuninig. S0 = DVB-S S1 = DVB-S2 Regards, Ales > Is there anyone that can give me a hint where to start looking for the > problem? > > Thanks! > > /Lars > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] UTF8 chars in weekday name
On Tuesday 27 of November 2007, [EMAIL PROTECTED] wrote: > Hello > > I want to describe some minor problem in VDR: > Short weekdays can't contain non ASCII-7 chars. Any other char is converted > to UTF8 (it is correct) and cropped to 6 bytes (not UTF8 chars, incorrect). > But this crop ignote UTF8 extensions. I'd like to confirm this problem. It appears when locale is UTF-8. When locale is not UTF-8 everything is ok. Regards Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] next features?
On Wednesday 21 of November 2007, Klaus Schmidinger wrote: > lists all the CPUs this board supports, and since they are probably > all way faster than I'll actually need, it's probably best to use > the one with the lowest power consumption. > Does anybody know which of these has the lowest power requirements? > Or can point me to a source where I can find that information? > > Klaus Hi Klaus, see for ex. http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors Rgds, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] next features?
On Monday 19 of November 2007, Klaus Schmidinger wrote: > > i bought the p5gc recently; it is the only board with > > 6x PCI, but without onboard graphics. > > Well, I can plug a graphics card into that extra PCI slot. > There is also one extra PCIEx16 slot. > > the only problem so far is the onboard realtek 8169 > > NIC -> works not with the ubuntu 7.10 default kernel! > > (the latest git kernel should work -> not tested yet) > > That's a real pitty. > I wonder if it will work with the default SUSE 10.3 kernel... On Asus web there are drivers for linux (LAN, Audio) which are tested for kernel 2.6.21 and 2.6.22 - the need is kernel source and gcc. Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] next features?
On Sunday 18 of November 2007, Klaus Schmidinger wrote: > Does anybody have a recommendation for such a board? I've found one with four PCI slots, see http://www.asus.com/products.aspx?l1=3&l2=11&l3=307&l4=0&model=1480&modelmenu=1. Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] remote control and nexus-s CI module
Hi, I have CI expansion slot like http://www.dvbshop.cz/?w=produkt&id=80# . There is no jumper regarding any voltage, only one (not marked) which shorted is disabling IR input on the SS1 card and enabling the IR diode (as IR input) in the hole at right side of CI slots and vice versa. If CI slot (and CAM) are PCMCIA compatible the voltage should be chosen automatically. I'm not sure which voltage should be set for CI CRW. Ales On Tuesday 30 of October 2007, [EMAIL PROTECTED] wrote: > This is my CI module: > http://www.linuxtv.org/vdrwiki/images/d/dd/Pci-ci-Rev1.4.jpg > > BTW: for a Crytpoworks CAM the voltage should be 3 or 5V? > > Thanks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] remote control and nexus-s CI module
Unconnect jumper on CI module - by shorted jumper the IR sensor is at front of CI module. Hi, Ales On Monday 29 of October 2007, [EMAIL PROTECTED] wrote: > Hello, > > My issue is not strictly VDR related, but I'm using my DVB card > exclusively with VDR for about 2 years. > I have a nexus-s FF card with Hauppauge grey remote, and it's working ok. > Recently I added a CI module to my sistem (with a Cryptoworks module). If > the CI is connected with the flat cable to the FF daughterboard the remote > stops working, although it is detected when i'm loading the dvb driver > (dvb_ttpci) as av_7110_ir controller, and I have /dev/input/event3 but the > rc is no more detected by the remote plugin. > Any hint? > > Thanks, > Istvan > > BTW: Klaus, thanks for the subtitle support! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] future VDR and Net??eiver OEM from Reelmultimedia
On Friday 29 June 2007 07:45, Jeremy Jones wrote: > On 6/27/07, Georg Acher <[EMAIL PROTECTED]> wrote: > > On Wed, Jun 27, 2007 at 09:17:03PM +0100, Torgeir Veimo wrote: > > > On 27 Jun 2007, at 20:51, Igor wrote: > > > >Hello > > > > > > > >http://reel-multimedia.com/rmm-english/netceiver.html > > > >here's a good platform for future hdtv-vdr > > > >Are you agree ? :) > > > > > > Well, what's missing there is info about the "1x extra PCI slot for > > > HD-Decoder-Card". Having a PCI decoder for mpeg2/4/h.264 would be > > > fine, unles it's actually a mini-pci card that only works with reels > > > netceiver external tuner hardware. > > > > The HDTV decoder card in PCI format will be first used for the Reelbox > > Avantgarde (based on a Mini-ITX-PC). The usage in the NetCeiver itself in > > a > > PC-less combo is planned, but I don't think a vdr can run on that > > platform without serious restrictions. For example, the NetCeiver with > > its current firmware has no real DVB-API, as the CPU has nothing to do > > with the TS streaming, it only controls the tuners. The rest (filtering > > and network encapsulation) is done in the hardware. So it will be more a > > small STB application without bells and whistles,. > > > > But the chances are high that the HD card (running with the Micronas > > DeCypher) will be seperately available. As the Reelbox uses vdr, Linux > > drivers for the HD card and the NetCeiver (a DVB-API emulation and a vdr > > plugin with more features) will be there from the start. > > Is there any information regarding availability or pricing on the HDTV PCI > card ? I have been waiting a long time for an HD MPEG-2/4 decoder with > HDMI and this sounds promising :-) > > Thanks, > Brian See http://www.vdr-portal.de/board/thread.php?threadid=45922 . I'm waiting for it, but no info is available for some time. Maybe someone has any news? Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
