[vdr] Re: vdr 1.2.3 problems [Was: VDR 1.2.3 stops playback when a new timer is hit]

[Javier Marcet <lists@marcet.info>]

* Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de> [030819 20:16]:

> > I've updated my VDR to 1.2.3 (preview or rc at he moment, isn't it?),
> It was a pre-release, but it won't be released officially due to
> several problems.
The only other thing I have not liked is that of vdr quitting when
there's an error in a config file.
I have an autopid-patched version of vdr that I run from time to time to
check if there are new channels. I have a different init script for each
version, with their own plugin dir et all, but I didn't need to change
the setup.conf previously between the autopid-patched and non patched
versions. With this change, on the other hand, 'defaultCA' and
'updateServices' which are autopid-only settings, make the non patched
version quit.

Now that I think of it, disabling a plugin which uses its own settings
would yield the same error, hence, I guess it should be considered a
bug from any point of view. Do you agree?

> > I have a single FF DVB-s 1.3, and until vdr 1.2.2 when I was watching a
> > recording, nothing disturbed it, unless I implicitly stopped the
> > playback. With 1.2.3, however, if a new recording begins (a timer which
> > is started), the playback stops at the same time the channel change for
> > the new recording takes place.
[...]

> > I'll try vanilla if you deem it necessary, though.
> I guess this is a side effect of the change
> - Fixed freezing replay if a timer starts while in Transfer Mode from the device
>  used by the timer, and the timer needs a different transponder
> I'll take another look at this.
All right, thanks a lot :)))

--
Javier Marcet <javier@marcet.info>



--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.