snuq / vseqf Goto Github PK

arning: 'Scene_Tools_PT_sel_sim' doesn't have upper case alpha-numeric prefix
register_class(...):
Warning: 'Scene_Tools_PT_scene_tools' doesn't have upper case alpha-numeric prefix
register_class(...):
Warning: 'tot.mainmen_col' does not contain 'PT' with prefix and suffix
register_class(...):
Warning: 'tot.mainmen_colversion' does not contain 'PT' with prefix and suffix
register_class(...):
Warning: 'tot.mainmen_3d' does not contain 'PT' with prefix and suffix
register_class(...):
Warning: 'SceneBenchmark_Menu_TOT' does not contain 'PT' with prefix and suffix
register_class(...):
Warning: 'MaterialBenchmark_Menu_TOT' does not contain 'PT' with prefix and suffix
register_class(...):
Warning: 'ImageResizer_Menu_TOT' does not contain 'PT' with prefix and suffix
register_class(...):
Warning: 'tot.findin' does not contain 'PT' with prefix and suffix
register_class(...):
Warning: 'tot.actionsin' does not contain 'PT' with prefix and suffix
register_class(...):
Warning: 'TOT_MatB_UL_items' doesn't have upper case alpha-numeric prefix
register_class(...):
Warning: 'TOT_ImageResizer_UL_items' doesn't have upper case alpha-numeric prefix
Bypassing debug mode
Warning: property 'direction' not found in keymap item 'OperatorProperties'
Warning: property 'direction' not found in keymap item 'OperatorProperties'
Warning: property 'side' not found in keymap item 'OperatorProperties'
Warning: property 'side' not found in keymap item 'OperatorProperties'
Warning: property 'side' not found in keymap item 'OperatorProperties'
Warning: property 'ripple' not found in keymap item 'OperatorProperties'
Warning: property 'side' not found in keymap item 'OperatorProperties'
Warning: property 'ripple' not found in keymap item 'OperatorProperties'
Warning: property 'side' not found in keymap item 'OperatorProperties'
Warning: property 'ripple' not found in keymap item 'OperatorProperties'
Warning: property 'side' not found in keymap item 'OperatorProperties'
Warning: property 'ripple' not found in keymap item 'OperatorProperties'
Warning: property 'use_unselected' not found in keymap item 'OperatorProperties'
Warning: property 'use_unselected' not found in keymap item 'OperatorProperties'
Warning: property 'speed_factor' not found in keymap item 'OperatorProperties'
Warning: property 'speed_factor' not found in keymap item 'OperatorProperties'
Warning: property 'speed_factor' not found in keymap item 'OperatorProperties'
Warning: property 'side' not found in keymap item 'OperatorProperties'
Warning: property 'side' not found in keymap item 'OperatorProperties'
Warning: property 'preset' not found in keymap item 'OperatorProperties'
Warning: property 'speed' not found in keymap item 'OperatorProperties'
Warning: property 'speed' not found in keymap item 'OperatorProperties'
Warning: property 'speed' not found in keymap item 'OperatorProperties'
Warning: property 'speed' not found in keymap item 'OperatorProperties'
Warning: property 'speed' not found in keymap item 'OperatorProperties'
Warning: property 'select_mode' not found in keymap item 'OperatorProperties'
Warning: property 'gap_remove' not found in keymap item 'OperatorProperties'
Warning: property 'select_mode' not found in keymap item 'OperatorProperties'
Warning: property 'gap_remove' not found in keymap item 'OperatorProperties'
Warning: property 'select_mode' not found in keymap item 'OperatorProperties'
Warning: property 'gap_remove' not found in keymap item 'OperatorProperties'
Warning: property 'select_mode' not found in keymap item 'OperatorProperties'
Warning: property 'gap_remove' not found in keymap item 'OperatorProperties'
Warning: property 'select_mode' not found in keymap item 'OperatorProperties'
Warning: property 'gap_remove' not found in keymap item 'OperatorProperties'
Warning: property 'select_mode' not found in keymap item 'OperatorProperties'
Warning: property 'gap_remove' not found in keymap item 'OperatorProperties'
Warning: property 'select_mode' not found in keymap item 'OperatorProperties'
Warning: property 'gap_remove' not found in keymap item 'OperatorProperties'
Warning: property 'select_mode' not found in keymap item 'OperatorProperties'
Warning: property 'select_mode' not found in keymap item 'OperatorProperties'
Warning: property 'keep_audio' not found in keymap item 'OperatorProperties'
Warning: property 'type' not found in keymap item 'OperatorProperties'
Warning: property 'type' not found in keymap item 'OperatorProperties'
Warning: property 'type' not found in keymap item 'OperatorProperties'
Warning: property 'side' not found in keymap item 'OperatorProperties'
Warning: property 'side' not found in keymap item 'OperatorProperties'
Warning: property 'is_removing_transitions' not found in keymap item 'OperatorProperties'
Warning: property 'is_removing_transitions' not found in keymap item 'OperatorProperties'
Warning: property 'delete_selection' not found in keymap item 'OperatorProperties'
Warning: property 'delete_selection' not found in keymap item 'OperatorProperties'
Warning: property 'concatenate_all' not found in keymap item 'OperatorProperties'
Warning: property 'is_towards_left' not found in keymap item 'OperatorProperties'
Warning: property 'concatenate_all' not found in keymap item 'OperatorProperties'
Warning: property 'is_towards_left' not found in keymap item 'OperatorProperties'
Warning: property 'concatenate_all' not found in keymap item 'OperatorProperties'
Warning: property 'is_towards_left' not found in keymap item 'OperatorProperties'
Warning: property 'concatenate_all' not found in keymap item 'OperatorProperties'
Warning: property 'is_towards_left' not found in keymap item 'OperatorProperties'
Warning: property 'direction' not found in keymap item 'OperatorProperties'
Warning: property 'trim_target_channel' not found in keymap item 'OperatorProperties'
Warning: property 'direction' not found in keymap item 'OperatorProperties'
Warning: property 'trim_target_channel' not found in keymap item 'OperatorProperties'
Warning: property 'direction' not found in keymap item 'OperatorProperties'
Warning: property 'trim_target_channel' not found in keymap item 'OperatorProperties'
Warning: property 'direction' not found in keymap item 'OperatorProperties'
Warning: property 'trim_target_channel' not found in keymap item 'OperatorProperties'

