Re: [Freevo-devel] ivtv-xine-tv problem

2009-02-01 Thread Duncan Webb
Hans Meine wrote: > On Freitag 02 Januar 2009, Duncan Webb wrote: >> Hans Meine wrote: >>> Hi, >>> >>> after my system and freevo updates, I still have one problem: Interlaced >>> content (i.e., TV & recordings) does not get deinterlaced anymore. Are >>> there any (new) settings I need to adjust?

Re: [Freevo-devel] ivtv-xine-tv problem

2009-02-01 Thread Hans Meine
On Freitag 02 Januar 2009, Duncan Webb wrote: > Hans Meine wrote: > > Hi, > > > > after my system and freevo updates, I still have one problem: Interlaced > > content (i.e., TV & recordings) does not get deinterlaced anymore. Are > > there any (new) settings I need to adjust? > > Isn't this an opt

[Freevo-devel] Freevo 1.x and kaa.rpc2

2009-02-01 Thread Dirk Meyer
Hi, I changed the code in Freevo 1.x to use kaa.rpc2 instead of kaa.rpc. Please test. If it works, I will move kaa.rpc2 to kaa.rpc in kaa.base. Dischi -- I just got lost in thought... It was unfamiliar territory. --

Re: [Freevo-devel] unable to start freevo2

2009-02-01 Thread Dirk Meyer
Stephen Rowles wrote: > Having seen the python 2.5 discussion I thought I would give freevo2 a > shot on my laptop. I'm a java developer so I know about svn and code but > no real python experience, I'm happy to hack away a bit to get it > working if required :). > > hardware: Core Duo T7300 @ 2

[Freevo-devel] unable to start freevo2

2009-02-01 Thread Stephen Rowles
Having seen the python 2.5 discussion I thought I would give freevo2 a shot on my laptop. I'm a java developer so I know about svn and code but no real python experience, I'm happy to hack away a bit to get it working if required :). hardware: Core Duo T7300 @ 2ghz, 2gig ram, Intel X3100 graphi

Re: [Freevo-devel] More Problems with current Freevo rel-1: autoshutdown plugin, favorites, romdrive output

2009-02-01 Thread Duncan Webb
Hans Meine wrote: > Hi Duncan, > >> But I think the test is incorrect. It should be >> and event != Event('SCREENSAVER_START') >> again freevo prompt comes in handy here: >> # freevo prompt >> Python 2.6.1 (r261:67515, Jan 24 2009, 14:48:40) >> [GCC 4.1.1] on linux2 >> Type "help", "copyright", "c

Re: [Freevo-devel] Bug in conflict resolution (Freevo rel-1 branch, r11270)

2009-02-01 Thread Duncan Webb
Hans Meine wrote: > On Sonntag 01 Februar 2009, Duncan Webb wrote: >> Hans Meine wrote: >>> On Donnerstag 29 Januar 2009, Duncan Webb wrote: > BTW: How do I enable the output of all the _debug_('...', 2) lines? (I > tried setting DEBUG and DEBUG_RECORDSERVER to 2, but that did not do >

Re: [Freevo-devel] Bug in conflict resolution (Freevo rel-1 branch, r11270)

2009-02-01 Thread Hans Meine
On Sonntag 01 Februar 2009, Duncan Webb wrote: > Hans Meine wrote: > > On Donnerstag 29 Januar 2009, Duncan Webb wrote: > >>> BTW: How do I enable the output of all the _debug_('...', 2) lines? (I > >>> tried setting DEBUG and DEBUG_RECORDSERVER to 2, but that did not do > >>> the trick.) > >> > >

Re: [Freevo-devel] More Problems with current Freevo r el-1: autoshutdown plugin, favorites, romdr ive output

2009-02-01 Thread Hans Meine
Hi Duncan, thanks for your answers. On Sonntag 01 Februar 2009, Duncan Webb wrote: > > File "/usr/lib/python2.5/site-packages/freevo/plugins/autoshutdown.py", > > line 364, in eventhandler > > if plugin.isevent(event) != 'IDENTIFY_MEDIA' and > > event.name != 'SCREENSAVER_START': > > Attrib

Re: [Freevo-devel] More Problems with current Freevo rel-1: autoshutdown plugin, favorites, romdrive output

2009-02-01 Thread Duncan Webb
Hans Meine wrote: > Hi again, > > maybe I should not run a potentially unstable development version on the > living room HTPC used by my wife, but now I am facing the following problems > (apart from the non-working recordserver): > > 1) Freevo just showed her a "crash" message; the autoshutdow

Re: [Freevo-devel] Bug in conflict resolution (Freevo rel-1 branch, r11270)

2009-02-01 Thread Duncan Webb
Hans Meine wrote: > On Donnerstag 29 Januar 2009, Duncan Webb wrote: >>> BTW: How do I enable the output of all the _debug_('...', 2) lines? (I >>> tried setting DEBUG and DEBUG_RECORDSERVER to 2, but that did not do the >>> trick.) >> Have you set? >> LOGGING = logging.DEBUG >> LOGGING_RECORDSERV