https://bugs.kde.org/show_bug.cgi?id=359030
David Tschumperlé changed:
What|Removed |Added
CC||david.tschumpe...@gmail.com
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=360764
--- Comment #2 from David Tschumperlé ---
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
https://bugs.kde.org/show_bug.cgi?id=359030
--- Comment #4 from David Tschumperlé ---
Ha yes, you are right about the progress report.
I'll ask Thomas to look into this problem, I'm sure this can be solved really
easily.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359030
--- Comment #5 from David Tschumperlé ---
Sorry, I'll ask *Tobias*, not Thomas :)
He is the author of the libc interface.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359030
--- Comment #6 from David Tschumperlé ---
Well, after looking more closely at the G'MIC libc interface, I've seen this is
already possible to get access to the progress bar. Maybe Lukas can tell me
what is missing exactly.
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=359030
--- Comment #12 from David Tschumperlé ---
Well, maybe there is filters remaining where the two parallelization methods
are used in the same time (which is useless of course).
Precisely, could you tell what filter allows you to choose the number of CPU
https://bugs.kde.org/show_bug.cgi?id=357880
David Tschumperlé changed:
What|Removed |Added
CC||david.tschumpe...@gmail.com
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=357880
--- Comment #4 from David Tschumperlé ---
I'll try at least to compile it with msvc2012 (the one I have at the lab).
Anyway, I doubt there will be an improvement compared to previous versions of
G'MIC. I think you should consider using the .dll bridge d
https://bugs.kde.org/show_bug.cgi?id=357880
--- Comment #6 from David Tschumperlé ---
No, But I've sent you a mail so you can contact Tobias directly.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357880
--- Comment #8 from David Tschumperlé ---
Today, I've released a 'pre-version' of G'MIC, which should be very close to
the final release. I'm still trying to find bugs (if any remaining :) ). Maybe
it could be a good candidate to test on your own.
So fa
https://bugs.kde.org/show_bug.cgi?id=357880
--- Comment #9 from David Tschumperlé ---
(In reply to David Tschumperlé from comment #8)
> Today, I've released a 'pre-version' of G'MIC, which should be very close to
> the final release. I'm still trying to find bugs (if any remaining :) ).
> Maybe i
https://bugs.kde.org/show_bug.cgi?id=357880
--- Comment #12 from David Tschumperlé ---
So, it seems to work ? Final release of 1.6.9 is planed for next week :)
Thanks for your time Boud.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359030
--- Comment #8 from David Tschumperlé ---
So, maybe more info about how multi-threading is implemented and used in G'MIC.
There are two different ways for G'MIC to use multiple cores for doing
calculations:
1 - Either a G'MIC filter uses one of the "bu
13 matches
Mail list logo
