Ok, this is what I did and what did minor problems I hit. the .33 version of XMLTV installed to a diferent directory than previous versions. So I had to search for all the old xmltv libs and replace the the old with the new ones.
After executing the command freevo tv_grab , the command would never finish and tv_sort would not run either. I did modify the local_config.py to use the new _dd version. The standard grabber for getting the channel ID's does not work on the new version of the TV.xml.The channels do not match the id's. I just went and manually got each ID out of the file. To get the new ID's to be read by the webserver part of freevo I had to reboot. Restarting the webserver and record server did not work. I run the tv_grab_na_dd and tv_sort manually now. Do to freevo tv_grab command never finishing. If anyone wants more detial just ask. Wes --- StormeRider <[EMAIL PROTECTED]> wrote: > On Mon, 2004-05-24 at 04:00, StormeRider wrote: > > tv_grab_na just died and I'm scrambling to get > tv_grab_na_dd working. > > After messing with a few perl dependancies I got > it installed and > > seemingly pulling down correct data from zap2it, > after registering and > > all that. > > > > Problem I'm facing now is that tv_grab_na_dd has > pulled down the data > > and saved it to /tmp/TV.xml like normal (I pull a > week at a time, so no > > point to doing the whole timestamp part...), but > Freevo doesn't seem to > > recognize it. The web interface still says listing > expire in 0 hours, > > the TV Guide is blank, etc. > > *sigh* Figures that it would hit me that the channel > IDs changed as a > result of the grabber conversion after I sent out > the mail... ah well. > For anyone else who might miss that, and stumble > across this in the > archives... you will have to regenerate the > TV_CHANNEL lines in > local_conf.py. > > I did that and it still didn't work... then after > searching around some > more I came across the --old-chan-id parameter... > re-pulled the listings > with that, and everything looks good :) > > Not sure if it was the perl script in the archives > that I used that > necessitates the old chan id setting, or if it's > just how freevo > interprets it, but that was my experience... > hopefully it'll help anyone > else also affected by the cutover. > > --Nathan > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the > market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the > exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Freevo-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/freevo-users ===== __________________________________ Do you Yahoo!? Yahoo! Domains � Claim yours for only $14.70/year http://smallbusiness.promotions.yahoo.com/offer ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
