Re: [vdr] Turn off/relocate ts error logging
>From the auther of the atsc plugin:
Yes, that's from the plugin. To fix it, find the following line in VDR's
channels.c
Code:
dsyslog("changing pids of channel %d from %d+%d=%d:%s:%s:%d to
%d+%d=%d:%s:%s:%d", Number(), vpid, ppid, vtype, OldApidsBuf,
OldSpidsBuf, tpid, Vpid, Ppid, Vtype, NewApidsBuf, NewSpidsBuf, Tpid);
and change it to
Code:
if (Number())
dsyslog("changing pids of channel %d from %d+%d=%d:%s:%s:%d to
%d+%d=%d:%s:%s:%d", Number(), vpid, ppid, vtype, OldApidsBuf,
OldSpidsBuf, tpid, Vpid, Ppid, Vtype, NewApidsBuf, NewSpidsBuf, Tpid);
- Original Message -
From: "Klaus Schmidinger"
To:
Sent: Sunday, August 23, 2009 1:26 PM
Subject: Re: [vdr] Turn off/relocate ts error logging
> On 23.08.2009 20:03, Timothy D. Lenz wrote:
> > Form /var/log/user.log:
> >
> > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (2)
> > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (6)
> > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (9)
> > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (11)
> > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (8)
>
> This doesn't come from VDR (any more), because it no longer uses
> cTS2PES.
>
> > But in looking at the log now with it having run a bit with good signal, I
> > find another log spam:
> >
> > Aug 23 10:44:18 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
> > Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0
> > Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 65+65=2:0;68=eng,72=eng:0:0
> > Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0
> > Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0
> > Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 65+65=2:0;68=spa,72=spa:0:0
> > Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 81+81=2:0;84=eng,88=eng:0:0
> > Aug 23 10:45:21 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0
> > Aug 23 10:45:42 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;50=eng:0:0
> > Aug 23 10:45:42 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 65+65=2:0;66=spa:0:0
> > Aug 23 10:46:03 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0
> > Aug 23 10:46:03 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0
> > Aug 23 10:46:24 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
> > Aug 23 10:46:24 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0
> > Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
> > Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 65+65=2:0;68=eng:0:0
> > Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0
> > Aug 23 10:47:06 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 17+17=2:0;20=eng:0:0
> > Aug 23 10:47:27 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
> > Aug 23 10:47:48 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
> > Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0
> > Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 65+65=2:0;68=eng,72=eng:0:0
> > Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0
> > Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0
> > Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 65+65=2:0;68=spa,72=spa:0:0
> > Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 81+81=2:0;84=eng,88=eng:0:0
> > Aug 23 10:48:51 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0
> > Aug 23 10:49:12 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;50=eng:0:0
> > Aug 23 10:49:12 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 65+65=2:0;66=spa:0:0
> > Aug 23 10:49:33 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0
> > Aug 23 10:49:33 LLLx64-32 vdr: [2230] changing pids of channel 0 from
> > 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0
> > Aug 23 10:49:54 LLLx64-32 vdr: [2230
Re: [vdr] No EIT for channel Yesterday
On Mon, 10 Aug 2009 00:52:55 +0100 Tony Houghton wrote: > In fact, it isn't just Yesterday, the entire Freeview network has no EPG > in VDR. I can tune to the channels though. The DVB-S EPG is present > though. I think what it's turned out to be was a problem in my channels.conf. There was a bug in the program I use to generate it, prepending a '1' to the guard interval denominator. It was also outputting "I0" whereas I noticed scan from dvb-apps outputs "I999". After changing those two things I've got my EPG back. Strange how the problem didn't prevent viewing as well as EPG harvesting. -- TH * http://www.realh.co.uk ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] LIVE: Missing streams for recordings
Dear list, I was amazed how easy a Linux VDR can be set up, using (in my case) Sidux (recent Debian sid packages). I installed several plugins, and especially LIVE is what we need to have remote access via LAN. There was no problem to use the online EPG in order to time recordings. Also, it is possible to watch current streams of any channel. But as it comes to finished recordings, we miss a button that would open vlc[plugin] and give the corresponding stream. Do we need extra settings/plugins? Sorry for being less detailed, but I have to describe our problem from memory. Extra question: Is there a way to use specific PAM-modules for login or, at least, create additional users (rather than giving away "admin" account to anybody)? Thanks Ralf. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] FullHD OSD problem
Hi, I am still using 1.6.0-2 and have patched it for FullHD OSD (http://www.vdrportal.de/board/thread.php?threadid=79647&threadview=0&hilight=&hilightuser=0&page=1 ). Frontend is xineliboutput-cvs (vdr-sxfe in other computer; tcp connection) and skinenigmang-0.1.0 is in use. Everything seems fine except that if I use antialiased fonts there is one problem that I have noticed only with epgsearch plugin "Schedule" view. The problem is that Schedule is not shown if the OSD should be really full. With short EPG info the schedule is shown. The problem seems to be in buffering as I get following message in / var/log/messages: Aug 25 18:04:35 server vdr: [7573] [xine..put] write_osd_command: socket buffer full, OSD send skipped (got 262142 ; need 302366 256k seems to be the limit. Is it the problem in vdr, xineliboutput, epgsearch or somewhere else? OK I understand that these versions were not designed for fullHD support but anyways it would be nice fix this. I can avoid problem by disabling anti-alias fonts or setting "Try 8bpp single area: no" from skinenigmang options. - Kimmo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdpau patches
On Tue, 25 Aug 2009 11:39:51 +0200 (CEST) "Gerald Dachs" wrote: > > I take it you are using them on xinelib 1.2, are you using xineliboutput > > 1.0.4 or cvs? > > I use 1.0.4, cvs has currently audio problems. I use CVS with only slight glitches (sometimes the picture is not deinterlaced properly) problems. But I must add, I only use it for PAL-TV with vdr-1.6.0-2. > > Gerald > > > ___ > 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] vdpau patches
> I take it you are using them on xinelib 1.2, are you using xineliboutput > 1.0.4 or cvs? I use 1.0.4, cvs has currently audio problems. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput vs xine-vdr plugin
On 25/08/2009, Torgeir Veimo wrote: > 2009/8/25 Magnus Hörlin : > > >> Why is that an advantage of xine-vdr? I toggle between xineliboutput and > >> xbmc. > > > > Yes, so do I. I guess he's starting the frontend from vdr instead of doing > > that separately. > > > Have never tried xineliboutput, only xine-vdr. > set local = none allow remote connections on xineliboutput, connect "remotely" via unix socket or network port to localhost, will allow vdr to continue when you close vdr-sxfe ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdpau patches
On Mon, 24 Aug 2009 18:48:21 +0200, Malte Schröder wrote: > On Mon, 24 Aug 2009 12:49:18 +0100 > scott wrote: > >> >> >> I was thinking of giving xine/vdpau/xineliboutput another try after >> failing earlier in the year. I came across these patches: >> >> http://www.nfvdr.net/bbs/thread-5856-1-1.html >> >> Is anyone using these? >> > > Looks like this: > http://vdrportal.de/board/thread.php?threadid=86804 > > And yes, I use the patches and they improved playback considerably. Oh, yes its just a translation, thanks. I take it you are using them on xinelib 1.2, are you using xineliboutput 1.0.4 or cvs? -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput vs xine-vdr plugin
2009/8/25 Magnus Hörlin : >> Why is that an advantage of xine-vdr? I toggle between xineliboutput and >> xbmc. > Yes, so do I. I guess he's starting the frontend from vdr instead of doing > that separately. Have never tried xineliboutput, only xine-vdr. -- -Tor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput vs xine-vdr plugin
> -Ursprungligt meddelande- > Från: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] För Gerald > Dachs > Skickat: den 25 augusti 2009 10:05 > Till: VDR Mailing List > Ämne: Re: [vdr] xineliboutput vs xine-vdr plugin > > > Am wondering if the xineliboutput is a tad better thant xine-vdr w/ > > xine patched for vdpau? > > > > I currently use the latter, with the advantage that I can stop xine in > > order to run xbmc and possibly toggle between them using a lirc hotkey > > setup, all the while vdr runs all the time in the background for > > eventual recordings, but it seems that xineliboutput might have some > > more advanced features wrt cropping etc? > > Why is that an advantage of xine-vdr? I toggle between xineliboutput and > xbmc. > > Gerald > > Yes, so do I. I guess he's starting the frontend from vdr instead of doing that separately. /Magnus H ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput vs xine-vdr plugin
> Am wondering if the xineliboutput is a tad better thant xine-vdr w/ > xine patched for vdpau? > > I currently use the latter, with the advantage that I can stop xine in > order to run xbmc and possibly toggle between them using a lirc hotkey > setup, all the while vdr runs all the time in the background for > eventual recordings, but it seems that xineliboutput might have some > more advanced features wrt cropping etc? Why is that an advantage of xine-vdr? I toggle between xineliboutput and xbmc. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] 1.7.9 patches
[vdr] 1.7.9 patches Thanks for the link Goga The extensions patch there applied clean to vdr 1.7.9 but then enabling SETUP = 1 and TTXTSUBS = 1 results in errors. Did somebody manage to have somehow vdr 1.7.9 with SETUP and TTXTSUBS working? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] 1.7.9 patches
Thanks for the link Goga The extensions patch there applied clean to vdr 1.7.9 but then enabling SETUP = 1 and TTXTSUBS = 1 results in errors. Did somebody manager to have somehow vdr 1.7.9 with SETUP and TTXTSUBS working? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
