Re: [vdr] HD clients for vdr
the main reason why nvidia chooses to deinterlace always even if you use an interlaced video timing is not the scaling problem you mention. This could be eventually solved (albeit not perfectly) by scaling both fields independently. The main reason is: even with VDPAU there still exists no synchronization between stream and video timing. is it possible to solve radically this problem with vdpau ? did you discuss with nvidia developpers about this issue ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] gotoX patch vdr 1.7.8
hi I tried to use the gotox patch (thanks to Seppo Ingalsuo and Ales Jurik) for vdr 178 http://www.linuxtv.org/pipermail/vdr/2009-June/020800.html I have this scheme vdr with hvr4000 card --- rotor 4x1 diseqc switch --- LNB Ku band Linear + LNB Ku band Circular + LNB С band Circular my diseqc.conf (for Ku circular) is S36.0E 0 V 10750 t v [E0 10 38 F4] W150 G v t S36.0E 9 V 10750 t v [E0 10 38 F5] W150 G v t S36.0E 0 H 10750 t V [E0 10 38 F6] W150 G V t S36.0E 9 H 10750 t V [E0 10 38 F7] W150 G V t but it seems something is wrong - I don't see anything questions - how to log the diseqc command for more investigations ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD clients for vdr
Приветствую, Vladimir Is it AMD (ATI) have the same problem? yes. but for ati and intel there's solution from Thomas - see http://www.forum.free-x.de/wbb/index.php?page=ThreadpostID=2576#post2576 http://lowbyte.de/vga-sync-fields/vga-sync-fields/ Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] gotoX patch vdr 1.7.8
I have this scheme vdr with hvr4000 card --- rotor 4x1 diseqc switch --- LNB Ku band Linear + LNB Ku band Circular + LNB С band Circular my diseqc.conf (for Ku circular) is S36.0E 0 V 10750 t v [E0 10 38 F4] W150 G v t S36.0E 9 V 10750 t v [E0 10 38 F5] W150 G v t S36.0E 0 H 10750 t V [E0 10 38 F6] W150 G V t S36.0E 9 H 10750 t V [E0 10 38 F7] W150 G V t Does the dish turn? honestly - I don't know because the dish is on the roof of my home - I don't have access to it currently I wonder if the order of G and [E0 10 38 xx] switch command matters? Have you enabled diseqc.conf usage from vdr lnb setup menu? yes You could set it to no as well to eliminate diseqc.conf for a while to just see if the dish is moving. I suppose it should because it's not behind the switch in your setup. have you ideas about how can I see in the log the disecs commands from vdr to dish ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] gotoX patch vdr 1.7.8
honestly - I don't know because the dish is on the roof of my home - I don't have access to it currently OK, that makes debugging more complicated. I connected the ampermeter for measure the current in dish cable and found out that no any problem with software - when I are moving between satellite the current is arising from 120 ma to 200-300 ma. But I don't have lock. I suppose that my dish installed not so correctly - that's why I should play with altitude and latitude. I will do. have you ideas about how can I see in the log the disecs commands from vdr to dish ? I don't know of logging but it should be with your diseqc.conf as simple as: tone on/off voltage 13/18 E0 10 38 xx wait 150 ms G becomes voltage 18 tone off wait 20ms EO 31 6E yy zz if repeated wait 20 ms E1 31 6E yy zz wait dish turn for 100 ms ... 100s (e.g.) tone on/off voltage 13/18 Did you have this working with some other vdr setup or set to box? no, I have only these logs Aug 22 20:21:19 arvdr vdr: [3218] DiSEqC GotoX -192 (35008) - -360 (35176), wait time 1.7s Aug 22 20:21:22 arvdr vdr: [3218] DiSEqC GotoX done. Aug 22 20:21:27 arvdr vdr: [3195] warning: Moving dish to 19.2E - 1s Aug 22 20:21:29 arvdr vdr: [3195] warning: Moving dish to 36.0E - 1s Aug 22 20:21:31 arvdr vdr: [3218] frontend 0 timed out while tuning to channel 13, tp 112303 Aug 22 20:21:36 arvdr vdr: [3195] switching to channel 14 Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
I'm trying to do just that. A separate install for vdr and xbmc. No integration for me now, since the plugins functionality is lost. A few methods are described here - http://www.xbmc.org/forum/showthread.php?t=47560. with that scrip you can run vdr or xbmc independently !/bin/bash export LANG=ru_RU.UTF-8 export LC_ALL=ru_RU.UTF-8 /usr/src/VDR/vdr --lirc --localedir=/usr/src/VDR/locale -s /etc/vdr/vdrpoweroff.sh -v /video -c /etc/vdr -u root -L /usr/src/VDR/PLUGINS/lib -Pxine -r while [ 1 -eq 1 ]; do svdrpsend.pl remo on xine -f --post vdr_video --post vdr_audio --post upmix_mono --verbose=2 -V vdpau -A alsa vdr:/tmp/vdr-xine/stream#demux:mpeg_pes svdrpsend.pl remo off xbmc -fs -l done ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
Of course it has limitations, it's a very young project. But it's progressing very fast sure and I think, given some time, that I will eventually abandon xinelib. and vdr too ?:-) Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD clients for vdr
Well, my ION board with 9400m does temporal deinterlacing of 1080i HDTV just fine in xbmc. did you try the temporal_spatial with 1080i ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD clients for vdr
Well, my ION board with 9400m does temporal deinterlacing of 1080i HDTV just fine in xbmc. did you try the temporal_spatial with 1080i ? Hi Goga. No, it's not available in xbmc. do you know - why so limited ? For some reason xineliboutput has never worked as well for HD as xbmc does. sorry, what do you mean ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] mplayer plugin - INFO: Source Video has Resolution of 0 x 0
I couldn't play with mplayer plugin the ts-files recorded on VDR 178 Jul 11 17:36:29 arvdr logger: *** DEBUG: MPLAYER_RETURN: 0 Jul 11 17:36:30 arvdr logger: *** INFO: Source Video has Resolution of 0 x 0 ... Jul 11 17:36:30 arvdr logger: *** FATAL: something went wrong analyzing the video; check your mplayer version ... any ideas ? Try to use a number 0 for the -frames parameter in line 277 of the mplayer.sh script, e.g. 10. Does this help? sorry, currently I can't check - I uninstalled mplayer plugin and moved to XBMC + VDR Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] text2skin and missing tokens
Hi
how is it possible to implement in text2skin-based skin follow information -
which tokens is it possible to use for it ?
- transponders parameters
- bitrate and resolution
- type of system encryption
- BER
- video format - 16:9 or 4:3
- audio format (AC-3)
- what's token {VideoAR} {ReplayVideoAR} ?
We would like to implement that feature in new text2skin based skin - AVP
http://www.forum.free-x.de/wbb/index.php?page=ThreadpostID=4804#post4804
Goga
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Patches for VGA timing not matching up with the TV (was: HD output - your current favourites)
I'm wondering - does the problem with timing and sync also important and for for vdpau nvidia cards ? or that project is important only for intel and ati ? Now that I think about it, I believe this is what I was really asking about.. is it perhaps that good LCD TVs have so much smoothing/deinterlacing processing circuitry that the interlace timing is less of a problem when provided by VGA or HDMI? but to run nvidia geforce 8/9 series cards with 1080i 50Hz mode is not so easy or could you run 1080i mode on vdpau card with good result ? At least you should be able to run 1080p50 and let vdpau do deinterlacing for you.. I believe it should be possible to get 50 fps progressive output from 50i material using vdpau deinterlacing. yes, my PCI Geforce 8400 card on GPU G98 can do 10...@50 but with the simplest bob deinterlacing only. I prefer to use more advanced deinterlacing algorithm - temporal_spatial or temporal. But with them I have jerky video .. But you might get better results if you outputted 1:1 interlaced material using 1080i50 mode and let the LCD tv do the deinterlacing.. Yes, exactly what I want to try, But I couldn't run properly 10...@50 - even in xorg.log I have the report about validated 10...@50 mode - my LCD TV Philips 9703PFL reported about 1080p source from hdmi Not sure if that's possible with Nvidia hardware/drivers. http://us.download.nvidia.com/XFree86/Linux-x86/185.18.29/README/chapter-19.html yes it's possible Chapter 19. Programming Modes The NVIDIA Accelerated Linux Graphics Driver supports all standard VGA and VESA modes, as well as most user-written custom mode lines; double-scan modes are supported on all hardware. Interlaced modes are supported on all GeForce FX/Quadro FX and newer GPUs, and certain older GPUs; the X log file will contain a message Interlaced video modes are supported on this GPU if interlaced modes are supported. Note that when validating interlaced mode timings, VertRefresh specifies the field rate, rather than the frame rate. For example, the following modeline has a vertical refresh rate of 87 Hz: # 1024x768i @ 87Hz (industry standard) ModeLine 1024x768 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace Goga Linux/VDR форум http://www.forum.free-x.de/wbb/index.php?page=Portal ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Patches for VGA timing not matching up with the TV (was: HD output - your current favourites)
I'm wondering - does the problem with timing and sync also important and for for vdpau nvidia cards ? or that project is important only for intel and ati ? Now that I think about it, I believe this is what I was really asking about.. is it perhaps that good LCD TVs have so much smoothing/deinterlacing processing circuitry that the interlace timing is less of a problem when provided by VGA or HDMI? but to run nvidia geforce 8/9 series cards with 1080i 50Hz mode is not so easy or could you run 1080i mode on vdpau card with good result ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] osd legend - frontend 0 timed out while tuning to channel
Hi does it possible to implement in OSD VDR such legend frontend timed out while tuning to channel or something like this ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] bitstreamout plugin for vdr 1.7.8
is it need to use bitstreamout plugin
http://downloads.sourceforge.net/sourceforge/bitstreamout/vdr-bitstreamout-0.89b.tar.bz2?use_mirror=sunet
for vdr 178 and vdr-xine 093 ?
Xine-lib handles encoded formats such as AC3 and DTS over S/PDIF. No
vdr plugins are required. Try to set up AC3 audio from DVD first with
gxine or other xine UI player. There is a pass-trough option somewhere.
yes, in xine config there's some options
but they couldn't help me :9
I can listen mono and stereo audio through spdif and can't listen anything if I
switch on DD audio tarck
# device used for mono output
# string, default: default
audio.device.alsa_default_device:iec958:CARD=V8237,DEV=0
# device used for stereo output
# string, default: plug:front:default
audio.device.alsa_front_device:iec958:CARD=V8237,DEV=0
# alsa mixer device
# string, default: PCM
#audio.device.alsa_mixer_name:PCM
# sound card can do mmap
# bool, default: 0
#audio.device.alsa_mmap_enable:0
# device used for 5.1-channel output
# string, default: iec958:AES0=0x6,AES1=0x82,AES2=0x0,AES3=0x2
audio.device.alsa_passthrough_device:iec958:CARD=V8237,DEV=0
# device used for 4-channel output
# string, default: plug:surround40:0
audio.device.alsa_surround40_device:plug:surround40:iec958:CARD=V8237,DEV=0
# device used for 5.1-channel output
# string, default: plug:surround51:0
audio.device.alsa_surround51_device:plug:surround51:iec958:CARD=V8237,DEV=0
# speaker arrangement
# { Mono 1.0 Stereo 2.0 Headphones 2.0 Stereo 2.1 Surround 3.0 Surround
4.0 Surround 4.1 Surround 5.0 Surround
audio.output.speaker_arrangement:Pass Through
# offset for digital passthrough
# numeric, default: 0
#audio.synchronization.passthrough_offset:0
# play audio even on slow/fast speeds
# bool, default: 0
#audio.synchronization.slow_fast_audio:0
# method to sync audio and video
# { metronom feedback resample }, default: 0
#audio.synchronization.av_sync_method:metronom feedback
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] bitstreamout plugin for vdr 1.7.8
Hi is it need to use bitstreamout plugin http://downloads.sourceforge.net/sourceforge/bitstreamout/vdr-bitstreamout-0.89b.tar.bz2?use_mirror=sunet for vdr 178 and vdr-xine 093 ? I don't have AC3 audio from my via8237 integrated sound card, but mono and stereo audio work well with spdif (in vdr setup I turn on the option for use DD) anyway I couldn't compile bitstreamout arvdr:/usr/src/vdr/PLUGINS/src/bitstreamout# make all bitstreamout Version 0.89b g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DPIC -DPLUGIN_NAME_I18N='bitstreamout' -D_GNU_SOURCE -DVERSION=\0.89b\ -DHAS_ASOUNDLIB_H -DHAS_CDEFS_H -DHAS_MAD_H -I../s2-liplianin/linux/include -I../../../include -c bitstreamout.c bitstreamout.c: In member function ‘virtual bool cBitStreamOut::Start()’: bitstreamout.c:239: error: cannot allocate an object of abstract type ‘cReplayOutSPDif’ replay.h:33: note: because the following virtual functions are pure within ‘cReplayOutSPDif’: ../../../include/vdr/audio.h:27: note: virtual void cAudio::PlayTs(const uchar*, int) make: *** [bitstreamout.o] Ошибка 1 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] mplayer plugin - INFO: Source Video has Resolution of 0 x 0
Hi I couldn't play with mplayer plugin the ts-files recorded on VDR 178 Jul 11 17:36:26 arvdr vdr: [3904] mplayer: player thread started (pid=3126) Jul 11 17:36:26 arvdr vdr: [3899] TS buffer on device 1 thread ended (pid=3126, tid=3899) Jul 11 17:36:26 arvdr vdr: [3898] buffer stats: 60912 (2%) used Jul 11 17:36:26 arvdr vdr: [3898] receiver on device 1 thread ended (pid=3126, tid=3898) Jul 11 17:36:26 arvdr logger: *** Starting mplayer.sh Version 0.8.7 Jul 11 17:36:26 arvdr logger: *** DEBUG: Variable CFGFIL has value /usr/bin/mplayer.sh.conf Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable USEAC3 has value false Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable AC3AOUT has value -ao alsa9 -ac hwac3 Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable TV_ASPECT has value 16/9 Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable PAL has value true Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable NTSC has value true Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable USE_SPEED has value true Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable DETC_FILTER has value detc=dr=2:am=1 Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable MPLAYER has value /usr/local/bin/mplayer Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable VOP has value lavc=5000 Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable VO has value vdpau Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable AO has value alsa Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable CACHE has value 4096 Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable CACHESTR has value -cache 4096 Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable FRAMEDROP has value true Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable FDSTR has value -framedrop Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable LIRCRC has value Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable LIRCSTR has value Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable SUBTITLE has value -subpos 80 -sub-bg-color 0 -sub-bg-alpha 30 Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable REMOTE has value -slave -nolirc Jul 11 17:36:27 arvdr logger: *** Use Option USERDEF at your own risk! Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable USERDEF has value -fs -nolirc -slave -vc ffh264vdpau,ffmpeg12vdpau,f fvc1vdpau,ffwmv3vdpau -correct-pts -mc 100 Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable XResPAL has value 352 480 528 544 704 720 Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable XResNTSC has value 352 480 512 544 640 704 720 Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable SLOW_CPU has value false Jul 11 17:36:27 arvdr logger: *** DEBUG: *** Option DVDFiles not set correctly! You will not be able to play VCD/DVD Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable DVDFiles has value Jul 11 17:36:27 arvdr logger: *** DEBUG: *** Option DVD not set correctly! You will not be able to play VCD/DVD Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable DVD has value Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable DVDLANG has value ru Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable DVDOPTIONS has value Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable VCDOPTIONS has value Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable MPEG_DIRECT has value true Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable SUFFIX has value 1.ts Jul 11 17:36:27 arvdr logger: *** DEBUG: Variable MPLAYER_V1 has value true Jul 11 17:36:27 arvdr logger: *** DEBUG: Calling getvidxy function to analyze source video stream ... Jul 11 17:36:28 arvdr lircd-0.8.3[2455]: accepted new client on /dev/lircd Jul 11 17:36:29 arvdr lircd-0.8.3[2455]: removed client Jul 11 17:36:29 arvdr logger: *** DEBUG: MPLAYER_RETURN: 0 Jul 11 17:36:29 arvdr logger: *** DEBUG: parsed output for ORIG_X: 0 Jul 11 17:36:29 arvdr logger: *** DEBUG: parsed output for ORIG_Y: 0 Jul 11 17:36:29 arvdr logger: *** DEBUG: parsed output for ORIG_FPS: 25.000 Jul 11 17:36:30 arvdr logger: *** DEBUG: parsed output for ORIG_ASPECT: 0. Jul 11 17:36:30 arvdr logger: *** DEBUG: parsed output for VIDEO_FORMAT: 0x1005 Jul 11 17:36:30 arvdr logger: *** DEBUG: parsed output for AUDIO_CODEC: mp3 Jul 11 17:36:30 arvdr logger: *** INFO: Source Video has Resolution of 0 x 0 ... Jul 11 17:36:30 arvdr logger: *** FATAL: something went wrong analyzing the video; check your mplayer version ... Jul 11 17:36:30 arvdr vdr: [3904] mplayer: player thread ended (pid=3126) Jul 11 17:36:30 arvdr logger: ao_flush (loop running: 1) Jul 11 17:36:30 arvdr logger: video discontinuity #576, type is 0, disc_off 0 Jul 11 17:36:30 arvdr logger: waiting for audio discontinuity #576 Jul 11 17:36:30 arvdr logger: audio discontinuity #576, type is 0, disc_off 0 Jul 11 17:36:30 arvdr logger: waiting for in_discontinuity update #576 Jul 11 17:36:30 arvdr logger: vpts adjusted with prebuffer to 504741024 Jul 11 17:36:30 arvdr logger: ao_flush (loop running: 1) Jul 11 17:36:30 arvdr logger: audio discontinuity #577, type is 0, disc_off 0 Jul 11 17:36:30 arvdr logger: waiting for in_discontinuity update #577 Jul
Re: [vdr] [ANNOUNCE] xxv-1.4 - Stable release
Hi, Andreas where xxv should be install - on vdr computer or on remote computer ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] ERROR: driver buffer overflow on device 1 on 1080i channels
Hi my configuration is HVR-4000+firmware version 1.23.86.1+S2-Liplianin VDR 1.7.8+vdr-xine 0.9.3 Debian SID + kernel 2.6.30 AMD Sempron(tm) Processor 2800+ NVIDIA Sparkle GeForce 8400 GS 512 MB (GPU G98 A2) fanles PCI + Nvidia 185.18.14 + xine-vdpau rev. 273 with 1080i channels and temporal or half temporal_spatial deinterlacing I always have jerky and stuttering audio and video With bob , half temporal - no problems does it possible to fix that problem ? Jul 7 18:55:17 arvdr vdr: [4361] ERROR: skipped 287597 bytes to sync on TS packet on device 1 Jul 7 18:55:17 arvdr vdr: [4362] buffer usage: 10% (tid=4361) Jul 7 18:55:17 arvdr vdr: [4361] ERROR: skipped 1731910 bytes to sync on TS packet on device 1 Jul 7 18:55:17 arvdr vdr: [4361] TS continuity error (8) Jul 7 18:55:17 arvdr vdr: [4361] PES packet shortened to 2550 bytes (expected: 3470 bytes) Jul 7 18:55:18 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:55:18 arvdr vdr: [4362] buffer usage: 80% (tid=4361) Jul 7 18:55:18 arvdr vdr: [4362] buffer usage: 90% (tid=4361) Jul 7 18:55:19 arvdr vdr: [4362] buffer usage: 100% (tid=4361) Jul 7 18:55:20 arvdr vdr: [4362] ERROR: driver buffer overflow on device 1 Jul 7 18:55:20 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:55:21 arvdr vdr: [4361] ERROR: skipped 847891 bytes to sync on TS packet on device 1 Jul 7 18:55:21 arvdr vdr: [4361] TS continuity error (12) Jul 7 18:55:21 arvdr vdr: [4361] TS continuity error (9) Jul 7 18:55:23 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:55:23 arvdr vdr: [4362] buffer usage: 80% (tid=4361) Jul 7 18:55:23 arvdr vdr: [4362] buffer usage: 90% (tid=4361) Jul 7 18:55:23 arvdr vdr: [4362] buffer usage: 100% (tid=4361) Jul 7 18:55:24 arvdr vdr: [4362] ERROR: driver buffer overflow on device 1 Jul 7 18:55:25 arvdr vdr: [4362] buffer usage: 10% (tid=4361) Jul 7 18:55:25 arvdr vdr: [4361] ERROR: skipped 1899195 bytes to sync on TS packet on device 1 Jul 7 18:55:25 arvdr vdr: [4361] ERROR: skipped 391032 bytes to sync on TS packet on device 1 Jul 7 18:55:26 arvdr vdr: [4361] TS continuity error (1) Jul 7 18:55:28 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:55:28 arvdr vdr: [4362] buffer usage: 80% (tid=4361) Jul 7 18:55:28 arvdr vdr: [4362] buffer usage: 90% (tid=4361) Jul 7 18:55:28 arvdr vdr: [4362] buffer usage: 100% (tid=4361) Jul 7 18:55:30 arvdr vdr: [4362] ERROR: driver buffer overflow on device 1 Jul 7 18:55:31 arvdr vdr: [4361] ERROR: skipped 982908 bytes to sync on TS packet on device 1 Jul 7 18:55:31 arvdr vdr: [4361] ERROR: skipped 882439 bytes to sync on TS packet on device 1 Jul 7 18:55:31 arvdr vdr: [4362] buffer usage: 0% (tid=4361) Jul 7 18:55:31 arvdr vdr: [4361] TS continuity error (3) Jul 7 18:55:33 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:55:33 arvdr vdr: [4362] buffer usage: 80% (tid=4361) Jul 7 18:55:33 arvdr vdr: [4362] buffer usage: 90% (tid=4361) Jul 7 18:55:33 arvdr vdr: [4362] buffer usage: 100% (tid=4361) Jul 7 18:55:35 arvdr vdr: [4362] ERROR: driver buffer overflow on device 1 Jul 7 18:55:36 arvdr vdr: [4361] ERROR: skipped 331513 bytes to sync on TS packet on device 1 Jul 7 18:55:36 arvdr vdr: [4361] ERROR: skipped 1719014 bytes to sync on TS packet on device 1 Jul 7 18:55:36 arvdr vdr: [4361] TS continuity error (11) Jul 7 18:55:36 arvdr vdr: [4361] TS continuity error (5) Jul 7 18:55:36 arvdr vdr: [4362] buffer usage: 0% (tid=4361) Jul 7 18:58:15 arvdr vdr: [4362] buffer usage: 90% (tid=4361) Jul 7 18:58:15 arvdr vdr: [4362] buffer usage: 100% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:22 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:22 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:22 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:22 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:23
[vdr] svn Mplayer + mplayer-plugin from HG = no SLAVE mode
Hi I try to use vdr 178 + mplayer from svn + mplayer-plugin from HG + mplayer.sh from hotwings #!/bin/sh CMDLINE=mplayer -fs -vo vdpau -vc ffh264vdpau,ffmpeg12vdpau,ffvc1vdpau,ffwmv3vdpau, -ao alsa -cache 4096 -slave -v -noconfig all -idx exit but I don't have any reactions If I press during of playback OK button on RC (should be vdr osd info about file), menu BUTTON(should be vdr files list). I installed manually the patch from mplayer-plugin directory - mplayer-1.0rc2-slavemode.diff - no effect can someone to help me please Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-weatherng-0.0.10 - couldn't run properly with vdr 1.7.8
Приветствую, hu_emulator I solved my problem with gcc 4.3. patch from vdr-portal could you run weatherng on vdr 178 ? I could compile but I couldn't it run properly when I try to download the dates from Internet I have the crash which imageMagic version should I use - in debian sid there are several versions of libmagic and libmagic+++ libmagic-dev: /usr/lib/libmagic.so libmagic1: /usr/share/doc/libmagic1/copyright libmagick++-dev: /usr/share/doc/libmagick++-dev/changelog.Debian.gz libmagick++-dev: /usr/share/doc/libmagick++-dev/copyright libmagick++10: /usr/share/doc/libmagick++10/changelog.Debian.gz libmagick10: /usr/share/doc/libmagick10/copyright libmagick9-dev: /usr/share/doc/libmagick9-dev/changelog.Debian.gz libmagick++9-dev: /usr/share/doc/libmagick++9-dev/changelog.Debian.gz libmagick9-dev: /usr/share/doc/libmagick9-dev/upgrade-checklist.txt.gz libmagickcore-dev: /usr/share/doc/libmagickcore-dev/changelog.Debian.gz My logs ar...@arvdr:/vdr$ LANG=C ./vdr -Pxine -p -r -P weatherng weatherng: no themefile found ! - MakePrimaryDevice: 1 = SetVideoFormat: 0 SetVolumeDevice: 255 SetAudioChannelDevice: 0 SetVolumeDevice: 255 SetPlayMode: 1 SetDigitalAudioDevice: 0 frame: (0, 0)-(-1, -1), zoom: (1.00, 1.00) vdr-xine: Client connecting ... vdr-xine: Client connected! frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) checking image with spec /etc/vdr/plugins/weatherng/images/44.png_210_196_196_14..weatherng-image: load image /etc/vdr/plugins/weatherng/images/44.png vdr: magick/cache.c:3459: GetVirtualPixels: Assertion `cache_info-signature == 0xabacadabUL' failed. Аварийный останов n 18 22:28:16 arvdr vdr: [4235] VDR version 1.7.8 started Jun 18 22:28:16 arvdr vdr: [4235] codeset is 'ANSI_X3.4-1968' - unknown Jun 18 22:28:16 arvdr vdr: [4235] found 0 locales in ./locale Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'deu,ger' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'slv,slo' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'ita' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'dut,nla,nld' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'por' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'fra,fre' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'nor' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'fin,suo' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'pol' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'esl,spa' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'ell,gre' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'sve,swe' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'rom,rum' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'hun' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'cat,cln' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'rus' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'hrv' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'est' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'dan' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'cze,ces' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'tur' Jun 18 22:28:16 arvdr vdr: [4235] no locale for language code 'ukr' Jun 18 22:28:16 arvdr vdr: [4235] loading plugin: ./PLUGINS/lib/libvdr-xine.so.1.7.8 Jun 18 22:28:17 arvdr vdr: [4235] loading plugin: ./PLUGINS/lib/libvdr-weatherng.so.1.7.8 Jun 18 22:28:17 arvdr vdr: [4235] loading /etc/vdr/setup.conf Jun 18 22:28:17 arvdr vdr: [4235] loading /etc/vdr/sources.conf Jun 18 22:28:17 arvdr vdr: [4235] loading /etc/vdr/diseqc.conf Jun 18 22:28:17 arvdr vdr: [4235] loading /etc/vdr/channels.conf Jun 18 22:28:17 arvdr vdr: [4235] loading /etc/vdr/timers.conf Jun 18 22:28:17 arvdr vdr: [4235] loading /etc/vdr/svdrphosts.conf Jun 18 22:28:17 arvdr vdr: [4235] loading /etc/vdr/remote.conf Jun 18 22:28:17 arvdr vdr: [4236] video directory scanner thread started (pid=4235, tid=4236) Jun 18 22:28:17 arvdr vdr: [4236] video directory scanner thread ended (pid=4235, tid=4236) Jun 18 22:28:17 arvdr vdr: [4237] video directory scanner thread started (pid=4235, tid=4237) Jun 18 22:28:17 arvdr vdr: [4237] video directory scanner thread ended (pid=4235, tid=4237) Jun 18 22:28:17 arvdr vdr: [4235] reading EPG data from /video/epg.data Jun 18 22:28:17 arvdr vdr: [4235] probing /dev/dvb/adapter0/frontend0 Jun 18 22:28:17 arvdr vdr: [4235] device 1 provides DVB-S2 (Conexant CX24116/CX24118) Jun 18 22:28:17 arvdr vdr: [4239] tuner on device 1 thread started (pid=4235, tid=4239) Jun 18 22:28:17 arvdr vdr: [4240] section handler thread started (pid=4235, tid=4240) Jun 18 22:28:17 arvdr vdr: [4235] found 1 video device n 18 22:28:17 arvdr vdr: [4235] initializing plugin: xine (0.9.3): Software based playback using xine Jun 18 22:28:17
Re: [vdr] vdr 1.7.8 - __u8’ does not name a type
I added #include asm/types.h as Tobi recommended http://e-tobi.net/websvn/filedetails.php?repname=vdr-pkgpath=%2Fvdr%2Fbranches%2Fdevel%2Fdebian%2Fpatches%2F99_dvb-header-fixes.dpatch and after that I could compile vdr 178 [...] ../s2-liplianin/linux/include/linux/dvb/frontend.h:92: error: ‘__u8’ does not name a type Strange, that file (at least current version) #includes linux/types.h, which in turn (/usr/include/linux/types.h) #includes asm/types.h. Including asm/types.h from VDR should not be necessary. Could you confirm that your frontend.h file also contains #include linux/types.h and tha tyour /usr/include/linux/types.h #includes asm/types.h ? yes my /s2-liplianin/linux/include/linux/dvb/frontend.h contains #include linux/types.h and /usr/include/linux/types.h also conteins #includes asm/types.h Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-weatherng-0.0.10 - can't compile with vdr 1.7.8 and debian sid
Hi In debian sid the're updated packages for imagic liblqr-1-0-dev (0.4.1-1) ... libmagick++2 (7:6.5.1.0-1.1) ... libmagickcore-dev (7:6.5.1.0-1.1) ... libmagickwand-dev (7:6.5.1.0-1.1) ... libmagick++-dev (7:6.5.1.0-1.1) . with vdr 178 I couldn't compile vdr-weatherng-0.0.10.tar.bz2 g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='weatherng' -I../s2-liplianin/linux/include -I../../../include -obitmap.o bitmap.c In file included from bitmap.h:8, from bitmap.c:5: imagecache.h:22: error: ‘uint’ does not name a type imagecache.h:29: error: expected `)' before ‘MaxItems’ imagecache.h:36: error: ‘uint’ does not name a type imagecache.h:46: error: expected constructor, destructor, or type conversion before ‘(’ token imagecache.h: In member function ‘data_type cxCachekey_type, data_type::operator[](const key_type)’: imagecache.h:91: error: ‘mMaxItems’ was not declared in this scope In file included from bitmap.c:5: bitmap.h: In constructor ‘cBitmapCache::cBitmapCache(uint)’: bitmap.h:58: error: no matching function for call to ‘cxCachetBitmapSpec, cWeatherBitmap*::cxCache(uint)’ imagecache.h:13: note: candidates are: cxCachetBitmapSpec, cWeatherBitmap*::cxCache() imagecache.h:13: note: cxCachetBitmapSpec, cWeatherBitmap*::cxCache(const cxCachetBitmapSpec, cWeatherBitmap*) make: *** [bitmap.o] Ошибка 1 any ideas ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-weatherng-0.0.10 - can't compile with vdr 1.7.8 and debian sid
Приветствую, Goga777 with gcc 4.3.* патч http://www.vdr-portal.de/board/thread.php?postid=776855#post776855 Ш could compile plugin Hi In debian sid the're updated packages for imagic liblqr-1-0-dev (0.4.1-1) ... libmagick++2 (7:6.5.1.0-1.1) ... libmagickcore-dev (7:6.5.1.0-1.1) ... libmagickwand-dev (7:6.5.1.0-1.1) ... libmagick++-dev (7:6.5.1.0-1.1) . with vdr 178 I couldn't compile vdr-weatherng-0.0.10.tar.bz2 g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='weatherng' -I../s2-liplianin/linux/include -I../../../include -obitmap.o bitmap.c In file included from bitmap.h:8, from bitmap.c:5: imagecache.h:22: error: ‘uint’ does not name a type imagecache.h:29: error: expected `)' before ‘MaxItems’ imagecache.h:36: error: ‘uint’ does not name a type imagecache.h:46: error: expected constructor, destructor, or type conversion before ‘(’ token imagecache.h: In member function ‘data_type cxCachekey_type, data_type::operator[](const key_type)’: imagecache.h:91: error: ‘mMaxItems’ was not declared in this scope In file included from bitmap.c:5: bitmap.h: In constructor ‘cBitmapCache::cBitmapCache(uint)’: bitmap.h:58: error: no matching function for call to ‘cxCachetBitmapSpec, cWeatherBitmap*::cxCache(uint)’ imagecache.h:13: note: candidates are: cxCachetBitmapSpec, cWeatherBitmap*::cxCache() imagecache.h:13: note: cxCachetBitmapSpec, cWeatherBitmap*::cxCache(const cxCachetBitmapSpec, cWeatherBitmap*) make: *** [bitmap.o] Ошибка 1 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] CW-4000HD High Definition Linux Media Center with VDR
http://www.captiveworks.com/cw4000hd.php CaptiveWorks introduces the CW-4000HD, its latest High Definition Multimedia Platform. The CW-4000HD is a available in a black finish with high-gloss front panel and silver highlighting. Dimensions: - Width: 367 mm(14.45 in) - Height: 99 mm( 3.89 in) - Depth: 350 mm(13.78 in) Hardware: - Processor: AMD 5000 X2 Processor - Memory: 512MB DDRII RAM Expandable to 8GB - Flash Drive: 1GB Fast System Flash - Hard Drive: Not Included - Video: Nvidia GeForce 7050 - Satellite Tuner: Genpix Skywalker-CW3K (internal) - Input terminal: F-type 75 Ohm - Receiving frequency: 950~2150 MHz tuning range - Input level: -65~-25dBm - Support MCPC and SCPC - Symbol rate: 256Ksps~30 Msps - FEC Codes: 1/2,2/3,3/4,5/6,7/8 and Auto - QPSK, 8PSK, 16QAM - LNB/switch control: 13/18V (or 14/19V), 22khz, Tone Burst, DiSEqC 1.0/1.2, Legacy switch commands, 450 mA - ATSC Tuner: (optional) - Latest LG 5th generation tuner for enhanced reception. - Supports QAM 64 and QAM 256 Cable signals. - One TV antenna 75 ohm reception port. - One stereo connection jack to sound card for analog TV. - Video Output: HDMI/SVGA/Component/S-Video - Audio Ouput: Analog and SPDIF Dolby Digital Audio output - USB Ports: 4 USB v2.0 ports on back panel and 2 USB v2.0 ports on front panel. - Ethernet Port: RJ-45 10/100/1000 Mbits compatible. - DVDRW: Read/Write DVDs and CDs. Software : - Java 1.4.2 Graphical User Interface - Open Source Linux Operating System - Version 2.6 Kernel - X Windows Environment - VDR (Video Disk Recorder) - atscepg - epgsearch - extrecmenu - femon - nacc - nvsettings - radioinfo - radiolist - satlist - setup - skinsoppalusikka - streamdev-server - xine - yaepg - zaphistory - zoom - GQview image viewer - Roaster mpg, iso, and disc builder - Firefox web browser (Bon Echo) - Lighttpd web server - EPDFview pdf viewer - Samba file server (Windows style networking) - Xine multimedia player Official CW-4000HD Support can be obtained at www.CaptiveWorks.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine settings for VDPAU SD and HD
Приветствую, VDR user would you show please your modeline in xorg.conf please do you use 1080i or 1080p in it ? I don't know if this will help you any but I use xine-vdpau for both sdtv hdtv. I haven't changed anything in .xine/config so the buffer settings and so on are whatever they are as default. My box runs debian with vdr-1.7.7 and xine-0.9.2 in case that matters. Currently using xine-vdpau r266 released earlier today and nvidia driver 185.18.14 with an 8400GS (with spdif connected to it). I don't think it matters but I'm outputting to a tv using dvi-hdmi cable. I start xine with: xine -A alsa -V vdpau --post vdr_video --post vdr_audio vdr://tmp/vdr-xine/stream#demux:mpeg_pes --verbose=2 --fullscreen --no-gui --no-mouse --deinterlace --no-logo --no-splash ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.7.8 - __u8’ does not name a type
Hi I can't compile vdr 178 with 2.6.29 kernel and s2-liplianin http://mercurial.intuxication.org/hg/s2-liplianin deo\ -DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\./locale\ -I/usr/include/freetype2 -I../s2-liplianin/linux/include vdr.c In file included from dvbdevice.h:14, from vdr.c:45: ../s2-liplianin/linux/include/linux/dvb/frontend.h:92: error: ‘__u8’ does not name a type ../s2-liplianin/linux/include/linux/dvb/frontend.h:93: error: ‘__u8’ does not name a type ../s2-liplianin/linux/include/linux/dvb/frontend.h:98: error: ‘__u8’ does not name a type ../s2-liplianin/linux/include/linux/dvb/frontend.h:99: error: ‘__u8’ does not name a type ../s2-liplianin/linux/include/linux/dvb/frontend.h:361: error: ‘__u8’ does not name a type make: *** [vdr.o] Ошибка 1 the trick from Klaus in thread Re: [vdr] error compiling vdr 1.7.7 (frontend.h - '__u8' does not name a type) http://www.mail-archive.com/vdr@linuxtv.org/msg10382.html didn't help me Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.8 - __u8’ does not name a type
Hi I added #include asm/types.h as Tobi recommended http://e-tobi.net/websvn/filedetails.php?repname=vdr-pkgpath=%2Fvdr%2Fbranches%2Fdevel%2Fdebian%2Fpatches%2F99_dvb-header-fixes.dpatch and after that I could compile vdr 178 I can't compile vdr 178 with 2.6.29 kernel and s2-liplianin http://mercurial.intuxication.org/hg/s2-liplianin deo\ -DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\./locale\ -I/usr/include/freetype2 -I../s2-liplianin/linux/include vdr.c In file included from dvbdevice.h:14, from vdr.c:45: ../s2-liplianin/linux/include/linux/dvb/frontend.h:92: error: ‘__u8’ does not name a type ../s2-liplianin/linux/include/linux/dvb/frontend.h:93: error: ‘__u8’ does not name a type ../s2-liplianin/linux/include/linux/dvb/frontend.h:98: error: ‘__u8’ does not name a type ../s2-liplianin/linux/include/linux/dvb/frontend.h:99: error: ‘__u8’ does not name a type ../s2-liplianin/linux/include/linux/dvb/frontend.h:361: error: ‘__u8’ does not name a type make: *** [vdr.o] Ошибка 1 the trick from Klaus in thread Re: [vdr] error compiling vdr 1.7.7 (frontend.h - '__u8' does not name a type) http://www.mail-archive.com/vdr@linuxtv.org/msg10382.html didn't help me ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wrong OSD values in setup.conf (was: Re: vdr-xine-0.9.2 - ERROR: cOsd::SetAreas returned 5)
Приветствую, Andreas thanks it helped as you can see your values are 0 too. I suggest you set (VDR stopped!) OSDHeightP and OSDWidthP to 0.5 (=50%) and FontFixSizeP, FontOsdSizeP, FontSmlSizeP to 0.03 to get an OSD. After that you can fine-tune the OSD settings. Regards, Andreas 2009/6/10 Goga777 goga...@bk.ru: check your setup.conf. Mine has invalid sizes: FontFix = Courier:Bold FontFixSize = 0 FontFixSizeP = 0,00 FontOsd = VDRSymbols Sans:Bold FontOsdSize = 0 FontOsdSizeP = 0,00 FontSml = VDRSymbols Sans:Book FontSmlSize = 0 FontSmlSizeP = 0,00 OSDHeight = 0 OSDHeightP = 0,00 OSDLanguage = de_DE OSDLeft = 0 OSDLeftP = 0,00 OSDTop = 0 OSDTopP = 0,00 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wrong OSD values in setup.conf (was: Re: vdr-xine-0.9.2 - ERROR: cOsd::SetAreas returned 5)
check your setup.conf. Mine has invalid sizes: FontFix = Courier:Bold FontFixSize = 0 FontFixSizeP = 0,00 FontOsd = VDRSymbols Sans:Bold FontOsdSize = 0 FontOsdSizeP = 0,00 FontSml = VDRSymbols Sans:Book FontSmlSize = 0 FontSmlSizeP = 0,00 OSDHeight = 0 OSDHeightP = 0,00 OSDLanguage = de_DE OSDLeft = 0 OSDLeftP = 0,00 OSDTop = 0 OSDTopP = 0,00 OSDWidth = 0 OSDWidthP = 0,00 my setup.conf FontFix = Courier:Bold FontFixSize = 0 FontFixSizeP = 0.00 FontOsd = Sans Serif:Bold FontOsdSize = 0 FontOsdSizeP = 0.00 FontSml = Sans Serif FontSmlSize = 0 FontSmlSizeP = 0.00 InitialChannel = 0 OSDHeight = 0 OSDHeightP = 0.00 OSDLanguage = en_US OSDLeft = 0 OSDLeftP = 0.00 OSDMessageTime = 2 OSDSkin = sttng OSDTheme = default OSDTop = 0 OSDTopP = 0.00 OSDWidth = 0 OSDWidthP = 0.00 As you can see they are are all 0. I don't know how that could happen, but I already had that on two VDR instances. Both upgraded from VDR 1.6.0. After setting them once in VDR 1.7 they are fine. What skin do you use? My own EnigmaNG skin (CVS release) takes care of invalid values ;) I didn't install additional skins, I'm using default skin ST:TNG Goga 2009/6/9 Reinhard Nissl rni...@gmx.de: Hi, Goga777 schrieb: how can I fix my problem with ERROR: cOsd::SetAreas returned 5 This number matches the enum value oeWrongAlignment. In VDR's code excerpt you can see the condition for this error: if (Areas[i].x1 Areas[i].x2 || Areas[i].y1 Areas[i].y2 || Areas[i].x1 0 || Areas[i].y1 0) return oeWrongAlignment; Jun 9 21:25:39 arvdr vdr: [12294] vdr-xine: new OSD(0, -108) requested with coordinates out of range Jun 9 21:25:39 arvdr vdr: [12294] ERROR: cOsd::SetAreas returned 5 I've no idea why a vanilla VDR-1.7.7 should produce such an incorrect OSD setup. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rni...@gmx.de ___ 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] need help with GOTOX patch.
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 ? 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 ? -- Удачи, Игорь ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-xine-0.9.2 - ERROR: cOsd::SetAreas returned 5
Hi how can I fix my problem with ERROR: cOsd::SetAreas returned 5 Jun 9 21:25:26 arvdr vdr: [12294] VDR version 1.7.7 started Jun 9 21:25:26 arvdr vdr: [12294] codeset is 'UTF-8' - known Jun 9 21:25:26 arvdr vdr: [12294] found 23 locales in ./locale Jun 9 21:25:26 arvdr vdr: [12294] loading plugin: ./PLUGINS/lib/libvdr-xine.so.1.7.7 Jun 9 21:25:26 arvdr vdr: [12294] loading /video/setup.conf Jun 9 21:25:26 arvdr vdr: [12294] loading /video/sources.conf Jun 9 21:25:26 arvdr vdr: [12294] loading /video/diseqc.conf Jun 9 21:25:26 arvdr vdr: [12294] loading /video/channels.conf Jun 9 21:25:26 arvdr vdr: [12294] loading /video/timers.conf Jun 9 21:25:26 arvdr vdr: [12294] loading /video/svdrphosts.conf Jun 9 21:25:26 arvdr vdr: [12295] video directory scanner thread started (pid=12294, tid=12295) Jun 9 21:25:26 arvdr vdr: [12295] video directory scanner thread ended (pid=12294, tid=12295) Jun 9 21:25:26 arvdr vdr: [12296] video directory scanner thread started (pid=12294, tid=12296) Jun 9 21:25:26 arvdr vdr: [12296] video directory scanner thread ended (pid=12294, tid=12296) Jun 9 21:25:26 arvdr vdr: [12294] reading EPG data from /video/epg.data Jun 9 21:25:26 arvdr vdr: [12294] probing /dev/dvb/adapter0/frontend0 Jun 9 21:25:26 arvdr vdr: [12294] device 1 provides DVB-S2 (Conexant CX24116/CX24118) Jun 9 21:25:26 arvdr vdr: [12298] tuner on device 1 thread started (pid=12294, tid=12298) Jun 9 21:25:26 arvdr vdr: [12299] section handler thread started (pid=12294, tid=12299) Jun 9 21:25:26 arvdr vdr: [12294] found 1 video device Jun 9 21:25:26 arvdr vdr: [12294] initializing plugin: xine (0.9.2): Software based playback using xine Jun 9 21:25:26 arvdr vdr: [12300] XineRemote control thread started (pid=12294, tid=12300) Jun 9 21:25:26 arvdr vdr: [12300] Entering cXineRemote thread Jun 9 21:25:26 arvdr vdr: [12294] setting primary device to 2 Jun 9 21:25:26 arvdr vdr: [12294] assuming manual start of VDR Jun 9 21:25:26 arvdr vdr: [12294] SVDRP listening on port 2001 Jun 9 21:25:26 arvdr vdr: [12294] setting current skin to sttng Jun 9 21:25:26 arvdr vdr: [12294] loading /video/themes/sttng-default.theme Jun 9 21:25:26 arvdr vdr: [12294] starting plugin: xine Jun 9 21:25:28 arvdr vdr: [12303] KBD remote control thread started (pid=12294, tid=12303) Jun 9 21:25:28 arvdr vdr: [12294] ERROR: remote control XineRemote not ready! Jun 9 21:25:28 arvdr vdr: [12294] remote control KBD - learning keys Jun 9 21:25:28 arvdr vdr: [12294] ERROR: cOsd::SetAreas returned 5 Jun 9 21:25:38 arvdr vdr: [12294] switching to channel 3 Jun 9 21:25:39 arvdr vdr: [12311] receiver on device 1 thread started (pid=12294, tid=12311) Jun 9 21:25:39 arvdr vdr: [12312] TS buffer on device 1 thread started (pid=12294, tid=12312) Jun 9 21:25:39 arvdr vdr: [12294] OSD size changed to 720x576 @ 4:3 Jun 9 21:25:39 arvdr vdr: [12294] vdr-xine: new OSD(0, -108) requested with coordinates out of range Jun 9 21:25:39 arvdr vdr: [12294] ERROR: cOsd::SetAreas returned 5 Jun 9 21:25:48 arvdr vdr: [12298] frontend 0 timed out while tuning to channel 3, tp 110744 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-sxfe doesn't work correctly with keyboard
no it doesn't help In xine_sxfe_frontend.c I replaced the line if(kev-keycode) to if(kev-keycode(kev-type==KeyPress)) and after that everything is OK thanks to psofa from xine-vdpau irc channel for this useful hint Goga remove XKeySym.Up Up XKeySym.Down Down does it fix up and down? then remove the numbers 2 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-sxfe doesn't work correctly with keyboard
Hi my system is server - debian + kernel 2.6.29 + vdr 177 + s2-liplanin + hvr4000 + cvs xineliboutput + vdr-xine from hg remote client - debian + vdr-sxfe from cvs xineliboutput + xine-lib-1.2 from hg I have the problem with keyboard on remote frontend computer (vdr-sxfe) For example - If I press and after that release the any digital button (2 or 5) I have the 22 or 55 results - not 2 or 5 as usual . Another example - If I press and release the button UP or DOWN the cursor will move on TWO lines to up or to down. The problem is when I released the button - after release of button I have second event - double figure or double moving. Also I couldn't use the pipe connection , rtp, udp protocols - only tcp connection Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Trying PIPE connection ... Jun 6 11:44:37 arvdr vdr: [17202] creating directory /video/plugins/xineliboutput/pipes.17195 Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Pipe not opened by client Jun 6 11:44:37 arvdr vdr: [17202] removing /video/plugins/xineliboutput/pipes.17195 Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Trying RTP connection ... Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] RTP transport not implemented for vdr-1.7.x Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Trying UDP connection ... Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] UDP transport not implemented for vdr-1.7.x logs from vdr 177 arvdr:/vdr# ./vdr -Pxineliboutput --local=none --remote=37890 Jun 6 11:43:45 arvdr vdr: [17195] cTimeMs: using monotonic clock (resolution is 1 ns) Jun 6 11:43:45 arvdr vdr: [17195] VDR version 1.7.7 started Jun 6 11:43:45 arvdr vdr: [17195] codeset is 'UTF-8' - known Jun 6 11:43:45 arvdr vdr: [17195] found 23 locales in ./locale Jun 6 11:43:45 arvdr vdr: [17195] loading plugin: ./PLUGINS/lib/libvdr-xineliboutput.so.1.7.7 Jun 6 11:43:45 arvdr vdr: [17195] loading /video/setup.conf Jun 6 11:43:45 arvdr vdr: [17195] [xine..put] Skipping configuration entry Frontend=sxfe (overridden in command line) Jun 6 11:43:45 arvdr vdr: [17195] loading /video/sources.conf Jun 6 11:43:45 arvdr vdr: [17195] loading /video/diseqc.conf Jun 6 11:43:45 arvdr vdr: [17195] loading /video/channels.conf Jun 6 11:43:45 arvdr vdr: [17195] loading /video/svdrphosts.conf Jun 6 11:43:45 arvdr vdr: [17195] loading /video/remote.conf Jun 6 11:43:45 arvdr vdr: [17196] video directory scanner thread started (pid=17195, tid=17196) Jun 6 11:43:45 arvdr vdr: [17196] video directory scanner thread ended (pid=17195, tid=17196) Jun 6 11:43:45 arvdr vdr: [17197] video directory scanner thread started (pid=17195, tid=17197) Jun 6 11:43:45 arvdr vdr: [17197] video directory scanner thread ended (pid=17195, tid=17197) Jun 6 11:43:45 arvdr vdr: [17195] reading EPG data from /video/epg.data Jun 6 11:43:45 arvdr vdr: [17195] probing /dev/dvb/adapter0/frontend0 Jun 6 11:43:45 arvdr vdr: [17195] device 1 provides DVB-S2 (Conexant CX24116/CX24118) Jun 6 11:43:45 arvdr vdr: [17199] tuner on device 1 thread started (pid=17195, tid=17199) Jun 6 11:43:45 arvdr vdr: [17200] section handler thread started (pid=17195, tid=17200) Jun 6 11:43:45 arvdr vdr: [17195] found 1 video device Jun 6 11:43:45 arvdr vdr: [17195] initializing plugin: xineliboutput (1.0.90-cvs): X11/xine-lib output plugin Jun 6 11:43:45 arvdr vdr: [17195] [xine..put] cTimePts: clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us Jun 6 11:43:45 arvdr vdr: [17195] [xine..put] cTimePts: using monotonic clock Jun 6 11:43:45 arvdr vdr: [17195] [xine..put] RTP SSRC: 0x27fae0fc Jun 6 11:43:45 arvdr vdr: [17195] setting primary device to 1 Jun 6 11:43:45 arvdr vdr: [17195] device 1 has no MPEG decoder Jun 6 11:43:45 arvdr vdr: [17195] trying device number 2 instead Jun 6 11:43:45 arvdr vdr: [17195] setting primary device to 2 Jun 6 11:43:45 arvdr vdr: [17195] assuming manual start of VDR Jun 6 11:43:45 arvdr vdr: [17195] SVDRP listening on port 2001 Jun 6 11:43:45 arvdr vdr: [17195] setting current skin to sttng Jun 6 11:43:45 arvdr vdr: [17195] loading /video/themes/sttng-default.theme Jun 6 11:43:45 arvdr vdr: [17195] starting plugin: xineliboutput Jun 6 11:43:45 arvdr vdr: [17202] Remote decoder/display server (cXinelibServer) thread started (pid=17195, tid=17202) Jun 6 11:43:45 arvdr vdr: [17202] [xine..put] cXinelibServer priority set successful SCHED_RR 2 [1,99] Jun 6 11:43:45 arvdr vdr: [17202] [xine..put] Listening on port 37890 Jun 6 11:43:45 arvdr vdr: [17202] [xine..put] Listening for UDP broadcasts on port 37890 Jun 6 11:43:45 arvdr vdr: [17202] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0^M Server port: 37890^M Server vers ion: xineliboutput-1.0.90-cvs^M ^M Jun 6 11:43:45 arvdr vdr: [17195] [xine..put] cXinelibDevice::StartDevice(): Device started Jun 6 11:43:45 arvdr vdr: [17203] KBD remote control thread started (pid=17195, tid=17203) Jun 6 11:43:45 arvdr vdr: [17195] remote control KBD - learning keys Jun 6
Re: [vdr] Any really working HD video output systems for VDR?
great English howto HTPC DVB-S2 VDR 1.7.7 Howto http://ubuntuforums.org/showthread.php?t=1126258 Could you please both detail a bit the DVB sources, software versions, plugins, patches, etc. related to HD, that you actually use now ? (DVB-T, DVB-S or S2, DVB kernel patches, VDR core, xineliboutput or xine plugin, xinelib patches...) I use DVB-S sources on VDR-1.7.7 with just basic plugins and xine-vdpau (r260). No special patches are needed for/to anything although I do use vdr-1.7.3-ntsc-fps.diff which changes the default framespersecond to 30.0 (NTSC) instead of 25.0 (PAL), although I've heard this is not necessary now that VDR uses mpeg-ts. It's really straight forward. Maybe there is an english howto somewhere ? There are english forums at: http://dvbn.happysat.org (they have a linux specific forum there which is very active) http://www.hoochvdr.info (good howtos but not actively kept up anymore _I think_) vdrportal looks like a good forum but as already pointed out, it's in German and thus practically useless for all of us english-speaking users. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.7 crashes during starting wiith rotor plugin
Приветствую, Arthur Is it possible to determine why vdr crashes during starting with rotor plugin enabled? Plugin and vdr core patched properly (rotor-0.1.4S2API, vdr-1.7.7-rotor.diff) what's rotor-0.1.4S2API ? does it patched rotor plugin ? -- Удачи, Игорь Linux VDR/DVB форум http://www.forum.free-x.de/wbb/index.php?page=Portal ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How to keep the channel list tidy automatically
There used to be a plugin ,'autosort' i believe, which did some of those things. http://www.vdr-wiki.de/wiki/index.php/Autosort-plugin http://www.copypointburscheid.de/linux/autosort.htm home page of that plugin doesn't work where is it possible to download that plugin for vdr 1.7.7 ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How to keep the channel list tidy automatically
There used to be a plugin ,'autosort' i believe, which did some of those things. http://www.vdr-wiki.de/wiki/index.php/Autosort-plugin http://www.copypointburscheid.de/linux/autosort.htm home page of that plugin doesn't work where is it possible to download that plugin for vdr 1.7.7 ? I have no idea, I have vdr-autosort-0.1.3.tgz file, dated 1.4.2007 so I'm sure it needs work, to run with vdr-1.7.7 I can mail it to you if you like, its only 40kb file. thanks I found it here http://www.copypointburscheid.de/linux/vdr-autosort-0.1.3.tgz Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] IPTV streaming of h.264 channels - VDR as server
Hi has someone the experience with IPTV streaming of h264 hdtv channels to local network from VDR ? which software need to use for that ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] IPTV streaming of h.264 channels - VDR as server
has someone the experience with IPTV streaming of h264 hdtv channels to local network from VDR ? which software need to use for that ? You can use streamdev for it. for iptv hdtv h264 ? are you sure ? does it really work ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] NVidia ION mini-ITX arriving
Well, my first imressions of the ION platform (Acer Revo) are very good. It does the vdpau deinterlacing without problems and so far the video decoding has not exceeded 1% cpu load for ANY 1080p clip I've tried. This is the best VDR frontend/XBMC machine I've ever tried. I don't know why, but it works better than my Intel E7200/Nvidia 9400 uATX board. For those interested it uses 34W from 220V with the hdd still attached. I don't know if it's using any power though, since I've disabled SATA in the bios because I boot it off the network. Anyone who knows how to open this wonderful little thing? thanks for your report. but can you watch dvb-s2 h264 channels with some usb dvb-card ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] NVidia ION mini-ITX arriving
thanks again which resolution and diagonal size has your TV set ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] GOTOX patch for 1.7.5
Приветствую, 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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr and vdpau
Приветствую, marti...@embl.de I have installed an nvidia driver with vpdau support, patched xine-lib1.2 with the vpdau patch, and recompiled xine-ui I have improvement with HD channels cpu utilization wise but still choppy image. Do I need to patch vdr itself or change some config options to optimize the speed? nvidia 8200 on-board only Speedup patch for VDR-1.7.5 from Reinhard Nissl - see in vdr list Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR behaviour with wrong NIT
Hi
there's one sat-provider from 9e which is sending NIT with wrong parameters
Frequency: 18437984 (= 11.95760 GHz)
Kind: 0 (0x00) [= DVB-S]
fixed ('00'): 0 (0x00)
Modulation_type: 2 (0x02) [= 8PSK]
Symbol_rate: 2506752 (= 26.4000)
FEC_inner: 2 (0x02) [= 2/3 conv. code rate]
how VDR will manage with that table and with option add new channels and
transponders ?
/video# dvbsnoop -n 1 16
dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/
SECT-Packet: 0001 PID: 16 (0x0010), Length: 103 (0x0067)
Time received: Sat 2009-04-25 16:16:14.037
: 40 f0 64 00 01 e7 00 00 f0 18 40 0c 50 6c 61 74 @.d...@.plat
0010: 66 6f 72 6d 61 20 48 44 40 08 50 48 44 20 53 69 forma h...@.phd Si
0020: 74 65 f0 3f 18 38 00 01 f0 21 41 12 00 0a 01 00 te.?.8...!A.
0030: 14 19 00 1e 19 00 28 19 00 32 19 00 3c 19 43 0b ..(..2...C.
0040: 01 19 57 60 00 90 a2 02 64 00 02 1d 4c 00 01 f0 ..W`d...L...
0050: 12 41 03 00 06 01 43 0b 00 00 00 00 00 00 02 00 .AC.
0060: 50 00 01 67 df 80 48 P..g..H
PID: 16 (0x0010) [= assigned for: DVB Network Information Table (NIT),
Stuffing Table (ST)]
Guess table from table id...
NIT-decoding
Table_ID: 64 (0x40) [= Network Information Table (NIT) - actual network]
section_syntax_indicator: 1 (0x01)
reserved_1: 1 (0x01)
reserved_2: 3 (0x03)
Section_length: 100 (0x0064)
Network_ID: 1 (0x0001) [= Astra Satellite Network 19.2E / Satellite / SES]
reserved_3: 3 (0x03)
Version_number: 19 (0x13)
current_next_indicator: 1 (0x01) [= valid now]
Section_number: 0 (0x00)
Last_Section_number: 0 (0x00)
reserved_4: 15 (0x0f)
Network_descriptor_length: 24 (0x0018)
DVB-DescriptorTag: 64 (0x40) [= network_name_descriptor]
descriptor_length: 12 (0x0c)
Network_name: Platforma HD -- Charset: Latin alphabet
DVB-DescriptorTag: 64 (0x40) [= network_name_descriptor]
descriptor_length: 8 (0x08)
Network_name: PHD Site -- Charset: Latin alphabet
reserved_5: 15 (0x0f)
Transport_stream_loop_length: 63 (0x003f)
Transport_stream_ID: 6200 (0x1838)
Original_network_ID: 1 (0x0001) [= Astra Satellite Network 19,2�E |
Soci�t� Europ�enne des Satellites]
reserved_1: 15 (0x0f)
Transport_descriptor_length: 33 (0x0021)
DVB-DescriptorTag: 65 (0x41) [= service_list_descriptor]
descriptor_length: 18 (0x12)
service_ID: 10 (0x000a)[ -- refers to PMT program_number]
service_type: 1 (0x01) [= digital television service]
service_ID: 20 (0x0014)[ -- refers to PMT program_number]
service_type: 25 (0x19) [= advanced codec HD digital television
service]
service_ID: 30 (0x001e)[ -- refers to PMT program_number]
service_type: 25 (0x19) [= advanced codec HD digital television
service]
service_ID: 40 (0x0028)[ -- refers to PMT program_number]
service_type: 25 (0x19) [= advanced codec HD digital television
service]
service_ID: 50 (0x0032)[ -- refers to PMT program_number]
service_type: 25 (0x19) [= advanced codec HD digital television
service]
service_ID: 60 (0x003c)[ -- refers to PMT program_number]
service_type: 25 (0x19) [= advanced codec HD digital television
service]
DVB-DescriptorTag: 67 (0x43) [=
satellite_delivery_system_descriptor]
descriptor_length: 11 (0x0b)
Frequency: 18437984 (= 11.95760 GHz)
Orbital_position: 144 (= 9.0)
West_East_flag: 1 (0x01) [= EAST]
Polarisation: 1 (0x01) [= linear - vertical]
Kind: 0 (0x00) [= DVB-S]
fixed ('00'): 0 (0x00)
Modulation_type: 2 (0x02) [= 8PSK]
Symbol_rate: 2506752 (= 26.4000)
FEC_inner: 2 (0x02) [= 2/3 conv. code rate]
Transport_stream_ID: 7500 (0x1d4c)
Original_network_ID: 1 (0x0001) [= Astra Satellite Network 19,2�E |
Soci�t� Europ�enne des Satellites]
reserved_1: 15 (0x0f)
Transport_descriptor_length: 18 (0x0012)
DVB-DescriptorTag: 65 (0x41) [= service_list_descriptor]
descriptor_length: 3 (0x03)
service_ID: 6 (0x0006)[ -- refers to PMT program_number]
service_type: 1 (0x01) [= digital television service]
DVB-DescriptorTag: 67 (0x43) [=
satellite_delivery_system_descriptor]
descriptor_length: 11 (0x0b)
Frequency: 0 (= 0.0 GHz)
Orbital_position: 0 (= 0.0)
West_East_flag: 0 (0x00) [= WEST]
Polarisation: 0 (0x00) [= linear - horizontal]
Kind: 0 (0x00) [= DVB-S]
fixed ('00'): 0
Re: [vdr] VDR behaviour with wrong NIT
And which parameters are the wrong ones?
these two parameters are wrong
Frequency: 18437984 (= 11.95760 GHz) - should be another freq =
12.380
Kind: 0 (0x00) [= DVB-S] - should be dvb-s2
also, no any information about roll off factor, that's why vdr substituted roll
off = auto , cx24116 based cards don't
understand roll off = auto.
Goga
fixed ('00'): 0 (0x00)
Modulation_type: 2 (0x02) [= 8PSK]
Symbol_rate: 2506752 (= 26.4000)
FEC_inner: 2 (0x02) [= 2/3 conv. code rate]
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR behaviour with wrong NIT
And which parameters are the wrong ones?
these two parameters are wrong
Frequency: 18437984 (= 11.95760 GHz) - should be another freq =
12.380
Kind: 0 (0x00) [= DVB-S] - should be dvb-s2
also, no any information about roll off factor, that's why vdr substituted
roll off = auto , cx24116 based cards don't
understand roll off = auto.
Goga
fixed ('00'): 0 (0x00)
Modulation_type: 2 (0x02) [= 8PSK]
Symbol_rate: 2506752 (= 26.4000)
FEC_inner: 2 (0x02) [= 2/3 conv. code rate]
Well, if VDR is told this is a DVB-S transponder, while in fact it is
DVB-S2, I'm afraid there's nothing it can do about that.
Have you tried complaining to the provider?
yes, sure.
Answer from provider - please use our official receivers
@klaus
could you change VDR behaviour if in the NIT the rolloff is missing - is it
possible to substitute roll off = 35 instead
of roll off = auto ?
Goga
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 2 channels on Astra 19e not working
With VDR 1.7.5 I am unable to tune 2 DVB-S channels. The signal is strong so not a problem (and they work with my dreambox) TVE 2;LA 2:10979:VC56M2O0S0:S19.2E:22000:167=2:108=esl,109=por:1034:0:30658:1:1033:0 Antena 3;Digital+:10877:VC56M2O0S0:S19.2E:22000:160=2:80=esl:0:0:30610:1:1060:0 I have tried to enter manually the PIDS (this helped with 2 other channels that were not working) but with these two no luck. Can somebody tune them? HAVE you lock ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Fw: Vote your VDR patches
Hi so is there any results for that very important and interesting vote ? Goga we have start a poll at http://www.nmsweb.de/vdr/patch.php where you have the possibility to vote for your favorite VDR patches. ___ 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
[vdr] dvbdevice.c: In member function ‘virt ual void cDvbDevice::StillPicture(const uchar*, int) ’:
Hi with kernel 2.6.29 from debian sid I couldn't compile vdr 174 r...@goga:/usr/src/vdr# make 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 audio.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 channels.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 ci.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 config.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 cutter.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 device.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 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 In file included from dvbdevice.c:17: /usr/include/linux/dvb/video.h:159: error: expected ‘;’ before ‘*’ token /usr/include/linux/dvb/video.h:192: error: expected ‘;’ before ‘*’ token dvbdevice.c: In member function ‘virtual void cDvbDevice::StillPicture(const uchar*, int)’: dvbdevice.c:1275: error: too many initializers for ‘video_still_picture’ dvbdevice.c:1275: error: invalid conversion from ‘char*’ to ‘__s32’ dvbdevice.c:1281: error: too many initializers for ‘video_still_picture’ dvbdevice.c:1281: error: invalid conversion from ‘char*’ to ‘__s32’ make: *** [dvbdevice.o] Ошибка 1 any ideas ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] dvbdevice.c: In member function ‘virt ual void cDvbDevice::StillPicture(const uchar*, int) ’:
Приветствую, Goga777 I applied the patch from http://git.kernel.org/?p=linux/kernel/git/jaswinder/linux-2.6-tip.git;a=commitdiff;h=57b4b9d7b56d283b6619a893341be16d1a0467a6#patch7 but without luck In file included from dvbdevice.c:17: /usr/include/linux/dvb/video.h:159: error: expected ‘;’ before ‘*’ token /usr/include/linux/dvb/video.h:192: error: expected ‘;’ before ‘*’ token dvbdevice.c: In member function ‘virtual void cDvbDevice::StillPicture(const uchar*, int)’: dvbdevice.c:1275: error: too many initializers for ‘video_still_picture’ dvbdevice.c:1275: error: invalid conversion from ‘char*’ to ‘__s32’ dvbdevice.c:1281: error: too many initializers for ‘video_still_picture’ dvbdevice.c:1281: error: invalid conversion from ‘char*’ to ‘__s32’ make: *** [dvbdevice.o] Ошибка 1 -- Удачи, Игорь ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Where do you live and what kind of broadcast do you receive?
Country: Russia Transmission: DVB-S, DVB-S2, DVB-T (soon) Encoding: MPEG-2 for SD, H.264 for SD/HD Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Forthcoming VDR Release To Support VDPAU (???)
imho - some strange article http://www.phoronix.com/scan.php?page=news_itempx=NzEzMA Forthcoming VDR Release To Support VDPAU Posted by Michael Larabel on March 09, 2009 NVIDIA's VDPAU feature for providing greater GPU acceleration during video playback on Linux desktops has experienced great adoption since its November launch. This NVIDIA-spawned video API has already worked its way into open-source projects like MPlayer / FFmpeg, MythTV, Xine, and XBMC. This morning we find out from Stefan Huskamp that a new Linux VDR (Video Disk Recorder) / EasyVDR release is coming soon and it too will feature support for the Video Decode and Presentation API for Unix through its use of the Xine library. The latest release of this German open-source software is version 1.6.0 and it came out last March. The current development release is version 1.7.4. Look for a new release soon with VDPAU support. If Intel ends up implementing VDPAU support times will certainly be great for video playback on Linux, Not only is VDPAU much better than XvMC, but it even allows HD video playback with a very cheap GPU and CPU. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] development infrastructur for VGA2SCART patch set
In general I would have no objections against this. What kind of patches is this all about? I haven't followed this VGA2SCART thing, but a quick lookup showed, that this involves patching XOrg stuff and xineliboutput. That is correct. It requires several programs to be patched. If this is the case, then a single Git repository might not be appropriate. we must distinguish 4 cases. VGA2SCART on: and what about of nvidia vdpau cards ? 1. ATI Radeon without FRC 2. Intel i9xx without FRC 3. ATI Radeon withFRC 4. Intel i9xx withFRC Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] development infrastructur for VGA2SCART patch set
It's a binary driver, so I don't think you can patch anything there. exactly. But many nVidia chips are VGA2SCART capable (without FRC of course) directly with the binary driver. Just a proper xorg.conf is needed. please - could you point out please on proper xorg.conf does that xorg.conf corrected ? http://mymediasystem.net/wp/2009/02/xorg.conf1 Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] information about NO signal
Hi is it possible to implement in VDR the feature as that - If there is NOT any LOCK to write about it like Channel doesn't found Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] ArchVDR
Приветствую, gimli I'm wondering - why do you choose the ArchLinux ? [ANNOUNCE] ArchVDR Anouncing ArchVDR : http://archvdr.sourceforge.net This project holds PKGBUILD's for buildding a Archlinux based VDR platform. Our main focus is on: Budget Systems DVB-S2 Hardware accelerated HDTV. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdpau output to pal tv,
And if the video has to be scaled it would have to scale each field separately then reinterlace them line-by-line at the output resolution Ok, I guess this single issue implies that vdpau is not fully suitable for displaying interlaced material with interlaced output. but what about hdmi output from vdpau cards to LCD TV SET ? is that issue also actually or not ? or that problem exists only for s-video/rgb/component video fro CRT TV SET It's an issue with interlaced output when the source material is interlaced, and no deinterlacing is performed by the gfx card. thanks. Last questions :) If the GPU deinterlacing is performed by the VDPAU card with the different deiinterlacing algos that issue exist ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Small VDR-streamdev patch for Popcorn Hour NMT
Приветствую, Frank For popcornhour the CVS version of streamdev is required. is it need to patch it for vdr 174 ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdpau output to pal tv,
And if the video has to be scaled it would have to scale each field separately then reinterlace them line-by-line at the output resolution Ok, I guess this single issue implies that vdpau is not fully suitable for displaying interlaced material with interlaced output. but what about hdmi output from vdpau cards to LCD TV SET ? is that issue also actually or not ? or that problem exists only for s-video/rgb/component video fro CRT TV SET Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.7.4 + streamdev + Popcorn ???
Hi could someone to run the streaming with vdr 174 + streamdev-plugin for popcorn Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.4 + streamdev + Popcorn ???
could someone to run the streaming with vdr 174 + streamdev-plugin for popcorn Yes, I do have this combination running. Streaming live-tv breaks after a couple of minutes (only tested HD), but other than that it works like a charm (i.e. replaying TS recordings [even while they are being recorded], audio switching in live-tv and recordings)... which streamdev version and which patches do you use ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] rotor and vdr
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
Re: [vdr] rotor and vdr
Приветствую, matthieu is there any working solution for moving of rotor with vdr ? Yes Matthieu PS : I let you search it (hint search in vdr plugin page). do you mean rotor plugin ? But it didn't work correctly with goto xx / goto position on my мвкю Also it couldn't save the satellite position in rotor memory for goto xxx Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor and vdr
I'm using vdr-gotox patch. For which version of vdr do you need it? vdr 174 Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] skinreel3 for vdr 1.7.*
there's nice skin skinreel3 http://vdr-portal.de/board/thread.php?threadid=82604threadview=0hilight=hilightuser=0page=2 seems to me it works only with eHD card is it possible to run it with non eHD vdr-system ? I've wondered the same thing myself. I really like that skin. Along with the new support for hdtv and so on, it would be nice if the osd finally got a nice overhaul. VDR would be unstoppable! :) Did you see the pictures from XBMC patched for vdr? where's it possible to look on that pictures ? This is great! There is only the problem that XBMC doesn't support vdpau :( . ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] skinreel3 for vdr 1.7.*
Hi there's nice skin skinreel3 http://vdr-portal.de/board/thread.php?threadid=82604threadview=0hilight=hilightuser=0page=2 seems to me it works only with eHD card is it possible to run it with non eHD vdr-system ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] skinreel3 for vdr 1.7.*
there's nice skin skinreel3 http://vdr-portal.de/board/thread.php?threadid=82604threadview=0hilight=hilightuser=0page=2 here's sources http://ag1455.nm.ru/VDR/174_skinreel3.tar.bz2 seems to me it works only with eHD card is it possible to run it with non eHD vdr-system ? I've wondered the same thing myself. I really like that skin. Along with the new support for hdtv and so on, it would be nice if the osd finally got a nice overhaul. VDR would be unstoppable! :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.4
Приветствую, Klaus Danke for your work. when are you planning to implement in vdr the native h.264 support ? it will be in vdr 1.7.* branch ? VDR developer version 1.7.4 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.7.4.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.7.3-1.7.4.diff Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.4
when are you planning to implement in vdr the native h.264 support ? it will be in vdr 1.7.* branch ? What do you mean by native h.264 support? VDR just records the TS and sends it to the output device. It doesn't care too much about the actual contents. It's up to the output devices to replay h.264. Or is there something missing that I'm not seeing at the moment? I kept in mind the h264 patch from Reinhard Nissl for vdr 1.7.0. As far as I understand you - for vdr 1.7.4 no need to install any patches for h264 support ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] compiling the xine-1.2 with external ffmpeg
I just compiled the hg xine-lib 1.2 with SVN ffmpeg. In case someone is interested in the same, these are the options required for xine-lib: ./autogen.sh --with-external-ffmpeg /usr/src/xine-lib-1.2# ./configure --help | grep ffmpeg /usr/src/xine-lib-1.2# no need to use now --with-external-ffmpeg option for hg xine-lib 1.2 Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] reelchannelscan with dvb-s2 support ??
Hi could someone create the patch for reelchannelscan with dvb-s2 support ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Choice of recording format
I was just wondering what prompted the move from recording in PES to TS. Is it because TS is more widely supported? see the answer from Nico Sabbi - MPlayer dvb developper as I already explained many times (also to Vdr's developer, since I suspect it's a vdr dump) H264 in mpeg-pes can't be read due to lack of codec qualification http://lists.mplayerhq.hu/pipermail/mplayer-users/2008-May/072986.html Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.3 + reelbox plugin
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. yes, me too Then I used S2API from 23.11.2008 - it is necessary to patch this version reg. Klaus need. you can use fresh http://mercurial.intuxication.org/hg/s2-liplianin I don't have such problem as with v4l-dvb Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
Could some pse tell me what kind of patch and v4l drivers i should use to run vdr-1.7.x in HD mode ? you have to install http://mercurial.intuxication.org/hg/s2-liplianin vdr 170 and 2 patches http://www.linuxtv.org/pipermail/vdr/attachments/20080413/1054bcfb/attachment-0001.bin vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff.bz2 http://www.linuxtv.org/pipermail/vdr/attachments/20081007/edcd3fcc/attachment-0001.obj vdr-1.7.0-s2api-07102008-h264-clean.patch.gz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 1.7.2 xine plugin FIXMEs
Newbie alert!! I'm trying to get started with vdr and dvb-s (and s2 hopefully) and xine. I've downloaded v4l-dvb (30/12), and patched it with v4l-dvb-s2api-add-s2-capability.diff. That builds and installs fine. Modules load fine (for Nova HD-S2) and I can record (and playback) streams using gnutv so I guess the card and its module are ok. I then run vdr (1.7.2) from the command line like this and I get a bunch of FIXMEs: ./vdr -c /etc/vdr -L ./PLUGINS/lib -v /data/video -E/data/video -Pxine -r which seem to indicate that the stream does not begin 0 0 1. GrabImage is there as I had VDRAdmin-AM running, it also seems to have a problem, hopefully the same one.Any ideas where I go with this? please install vdr 170 and 2 patches for it, not vdr 172. For vdr 172 there' is not any software decode plugins (vdr-xine. softdevice,xineliboutput) yet. Let's wait for Also is there a cvs/hg repository for vdr, no any cvs/hg repo for vdr Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.2 and xine-vdpau ?
is someone able to use this combinaison ? In the affirmative, by which way ? xine-plugin gives lots of FIXME and I got about one frame every 3-4 seconds (0.25 fps) for regular mpeg2 channels... I couldn't run vdr 1.7.2 even with regular xine-lib + xineliboutput , I think we should waiting for when vdr 172 support will include in vdr software decode plugins Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VAAPI patches for FFmpeg MPlayer
These patches add VA API support to FFmpeg and MPlayer. HW video decode capabilities depend on the actual VA API implementation. Besides, from an MPlayer perspective, only full-offload (VLD) of the video is supported for the following codecs: MPEG-2 MPEG-4 ASP (DivX) MPEG-4 AVC (H.264) http://www.splitted-desktop.com/~gbeauchesne/mplayer-vaapi/ http://www.freedesktop.org/wiki/Software/vaapi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VAAPI patches for FFmpeg MPlayer
These patches add VA API support to FFmpeg and MPlayer. HW video decode capabilities depend on the actual VA API implementation. Besides, from an MPlayer perspective, only full-offload (VLD) of the video is supported for the following codecs: MPEG-2 MPEG-4 ASP (DivX) MPEG-4 AVC (H.264) http://www.splitted-desktop.com/~gbeauchesne/mplayer-vaapi/ http://www.freedesktop.org/wiki/Software/vaapi need to clarify http://www.phoronix.com/scan.php?page=articleitem=xorg_vaapi_mplayernum=1 The Video Acceleration API has gone through several revisions this year and last year, but it has yet to see any wide adoption. The libVa library provides the VA-API implementation and is put out under an open-source MIT license while the only driver implementing VA-API support is the Poulsbo video driver. The Intel Poulsbo graphics driver is closed-source while their DRM kernel driver is open-source. Poulsbo is the code-name for Intel's MID (Mobile Internet Device) chipset that is used in conjunction with the Silverthorne Atom processors. However, the Poulsbo chipset is used on very few netbooks and the MIDs with these chipsets are not very common (at least not in the US). One system that does use this chipset is the Dell Inspiron Mini 12. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EPG for Hotbird / russian programmes
Приветствую, Harald what do you mean ? No any problem with Russian EPG currently on vdr 160 / 170, I checked on W4 36E 2 years after my last question about russian EPGs I need to ask again. The tvgrabru set on free-x.de is out of date, and there seems to be no other source of information. Has anybody been working on this topic lately? TIA, and have a nice Xmas (in case you dou celebrate it) and a happy new year. On Wed, Nov 29, 2006 at 06:58:57PM +0100, Harald Milz wrote: now that my VDR works fine with 2 satellites thanks to the help of some kind folks here and the SourceCaps patch (did I mention it should be in the mainstream VDR?) I have now a couple of FTA programmes in russian language for my better half :-) The only problem is, none of these programmes carry -- Удачи, Игорь ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EPG for Hotbird / russian programmes
anyway have a look please http://www.free-x.de/xmltv/ 2 years after my last question about russian EPGs I need to ask again. The tvgrabru set on free-x.de is out of date, and there seems to be no other source of information. Has anybody been working on this topic lately? TIA, and have a nice Xmas (in case you dou celebrate it) and a happy new year. On Wed, Nov 29, 2006 at 06:58:57PM +0100, Harald Milz wrote: now that my VDR works fine with 2 satellites thanks to the help of some kind folks here and the SourceCaps patch (did I mention it should be in the mainstream VDR?) I have now a couple of FTA programmes in russian language ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.7.2 with budget cards ?
Hi I'm wondering could somebody to watch dvb mpeg2 channels with vdr 172 based on budget card ? I couldn't Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.7.2 + h264-patch + xineliboutput + vdr-xine + softdevice
Dears developers of such nice these plugins/patch are you planing to adapt your plugins to vdr 172 ? Will someone release h264 patch for vdr 172 ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.2 + h264-patch + xineliboutput + vdr-xine + softdevice + reelchannelscan
I forgot to mention the reelchannelscan :) Dears developers of such nice these plugins/patch are you planing to adapt your plugins to vdr 172 ? Will someone release h264 patch for vdr 172 ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
I just wanted to download the dvb-apps from linuxtv.org, but apparently all those repositories are gone, http://linuxtv.org/hg/dvb-apps is empty. Any idea where to get the scan-s2 source now? http://mercurial.intuxication.org/hg/scan-s2/ also you can try new dvb-s/dvb-s2 scanner - xmlscan http://hg.kewl.org/dvb2010/ Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] XBMC + VDR 1.7.0
http://www.youtube.com/watch?v=_Cl70fq7sn8 here's you can have a look on xbmc and integrated in it vdr Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
I hope you don't buy an eHD card since I don't believe it's the way to go and it would drive VDR in the wrong direction. I'm sitting here with a €65 nvidia 8200-based motherboard playing 1080p videos with the cpu 97% idle using vdpau and ffmpeg! which cpu do you have ? What about pictures quality on your TVset ? are you using hdmi ? so , did you test a lot of 1080i/1080p samples ? or only test samples from NVidia ? That's NOT software decoding if you ask it's GPU decoding :) me. And now that hdmi audio finally works with nvidia it's just awesome. ah, fine I REALLY hope the xine guys will get this running soon. +1 Btw, thanks to Klaus and the rest for all the work you put into this. +1 too :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API
Is ther a problem with vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup patch fom Reinhard Nilsl ? Could this patch be included in vdr-1.7.2 like S2API patch? yes, it will be great Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API
Приветствую, Klaus does your vdr-1.7.1-s2api.diff good for vdr 1.7.0 ? The attached patch is what I've gathered from various postings regarding adapting VDR to the S2API driver API (thanks to Igor M. Liplianin, Niels Wagenaar and Edgar Hucek - did I forget anybody?). Since the S2SAPI doesn't provide a way of determining whether a DVB-S device supports DVB-S2 (at least I didn't find any), you need to apply the second attached patch to the driver in order to impelement a new capability flag that reports the availability of DVB-S2 support. If you don't want to patch the driver, you can change the line case FE_QPSK: frontendType = (frontendInfo.caps FE_CAN_2ND_GEN_MODULATION) ? SYS_DVBS2 : SYS_DVBS; break; in dvbdevice.c to avoid FE_CAN_2ND_GEN_MODULATION. Either set frontendType permanently to SYS_DVBS or SYS_DVBS2, depending on what you have. So far DVB-S and DVB-S2 appears to tune fine. DVB-C is completely untested. With DVB-T tuning doesn't work, even though my TDA10046H based DVB-T card does work with the S2API driver under VDR 1.6.0. So for the moment I would appreciate if people could test DVB-T tuning and check whether maybe I made some silly mistake in the DVB-T tuning code. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API
Приветствую, Goga777 Приветствую, Klaus does your vdr-1.7.1-s2api.diff good for vdr 1.7.0 ? ah, no /vdr170# patch -p1 vdr-1.7.1-s2api_from_Klaus.diff patching file channels.c Hunk #6 succeeded at 636 (offset -1 lines). Hunk #7 succeeded at 643 (offset -1 lines). Hunk #8 succeeded at 665 (offset -1 lines). Hunk #9 succeeded at 685 (offset -1 lines). patching file channels.h Hunk #2 succeeded at 146 (offset -1 lines). Hunk #3 succeeded at 203 (offset -2 lines). Hunk #4 succeeded at 215 (offset -2 lines). patching file dvbdevice.c Hunk #7 FAILED at 265. Hunk #8 FAILED at 323. Hunk #9 succeeded at 407 (offset 11 lines). Hunk #10 succeeded at 430 (offset 11 lines). Hunk #11 succeeded at 493 (offset 11 lines). Hunk #12 succeeded at 831 (offset 11 lines). 2 out of 12 hunks FAILED -- saving rejects to file dvbdevice.c.rej patching file dvbdevice.h patching file menu.c patching file nit.c ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] MythTV Adds Support For NVIDIA VDPAU
FYI http://www.phoronix.com/scan.php?page=news_itempx=Njg4Ng Posted by Michael Larabel on November 29, 2008 Last month NVIDIA brought PureVideo features to Linux through a new API they call the Video Decode and Presentation API for Unix in their NVIDIA 180.xx driver. NVIDIA also provided a set of patches that enabled MPlayer to use this API that offloads video decoding and other tasks to the GPU. The formats supported by VDPAU are currently H.264, MPEG, WMV3, and VC-1. In our VDPAU benchmarks we found this NVIDIA video implementation to work very well and the CPU usage was much lower during video playback. With NVIDIA providing a header file in the driver that details this API, the community has been able to study VDPAU and one of the first fruits of this work is now available. Committed to MythTV is a VDPAU decoder. VDPAU in MythTV has full OSD (On-Screen Display), de-interlacers, color controls, and codecs support through the Video Decode and Presentation API for Unix. MythTV will automatically use VDPAU when it's compatible with the video format otherwise it falls back to using X-Video. According to those that have tested it already, this community VDPAU implementation in MythTV actually exceeds that of NVIDIA's patch in MPlayer when it comes to quality and its capabilities. This should be great news to anyone with a recent NVIDIA graphics card that uses MythTV for their HTPC needs. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-femon-1.6.4 / vdr-skinsoppalusikka-1.6.3
Приветствую, Rolf This femon release should fix those reported hangups while zapping through channels. Femon: == 2008-11-30: Version 1.6.4 - Added new helper functions. - Updated Italian translation (Thanks to Diego Pierotto). - Fixed a memory leak. - Added a check for the minimum OSD height. - Replaced Use single area (8bpp) option with VDR's Setup/OSD/Anti-alias. - Removed the FEMON_NTSC option. - Fixed a deadlock in cFemonReceiver (Thanks to Antti Seppälä for reporting this one). http://www.saunalahti.fi/~rahrenbe/vdr/femon/ btw - do you know - the femon is winner of VDR Plugin Survey 2008 http://www.e-tobi.net/blog/2008/11/29/vdr-plugin-survey-2008-auswertung-teil-2 http://www.e-tobi.net/vdr-plugin-survey-2008/ Survey results for the plugin 'femon' = 330 from 574 survey participants are using this plugin). Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput software scaling on fly
Hi is it possible to implement in xineliboutput the on fly software scaling on fly (as it has been realize in vdr-xine) ? I mean the option - Video - Software scaling - yes - Change video size http://ag1455.nm.ru/VDR/IMG_1056.JPG Need to restart vdr and after that new settings will apply. It's not comfortable. Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Converting H264 vdr 1.7.0 recordings to xvid (or x264) in avi container
I have a little question about vdr recording format when in H264 (BBC HD), currently I can convert with mencoder my recording made from my HD terminal after converting trp to ts. When I try to mplayer the same vdr recording (ie 001.vdr) it find no video track. I can only see them with xine from vdr or from command line Does anybody has successfully convert those records ? Thanks for help you must use a different demuxer with mplayer: $ mplayer -demuxer lavf 001.vdr Will playback the recording. thanks for your advice. It's working :) I didn't know about this hint btw - when MPlayer developers implement such method ? recently ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] femon 1.6.3 - some remarks
I have installed femon 163 with my vdr 170. There's some remarks concerning of h264 channels no any information in CoderateH (I can see only ---) The plugin doesn't support multiproto/S2API and therefore channels using new coderates like 9/10 are shown as data invalid (---). ok, I will check with another fec in BITRATE field I can see only ---(6 Mbit/s) FRAME RATE - --- Codec - H264 I don't have any access to H.264 (or HE-AAC) streams so support for these are more like academic. The bitrate, framerate, and scan type aren't parsed at the moment as my blindly written code didn't worked right from the start. This particular piece of code was hidden behind #if pragmas in femonh264.c, so it would be nice, if someone could take a look at it and send be a patch. -- |## Channel Name ## [AR][VF][A/DD][D]| |[ Signal Strength in % ==|=]| |[ Signal-to-Noise Ratio in % |=]| | STR: # (0%) BER: # Video: 0 Mbit/s | | SNR: # (0%) UNC: # Audio: 0 kbit/s | | [LOCK] [SIGNAL] [CARRIER] [VITERBI] [SYNC] | -- I can see without any problem video/audio bitrate on the top right of OSD (that's why the bitrate is parsed at the moment correctly) , but I don't see video/audio bitrate below in OSD Audio stream #0 () Codec - --- Channel Mode - --- Bitrate - --- Sampling Frequency - --- This looks also ok. Non-existent audio pid provides no stream information. I guess your channel contained only ac3 audio or no audio at all. again - I can see without any problem video/audio bitrate on the top right of OSD (that's why the bitrate is parsed at the moment correctly) , but I don't see video/audio bitrate below in OSD of femon If I try to switch channel up/down with OSD femon menu my vdr will hang up I cannot reproduce this on my setup. Please, use vanilla (or _only_ liemikuutio patched) VDR for testing. There 2 active femon users (me and my friend), so the testing has been quite light - at least I haven't got any bug/success reports from other users. :) the same problem was described on our Russian-vdr forum from other vdr user. It wasn't happened on previous femon versions. I will not be able to run vanilla vdr 170 because I have s2api drivers Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR - S2API: 2 questions
After quite a while away from VDR development, I've dedicated this weekend to switching VDR to S2API (TS recording will be postponed). Just two quick questions: - Where do I find the ultimate, latest, greatest S2API driver source? I would assume it is at http://linuxtv.org/hg/v4l-dvb, but with all the recent patching and various repositories, I'm unsure... imho, http://mercurial.intuxication.org/hg/s2-liplianin/ also good choise. Igor has implemented some improvements in drivers, that's why with s2-liplianin possible to work with dvb-s/svb-s2 channels which have high and low SR. I don't know why these improvements didn't include in v4l-dvb tree. - Is there a patch available that implements the S2API changes into VDR? I've seen some postings about such a patch, but IIRC it also containes several other things that are unrelated to the plain S2API change. for vdr 170 it's s2api patch from Niels Wagenaar http://www.linuxtv.org/pipermail/vdr/2008-October/017964.html it is working perfectly on my vdr 170 Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR - S2API: 2 questions
After quite a while away from VDR development, I've dedicated this weekend to switching VDR to S2API (TS recording will be postponed). Just two quick questions: - Where do I find the ultimate, latest, greatest S2API driver source? I would assume it is at http://linuxtv.org/hg/v4l-dvb, but with all the recent patching and various repositories, I'm unsure... imho, http://mercurial.intuxication.org/hg/s2-liplianin/ also good choise. Igor has implemented some improvements in drivers, that's why with s2-liplianin possible to work with dvb-s/svb-s2 channels which have high and low SR. I don't know why these improvements didn't include in v4l-dvb tree. People using some STB0899 versions will have their demodulators burned due to the demodulator running with a too high unsupported clock of 135MHz. The STB0899 is rated to run at a maximum of 99 MHz only. The safe bet is to use http://linuxtv.org/hg/v4l-dvb Manu with http://linuxtv.org/hg/v4l-dvb is it possible to lock dvb-s2 8psk channels with sr=3 and dvb-s channels with sr44 ? of course, the safety is first, nobody want to burn the dvb card. But which solution do you propose for owners of stb0899 cards and who want to see the dvb-s/dvb-s2 channels with low/high SR ? to sell stb0899 based cards and to buy cx24116 based card ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput crashes when closing t he xineliboutput/videomenu
This is the most annoying bug : after some time tweaking the video output (which works), the video submenu just crashes VDR upon closing (with back, menu or ok keys). No matter that I change setting or not : closing will crash. The current video setup is : xineliboutput.Video.AspectRatio = 0 xineliboutput.Video.AutoCrop = 0 xineliboutput.Video.AutoCrop.AutoDetect = 1 xineliboutput.Video.AutoCrop.DetectSubs = 1 xineliboutput.Video.AutoCrop.FixedSize = 1 xineliboutput.Video.AutoCrop.SoftStart = 1 xineliboutput.Video.Brightness = -1 xineliboutput.Video.Contrast = -1 xineliboutput.Video.Deinterlace = bob xineliboutput.Video.DeinterlaceOptions = method=Linear,cheap_mode=1,pulldown=none,framerate_mode=full,judder_correction=1,use_progressive_frame_flag=1,chroma_filter=0,enabled=1 xineliboutput.Video.Driver = xxmc xineliboutput.Video.FieldOrder = 0 xineliboutput.Video.HUE = -1 xineliboutput.Video.IBPTrickSpeed = 0 xineliboutput.Video.MaxTrickSpeed = 12 xineliboutput.Video.Overscan = 0 xineliboutput.Video.Port = :0.0 xineliboutput.Video.Saturation = -1 xineliboutput.Video.Scale = 0 xineliboutput.Video.SwScale = 0 xineliboutput.Video.SwScale.Aspect = 0 xineliboutput.Video.SwScale.Downscale = 0 xineliboutput.Video.SwScale.Height = 576 xineliboutput.Video.SwScale.Resize = 0 xineliboutput.Video.SwScale.Width = 720 xineliboutput.VideoModeSwitching = 1 I guess there is some kind of impossibility here, but I didn't tweak these setting manually. (I didn't find an english-speaking xineliboutput-specific mailing list anywhere, so I guess the good spot is here) you can send gdb ouput of crash to this list http://sourceforge.net/mailarchive/forum.php?forum_name=xineliboutput-devel xineliboutput-devel Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] femon 1.6.3 - some remarks
in BITRATE field I can see only ---(6 Mbit/s) I can see without any problem video/audio bitrate on the top right of OSD (that's why the bitrate is parsed at the moment correctly) , but I don't see video/audio bitrate below in OSD Sorry, I don't quite get your explanation, but femon shows two different bitrates: one in the status window is always a calculated bitrate and in the bigger detailed information window there are both the nominal bitrate parsed from the video stream (--- above) and the calculated one in brackets (6 MBit/s above). The calculated bitrate is always available if enabled in setup as it simply calculates the data rate of a selected pid in defined time period. The nominal bitrate is kind of maximum bitrate value as a hint for the decoder. ok, I see. btw - here's you can have a look on screenshots with femon 163 + vdr 170 + s2api patch + h264 patch http://ag1455.nm.ru/VDR/176.png http://ag1455.nm.ru/VDR/175.png the same problem was described on our Russian-vdr forum from other vdr user. It wasn't happened on previous femon versions. I will not be able to run vanilla vdr 170 because I have s2api drivers As I already told you, the femon doesn't support = vdr-1.7.0 (yet), so does this hang happen also in the latest vdr-1.6.0 series? no, with early femon and vdr version I didn't note this vdr hung up Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] femon 1.6.3 - some remarks
I confirm also that femon 163 + vdr 1.7.0 + H264 + multiproto hang when you change channel while femon is displaying info, happen often when going from H264 to Mpeg2 channels (like simul HD and Simul SD on Astra 19.2) No problem at all if you close femon before switching channels I'm happy to see that you have signal strength with S2API, with multiproto plus on S2-3200 nothing appears (Quality + level = 0) :o( with hvr4000 and multiproto I had signal strength and SNR with old femon version. do you have this figures (snr/sig) with szap-s2 or xmlscan ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
