- User Since
- Apr 30 2018, 2:53 AM (63 w, 5 d)
Tue, Jul 9
- Sequencer: add SequencerFadesClear and SequencerFadeAdd operators
- Add FadesAdd operator to the Add menu
- Capitalize names for menu entries
- Fix edge case when clearing keyframes
- Ensure the fade is at least 1 frame long
Mon, Jul 8
Thanks William, I'll update the diff when adjust last op's been added 🙂
There's code from @Peter Fog (tintwotin) to add the op to the menus. Is there a way to add him as a co-author of the diff or commits?
Thanks, I updated https://developer.blender.org/D5166 with your code.
Register the operators in the Add menu
I added the improvements I could based on @Peter Fog (tintwotin)'s feedback. It's ready for review now. I'd just need to know if the operator should work in frames instead of seconds?
Calculate a maximum fade duration, based on the shortest sequence
Rename bpy.types.Operator -> Operator
Fade to the next keyframe in the curve in the fade direction
Use a try/except block to catch ReferenceErrors
Wed, Jul 3
- Fade In/Out to/from the current level(at the next/previous frame of graph) and not the max level of the strip.: should the fade use the first keyframe on either side of the curve, or use the value right after the fade?
Fixed a typo
Tue, Jul 2
Improvement suggested by @Peter Fog (tintwotin):
I just put up a new patch as a suggestion to replace this one: https://developer.blender.org/D5166
It adds a flexible fade add operator, with hopefully more flexible code so we can keep improving it moving forward. It's a core operation when it comes to video editing so it should be rock-solid.
Mon, Jul 1
We've discussed this on the vse channel on blender.chat. I'm on it, wrote an operator with more features today. The code is almost ready, I'm just running out of time tonight to finish testing and open the diff. I'll open it tomorrow.
Sat, Jun 22
I think that preferably you should start creating new stuff, and realize in process that "if only I could tweak this exiting operator..." :)
Jun 13 2019
user has to save selection state, do stuff, and restore selection. Not a good practice IMO.
Jun 12 2019
Richard asked for some new operators or features we'd like to suggest as part of this project. I wrote and played quite a bit with the VSE with our add-on power sequencer. I've written operators that help to edit all kinds of content faster than with vanilla blender:
The idea was to make it possible for Python developers to contribute to the VSE more easily and maintain these operators. The operators being object-like, they're easier to write, read, and encapsulate in Python: in C you need several functions.
May 30 2019
I'd like to start contributing to the VSE itself instead of working on add-ons. But it's still not clear what the target is for the project, what are the intended or supported use cases, and which contributions would be welcome or not.
Jan 21 2019
Regarding the C core and Py shell idea: if we can contribute operators in Python, we'd work directly on Blender instead of our add-on Power Sequencer with my teammate Razvan. I'm in the middle of a Kickstarter campaign now so too busy to help, unfortunately, but we do all of our work with the VSE so we'd gladly contribute directly to Blender itself. 🙂
Thanks a lot for your work everyone!
Dec 19 2018
custom playback speeds must be supported. This is the main reason why this change is needed. Support in sequencer itself is separate task.
Nov 26 2018
Your usecase is already a little bit 'out of the usual' because the strips dont overlap (but instead are on the same channel and have "a bit of space between them").
Not sure how useful this really is? (You would have to describe in more detail why you need a setup like this)
Aug 31 2018
Sorry, forgot about this. But it's a quick to fix.
I will update this soon.
Aug 30 2018
This option properly should rename "Build JPEG quality" to "Bitrate percentage"
Aug 18 2018
I tested it in your custom build and it's a much welcome improvement! How about updating the scale when volume != 1.0? I use .wav audio samples and soundtracks that are normalized by default, and I lower their volume in the VSE. But the waveform still doesn't reflect that. Would that improvement be possible? It'd be much welcome for me 😄