The parenting bug where all audio strips get parented to one video strip doesn't happen always, it seems to be triggered when opacity keyframes are added or removed or when using Shift+S on any strip, and always when the playhead is on frame 1.
The 2nd bug is about opacity keyframes created even when a quick fade operation is canceled.
The 3rd is about quick fade working even when disabled.

buggy.zip

Hey, this looks amazing. I was just wondering if you plan on developing it for Blender 3.x. It seems to give a lot of add-on developers trouble, but I would appreciate it. I donated a bit to help you out. Cheers.

Hello, today's release of Blender 3.5 solid release the console outputs this:
AttributeError: 'NoneType' object has no attribute 'areas'
Traceback (most recent call last):
File "C:\Users\3DCompositor\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\VSEQF-meter_only_init_.py", line 55, in frame_step
vu_meter.vu_meter_calculate(scene)
File "C:\Users\3DCompositor\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\VSEQF-meter_only\vu_meter.py", line 83, in vu_meter_calculate
for area in bpy.context.screen.areas:
AttributeError: 'NoneType' object has no attribute 'areas'
Traceback (most recent call last):
File "C:\Users\3DCompositor\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\VSEQF-meter_only_init_.py", line 55, in frame_step
vu_meter.vu_meter_calculate(scene)
File "C:\Users\3DCompositor\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\VSEQF-meter_only\vu_meter.py", line 83, in vu_meter_calculate
for area in bpy.context.screen.areas:
AttributeError: 'NoneType' object has no attribute 'areas'
Traceback (most recent call last):
File "C:\Users\3DCompositor\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\VSEQF-meter_only_init_.py", line 55, in frame_step
vu_meter.vu_meter_calculate(scene)
File "C:\Users\3DCompositor\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\VSEQF-meter_only\vu_meter.py", line 83, in vu_meter_calculate
for area in bpy.context.screen.areas:
AttributeError: 'NoneType' object has no attribute 'areas'

