- User Since
- Apr 30 2018, 2:53 AM (55 w, 2 h)
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 😄