Virtual Console Sliders not stopping functions when at 0

Archive of the non-categorized posts related to the QLC+ technical support.
Please do not create new threads here, instead, use the categories above !
Post Reply
Tubby
Posts: 16
Joined: Fri May 29, 2015 10:06 am
Real Name:

Hi All,

I think I have found a bug with sliders in playback mode when they are in a solo frame (with or without mixing).

I am finding that unless the user moves the slider to 0, the function attached to it stays running even though QLC+ has set the slider to 0.
I think this was causing me problems on LTP channels in my normal workspace.

I have attached a simple workspace that shows this issue.

Steps to reproduce in frame "Mix sliders in playback = True" or "Mix sliders in playback = False":

[ 1 ] Check "Running Functions" find no functions are running.
[ 2 ] Move Slider 3 to 255
[ 3 ] Move Slider 2 to 255 - QLC+ reduces Slider 3 to 0.
[ 4 ] Check "Running Functions" find the functions mapped to slider 2 and 3 are running. I expected only the function mapped to slider 2 to be running as slider 3 is at 0.
[ 5 ] Move Slider 2 to 0
[ 6 ] Check "Running Functions" find the function mapped to slider 3 is running. Expected no running functions.
[ 7 ] Check DMX Values, find some LTP channels have been set to slider 3's functions values, expected them to stay at slider 2's function values.
Attachments
QLC+4.10.2b Slider Demo.qxw
(9.14 KiB) Downloaded 62 times
plugz
Posts: 637
Joined: Sun Apr 12, 2015 6:30 pm
Real Name: David

Hello,

You're right, this will be fixed soon.

I have a question, How do you «Check "Running Functions"» ?
I managed to see that the functions are running by adding a button for each function in the virtual console.
Tubby
Posts: 16
Joined: Fri May 29, 2015 10:06 am
Real Name:

Thanks for the quick response plugz.

I checked it by opening "Live edit a function", then selecting "Running Functions"
plugz
Posts: 637
Joined: Sun Apr 12, 2015 6:30 pm
Real Name: David

Tubby wrote: Thanks for the quick response plugz.
Thanks for the clear explanation + the attached workspace, you saved me a lot of time :)
Tubby wrote:I checked it by opening "Live edit a function", then selecting "Running Functions"
OK nice trick :D


The issue is now fixed in git :)
Post Reply