Hello,
Steffen Barszus wrote:
> As already said. Start a second vdr instance , using streamdev server
> and client for the dvb devices, and xineliboutput as output, start the
> plugins you want for the client on that instance. and you are done.
OK - I'll try that on my next bigger sparetime slot
On Sun, 16 Jan 2011 16:27:47 +0100
Gero wrote:
> With my current setup I do have certain issues. But meanwhile I know
> how to handle most of them, which means, I don't have any pressure to
> change my setup.
>
As already said. Start a second vdr instance , using streamdev server
and client for t
Hello,
Gerald Dachs wrote:
> Sorry, but I think I don't ask you for too much, if I ask you to look
> into the sources of this addon yourself.
Ok - you could have mentioned that earlier.
I expected the solution in the blog article.
... but what stated Steffen: my expectations are wrong.
Obviousl
Am Sun, 16 Jan 2011 16:27:47 +0100
schrieb Gero :
> I beg your pardon second time!
>
> I don't use yavdr and I'm not willing to change my vdr to yavdr - so
> using your addon is no acceptable solution - no matter how good your
> addon might be! You know, that the reason for not using yavdr is
> u
Hello,
Gerald Dachs wrote:
> You should really look more carefully into it.
I beg your pardon!
I read that page for sure, but I can't state, that I understood much.
I did not find any hint, that could change any of my issues either.
May be that hint might be there, but then I did not understand
Am Sun, 16 Jan 2011 12:19:41 +0100
schrieb Gero :
> Hello,
>
> thank you for the link.
>
> Gerald Dachs wrote:
> > It is not really what you are looking for, ...
>
> Hm - may be I missed the real thing, but I did not find anything
> about installing 2 vdr instances on the same machine.
Maybe y
Al 16/01/11 12:09, En/na Gero ha escrit:
Currently when I forget to switch to a SD channel on the xineliboutput
frontend before stopping that frontend, the vdr is not operable for the FF-
user. There's no way to recover.
I had the same issue with vdr-xine and the dxr3 plugin.
Maybe the ff outp
Hello,
Steffen Barszus wrote:
> actually i think its wrong setup on your side. call it "wrong
> expectations".
That - of cause - may be true!
I'm quite new to client/server vdr. I tried lot of things and my current
installation is the only, I succeeded to get into play.
... and - after all - i
Hello,
thank you for the link.
Gerald Dachs wrote:
> It is not really what you are looking for, ...
Hm - may be I missed the real thing, but I did not find anything about
installing 2 vdr instances on the same machine.
When I install a second instance on my backend, I need to know, what happen
On Sun, 16 Jan 2011 12:09:34 +0100
Gero wrote:
> Hello,
>
> Udo Richter wrote:
> > Its probably a lot easier to solve this at the output side within
> > xineliboutput.
>
> So you change a possible issue into a 'NMP'-issue - not very smart.
> (NMP stands for "not my problem")
actually i thin
Hello,
Udo Richter wrote:
> Am 16.01.2011 05:35, schrieb Gero:
> > Currently I use a "backend"-vdr with budget-cards and an old fashioned
> > FF. My TV is plugged to the old FF and I watch HD through a
> > frontend-client with xineliboutput.
>
> You're using a very special situation here, as xine
Am Sun, 16 Jan 2011 10:44:16 +0100
schrieb Gero :
> > Its not to much overhead actually :)
>
> Well, I decide that, when I see the system load ...
>
> So - I'm curious and willing to test. Do you know a url occasionally
> of someone who already did it?
It is not really what you are looking for,
Am 16.01.2011 05:35, schrieb Gero:
> I read about the ongoing work at the OSD system.
> I have to confess, that I don't really miss a truecolor OSD, but what I miss
> is the possibility to configure the OSD for each output-device separately.
>
> Currently I use a "backend"-vdr with budget-cards a
Hello,
thank you for your support!
Steffen Barszus wrote:
> configure a second vdr instance (on the client or the server) ...
Hm - the client does not have a vdr-instance yet - and for so, the only thing
I can configure there, is the IP of the server and the frontend to use.
AFAIK all configura
On Sun, 16 Jan 2011 06:16:59 +0100
Gero wrote:
> Hello,
>
> VDR User wrote:
> > I don't know about any of that but I wonder if the new osd system
> > will be able to maintain widescreen HD resolution even when viewing
> > 4:3 SD channels. Or if it will behave as it currently does,
> > stretches
Hello,
VDR User wrote:
> I don't know about any of that but I wonder if the new osd system will
> be able to maintain widescreen HD resolution even when viewing 4:3 SD
> channels. Or if it will behave as it currently does,
> stretches/shrinks according to the channel/recording you're watching.
>
I don't know about any of that but I wonder if the new osd system will
be able to maintain widescreen HD resolution even when viewing 4:3 SD
channels. Or if it will behave as it currently does,
stretches/shrinks according to the channel/recording you're watching.
Preferrably it won't do that, or a
Hello,
I read about the ongoing work at the OSD system.
I have to confess, that I don't really miss a truecolor OSD, but what I miss
is the possibility to configure the OSD for each output-device separately.
Currently I use a "backend"-vdr with budget-cards and an old fashioned FF. My
TV is plu
18 matches
Mail list logo
