On 31 Jul, Sergei Haller wrote: > On Mon, 31 Jul 2006, Klaus Frahm (KF) wrote: > KF> you must not forget to unload first the old dvb modules [...] > > did all that. apparently, forgot dvb_core for some reason. *blush'n'hide* > sorry for noise on the list... I personally don't mind, maybe it is quite useful to remind from time to time these kind of traps for those who read the archives. > > Now more good news: > > The new driver is better in regard with locking (hope I use correct > terminology). > > with the v4l-dvb.stk3000p, VDR would never show a picture when started. > I had to switch a couple of times (quickly) between two channels from > different transponders after that, everything was fine. Unless I stopped > and started VDR again. > > With the new driver I get the picture immediately. > I am pretty certain that have had exactly the same problem as me, only I classified it that one needs to get a 2nd lock immediately after the first one to start the video flux. I am using VLC and either I had to push the stop/play buttons or as another work to use "tzap -x <Channel-name>" directly followed VLC. I believe this should also work with VDR (if you retry the old driver). The workaround with tzap is (or was) important when I wanted to program to record something. See my first answer in this thread for more details and links to other posts in the mailing list about this issue. As with you, the new driver solves this locking problem. Greetings, Klaus. _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