...
and the error keeps repeating in the console until blender crashes.

This is all there is left of the VSE menus anter a removal of VSEQF, making the VSE unuseable:

I think you should try to figure out how to execute space_sequencer.py as part of the uninstallation process to restore the original vse menus.

I cut an audio strip in 3 pieces and move the rightmost strip a bit away.
Then I select the middle strip and hit Ctrl + K to open the Cut menu and select ripple delete.
Blender crashes.

As the title describes, I've used the master version and the released version both to no avail with the VSE, I am on a bit of a later version attempting to do so (3.4 to be exact) and nothing happens when trying to use the feature, besides the default behaviour of it snapping back to the original position.

This has been an issue for a while, I don't have specific version numbers. but I just recently attributed it to VSE quick functions, disabling the add-on fixes the issue, but the add-on is so useful I don't want to live without it!

behaviors observed. I'm going to use move (g) as an example, but I see the same behavior on just about any shortcut key.
start with the strip unselected, click the strip to select it and press g. nothing happens. the strip does not go into move mode.
to get around the problem I find you must interact with the mouse before clicking g. if you click a second time, or move the mouse (within or out of the strip doesn't matter) the g key then works.

this behavior I see is consistent, there are never situations in which this doesn't happen. if I turn VSEQF off, this problem fixes itself, you can click on a strip, press g, and simply move it as expected. turn VSEQF back on, the bug returns.

this works the same way for all kinds of strips, video, audio, modifiers etc. it also affects the strip end handles in the same way. it affects almost all keyboard shortcuts not just move. for example if I try to add a modifier to a strip, click the strip press SHIFT+A, nothing happens. if I select the strip, then move the mouse (even a little) press SHIFT+A the context menu appears like normal.

one more note, the shortcut keys continue to be disabled until the mouse moves, meaning:
select a strip then take your hand off the mouse so it does not and has not moved.
press any short cut key or combination of keys as many times as you want, none of them have any effect.
move the mouse,
repeat the above, the shortcuts all work again.

This may seem like such a small issue, but I encounter this problem constantly when using the VSE, apparently the way I work the computer I click on a strip and attempt to use shortcut keys right away without moving the mouse at all, while VSEQF is enabled, it causes those keys to have no effect.

I have updated to the latest version of VSEQF, this is blender 3.0 on Ubuntu 18.04. the problem existed for the last several releases of blender and VSEQF at least.
I also tried to turn off all VSEQF features that I don't routinely use to see if its a problem with any function in particular. auto parenting, quick markers, quick tags, quick cuts, compact edit panel, quick three point etc all turned off. the behavior still exists.

I installed the plugin and everytime i try to click into the Sequencer this error occurs:

Traceback (most recent call last):
  File "C:\Users\Philipp\AppData\Roaming\Blender Foundation\Blender\2.82\scripts\addons\VSEQF-2_82_2\grabs.py", line 322, in invoke
    self.click_mode = context.window_manager.keyconfigs.active.preferences.select_mouse
AttributeError: 'NoneType' object has no attribute 'select_mouse'

location: <unknown location>:-1

Makes this plugin unusable. Since that code is not changed for 2 years now, i suspect i have something wrongly setup.

Something i found from quick googling: https://developer.blender.org/T59064

If you add these two lines to unregistering, the original menus will be restored:
bpy.ops.script.python_file_run(filepath= bpy.utils.resource_path(type="LOCAL")+"\\scripts\\startup\\bl_ui\\space_sequencer.py") bpy.ops.script.reload()

Right clicking in sound strip header with a 0 frames fade and adding a fade in throws this error:

Same thing with a 0 frames long Fade out(with no existing fade on the strip).
Maybe the default fade value(in the menu) should be one sec(according to the current settings?)

The fade menu could be added to the context menu and the Add menu?

This error is displayed every time I grab strip by the ends and try to move it, it still moves after the error, but it pops up every time. in 3.4 and 3.5 too

Python: Traceback (most recent call last):
  File "C:\Users\admin\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\VSE Quick Functions\grabs.py", line 606, in modal
    ripple_offset = move_sequences(context, self.starting_data, offset_x, offset_y, self.grabbed_sequences, ripple_pop=self.ripple_pop, fix_fades=False, ripple=self.ripple, move_root=False)
  File "C:\Users\admin\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\VSE Quick Functions\grabs.py", line 175, in move_sequences
    move_sequence(context, sequence, offset_x, offset_y, data.select_left_handle, data.select_right_handle, data.channel, data.frame_start, data.frame_final_start, data.frame_final_end, ripple=ripple, fix_fades=fix_fades, only_fix=not move_root)
  File "C:\Users\admin\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\VSE Quick Functions\grabs.py", line 128, in move_sequence
    move_sequence_right_handle(context, sequence, offset_x, new_channel, start_frame_final_end, fix_fades=fix_fades, only_fix=only_fix)
  File "C:\Users\admin\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\VSE Quick Functions\grabs.py", line 94, in move_sequence_right_handle
    if new_end <= sequence.frame_final_start + 1 + sequence.frame_still_start:
AttributeError: 'ImageSequence' object has no attribute 'frame_still_start'. Did you mean: 'frame_final_start'?

Could the .frame_start value be used for showing sync, when a movie and a sound strip with the same basename are parented and .frame_start match, by changing the color of the parent line to ex. green(as in green-light go) in that case?

Is the Speed Step widget needed in the header? Or maybe it could be moved into the Time Line header?

Vertical zoom can be set like this: https://devtalk.blender.org/t/on-view2d-zoom-in-out/3563/4

Maybe you could add the Quick Cuts menu to the Strip menu? It's more logic to find edit operations in the menus, than in the sidebar, imo. As a rule of thumb, keep strip&tool settings in the sidebar and edit functions in the menu. The various VSEQF pop-up menus maybe also should be accessible from the menu, so their short-cuts will be visible in the UI.

Should the Timeline menu(from the Quick Cuts menu) be added to the context menu for right clicking in empty time line area too? Could be added to the View menu too.

Maybe the Quick Cuts menu would be faster to read if there are sub menus for Left/Right options and the icons where removed(in native Blender only Add menu entries are allowed icons).

Playhead is now the official name for the previous called Time Cursor(See the select menu) - VSEQF is using Cursor as name

It is very hard to find the 3 point Edit function in the bottom of the left sidebar in the File Browser pop up, maybe it could be moved to the right sidebar instead(in pop up and not in VSE workspace)?

To ease the use of 3 point edit, when importing the clip, and no clip editor is found, the preview area could be split and the right sidebar of the clip editor could be auto opened(left closed?) and the the set in/out function is auto executed(This will save users a lot of steps).

Maybe it would be better to move the In/Out lines to the bottom, so they won't collide with the zoom gizmo?

Having in and out on the same line would be more elegant, but I guess that this is the only way to get it to work?

Maybe timecode layout could be used in the panel instead? (to save vertical space)

In Avid the two ways to add a strip is by insert(as it is in VSEQF(respecting sync)) and overwrite, which cuts a hole in the current strip and add the new strip into the old strip - I don't think this it currently possible?

BTW. I posted about your draw volume level feature on Twitter, and it is getting a lot of love: https://twitter.com/rintworin/status/1207203074621792256

I'm getting this error when trying to enable the add-on in the Preferences menu:

So nice with the gifs. Really shows some of the power of your add-on. Looking forward to try the draw-volume function.

After installing, at the moment of enabling the addon, the following error appears: "... already registered as a subclass ..."

Hello Snug. Thanks for taking the effort to update the quick function addon for blender 2.8. I been using 2.79 for Blender 2.79 for quite along time and its working great

I decided to venture into blender 2.8 (2.81 the current as of the writing of this post). I followed the same old procedure to add addons. For some reason after the installation the addon doesn't show up in preference >> Addons list.

I had no problems installing other third party addons such as VSE_Transform_Tool in the new blender Evee

I did go through the read me file for VSEQF 2.81. in case I could have missed something, also updated to 2.81a in case it will help, no luck so far

Further information that might help

I have both blender 2.79 and 2.81a installed side by sid

With 2.79 installed from windows 64 setup version and 2.81a installed as portable unzipped into a separate folder

Intend to remove 2.79 once I completely get used to the new one, different workflow, some older addons compatibility issues plus being in the middle of developing blender course based on 2.79. so don't want to through away the old version just yet

Anyway mentioning this in case multiple blender versions could be causing potential conflict

Best Regards
Ahmed Anis

This is less of an issue but I can't find another way to make a comment/suggestion anywhere. (Is there a better way?)

But mostly I was hoping "Frame Selected" could be added to the Q menu. I don't have a numpad so I use to use Q for my quick favorites menu which previously only had the "Frame Selected" button. It was ultra useful and now this new Q menu is more useful, but it lacks my beloved Frame Selected button.

I'll be happy to just create my own version if I need to, but I figured this may be beneficial to others as well.

Doesn't work for me(I'm in left select mode).

When pressing V the text in the header notifies me about the keyframe mode, but nothing happens when pressing(left mouse) and dragging - nothing is being drawn.

I can leave the mode with right click.

BTW. maybe this mode can be added to the sound strip context menu?

When ripple deleting a strip in channel 1 the strip above in channel 2 moves up into channel 3 and the rest of the strips in channel 2 is rippled to the left. The strips in channel 2 should be untouched when ripple deleting a strip in channel 1.

Watch this gif for more explanation:
https://devtalk.blender.org/uploads/default/original/2X/5/589478b28d481eb8860dffb2422fd845f584100a.gif

I read the whole documentation and tried to test everything on the Blender 4.0 version, here's what I found:

• ripple moving strips moves locked strips too
• shift+m > add tag at cursor error
• zoom (to timeline, cursor) error + it adds a vseqf-temp-zoom strip
• file browser > import to clip editor not working
• features work even when disabled in the addon preferences
• auto parent audio to video : not working when new clip is dragged (it should be a global setting)
• when parent is duplicated, child is not
• Grab Multiple With Right-Click Drag > no option in settings menu?
• Making Meta Strip Additions (I don't understand this part)
• is the delete confirmation necessary? I prever the default VSE delete without confirmaion
• it's confusing when the addon and documentaion say Sequence instead of Strip
• selected to cursor seems to be the same as selected beginning to cursor
• error when 'follow cursor' button is enabled (and this feature is not mentioned in documentation)
• full timeline setup doesn't move the markers along with strips when ripple markers is enabled

I'm getting this error when left clicking in left click mode(ran the add on from the text editor and didn't install it):

Here is the error report:

Traceback (most recent call last):
  File "D:\Tools\Models\Blender\App\Blender64\4.0\scripts\modules\addon_utils.py", line 364, in enable
    mod = importlib.import_module(module_name)
  File "D:\Tools\Models\Blender\App\Blender64\4.0\python\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "D:\Tools\Models\Blender\Data\user_scripts\addons\VSEQF-4_0_1\__init__.py", line 55, in <module>
    from .addon_updater import Updater as updater
  File "D:\Tools\Models\Blender\Data\user_scripts\addons\VSEQF-4_0_1\addon_updater.py", line 30, in <module>
    import ssl
  File "D:\Tools\Models\Blender\App\Blender64\4.0\python\lib\ssl.py", line 99, in <module>
    import _ssl             # if we can't import it, let the error propagate
ImportError: Module use of python311.dll conflicts with this version of Python.

Hello & thanks for all you've done! It's my first time using the addon, and these are some issues I spotted in the 4.0 version.

Drawing a volume curve is a really cool feature, but I've run into a couple issues.

Firstly, the range of the drawing extends up into the header. I keep trying to click to move the playhead back, and I end up setting that spot to +2.8 or so (depending on zoom levels). I also wish that I could play the sequence without exiting draw mode. If drawing while playing would cause issues, there are a couple options to avoid that:

• Disable drawing while video is playing
• have playing automatically exit draw mode.

The other problem I have is that I typically want volume to return to exactly 1 after I duck or boost a section, and I don't see an easy way to do that. There are a few ways I could see facilitating this:

• A 10%-increment snapping modifier (Possibly problematic depending on how frequently keyframes are placed? Maybe it could limit keyframe placement as well, so one ends up with something like a line graph rather than a staircase?)
• A mode that works like an eraser to reset values to 1
• Have 1.0 be the limit by default, and use a modifier to allow boosting above that

Some other features that would be handy:

• Context menu option to clear all volume keyframes in a selected sequence
• Hear sound at the volume you're drawing when audio scrubbing is turned on
• Modifier key to draw Pan or Pitch instead of volume

By the way, thank you for responding about 3.x support so quickly. This is an amazing add-on. Very exciting.

Does this update exist?

I'm seeing this Err in my console during baking a cloth+ rigid body simulation. I believe it is because I do not have the VSE open on screen. I'm guessing this just needs an exception pass added in for the cases where the user isn't actively using the VSE.

Error in bpy.app.handlers.frame_change_post[2]:1s), ETC: 5m 42s
Traceback (most recent call last):
File "C:\Users<USERNAMEREDACTED>\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\VSEQF-4_0_1_init_.py", line 747, in frame_step
vu_meter.vu_meter_calculate(scene)
File "C:\Users<USERNAMEREDACTED>\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\VSEQF-4_0_1\vu_meter.py", line 84, in vu_meter_calculate
for area in bpy.context.screen.areas:
^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'areas'

Not bugs, but a little feedback:

Opening it, again totally impressed by how much you managed to add to your toolset.

Maybe I just become accustomed to have box select as default left click(in open space) behavior, but I'm missing it in VSEQF.

If audio strips aren't aligned directly under their parented movie strip, maybe the attachment line could get a different color like red, to signify that the audio may be out of sync.
(I thought first that the small number inside the strips is the sync offset(it was next to the attachment line), but then realized that it was the duration.

Grab(under strip) is now called 'Move' in 2.80. The number is written on top of the Grab word when 20+ channels are shown and the strips are narrow.

Are Transitions available in the context menus?

The snap functions in the strip menu, maybe could be attached to the Transform menu(there there also are snap to playhead functions). SEQUENCER_MT_strip_transform

I think I would move the Quick Function Settings into the header after Strips. The same goes for Quick Cuts. They deserve to be full menus in the header. The menus will works as a representation of the included functions/tools, event though people access them through context menus or the panel.

Tags in the Right Click Menu seems to be empty?

Love the Quick List. Maybe the filename could be enabled/disabled to make it more clear what strip is selected? (maybe instead of the outline, which makes the list move on selection?)

In the sidebar, I think you should keep the strip properties related stuff in the Strip panel, but move the rest into a Tools tab, so the strip panel will not become too long. And tags and markers could have a tab of their own.

All for now. Congratulations on your most excellent add-on.

Should be fairly effortless to make a donation wallet, BTC donation is cumbersome because the transaction fees are so high and all the money is public, so as of now it's fairly unusable for "internet money" reasons like this one.

Markers should be affected by ripple edits. I can't think of a case where I would want a marker to stay where it was when the thing it marked got moved back.

When dragging markers, it would be useful to snap (possibly via a modifier) to cuts and the current frame. I see that holding Ctrl snaps movement to full-second increments, which is interesting but my initial thought is that it might be better to snap to full seconds on the timeline. Lastly, if there's a "Jump Cursor to This Marker" menu option, the opposite would also be nice.

Another useful feature would be the ability to copy the marker list to the clipboard. YouTube chapters are defined by listing timecodes in the video description, starting with 00:00. It would be very convenient for a YouTube workflow if one could just paste those in.