Error in Cuelist:
If we set the duration to "1H 11m 34s 967ms" - it's ok
But if we set more, Cuelist recounts:
Example :
"2H 0m 0s 0ms" = "0H 48m 25s 032ms"
Screenshots attached.
QLC 4.12.4
One device only (4-channel dimmer)
Regards!
Cuelist Duration Error
-
- Posts: 14
- Joined: Mon Nov 28, 2016 12:01 pm
- Real Name: Ralph
i have win10 64bit,
look on my workspace below.
I set the duration in "speed dial".
Up to 1H 11m 34s 967ms - everything is ok.
look on my workspace below.
I set the duration in "speed dial".
Up to 1H 11m 34s 967ms - everything is ok.
- Attachments
-
- qlc error.qxw
- (8.15 KiB) Downloaded 60 times
-
- Posts: 378
- Joined: Thu Apr 23, 2015 6:43 am
- Real Name: Ken Coughlin
I can't explain what's going on. On the functions tab, you can set the duration as high as you like.
It looks like it should work the way you're trying to do it, but is there a reason you're trying to set the duration this way?
It looks like it should work the way you're trying to do it, but is there a reason you're trying to set the duration this way?
-
- Posts: 14
- Joined: Mon Nov 28, 2016 12:01 pm
- Real Name: Ralph
Hello!
I set the "preset-buttons" in "Speed dial",
They are connected to the "Chaser" (and start the "lamp burn time"):
* 30 minutes
* 1h
* 2h
* Open (infinity)
In "Cuelist" I attach the same "chaser:".
By clicking a "preset-button" in "Speed dial", and then clicking "play" in "Cuelist",
a progress bar appears in "Cuelist" and the time to the end of the display counts down
QLC has an error:
If I run the button in "Speed Dial" 1h - in "cuelist" it is ok (duration is also 1h)
If I run the button in "Speed Dial" 2h - there is an error in "cuelist" (duration 36m50s065ms)
If I run the button in "Speed Dial" 3h - there is an error in "cuelist" (25m15s098ms)
Summary:
The last valid value is "1H 11m 34s 967ms".
Any value above is misread by "Cuelist".
See one by one - attachments.
-
- Posts: 14
- Joined: Mon Nov 28, 2016 12:01 pm
- Real Name: Ralph
-
- Posts: 14
- Joined: Mon Nov 28, 2016 12:01 pm
- Real Name: Ralph
1.
because additionally I want to be able to increase / decrease the time "manually", that is by clicking on the "+" or "-"
2.
because in the "cue list" I can see the time remaining until the end of the function
3.
because in "cue list" I can click on "pause" and then on "play" - then it does not count again, but from the pause value
because additionally I want to be able to increase / decrease the time "manually", that is by clicking on the "+" or "-"
2.
because in the "cue list" I can see the time remaining until the end of the function
3.
because in "cue list" I can click on "pause" and then on "play" - then it does not count again, but from the pause value
- sbenejam
- Posts: 557
- Joined: Sun Apr 12, 2015 6:28 pm
- Real Name: Santiago Benejam Torres
- Contact:
I tested your project. I think this is a bug. Setting duration from function editor works as expected. Fails setting duration from a SpeedDial Widget in Virtual Console.
-
- Posts: 14
- Joined: Mon Nov 28, 2016 12:01 pm
- Real Name: Ralph
- sbenejam
- Posts: 557
- Joined: Sun Apr 12, 2015 6:28 pm
- Real Name: Santiago Benejam Torres
- Contact:
I think the QLC+ developers will have to review and test it.
-
- Posts: 14
- Joined: Mon Nov 28, 2016 12:01 pm
- Real Name: Ralph
- sbenejam
- Posts: 557
- Joined: Sun Apr 12, 2015 6:28 pm
- Real Name: Santiago Benejam Torres
- Contact:
When Massimo has time to review the forum posts, he analyzes the severity of errors and resolves it when he can. I think this is a strange issue and no one has found it before, perhaps not everyone uses longer duration than hour eleven minutes of a chaser step.
- mcallegari
- Posts: 4528
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
I am reading this thread, don't worry.
I've added this to my TODO list.
Will keep you informed here when I find something
I've added this to my TODO list.
Will keep you informed here when I find something
-
- Posts: 14
- Joined: Mon Nov 28, 2016 12:01 pm
- Real Name: Ralph
Thank You, Massimo!mcallegari wrote: ↑Tue May 24, 2022 7:24 am I am reading this thread, don't worry.
I've added this to my TODO list.
Will keep you informed here when I find something
I can pay to fix and develop this feature.
I would also need:
* Adding "progress bar & progress time" directly in "Duration Widget" (then you wouldn't have to run the same in "Cuelist")
* Possibility to edit the appearance of elements in the "Duration Widget":
1) the size of buttons "+" and "-",
2) the size of the windows to enter the values "hours", "minutes", "seconds", miliseconds "
3) the size of buttons "presets"
4) standard variables - typeface, background color, font color)
5) selection of visible time components (show hours, show minutes, show seconds, show miliseconds) in the progress bar
6) "show" button "play / pause"
7) the ability to edit the size of the "play / pasue" button
Regards and have a nice day!
- mcallegari
- Posts: 4528
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
I have fixed the timing issue upstream
Unfortunately there is an issue (again) with Windows automated builds
I am checking what's wrong
Unfortunately there is an issue (again) with Windows automated builds
I am checking what's wrong
- mcallegari
- Posts: 4528
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
Windows TEST version available here:
viewtopic.php?f=12&t=3135
viewtopic.php?f=12&t=3135
-
- Posts: 14
- Joined: Mon Nov 28, 2016 12:01 pm
- Real Name: Ralph
Massimo,mcallegari wrote: ↑Sat Jun 11, 2022 11:32 am Windows TEST version available here:
viewtopic.php?f=12&t=3135
i love you!