On Wed, 11 Dec 2013, Tobias Boege wrote:
> On Wed, 11 Dec 2013, John Rose wrote:
> > Tobias,
> >
> > Thank you for your reply.
> >
> > The reason for my using "-f x11grab" as one parameter (rather than 2
> > parameters of "-f" & "x11grab") to the Exec command is that I was
> > thinking of that
On Wed, 11 Dec 2013, John Rose wrote:
> Tobias,
>
> Thank you for your reply.
>
> The reason for my using "-f x11grab" as one parameter (rather than 2
> parameters of "-f" & "x11grab") to the Exec command is that I was
> thinking of that string as being one parameter to ffmpeg. It would help
Tobias,
Thank you for your reply.
The reason for my using "-f x11grab" as one parameter (rather than 2
parameters of "-f" & "x11grab") to the Exec command is that I was
thinking of that string as being one parameter to ffmpeg. It would help
if the documentation had an Exec example with these
On Wed, 11 Dec 2013, Tobias Boege wrote:
> On Wed, 11 Dec 2013, John Rose wrote:
> > Tobias,
> >
> > Thanks for your example. I've now got the Exec's termination working OK.
> > Below is an extract from my code:
> > Private aExec As String[]
> > Private sOutput As String
> > Private hffmpeg As Pr
On Wed, 11 Dec 2013, John Rose wrote:
> Tobias,
>
> Thanks for your example. I've now got the Exec's termination working OK.
> Below is an extract from my code:
> Private aExec As String[]
> Private sOutput As String
> Private hffmpeg As Process
> hffmpeg = Exec aExec Wait For Input Output As "ff
Tobias,
Thanks for your example. I've now got the Exec's termination working OK.
Below is an extract from my code:
Private aExec As String[]
Private sOutput As String
Private hffmpeg As Process
hffmpeg = Exec aExec Wait For Input Output As "ffmpegMessages"
Public Sub ffmpegMessages_Read()
Dim
On Tue, 10 Dec 2013, Tobias Boege wrote:
> I attached a program that stops ffmpeg printing "q" to it. Hope it helps...
... and here comes the attachment.
ffmpeg-print-q-0.0.1.tar.gz
Description: Binary data
--
Rapidly tr
On Tue, 10 Dec 2013, John Rose wrote:
> Tobias,
> I just realised that a post that I made on the 'Line continuation'
> thread is better in this thread. The details are:
> I liked your ideas of:
> Dim aExec As String[]
> Dim sRes As String
> aExec = ["cat", "/proc/meminfo"]
> ' Use aExec.Add() to a
Right -- my fault! When I suggested the example "/proc/meminfo", I was just
looking for any script example, to discuss using string variables in SHELL
and EXEC for very long command strings. Tobias provided the coolest option
to do that job. But you've pointed out that I could have chosen a bett
Le 10/12/2013 14:49, John Rose a écrit :
> Tobias,
> I just realised that a post that I made on the 'Line continuation'
> thread is better in this thread. The details are:
> I liked your ideas of:
> Dim aExec As String[]
> Dim sRes As String
> aExec = ["cat", "/proc/meminfo"]
> ' Use aExec.Add() to
Tobias,
I just realised that a post that I made on the 'Line continuation'
thread is better in this thread. The details are:
I liked your ideas of:
Dim aExec As String[]
Dim sRes As String
aExec = ["cat", "/proc/meminfo"]
' Use aExec.Add() to add more arguments
Exec aExec To sRes
and (thread 'Sto
On Sun, 08 Dec 2013, John Rose wrote:
> I want to be able to stop a CLI program (started by an Exec statement)
> as though the user was keying in a special character from the keyboard.
> Specifically, I want to stop ffmpeg recording to disk when grabbing
> streaming video using x11grab. The rec
I want to be able to stop a CLI program (started by an Exec statement)
as though the user was keying in a special character from the keyboard.
Specifically, I want to stop ffmpeg recording to disk when grabbing
streaming video using x11grab. The recording is stopped by the user
entering q if t
13 matches
Mail list logo
