Re: dvcont rewind - any way to tell when done other than looping on 'dvcont status' exit status?

Dan Dennedy <[email protected]> Mon, 26 Sep 2011 22:22:05 -0700
Newsgroups gmane.comp.video.kino.devel
Message-ID <CABBVo1neHsS2nZZfWzVb01sRGj1_+xEr74JHEtpE2XwHoXrRCw@mail.gmail.com>
On Mon, Sep 26, 2011 at 8:19 PM, david <[email protected]> wrote:
> Dan, All,
>
> =A0 dvcont works fine, but it certainly isn't serial in processing comman=
ds. From
> the man page, 'dvcont <command1> [ <command2> ... ]', I thought 'dvcont r=
ewind
> eject' would rewind -- then eject. But when I saw the tape eject immediat=
ely, I
> knew that was a no-go.
>
> =A0 It seems simple "hey dummy, just look at the camcorder", but the camc=
order is
> hooked to a remote box and dvgrab/dvcont operations are done over ssh so =
knowing
> when the rewind is done is something more than just looking at the camcor=
der.
> What I've done is just run dvcont status and check for the "Winding rever=
se" or
> "Winding stop" status to determine when the rewind completes:
>
> (stat=3D$(dvcont status); while [[ $stat !=3D "Winding stop" ]]; do sleep=
 10;
> stat=3D$(dvcont status); done)
>
> =A0 Works fine, but if there is an easier way, I'd appreciate a suggestio=
n. Thanks.

There is no easier way other than to modify the dvcont C code or
dvgrab C++ code to your needs. Also, you would basically end up doing
the same thing in low level code - polling the transport status.

> --
> David C. Rankin, J.D., P.E.

---------------------------------------------------------------------------=
---
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1