Drivers not working for Video Sequence Editor #42240

New Issue

Tobiasz Karoń · 2014-10-15T14:04:22+02:00

Tobiasz Karoń commented

2014-10-15 14:04:22 +02:00

System Information
KXStudio, nVidia GeForce 310M w/ 1GB of RAM.

Blender Version
Broken: 2.72 and possibly all previous)
Worked: none I know of

Short description of error
Drivers don't affect VSE clips. I'd expext them to do so, or to be disabled (not possible to assign to VSE controls) if they are not expected to work this way.

Exact steps for others to reproduce the error

Run Blender;
Switch to Video Editing UI preset;
Add a Color clip (Add > Effect strip > Color);
Right click on the strip's Color swatch to open the context menu;
Select "Add Driver";
Press Alt+A to play the animation.

Demo project: unfa-NoDriversVSE-01.blend

The default driver creates a linear rising function that should make the black fade into white or immediately switch to white (values 1,1,1 for RGB). It doesn't happen, though.

**System Information** KXStudio, nVidia GeForce 310M w/ 1GB of RAM. **Blender Version** Broken: 2.72 and possibly all previous) Worked: none I know of **Short description of error** Drivers don't affect VSE clips. I'd expext them to do so, or to be disabled (not possible to assign to VSE controls) if they are not expected to work this way. **Exact steps for others to reproduce the error** 1. Run Blender; 2. Switch to Video Editing UI preset; 3. Add a Color clip (Add > Effect strip > Color); 4. Right click on the strip's Color swatch to open the context menu; 5. Select "Add Driver"; 6. Press Alt+A to play the animation. Demo project: [unfa-NoDriversVSE-01.blend](https://archive.blender.org/developer/F116965/unfa-NoDriversVSE-01.blend) The default driver creates a linear rising function that should make the black fade into white or immediately switch to white (values 1,1,1 for RGB). It doesn't happen, though.

Tobiasz Karoń commented

2014-10-15 14:04:22 +02:00

Changed status to: 'Open'

Tobiasz Karoń commented

2014-10-15 14:04:22 +02:00

Added subscriber: @TobiaszunfaKaron

Joshua Leung commented

2014-10-16 14:14:25 +02:00

Changed status from 'Open' to: 'Archived'

Joshua Leung closed this issue

2014-10-16 14:14:25 +02:00

Joshua Leung self-assigned this 2014-10-16 14:14:25 +02:00

Joshua Leung commented

2014-10-16 14:14:25 +02:00

Not a bug - You just haven't set up the drivers correctly :)

Unlike animation (where the curves represent the value (y) for the animated property with respect to time (x)), drivers let you take some combination (e.g. using some python expression) of input values (i.e. "driver variables") as your x value instead.

To get your intended effect, you'd want the drivers to use an expression like:

 frame / 255

where 255 is how long you want the transition to take (since colors are represented as floats - i.e. decimals between 0 and 1)

Not a bug - You just haven't set up the drivers correctly :) Unlike *animation* (where the curves represent the value (y) for the animated property with respect to time (x)), *drivers* let you take some combination (e.g. using some python expression) of input values (i.e. "driver variables") as your x value instead. To get your intended effect, you'd want the drivers to use an expression like: ``` frame / 255 ``` where 255 is how long you want the transition to take (since colors are represented as floats - i.e. decimals between 0 and 1)

Tobiasz Karoń commented

2014-10-16 23:07:41 +02:00

Thanks :D
May I just ask - If I just wanted to get noise input for a given parameter of a VSE strip, what should I do?

Thanks :D May I just ask - If I just wanted to get noise input for a given parameter of a VSE strip, what should I do?

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Drivers not working for Video Sequence Editor #42240