-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeline Rippled has no Effect #22
Comments
I will need some more information as it is working for me on blender 3.4: |
Sorry for being so late with the response, I just double checked just to make sure and seems like it was on me. I assumed holding vs pressing Alt would have the same effect, but apparently not. So it works if I select a strip then only press Alt, it works. Otherwise it does not. Although I did also stumble across another issue with Power Sequencer enabled, should I open another issue for that ? The TLDR is it seems to disable timeline ripple & parenting of strips. |
I'm not familiar at all with power sequencer, but it sounds like it is using its own variation on the grab function, or directly calling blender's built in grab function instead of vseqf's. Unfortunately, thats not really something I can do anything about on my end. A way to test if this is the case would be to try using a dedicated vseqf shortcut: alt+numpad5. There are a couple possible fixes: First, you can uninstall both addons, then install power sequencer first, then vseqf - whichever is installed last will override the shortcuts of the first one. Second, you can edit your shortcuts and manually assign shortcuts to the vseqf.grab operator. |
Hmm, I'll have to look into that second option, as for the first one though, Power Sequencer is bundled with Blender for a few versions now, so I definitely installed it second, I assume maybe it takes priority since it's bundled or something. |
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.
The text was updated successfully, but these errors were encountered: