Hi, good day,
I have a few workflow questions and feature requests regarding The Lighting Controller II, as well as one issue I’ve encountered:
1)Adding multiple generator buttons to a card
Is there a way to add multiple generator buttons to a card at once? Currently, adding buttons one by one requires repeatedly navigating back and forth, which can be time-consuming. The previous version of SweetLight allowed adding multiple buttons at once, which was much more efficient.
2)Direct RGB value entry / RGB faders
Is there a way to enter direct numeric values into the RGB color picker for RGB fixtures?
Alternatively, could an option be implemented to switch between the color picker and individual R, G, B faders, allowing for precise value entry and adjustment?
3)Multiple Child Windows
Is it possible to create and use multiple Child Windows simultaneously? If not, is this functionality planned?
4)Follow spot pan/tilt joystick mapping
Can the follow spot pan/tilt pad be mapped to a joystick or external controller axis?
5)Generic user-assignable faders
Would it be possible to implement a generic “Fader” option for fixture customization?
For example, if a fixture has a “Focus” channel, I would like to:
Add a generic fader labeled “Focus” in the fixture profile
Map that fader to a generic fader in the fader board
Use it to control the fixture’s focus channel directly
At the moment, only Dimmer and Speed faders appear to be supported.
6)Fixture response issue in version 0.1.31 (18 December 2025)
In version 0.1.31 (18 December 2025), fixtures appear correctly in the 3D window, but they do not respond to controls from the software. There is no visible movement or beam output when operating the fixtures.
I have tested this on two separate Windows computers, both exhibiting the same behavior. I have also verified that this is not related to my show file, as the issue persists when creating a new, independent light show in version 0.1.31 using fixtures directly from the fixture bank.
Thank you for your time, and I appreciate the continued development and improvement of SweetLight.
p.s: I’ve also noticed similar reports from at least one other user on the forum describing the same behavior in version 0.1.31, including lack of beam rendering and pan/tilt movement in the 3D View, even when testing with default lightshows.
Feature Requests & Fixture Response Issue – v0.1.31 (Windows)
Re: Feature Requests & Fixture Response Issue – v0.1.31 (Windows)
Hello,
Thank you for this report.
Please see below our answers.
1.
We do not understand this question, because the V9 and V_II software methods are similar:
- select the buttons with the check mark
- select the menu "Add selected buttons" in the Macro button
2.
This is currently not possible.
This is noted.
3.
Only one child window is possible.
This means you need 2 monitors to see the main window and the child window.
That said, the number of pages (= child window in V9) is not limited.
4.
This is currently not possible.
This is noted.
5.
The "Board Creator" allows to generate Preset buttons with a slider to go from min level to max level.
But this function does not work with a "pur" (no levels) channel.
This is noted.
6.
This is fixed in the new version 0.1.33 (Windows only).
Thank you for this report.
Please see below our answers.
1.
We do not understand this question, because the V9 and V_II software methods are similar:
- select the buttons with the check mark
- select the menu "Add selected buttons" in the Macro button
2.
This is currently not possible.
This is noted.
3.
Only one child window is possible.
This means you need 2 monitors to see the main window and the child window.
That said, the number of pages (= child window in V9) is not limited.
4.
This is currently not possible.
This is noted.
5.
The "Board Creator" allows to generate Preset buttons with a slider to go from min level to max level.
But this function does not work with a "pur" (no levels) channel.
This is noted.
6.
This is fixed in the new version 0.1.33 (Windows only).
Re: Feature Requests & Fixture Response Issue – v0.1.31 (Windows)
Thanks for the Reply..
RE:
1)Adding multiple generator buttons to a card
Is there a way to add multiple generator buttons to a card at once? Currently, adding buttons one by one requires repeatedly navigating back and forth, which can be time-consuming. The previous version of SweetLight allowed adding multiple buttons at once, which was much more efficient.
my question was not in reference to adding buttons to a macro button. (am not sure how to add images, so i will try to explain a bit more clearly.
1) Add Board
2) Add Buttons board
3) Add button
4) Add Generator button
5) Choose a Generator Project (only one can be selected/added at a time. So incases where multiple generator projects are to be added, steps 3 to 5 are to be repeated multiple times)
eg:
1) Add button
2) Add Generator button
3) Choose a Generator Project (button1)
1) Add button
2) Add Generator button
3) Choose a Generator Project (button2)
1) Add button
2) Add Generator button
3) Choose a Generator Project (button3)
and so on.. it would be greatly appreciated if we could select multiple generator projects at once, eg:
1) Add button
2) Add Generator button
3) Choose Generator Project/s (button1, button2, button3, etc)
Re:
3.
Only one child window is possible.
This means you need 2 monitors to see the main window and the child window.
That said, the number of pages (= child window in V9) is not limited.
yes i am aware that multiple monitors are needed. I currently run a two monitor setup, however, I am looking to build a 3 monitor setup. to accomplish this, i need at least two child windows in addition to the main window. The amount of pages isn't an issue. but would be grateful for at least 2 child windows.
RE:
1)Adding multiple generator buttons to a card
Is there a way to add multiple generator buttons to a card at once? Currently, adding buttons one by one requires repeatedly navigating back and forth, which can be time-consuming. The previous version of SweetLight allowed adding multiple buttons at once, which was much more efficient.
my question was not in reference to adding buttons to a macro button. (am not sure how to add images, so i will try to explain a bit more clearly.
1) Add Board
2) Add Buttons board
3) Add button
4) Add Generator button
5) Choose a Generator Project (only one can be selected/added at a time. So incases where multiple generator projects are to be added, steps 3 to 5 are to be repeated multiple times)
eg:
1) Add button
2) Add Generator button
3) Choose a Generator Project (button1)
1) Add button
2) Add Generator button
3) Choose a Generator Project (button2)
1) Add button
2) Add Generator button
3) Choose a Generator Project (button3)
and so on.. it would be greatly appreciated if we could select multiple generator projects at once, eg:
1) Add button
2) Add Generator button
3) Choose Generator Project/s (button1, button2, button3, etc)
Re:
3.
Only one child window is possible.
This means you need 2 monitors to see the main window and the child window.
That said, the number of pages (= child window in V9) is not limited.
yes i am aware that multiple monitors are needed. I currently run a two monitor setup, however, I am looking to build a 3 monitor setup. to accomplish this, i need at least two child windows in addition to the main window. The amount of pages isn't an issue. but would be grateful for at least 2 child windows.
Re: Feature Requests & Fixture Response Issue – v0.1.31 (Windows)
1.
Understood. This could be fixed with multi-selection files in the "open Generator files" window.
This is noted.
3.
We note that two child windows would be welcome for user with 3 monitors setup.
Thank you again for your comments.
Understood. This could be fixed with multi-selection files in the "open Generator files" window.
This is noted.
3.
We note that two child windows would be welcome for user with 3 monitors setup.
Thank you again for your comments.
Re: Feature Requests & Fixture Response Issue – v0.1.31 (Windows)
Pan & tilt have up to 65535 positions.4)Follow spot pan/tilt joystick mapping
Can the follow spot pan/tilt pad be mapped to a joystick or external controller axis?
Could you please tell us more about your wish ?
Could you show the item you wish our follow spot works with ?
Re: Feature Requests & Fixture Response Issue – v0.1.31 (Windows)
Thanks for reaching out..
am thinking more along line of using two rotary encoders (knobs) as opposed to a joystick.. 1 for the Pan and 1 for the tilt.
Basically adjusting the pan or tilt independent of each other.. I can set the tilt and freely pan left or right, keeping the same tilt
unless i adjust it. would be a nice touch for the generator as well.
am thinking more along line of using two rotary encoders (knobs) as opposed to a joystick.. 1 for the Pan and 1 for the tilt.
Basically adjusting the pan or tilt independent of each other.. I can set the tilt and freely pan left or right, keeping the same tilt
unless i adjust it. would be a nice touch for the generator as well.
Re: Feature Requests & Fixture Response Issue – v0.1.31 (Windows)
Thanks for the clarification — that makes sense.
In principle, using rotary encoders for pan and tilt control is an interesting idea. However, in practice, this type of controller can be quite tricky to support reliably.
The main issue is that there is no real standard for how endless rotary encoders send MIDI data. Different devices use different methods, which makes it difficult for us to ensure consistent and predictable behavior across all hardware.
We have already encountered compatibility issues with some existing products, which is why we have to be cautious with this type of implementation.
That said, do you have a specific controller model in mind, or a device that you are currently using ? If there is a well-defined reference, it may help us better evaluate what could be possible.
In principle, using rotary encoders for pan and tilt control is an interesting idea. However, in practice, this type of controller can be quite tricky to support reliably.
The main issue is that there is no real standard for how endless rotary encoders send MIDI data. Different devices use different methods, which makes it difficult for us to ensure consistent and predictable behavior across all hardware.
We have already encountered compatibility issues with some existing products, which is why we have to be cautious with this type of implementation.
That said, do you have a specific controller model in mind, or a device that you are currently using ? If there is a well-defined reference, it may help us better evaluate what could be possible.
Re: Feature Requests & Fixture Response Issue – v0.1.31 (Windows)
I would like them mappable to any of the knobs on an apc40 mk2..(but my total kit includes, 3 touch monitors, 1 apc mini mk2 and 1 apc40 mk2)
i understand that it may be a bit tricky, but it would be a nice step up for The Lighting controller II.
You have added follow spot, which i find is a nice touch. giving the user the flexibility to grab any moving fixture on
the fly and maneuver it as please..
but the practicality of the current maneuvering is the issue... it takes a bit of back and forth to get the fixture where you want. and you got
to constantly hold the mouse click while doing so, cause the moment you let go, if you don't click back in the
exact spot, the fixture jumps to the location of the new click.. now you have to do the dance all over again to get back to
where you need it to be.
side note..
the fact that we are having this dialogue, is already a plus in my books.. it shows that you not only listen to your users, but you engage them for
clarity rather than brushing off the idea.. all the best to you and your team,, and i look forward to the news of the update comining soon..
i understand that it may be a bit tricky, but it would be a nice step up for The Lighting controller II.
You have added follow spot, which i find is a nice touch. giving the user the flexibility to grab any moving fixture on
the fly and maneuver it as please..
but the practicality of the current maneuvering is the issue... it takes a bit of back and forth to get the fixture where you want. and you got
to constantly hold the mouse click while doing so, cause the moment you let go, if you don't click back in the
exact spot, the fixture jumps to the location of the new click.. now you have to do the dance all over again to get back to
where you need it to be.
side note..
the fact that we are having this dialogue, is already a plus in my books.. it shows that you not only listen to your users, but you engage them for
clarity rather than brushing off the idea.. all the best to you and your team,, and i look forward to the news of the update comining soon..