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

Know Zero <knowz...@pokemail.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |knowz...@pokemail.net

--- Comment #5 from Know Zero <knowz...@pokemail.net> ---
(In reply to healer.harie from comment #3)
> It's strange that you mentioned that it should already work. Was this
> behaviour replicatable in other machine (including linux and macOS) for
> 5.0.0beta1?
> 
> I did have krita v4.4.7 in an other Windows machine (long ago), where I've
> added an additional rule of the path of ffmpeg (C:\Program Files\fftools) to
> the environment variable, PATH. The CMD does recognize the `ffmpeg` command,
> but krita don't automatically find it.
> 
> I ran krita.com, and tried to open the "Render Animation", the log contained
> like:
> ```
> ...
> Qprocess: Destroyed while process ("C:\\Program Files\\fftools\\ffmpeg.exe")
> is still running.
> 
> ```
> 
> It seems that somehow, krita knows ffmpeg.exe exist and its location but the
> FFmpeg text box is still empty.
> 
> But, if I manually execute ffmpeg.exe (by clicking the ffmpeg executable),
> Krita will eventually fill up the location of ffmpeg and the "Qprocess log"
> stops appearing. It remember this even if I restart Krita again and again,
> but do I restart the computer itself, is when it will be back to normal and
> I had to execute ffmpeg again. This does not solve the problem.
> 
> On a side note, I see that proposedPaths is written to some stream
> https://github.com/KDE/krita/blob/fd7ec51dd1e66fc3aa92a6021036fb711ba69003/
> libs/ui/animation/KisFFMpegWrapper.cpp#L365, where could I possibly find
> this file?

It's the timeout issue that should have been fixed in:

https://invent.kde.org/graphics/krita/-/commit/123c302c722376870ed6def5a873b046576882b8

Try the latest nightly build and it should work.

This is a duplicate of:
https://bugs.kde.org/show_bug.cgi?id=441435

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

Reply via email to