Re: [Openpvr-devel] newly commited files built. But now what??
Brought to you by:
brian_j_murrell,
jfunk
From: Brian J. M. <24d...@in...> - 2002-04-17 22:13:39
|
On Wed, Apr 17, 2002 at 03:25:17PM -0500, Steve Headley wrote: > I have built the newly CVS commited file changes. I would like to run the > binaries. Excellent! > What do I need to do? The $50,000,000 question. Well, the $3 one anyway. :-) I will try to summarize here. Maybe I can turn this into a README some day soon. > Are their any instructions? Not much info in > your source code. How do I make the code do something?=20 All good questions. First thing you need is some XMLTV data. You need to grab the xmltv project from http://sourceforge.net/projects/xmltv/. I would suggest grabbing the cvs version as it's quite stable. Once you have xmltv built, installed and configured, grab some listings. I cheat a bit and run xmltv from it's build dir, but you should probably just "make intall" it and use it as directected. I grab 14 days worth of data with: $ mv /tmp/tv_data.xml.gz /tmp/tv_data.old.xml.gz; (cd /usr/src/xmltv; perl = -I blib/lib blib/script/tv_grab_na --days 14) | gzip -9 >/tmp/tv_data.xml.gz Which, if you "make install" xmltv properly should translate to: $ mv /tmp/tv_data.xml.gz /tmp/tv_data.old.xml.gz; tv_grab_na --days 14 | gz= ip -9 >/tmp/tv_data.xml.gz That will give you 14 days worth of programming in /tmp/tv_data.xml.gz. Next thing to do is make up a file of programs you want to schedule. The file is /tmp/wanted_programs.xml.gz and has the following format: <?xml version=3D"1.0" encoding=3D"ISO-8859-1" standalone=3D"yes"?> <!DOCTYPE my_programs SYSTEM "xmltv.dtd"> <program> <item title=3D"ER"> <score>60</score> </item> <item title=3D"CSI: Crime Scene Investigation"> </item> <item title=3D"Frasier"> <score>60</score> </item> <item title=3D"The Practice"> </item> <item title=3D"The West Wing"> </item> </program> Put in as many programs as you wish to schedule. Look in /tmp/tv_data.xml.gz for program titles. At this point, you should be able to run schedule with: $ .../path/to/schedule You will get some debug but at the end you will see a bunch of commands that you can enter at a shell prompt to schedule programs. For example: $ /usr/src/openpvr/schedule =2E.. Conflicts: Thu Apr 18 20:30 30m 5 WSTM: Friends: The One Where Chandler Takes a Bath s= c=3D50 sch=3Dno Fri Apr 19 20:00 60m 7 WWNY: CSI: Crime Scene Investigation: $35K O.B.O. sc= =3D50 sch=3Dno Mon Apr 22 22:00 60m 7 WWNY: First Monday: 1019527200 sc=3D25 sch=3Dno Wed Apr 24 20:00 60m 5 WSTM: Ed: 1019692800 sc=3D25 sch=3Dno =2E.. at 19:30 18.04.02 <<EOF /usr/src/openpvr/record --end "epoch 1019174399" --channel "3 CIIIOT" "Frie= nds: The One Where Joey Dates Rachel"; /usr/src/openpvr/seenput "Friends" "= The One Where Joey Dates Rachel"; /usr/src/openpvr/record --end "epoch 1019= 177999" "Survivor: Marquesas: Jury's Out"; /usr/src/openpvr/seenput "Surviv= or: Marquesas" "Jury's Out"; /usr/src/openpvr/record --end "epoch 101918159= 9" --channel "6 CJOH" "CSI: Crime Scene Investigation: Burked"; /usr/src/op= enpvr/seenput "CSI: Crime Scene Investigation" "Burked";=20 EOF /usr/src/openpvr/seenput "Friends" "The One Where Joey Dates Rachel" 101917= 2600 1800 "3 CIIIOT" /usr/src/openpvr/seenput "Survivor: Marquesas" "Jury's Out" 1019174400 3600= "3 CIIIOT" /usr/src/openpvr/seenput "CSI: Crime Scene Investigation" "Burked" 10191780= 00 3600 "6 CJOH" at 13:00 19.04.02 <<EOF /usr/src/openpvr/record --end "epoch 1019237399" --channel "54 PRIMETV" "Al= l in the Family: Gloria Poses in the Nude"; /usr/src/openpvr/seenput "All i= n the Family" "Gloria Poses in the Nude"; /usr/src/openpvr/record --end "ep= och 1019239199" "All in the Family: Archie in the Lock-Up"; /usr/src/openpv= r/seenput "All in the Family" "Archie in the Lock-Up";=20 EOF /usr/src/openpvr/seenput "All in the Family" "Gloria Poses in the Nude" 101= 9235600 1800 "54 PRIMETV" /usr/src/openpvr/seenput "All in the Family" "Archie in the Lock-Up" 101923= 7400 1800 "54 PRIMETV" at 20:00 19.04.02 <<EOF /usr/src/openpvr/record --end "epoch 1019264399" --channel "6 CJOH" "The Am= azing Race 2: I'm Gonna Throw Up on Phil's Shoes"; /usr/src/openpvr/seenput= "The Amazing Race 2" "I'm Gonna Throw Up on Phil's Shoes"; /usr/src/openpv= r/record --end "epoch 1019267999" --channel "7 WWNY" "First Monday: Strip S= earch"; /usr/src/openpvr/seenput "First Monday" "Strip Search";=20 EOF /usr/src/openpvr/seenput "The Amazing Race 2" "I'm Gonna Throw Up on Phil's= Shoes" 1019260800 3600 "6 CJOH" /usr/src/openpvr/seenput "First Monday" "Strip Search" 1019264400 3600 "7 W= WNY" =2E.. First thing to notice is the "Conflicts:". These are the programs that are running in the same over overlapping timeslot as another program in which case neither could be rescheduled to deal with the conflict. If you have these frequently, you need to either: a) watch the program listed in the Conflicts: section when it is showing b) videotape it (yuck, our goal is to obsolete video tape) c) get a second (or third) tuner card in your PVR (assuming you have the disk and/or CPU to record more than one program at once) and enhance schedule to know how to schedule multiple devices rather than the single that it understands currently d) miss the conflict and get it next time 'round (assuming it will be repeated) Second thing to notice is the shell commands to actually schedule the programming. Each group starts with an "at ..." and ends with some ".../seenput" commands. The "at" commands schedules at jobs to do the recordings. The seenput commands right after the at command updates the seen database to let "schedule" know that it's been scheduled so that a subsequent run of "schedule" will not try to reschedule the program or try to schedule the timeslot. I typically only run the at/seenput commands for the next 24 hours on the belief that the xmltv programming schedule might change to resolve some conflicts that are happening tomorrow, the next day and so forth. You might want to "preload" your seen database so that you don't get (say) the last 7 years worth of Friends episodes in syndication. I find the following website very handy for that: http://epguides.com/ although I don't yet have a tool to automate it. You can populate the seen database with previously seen programs with: $ .../seenput "<title>" "<sub-title>" Give that a whirl and let me know how it goes. It is likely I forgot something so let me know if you get stuck anywhere. b. --=20 Brian J. Murrell |