User Details
- User Since
- Nov 24 2017, 7:42 PM (239 w, 6 d)
Wed, Jun 29
The drag and drop from system file browser might have been affected by this patch: https://developer.blender.org/D14560
Tue, Jun 28
Thu, Jun 23
Well, having it fail without any useful explanation explanation, will be perceived as a bug by most users and it doesn't go well with the declared ambition of the VSE "should just work".
Tue, Jun 21
Thu, Jun 16
This file seems to hold the sync all the way through in spite of being vfr(very impressive):
@Hamdi Ozbayburtlu (hamdio) The trouble is that the DNxHD export option is available even though the current project settings may not support it.
Tue, Jun 14
@Richard Antalik (ISS) Maybe consider also adding Slide now you know how it is done?
Mon, Jun 13
By “sadly ignored”, did you mean by users like me?
No, by the BF devs.
It's information about the Overlay drop-down in the Sequencer header which is missing:
Let me recommend you the sadly ignored VSE manual by Husch for future questions: https://vse-docs.readthedocs.io/
Sun, Jun 12
Yes, this is a regression. Instead of doing a slip(move content), it is now doing a slide(move position).
Sun, Jun 5
JF Matheu did some great 2d widgets in python which may serve as UI reference for the surround position widget:
May 30 2022
Text size is not adjusted to fit when there is a resolution change and Preview is not updated either:
@Richard Antalik (ISS) When the scene is deleted of a scene strip, the strip gets a red line. This should happen to all strip types when the source is gone missing, and currently it doesn't.
May 20 2022
Improving the connection between the source scene time edits and the scene strip time edits is a good idea, IMO. The culprit is that the source scene range isn't linked to the hold values, The hold values and the scene strip source scene range values are displayed in the Time panel, when a Scene strip is an active strip:
Only the Hold values can be edited, but currently, they don't have any meaning in Scene strips, but the logical thing would be when changing them the range of the source scene should be changed accordingly. And vice versa, a change in the source scene range should change the hold drawing on the scene strip(this isn't currently the case). IMO this would be the consistent way to deal with the connection between the Scene strip range and the Source Scene Range - to link the Scene Strip Hold values with the Source Scene Range values.
May 16 2022
If you switch on View Caching, you'll see that it is caching the individual frames when moving the playhead. And the cache is flushed when moving a clip.
If you want to switch off the caching entirely it is done in the sidebar > Cache. When it is switched off, there should not be a drop in memory when moving playhead.
May 15 2022
May 14 2022
Though the issue here can be fixed by changing blend mode, it is very likely other users will encounter the same problem and report it again as a bug. If the ambition of the VSE is that "it should just work", then the default blend mode for Adjustment Layer should probably be Replace.
May 12 2022
@Philipp Oeser (lichtwerk) I'm sorry, my times as a code contributor are over.
May 10 2022
Does the problem persist if you uncheck mirror x?
It's a simple fix:
col = layout.column(heading="Mirror", align=True) col.prop(strip, "use_flip_x", text="X", toggle=True) col.prop(strip, "use_flip_y", text="Y", toggle=True)
May 7 2022
May 6 2022
Maybe if there is no active strip selected, the Linked Copy could make a copy of the current scene(with the active camera assigned). This is also a very useful option for storyboarding/previz because if VSE cache is switched off, the current 3d view will update live in the VSE if the frame is refreshed(or playhead is moved). A linked copy of the current scene as scene strip isn't an illegal operation afaik.
May 1 2022
What happens if you add a speed effect strip on the scene strip?
@Antonio Vazquez (antoniov) Is there a description of the optimal storyboarding workflow and needed changes somewhere? How does the new scene generating patches fit in? Is this it?
Apr 30 2022
Same here. On master.
Apr 28 2022
Very nice addition. I'm not sure the + icon is necessary?
Apr 24 2022
Apr 19 2022
When dragging into the preview, consider adding the new strip on the first empty channel on top. Adding it to the bottom channel and placing it behind the other channels, may not be what users expect:
Apr 17 2022
Apr 7 2022
Apr 2 2022
Apr 1 2022
Mar 31 2022
Mar 29 2022
Locking the channels doesn't seem to have any effect here.
Mar 25 2022
Mar 23 2022
Mar 22 2022
Mar 19 2022
The channel numbers exposed on the actual channels are quite important for functions like these since they are referring to the channel numbers(and not channel names):
If the user has edited the Channel header text and not kept the editable number, the above-mentioned functions will be very difficult - if not impossible - to use - keeping in mind there are now 128 optional channels.
So, maybe the channel numbers should be in an uneditable row for themselves(which also could be used to select Destination Channels on import)?
The Image Editor already has a Detect Image Sequences function, so it would be consistent to add one to the VSE import options too(downside is that the VSE import options are unavailable in the workspace embedded File Browser):
https://developer.blender.org/diffusion/B/browse/master/source/blender/editors/space_image/image_sequence.c$36
Mar 15 2022
@Philipp Oeser (lichtwerk) Was this intended to address T90856? If so, it doesn't seem to be solved for IDs in texts objects or text strips?
If the ambition only is to make the channel headers expose convenience buttons, with minimum height, you could look at the behavior of the toolbar, which is changing design depending on the space available, and finally collapse it, if it isn't big enough to carry any information/buttons:
Mar 14 2022
I've mentioned it before, but if you keep the VSE headers in consistency with the look and functionality of the NLA headers, they will look and feel like Blender UI:
Mar 10 2022
Waste of time... abandoned.
IIRC, the scale ratio is calculated on the first strip in the strip selection and indiscriminately applied to the following strips no matter if their ratio differs.
Mar 8 2022
Great the see the channel number limitation has been removed.
Mar 5 2022
Mar 1 2022
UI-wise it seems a bit counterintuitive to be able to create scene copies from within the properties of a scene strip.
Feb 28 2022
Feb 26 2022
Feedback from #VSE chat:
- It'll properly puzzle users that they are not able to scroll higher than channel 7, and they'll have to push a strip upwards to gain more channels. Can this be solved in a better way?
- Moving strip up or down in the top of the visible channels the zoom level should be adjusted to include that channel, but keep the lowest channel visible. This doesn't feel like moving a strip:
- The channel header area becomes empty/useless when it is too narrow. Should it be auto-collapsed, when it is too narrow?
- Use a checkbox icon instead of an eye, since the eye is for hiding things in the preview.
Reference:
- Use color icons only, not names too, as in the menu:
- Scrollbar isn't drawn to the bottom, even though you can't scroll further down:
- Use the UI colors of the sidebar:
- Do not use button backgrounds to show selection, the icons already have two states(Reference: NLA)
- Rounded corners of channel header backgrounds?
- Changing the color of the full channel header background, is too dramatic and will cause readability problems, use color icons instead, like in the sidebar:
- Make the channel header name one row and the buttons another, so they can be either stacked or side by side depending on the width and height of the channel header area.
- Channel Headers should not be drawn in Preview and Sequencer & Preview.
- Channel Header area needs a context menu of its own.
- Channel Headers should be selectable for batch-changing values of several channel headers in one go.
Feb 12 2022
@Francesco Siddi (fsiddi) Did you get around making a to-do for this?
Feb 10 2022
Feb 9 2022
Looks like the sync is kept. Maybe, in this case, trimming the strips in the Sequencer so the in and out points of the audio & video strips are aligned should be considered(and still have the extra frames available if needed):
Testing shows a strip offset:
Jan 27 2022
In the hope that this Movie Clip Preview patch, which just is a copy of the Image Preview code, will get into 3.1, I'll reopen this patch.
Jan 25 2022
Currently, Scene Strips have no proxies(as reported here) but also no caching, no prefetching, no thumbnails, no access to ex. 3d or compositor outputs in the same scene, and very poor performance.
Jan 18 2022
@Pablo Vazquez (pablovazquez) On a Nordic keyboard, accent grave is produced by pressing shift + the key to the left of backspace twice, and doing this, doesn't make the pie menu show up.
Ex. Swedish keyboard: https://upload.wikimedia.org/wikipedia/commons/thumb/e/e0/KB_Sweden.svg/2000px-KB_Sweden.svg.png
The Compositor Crop node actually comes with a crop gizmo, so maybe there is some code and design which can be reused?
Jan 17 2022
I'm not super familiar with the NLA, and it seems to be stuck with the same UI from before the Sequencer got handles(except the sidebar must have been added since), however, it does come with channel headers for lock, mute, box selection of channel headers(could be used for batch changing values) and even folding. For a 2. iteration of VSE channel headers, the folding could be used for opening and closing of Meta & Scene strips(or multi-channel audio) from within the current sequence(so no scene switching would be needed to reposition strips inside Meta&Scene strips).
Notice that the NLA headers have a lighter color with a dark background(like ex. the panels in the sidebar layout), which makes them look interactive, and in line with general Blender UI.
Considering all of the time spend on restricting Scene Strips, like in this case, maybe that time was better invested in trying to solve the problems of scene strips(like prefetch) and improve on their performance? Mind you, they are the only way to integrate working in the VSE with the rest of Blender, without rendering to file first.
Jan 14 2022
Interesting to see work on channel headers. I don't know if the NLA is going to be entirely redesigned at some point, but I guess the channel headers of the VSE properly could share basic code and designs with the NLA - or at least be a reference point?
Jan 11 2022
Jan 10 2022
If this operator is not going to get committed, the very basic Ripple Trim to Current Frame Left/Right can be implemented as simple macros: https://developer.blender.org/P2710
Dec 20 2021
Missing:
- Animation menu(Shortcut: I).
- Copy/Paste/Duplicate/Lock Transform/Mute/Move up&down in channels, Add Effects(Glow etc.).
- Crop tool.
- Text tool.
- Snap(boundingbox anchor to the grid?)
- Having both a Strip and an Image menu is a UI mess.
- Selection of overlaying images should be from the top channel and down.
- The outline is not fitting the source image, and is drawn on the "outside" so the bottom line disappears when using "Zoom to Fit":
- When moving elements outside the visible area, they're drawn under the dark area, so they simply disappear if you deselect them. They should be drawn on top of the dark area instead.
Looks nice. And good ways to distinguish the various guides. I hate to be the one who has to keep mentioning that if consistency is to be kept, then there are some safe area guides in the VSE too...
Dec 17 2021
Dec 14 2021
Dec 4 2021
Nov 30 2021
@Francesco Siddi (fsiddi) Why isn't this a valid solution, instead of crippling the Sequencer/Preview mode?
Nov 29 2021
Nov 26 2021
Nov 25 2021
Patch for Movie Clip thumbnails: D13305
Change the Image menu to Preview, since this makes it more clear that everything in the Preview is for manipulating the preview.
If it needs to be cut in stone, in Sequencer/Preview all functions relating to the Preview could be collected in a top-level menu called Preview:
Nov 24 2021
Menu clean-ups:
- Rename "Box Select" to Box Select Strips" and "Box Select(include handles)" to "Box Select Handles", since the first only allows selection of strips and the latter only handles.
- Remove redundant use of the word Strip in the "Strip" menus. Ex. "Snap Strips to Current Frame", also allows snapping of handles to the current frame, which isn't covered by the previous name.