[Freevo-users] [ANNOUNCE] freevo-vdr-0.5 for Freevo-1.5.4

2005-11-08 Thread Lucian Muresan
Hi,

after succeeding to make VDR happily work under df_xine starting from
the plugin version Mike Lewis sent some weeks ago to the users ML, I did
some hacking around and the result is a packaged freevo-vdr add-on (I
think originally called vdr-xine by Ove Risberg).

From HISTORY, what I've done since Mike's modifications:
- migrated to use http://sourceforge.net/projects/vdrpylib and therefore
renamed internally to vdrtv.py;
- added new VDR keys mapped to spare or new (which you can add in your
freevo freevo lircrc) LIRC events, see README for the complete list;
- added detection if the freevo VDR plugin is loaded in VDR, allowing
to switch off VDR's remotes via SVDRP (thus making compiling VDR without
LIRC or KBD support for proper operation whithin Freevo unnecessary) and
then VDR's remotes will only be enabled during key-presses from Freevo.
If the VDR plugin freevo which provides this functionality is not
detected at initialization, a warning is printed.
- re-added Ove's original setup.py and MANIFEST.in with little
odifications, added separate HISTORY, README and PKG-INFO files

From README:
REQUIREMENTS:

- vdrpylib from http://sourceforge.net/projects/vdrpylib installed
normally by python setup.py install
- a running vdr installation (of course :)
- when using tvtime/SVDRP: (Full featured DVB cards)
   - set SVDRP Timeout in vdrs OSD to 0
   - make sure to setup svdrphosts.conf correctly
   - add the color buttons (YELLOW,GREEN,RED,BLUE) to freevo's lirc file
   - optional, but yet very useful, add the buttons which are missing
from the right column below to freevo's lirc file:
VDR key: |  Freevo LIRC event
==
'RECORDINGS' : Event('RECORDINGS'),
'CHANNELS'   : Event('CHANNELS'),
'AUDIO'  : Event('LANG'),
'SCHEDULE'   : Event('GUIDE'),
'TIMERS' : Event('TIMERS'),
'SETUP'  : Event('SETUP'),
'COMMANDS'   : Event('EJECT'),
   - when using SVDRP, to avoid keystroke conflicts and not having to
bother with building VDR without LIRC and KBD support, use the new
vdr-freevo VDR plugin and load it with -P'freevo'. The plugin will be
detected by freevo's VDR plugin and then VDR's remotes will only be
enabled during key-presses from Freevo. If the VDR plugin freevo which
provides this functionality is not detected at initialization, a warning
is printed.
   - for XINE (Budget DVB cards, streaming client)
   - when using xine as a VDR decoder, the xine plugin for vdr. Start
vdr with -P'xine -r'

INSTALL:

- Unpack and run python setup.py install in the main source directory;
- Activatee the plugin in local_conf.py with
   plugin.activate('vdr_interface')
   plugin.activate('vdrtv', level=5)

- Configure the plugin by these variables in local_conf.py:
VDR_VIEWER_PLUGIN='xine'
VDR_USE_SVDRP=1
VDR_SVDRP_HOST='localhost'
VDR_SVDRP_PORT=2001
VDR_SVDRP_ALWAYSCLOSE=0
VDR_XINE_PIPE_PATH='vdr://var/vdr/xine/stream#demux:mpeg_pes'


You can download the Freevo plugin from
http://www.muresan.de/freevo/freevo-vdr-0.5.tgz
And the highly recommended VDR freevo plugin
http://www.muresan.de/freevo/vdr-freevo-0.0.1.tgz
This one does no more than providing the remotes deactivation/activation
in VDR for now, and has an yet unnecessary menu entry on VDR's main
menu, I will clean that up. In a later version, this plugin will
hopefully supress VDR's native OSD and we'll render it nicely on Freevo
side, directly in kaa.xine ;-). You might need to patch your VDR (for
sure up to vdr-1.3.36) before compiling this plugin, patch included in
the archive.


For Gentoo users:
Instead of getting the archives, you could just put the following
ebuilds somewhere in your portage overlay:

http://www.muresan.de/freevo/vdrpylib-.ebuild under
../dev-python/vdrpylib
http://www.muresan.de/freevo/vdrpylib.diff under
../dev-python/vdrpylib/files; unmask with -* as this will checkout
from CVS;

http://www.muresan.de/freevo/freevo-vdr-0.5.ebuild under
../media-plugins/freevo-vdr; unmask with ~x86 and set the USE flag
vdr_remotes_off for making it dependent of the companion plugin on VDR
side and get rid of keystroke conflicts:
http://www.muresan.de/freevo/vdr-freevo-0.0.1.ebuild under
../media-plugins/vdr-freevo; unmask with ~x86 and don't forget to
patch your VDR first.

Have fun, feedback appreciated, thanks to all who helped me so far!
Lucian

P.S. Mike Lewis, you might want to detail your enhancments in the
HISTORY and maybe also in the README :-)



---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42 plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net

Re: [Freevo-users] [ANNOUNCE] freevo-vdr-0.5 for Freevo-1.5.4

2005-11-08 Thread Rob Shortt
Lucian Muresan wrote:
 - migrated to use http://sourceforge.net/projects/vdrpylib and therefore

I hope you're using the CVS version of this. :)  If you're using a
recent VDR then it is required to work properly.

-Rob


-- 
---
Rob Shortt| http://tvcentric.com | Freevo
[EMAIL PROTECTED] | http://freevo.sf.net | Free your TV


signature.asc
Description: OpenPGP digital signature


Re: [Freevo-users] [ANNOUNCE] freevo-vdr-0.5 for Freevo-1.5.4

2005-11-08 Thread Ove Risberg
Great work...

I have tried to find time to update my vdr_xine plugin but there is so
many projects and so little time :-)

I could never decide how to map freevos EXIT event to vdrs BACK and EXIT
events.
The best solution would be to map EXIT to EXIT when vdr is does not have
any menus displayed and map EXIT to BACK when vdr is in any menu, but
how do we do this?

Do you plan to upload your plugin to the freevo addons page?
http://freevo.sourceforge.net/addons/

/Ove

On Tue, 2005-11-08 at 15:12, Lucian Muresan wrote:
 Hi,
 
 after succeeding to make VDR happily work under df_xine starting from
 the plugin version Mike Lewis sent some weeks ago to the users ML, I did
 some hacking around and the result is a packaged freevo-vdr add-on (I
 think originally called vdr-xine by Ove Risberg).
 
 From HISTORY, what I've done since Mike's modifications:
 - migrated to use http://sourceforge.net/projects/vdrpylib and therefore
 renamed internally to vdrtv.py;
 - added new VDR keys mapped to spare or new (which you can add in your
 freevo freevo lircrc) LIRC events, see README for the complete list;
 - added detection if the freevo VDR plugin is loaded in VDR, allowing
 to switch off VDR's remotes via SVDRP (thus making compiling VDR without
 LIRC or KBD support for proper operation whithin Freevo unnecessary) and
 then VDR's remotes will only be enabled during key-presses from Freevo.
 If the VDR plugin freevo which provides this functionality is not
 detected at initialization, a warning is printed.
 - re-added Ove's original setup.py and MANIFEST.in with little
 odifications, added separate HISTORY, README and PKG-INFO files
 
 From README:
 REQUIREMENTS:
 
 - vdrpylib from http://sourceforge.net/projects/vdrpylib installed
 normally by python setup.py install
 - a running vdr installation (of course :)
 - when using tvtime/SVDRP: (Full featured DVB cards)
- set SVDRP Timeout in vdrs OSD to 0
- make sure to setup svdrphosts.conf correctly
- add the color buttons (YELLOW,GREEN,RED,BLUE) to freevo's lirc file
- optional, but yet very useful, add the buttons which are missing
 from the right column below to freevo's lirc file:
   VDR key: |  Freevo LIRC event
   ==
   'RECORDINGS' : Event('RECORDINGS'),
   'CHANNELS'   : Event('CHANNELS'),
   'AUDIO'  : Event('LANG'),
   'SCHEDULE'   : Event('GUIDE'),
   'TIMERS' : Event('TIMERS'),
   'SETUP'  : Event('SETUP'),
   'COMMANDS'   : Event('EJECT'),
- when using SVDRP, to avoid keystroke conflicts and not having to
 bother with building VDR without LIRC and KBD support, use the new
 vdr-freevo VDR plugin and load it with -P'freevo'. The plugin will be
 detected by freevo's VDR plugin and then VDR's remotes will only be
 enabled during key-presses from Freevo. If the VDR plugin freevo which
 provides this functionality is not detected at initialization, a warning
 is printed.
- for XINE (Budget DVB cards, streaming client)
- when using xine as a VDR decoder, the xine plugin for vdr. Start
 vdr with -P'xine -r'
 
 INSTALL:
 
 - Unpack and run python setup.py install in the main source directory;
 - Activatee the plugin in local_conf.py with
plugin.activate('vdr_interface')
plugin.activate('vdrtv', level=5)
 
 - Configure the plugin by these variables in local_conf.py:
 VDR_VIEWER_PLUGIN='xine'
 VDR_USE_SVDRP=1
 VDR_SVDRP_HOST='localhost'
 VDR_SVDRP_PORT=2001
 VDR_SVDRP_ALWAYSCLOSE=0
 VDR_XINE_PIPE_PATH='vdr://var/vdr/xine/stream#demux:mpeg_pes'
 
 
 You can download the Freevo plugin from
 http://www.muresan.de/freevo/freevo-vdr-0.5.tgz
 And the highly recommended VDR freevo plugin
 http://www.muresan.de/freevo/vdr-freevo-0.0.1.tgz
 This one does no more than providing the remotes deactivation/activation
 in VDR for now, and has an yet unnecessary menu entry on VDR's main
 menu, I will clean that up. In a later version, this plugin will
 hopefully supress VDR's native OSD and we'll render it nicely on Freevo
 side, directly in kaa.xine ;-). You might need to patch your VDR (for
 sure up to vdr-1.3.36) before compiling this plugin, patch included in
 the archive.
 
 
 For Gentoo users:
 Instead of getting the archives, you could just put the following
 ebuilds somewhere in your portage overlay:
 
 http://www.muresan.de/freevo/vdrpylib-.ebuild under
 ../dev-python/vdrpylib
 http://www.muresan.de/freevo/vdrpylib.diff under
 ../dev-python/vdrpylib/files; unmask with -* as this will checkout
 from CVS;
 
 http://www.muresan.de/freevo/freevo-vdr-0.5.ebuild under
 ../media-plugins/freevo-vdr; unmask with ~x86 and set the USE flag
 vdr_remotes_off for making it dependent of the companion plugin on VDR
 side and get rid of keystroke conflicts:
 http://www.muresan.de/freevo/vdr-freevo-0.0.1.ebuild under
 ../media-plugins/vdr-freevo; unmask with ~x86 and don't forget to
 patch your VDR first.
 
 Have fun,