[vdr] info file
Hello Would it be possible to somewhat generate nfo file automatically with each recording? I know vdrnfofs which do it on-the-fly and I imagine such file could be generated automatically (optionally) with each recording. It seems very easy, because such nfo contains only title and plot. The idea after it is that vdrnfofs doesn't allow editing of nfo, while such nfo generated automatically by VDR could be freely editable. And also it would be possible to download fanart etc to recording directory. I know VNSI and that it works well with XBMC (allows for quite good scraping) but I would prefer offline metadata. There are times when I work on VDR switching it off and then recordings are unavailable for XBMC. If hardware brokes - VDR even doesn't start complaining for lack of hardware. And I can't fine tune my nfo file when scraper do something ot fully or wrong. Maybe it's idea for new plugin? Marx ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Call for development: enhancing mplayer-plugin
Hi, Support for seeing the VDR osd over mplayer doesn't exist yet. Who could add this feature please? And what would be the price? (Perhaps this could help: https://urandom.ca/mebox/downloads/vf_overlay.txt) TIA for any proposals, -- Peter Tel.: +33/0 299 680 353 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] No data in 8 seconds, queuing no signal image
Hi, Sometimes, when starting VDR, I get this message: [input_vdr] No data in 8 seconds, queuing no signal image And no video. When switching channels of the same transponder, nothing happens. But switching to a channel of another transponder (channel 7), video comes back. How could I avoid this problem please, when VDR starts automatically to start a recording? Here some log messages: --8---cut here---start-8--- Feb 25 21:00:03 media vdr: [2916] [input_vdr] No data in 8 seconds, queuing no signal image Feb 26 15:14:17 media vdr: [0] [xine..put] cXinelibOsd::CanHandleAreas(): Device does not support ARGB Feb 26 15:14:18 media vdr: [0] switching to channel 1 Feb 26 15:14:18 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:18 media vdr: [11133] TS buffer on device 2 thread ended (pid=0, tid=11133) Feb 26 15:14:18 media vdr: [11132] buffer stats: 188 (0%) used Feb 26 15:14:18 media vdr: [11132] receiver on device 2 thread ended (pid=0, tid=11132) Feb 26 15:14:18 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:18 media vdr: [11145] receiver on device 2 thread started (pid=0, tid=11145, prio=high) Feb 26 15:14:18 media vdr: [11146] TS buffer on device 2 thread started (pid=0, tid=11146, prio=high) Feb 26 15:14:22 media vdr: [0] switching to channel 2 Feb 26 15:14:22 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:22 media vdr: [11146] TS buffer on device 2 thread ended (pid=0, tid=11146) Feb 26 15:14:22 media vdr: [11145] buffer stats: 0 (0%) used Feb 26 15:14:22 media vdr: [11145] receiver on device 2 thread ended (pid=0, tid=11145) Feb 26 15:14:22 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:22 media vdr: [11147] receiver on device 2 thread started (pid=0, tid=11147, prio=high) Feb 26 15:14:22 media vdr: [11148] TS buffer on device 2 thread started (pid=0, tid=11148, prio=high) Feb 26 15:14:27 media vdr: [0] switching to channel 3 Feb 26 15:14:27 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:27 media vdr: [11148] TS buffer on device 2 thread ended (pid=0, tid=11148) Feb 26 15:14:27 media vdr: [11147] buffer stats: 0 (0%) used Feb 26 15:14:27 media vdr: [11147] receiver on device 2 thread ended (pid=0, tid=11147) Feb 26 15:14:27 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:27 media vdr: [11149] receiver on device 2 thread started (pid=0, tid=11149, prio=high) Feb 26 15:14:27 media vdr: [11150] TS buffer on device 2 thread started (pid=0, tid=11150, prio=high) Feb 26 15:14:30 media vdr: [0] switching to channel 4 Feb 26 15:14:30 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:30 media vdr: [11150] TS buffer on device 2 thread ended (pid=0, tid=11150) Feb 26 15:14:30 media vdr: [11149] buffer stats: 188 (0%) used Feb 26 15:14:30 media vdr: [11149] receiver on device 2 thread ended (pid=0, tid=11149) Feb 26 15:14:30 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:30 media vdr: [11151] receiver on device 2 thread started (pid=0, tid=11151, prio=high) Feb 26 15:14:30 media vdr: [11152] TS buffer on device 2 thread started (pid=0, tid=11152, prio=high) Feb 26 15:14:32 media vdr: [0] switching to channel 5 Feb 26 15:14:32 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:32 media vdr: [11152] TS buffer on device 2 thread ended (pid=0, tid=11152) Feb 26 15:14:32 media vdr: [11151] buffer stats: 0 (0%) used Feb 26 15:14:32 media vdr: [11151] receiver on device 2 thread ended (pid=0, tid=11151) Feb 26 15:14:32 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:32 media vdr: [11153] receiver on device 2 thread started (pid=0, tid=11153, prio=high) Feb 26 15:14:32 media vdr: [11154] TS buffer on device 2 thread started (pid=0, tid=11154, prio=high) Feb 26 15:14:34 media vdr: [0] switching to channel 6 Feb 26 15:14:34 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:34 media vdr: [11154] TS buffer on device 2 thread ended (pid=0, tid=11154) Feb 26 15:14:34 media vdr: [11153] buffer stats: 0 (0%) used Feb 26 15:14:34 media vdr: [11153] receiver on device 2 thread ended (pid=0, tid=11153) Feb 26 15:14:34 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:34 media vdr: [11155] receiver on device 2 thread started (pid=0, tid=11155, prio=high) Feb 26 15:14:34 media vdr: [11156] TS buffer on device 2 thread started (pid=0, tid=11156, prio=high) Feb 26 15:14:37 media vdr: [0] switching to channel 7 Feb 26 15:14:37 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:38 media vdr: [11156] TS buffer on device 2 thread ended (pid=0,
Re: [vdr] Call for development: enhancing mplayer-plugin
Am 2013-02-27 11:56, schrieb Peter Münster: Hi, Support for seeing the VDR osd over mplayer doesn't exist yet. Who could add this feature please? And what would be the price? I think this is already work in progress: http://www.vdr-portal.de/board17-developer/board21-vdr-plugins/p1127401-play-git-up-to-date/?highlight=%5Bplay%5D#post1127401 Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for development: enhancing mplayer-plugin
On Wed, Feb 27, 2013 at 7:38 AM, Gerald Dachs v...@dachsweb.de wrote: Am 2013-02-27 11:56, schrieb Peter Münster: Hi, Support for seeing the VDR osd over mplayer doesn't exist yet. Who could add this feature please? And what would be the price? I think this is already work in progress: http://www.vdr-portal.de/board17-developer/board21-vdr-plugins/p1127401-play-git-up-to-date/?highlight=%5Bplay%5D#post1127401 That's an alternative to the mplayer plugin -- still very new and primitive. It would be much better to have this support added to the mplayer plugin which is already stable and more capable. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] No data in 8 seconds, queuing no signal image
Am 27.02.2013 16:23, schrieb Peter Münster: Hi, Sometimes, when starting VDR, I get this message: [input_vdr] No data in 8 seconds, queuing no signal image And no video. When switching channels of the same transponder, nothing happens. But switching to a channel of another transponder (channel 7), video comes back. How could I avoid this problem please, when VDR starts automatically to start a recording? I don't know if it works, but you can configure vdr to start with always the same channel (which you'll never use for a recording) so that it has to switch explicitly when starting the recording. Lars. Here some log messages: --8---cut here---start-8--- Feb 25 21:00:03 media vdr: [2916] [input_vdr] No data in 8 seconds, queuing no signal image Feb 26 15:14:17 media vdr: [0] [xine..put] cXinelibOsd::CanHandleAreas(): Device does not support ARGB Feb 26 15:14:18 media vdr: [0] switching to channel 1 Feb 26 15:14:18 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:18 media vdr: [11133] TS buffer on device 2 thread ended (pid=0, tid=11133) Feb 26 15:14:18 media vdr: [11132] buffer stats: 188 (0%) used Feb 26 15:14:18 media vdr: [11132] receiver on device 2 thread ended (pid=0, tid=11132) Feb 26 15:14:18 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:18 media vdr: [11145] receiver on device 2 thread started (pid=0, tid=11145, prio=high) Feb 26 15:14:18 media vdr: [11146] TS buffer on device 2 thread started (pid=0, tid=11146, prio=high) Feb 26 15:14:22 media vdr: [0] switching to channel 2 Feb 26 15:14:22 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:22 media vdr: [11146] TS buffer on device 2 thread ended (pid=0, tid=11146) Feb 26 15:14:22 media vdr: [11145] buffer stats: 0 (0%) used Feb 26 15:14:22 media vdr: [11145] receiver on device 2 thread ended (pid=0, tid=11145) Feb 26 15:14:22 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:22 media vdr: [11147] receiver on device 2 thread started (pid=0, tid=11147, prio=high) Feb 26 15:14:22 media vdr: [11148] TS buffer on device 2 thread started (pid=0, tid=11148, prio=high) Feb 26 15:14:27 media vdr: [0] switching to channel 3 Feb 26 15:14:27 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:27 media vdr: [11148] TS buffer on device 2 thread ended (pid=0, tid=11148) Feb 26 15:14:27 media vdr: [11147] buffer stats: 0 (0%) used Feb 26 15:14:27 media vdr: [11147] receiver on device 2 thread ended (pid=0, tid=11147) Feb 26 15:14:27 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:27 media vdr: [11149] receiver on device 2 thread started (pid=0, tid=11149, prio=high) Feb 26 15:14:27 media vdr: [11150] TS buffer on device 2 thread started (pid=0, tid=11150, prio=high) Feb 26 15:14:30 media vdr: [0] switching to channel 4 Feb 26 15:14:30 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:30 media vdr: [11150] TS buffer on device 2 thread ended (pid=0, tid=11150) Feb 26 15:14:30 media vdr: [11149] buffer stats: 188 (0%) used Feb 26 15:14:30 media vdr: [11149] receiver on device 2 thread ended (pid=0, tid=11149) Feb 26 15:14:30 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:30 media vdr: [11151] receiver on device 2 thread started (pid=0, tid=11151, prio=high) Feb 26 15:14:30 media vdr: [11152] TS buffer on device 2 thread started (pid=0, tid=11152, prio=high) Feb 26 15:14:32 media vdr: [0] switching to channel 5 Feb 26 15:14:32 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:32 media vdr: [11152] TS buffer on device 2 thread ended (pid=0, tid=11152) Feb 26 15:14:32 media vdr: [11151] buffer stats: 0 (0%) used Feb 26 15:14:32 media vdr: [11151] receiver on device 2 thread ended (pid=0, tid=11151) Feb 26 15:14:32 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:32 media vdr: [11153] receiver on device 2 thread started (pid=0, tid=11153, prio=high) Feb 26 15:14:32 media vdr: [11154] TS buffer on device 2 thread started (pid=0, tid=11154, prio=high) Feb 26 15:14:34 media vdr: [0] switching to channel 6 Feb 26 15:14:34 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:34 media vdr: [11154] TS buffer on device 2 thread ended (pid=0, tid=11154) Feb 26 15:14:34 media vdr: [11153] buffer stats: 0 (0%) used Feb 26 15:14:34 media vdr: [11153] receiver on device 2 thread ended (pid=0, tid=11153) Feb 26 15:14:34 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:34 media vdr: [11155] receiver on device 2 thread started (pid=0, tid=11155,
Re: [vdr] No data in 8 seconds, queuing no signal image
Hi Peter, Did you change your VDR release ? Have you the same issue with SoftHDdevice ? Cheers, Bernard. 2013/2/27 Lars Hanisch d...@flensrocker.de Am 27.02.2013 16:23, schrieb Peter Münster: Hi, Sometimes, when starting VDR, I get this message: [input_vdr] No data in 8 seconds, queuing no signal image And no video. When switching channels of the same transponder, nothing happens. But switching to a channel of another transponder (channel 7), video comes back. How could I avoid this problem please, when VDR starts automatically to start a recording? I don't know if it works, but you can configure vdr to start with always the same channel (which you'll never use for a recording) so that it has to switch explicitly when starting the recording. Lars. Here some log messages: --8---cut here---start-8--- Feb 25 21:00:03 media vdr: [2916] [input_vdr] No data in 8 seconds, queuing no signal image Feb 26 15:14:17 media vdr: [0] [xine..put] cXinelibOsd::CanHandleAreas(): Device does not support ARGB Feb 26 15:14:18 media vdr: [0] switching to channel 1 Feb 26 15:14:18 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:18 media vdr: [11133] TS buffer on device 2 thread ended (pid=0, tid=11133) Feb 26 15:14:18 media vdr: [11132] buffer stats: 188 (0%) used Feb 26 15:14:18 media vdr: [11132] receiver on device 2 thread ended (pid=0, tid=11132) Feb 26 15:14:18 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:18 media vdr: [11145] receiver on device 2 thread started (pid=0, tid=11145, prio=high) Feb 26 15:14:18 media vdr: [11146] TS buffer on device 2 thread started (pid=0, tid=11146, prio=high) Feb 26 15:14:22 media vdr: [0] switching to channel 2 Feb 26 15:14:22 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:22 media vdr: [11146] TS buffer on device 2 thread ended (pid=0, tid=11146) Feb 26 15:14:22 media vdr: [11145] buffer stats: 0 (0%) used Feb 26 15:14:22 media vdr: [11145] receiver on device 2 thread ended (pid=0, tid=11145) Feb 26 15:14:22 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:22 media vdr: [11147] receiver on device 2 thread started (pid=0, tid=11147, prio=high) Feb 26 15:14:22 media vdr: [11148] TS buffer on device 2 thread started (pid=0, tid=11148, prio=high) Feb 26 15:14:27 media vdr: [0] switching to channel 3 Feb 26 15:14:27 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:27 media vdr: [11148] TS buffer on device 2 thread ended (pid=0, tid=11148) Feb 26 15:14:27 media vdr: [11147] buffer stats: 0 (0%) used Feb 26 15:14:27 media vdr: [11147] receiver on device 2 thread ended (pid=0, tid=11147) Feb 26 15:14:27 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:27 media vdr: [11149] receiver on device 2 thread started (pid=0, tid=11149, prio=high) Feb 26 15:14:27 media vdr: [11150] TS buffer on device 2 thread started (pid=0, tid=11150, prio=high) Feb 26 15:14:30 media vdr: [0] switching to channel 4 Feb 26 15:14:30 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:30 media vdr: [11150] TS buffer on device 2 thread ended (pid=0, tid=11150) Feb 26 15:14:30 media vdr: [11149] buffer stats: 188 (0%) used Feb 26 15:14:30 media vdr: [11149] receiver on device 2 thread ended (pid=0, tid=11149) Feb 26 15:14:30 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:30 media vdr: [11151] receiver on device 2 thread started (pid=0, tid=11151, prio=high) Feb 26 15:14:30 media vdr: [11152] TS buffer on device 2 thread started (pid=0, tid=11152, prio=high) Feb 26 15:14:32 media vdr: [0] switching to channel 5 Feb 26 15:14:32 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:32 media vdr: [11152] TS buffer on device 2 thread ended (pid=0, tid=11152) Feb 26 15:14:32 media vdr: [11151] buffer stats: 0 (0%) used Feb 26 15:14:32 media vdr: [11151] receiver on device 2 thread ended (pid=0, tid=11151) Feb 26 15:14:32 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer Feb 26 15:14:32 media vdr: [11153] receiver on device 2 thread started (pid=0, tid=11153, prio=high) Feb 26 15:14:32 media vdr: [11154] TS buffer on device 2 thread started (pid=0, tid=11154, prio=high) Feb 26 15:14:34 media vdr: [0] switching to channel 6 Feb 26 15:14:34 media vdr: [0] [input_vdr] vdr_flush_engine: playback is paused 0 Feb 26 15:14:34 media vdr: [11154] TS buffer on device 2 thread ended (pid=0, tid=11154) Feb 26 15:14:34 media vdr: [11153] buffer stats: 0 (0%) used Feb 26 15:14:34 media vdr: [11153] receiver on device 2 thread ended
Re: [vdr] Call for development: enhancing mplayer-plugin
Am 27.02.2013 11:56, schrieb Peter Münster: Support for seeing the VDR osd over mplayer doesn't exist yet. Who could add this feature please? And what would be the price? Basically, the OSD-over-mplayer does work for dvbsddevice and other devices that mplayer supports. Also, there was already an attempt to get mplayer plugin working for TT6400/dvbhddevice cards, but it got stuck a long time ago: http://www.vdr-portal.de/board16-video-disk-recorder/board55-vdr-plugins/105796-mplayer-und-tt-6400/?s=2f9ffc972e8fbfd8b390e5dfb1a6abe95cf80963 One thing the thread has is a generic solution for the need to mix OSD and video stream: There's a modified version of mplayer plugin that moves this part where it belongs, back into VDR. Instead of VDR closing the video device for mplayer while keeping the OSD open, VDR takes over a stream from mplayer and forwards it to the proper output device, whichever that is. Problem however is that the old stream output feature of mplayer is suffering from bit rot, and isn't working very well. Plus, the TT6400 didn't like the mplayer encoded stream. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for development: enhancing mplayer-plugin
On Wed, Feb 27, 2013 at 12:01 PM, Udo Richter udo_rich...@gmx.de wrote: Am 27.02.2013 11:56, schrieb Peter Münster: Support for seeing the VDR osd over mplayer doesn't exist yet. Who could add this feature please? And what would be the price? Basically, the OSD-over-mplayer does work for dvbsddevice and other devices that mplayer supports. Also, there was already an attempt to get mplayer plugin working for TT6400/dvbhddevice cards, but it got stuck a long time ago: http://www.vdr-portal.de/board16-video-disk-recorder/board55-vdr-plugins/105796-mplayer-und-tt-6400/?s=2f9ffc972e8fbfd8b390e5dfb1a6abe95cf80963 One thing the thread has is a generic solution for the need to mix OSD and video stream: There's a modified version of mplayer plugin that moves this part where it belongs, back into VDR. Instead of VDR closing the video device for mplayer while keeping the OSD open, VDR takes over a stream from mplayer and forwards it to the proper output device, whichever that is. Problem however is that the old stream output feature of mplayer is suffering from bit rot, and isn't working very well. Plus, the TT6400 didn't like the mplayer encoded stream. Is there any hope that this could be resurrected? Also, what about those of us who use VDPAU? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for development: enhancing mplayer-plugin
Am 27.02.13 11:56, schrieb Peter Münster: Support for seeing the VDR osd over mplayer doesn't exist yet. I use xineliboutput with a nvidia on-board graphic card to replay all kind of video without problems (SD and HD). Matthias -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning. -- Rich Cook ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] No data in 8 seconds, queuing no signal image
On Wed, Feb 27 2013, Lars Hanisch wrote: I don't know if it works, but you can configure vdr to start with always the same channel (which you'll never use for a recording) so that it has to switch explicitly when starting the recording. Yes, that should work. That's what I'll do, if there is no other solution. -- Peter ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for development: enhancing mplayer-plugin
On Wed, Feb 27 2013, Matthias Fechner wrote: Am 27.02.13 11:56, schrieb Peter Münster: Support for seeing the VDR osd over mplayer doesn't exist yet. I use xineliboutput with a nvidia on-board graphic card to replay all kind of video without problems (SD and HD). I use xineliboutput too, but it crashes too often. See also http://article.gmane.org/gmane.linux.vdr/47161 -- Peter ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] No data in 8 seconds, queuing no signal image
On Wed, Feb 27 2013, Bernard Jaulin wrote: Did you change your VDR release ? Yes. Now it's 1.7.37 and before it was 1.2.6 (several years ago... ;) Have you the same issue with SoftHDdevice ? I don't use this plugin, so I don't know. -- Peter ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for development: enhancing mplayer-plugin
Am 27.02.2013 22:16, schrieb VDR User: Is there any hope that this could be resurrected? Also, what about those of us who use VDPAU? Its more a thing for hardware decoder cards that cannot handle an uncompressed video stream, as it always re-encodes to some fixed output format, eg. mpeg1/2. The mplayer plugin modification should be ressurectable, with some updates to plugin structure. It basically expects a video stream that can be handled by the output device delivered via unix pipe. However, the mplayer playback-recode-to-file feature is quite broken, and currently needs some ugly workarounds. And of course, its still uncertain why the TT6400 denies playback of mplayer encoded video. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for development: enhancing mplayer-plugin
Am 27.02.13 23:01, schrieb Peter Münster: I use xineliboutput too, but it crashes too often. See also http://article.gmane.org/gmane.linux.vdr/47161 I used gentoo without problems and now yavdr without problems. It never crashed so it is related to the version/distribution or to your hardware you are using. Gruß, Matthias -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning. -- Rich Cook ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
