Re: [Openpvr-devel] Perl "record" script: mp1e doesn't stop??
Brought to you by:
brian_j_murrell,
jfunk
From: Brian J. M. <e9e...@in...> - 2002-07-14 05:33:50
|
On Mon, Jul 08, 2002 at 01:39:59AM -0400, Alan Murrell wrote: > Hello, Hi, > I am playing with mp1e using the Perl "record" script > (running it manually for now; will play with doing > scheduled recordings when I'm happy with the output), Cool. > and when I specify a --end time, it doesn't stop when > that time rolls around around; I have to kill the > process to stop it. I have tried specifying the --end > option in both 24hr time format (yes, my system time > is correct) and in seconds. >=20 > Here is the mp1e command it is running after I put > 'record --channel 45 --end <time/sec> test_file': Please! When you give a command line and it's output and complain that "it's not working", _do_not_ edit the command line. In your above command, you removed the _most_ useful (and only important) part of the command with your "<time/sec>" instead of putting in the value you really used. The time you ran the command would also have been useful. Please provide the command line and _all_ of it's output (up until mp1e starts writing status lines anyway) of some samples of: $ date; record --channel 45 --end <time/sec> test_file > --- output --- > v4lctl setchannel "45"; v4lctl bright 40000; v4lctl > contrast 30000; v4lctl hue 32768; v4lctl color 37500; > mp1e -vv -n 36503 Did you read the mp1e manpage when trying to debug this? -n <value> is the number of seconds to record. As you can see, whatever you put into "<time/sec>" was calculated to be 10.139722 (36503 / 60 / 60) hours long. Knowing the time you ran the command and the value of "<time/sec>" would help in debugging. > When I look at the coding, there doesn't seem to be > anything in the options for mp1e which specifies an > end time. -n <seconds> > Is it because I'm running it manually > (i.e., if I were to do cut and paste the output from > the schedule program into my console to put a schedule > into 'at', would it start and stop properly? Nope. > One other thing: at first, everytime I tried running > the 'record' script manually with mp1e, it would > immediately exit (bringing me back to the command > line). It *looked* like it was trying to find mp1e in > /tmp (i.e., /tmp/mp1e), so I commented the '/tmp' part > out, and seems to have worked quite nicely > (presumably, anyway; I still have to wait to see what > the test output files look like). Yeah, more "local" hard coding. I really do need to put some "autoconf" smarts into the openpvr code in general. b. --=20 Brian J. Murrell |