On Friday 15 May 2015 11:17:24 René J.V. Bertin wrote:
> On Thursday May 14 2015 20:56:33 Thiago Macieira wrote:
> >> Anyway, I can't remember, esp. not what exactly happens in popenEx().
> >> I've
> >> linked to the code, so you can look that up just as easily as I ...
> >
> >I did. You didn't do
On Thursday May 14 2015 20:56:33 Thiago Macieira wrote:
>> Anyway, I can't remember, esp. not what exactly happens in popenEx(). I've
>> linked to the code, so you can look that up just as easily as I ...
>
>I did. You didn't do what is the cause of the problem: the non-blocking part
>of it.
OK,
On Thursday 14 May 2015 23:51:46 René J.V. Bertin wrote:
> On Thursday May 14 2015 13:38:12 Thiago Macieira wrote:
> > No, I don't. I mean non-blocking writing.
>
> Well, non-blocking writing usually means that there's a buffer somewhere
> that allows the write call to return before everything is
On Thursday May 14 2015 13:38:12 Thiago Macieira wrote:
> No, I don't. I mean non-blocking writing.
Well, non-blocking writing usually means that there's a buffer somewhere that
allows the write call to return before everything is written to the destination
media :)
Anyway, I can't remember, e
On Thursday 14 May 2015 19:24:13 René J.V. Bertin wrote:
> On Thursday May 14 2015 07:59:41 Thiago Macieira wrote:
> > On Thursday 14 May 2015 13:21:59 René J.V. Bertin wrote:
> > > I never noticed particular performance issues with the input this code
> > > was
> > > used with (2-4Gb max).
> >
>
On Thursday May 14 2015 07:59:41 Thiago Macieira wrote:
> On Thursday 14 May 2015 13:21:59 René J.V. Bertin wrote:
> > I never noticed particular performance issues with the input this code was
> > used with (2-4Gb max).
>
> Asynchronous writing?
If you mean buffered, through standard stdio rout
On Thursday 14 May 2015 13:21:59 René J.V. Bertin wrote:
> FWIW, I did something similar a couple of years back. I didn't use Qt, but
> good old popen(). I did modify the Win32 version that (IIRC) ships/ped with
> MSVC (I used the Express version) so that it didn't open a console window
> and could
On Wednesday May 13 2015 06:49:18 Thiago Macieira wrote:
> On Tuesday 12 May 2015 17:36:59 Matthew Woehlke wrote:
> > After further testing, it seems that the problem is caused by writing to
> > the process's stdin? Is there some issue with writing to a QProcess's
> > input pipe on Windows? (We are
Hello,
Is OpenCV an option?
http://docs.opencv.org/doc/tutorials/highgui/video-write/video-write.html
On Tue, May 12, 2015 at 8:21 PM, Matthew Woehlke <
mw_tr...@users.sourceforge.net> wrote:
> I have an application that generates a series of images (QImage) and
> writes them to disk as a vid
On Tuesday 12 May 2015 17:36:59 Matthew Woehlke wrote:
> After further testing, it seems that the problem is caused by writing to
> the process's stdin? Is there some issue with writing to a QProcess's
> input pipe on Windows? (We are writing quite a lot - many MiB's - of
> data...)
Yes. The QWind
On 2015-05-12 14:21, Matthew Woehlke wrote:
> I have an application that generates a series of images (QImage) and
> writes them to disk as a video. I am encoding the video using an
> external FFmpeg process, which I start and communicate with via
> QProcess. I feed this the images via its stdin, u
I have an application that generates a series of images (QImage) and
writes them to disk as a video. I am encoding the video using an
external FFmpeg process, which I start and communicate with via
QProcess. I feed this the images via its stdin, using QImage::save to
write them to the QProcess in B
12 matches
Mail list logo
