Re: [Freevo-users] can't control via tcp remote

2009-03-15 Thread Wookjin, Na 
network issue is solved.

thanks webb

best regard


- Original Message - 
From: "Duncan Webb" 
Cc: 
Sent: Monday, March 16, 2009 5:15 AM
Subject: Re: [Freevo-users] can't control via tcp remote


> Duncan Webb wrote:
>> Wookjin, Na wrote:
>>> hi ,
>>>  
>>> I have a question. It makes me dizzy. please help me...
>>>  
>>> I used to remote control the freevo via tcp.
>>>  
>>> but this control not work when I played a movie with xine.
>>>  
>>> just only volume up,down and mute works well.
>>>  
>>> I checked text control message with print received via TCP.
>>>  
>>> I do not have any idea why freevo remote control is not working when I
>>> used to TCP remote.
>>>  
>>> but UDP works well, I tried to work with remote.py (in helper's folder)
>> 
>> You can try telnet and type the commands, which are freevo events, and
>> see if this works. The commands are like DOWN, UP, SELECT.
> 
> 
> Also change the remote.py to use SOCK_STREAM instead of SOCK_DGRAM
> 
> 
> Duncan
> 
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> Freevo-users mailing list
> Freevo-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freevo-users
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users

Re: [Freevo-users] can't control via tcp remote

2009-03-15 Thread Duncan Webb 
Duncan Webb wrote:
> Wookjin, Na wrote:
>> hi ,
>>  
>> I have a question. It makes me dizzy. please help me...
>>  
>> I used to remote control the freevo via tcp.
>>  
>> but this control not work when I played a movie with xine.
>>  
>> just only volume up,down and mute works well.
>>  
>> I checked text control message with print received via TCP.
>>  
>> I do not have any idea why freevo remote control is not working when I
>> used to TCP remote.
>>  
>> but UDP works well, I tried to work with remote.py (in helper's folder)
> 
> You can try telnet and type the commands, which are freevo events, and
> see if this works. The commands are like DOWN, UP, SELECT.


Also change the remote.py to use SOCK_STREAM instead of SOCK_DGRAM


Duncan

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users

Re: [Freevo-users] Problem watching live TV with mplayer

2009-03-15 Thread Duncan Webb 
Art S R wrote:
> On Sat, Mar 14, 2009 at 10:33 AM, Duncan Webb  wrote:
>> Art S R wrote:
>>> Hi Duncan,
>>>
>>> Here are the relevant lines from my local_conf.py:
>>>
>>> NORM = 'ntsc'
>>> INPUT = 'television'
>>> CHANLIST = 'us-cable'
>>> TV_DRIVER = 'v4l2'
>>> TV_DEVICE = '/dev/video0'
>>> TV_INPUT = 0
>>> TV_SETTINGS = 'NORM INPUT CHANLIST DEVICE'
>> This won't work and should never have worked.
>>
>> TV_SETTINGS is a string of values and should be something like:
>> TV_SETTINGS = 'ntsc television us-cable /dev/video0'
> 
> This produced exactly the same poor results as what I'd set originally.

You may need to debug this a bit yourself, it's not too hard. In
tv/v4l2.py add some print statements in the setstd (you can also set
DEBUG=2 in local_conf.py but this will give too much information). When
you see the standard being changed to PAL you can add a couple of lines:
import traceback
traceback.print_stack()
This will show you from where the setstd was called from.

Another trick is to type
freevo prompt
>>> import pprint
>>> import config
>>> pprint.pprint(config.__dict__)
This will show all the configuration settings; to send this to a file use:
>>> f = open('/tmp/x', 'w')
>>> pprint.pprint(config.__dict__, f)
>>> f.close()

grep -i pal /tmp/x
will show you if PAL has been set somewhere.

Duncan
> 
>> The more flexible way to do this is to add a TV_VIDEO_GROUPS setting to
>> you local_conf.py and comment out the TV_SETTINGS. You should be able to
>> generate the TV_VIDEO_GROUPS with the vg helper and then manually fix
>> the output from this command (freevo vg).
>>
>> Please send me the output from the freevo vg as I want to see if it is
>> working correctly.
> 
> Here's my 'freevo vg' output using the svn vg.py you sent me:
> 
> TV_VIDEO_GROUPS = [
>   VideoGroup( # normal device, group 0
> desc='BT878 video (Hauppauge (bt878))',
> group_type='normal',
> vdev='/dev/video0',
> vvbi='/dev/vbi0',
> adev=None,
> input_type='Television',
> input_num=0,
> tuner_norm='PAL',
> tuner_chanlist='FixMe',
> record_group=None
>   ),
> ]
> 
> Looks like it's erroneously using tuner_norm='PAL'  (instead of
> 'NTSC') and it doesn't know what tuner_chanlist should be.  By the
> way, the Freevo 1.8.3 version of vg.py listed all the available
> tv_norm standards:
> 
> tuner_norm='SECAM-DK,SECAM-L,NTSC-M,NTSC-M-KR,PAL,SECAM-G,PAL-M,SECAM-H,SECAM,SECAM-B,PAL-DK,SECAM-Lc,PAL-I,PAL-BG,NTSC-M-JP,PAL-60,PAL-N,NTSC,PAL-H,PAL-Nc',

I think that you should get the correct default just after boot and
before freevo has changed it to PAL. Or by stopping the record server
and freevo and rmmod and modprobe the driver.

> but tuner_chanlist also said 'FixMe'.

It's a bit difficult to default this. I don't think there a way to
default the channel list?

>> Attached is the current svn version that should set the tv standard
>> (tv_norm) you still need to set the channel list.
>>
>> HTH
>> Duncan
>>
>>> I used the same values in my previous Freevo installations (1.6.x,
>>> 1.7.x) and did not have problems watching live TV with the mplayer plugin.
>>>
>>> Thanks,
>>>
>>> Art SR
>>>
>>> On Tue, Mar 10, 2009 at 1:08 PM, Duncan Webb >> > wrote:
>>>
>>> Art S R wrote:
>>> > Hi Duncan,
>>> >
>>> > I tried 'v4l2-ctl --set-freq=187.250' but nothing changed on the
>>> Freevo
>>> > window playing live TV -- it still displayed the ghosted random
>>> > station.  I then issued 'v4l2-ctl --all' and noticed that the Video
>>> > Standard is set to PAL even though it should have been NTSC as it was
>>> > passed to the mplayer command in the 'norm=NTSC' parameter.  When I
>>> > issued 'v4l2-ctl --set-standard=ntsc', then the correct station popped
>>> > up in the Freevo TV window.  However, if I hit Esc to return to the
>>> > Freevo TV guide and select any station, it displays the garbage screen
>>> > again and 'v4l2-ctl --all' shows that Freevo had changed the Video
>>> > Standard back to PAL.
>>> >
>>> > I even grabbed the svn version of mplayer.py, but it made no
>>> difference.
>>> >
>>> > Any ideas why the exact same command, when issued outside of Freevo,
>>> > displays the station correctly but, when passed by Freevo to mplayer,
>>> > the video standard is changed from NTSC to PAL?
>>>
>>> Would need to see what TV settings you have in your local_conf.py to see
>>> what could be causing this problem. Will you post the TV_ settings from
>>> you local_conf.py?
>>>
>>> Duncan
>>>
>>>
>>
> 


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. htt

Re: [Freevo-users] can't control via tcp remote

2009-03-15 Thread Duncan Webb 
Wookjin, Na wrote:
> hi ,
>  
> I have a question. It makes me dizzy. please help me...
>  
> I used to remote control the freevo via tcp.
>  
> but this control not work when I played a movie with xine.
>  
> just only volume up,down and mute works well.
>  
> I checked text control message with print received via TCP.
>  
> I do not have any idea why freevo remote control is not working when I
> used to TCP remote.
>  
> but UDP works well, I tried to work with remote.py (in helper's folder)

You can try telnet and type the commands, which are freevo events, and
see if this works. The commands are like DOWN, UP, SELECT.

> by the way, when I first start a freevo, tcp port is settup twice so It
> made error message of port is occupied
>  
> that's not important i think . because I made it port number increasing.
> so It just passed.

The last part of you problem is caused by the last line of
src/util/__init__.py which imports mediainfo; comment out this line and
the bind error should go away.

I couldn't reproduce this error last time I tried but I can now. What is
happening is that the mediainfo is causing the rc.py to reinitialise
before it had finished the first time.

Duncan

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users

Re: [Freevo-users] TV recordings don't display year on Recorded shows page

2009-03-15 Thread Art S R 
On Sat, Mar 14, 2009 at 9:31 AM, Duncan Webb  wrote:
> Art S R wrote:
>> Hi all,
>>
>> I noticed that when I go to the Recorded shows page, the year
>> (date/timestamp) field is not displayed to the left of runtime for any
>> of my recordings in Freevo 1.8.3.  I verified the fxd files contained
>> year info.  When I ran debug, I noticed that mediainfo.py was assigning
>> userdate as the year.  Checking svn, I saw that in revision 10905 of
>> mediainfo.py, there's a comment "Fixed missing year item, change to
>> userdate in kaa.metadata" and the following statements were added to def
>> __getitem__(self, key):
>>         if key == 'year':
>>             key = 'userdate'
>> Even though the Freevo 1.8.3 version of mediainfo.py includes these
>> statements, year is not displayed.  However, when I commented out these
>> two statements, the year information is now displayed correctly when
>> looking at the descriptions of my recorded TV shows.  It seems the fix
>> is what actually is causing the problem with the year not displaying?
>> Or is this dependent on the kaa.metadata version?  I'm using
>> kaa.metadata-0.7.5 from sourceforge.
>
> The userdate is really for audio (MP3) files so if you remove the lines
> the date from the audio files will be removed.
>
> Personally I don't think the year of the recording is very useful,
> possible the scheduled recording date would be better.

Actually, the 'year' variable displays the date/timestamp of the
recorded program, such as:  "(Fri, 27 Feb 2009 03:00:00 PST)"
displayed to the left of the recording length (e.g., "59 min").  This
entire date/timestamp line was missing underneath the program
description, leaving only the recording length.  I find it useful to
know when a particular recording was made.

> May be also the channel that a programme has been recorded on would be a
> useful addition too.
>
> Duncan
>
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> Freevo-users mailing list
> Freevo-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freevo-users
>

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users

Re: [Freevo-users] Problem watching live TV with mplayer

2009-03-15 Thread Art S R 
On Sat, Mar 14, 2009 at 10:33 AM, Duncan Webb  wrote:
> Art S R wrote:
>> Hi Duncan,
>>
>> Here are the relevant lines from my local_conf.py:
>>
>> NORM = 'ntsc'
>> INPUT = 'television'
>> CHANLIST = 'us-cable'
>> TV_DRIVER = 'v4l2'
>> TV_DEVICE = '/dev/video0'
>> TV_INPUT = 0
>> TV_SETTINGS = 'NORM INPUT CHANLIST DEVICE'
>
> This won't work and should never have worked.
>
> TV_SETTINGS is a string of values and should be something like:
> TV_SETTINGS = 'ntsc television us-cable /dev/video0'

This produced exactly the same poor results as what I'd set originally.

> The more flexible way to do this is to add a TV_VIDEO_GROUPS setting to
> you local_conf.py and comment out the TV_SETTINGS. You should be able to
> generate the TV_VIDEO_GROUPS with the vg helper and then manually fix
> the output from this command (freevo vg).
>
> Please send me the output from the freevo vg as I want to see if it is
> working correctly.

Here's my 'freevo vg' output using the svn vg.py you sent me:

TV_VIDEO_GROUPS = [
  VideoGroup( # normal device, group 0
desc='BT878 video (Hauppauge (bt878))',
group_type='normal',
vdev='/dev/video0',
vvbi='/dev/vbi0',
adev=None,
input_type='Television',
input_num=0,
tuner_norm='PAL',
tuner_chanlist='FixMe',
record_group=None
  ),
]

Looks like it's erroneously using tuner_norm='PAL'  (instead of
'NTSC') and it doesn't know what tuner_chanlist should be.  By the
way, the Freevo 1.8.3 version of vg.py listed all the available
tv_norm standards:

tuner_norm='SECAM-DK,SECAM-L,NTSC-M,NTSC-M-KR,PAL,SECAM-G,PAL-M,SECAM-H,SECAM,SECAM-B,PAL-DK,SECAM-Lc,PAL-I,PAL-BG,NTSC-M-JP,PAL-60,PAL-N,NTSC,PAL-H,PAL-Nc',

but tuner_chanlist also said 'FixMe'.


> Attached is the current svn version that should set the tv standard
> (tv_norm) you still need to set the channel list.
>
> HTH
> Duncan
>
>>
>> I used the same values in my previous Freevo installations (1.6.x,
>> 1.7.x) and did not have problems watching live TV with the mplayer plugin.
>>
>> Thanks,
>>
>> Art SR
>>
>> On Tue, Mar 10, 2009 at 1:08 PM, Duncan Webb > > wrote:
>>
>>     Art S R wrote:
>>     > Hi Duncan,
>>     >
>>     > I tried 'v4l2-ctl --set-freq=187.250' but nothing changed on the
>>     Freevo
>>     > window playing live TV -- it still displayed the ghosted random
>>     > station.  I then issued 'v4l2-ctl --all' and noticed that the Video
>>     > Standard is set to PAL even though it should have been NTSC as it was
>>     > passed to the mplayer command in the 'norm=NTSC' parameter.  When I
>>     > issued 'v4l2-ctl --set-standard=ntsc', then the correct station popped
>>     > up in the Freevo TV window.  However, if I hit Esc to return to the
>>     > Freevo TV guide and select any station, it displays the garbage screen
>>     > again and 'v4l2-ctl --all' shows that Freevo had changed the Video
>>     > Standard back to PAL.
>>     >
>>     > I even grabbed the svn version of mplayer.py, but it made no
>>     difference.
>>     >
>>     > Any ideas why the exact same command, when issued outside of Freevo,
>>     > displays the station correctly but, when passed by Freevo to mplayer,
>>     > the video standard is changed from NTSC to PAL?
>>
>>     Would need to see what TV settings you have in your local_conf.py to see
>>     what could be causing this problem. Will you post the TV_ settings from
>>     you local_conf.py?
>>
>>     Duncan
>>
>>
>
>

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users

Re: [Freevo-users] SVN version 11339 is not working?

2009-03-15 Thread Duncan Webb 
Han Hartgers wrote:
> Hi Ducan and others,
> 
> I have tried last night freevo svn 11342 with kaa svn 3862.
> 
> The webserver is indeed started in the background with "freevo
> webserver --daemon". (SOLVED)
> 
> One of the problems that still persists is that freevo itself is not
> passing the intro screen.
> 
> I try to explain the situation a bit better:
> 
> Begin situation: no freevo related process is running.
> 
> When I start freevo,  "freevo" on the shell prompt. the intro screen
> is displayed but stopped when the progress bar is full.  I never get
> to the menu.
> (The main-1001.log file is generated change compared with last time I
> tried the svn.)
> I think that the problem is the way how the webserver is automatically
> started from the freevo process; this is what I see when I do  "ps ax
> | grep freevo":
> 
>  6731 pts/0S+ 0:00 /usr/bin/python /usr/bin/freevo
>  6735 pts/0Sl+0:04 python
> /usr/lib/python2.5/site-packages/freevo/main.py
>  6745 pts/0S+ 0:00 sh -c /usr/bin/freevo webserver start
>  6746 pts/0S+ 0:00 /usr/bin/python /usr/bin/freevo webserver start
>  6749 pts/0S+ 0:00 python
> /usr/lib/python2.5/site-packages/freevo/helpers/webserver.py webserver
> start
> 
> I believe that the word "start" should have been --daemon for process
> 6745 and/or 6746. The webserver is running and is responsive to
> requests.
> I do get the freevo main menu when I kill process 6746.

I think that this was my fault I hadn't noticed that the freevo script
was being used in unexpected places such as the www plug-in.

If you are using the www plugin (plugin.activate('www')) and starting
the webserver from the command line then remove the plug-in activation
from the local_conf.py. IMHO having the www plug-in causes more problems
than it solves; why do we need to start the plug-in when freevo starts
rather than when the machine starts?

> (I do not have this problem when I start the webserver in advance
> before I start freevo but freevo is complaining a bit on the prompt
> about that situation: "webserver still running, run 'webserver --stop'
> to stop" noting is shown in the log file.)
> 
> 
> I have one error message (coming from the weather plugin) but I do not
> care too much about that now.
>  ERROR: global name 'NetworkException' is not defined

Which weather plug-in?

> But  a more inportant item is that the system shutdown functionality
> is not really working.
> Freevo shutdown (the freevo process stops) but the computer not (the
> shutdown/halt command is never issued). This is both true for the menu
> option "shutdown system" as the automatic shutdown timer.

This should be fixed too, another place where the freevo script was
being used.

> I have this in my local_config.py
> 
> SYS_SHUTDOWN_CMD = "/home/freevo/bin/sysshutdown.sh halt"
> SYS_RESTART_CMD = "/home/freevo/bin/sysshutdown.sh reboot"
> 
> (sysshutdown.sh is a little wrapper script arround "sudo shutdown -h
> now" (or -r now))
> And that worked well with svn release 11227.
> 
> Is the variable name changed or is it something more in the internals
> of freevo/kaa?

Duncan

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users