Re: [vdr] VDR 1.7.28, xineliboutput 1.0.7: Using local frontend gives `No protocol specified`
On ti, 2012-06-12 at 11:31 +0200, Paul Menzel wrote: Dear VDR folks, somehow I am not able to get the local frontend to work. Debian Sid/unstable is installed with $ dpkg -l vdr vdr-plugin-xineliboutput libxineliboutput-sxfe […] ii libxineliboutput-sxfe 1.0.7+cvs20120609.1902-1 Local X-Server frontend for the xineliboutput plugin ii vdr 1.7.28-1 Video Disk Recorder for DVB cards ii vdr-plugin-xineliboutput 1.0.7+cvs20120609.1902-1 VDR plugin for Xine based sofdevice frontends and I try to get the local frontend working but it fails. $ sudo -u vdr vdr -Pxineliboutput --local=sxfe --video=auto --audio=alsa --remote=none No protocol specified No protocol specified No protocol specified Maybe it has no rights to open X window. Do you see any errors in log ? Do you start it from X terminal ? Some things to try: - run xhost +si:localuser:vdr or xhost + before starting vdr (note that this opens a security hole) - try starting without su (as current user, or with vdr option --user=vdr) Unfortunately I do not know what the problem is as this is the command mentioned in `README` of `xineliboutput`. Usage examples (VDR plugin) If no arguments are given, both X11 and framebuffer frontends are tried. First working frontend is used with best available video driver. Complete list of available command-line arguments can be obtained with vdr --help. Only local frontend, X11/Xv video, alsa audio: vdr -Pxineliboutput --local=sxfe --video=xv --audio=alsa --remote=none Thanks, Paul ___ 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] [solved] VDR 1.7.28, xineliboutput 1.0.7: Using local frontend gives `No protocol specified`
Am Freitag, den 15.06.2012, 12:47 +0300 schrieb Petri Hintukainen: On ti, 2012-06-12 at 11:31 +0200, Paul Menzel wrote: somehow I am not able to get the local frontend to work. Debian Sid/unstable is installed with $ dpkg -l vdr vdr-plugin-xineliboutput libxineliboutput-sxfe […] ii libxineliboutput-sxfe 1.0.7+cvs20120609.1902-1 Local X-Server frontend for the xineliboutput plugin ii vdr 1.7.28-1 Video Disk Recorder for DVB cards ii vdr-plugin-xineliboutput 1.0.7+cvs20120609.1902-1 VDR plugin for Xine based sofdevice frontends and I try to get the local frontend working but it fails. $ sudo -u vdr vdr -Pxineliboutput --local=sxfe --video=auto --audio=alsa --remote=none No protocol specified No protocol specified No protocol specified Maybe it has no rights to open X window. Do you see any errors in log ? I did not see any errors printed to the terminal. What log file should I have looked at? Do you start it from X terminal ? Yes. I used GNOME Terminal with GNOME 3 running. Some things to try: - run xhost +si:localuser:vdr or xhost + before starting vdr (note that this opens a security hole) That indeed helped. Both commands work and knowing the solution it of course is the vdr user forbidden to put windows on the X session of a different user. - try starting without su (as current user, or with vdr option --user=vdr) I had tried that before and the problem is that the video directory is owned by the vdr user and it looks like starting `vdr` from a normal user and passing `--user=vdr` cannot change the user. That is why I tried it with `sudo`. […] Thanks a million, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] How to make bug report
Hello I have four DVB cards: DVB-S2: -Pinnacle PCTV SAT HDTV 452E PRO USB (main kernel support) -Terratec Cinergy S2 USB HD v.2 -Prof Revolution DVB-S2 8000 PCIe DVB-T: -AF9015 noname USB (main kernel support) on AMD Brazos platform (Asrock E350M1) with Debian (lately with 3.4 kernel). While I could be able to make all of them working via different drivers (media-build, patches, vendor drivers, Igor Liplianin's repo, yavdr dkms package etc) none of this card works stable (unlike Twinhan PCI I had previously). Prof hangs system, Pinnacle doesn't work with DVB-S2, Terratec records streams partially unplayable, AF9015 stops working after and hour or so etc. Often I see errors of I2C subsystem. While I'm in process of testing it on different hardware (laptop) I would like to know if it's good place to write about dvb drivers bugs. Or maybe should I write directly to developer? or write bugs in Debian/kernel bugzilla or sth similair? How to properly report bugs? What kernel should I use, which driverset? What logs to attach (kernel.log)? how to enable debug options (if needed)? I think it's rather unusual all of cards doesn't work, so I suspect that there can be something wrong with my system. Maybe you, as skilled developers, can direct me what can be wrong, what can I test? Marx ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] RFE: Make VDR more friendly when using combinations of DVB-S, DVB-T and DVB-C
Hello, Some time ago, I started a discussion in german on the VDR forum about making the VDR more friendly for users that are simultaneously using different sources to receive channels: http://www.vdr-portal.de/board16-video-disk-recorder/board8-vdr-grundlagen/110156-%C3%BCberlegungen-zur-channels-conf-f%C3%BCr-dvb-c-s-t-mischbetrieb/index3.html I am going to explain the problem, when receiving channels from two different sources by using the second german public channel named ZDF: Suppose a user is receiving the channel ZDF by dvb-s and dvb-t. For the VDR, these are two different channels, and it probably is not a bad thing that the VDR differentiates between them because these channels might be of different quality (different data rates, etc.). However, as both sources name these channels often the same way, it is not easily possible to differentiate between the two channels in the VDR OSD, which is particularly annoying for the timers, one of the main VDR features. Currently, I work around this problem, by setting the VDR to not update channelnames and manually adding a suffix to the channelnames in the channels.conf. So, to use the example above and differentiate between the two channels, they could be renamed to ZDF-s and ZDF-t (or ZDF.s and ZDF.t, or...). In practice, I only only rename the channelnames of the source with the smallest number of channels; I know that the channelnames without suffix are those from the other source. @ Klaus Do you think that you could add an additional option to one of your next VDR releases, like Add suffix about source to channelnames; I could imagine such an option next to the Update channels option in the DVB section of the Setup in the OSD of the VDR. Since the information is already in the channels.conf for every channel, I assume, that it will not require huge changes to the VDR code to use channelnames-source (or something similar) instead of only the channelname in the channelname field of the channels.conf, when the corresponding option is active. In case, I am missing something, I would also like to ask everybody reading this to let us know, if for any reason, the idea about replacing the channelnames with channelname-source cannot work. There are of course also other solutions, like adding a system to the VDR allowing the user to indicate to the VDR, that both ZDF channels (to continue with the example above) are only variations of the same channel; the VDR could thus only show one of the two channels in his channellist (hd channels could also be seen as another variation of the channel); a priority system would be required to indicate what variation of the channel to use for recordings,... Restarting the discussion about how to best handle the simultaneous reception of more than one source is on my ToDo list since I started that thread in the german forum. Unfortunately, I did not have the time to do it until now, and probably will not have the time to do it seriously in the near future. Moreover, since I got the idea about simply adding the information about the source to the string of the channelname, I decided to ask for it, instead of waiting for something, that would probably require a long time to get designed and implemented. Cheers, Ludi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
