I can see how file cinco.mov is growing while recording but when I exectue
REMOVE 1 FILE “RECORDS/cinco.mov”
in order to stop recording then the messages
202 REMOVE OK\r\n
[ffmpeg_consumer] Uninitialized.
are shown and inmediately Caspar process crashes.
As a result the file “cinco.mov” is not possible to be played, probably because wasn’t closed properly.
Have you noticed something like this? is there anyway to fix this issue?
Just for curiosity: Have you ever tried the same without giving the .mov extension? If that does not help please check if that bug is already reported and if not file a bug report on Caspar’s GitHub page.
This is a known problem with thee FFmpeg consumer on Windows, affecting REMOVE FILE and REMOVE STREAM … or a sequence of 2 ADD FILEs or 2 ADD STREAMs. Through experiment, it has been shown that this can be avoided by compiling with /INCREMENTAL linking or by selecting a build type of ReleaseWithDbgInfo (which switches on incremental linking!).
Shoud I download source code and compile with /INCREMENTAL linking? Where I can get a build type of ReleaseWithDbgInfo ?