> On Jan 11, 2018, at 3:40 PM, Moritz Barsnick wrote:
>
> On Thu, Jan 11, 2018 at 21:11:55 +0100, Nicolas George wrote:
>>> So apparently, ffmpeg is getting some different signal under Linux,
>>> and/or handling it differently.
>>
>> SIGPIPE, obviously.
>
> It was originally
On Thu, Jan 11, 2018 at 21:11:55 +0100, Nicolas George wrote:
> > So apparently, ffmpeg is getting some different signal under Linux,
> > and/or handling it differently.
>
> SIGPIPE, obviously.
It was originally obvious to me. Except that I don't get what Windows
does differently. But I never
Moritz Barsnick (2018-01-11):
> So apparently, ffmpeg is getting some different signal under Linux,
> and/or handling it differently.
SIGPIPE, obviously.
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
___
ffmpeg-user
On 1/12/2018 12:14 AM, Moritz Barsnick wrote:
Apparently, this requires you to explicitly map something ("-map 0"). I
don't recall why, and why not with a filter involved. Too lazy to
contemplate. *shrug*
My guess is, in absence of map, ffmpeg auto-selects streams for output
based on what
On Thu, Jan 11, 2018 at 10:56:13 -0500, Dave Rice wrote:
> Could you share the working command you used?
I'm sure it was
$ ffmpeg -report -f lavfi -i testsrc2 -f nut - test.mov -y | ffplay -
That was at work, under Windows. Now I'm at home, and "all" I have
access to is Linux. And here, I can
Hi Moritz,
> On Jan 11, 2018, at 10:19 AM, Moritz Barsnick wrote:
>
> On Thu, Jan 11, 2018 at 16:03:08 +0100, Moritz Barsnick wrote:
>> Interesting: ffmpeg doesn't close one output correctly, if the other
>> one fails? (I didn't double check, but that is an undesired
On Thu, Jan 11, 2018 at 16:03:08 +0100, Moritz Barsnick wrote:
> Interesting: ffmpeg doesn't close one output correctly, if the other
> one fails? (I didn't double check, but that is an undesired limitation,
> if you ask me. I'm not using the word "bug" yet. ;-))
I just tested this with both
On Thu, Jan 11, 2018 at 09:25:53 -0500, Dave Rice wrote:
> When running these commands the video plays (in either ffplay or
> mpv). When I close the playback window to stop the player, then
> ffmpeg also stops, but with an invalid output. In this case the file
> will_this_file_work.mov will have
Hi all,
With ffmpeg I’m trying to write a file from a device input while also piping
out audiovisual data to a separate player. These commands replicate what I’m
trying to do:
ffmpeg -f lavfi -i testsrc will_this_file_work.mov -f nut - | mpv -
ffmpeg -f lavfi -i testsrc will_this_file_work.mov