Unfortunately not all filters can be used in all situations.
Changes could be made but that would mean going back to the source, applying those changes and then compiling for all the OS’s, not a fun exercise.
As you say @sauron , it can still be rather handy especially once it has keyframes.
@brian
What are the chances of including a small area under the sliders of the filters (or at least some) that gives the user a short description of the filter and any shortcomings?
For example for the RGB Spilt:
RGB splitter - splits the red, green and blue channels and shifts them by the amount set by the sliders.
NOTE - Does not preserve the alpha channel.
Labor over the filter name and the names of the parameters to make them as clear as possible
Add tooltips to the parameters to help give further detail
Fix the underlying alpha issue (I can help with that)
I think that adding informational text is only a very last resort if we can’t find a way to make the interface itself intuitive. In my experience, the best user interfaces don’t require any instructions because the user can tell what to do just by looking at it. But sometimes it isn’t possible to achieve that.
I do agree with you, choice of name is very important.
Busy studying examples and the notes for QT qml and seeing which would be the best way to apply tooltips without them becoming annoying.
As regards fixing the alpha problem, I’m wondering if it’s worth it for just this filter.
It can still be used just not when alpha is required.
Your time and effort could probably be better spent on other areas of Shotcut, like adding VST support, hint, hint
I would argue that it’s an oversight that should be corrected. Who knows if a future filter would also be affected. Plus, even if an explanation were provided to the user in the UI about this, only being able to use the filter on a clip if there is no image or video underneath it is a perplexing limitation and one that would always carry a workaround that really shouldn’t exist.
You really like this filter…only kidding, you do raise some valid points.
However, I’m thinking as to why the alpha was stripped off and suspecting that it created problems.
Judging by the comment in the code, it certainly looks that way.
“// No need to save alpha because it will distort the resulting image”
So taking that into account, will it be worth spending time and effort on trying to add it?
I don’t know.
I certainly don’t have the time and enough C++ experience, coded a bit with C ages ago, but that is a different kettle of fish.
If @brian and @shotcut think it’s worth it and they have the time then great, it would be nice to have alpha too, but it’s not a show stopper for me.
It is a bug in that frei0r plugin in my opinion. It should not touch the alpha if the effect does not use or affect it. Easy change but needs contributors review.
I added this filter for the next release. In the course of that, not only did I make some changes and fix some bugs but also added support for keyframes (simple and advanced). Prior to adding keyframes, I created a small UI framework to support keyframable filters and used that for this filter addition. The framework is intended to take away a lot of the boilerplate JavaScript code to support keyframes that gets copied from one filter to the next. Thank you for the contribution.
amazing filter… well done
p.s. before this filter i just make 3 layer copys on the video with different color channels… but now everything is much more easy
edit: from where i can find and download other shotcut filters ?