openpvr-devel Mailing List for OpenPVR (Page 3)
Brought to you by:
brian_j_murrell,
jfunk
Menu
▾
▴
openpvr-devel — Development of an Open PVR
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(12) |
Dec
(7) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(2) |
Feb
|
Mar
(28) |
Apr
(22) |
May
|
Jun
(19) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
(7) |
Dec
|
| 2003 |
Jan
|
Feb
(2) |
Mar
(5) |
Apr
|
May
(5) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
|
| 2004 |
Jan
(4) |
Feb
|
Mar
|
Apr
(7) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Brian J. M. <55d...@in...> - 2002-06-06 01:12:46
|
On Wed, Jun 05, 2002 at 06:42:45PM -0500, Monty Walls wrote: > =20 > Been playing with mp1e, first had to patch the v4l code (patch is turned = in). How come? You want to use v4l2 anyway. Much better a/v syncing results. > Still looking at the differences for comparable picture quality (overhead= /filesize). =20 Well, MPEG1 is definately not as good at compression as divx/mpeg4. > What are you using for commandline options? Lemme see what my record (in cvs) script barfs out... $ mp1e -vv -n 39200 -s 640x480 -b 5000 -f 29.97 -a 0 -B 128 -p /dev/dsp1 -S= 32 -x /dont/set/mixer> "/video/test.mpeg" > From what I can tell I'll have to=20 > run a seperate mpeg2divx pass to get decent file sizes (1hr =3D 600-700mb= ). Yes. I record with mp1e at 5Mb/s bitrate and usually don't do anything with the resulting ~1.1GB/hr file other than watch it and delete it but occaisonally (too occaisonally :-) I run out of space and use mencoder to re-encode to mpeg4 at at bitrate of 1.25Mb/s. But I am a stickler for picture quality. I don't want to see pixelization. :-) b. --=20 Brian J. Murrell |
|
From: Monty W. <mw...@ca...> - 2002-06-05 23:48:16
|
On Wed, 5 Jun 2002 18:06:22 -0400 "Brian J. Murrell" <803...@in...> wrote: > On Wed, Jun 05, 2002 at 04:54:55PM -0500, Monty Walls wrote: > > > > seems to work ok. > > Cool. > > > I have found a nice cheat on recording - record at 640x240, then use a vertical > > line doubler in outputing it to screen (mplayer can). Since 640x480 is interlaced > > and requires more horsepower than I have for either divx or mpeg, but I can > > manage 640x240 realtime. > > You should really try mp1e then. It can do 640x480 (with a linear > interpolation between fields -- drooling for mpeg2 realtime as > efficient as mp1e) at about 30-40% of my AMD TB 800. 640x480 eats my > CPU for breakfast trying any of the divx encoders. > > I don't like .avi anyway. It's not seekable until the file is closed. > Been playing with mp1e, first had to patch the v4l code (patch is turned in). Still looking at the differences for comparable picture quality (overhead/filesize). What are you using for commandline options? From what I can tell I'll have to run a seperate mpeg2divx pass to get decent file sizes (1hr = 600-700mb). > b. > > -- > Brian J. Murrell > > -- -Monty Walls (mw...@ca...) - MIS, Oklahoma Tax Commission - - My opinions are my own, my employer knows nothing about it. |
|
From: Brian J. M. <803...@in...> - 2002-06-05 22:07:12
|
On Wed, Jun 05, 2002 at 04:54:55PM -0500, Monty Walls wrote: >=20 > seems to work ok. Cool. > I have found a nice cheat on recording - record at 640x240, then use a ve= rtical > line doubler in outputing it to screen (mplayer can). Since 640x480 is i= nterlaced > and requires more horsepower than I have for either divx or mpeg, but I c= an > manage 640x240 realtime. You should really try mp1e then. It can do 640x480 (with a linear interpolation between fields -- drooling for mpeg2 realtime as efficient as mp1e) at about 30-40% of my AMD TB 800. 640x480 eats my CPU for breakfast trying any of the divx encoders. I don't like .avi anyway. It's not seekable until the file is closed. b. --=20 Brian J. Murrell |
|
From: Monty W. <mw...@ca...> - 2002-06-05 22:00:26
|
On Wed, 5 Jun 2002 17:45:33 -0400 "Brian J. Murrell" <051...@in...> wrote: > On Wed, Jun 05, 2002 at 04:37:45PM -0500, Monty Walls wrote: > > > > I just added the merged low-latency+preempt patches to my rh7.[23] systems > > to cut drops while doing record to divx (directly). > > And how well does it work? How much improvement? > seems to work ok. I was having drop problems with vcr (uses avifile library), which was caused by vcr's internal code and the OS's drops during disk i-o (both are handled now, grrr). vcr really doesn't do much buffering so if the OS hiccups, it use to drop frames... Unfortunately most of the improvement is probably in my code rewrites since the improvements also work without the RT kernel. I haven't had any crashes yet from it (knock on wood...), but I've only been using it about a week. So if you aren't having drop problems I wouldn't bother, it's probably in the application code (at least based on my playing). I have found a nice cheat on recording - record at 640x240, then use a vertical line doubler in outputing it to screen (mplayer can). Since 640x480 is interlaced and requires more horsepower than I have for either divx or mpeg, but I can manage 640x240 realtime. -- -Monty Walls (mw...@ca...) - MIS, Oklahoma Tax Commission - - My opinions are my own, my employer knows nothing about it. |
|
From: Brian J. M. <051...@in...> - 2002-06-05 21:45:51
|
On Wed, Jun 05, 2002 at 04:37:45PM -0500, Monty Walls wrote: >=20 > I just added the merged low-latency+preempt patches to my rh7.[23] systems > to cut drops while doing record to divx (directly). And how well does it work? How much improvement? b. --=20 Brian J. Murrell |
|
From: Monty W. <mw...@ca...> - 2002-06-05 21:43:17
|
On Wed, 5 Jun 2002 16:38:08 -0400 "Brian J. Murrell" <6df...@in...> wrote: > On Wed, Jun 05, 2002 at 02:24:28PM -0600, Mark Lane wrote: > > I was going to suggest that you might want to consider using the preemptive > > kernel patches with this project. They will help with recording. > > They might. I have too much on my plate to be doing kernel > maintenance as well however and the lack of the the patches does not > seem to be too-ill-affecting when I record with mp1e. > > It will be interesting to try when they become mainstream (or in my > distro's kernel anyway). > I just added the merged low-latency+preempt patches to my rh7.[23] systems to cut drops while doing record to divx (directly). I've built them as an RPM set (including the normal 2.4.18-4 RedHat patches). So if someone wants to play with it, let me know. #include <std.disclaimer.h> -- -Monty Walls (mw...@ca...) - MIS, Oklahoma Tax Commission - - My opinions are my own, my employer knows nothing about it. |
|
From: Brian J. M. <e0e...@in...> - 2002-06-05 20:56:39
|
On Wed, Jun 05, 2002 at 03:38:43PM -0500, Steve Headley wrote: > Have there been any new developments. Nothing really new on my end. I am waiting for some pieces to come together so I can start on the GUI for the playback part of my PVR. I really want to use DirectFB as it supports transparency (think of an OSD over the playback) and MPlayer supports DirectFB as well. What I am waiting for is DirectFB to support vsync flipping compatible with how MPlayer wants to do it and I need to build a GTK+ 2.03 for DirectFB. I started that before but there were problems with my build tools on my distro. > Anything that needs help. Well, I guess there is always something to do. I like the functionality of the scheduler right now although it's still rough. > Haven't > heard about anything going on in a while Well just scratchin' itches as they get itchy. :-) The latest itch is a GUI. I got LIRC working with my box so I can use my remote to control MPlayer. Very nice! :-) b. --=20 Brian J. Murrell |
|
From: Steve H. <she...@om...> - 2002-06-05 20:43:40
|
Have there been any new developments. Anything that needs help. Haven't
heard about anything going on in a while
Steven H.
|
|
From: Brian J. M. <6df...@in...> - 2002-06-05 20:38:29
|
On Wed, Jun 05, 2002 at 02:24:28PM -0600, Mark Lane wrote: > I was going to suggest that you might want to consider using the preempti= ve=20 > kernel patches with this project. They will help with recording. They might. I have too much on my plate to be doing kernel maintenance as well however and the lack of the the patches does not seem to be too-ill-affecting when I record with mp1e. It will be interesting to try when they become mainstream (or in my distro's kernel anyway). b. --=20 Brian J. Murrell |
|
From: Mark L. <ma...@ha...> - 2002-06-05 20:25:22
|
I was going to suggest that you might want to consider using the preemptive kernel patches with this project. They will help with recording. -- Mark Lane Hard Data Ltd. mailto:ma...@ha... Telephone: 01-780-456-9771 FAX: 01-780-456-9772 11060 - 166 Avenue Edmonton, AB, Canada T5X 1Y3 http://www.harddata.com/ --> Ask me about our Affordable Alpha Systems! <-- |
|
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 |
|
From: Steve H. <she...@om...> - 2002-04-17 20:28:22
|
I have built the newly CVS commited file changes. I would like to run the binaries. What do I need to do? Are their any instructions? Not much info in your source code. How do I make the code do something? |
|
From: Brian J. M. <1b3...@in...> - 2002-04-15 19:51:33
|
[ Just an item of administrivia: can you please put a subject on your mail submissions to the list. It helps the digest readers as well as those looking through the archive looking for answers. Thanx. ] On Mon, Apr 15, 2002 at 02:10:05PM -0500, Steve Headley wrote: > I was trying to compile the source and received the following errors. > what am I missing: >=20 >=20 > gcc -g -I/usr/include/glib-1.2 -I/usr/lib/glib/include > -I/usr/include/gnome-xml -Wall -g -lxml -lz -lglib -ldb-3.3 schedule.c > -o schedule > schedule.c: In function `compareEpisodes': > schedule.c:198: warning: value computed is not used > schedule.c: In function `comparePrograms': > schedule.c:247: warning: value computed is not used > schedule.c: In function `compareWanteds': > schedule.c:338: warning: value computed is not used > schedule.c: In function `compareShowings': > schedule.c:546: warning: value computed is not used These are all warnings which do not show with gcc 3.0.4. The fact that they are warning is an error IMMHO. gcc seems to have corrected that in later versions. In any case, it is a warning and can be ignored. > schedule.c: In function `main': > schedule.c:1313: parse error before `*' > schedule.c:1326: `prev_showing' undeclared (first use in this function) > schedule.c:1326: (Each undeclared identifier is reported only once > schedule.c:1326: for each function it appears in.) > schedule.c:1329: `at_command' undeclared (first use in this function) > schedule.c:1330: `seendb_command' undeclared (first use in this function) > make: *** [schedule] Error 1 Interesting. gcc 3.0.4 allows declarations in the middle of blocks like C++ allows. I made the declarations in the middle of the block in error and have moved them to the top of the block. rsync cvs and try again. b. --=20 Brian J. Murrell |
|
From: Brian J. M. <77e...@in...> - 2002-04-15 19:40:22
|
On Mon, Apr 15, 2002 at 11:15:55AM -0500, Steve Headley wrote: > I am new at this open source design thing. I was wondering if use cases a= re > something that might be considered for use in design of the PVR system. The only use case right now is what I do in my living room. :-) This is the best use case of all however as it makes sure that what is needed is implemented. Think of this as the ultimate of needs anaylsis, solution design, implementation and actual use, because it's all being done by the same party. Who better knows what the users want than the users, and who better to develop what the user needs than the user? Of course, the needs will expand beyond my own, at which point some users will voice their wants and needs and they can then be evaluated. This process is more reactionary than proactive. We are not going to try to guess what the users need, nor will we be doing surveys of the userbase or anything like that. We will wait for them to tell us. Of course this is much different than the "formal" process in which a company gets paid to do proactive anylsis and/or implemenation, but we are not a company and not getting paid. We meet our own requirements first. > There seems to be a lot of information categorized in different places. Can you give an example of what kind information you mean? > If > we were design with use cases or something else that would diagram all the > pieces working together and I would be better able to understand the syst= em > as a whole. I think what you will find is that the system will grow from the core out. The core might need to be redesigned after some time to meet expanding needs but that's the nature of free software development, it scratches the itch of the day. b. --=20 Brian J. Murrell |
|
From: Brian J. M. <f4a...@in...> - 2002-04-15 19:32:30
|
On Mon, Apr 15, 2002 at 10:30:51AM -0500, Steve Headley wrote: > > can we incorporate some technology that allows video on demand via > > INTERNET, Video LAN technology? How could we use GET methods to provide > > the same functionality?=20 Well, from the usage level, if you want to see how it would work: $ mplayer http://www.example.com/test.mpeg Is that what you mean? b. --=20 Brian J. Murrell |
|
From: Steve H. <she...@om...> - 2002-04-15 19:13:17
|
I was trying to compile the source and received the following errors. what am I missing: gcc -g -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/include/gnome-xml -Wall -g -lxml -lz -lglib -ldb-3.3 schedule.c -o schedule schedule.c: In function `compareEpisodes': schedule.c:198: warning: value computed is not used schedule.c: In function `comparePrograms': schedule.c:247: warning: value computed is not used schedule.c: In function `compareWanteds': schedule.c:338: warning: value computed is not used schedule.c: In function `compareShowings': schedule.c:546: warning: value computed is not used schedule.c: In function `main': schedule.c:1313: parse error before `*' schedule.c:1326: `prev_showing' undeclared (first use in this function) schedule.c:1326: (Each undeclared identifier is reported only once schedule.c:1326: for each function it appears in.) schedule.c:1329: `at_command' undeclared (first use in this function) schedule.c:1330: `seendb_command' undeclared (first use in this function) make: *** [schedule] Error 1 |
|
From: Steve H. <she...@om...> - 2002-04-15 18:44:38
|
My confusion. I was able to checkout. >FROM: Brian J. Murrell >DATE: 04/15/2002 09:31:39 >SUBJECT: RE: [Openpvr-devel] problems gettig into CVS --LGr9gtkSK9ARF7Ax Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 15, 2002 at 10:43:26AM -0500, Steve Headley wrote: > I get the following when trying to access cvs: >=20 > root@linux:/openpvr > cvs > -d:pserver:<EMAIL: PROTECTED>:/cvsroot/openpvr login > (Logging in to <EMAIL: PROTECTED>) > CVS password:=20 >What are you putting in here when it asks for the password? > cvs login: authorization failed: server cvs.openpvr.sourceforge.net rejec= ted > access to /cvsroot/openpvr for user anonymous b. --=20 Brian J. Murrell --LGr9gtkSK9ARF7Ax -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see <http://www.gnupg.org> iD8DBQE8uwBrl3EQlGLyuXARAs3oAKDZf5LnK9V+hyKNw8azX2DEd24YnQCeNCYL HaZNKpCFgUn5hIoo4tdA3EU= =1Alq -----END PGP SIGNATURE----- --LGr9gtkSK9ARF7Ax-- _______________________________________________ Openpvr-devel mailing list <EMAIL: PROTECTED> https://lists.sourceforge.net/lists/listinfo/openpvr-devel |
|
From: Brian J. M. <ce0...@in...> - 2002-04-15 16:31:59
|
On Mon, Apr 15, 2002 at 10:43:26AM -0500, Steve Headley wrote: > I get the following when trying to access cvs: >=20 > root@linux:/openpvr > cvs > -d:pserver:ano...@cv...:/cvsroot/openpvr login > (Logging in to ano...@cv...) > CVS password:=20 What are you putting in here when it asks for the password? > cvs login: authorization failed: server cvs.openpvr.sourceforge.net rejec= ted > access to /cvsroot/openpvr for user anonymous b. --=20 Brian J. Murrell |
|
From: Steve H. <she...@om...> - 2002-04-15 16:19:00
|
I am new at this open source design thing. I was wondering if use cases are
something that might be considered for use in design of the PVR system.
There seems to be a lot of information categorized in different places. If
we were design with use cases or something else that would diagram all the
pieces working together and I would be better able to understand the system
as a whole.
Steven H.
|
|
From: Steve H. <she...@om...> - 2002-04-15 15:46:30
|
I get the following when trying to access cvs: root@linux:/openpvr > cvs -d:pserver:ano...@cv...:/cvsroot/openpvr login (Logging in to ano...@cv...) CVS password: cvs login: authorization failed: server cvs.openpvr.sourceforge.net rejected access to /cvsroot/openpvr for user anonymous |
|
From: Steve H. <she...@om...> - 2002-04-15 15:33:52
|
> can we incorporate some technology that allows video on demand via > INTERNET, Video LAN technology? How could we use GET methods to provide > the same functionality? > > -----Original Message----- > From: Steve Headley > Sent: Friday, April 12, 2002 12:38 PM > To: 'ope...@li....' > Subject: Switching Protocol > > has anyone thought about incorporating SIP protocol in the PVR? That way > we can issue signaling message from across the INTERNET. It make for a > more innovative approach. > > > Steven H. |
|
From: Brian J. M. <e87...@in...> - 2002-04-14 06:40:58
|
OK, I just commited a big change to schedule.c and the "record" script in CVS. "record" was just updated to reflect what I do here. Defaults, encoder of choice etc. Still very "localized" to my environment. Needs an external config file of some sort badly. "schedule" has seen the conversion of the "seen" database from an XML file which had to be maintained manually to a Berkeley DB database that is updated by the command spit out from schedule to schedule programs. This means you can run schedule, use the commands it gives you to schedule programming and then run schedule again and it will remember what has already been scheduled (and not try to reschedule it) and not try to schedule something in the same timeslot as perviously. This is a big improvement over the way it used to work, IMO. schedule still does not really schedule anything itself but rather gives you the command that you can enter to affect the recording via "at". Note the "seenput" commands after the "at" command that need to be entered at the shell prompt right after the "at" command. That is what tells the DB what is scheduled to record. I am sure I have broken something in all those changes, so let me know what doesn't work (if there is actually anyone out there playing with this stuff :-). Cheers, b. --=20 Brian J. Murrell |
|
From: Brian J. M. <352...@in...> - 2002-04-12 21:14:29
|
On Fri, Apr 12, 2002 at 03:30:14PM -0500, Steve Headley wrote: > here are good link that defines SIP: >=20 > http://www.cs.columbia.edu/sip/faq/cache/2.html >=20 > http://www.radvision.com/papers/C1_What_is_SIP.html >=20 > basically, it is a signalling protocol that allows setup controlling and > tear down of multimedia sessions. It is popular in the IP telephony arena, > but could be used by any session that wants to do signalling control. The > way that SIP could be used for our purposes is to signal across the INTER= NET > that you want a particular PVR stream to reach you at a particular web > address. You would be able to signal the PVR via the web to have the stre= am > come to you at a different location. Other uses I am sure will be present= ed > by others. Just a thought. OK, I think I get it. But I am not sure how it relates to content delivery in the case of something like a PVR (or any other sort of "video on demand" aplication. ISTM that SIP is much more useful in the event that two parties want to contact one another, real-time. I don't really see video-on-demand as needing much more sophistication than an HTTP GET. Please, enlighten me if there is an aspect that I am missing. b. --=20 Brian J. Murrell |
|
From: Steve H. <she...@om...> - 2002-04-12 20:33:20
|
here are good link that defines SIP: http://www.cs.columbia.edu/sip/faq/cache/2.html http://www.radvision.com/papers/C1_What_is_SIP.html basically, it is a signalling protocol that allows setup controlling and tear down of multimedia sessions. It is popular in the IP telephony arena, but could be used by any session that wants to do signalling control. The way that SIP could be used for our purposes is to signal across the INTERNET that you want a particular PVR stream to reach you at a particular web address. You would be able to signal the PVR via the web to have the stream come to you at a different location. Other uses I am sure will be presented by others. Just a thought. Steven H. -----Original Message----- From: ope...@li... [mailto:ope...@li...] Sent: Friday, April 12, 2002 3:05 PM To: ope...@li... Subject: Openpvr-devel digest, Vol 1 #20 - 2 msgs Send Openpvr-devel mailing list submissions to ope...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/openpvr-devel or, via email, send a message with subject or body 'help' to ope...@li... You can reach the person managing the list at ope...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Openpvr-devel digest..." Today's Topics: 1. Switching Protocol (Steve Headley) 2. Re: Switching Protocol (Brian J. Murrell) --__--__-- Message: 1 From: Steve Headley <she...@om...> To: "'ope...@li....'" <ope...@li....> Date: Fri, 12 Apr 2002 12:37:40 -0500 Subject: [Openpvr-devel] Switching Protocol has anyone thought about incorporating SIP protocol in the PVR? That way we can issue signaling message from across the INTERNET. It make for a more innovative approach. Steven H. --__--__-- Message: 2 Date: Fri, 12 Apr 2002 13:57:07 -0400 To: "'ope...@li....'" <ope...@li...> Subject: Re: [Openpvr-devel] Switching Protocol From: "Brian J. Murrell" <caf...@in...> --332CIdRmeZdukXAd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 12, 2002 at 12:37:40PM -0500, Steve Headley wrote: > has anyone thought about incorporating SIP protocol in the PVR? That way = we > can issue signaling message from across the INTERNET. It make for a more > innovative approach. I have heard of the acronym (SIP) in the context of digital media but I have not read much more than that. Can you point me to a good (better than RFC, that I could probably find quite easily) description or give a brief description of what SIP is? b. --=20 Brian J. Murrell --332CIdRmeZdukXAd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8tx/zl3EQlGLyuXARArZWAKD1wUTBc+/yjE7W6jCOIirrAMurpwCeO8O7 A8bEwuwxBmLNhJf/hhPjEu0= =CYAS -----END PGP SIGNATURE----- --332CIdRmeZdukXAd-- --__--__-- _______________________________________________ Openpvr-devel mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/openpvr-devel End of Openpvr-devel Digest |
|
From: Billy B. <ve...@du...> - 2002-04-12 20:09:17
|
Brian J. Murrell (caf...@in...): > On Fri, Apr 12, 2002 at 12:37:40PM -0500, Steve Headley wrote: > > has anyone thought about incorporating SIP protocol in the PVR? That > > way we can issue signaling message from across the INTERNET. It make > > for a more innovative approach. > > I have heard of the acronym (SIP) in the context of digital media but > I have not read much more than that. Can you point me to a good > (better than RFC, that I could probably find quite easily) description > or give a brief description of what SIP is? http://www.cs.columbia.edu/sip/ is the main reference. To note, I wrote one of the first open source SIP implementations, my stack is over here: http://div8.net/dissipate/ I was also a co-author of an I-D on SIP for remote device control. I could also probably write a SIP client for a PVR in not too much time. :) The question is really would it be useful. SIP is intended for signalling of media sessions, so you might want to use it for doing the equivalent of 'videolan', or you could use it as a remote device control protocol, but I'm not sure if that's really needed or interesting. It's also emerging as a popular choice for a standard IM protocol. -- Billy Biggs ve...@du... |
