- User Since
- Nov 24 2017, 7:42 PM (64 w, 1 d)
Tue, Jan 22
Testing the various operators:
I'm must confess that I'm not ready to give up on this yet... I've updated the space_sequencer.py according to the renaming in your version of the operator file:
If you want to edit the space_sequencer.py file from the Blender text-editor, several additional files needs to be loaded into the text editor to avoid errors. They are opened in this .blend:
Mon, Jan 21
Sun, Jan 20
Ctrl+drag playhead/strip will snap to next cut, so snapping with Ctrl pressed would be in consistency, but the default move should be without snapping.
- How to handle collisions? What should happen when you do ripple delete and attached effect in upper channel would collide into some strip?
- prevent execution and throw error?
- move as far as possible?
- configurable behavior?
When pasting, stips will be inserted into the first free channels, so maybe when strips are colliding they should be moved upwards into the first free channel(but only if it is effect-strips).
- What should be behavior of strip lock?
- prevent any modification other then changing lock state?
Yes, I think so too.
Another thing, that I wanted to tackle was displaying and modifying properties of selection.
- I was thinking about concept of active strip - my brain refuses to accept it's usefulness. Maybe because active strip is completely independent of selection.
Maybe all select-operators should ensure that the active strip is always the last selected strip, which it is when you select manually. The question is if you deselect all also should deselect the active strip(and close the strip properties panel?). That would be an understandable behavior, but I don't know if it will be annoying to have the panel open and close all the time?
- Alt + tweak value and alt + enter seems to work pretty well so nothing to do here I guess
I feel that info about the shift/ctrl/alt functions should be in the status bar and context-sensitive, so ex. when hovering over a checkbox is should say +alt will add values to entire selection(if that is not the default behavior).
Displaying properties of selection could be done better IMO.
- Ideally you want to display all properties of all types. Logical step would be group properties based on strip type
- use tab per type, so you can immediately see what types are selected and switch between them?
- Not sure, if we can show only values of fields that would be same for all selected strips of the same type, otherwise they could be blank or display some label like "varies".
I don't know if this is too much trouble for now? How does the 3D View deal with selections containing different types?
- when I change active strip to strip of different type(from movie to sound), panel organization is quite inconsistent.
- Don't know what we can do about this...
Yeah, the strips have quite individual settings, which makes it hard to avoid panels jumping around when changing type.
@Richard Antalik (ISS) Thank you for investing so much time in this. The "space_sequencer.py" doesn't seem to be updated to reflect the changes in "sequencer.py"? When I replace these two files in a fresh build of Blender the entire UI is broken. So I can't test your changes.
Sat, Jan 19
Sorry, I didn't know that. My son was jumping around me when I updated the file, so I feel that there might be things unfinished. the main changes are the split-extract/lift/remove,operator, navigation - range-start/end menu. Will not do more for now.
These functions seem to be already included in the 'Input' submenu:
Jan 17 2019
Thank you for updating the files. I can see the try/except wasn't removed in my Github, but they are removed now.
Jan 16 2019
Jan 15 2019
Jan 14 2019
@Brecht Van Lommel (brecht) @Richard Antalik (ISS)
More fixes and comments here: https://github.com/tin2tin/blender_vse_reworked
Ex. View Channel Solo/All & Toggle All Modifiers have now been removed.
A lot has been fixed/addressed, but not yet everything.
Jan 13 2019
@Brecht Van Lommel (brecht) & @Richard Antalik (ISS)
Thank you for spending your time on this.
As I have already stated, I'm not a coder.
Most of the operators are reworked code from ex. KinoRaw. That's why the code-style differs.
I have made the first round of changes from your(Brecht's) remarks(mostly the cosmetic ones), and uploaded the files here:
(I don't know how to submit patches, sorry)
Thank you for this, @Richard Antalik (ISS)
The changes should work without changing the default VSE layout.
Dec 19 2018
If you want collect VSE issues and such. Here are some links to public documents on bugs, papercuts and suggestions for the VSE:
Dec 17 2018
If you want to test it against a (unofficial) 2.80 VSE panel, you can get it here: https://devtalk.blender.org/t/can-we-in-collaboration-produce-a-working-suggestion-for-improving-the-user-interface-of-the-vse/3264/77
Dec 16 2018
I think this change will be problematic when adding more strips from the same scene using ex. different cameras. I personally do not want the scene-strips to inherit or be limited by any duration from the scene's preview/render ranges. That duration should only be determined by the length of the strip in the sequencer(and not limited to or changed by the range currently in that scene), but that's just my opinion.
Dec 13 2018
Dec 12 2018
Dec 4 2018
Nov 30 2018
Nov 23 2018
Nov 19 2018
If you want to improve the VSE defaults, here's a collection of suggestions: https://devtalk.blender.org/t/suggestions-for-vse-ui-cleanup-and-default-settings-in-2-8/2210
Nov 16 2018
On the topic of left click mode and alterations, it feels counter-intuitive to right click in 'Timeline' and 'Sequencer' to drag the time cursor. Could this be the left click instead?
Nov 15 2018
For inspiration a discussion on StackExchange on the topic of this papercut:
Please click on the gif for an illustration of the problem when ex. swapping the position of the panel, where the vertical scrollbar completely disappears, making it impossible to work in the vse:
Nov 13 2018
Wow! On the official 2.79b I get 5 fps.
On your patch I get a clean 25 fps in the cached areas.
Nov 12 2018
Would love to test it, if you can share a build?
Oct 2 2018
I would suggest that the word "Movie" (ex. Movie Clip Editor) in Blender was changed to ex. "Video" or just "Clip".
Sep 21 2018
Strange. It crashes here on 2.8 too.
Sep 18 2018
Sep 4 2018
Aug 30 2018
Thanks for the test-build. I had to run it in compatibility mode for Windows 7 to get it to run on Windows 8.
Aug 19 2018
Aug 9 2018
Jan 26 2018
Jan 18 2018
Dec 23 2017
Dec 22 2017
Oh, so integrating the sequencer with the 3D Viewport like this, will no more be possible? Previz Camera Tools