<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<blockquote type="cite"
cite="mid:CAPYw7P7j0yWQWF0TDFd-VuQTxXJ6rgsvKuFhyXc=exNBKZQmQw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_quote">
<div>Nope, your software can't do it.</div>
<div><br>
</div>
<div>Use ffmpeg's stereotools filter with
asendcmd. Supports runtime changing of
parameters.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>Thanks for suggestion! Yes, fully automatic panning
on variable length clips probably not easy to automate
in CinGG <br>
</div>
<div>(even in bath mode). But I opened said filter
(stereotools) and apparently I can set cingg plugin
keyframes for its internal parameters ..</div>
<div><br>
</div>
<div>I do not think we have timeline support for ff
filters, but does this system offer any advantage in
our case?<br>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div> Timeline and runtime changeable parameters are different
things, they are not same.</div>
<div><br>
</div>
<div>Timeline just disables/bypass processing in certain time
frames. While runtime parameters can be changed at any time
frame.</div>
<div>But parameters can also be slowly interpolated so that no
artifacts appear upon changes.</div>
</div>
</div>
</blockquote>
<p>The attached Windows bat file with comments represents the
present state of my solution to the requirements. While obtaining
the mid-point of the input audio file via a string of unix
commands is workable, I had really hoped that there would be some
global variable or macro providing the duration. I have not been
able to find it and having to invoke ffmpeg twice to get the job
done is not ideal.<br>
</p>
<p>I am happy that you pointed me in the direction of using the
ffmpeg executable, but as I can imagine scope creep, I am not
adverse to going back to my attempt to write the solution as a C
program if that would be the better way to obtain the duration(s)
of the input(s).</p>
<p>Thank you again.<br>
</p>
</body>
</html>