New VSE Reworked feature: ‘Concatenate’ aka. Extract gaps after selected strips.
The old Extract Gap(s) functions only works when there are gaps in all channels vertically, meaning you can’t remove a gap if there isn’t a gap above and below. Should I remove them and just keep this new one?
Here’s a demo showing the problem of first the two old ones and then the new(last):
If I may just add one thing…
I’m a game artist, and I do a lot of character lipsync animation in Blender, so seeing the waveform of an audioclip in the sequence editor is crucial to my work.
However, showing the waveform hides the filename of an audioclip, and I need to see both at the same time, so that I can immediately tell which audioclip is which. I’m not talking about the full file path but just the name. The N-panel already shows the full path and that’s perfectly sufficient.
So, hopefully there’s a chance you people will make it possible for filename and waveform to be shown at the same time. Even if they’re overlapping, that would be totally fine.
The work we’re doing here is limited to what we can change in two blender native python scripts. One script deals with the layout of the menus and n-panel and the other with minor functions.
The look of the strips can’t be changed in these scripts, so you better add your suggestion to right-click-select.
I didn’t realize the script was part of an addon package. When I install the entire Amaranth package it works.
However, what this script does is display the name of the currently selected/viewed clip inside the header of the sequencer window. And it works for image clips only, not for audio or video.
What I really wanted was something like this:
But I guess that’s just not possible without significant changes to Blender’s C++ core.
Thanks for helping me realize this. And I’m sorry to have bothered you. I’m still figuring out how this forum is structured…
If it’s possible for image clips then I think it should be possible for the otheres, too. Why not submit the feature request to the amaranth add-on github issue tracker?
I’ve started to trying to convert the VSE Sidebar into one column and move the most important elements to the top. Are there any objections to this work?
I think Image offset and Image Crop properly should go to the Edit Strip too.
Maybe move Filter above Strip Input.
Data was originally called Info, but in order to move it down I had to rename it. Maybe it should be under Proxy too? The text-labels aren’t working that well in Data. Any ideas?
Alrighty, I’m as far with converting the VSE panels to 2.80 style, as I can get without help.
Codewise, I’ve only uncommented stuff - so it was quick to go back to having functions where they originally were. So the script does need a round of clean up all the uncommented stuff. However, there are a few things I need help with.
Download the VSE Reworked files from here:
Follow the installation instructions. In the Blender 2.80 Text Editor you’ll need to also open: “\2.80\scripts\startup\bl_ui\properties_grease_pencil_common.py” and “2.80\scripts\startup\bl_ui\space_time.py” in the Text Editor to avoid errors.
Hello, when i try to run the script “space_sequencer_panel.py”, i receive this error ( last Blender Build aca13040dac Linux ):
Traceback (most recent call last):
File "/space_sequencer_panel.py", line 23, in <module>
ModuleNotFoundError: No module named '__main__.properties_grease_pencil_common'; '__main__' is not a package
Error: Python script fail, look in the console for now...\
“sequencer.py”, “space_sequencer.py” and “vse_keymap.blend.py” seem to work well
You need to do this too: If you want to run the space_sequencer_panel.py from the Blender 2.80 Text Editor you’ll need to also open: “\2.80\scripts\startup\bl_ui\properties_grease_pencil_common.py” “2.80\scripts\startup\bl_ui\space_time.py” in the Text Editor to avoid errors.
There are some places where it could be a bit more concise. For example, where it says Trim Duration, you can inline that with Start, so it says Trim Duration Start and then End on the next line. Refer to other places in Properties where we do this, like Location X, Y, Z and others.