subject:"\[krita\] \[Bug 359030\] G'Mic for Krita is limited to one CPU thread"

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

2016-04-19 Thread Camille Bissuel via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=359030 --- Comment #13 from Camille Bissuel --- The two filters where I can set up the rationalization number I found are Artistic > Dream smoothing Repair > Smooth [thin brush] as mentioned above ;) There may be more, but I can't find any other right know… m

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

2016-04-18 Thread David Tschumperlé via KDE Bugzilla

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

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

2016-04-18 Thread Boudewijn Rempt via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=359030 --- Comment #11 from Boudewijn Rempt --- I am tempted to say no... I could look into it, but in principle, all options are passed to gmic and then it's up to gmic to do stuff with it, and I cannot debug gmic itself. -- You are receiving this mail beca

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

2016-04-18 Thread Camille Bissuel via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=359030 --- Comment #10 from Camille Bissuel --- Many thanks to both of you ! I've just complied a fresh Krita 3 with AUR https://aur.archlinux.org/packages/krita-git/ to test your work … and parallel processing is now working, it's great ! BUT : Setting expl

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

2016-04-17 Thread Boudewijn Rempt via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=359030 Boudewijn Rempt changed: What|Removed |Added Latest Commit||http://commits.kde.org/krit

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

2016-04-16 Thread David Tschumperlé via KDE Bugzilla

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

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

2016-04-16 Thread Boudewijn Rempt via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=359030 --- Comment #7 from Boudewijn Rempt --- Er, wait, this whole discussion is bogus: this is about g'mic on _linux_! -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

2016-03-22 Thread Boudewijn Rempt via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=359030 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

2016-03-20 Thread David Tschumperlé via KDE Bugzilla

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

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

2016-03-20 Thread David Tschumperlé via KDE Bugzilla

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.

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

2016-03-20 Thread David Tschumperlé via KDE Bugzilla

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.