Re: [vdr] PVRinput Ideas..
Am Donnerstag, 7. Januar 2010 04:10:21 schrieb Rob Davis: > Would it be possible to get the pvrinput plugin to be able to create > different channels line which all call the same s-video channel this works: Test1:1:PVRINPUT|SVIDEO1:P:0:301=2:300:305:0:9012:0:0:0 Test2:1:PVRINPUT|SVIDEO1:P:0:301=2:300:305:0:9013:0:0:0 Test3:1:PVRINPUT|SVIDEO1:P:0:301=2:300:305:0:9014:0:0:0 > but also > call the channel change script? I will think about a possibility to call an external script (e.g. /usr/local/bin/extern_channelswitch.sh) in SetChannelDevice() with two parameters: card-number (e.g. 1 if the available pvrinput device that will be used is /dev/video1) and the SID (Service-Id, e.g. 9012 for channel 12 in your receiver) > All it would need to do would be execute the program dct6200 (which > could be in the /etc/vdr/plugins/pvrinput directory) with the argument > of 41 or 08 and the cable box would change. This would also work for > someone using an irblaster with a SkyBox and a PVR card. you would need to write a bash-Script (extern_channelswitch.sh) that executes your dct6200 binary with the needed commands. Should be simple. Please contact me privately with an example how your dct6200 binary has to be called. Is "dct6200 12" sufficient to switch to channel 12? This solution could indeed be useful for other users, as it is not limited to your box. The script could execute lirc irsend or whatever. I can't promise too much but I have an idea and will see if I get it working. Greets, Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PCR pid
Hi Klaus, Thanks for your answer and sorry for replaying so late. Setting Ppid to 0x1FFF means disable it. The effect is that some mpeg2 players refuse to play vdr recordings. I think that the PCR pid is more important in recordings than in live viewing, because in live viewing the timing is implicit in the packet time of arrival. When you have a file you lose that information because you try to fill the playing buffer. What I said is anyway wrong, because PCR is part of the mpeg2 standard and it have to be present in the stream. Maybe, the particular implementation of the mpeg2 decoder in the DVB FF card derives its internal clock using the framerate of the mpeg2 stream, but it is not standard. Giampaolo P.S. I liked very much the architecture of the 1.7.11 regarding the dvb FF support. I think that the more VDR will be hardware agnostic, the more its architecture will be well designed. -Original Message- From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of Klaus Schmidinger Sent: sabato 5 dicembre 2009 12:27 To: vdr@linuxtv.org Subject: Re: [vdr] PCR pid On 26.11.2009 13:51, Giampaolo Sica wrote: >> Maybe because you haven't applied it to your copy of version 1.7.10? ;-) > > :))) > >> In hindsight I'm not sure whether the change "Fixed writing the PCR pid >> into the PMT in cPatPmtGenerator::GeneratePmt()" was a good idea, because >> VDR doesn't record the PCR pid at all. > >> I tend to revert that change, because I don't think that >> a separate PCR pid is necessary in a recording. AFAIK the >> PCR pid is only for live viewing. > >> Klaus > > > Yes, you're right if you are replaying recordings on a FF card, but: > > 1) Some players refuse to play TS streams without PCR information (screen > remains black). > 2) I'm porting VDR to IPBOX 9000HD (STi710x based STB... yes, I know there > is enigma2, but I've been using vdr since 2000 and I love it) and the PCR > pid is essential to have the timeline while watching recording, because the > ioctl DMX_GET_STC fails and the only way to you get time information is from > the video/audio decoder (VIDEO_GET_PTS/ AUDIO_GET_PTS). So, even if I wrote > a plugin for this device, I'd have to patch the base classes that is in > contrast with the plugins philosophy Can you please try what happens if you set int Ppid = 0x1FFF; in cPatPmtGenerator::GeneratePmt()? As far as I understand the PCR (please correct me if I'm wrong), it only has a meaning in live mode, where PCR packets arrive at precise points in time and are used to syncronize the player's internal clock. When replaying a recording, it is not defined when the PCR packets arrive at the player, and thus they have no meaning. Klaus ___ 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] [Patch] Allow to limit SVDRP port to given IP
Hello, the INSTALL file in the VDR source code says: WARNING: DUE TO THE OPEN SVDRP PORT THIS PROGRAM MAY CONSTITUTE A === POTENTIAL SECURITY HAZARD! IF YOU ARE NOT RUNNING VDR IN A CONTROLLED ENVIRONMENT, YOU MAY WANT TO DISABLE SVDRP BY USING '--port=0'! This is a solution, but it also makes it impossible to use svdrpsend.pl on the local VDR and so makes scripts fail, which want to send status messages to VDR and makes it impossible to to remap the power key to call "svdrpsend.pl HITK POWER". A much better solution would be to allow to just open the SVDRP port on "localhost", so only local software is able to use it and the port is not accessible from network. I've attached a patch, which makes the following command line a valid command line for VDR: vdr -p 127.0.0.1:2001 Any other IP may be specified, too, for example to get VDR to listen only on one NIC on a machine with multiple NICs. The patch is only a proof of concept. It uses a global variable to hold the IP, as this was the minimally invasive way to modify VDR. This should be modified in a final version of the patch. I'll make a nicer version, if Klaus thinks, that this feature may be interesting for VDR. The patch can be applied to VDR 1.6.0-2 with or without extensions patch and VDR 1.7.10. I didn't try 1.7.11, but most probably the patch will work there, too. Yours Manuel Reimer -- () ascii ribbon campaign - against html mail /\- gegen HTML-Mail answers as html mail will be deleted automatically! Antworten als HTML-Mail werden automatisch gelöscht! Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser vdr-1.6.0-2_setip.diff Description: Binary data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Patch] Allow to limit SVDRP port to given IP
On 08.01.2010 13:27, Manuel Reimer wrote: > Hello, > > the INSTALL file in the VDR source code says: > > WARNING: DUE TO THE OPEN SVDRP PORT THIS PROGRAM MAY CONSTITUTE A > === POTENTIAL SECURITY HAZARD! IF YOU ARE NOT RUNNING VDR IN > A CONTROLLED ENVIRONMENT, YOU MAY WANT TO DISABLE SVDRP > BY USING '--port=0'! > > This is a solution, but it also makes it impossible to use svdrpsend.pl on > the local VDR and so makes scripts fail, which want to send status messages > to VDR and makes it impossible to to remap the power key to call > "svdrpsend.pl HITK POWER". > > A much better solution would be to allow to just open the SVDRP port on > "localhost", so only local software is able to use it and the port is not > accessible from network. > > I've attached a patch, ... What about svdrphosts.conf? # # svdrphostsThis file describes a number of host addresses that # are allowed to connect to the SVDRP port of the Video # Disk Recorder (VDR) running on this system. # Syntax: # # IP-Address[/Netmask] # 127.0.0.1 # always accept localhost #192.168.100.0/24 # any host on the local net #204.152.189.113 # a specific host #0.0.0.0/0# any host on any net (USE THIS WITH CARE!) Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PCR pid
On 08.01.2010 12:19, Giampaolo Sica wrote: > Hi Klaus, > > Thanks for your answer and sorry for replaying so late. > > Setting Ppid to 0x1FFF means disable it. The effect is that some mpeg2 > players refuse to play vdr recordings. > > I think that the PCR pid is more important in recordings than in live > viewing, because in live viewing the timing is implicit in the packet time > of arrival. When you have a file you lose that information because you try > to fill the playing buffer. > > What I said is anyway wrong, because PCR is part of the mpeg2 standard and > it have to be present in the stream. > > Maybe, the particular implementation of the mpeg2 decoder in the DVB FF card > derives its internal clock using the framerate of the mpeg2 stream, but it > is not standard. Can you point to some documentation that specifies how the PCR data is actually used during replay of a recording? I find it very hard to believe that this can actually be used, because you just can't syncronize a local clock to the PCR if the PCR packets don't arrive in real time. Klaus > -Original Message- > From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of > Klaus Schmidinger > Sent: sabato 5 dicembre 2009 12:27 > To: vdr@linuxtv.org > Subject: Re: [vdr] PCR pid > > On 26.11.2009 13:51, Giampaolo Sica wrote: >>> Maybe because you haven't applied it to your copy of version 1.7.10? ;-) >> :))) >> >>> In hindsight I'm not sure whether the change "Fixed writing the PCR pid >>> into the PMT in cPatPmtGenerator::GeneratePmt()" was a good idea, because >>> VDR doesn't record the PCR pid at all. >>> I tend to revert that change, because I don't think that >>> a separate PCR pid is necessary in a recording. AFAIK the >>> PCR pid is only for live viewing. >>> Klaus >> >> Yes, you're right if you are replaying recordings on a FF card, but: >> >> 1) Some players refuse to play TS streams without PCR information (screen >> remains black). >> 2) I'm porting VDR to IPBOX 9000HD (STi710x based STB... yes, I know there >> is enigma2, but I've been using vdr since 2000 and I love it) and the PCR >> pid is essential to have the timeline while watching recording, because > the >> ioctl DMX_GET_STC fails and the only way to you get time information is > from >> the video/audio decoder (VIDEO_GET_PTS/ AUDIO_GET_PTS). So, even if I > wrote >> a plugin for this device, I'd have to patch the base classes that is in >> contrast with the plugins philosophy > > Can you please try what happens if you set > > int Ppid = 0x1FFF; > > in cPatPmtGenerator::GeneratePmt()? > > As far as I understand the PCR (please correct me if I'm wrong), it only > has a meaning in live mode, where PCR packets arrive at precise points in > time and are used to syncronize the player's internal clock. > When replaying a recording, it is not defined when the PCR packets arrive > at the player, and thus they have no meaning. > > Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multiple non-independent frontends
On 06.01.2010 19:30, Anssi Hannula wrote: > Klaus Schmidinger wrote: >> On 06.01.2010 14:22, Tomasz Bubel wrote: >>> [...] - Added support for DVB cards with multiple fontends. Note that this only works for DVB cards where each frontend can be used independently of all the others on the same adapter. >>> [...] >>> Any chance of using using DVB-T frontend on HVR-4000? This card have 2 >>> separate frontends. And as quoted on >>> http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-4000: >>> >>> "Multiple frontends are supported: DVB-S/S2 and DVB-T appear as >>> /dev/dvb/adapterN/frontend0 and /dev/dvb/adapterN/frontend1 >>> respectively. >>> >>> Due to a hardware limitation, the two frontends cannot be used >>> simultaneously. However they can be used sequentially within the same >>> application. The driver handles the mutual exclusion appropriately." >> Well, that's still a problem. >> Is there a defined way (via the LinuxDVB driver API) through which VDR >> can find out whether the frontends can be used independently? > > Shouldn't all frontends that are independent show up as completely different > adapters in /dev/dvb/, so that VDR can assume only one frontend per adapter > is > usable simultaneously? I would love it if I could assume that with an adapter with several frontends, only *one* of these frontends could be used at any given time, and that, if a DVB hardware provides several frontends that can be used simultaneously, these would appear as separate adapters with one frontend each. That would be a simple, straightforward setup. But apparently things aren't meant to be simple... :-( Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.11
On 06.01.2010 23:24, Goga777 wrote: >>> could you comment please about this change >>> - The support for full featured DVB cards of the TT/FuSi design has been moved into the new plugin 'dvbsddevice'. >>> which advantages and improvements is waiting us ? >> At this point this is merely the reaction on many comments >> that VDR would be too tailored towards the FF-DVB cards. >> Well, it's also in preparation for things that will hopefully come soon ;-) > > do you mean FF DVB-S2 cards ? :-) Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.11
On 06.01.2010 20:31, JW wrote: > Am Mittwoch, den 06.01.2010, 13:34 +0100 schrieb Klaus Schmidinger: >> VDR developer version 1.7.11 is now available at > > ... > >> The changes since version 1.7.10: >> > ... >> - Implemented handling the "Content Descriptor" (based on a patch from Rolf >> Ahrenberg). The 'classic', 'sttng' and 'curses' skins display the textual >> representation of the content descriptors as "genre". The epg.data file >> stores >> the genre using the tag character 'G'. > > Believe it or not, I was working on this patch this afternoon. I should > have checked my emails earlier. But how about changing all these > #defines in enumeration in epg.h? I also changed the names the way, that > they fit better to the rest of vdr's source code (patch attached). Adopted for version 1.7.12. I also changed "mask" to "group", because these values are not really mask values. Please provide your real name if you care to be mentioned in VDR/CONTRIBUTORS. > ARD also sends some kind of user defined Content Descriptor, but > unfortunately it's nowhere documented. The DVB standard should never have allowed any "user defined" stuff... :-( Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Patch] Allow to limit SVDRP port to given IP
Original-Nachricht > Datum: Fri, 08 Jan 2010 14:57:12 +0100 > Von: Klaus Schmidinger > An: VDR Mailing List > Betreff: Re: [vdr] [Patch] Allow to limit SVDRP port to given IP > What about svdrphosts.conf? It just denies someone to access. The port is still available, accessible and in worst case also attackable. IIRC it is even required to accept the connection at first, to find out the IP of the computer, which tries to access and then to drop the connection in a second step. IMHO the better way, from the security standpoint, is to get the port closed, so a potential attacker isn't able to get to it at all. Most other daemons, which open ports, allow such configuration, like cups, apache and others. svdrphosts.conf, of course, still is needed for fine-configuration of allowed hosts (other daemons also have this), but limiting the port to localhost would be the better alternative to just disabling svdrp by setting the port to zero, as currently recommended in the INSTALL file. If someone wants to configure his system to have a minimum of ports opened to the outside world (like me), then *disabling* svdrp is never a good solution, as this breaks scripts and other external features. The only thing, I'm unsure about, is, if we really need to specify an IP. A simple switch like "--svdrp-localhost" (or similar) would also do the job. But my first solution has the advantage, that there is no additional switch needed. Yours Manuel -- () ascii ribbon campaign - against html mail /\- gegen HTML-Mail answers as html mail will be deleted automatically! Antworten als HTML-Mail werden automatisch gelöscht! GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Patch] Allow to limit SVDRP port to given IP
On 08.01.2010 16:56, Manuel Reimer wrote: > Original-Nachricht >> Datum: Fri, 08 Jan 2010 14:57:12 +0100 >> Von: Klaus Schmidinger >> An: VDR Mailing List >> Betreff: Re: [vdr] [Patch] Allow to limit SVDRP port to given IP > >> What about svdrphosts.conf? > > It just denies someone to access. The port is still available, accessible and > in worst case also attackable. IIRC it is even required to accept the > connection at first, to find out the IP of the computer, which tries to > access and then to drop the connection in a second step. IMHO the better way, > from the security standpoint, is to get the port closed, so a potential > attacker isn't able to get to it at all. Most other daemons, which open > ports, allow such configuration, like cups, apache and others. > > svdrphosts.conf, of course, still is needed for fine-configuration of allowed > hosts (other daemons also have this), but limiting the port to localhost > would be the better alternative to just disabling svdrp by setting the port > to zero, as currently recommended in the INSTALL file. If someone wants to > configure his system to have a minimum of ports opened to the outside world > (like me), then *disabling* svdrp is never a good solution, as this breaks > scripts and other external features. > > The only thing, I'm unsure about, is, if we really need to specify an IP. A > simple switch like "--svdrp-localhost" (or similar) would also do the job. > But my first solution has the advantage, that there is no additional switch > needed. How about this: if svdrphosts.conf contains only one single IP number, then open the port for only that IP number. Otherwise i needs to be opened generally, anyway. BTW: please don't CC: me - I am subscribed to the list ;-) Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PCR pid
Hi Klaus, in the iso13818-1 (you can find a copy at http://neuron2.net/library/mpeg2/iso13818-1.pdf), in the section 2.4.2.2 Input to the Transport Stream system target decoder, is explained how the PCR is used to reconstruct the transport stream clock. Giampaolo -Original Message- From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of Klaus Schmidinger Sent: venerdì 8 gennaio 2010 15.01 To: vdr@linuxtv.org Subject: Re: [vdr] PCR pid On 08.01.2010 12:19, Giampaolo Sica wrote: > Hi Klaus, > > Thanks for your answer and sorry for replaying so late. > > Setting Ppid to 0x1FFF means disable it. The effect is that some mpeg2 > players refuse to play vdr recordings. > > I think that the PCR pid is more important in recordings than in live > viewing, because in live viewing the timing is implicit in the packet time > of arrival. When you have a file you lose that information because you try > to fill the playing buffer. > > What I said is anyway wrong, because PCR is part of the mpeg2 standard and > it have to be present in the stream. > > Maybe, the particular implementation of the mpeg2 decoder in the DVB FF card > derives its internal clock using the framerate of the mpeg2 stream, but it > is not standard. Can you point to some documentation that specifies how the PCR data is actually used during replay of a recording? I find it very hard to believe that this can actually be used, because you just can't syncronize a local clock to the PCR if the PCR packets don't arrive in real time. Klaus > -Original Message- > From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of > Klaus Schmidinger > Sent: sabato 5 dicembre 2009 12:27 > To: vdr@linuxtv.org > Subject: Re: [vdr] PCR pid > > On 26.11.2009 13:51, Giampaolo Sica wrote: >>> Maybe because you haven't applied it to your copy of version 1.7.10? ;-) >> :))) >> >>> In hindsight I'm not sure whether the change "Fixed writing the PCR pid >>> into the PMT in cPatPmtGenerator::GeneratePmt()" was a good idea, because >>> VDR doesn't record the PCR pid at all. >>> I tend to revert that change, because I don't think that >>> a separate PCR pid is necessary in a recording. AFAIK the >>> PCR pid is only for live viewing. >>> Klaus >> >> Yes, you're right if you are replaying recordings on a FF card, but: >> >> 1) Some players refuse to play TS streams without PCR information (screen >> remains black). >> 2) I'm porting VDR to IPBOX 9000HD (STi710x based STB... yes, I know there >> is enigma2, but I've been using vdr since 2000 and I love it) and the PCR >> pid is essential to have the timeline while watching recording, because > the >> ioctl DMX_GET_STC fails and the only way to you get time information is > from >> the video/audio decoder (VIDEO_GET_PTS/ AUDIO_GET_PTS). So, even if I > wrote >> a plugin for this device, I'd have to patch the base classes that is in >> contrast with the plugins philosophy > > Can you please try what happens if you set > > int Ppid = 0x1FFF; > > in cPatPmtGenerator::GeneratePmt()? > > As far as I understand the PCR (please correct me if I'm wrong), it only > has a meaning in live mode, where PCR packets arrive at precise points in > time and are used to syncronize the player's internal clock. > When replaying a recording, it is not defined when the PCR packets arrive > at the player, and thus they have no meaning. > > Klaus ___ 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] [Patch] Allow to limit SVDRP port to given IP
Hi! Klaus Schmidinger schrieb: > How about this: if svdrphosts.conf contains only one single IP number, then > open the port for only that IP number. Otherwise i needs to be opened > generally, > anyway. AFAIK one can only bind an IP socket to a local address (usually corresponding to a network interface, e.g. 127.0.0.1) or 0.0.0.0, so if I want to accept SVDRP _from_ a specific address via eth0, I have to bind to the address configured on eth0. As I get the peer address via accept(), I can directly determine if I want to "risk" talking to (or even reading from) it, I assume VDR does exactly this by looking up the address in svdrphosts.conf. IMHO: If there is a vulnerability that is effective when one only calls accept(), this is a problem of the OS (Kernel/libc). If one is really paranoid, there's always netfilter. Ciao Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-xine 0.9.3 audio problems [RESOLVED]
Hi After literally a year or more, I've finally found the one thing that was causing my problems with this. Problem: Any version of vdr-xine above 0.8.0 (and associated xine-lib and xine-ui from Reinhard's website) caused audio and video skips a few minutes into watching a recording. This was indicated by multiple "fixing sound card drift by pts" messages in the xine console coinciding with the video "catching up" Fix: (too easy, as these things often turn out to be!!!) modify ~/.xine.config from: audio.synchronization.av_sync_method:0 audio.synchronization.resample_mode:0 to: audio.synchronization.av_sync_method:resample audio.synchronization.resample_mode:on HOORAY!!! I'm finally able to move off a 2007 plugin! Next problem - I can't get vdpau to work. But I'll start another thread for that. Regards Simon - Original Message - From: "Reinhard Nissl" To: "VDR Mailing List" Sent: Monday, October 05, 2009 10:29 AM Subject: Re: [vdr] vdr-xine 0.9.3 audio problems Hi, Simon Baxter schrieb: #engine.buffers.video_num_buffers is left at the default of 500. If I set this any higher, fast forwarding or rewinding causes the video to jump about 90 seconds. VDR-1.7.x should address this. 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] vdr-xine - skipping audio & video [RESOLVED]
Hi After literally a year or more, I've finally found the one thing that was causing my problems with this. Problem: Any version of vdr-xine above 0.8.0 (and associated xine-lib and xine-ui from Reinhard's website) caused audio and video skips a few minutes into watching a recording. This was indicated by multiple "fixing sound card drift by pts" messages in the xine console coinciding with the video "catching up" Fix: (too easy, as these things often turn out to be!!!) modify ~/.xine.config from: audio.synchronization.av_sync_method:0 audio.synchronization.resample_mode:0 to: audio.synchronization.av_sync_method:resample audio.synchronization.resample_mode:on HOORAY!!! I'm finally able to move off a 2007 plugin! Next problem - I can't get vdpau to work. But I'll start another thread for that. Regards Simon - Original Message - From: "Simon Baxter" To: "VDR Mailing List" Sent: Sunday, October 18, 2009 9:57 PM Subject: [vdr] vdr-xine - skipping audio & video Hi - am at my wits end!!! I've now tried vdr-xine-0.9.3 with XV and with VDPAU, and several settings in .xine/config for engine.buffers.audio_num_buffers (2300) and engine.buffers.video_num_frames (60) but I still get skips in audio and video when viewing recorded programs - which I don't get in vdr-xine-0.8.0. The skips occur at the same time as VDR console messages "buffering xx frames", and start out OK when watching the program but within a few minutes deteriorate further and further. I've been trying to upgrade from 0.8.0 since 2007 now - but it's the only version which works flawlessly for me. My production box has: vdr-1.6.0 fedora 10 with latest kernel fluxbox and X window manager latest standard v4l-dvb drivers plugins: vdr-xine-0.8.0, iptv, epgsearch, skinenigmang, femon, radio, recstatus, pvrinput. xine started with : xine --no-splash -Bfpqg --hide-gui -r anamorphic -V xv -Dtvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=1 --post vdr_video --post vdr_audio vdr://tmp/vdr-xine/stream#demux:mpeg_pes I've tested the following vdr-1.7.9 with the s2-liplianin drivers vdr-1.7.9 with the standard latest v4l-dvb drivers vdr-xine various versions from 0.8.1 right up to 0.9.3 xine-lib-1.2 with VDPAU and with XV output started by either: xine --no-splash -Bfpqg --hide-gui -r anamorphic -V vdpau -Dtvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=1 --post vdr_video --post vdr_audio vdr://tmp/vdr-xine/stream#dex:mpeg_pes OR xine --no-splash -Bfpqg --hide-gui -r anamorphic -V xv -Dtvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=1 --post vdr_video --post vdr_audio vdr://tmp/vdr-xine/stream#demux:mpeg_pes Can someone share their experiences with VDPAU and vdr-xine, or offer any suggestions??? Thanks Simon ___ 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] [Patch] Allow to limit SVDRP port to given IP
Hello, > How about this: if svdrphosts.conf contains only one single IP number, > then > open the port for only that IP number. Otherwise i needs to be opened > generally, > anyway. You are absolutely right! So if svdrphosts.conf only contains "127.0.0.1" (which is the default), then the port would be opened locally, only. I'll try to find an easy way to add this and post a new patch as soon as possible. CU Manuel -- () ascii ribbon campaign - against html mail /\- gegen HTML-Mail answers as html mail will be deleted automatically! Antworten als HTML-Mail werden automatisch gelöscht! GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine vdpau not working?
En/na Simon Baxter ha escrit: ANY IDEAS?? I'm using xine-lib-1.2 and patching with xine-lib-1.2-vdpau-r286.diff which was configured with: ./autogen.sh --with-vdpau --enable-debug --disable-optimizations --with-mpc=no Did it actually find vdpau headers? You can check config.log for it. Bye -- Luca ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine vdpau not working?
Am Sat, 9 Jan 2010 12:25:51 +1300 schrieb "Simon Baxter" : > ls -l /usr/local/lib/libxine* > Any ideas?? What am I doing wrong? Good chance that you have built against another libxine that is in /usr/lib. Use --prefix=/usr with autogen, so that the new libxine replaces the old one, or use our ppa: https://launchpad.net/~the-vdr-team/+archive/vdr-ubuntu-karmic Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine vdpau not working?
On Sat, Jan 9, 2010 at 1:25 AM, Simon Baxter wrote: > I'm using xine-lib-1.2 and patching with xine-lib-1.2-vdpau-r286.diff which There is no need to do such thing, since there already exists a repository which contains vdpau: xine-lib/xine-lib-1.2-vdpau You can use it as follows: hg clone http://hg.debian.org/hg/xine-lib/xine-lib-1.2-vdpau Otherwise, just pay attention to the messages you get when configuring/compiling xine-lib. -Petri ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine vdpau not working?
On Sat, Jan 9, 2010 at 1:25 AM, Simon Baxter wrote: I'm using xine-lib-1.2 and patching with xine-lib-1.2-vdpau-r286.diff which There is no need to do such thing, since there already exists a repository which contains vdpau: xine-lib/xine-lib-1.2-vdpau You can use it as follows: hg clone http://hg.debian.org/hg/xine-lib/xine-lib-1.2-vdpau Otherwise, just pay attention to the messages you get when configuring/compiling xine-lib. -Petri OK, so I installed the headers and everything compiles and looks OK. But when I try and run xine get: #grep vdpau* xine_log load_plugins: plugin vdpau_mpeg12 failed to instantiate itself. load_plugins: plugin /usr/local/lib/xine/plugins/2.0/xineplug_decode_vdpau_mpeg12.so found load_plugins: plugin /usr/local/lib/xine/plugins/2.0/xineplug_decode_vdpau_vc1.so found load_plugins: plugin /usr/local/lib/xine/plugins/2.0/xineplug_decode_vdpau_h264.so found load_plugins: plugin /usr/local/lib/xine/plugins/2.0/xineplug_vo_out_vdpau.so found main: probing video output plugin vo_vdpau: Can't create vdp device : No vdpau implementation. load_plugins: plugin vdpau_mpeg12 failed to instantiate itself. main: video driver failed Any ideas? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine vdpau not working?
SB said: OK, so I installed the headers and everything compiles and looks OK. But main: probing video output plugin vo_vdpau: Can't create vdp device : No vdpau implementation. load_plugins: plugin vdpau_mpeg12 failed to instantiate itself. main: video driver failed I've moved to my production box and vdpau works there - looks like my development box video card won't support. So xine-1.6.0, vdr-xine-0.9.3 and vdpau works - which is a move forward. But VDR doesn't work as well as under xv. It's slower changing channels and watching (SD) recordings freezes things for a few seconds. Also, the quality is actually worse - during "action scenes" objects seem to be a bit jerky and have "lines" momentarily. Only advantage, under vdpau the cpu sits at about 40%, where under xv it sits 50-70%. Any thoughts? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine vdpau not working?
On Saturday 09 January 2010 03:58:49 Simon Baxter wrote: > But VDR doesn't work as well as under xv. It's slower changing channels > and watching (SD) recordings freezes things for a few seconds. Also, the > quality is actually worse - during "action scenes" objects seem to be a > bit jerky and have "lines" momentarily. Only advantage, under vdpau the > cpu sits at about 40%, where under xv it sits 50-70%. > > Any thoughts? I had the same kind of issues you describe (bad frame rate, high cpu load, tearing, picture freezing for a long while etc) and only fix I found was to disable the composite extension in Xorg. You can do it simply by adding Section "Extensions" Option "Composite" "Disable" EndSection to xorg.conf. This will make it impossible to use the hud osd so expect some hideous scaling artifacts, but the cpu load stays well under 10% on a Sempron LE-1250 clocked at 1.8GHz and frame rates are smooth with no tearing. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
