[vdr] Re: Streamdev Client

[Chad Flynt <hoochster@sofnet.com>]

Thanks again, you are watching the ML like a hawk!  Ok, I tried with 
both server and client as plugins, and still get the same message on 
running it.  I am in process of putting xine on but was just testing to 
see it run first, that is the only reason I didn't have an output!  But 
I don't think that is the issue.  Wondering if the patched ver of 
streamdev I got is still broke for the client even though the site 
stated it was already prepatched for the client too.  So who knows!  I 
do appreciate the help, I will keep at it, was just seeing if there was 
something I was missing.  I have used the server for a long time now I 
stream transcoding over VLC so I can watch while out of town!  Works 
great.  Just wanted to delve a little deeper and see what I could do 
across my laptops with control capability!  I run a FF DVB also, but 
obviously this laptop won't have any DVB at all. 
Chad!

Gavin Hamill wrote:

> On Saturday 12 February 2005 00:24, Chad Flynt wrote:
>
>  
> > Thanks so much for your reply, so my next question is then, in order for
> > VDR to actually run it needs some sort of output device like the Xine
> > Plugin?  
> >    
> It needs one 'output device', yes.
>
>  
> > I was just starting with making sure VDR ran with the 
> > streamdev-client, since I knew there were some issues awhile back, so
> > that is ALL I have installed so far.  But have not put Xine on yet, will
> > do that next, if that is what you are thinking is the problem.  Is it
> > has nowhere to go so it fails to run.
> >    
> You can actually just install the streamdev-server as that's a valid output 
> device - of course you won't be able to get any pretty OSD aside from using 
> the text - console one (is this related to the 'skincurses' plugin, anyone? I 
> only use a real OSD with LIRC...), but it should at least satisfy VDR's 
> output-device requirement.. then point mplayer at 
> http://localhost:3000/channelnumber :)
>
> Personally I use a full DVB card and have not touched the software decoders 
> for many months, so any advice I could give would likely be woefully out of 
> date. Does the xine plugin still need its own tarball-compiled-from-source or 
> can it use a normal release version?
>
> Cheers,
> Gavin.
>
>
>
>