https://bugs.kde.org/show_bug.cgi?id=436725

--- Comment #4 from Eoin O'Neill <eoinoneill1...@gmail.com> ---
Hey Ahab Greybeard,

This change has to do with the unification of multiple FFMPEG wrappers. We
currently have a discussion around the FFMPEG wrapper and it's future on
phabricator ( https://phabricator.kde.org/T14331 ) which encompasses some of
the discussion around using the temp folder, what to do with temporary files,
and more.

Currently, the plan is to always store the log file in the system temporary
folder and to only move (really, copy) the log file into the destination folder
(where the video file was going to save) if we determine that FFMPEG ran into
an error, which the new C++ wrapper is better at determining. Before, the log
file was always saved into the target directory regardless of success or
failure, which created a lot of garbage and unused data for the artists IMO.
Additionally, with the increased scope of parts that use FFMPEG within Krita,
it would be nice to have a unified place for us to ask users to check if they
want to know how ffmpeg ran for their given task. 

With that in mind, we're still in the planning and discussion phase, with more
changes planned beyond 5.0's release. Please, if you have any specific requests
regarding animation / ffmpeg / log file production, please give us your
thoughts on the phabricator page so that we can have a single place to track
discussion around this topic. Additionally, since KnowZero has also been
helping with FFMPEG features and frontend changes, it will also help him to see
artist and user feedback on some of the more recent changes to the FFMPEG
wrapper as well.

I'm going to leave this open and assigned. For 5.0's immediate release, I will
at least make sure that FFMPEG will reliably place error files where videos
were supposed to go when errors occur and triple check that all of the FFMPEG
operations produce a log file in the temp folder as they should.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to