* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. * but WITHOUT ANY WARRANTY without even the implied warranty of * This program is distributed in the hope that it will be useful, * the Free Software Foundation, either version 3 of the License, or * it under the terms of the GNU General Public License as published by * This program is free software: you can redistribute it and/or modify This might be a good example to work from: mltframework/shotcut/blob/master/src/qml/filters/blur/ui_box_blur.qml /* I agree with Dan’s comment: It is good to start from a recent example that uses KeyframableFilter and then modify to match your needs for this filter. My opinion is that if you are going to show three keyframe parameters in the keyframe panel, then you should have three keyframe toggle buttons in the filter panel (instead of making them all share one stopwatch button). Sometimes that helps to get feedback on the use cases for that specific filter. You could post a screenshot of your progress so far and people could comment on that. Are users likely to want to keyframe the three parameters separately? Or are they more likely to modify all 3 values at the same time? So you should consider the use cases for your filter. For the 3-band EQ, I combined the three parameters into one set of keyframes because I think it makes sense to modify all the values together. I do not think we have generalized guidelines for this. This is a judgement call decision on a case-by-case basis. I couldn’t find a UI/UX guide so am asking for directions. It’s unclear if they should be supported for new filters. It’s a bit hard to figure out but looks like they’re sort of old and are converted into regular keyframes if the keyframe type is changed. A compromise might be three different keyframe buttons that let the user animate individual properties.Īnother question is whether “simple” keyframes should be supported (fade-in/fade-out). The logic is also a bit more convoluted because changes of just one knob shouldn’t create keyframes in other knob tracks. However, it means that this filter alone creates three separate KF tracks. However, internally this UI is easier to make and it wouldn’t clutter the keyframe timeline.įor LP I made three “curve” tracks (cutoff, rolloff rate, wetness) so I can see their values right in the timeline. Every point indicates that some values were changed at this frame but it’s not possible to see which exactly. it’s not possible to edit the keyframe values directly in the track, they’re all squashed into “points” instead. But in 3eq filter, for example, there’s only one track and it’s not a “curve” track i.e. Shotcut allows to make separate keyframe tracks for every knob. I want to know what UX is preferred for this. Still, needs UI and logic modification in QML. I dug into the source and today implemented keyframes for the low-pass filter, it’s not that hard but also not as easy as setting a flag “use keyframes” inside. Quite weird, I thought all filters can use keyframes. I was making a meme video and needed to keyframe the low-pass filter (and also reverb) but it wasn’t possible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |