Dear Wiki user, You have subscribed to a wiki page or wiki category on "Freevo Wiki" for change notification.
The following page has been changed by 24.224.158.108: http://freevo.sourceforge.net/cgi-bin/moin.cgi/DocumentationPage ------------------------------------------------------------------------------ @@ -69,87 +69,6 @@ * Check path for mencoder in VCR command -=== Recording Server === - -If you are using Freevo from CVS then you need to be running record_server.py instead of using record_daemon.py from cron, please see below. - -If you will be recording with record_daemon.py (Freevo version 1.3.4 or older), you will need to a single cron job. This cronjob should call '<path>/freevo execute src/tv/record_daemon.py' as often as you want. Most people run this every minute of every hour, but some run only every five. That's your call-- will you miss a record command on every five? - Sample cron entry: -{{{ - # Every minute - * * * * * /usr/local/freevo/freevo execute src/tv/record_daemon.py - # Every 5 minutes instead (remove #) - #*/5 * * * * /usr/local/freevo/freevo execute src/tv/record_daemon.py -}}} - -{{{ - NOTE: - Many people have library path errors with the record_daemon.py. You should log - the output of your cronjob or watch the local mail for this account carefully - for the first few days and make sure it is working. - The error is something like: - sh: /lib/ld-linux.so.2: version `GLIBC_PRIVATE' not found - (required by ./runtime/dll/libc.so.6) - - The fix is to edit freevo/src/tv/record_daemon.py and add the second line as seen below: - import os - os.environ['LD_PRELOAD'] = '' # Add this line to stop GLIBC_2.X preload errors - -}}} - -If you are using Freevo from CVS then you need to be running record_server.py instead of using record_daemon.py from cron. - -record_server.py is a completly new interface for TV recording. This is a standalone persistant process that runs seperately from the main Freevo preocess that you see on your TV or monitor. Record server listens on the network for client connections and will communicate to a client using XML-RPC. - -Please make sure that your XMLTV data is displaying correctly in the Freevo program guide before attempting to run the record server. This will save you problems in case there is something wrong with epg_xmltv.py or your XMLTV data. Since record_server.py must run outside of the main Freevo process you should use one of the scripts in the boot/ directory to help start it. The record_server scripts here need you to have the boot_config file placed in your /etc/freevo/ directory and edited to suit your system. The record_server script is an rc style start/stop script and can be placed in your /etc/init.d/ directory (or equivalent) but must be set to start/stop at the proper runlevels. That is outside the scope of this document. The record_server_init script is designed to run from the init process using your /etc/inittab file. There are instructions for doing this at the top of the record_server_init file. - -If you are not using the Freevo binary runtime and instead installed all of the Freevo dependancies yourself, make sure you have Twisted (http://www.twistedmatrix.com) installed as well. - - -'''Record server configuration:''' - -You must chose a recording plugin. The default plugin is generic_record and if you are using mencoder or any other external command to do your recording then this is the plugin for you. If, on the other hand, you are using a Hauppage WinTV PVR-250/350 then you can activate the ivtv_record plugin and it will do the recording work for you. Before using this card in Freevo please make sure that it is working properly and you have no driver problems. See http://ivtv.sourceforge.net for details. - -The recording server looks for a few items in your config: DIR_RECORD, RECORD_SCHEDULE, RECORD_SERVER_IP, and RECORD_SERVER_PORT. Please see frevo_config.py for details. Please be aware that record_server.py is a network application and your Freevo machine should not have wide open access from the internet without a firewall limiting what ports outsiders can connect to. - -If you are using the generic_record plugin (default) then you must have VCR_CMD configured to your liking. There is an example of this in freevo_config.py as well. - -In order to use the ivtv recording plugin have the following in your local_conf.py: - -{{{ -plugin.remove('tv.generic_record') -plugin_record = plugin.activate('tv.ivtv_record') -}}} - -Also for ivtv_record you may set some recording options: - -{{{ -IVTV_OPTIONS = { - 'input' : 4, - 'resolution' : '720x480', - 'aspect' : 2, - 'audio_bitmask' : 233, - 'bframes' : 3, - 'bitrate_mode' : 1, - 'bitrate' : 4000000, - 'bitrate_peak' : 4000000, - 'dnr_mode' : 0, - 'dnr_spatial' : 0, - 'dnr_temporal' : 0, - 'dnr_type' : 0, - 'framerate' : 0, - 'framespergop' : 15, - 'gop_closure' : 1, - 'pulldown' : 0, - 'stream_type' : 10, -} - -# Please see freevo_config.py for details. -}}} - -Once configured, and you would like to test the recording server, simply run ./record_server start (record_server script from the boot/ directory). Remember, those scripts rely on the boot_config file being in /etc/freevo/ and modified for your system. Once it is running you will have a log, either in /var/log/freevo or /tmp/freevo, called internal-record_server-0.log (0 is the uid of the user running it, 'root' in this case). The web interface or the main Freevo interface will let you know if the recording server is down. It will need to be running in order to schedule and record shows. - - === TV setup === ==== XMLTV ==== @@ -235,6 +154,88 @@ It uses the information in the /tmp/TV.xml file, which has url's for the logos, to locate and grab the images. The logos are stored and will be displayed in the channel list. + + +=== Recording Server === + +If you are using Freevo from CVS then you need to be running record_server.py instead of using record_daemon.py from cron, please see below. + +If you will be recording with record_daemon.py (Freevo version 1.3.4 or older), you will need to a single cron job. This cronjob should call '<path>/freevo execute src/tv/record_daemon.py' as often as you want. Most people run this every minute of every hour, but some run only every five. That's your call-- will you miss a record command on every five? + Sample cron entry: +{{{ + # Every minute + * * * * * /usr/local/freevo/freevo execute src/tv/record_daemon.py + # Every 5 minutes instead (remove #) + #*/5 * * * * /usr/local/freevo/freevo execute src/tv/record_daemon.py +}}} + +{{{ + NOTE: + Many people have library path errors with the record_daemon.py. You should log + the output of your cronjob or watch the local mail for this account carefully + for the first few days and make sure it is working. + The error is something like: + sh: /lib/ld-linux.so.2: version `GLIBC_PRIVATE' not found + (required by ./runtime/dll/libc.so.6) + + The fix is to edit freevo/src/tv/record_daemon.py and add the second line as seen below: + import os + os.environ['LD_PRELOAD'] = '' # Add this line to stop GLIBC_2.X preload errors + +}}} + +If you are using Freevo from CVS then you need to be running record_server.py instead of using record_daemon.py from cron. + +record_server.py is a completly new interface for TV recording. This is a standalone persistant process that runs seperately from the main Freevo preocess that you see on your TV or monitor. Record server listens on the network for client connections and will communicate to a client using XML-RPC. + +Please make sure that your XMLTV data is displaying correctly in the Freevo program guide before attempting to run the record server. This will save you problems in case there is something wrong with epg_xmltv.py or your XMLTV data. Since record_server.py must run outside of the main Freevo process you should use one of the scripts in the boot/ directory to help start it. The record_server scripts here need you to have the boot_config file placed in your /etc/freevo/ directory and edited to suit your system. The record_server script is an rc style start/stop script and can be placed in your /etc/init.d/ directory (or equivalent) but must be set to start/stop at the proper runlevels. That is outside the scope of this document. The record_server_init script is designed to run from the init process using your /etc/inittab file. There are instructions for doing this at the top of the record_server_init file. + +If you are not using the Freevo binary runtime and instead installed all of the Freevo dependancies yourself, make sure you have Twisted (http://www.twistedmatrix.com) installed as well. + + +'''Record server configuration:''' + +You must chose a recording plugin. The default plugin is generic_record and if you are using mencoder or any other external command to do your recording then this is the plugin for you. If, on the other hand, you are using a Hauppage WinTV PVR-250/350 then you can activate the ivtv_record plugin and it will do the recording work for you. Before using this card in Freevo please make sure that it is working properly and you have no driver problems. See http://ivtv.sourceforge.net for details. + +The recording server looks for a few items in your config: DIR_RECORD, RECORD_SCHEDULE, RECORD_SERVER_IP, and RECORD_SERVER_PORT. Please see frevo_config.py for details. Please be aware that record_server.py is a network application and your Freevo machine should not have wide open access from the internet without a firewall limiting what ports outsiders can connect to. + +If you are using the generic_record plugin (default) then you must have VCR_CMD configured to your liking. There is an example of this in freevo_config.py as well. + +In order to use the ivtv recording plugin have the following in your local_conf.py: + +{{{ +plugin.remove('tv.generic_record') +plugin_record = plugin.activate('tv.ivtv_record') +}}} + +Also for ivtv_record you may set some recording options: + +{{{ +IVTV_OPTIONS = { + 'input' : 4, + 'resolution' : '720x480', + 'aspect' : 2, + 'audio_bitmask' : 233, + 'bframes' : 3, + 'bitrate_mode' : 1, + 'bitrate' : 4000000, + 'bitrate_peak' : 4000000, + 'dnr_mode' : 0, + 'dnr_spatial' : 0, + 'dnr_temporal' : 0, + 'dnr_type' : 0, + 'framerate' : 0, + 'framespergop' : 15, + 'gop_closure' : 1, + 'pulldown' : 0, + 'stream_type' : 10, +} + +# Please see freevo_config.py for details. +}}} + +Once configured, and you would like to test the recording server, simply run ./record_server start (record_server script from the boot/ directory). Remember, those scripts rely on the boot_config file being in /etc/freevo/ and modified for your system. Once it is running you will have a log, either in /var/log/freevo or /tmp/freevo, called internal-record_server-0.log (0 is the uid of the user running it, 'root' in this case). The web interface or the main Freevo interface will let you know if the recording server is down. It will need to be running in order to schedule and record shows. + === Image Slideshows === ------------------------------------------------------- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code=104 _______________________________________________ Freevo-wikilog mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-wikilog
