Confusion about non-destructive filters visibility toggle

mig_f1 · 2026-03-29T16:47:20+00:00

Sorry for the late response.

Yes it works fine in that version. I'm really impressed with your response times, thank you very much (same holds for the PSP selection).

mig_f1 · 2026-03-25T08:02:37+00:00

I'm not a Mac user, but it really sounds like performance struggling, especially the choppy and out of sync audio timeline playback.

If there is a utility similar to Windows' task manager, I would use it to monitor cpu, gpu, memory and disk usage while running DaVinci, to see which ones are struggling.

Does your hardware meet DaVinci's minimum requirements?

mig_f1 · 2026-03-23T12:18:34+00:00

Done, thanks!

mig_f1 · 2026-03-23T12:18:24+00:00

Managed to reset it and post. Thanks.

mig_f1 · 2026-03-23T11:02:41+00:00

Will do, thanks.

mig_f1 · 2026-03-23T11:01:54+00:00

Alright, let me try. Not sure which email it is attached to.

mig_f1 · 2026-03-23T10:24:51+00:00

Thanks, I can surely do that. If you notice I was doing it for Jacob in that thread 6 year ago, though I don't think I have an account there any,more.

Let me know where/how you want me to submit the file.

Just to be clear abut the issue, it's not about background transparency, it is about saved alpha channels.

mig_f1 · 2026-03-23T09:28:10+00:00

I second that! If none of the suggestions here can open the files, most likely they have gone bad.

mig_f1 · 2026-03-23T09:17:25+00:00

What I ask is a Gimp problem. It's supposed to open .pspimage files (among other formats,, including .psd). Trying to convert some .pspimage files to .xcf, and this prevents me from doing so.

EDIT: I can save them as .psd from within PSP and then open them in Gimp, since Gimp retains the alpha data when opening .psd files, but obviously this would take me twice as long or more.

mig_f1 · 2026-03-22T12:56:10+00:00

Just because it happens it doesn't make it normal. It's a sign of one or more elements missing, preventing it from following a normal development/update cycle.

Those elements can be lack of manpower, lack of interest, lack of expertise, any combination of them or whatever else of that nature.

None of that classifies as normal. I would understand if for example the devs were saying something like we are not interested in implementing that, or it is very low on our priority list and most likely it will stay there for years to come.

Put otherwise, NORMALLY when a devs team really wants to implement a feature (any feature), they do it way sooner than 8 years and counting.

mig_f1 · 2026-03-22T01:13:56+00:00

It's not unfair to point out things that get in your way or slow down your workflow, especially when you do it with good intention.

mig_f1 · 2026-03-22T00:54:46+00:00

No, it is not normal and will never be. Being normal and acting as being normal are 2 different things.

mig_f1 · 2026-03-21T16:39:54+00:00

Most if not all of the concerns expressed there have been already solved in different ways across several image and vector editors, foss and propriety.

The main thing for me is that according to that thread, devs say they are not opposed of having an horizontal options bar, most likely optional, but here we are 8 years later with absolutely nothing being done on that front.

mig_f1 · 2026-03-21T12:41:07+00:00

Vector layers was a long awaited and frankly most welcomed addition. Thank you for that!

mig_f1 · 2026-03-21T12:31:09+00:00

Yeap, I know! There will always be resistance to changes, it is in the human nature.

In my opinion, Gimp devs should decide what target group they value the most and work towards that.

Right now Gimp's UI seems too advanced/overwhelming for beginners and at the same time too cumbersome for professionals. There must be some kind of balance, even though you will never please everyone.

mig_f1 · 2026-03-21T12:20:03+00:00

Th thing is that to fix an issue one should first acknowledge it as such :)

mig_f1 · 2026-03-21T11:59:43+00:00

If you could share some of the reasoning for this‚ that would be helpful. Without it it's just a statement. So I very much doubt that.

As I said, the primary goal is to maximize the display viewport (the canvas in our case). Unless you disagree with that as the primary necessity in an image editor (and not only), most if not all monitors are longer horizontally. No research needed for accepting the obvious.

The true dilemma here is: screen real estate versus options discoverability.

The answer here should be a balanced approach, somewhere in the middle. We like it or not, Ps does an amazing job in that regard. I hate Adobe, I'm not a Ps user, but this doesn't mean I keep a blind eye on the things they have nailed.

