https://bugs.kde.org/show_bug.cgi?id=403717
--- Comment #2 from Jonathan Gilbert ---
Huh, okay -- I simply did it without thinking and everything I used worked
except for the bug I reported here. ¯\_("/)_/¯
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403717
Bug ID: 403717
Summary: When multiple instances are running, render progress
is not handled consistently
Product: kdenlive
Version: 18.12.1
Platform: MS Windows
https://bugs.kde.org/show_bug.cgi?id=411260
Jonathan Gilbert changed:
What|Removed |Added
Platform|Other |MS Windows
OS|Linux
https://bugs.kde.org/show_bug.cgi?id=411261
Jonathan Gilbert changed:
What|Removed |Added
Platform|Other |MS Windows
OS|Linux
https://bugs.kde.org/show_bug.cgi?id=411260
Bug ID: 411260
Summary: "f=mkv" or "f=matroska" produces MP4 file output
Product: kdenlive
Version: 19.08.0
Platform: Other
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=411261
--- Comment #1 from Jonathan Gilbert ---
Created attachment 122332
--> https://bugs.kde.org/attachment.cgi?id=122332=edit
Screenshot of the "Rendering" dialog with "f=mkv" format after editing and
saving the format wi
https://bugs.kde.org/show_bug.cgi?id=411261
Bug ID: 411261
Summary: Rendering dialog does not recognize MKV file format on
initial load
Product: kdenlive
Version: 19.08.0
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=411261
Jonathan Gilbert changed:
What|Removed |Added
Summary|Rendering dialog does not |Rendering dialog does
https://bugs.kde.org/show_bug.cgi?id=411261
Jonathan Gilbert changed:
What|Removed |Added
Summary|Rendering dialog does not |Rendering dialog does
https://bugs.kde.org/show_bug.cgi?id=411335
Bug ID: 411335
Summary: Rendering selected zone not functioning
Product: kdenlive
Version: 19.08.0
Platform: MS Windows
OS: MS Windows
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=411335
--- Comment #2 from Jonathan Gilbert ---
@emohr This unfortunately did not affect the outcome.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411335
--- Comment #6 from Jonathan Gilbert ---
That did not correct the issue. However, I inadvertently had settings in place
from an unrelated render configuring it to Rescale the video, and after some
experimentation, it appears that _any_ Rescale value
https://bugs.kde.org/show_bug.cgi?id=411930
--- Comment #4 from Jonathan Gilbert ---
Work-around: Disable parallel processing.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411930
--- Comment #3 from Jonathan Gilbert ---
Created attachment 122666
--> https://bugs.kde.org/attachment.cgi?id=122666=edit
Sample frame
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411930
Bug ID: 411930
Summary: DeFish filter is not threadsafe
Product: kdenlive
Version: 19.08.0
Platform: MS Windows
OS: MS Windows
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=411930
--- Comment #2 from Jonathan Gilbert ---
Created attachment 122665
--> https://bugs.kde.org/attachment.cgi?id=122665=edit
Sample frame
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411930
--- Comment #1 from Jonathan Gilbert ---
Created attachment 122664
--> https://bugs.kde.org/attachment.cgi?id=122664=edit
Sample frame
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411930
--- Comment #6 from Jonathan Gilbert ---
Perhaps it would make sense, then, for Kdenlive to know which filters have this
upstream problem and either warn the user or refuse to use parallel processing
if the render will be affected.
--
You
https://bugs.kde.org/show_bug.cgi?id=411335
--- Comment #4 from Jonathan Gilbert ---
Some of the clips have apostrophes in their names, but as far as I can see none
of them have characters outside of the 7-bit printable ASCII plane.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=411260
--- Comment #8 from Jonathan Gilbert ---
I actually have a further update. It seems this is more properly a bug in MLT,
because the XML standard says that attribute order should not be a semantic
difference -- that's why Qt 5 feels it is okay to start
https://bugs.kde.org/show_bug.cgi?id=411260
--- Comment #9 from Jonathan Gilbert ---
MLT master now has a fix for this issue, so as long as it has another release
before the next Kdenlive release, and Kdenlive updates to take that release,
this bug should be resolved. :-)
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=411260
--- Comment #1 from Jonathan Gilbert ---
I have been reviewing the background of this report and tried to reproduce a
previous Kdenlive version producing an MKV file as I remembered. From fresh
installations of 17.12 and 18.12.2, I saw the same
https://bugs.kde.org/show_bug.cgi?id=411260
--- Comment #2 from Jonathan Gilbert ---
I have just done a follow-up test. It appears that if "f=mp4" is entirely
removed from the presets file (no 'f' option value specified), then a value
specified in the render format definition
https://bugs.kde.org/show_bug.cgi?id=411260
--- Comment #3 from Jonathan Gilbert ---
With further experimentation, I have determined that the preset files in
question are sourced directly from the MLT release and aren't part of the
Kdenlive codebase. As such, I believe I need to take this issue
https://bugs.kde.org/show_bug.cgi?id=411260
--- Comment #4 from Jonathan Gilbert ---
Alright, I have feedback from the MLT side. This appears to be a bug on the
Kdenlive side after all. When it generates the tag in the MLT
script, the parameters get reordered apparently randomly (maybe they're
https://bugs.kde.org/show_bug.cgi?id=411260
--- Comment #5 from Jonathan Gilbert ---
I did a bit more research. Kdenlive is using the Qt `QDomDocument` type to
represent an XML DOM in-memory while building the MLT script. It turns out that
between Qt 4 and Qt 5, this DOM representation got
https://bugs.kde.org/show_bug.cgi?id=411261
Jonathan Gilbert changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=411261
--- Comment #2 from Jonathan Gilbert ---
Turns out that "f=mkv" really is missing from the list that MLT passes back
when queried. The fact that the error goes away when editing the profile is the
real bug, described in #414814, and it i
https://bugs.kde.org/show_bug.cgi?id=414814
--- Comment #3 from Jonathan Gilbert ---
I have an update from the MLT team. MLT is passing the format value to/from
FFmpeg under the hood. When you ask MLT what "f" values it supports, it asks
FFmpeg, and from what I've been told, FFmp
https://bugs.kde.org/show_bug.cgi?id=368710
Jonathan Gilbert changed:
What|Removed |Added
CC||c6kargn...@liamekaens.com
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=414814
Jonathan Gilbert changed:
What|Removed |Added
CC||c6kargn...@liamekaens.com
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=414814
--- Comment #2 from Jonathan Gilbert ---
I've just poked at the source code to see what's up, and I note the following:
* All of the code involved is found inside src/dialogs/renderwidget.cpp.
* The validation is done by RenderWidget::refreshView
32 matches
Mail list logo
