Re: [vdr] PANIC: watchdog timer expired - exiting
PLU Dominique wrote: > Is there a way to force vdr to first update system time to transponder time > as design and after look if something is really scheduled ? You could use a tool like dvbdate to update the clock before starting VDR. If you have a permanent Internet connection, or at least some local LAN server with a better clock, you can use NTP to synchronize the clock. Another idea is to use some tool to correct constant clock drift. This should get your clock quite well, if the clock drift is constant, like 5 minutes per day. (The ntpd time server has a built-in drift correction, but of course requires another exact time source) Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PANIC: watchdog timer expired - exiting
On 06/05/07 19:47, PLU Dominique wrote: > Hi > > By the way, I have another question about clock and vdr, I have put vdr > setting to synchronise time with a specific channel and setup vdr to start on > this channel. > Unfortunately , when vdr start, the system is never on time, at least there > is > two hours minus Are you sure you have set the correct time zone? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Thunderstorm over Munich
[EMAIL PROTECTED](Stefan Taferner) 28.05.07 14:22 Once upon a time "Stefan Taferner " shaped the electrons to say... >On Monday 28 May 2007 10:38:50 Marko Myllymaa wrote: >> On Sun, 27 May 2007, Andrew Herron wrote: >>> I have to say that I agree with both of you... constructive >>> criticism is best! >>> >>> As a quiet 'user' of vdr, for about a year, I agree with the >>> sentiments in Martin's post. It is very frustrating that vdr exits >>> when reception is less than perfect. I personally would prefer it >>> if vdr announced on screen that there was a bad signal condition. >>> This is particularly frustrating if at the time you are just >>> watching a perfectly good recording. >> >> I agree, with all. I would suggest to handle viewing recording or >> running a plugin (dvd plugin or mp3/mplayer etc.) would get a >> priority, for example 90. Then every recording that has lower >> priority would not cause emergency exits, no matter what. But if >> recording has higher priority, it can cause restarts. >Hmm... IMO it is good that vdr tries to fix the recording problem with >a restart. I think that's "historical" When VDR (and me?) were young, there were tons of problems with the driver, with firmware, with multithreading, reentrance and real hardware bugs etc. (remember: the drivers are mostly based on reverse engineerings! And the early baords tent to "hang" causd by bad Vcc filtering and desgin errors.) At that time it was the only way to reload the driver by resetting the entire box, because it was impossible to determine where the problem actually was. Today i would ask: Why can't VDR read out the signal (strength/quality) information? As long as there is a bit level, there is no reason to reboot, tho no video stream might be decodable. >If I have the choice between a corrupted recording and >being interrupted by a restart, I would choose the restart. The recording is corrupt anyway. And if you have more than one card, and record more than one transponder at the same time both(!) recordings will be broken tho only one transponders had problems... Not really an option, or? At least me would prefere to have only 1 broken recording instead of 4...i would not choose to restart. We had this thread all 12/18 month the last 5 years ;-) (Thunder storms in summer and snow in winter) Rainer ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PANIC: watchdog timer expired - exiting
Hi Currently, no, the TZ is set to GMT , the solution is to change it but it will not resolve entierly the problem, when I shutdown the system, the clock of another computer miss many days or year, meaning bios battery is dead and as long this battery is not standard (std=cr2032 or equiv) I cannot change it I was just hoping that the system could first synchronize the system time to transponder inside the init phase and after start operation like schedule. Maybe in future release ? By the way, I will follow the recommandation of Udo Richter and going to ntp solution if I can adapt to my slack/vdrlive system Thanks for your help and time Le mercredi 6 juin 2007 19:04, Klaus Schmidinger a écrit : > On 06/05/07 19:47, PLU Dominique wrote: > > Hi > > > > By the way, I have another question about clock and vdr, I have put vdr > > setting to synchronise time with a specific channel and setup vdr to > > start on this channel. > > Unfortunately , when vdr start, the system is never on time, at least > > there is two hours minus > > Are you sure you have set the correct time zone? > > 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] setting tv standard in /dev/video0
Hi,
I am currently using VDR with a Nexus-S FF card in an NTSC environment. For
a long time, I could never get the correct tv standard (NTSC) while trying
to watch television via VDRAdmin. I recently noticed that once I stream VDR
using VLC and its v4l interface, something in /dev/video0 gets set to NTSC,
because from then on, the video is correctly set to NTSC mode and I can
watch television via the VDRAdmin television interface. Here is the VLC
command I'm using:
vlc -vvv v4l:/dev/video0:adev=/dev/dsp:audio=1:norm=ntsc:size=352x240 --sout
'#transcode{vcodec=DIV3,vb=64,acodec=mp3,ab=48,deinterlace}:std{access=http,mux=asf,dst=:6789}'
Notice how VLC is directly interacting with the video from /dev/video0 (this
method only works with FF cards). Somehow, the v4l interface from VLC is
setting the tv standard properly for /dev/video0 and fixing VDRAdmin for
NTSC. Anyone have an idea whats going on? The firmware is set to NTSC as
soon as the card tunes to a NTSC channel. Why would /dev/video0 not be set
to NTSC until I stream it with VLC?
Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] setting tv standard in /dev/video0
Stone wrote: > Hi, > > I am currently using VDR with a Nexus-S FF card in an NTSC environment. For > a long time, I could never get the correct tv standard (NTSC) while trying > to watch television via VDRAdmin. I recently noticed that once I stream VDR > using VLC and its v4l interface, something in /dev/video0 gets set to NTSC, > because from then on, the video is correctly set to NTSC mode and I can > watch television via the VDRAdmin television interface. Basically there are two ways to select NTSC mode: - v4lctl setnorm NTSC - module parameter 'tv_standard' for dvb-ttpci modinfo dvb-ttpci: ... parmtype: tv_standard:int parm: tv_standard:TV standard: 0 PAL (default), 1 NTSC ... Oliver -- VDR Remote Plugin 0.3.9: http://www.escape-edv.de/endriss/vdr/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] setting tv standard in /dev/video0
On 6/7/07, Oliver Endriss <[EMAIL PROTECTED]> wrote: Stone wrote: > Hi, > > I am currently using VDR with a Nexus-S FF card in an NTSC environment. For > a long time, I could never get the correct tv standard (NTSC) while trying > to watch television via VDRAdmin. I recently noticed that once I stream VDR > using VLC and its v4l interface, something in /dev/video0 gets set to NTSC, > because from then on, the video is correctly set to NTSC mode and I can > watch television via the VDRAdmin television interface. Basically there are two ways to select NTSC mode: - v4lctl setnorm NTSC - module parameter 'tv_standard' for dvb-ttpci modinfo dvb-ttpci: ... parmtype: tv_standard:int parm: tv_standard:TV standard: 0 PAL (default), 1 NTSC Yes, I use the tv_standard option when modprobing the drivers as follows: alias /dev/dvb/* /dev/dvb alias char-major-212-* dvb-ttpci options dvb-core dvb_shutdown_timeout=0 options dvb-ttpci tv_standard=1 But, this seems to make no difference when VDRAdmin tells VDR to "grab" the picture. Basically VDRAdmin uses VDR's SVDRP interface to "grab" a frame and send it over http. Prior to streaming VDR with VLC, VDR's grab still gets the frames in PAL mode for some reason. VLC's v4l module is doing something in addition to switching the driver in NTSC mode with modprobe options. Also, this is only a problem with FF ttpci cards. Best Regards. R ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] setting tv standard in /dev/video0
But, this seems to make no difference when VDRAdmin tells VDR to "grab" the picture. To summarize, when I stream /dev/video0 with VLC, it seems like VLC's v4l module is setting the resolution in the driver to something other than PAL because now for the first time ever, I can use VDR's grab command with a FF card, in NTSC mode, and not have the picture look like the horizontal is all offset. The image does not have horizontal lines in it now. This has always been a problem with FF cards, NTSC, and VDR's grab command. Best Regards. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR timer + mplayer = VDR crash. Please fix!
If a timer is triggered while the mplayer plugin is in use, VDR crashes. This has happened to me about a zillion times now and I'm hoping somebody will fix this! You can use the mplayer plugin after a timer is started no problem. Correct me if I'm wrong but mplayer should never have to take control of the tuner in the first place since it's not required to play a media file. Free booze to anyone who can fix this incredibly annoying problem once and for all!! Thanks. :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR timer + mplayer = VDR crash. Please fix!
VDR User wrote: > If a timer is triggered while the mplayer plugin is in use, VDR > crashes. This has happened to me about a zillion times now and I'm > hoping somebody will fix this! You can use the mplayer plugin after a > timer is started no problem. Correct me if I'm wrong but mplayer > should never have to take control of the tuner in the first place > since it's not required to play a media file. > > Free booze to anyone who can fix this incredibly annoying problem once > and for all!! This could be related to the fact that when mplayer-plugin forks mplayer from vdr, the /dev/dvb/adapter* file descriptors are copied as well and are not closed. -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR timer + mplayer = VDR crash. Please fix!
On 6/6/07, Anssi Hannula <[EMAIL PROTECTED]> wrote: > VDR User wrote: > > If a timer is triggered while the mplayer plugin is in use, VDR > > crashes. This has happened to me about a zillion times now and I'm > > hoping somebody will fix this! You can use the mplayer plugin after a > > timer is started no problem. Correct me if I'm wrong but mplayer > > should never have to take control of the tuner in the first place > > since it's not required to play a media file. > > > > Free booze to anyone who can fix this incredibly annoying problem once > > and for all!! > > This could be related to the fact that when mplayer-plugin forks mplayer > from vdr, the /dev/dvb/adapter* file descriptors are copied as well and > are not closed. Thanks for such a quick reply Anssi! Is that an easy thing to fix? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
