https://bugs.kde.org/show_bug.cgi?id=456598
Julius Künzel <jk.kde...@smartlab.uber.space> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jk.kde...@smartlab.uber.spa
| |ce
Resolution|DUPLICATE |WAITINGFORINFO
--- Comment #8 from Julius Künzel <jk.kde...@smartlab.uber.space> ---
First of all I kindly ask you to follow the Code of Conduct in your reports
(https://kde.org/code-of-conduct/), we are not going to continue the
conversation if you don't use a decent and respectful language.
Kdenlive is an open-source project with a small developer team of 1-3 active
devs spending their spare time and we are not able to fix everything we want as
fast as we want. At least we are not aware of all bugs and we need reports like
yours to make Kdenlive better.
It is up to you to use a different software if you are not happy with Kdenlive
and it's community.
However coming to your problem: Kdenlive uses the network connection only for
very few features and only on your explicit request (eg. if you download new
render presets). Hence I would be really surprised if the problem is on
Kdenlive's side. I rather suspect a different software (maybe malware?) using
CPU or RAM resources if there is a network connection and Kdenlive can't use
the resources for rendering then. I think it should be possible to investigate
this thesis eg. with the Windows Taskmanager.
Please check this and give us feedback and set the status back to REPORTED or
to RESOLVED NOT A BUG
Also please send us the link to your former bug report (the one where you "got
told to update"). In general it would be good to continue the conversation in
the original report if the issue is the same instead of opening a new one.
Please read https://kdenlive.org/en/bug-reports/ and
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging if you have any
questions about the bug reporting process.
--
You are receiving this mail because:
You are watching all bug changes.
