GIMP Chat http://gimpchat.com/ |
|
CMYK Student's non-destructive dev build after 2.99.18 in use by me http://gimpchat.com/viewtopic.php?f=9&t=20691 |
Page 5 of 5 |
Author: | contrast_ [ Sat Feb 17, 2024 11:49 am ] |
Post subject: | Re: CMYK Student's non-destructive Gimp build in use by me. |
viewtopic.php?f=9&t=20691&start=60#p288016 The bug stated in post above sometimes happens but it doesn't always happen Attachment: 2024-02-17_11-35.png [ 373.44 KiB | Viewed 601 times ] |
Author: | contrast_ [ Mon Feb 19, 2024 4:12 pm ] |
Post subject: | Re: CMYK Student's non-destructive Gimp build in use by me. |
2.99.18 is going to be released to the public soon and it turns out a build to said download is here. viewtopic.php?f=7&t=20769&p=288104#p288104 https://download.gimp.org/mirror/pub/gimp/v2.99/ |
Author: | contrast_ [ Tue Feb 20, 2024 10:08 am ] |
Post subject: | Re: CMYK Student's non-destructive dev build after 2.99.18 in use by m |
This threads named changed from CMYK Student's non-destructive Gimp build in use by me to CMYK Student's non-destructive dev build after 2.99.18 in use by me because I'm going to be building the latest versions and keeping up beyond the checkpoint release. |
Author: | contrast_ [ Wed Feb 21, 2024 3:01 pm ] |
Post subject: | Re: CMYK Student's non-destructive dev build after 2.99.18 in use by m |
Saint GEGL (myself) is using Gimp 2.99.19 built from source while everyone else uses 2.99.18. Though I'm sure a flatpak build exist on Linux. It does master not CMYK student's build. Attachment: 299_19.png [ 212.34 KiB | Viewed 517 times ] |
Author: | contrast_ [ Wed Feb 21, 2024 3:45 pm ] |
Post subject: | Re: CMYK Student's non-destructive dev build after 2.99.18 in use by m |
Drop Shadow and my plugin Inner Glow being applied non-destructively in 2.99.19 Their custom clors are remembered Attachment: 299_19_works_proper.png [ 233.06 KiB | Viewed 516 times ] I've been compiling Gimp 2.99 from Jan 1st 2023 until today. Feb 21 2024. This Gimp 2.99.19 special branch may be the first release I consider usable for real world work. Though we still have ways to go such. IMO, Four new goals should exist for CMYK Student in order to comply with professional standards 1. Make it in default where all filters are destructive until a layer is converted into an "effects" layer. Add a section in menus called "convert to effects layer" with a GEGL icon. If they de-convert it all effects are rasterized unless it is text. Perhaps we can make it where text layers are 'effect layers' by default but normal layers and layer mask are not. 2. Add non-destructive filters on Layer mask. When of course they are converted to 'effect layers'. 3. Make it where each effect layer has its own layer mask EXCEPT for effect layer of a layer mask. IMO there is no need to give channels effect layers. 4. PLEASE DO NOT MAKE ADJUSTMENT LAYER GROUPS. Instead just make normal adjustment layers like Photoshop and Pixelitor. It can work by adding a gegl graph to each layer below it. Unless a layer group on normal cancels the adjustment layer effect. We might even be able to make it where the adjustment layer goes both up and down or ignores specified layers. But historically a adjustment layer inside a normal layer group is cancelled. From a very technical view point "adjustment layers" can be thought of as "layer effects" that have clone filters on many layers below them. In default Photoshop and Pixelitor only have the ability to use adjustment layers of fast color lighting filters but Pixelitor allows ANYTHING to be an adjustment layer if users left clicks the adjustment layer icon and select a filter. I do not have the ability to test Photoshop after 2010, so its possible CC can do this now. I am serious about Adjustment layer groups being a bad idea. Here is a preview of adjustment layers in an open source program called Pixelitor. You have to enable experimental features to use them but trust me they are stable as I've been using them for almost two years. Pixelitor can also call GEGL from the command line bash and that too can be used as an adjustment layer, but it is very slow and syntax only (for GEGL and GMIC, not native filters, they are fast). In Pixelitor adjustment layers apply something like "gegl graphs" to every layer below them unless blocked out by a "normal layer group". https://github.com/lbalazscs/Pixelitor Pixelitor using its Gradient Map filter as an adjustment layer Attachment: adjustment_layer_native.png [ 214.42 KiB | Viewed 516 times ] Pixelitor using GEGL syntax "command line filter" as an adjustment layer. Attachment: pixelitor_adjustment_layer_gegl.png [ 334.73 KiB | Viewed 516 times ] |
Author: | contrast_ [ Wed Feb 21, 2024 5:27 pm ] |
Post subject: | Re: CMYK Student's non-destructive dev build after 2.99.18 in use by m |
2.99.19 soft locked while quick saving an xcf file. No idea why. It already saved the .xcf on disk but the quick update save "ctrl s" caused the soft lock Attachment: why.png [ 946.69 KiB | Viewed 506 times ] Other then that this is beautiful. It looks like 2.99.19 is STABLE |
Author: | contrast_ [ Wed Feb 21, 2024 5:34 pm ] |
Post subject: | Re: CMYK Student's non-destructive dev build after 2.99.18 in use by m |
It soft locked again while saving but this time I got a bug report crash and it looks like it has to do with my plugin SSG. An acronym for (stroke shadow glow) https://github.com/LinuxBeaver/GEGL-SSG ... /releases/ @CMYK_Student check this bug out. Serious hindrance to a pros workflow here. Code: Select all <!-- Copy-paste this whole debug data to report to developers --> |
Author: | contrast_ [ Wed Feb 21, 2024 6:01 pm ] |
Post subject: | Re: CMYK Student's non-destructive dev build after 2.99.18 in use by m |
I triggered the out of bounds bug by making a composition with text and dropshadow then moving and expanding the text layer. Please manipulate the text layers corners in hopes of triggering the out of bounds text bug yourself. Attachment: out_of_bounds_clip_bug.png [ 316.86 KiB | Viewed 505 times ] Attachment: four_corners_to_manipulate.png [ 415.46 KiB | Viewed 505 times ] We can solve this bug. I believe in your CMYK Student! |
Author: | contrast_ [ Wed Feb 21, 2024 9:47 pm ] |
Post subject: | Re: CMYK Student's non-destructive dev build after 2.99.18 in use by m |
@CMYK_Student I found a bug that is very easy to duplicate. I duplicated a composition and two layers with non-destructive filters were in a "normal" layer group. After duplicating the composition all non-destructive filters were in tact except the ones inside the layer group. Let's solve this bug! |
Author: | contrast_ [ Thu Feb 22, 2024 10:02 pm ] |
Post subject: | Re: CMYK Student's non-destructive dev build after 2.99.18 in use by m |
Congrats for the inspiration. CMYK Student's 2.99 Gimp build inspired me to make a new unreleased plugin that remembers the original color of an image before doing an "outline only" effect. Said unreleased GEGL plugin depends on two other plugins of mine SSG and Custom Bevel. Users can now use shape brush packs in Gimp and make real time non-destructive shape outlines or easy bevel outline only text. The plugin also works in Gimp 2.10 but it won't have real time brush abilities. The technical reason for me making this plugin is so that 2.99 users could make outline only bevels on the same 'layer effect' setting without writing GEGL syntax. Bevel Mode Attachment: new_plugin_CMYK.png [ 373.55 KiB | Viewed 473 times ] Outline Mode Attachment: 2024-02-22_21-59.png [ 315.9 KiB | Viewed 473 times ] I will make a separate thread when this plugin is released, and due to the fact that Gimp 2.99x currently crashes most of the time when using layer src=/image_here.jpg in the GUI only, This plugin will NOT contain the ability to upload an image file. This would have been a trivial addition but I don't want to make any new plugins that use that feature until that bug is fixed. |
Author: | contrast_ [ Thu Feb 22, 2024 10:18 pm ] |
Post subject: | Re: CMYK Student's non-destructive dev build after 2.99.18 in use by m |
@CMYK_Student I got a new bug while dragging and dropping a color into a layer. Usually in Gimp 2.10 I have a keyboard shortcut to alpha lock an image and color fill but in 2.99.19 I don't have the same keyboard shortcuts. So I did it manual and it spit out this. I was running my new underdeveloped unreleased plugin "Outline Deluxe" but just skimming through the error it looks like it has nothing to do with it. Code: Select all <!-- Copy-paste this whole debug data to report to developers --> |
Author: | contrast_ [ Thu Feb 22, 2024 11:41 pm ] |
Post subject: | Re: CMYK Student's non-destructive dev build after 2.99.18 in use by m |
Outline Deluxe plugin is released. Download below https://github.com/LinuxBeaver/Outline- ... n/releases Attachment: 307221904-bd7c761c-9847-44b0-a2ae-6609b15bbf37.png [ 469.57 KiB | Viewed 468 times ] Attachment: 307222574-21d83a85-8b13-4518-bb45-957277a7a756.png [ 574.27 KiB | Viewed 468 times ] It has code and binaries and will work on 2.10 and 2.99 but it is specially intended for 2.99.19. Usually I do not release plugins several hours after I make them. This is a quickie exception. |
Author: | contrast_ [ Tue Feb 27, 2024 3:20 am ] |
Post subject: | Re: CMYK Student's non-destructive dev build after 2.99.18 in use by m |
-- Two New bugs caused by the same thing -- Anchoring a floating point with non-destructive filters creates a visual bug on layer with active effects if it is close to it. If the layer is far away enough it won't do that, but eitherway the anchor will double apply and clip the effect, and the original content in the layer will have a destructive effect. The double apply is the effect applying on a destructive layer. Take the green and red square for example. The red square has always been there as a non-destructive layer. Green is a floating point that is being anchored in the same layer. Now the drop shadow creates a visual clip bug. Clip bug created by anchoring a floating point on the same layer too close to alpha defined content. I incorrectly used the term "merged" Attachment: anchor_floating_point_dropshadow.png [ 53.27 KiB | Viewed 401 times ] Drop Shadow applying destructive bug by anchoring a floating point on the same layer with alpha defined content. Attachment: anchor_floating_point_destructive_original_dropshadow.png [ 37.89 KiB | Viewed 401 times ] The expected behaviour is for both shapes to exist on the same layer, anchoring a floating point should work without the clip or destructive anchor. I hope this bug gets solved. It appears the problem is that anchoring a floating point applies all layer effects when it shouldn't. - UPDATE I did a floating point with select all and it still failed to solve this problem. |
Author: | contrast_ [ Thu Apr 25, 2024 9:38 pm ] |
Post subject: | Re: CMYK Student's non-destructive dev build after 2.99.18 in use by m |
The bug above with the colored squares has been solved for a while now... Moving onto previews of recent Gimp 2.99.19x Attachment: 2024-04-25_22-18.png [ 1.22 MiB | Viewed 223 times ] The same template can be reused by merging floating points Attachment: non-destructive_template.png [ 796.04 KiB | Viewed 223 times ] Outside of the aura plugin on the second image, both images are using the same "layer effects" for styling text and transparent images. This is called a 'non-destructive' template and I have been working like this in Pixelitor for TWO YEARS and now Gimp can finally do this type of work. The text you see was easily changed just by typing new text, but the image of the lady had to be deleted and replaced with a floating point of the greek bust statue. One could have also made a duplicate layer and then deleted and added a floating point. For a download to the text styling plugin that works in Gimp 2.10 and 2.99.19 go here https://github.com/LinuxBeaver/Royal_Te ... /releases/ |
Page 5 of 5 | All times are UTC - 5 hours [ DST ] |
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |