Then surely it will not be an OSD pip any more but rather just a pip?
seems like osd is the bottle neck?
On 29/04/2008, Grégoire FAVRE <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 29, 2008 at 10:52 AM, Patrick Boettcher
> <[EMAIL PROTECTED]> wrote:
>
> With xine/softdevice, one should be able to do
On Tue, Apr 29, 2008 at 10:52 AM, Patrick Boettcher
<[EMAIL PROTECTED]> wrote:
With xine/softdevice, one should be able to do such things with very
few CPU usage, but that won't be
compatible to other output devices, kvdr for example was doing it
without any problem on my old [EMAIL PROTECTED]
An
Hi,
I'm using it with vdr-xineliboutput from e-tobi. (not the 0.0.9 I think,
but I'm not sure).
Except that this version uses one complete processor when running. Good
thing, I have a dual-core :).
Patrick.
On Tue, 29 Apr 2008, Theunis Potgieter wrote:
> What are the requirements of this plu
What are the requirements of this plugin?
Will it work with vdr-softdevice/vdr-xineliboutput/vdr-xine?
Or does it require a work around on their behalf to make it work properly?
Theunis
On 28/04/2008, Anssi Hannula <[EMAIL PROTECTED]> wrote:
> Andreas Regel wrote:
> > Hi,
> >
> > there is a
Andreas Regel wrote:
> Hi,
>
> there is a new version of the osdpip plugin available:
> http://home.arcor.de/andreas.regel/files/vdr-osdpip-0.0.9.tgz
Thanks.
BTW, the "Latest version available at" in README has not been changed
and points to the original site, that still has 0.0.8.
--
Anssi Ha
