First of all, thank you for a wonderful software package!
I think I found a bug, (and a workaround) in version 4.5.0.:
Running scenes using a button attached to a function, it appears that any fade-out timing that has been set will not engage unless at least one scene/function is already on. (and left on).
If only one scene is clicked on, the fade-in timing works fine, however clicking the button off results in an instant-off, rather than a fade out based on the set time.
Again the work around is another scene must also be on, and left on. In this case I created a dummy generic fixture, created a scene with it, attached it to a button, and just left it on during the show.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First of all, thank you for a wonderful software package!
I think I found a bug, (and a workaround) in version 4.5.0.:
Running scenes using a button attached to a function, it appears that any fade-out timing that has been set will not engage unless at least one scene/function is already on. (and left on).
If only one scene is clicked on, the fade-in timing works fine, however clicking the button off results in an instant-off, rather than a fade out based on the set time.
Again the work around is another scene must also be on, and left on. In this case I created a dummy generic fixture, created a scene with it, attached it to a button, and just left it on during the show.
It was indeed a bug. A regression introduced on 4.5.0.
I have fixed it and will be released with v4.5.1.
Yep. Just discovered this as well. Thanks for the fix. Great Prog.
PS Any idea when you'll have 4.5.1 ready?
Thanks