----- Oorspronkelijk bericht -----
From: Rob Shortt <[EMAIL PROTECTED]>
To: [email protected]
Date: 07-Feb-2006 14:51
Subject: Re: [Freevo-devel] handling VIDEO_GROUPS

> Richard van Paasen wrote:
> > 
> >>TheHog wrote:
> >>>I'm rewriting a plugin for xine/ivtv/tv. Now I'm fighting with the video
> >>>groups config setting. With the method
> > 
> > "FreevoChannles.getVideoGroup(chan)" I
> > 
> >>>get the video group the selected channel belongs to. But what if my
> > 
> > plugin
> > 
> >>>cannot handle its group_type ? What should it do then?
> >>
> >>You would do something like:
> >>
> >>grp = freevochannels.getVideoGroup(chan)
> >>if grp.group_type not in [ 'tv', 'ivtv' ]:
> >>  log error
> >>  send popup to user
> >>  return
> >>
> > 
> > 
> > Hmm, sounds like I don't fully understand the concept Video Group. I
though
> > it was meant to seperate channels in groups such that one could have
(e.g.)
> > dvb channels in addition to (e.g.) regular cable channels. Both channels
are
> > provided by different devices and thus different drivers.
> 
> Right,
> 
> 
> > Now, my plugin starts xine with the ivtv driver and hardware MPEG
> > accelleration. Channel switching works, as long as the new channel is
part of
> > the ivtv group. But what if the user switches to a channel that belongs
to
> > another group? Preferably I'd hand over control to another plugin (or
back to
> > freevo). If I'd popup an error box then the particular channel group
isn't
> > needed at all.
> 
> I think there's an example in one of the TV plugins on how to do that,
> maybe one of the mplayer ones.  I used to have my setup doing this
> somewhat ok - I had 3 groups, one for my ivtv tuner input, one for
> composite (sat receiver input), and a webcam.  I could switch between
> them without problems.  One thing I didn't do though was to say one
> channel was provided by two groups for redundancy.  I think you'll need
> to dig a bit more and add some logic.
> 
> It's been so long since I've looked at the 1.5.x code, and we don't
> really care to since 2.0 is "close".  BTW Freevo 2.0 can / will be able
> to do what you're trying.
> 
> -Rob
> 


Well it's not that important to have this video-group switching working, I
just left it unimplemented. I have a smooth running xine/ivtv module after
one night work and don't feel to put more work into it that I don't need. BTW
good to hear that 2.0 is close and that it will incorporate xine/ivtv/tv
support!

I also wrote a shutdown/wakeup plugin for 1.5.4 that can do what some of the
shutdown plugins out there can do. In addition, it includes an option for a
periodic startup, in the case no recordings are scheduled (just for
retrieving the program guide). Will 2.0 include the more advanced
shutdown/wakeup functionality too?

Maybe I should move on to Freevo 2.0, but I'd like to have a functional,
stable Freevo setup too...

- Richard.




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Freevo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to