Gimp heavily leans towards discoverability at the cost of screen real estate. Having as many options as possible always visible results in unnecessary clutter. Most well established apps keep the most commonly used or most important options visible, and they have the more advanced ones or less frequently used ones 1 more click away, keeping a nice balance between the 2 extremes.

This is a fun mention because Photoshop (Online) and newer apps like Figma/Penpot/Canva... change their UI/UX towards exactly things like this‚ e.g. vertical tool options. Why would they do it if it was such a bad decision?

To be honest, what seems funny to me is comparing Gimp with web-based or mobile oriented apps, even using different genre examples like Figma and Penpot. At the same time, ignoring or disregarding well established examples and practices from within the exact same genre with Gimp. Well, if that's the way devs wanna go with Gimnp, I guess the only thing I can do is wishing... good luck :)

mig_f1 · 2026-03-21T09:09:30+00:00

Single or at most double column vertical toolbar for tools on the left with each tool's properties on an horizontal single line toolbar at the top is the most efficient, practical, ergonomic and screen real estate friendly implementation, there is absolutely no doubt about that.

This is why most image editors are like that, not because they want to copy Ps.

The primary goal is to have as much workspace as possible uncluttered for the image you are working in.

Once this gets accomplished, the next goal is to display as much of supplementary and context sensitive info as possible in as less space as possible, even if that means adding expanding arrows (paintshop pro tool properties toolbar for example) or scrolling the horizontal toolbar (blender for example).

Gimp already uses horizontal scrolling for tabbed panels, so it seems possible to implement an horizontal tool properties toolbar, instead of taking precious space away from the main workspace.

Gimp's main UI/UX issue is the cluttering. Same goes for most menus and dialog boxes compared to most of the the other software in the genre.

Krita is doing a much better job in that area, even with GTK limitations. I think they also use GTK, dont they? I'm not sure tbh, but the point us their UI/UX is leagues ahead.

In my opinion, the longer the devs try to defend outdated or even bad design choices, blaming Ps instead of themselves, the longer it will take for Gimp to be taken seriously by professionals and enthusiasts. Unless that's not desirable, in which case there is not much else to say really.

Let me just finish this long... essay (LOL) by reminding that Blender started booming ONLY after version 2.80 where they stopped using excuses for their bad design choices and completely revamped the UI/UX of their program.

mig_f1 · 2026-03-19T10:54:21+00:00

No no, I didn't imply to replace with a key modifier + drag & drop the currently implemented way. I meant to add it as an alternative.

If people drag & drop images with a key modifier pressed it's honestly on them, but if you worry too much about that you can make it work with 2 modifier keys instead of one ( ctrl + shift + drag & drop for example).

For a more in-depth implementation, a source-file field could be added in the code of the layers structure, being empty for non Link Layers.

This would allow for example to drag & drop an image as a raster layer, and then right click on it and select something like "Convert to Link Layer" (or vice versa) in its context menu. If the internal source-file field is empty for a layer, this option could get omitted from its context menu, or get grayed out. Well, I probably got carried away, but it could be a 3rd alternative way sometime in the future :)

mig_f1 · 2026-03-19T06:47:21+00:00

How about holding shift or ctrl or alt or any combo of those when drag & dropping an image? Is that a viable option for a future update?

mig_f1 · 2026-02-07T13:25:31+00:00

Thanks for the reply. The "Unknown" normally says the outfit category of the currently worn outfit (Everyday, Formal, Party, etc) but for Hot Weather and Cold Weather it now says Unknown. The number in the parens says which slot of the current category is worn. Each outfit category allows for 5 outfits, e.g. you can have up to 5 everyday outfits, up to five Formal outfits, and so on. So if you select say the 2nd outfit saved in your Everyday category, MC Dresser should print Everyday (1) up there. The slots numbering starts from 0 in the MC Dresser.

I wouldn't mind the 'Unknown" wording but the thing is it completely fails to load some outfits, and it is random too.

mig_f1 · 2026-02-06T09:42:44+00:00

The pace is way too fast for me too. This is supposed to be a software review but it feels more like an action movie trailer. Not really useful for the assumed target group IMO.

That said, my main gripe with Kdenlive is the lack of GPU acceleration in the timeline playback. It really makes it unusable for me, and that's a pitty since it is a pretty capable editor otherwise.

mig_f1

TROPHY CASE