Summary: | G'mic interactive colorize integrated with Krita is much slower than stand-alone G'mic | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Rastaban26 <regulus2626> |
Component: | G'Mic for Krita | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | minor | CC: | halla |
Priority: | NOR | ||
Version First Reported In: | 3.0 Alpha | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Rastaban26
2016-03-20 09:13:31 UTC
Hi, Thanks for your report. I think that this is related to https://bugs.kde.org/show_bug.cgi?id=359030 so I'll add this bug report to that one. *** This bug has been marked as a duplicate of bug 359030 *** As a side note, let me say that the main colorization algorithm is not multi-threaded, so the difference cannot be due to the fact OpenMP is enabled in the CLI version of G'MIC. I suspect this has to do with the different compilers used (G'MIC CLI uses g++, while Krita uses MSVC). I has observed the same kind of problems when compiling G'MIC CLI using MSVC : it is way slower to compile, but has also slower performances when executing filters. Okay, that explains the issue. |