Brian, for recording problems check your log file in /var/log/freevo/internal-record_daemon-0.log
to see if it gives you any info on whats going on.
I did, and I didn't see anything there. I don't know where those GLIBC errors were going; they got totally lost when running from cron.
A while ago I was getting the infamous glibc error, that prevented me from recording. Not sure if that problem was every fully resolved.
Apparently not; I had it, too.
import os os.environ['LD_PRELOAD'] = '' # Add this line to stop GLIBC_2.X preload errors
That seems to have done it. I think a cleaner bit of code would be del(os.environ['LD_PRELOAD'])
Thanks for the info, Rich. I've scheduled a couple of programs to test it out. :-)
This still doesn't solve the crux of my problem which is incorrect paths in the config files for the runtime tools. Out of the box, without mucking with /usr/local/freevo/freevo_config.py and changing the path to mencoder in the VCR_CMD variable, you can't record!
I don't mean to be hard on the Freevo developers. I think the project is off to a great start, but I also feel that that the RPMs and self-contained tarballs are misleading because, well, they're broken. The documentation's too sketchy and doesn't take the uninitiated from start to end without having to hit the mailing lists for help.
It seems like everyone else is absolutely raving about the simplicity of working with Freevo, so that's why I still think I'm missing something obvious. I'll try to go back and read the docs from the start and see if I can fill in the missinc pieces myself.
G'night, B
-- __ ____ / / / __/ Brian Lalor / _ \/__ \ [EMAIL PROTECTED] /_.__/____/ http://bravo5.org/
------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
