This is directed to the developers and company of DasLight
It seems you have lost touch with the community and what people really are looking for in your software for DL5. Your software feels incomplete in comparison to others like SunLite 3 and taking out some vital features DL4 already had shows you don't know what the community wants. Start interacting with the community more and listen!
Here is what we want:
Multi Associations for Touch buttons, faders, and encoders!
Be able to assign associations to buttons, faders, and encoders made in touch edit like DL4
Touch button, fader, and encoder Priority ranks (master, releases)
Banks Master Controls!
Live mode resets ( you have the "save to scene" from live but no reset all )
buttons on the Daslight control box to be controlled like a MiDi controller with the program and not just standalone.
There are much more I'm sure others want to see. Please Listen to your community more!
DL5 Developers
Re: DL5 Developers
Hello,
Thanks for raising this thread.
- Multi associations for Touch controls is possible already, if you right click on an existing mapping, then click 'Duplicate'- you can then assign the function to a new Touch control.
- The mapping function for Touch control is indeed different from Daslight 4, this is because the Daslight 4 method had it's own set of issues which we tried to eradicate with this new method. I know some prefer the D4 method, and some prefer the D5- I think it's a learning point for us to figure out exactly what is good, and what isn't about both and look to combine more of what's good going forwards.
- Touch function priority and releases is an interesting idea, and isn't one I've heard before. I'll log it into our suggestions list for consideration going forwards.
- Regarding Bank Master controls- could you be more specific as to what exactly you are referring to? I will mention in case it's helpful- it is possible to do a lot of 'Bank' controls through the mappings screen, so if for example you want to set the Speed control dial of all scenes in a Bank to the same Touch dial- you can do this by setting the 'Target' to 'Bank'.
- Live Mode resets can be done using the 'Reset all beams' or 'Reset selected beams' buttons (found immediately right of the beam on/off and centre beam buttons).
- It is possible to use the buttons on the DVC controller as a MIDI controller, you need to go to the Mappings > Ports mappings screen- then use this function in the same way as you would with a MIDI controller.
Kind regards,
Will
Thanks for raising this thread.
- Multi associations for Touch controls is possible already, if you right click on an existing mapping, then click 'Duplicate'- you can then assign the function to a new Touch control.
- The mapping function for Touch control is indeed different from Daslight 4, this is because the Daslight 4 method had it's own set of issues which we tried to eradicate with this new method. I know some prefer the D4 method, and some prefer the D5- I think it's a learning point for us to figure out exactly what is good, and what isn't about both and look to combine more of what's good going forwards.
- Touch function priority and releases is an interesting idea, and isn't one I've heard before. I'll log it into our suggestions list for consideration going forwards.
- Regarding Bank Master controls- could you be more specific as to what exactly you are referring to? I will mention in case it's helpful- it is possible to do a lot of 'Bank' controls through the mappings screen, so if for example you want to set the Speed control dial of all scenes in a Bank to the same Touch dial- you can do this by setting the 'Target' to 'Bank'.
- Live Mode resets can be done using the 'Reset all beams' or 'Reset selected beams' buttons (found immediately right of the beam on/off and centre beam buttons).
- It is possible to use the buttons on the DVC controller as a MIDI controller, you need to go to the Mappings > Ports mappings screen- then use this function in the same way as you would with a MIDI controller.
Kind regards,
Will
Re : Développeurs DL5
À mon sens, mais que le mien c Le meilleur logiciel est bien celui-ci, avec une Timeline, ce que tout le monde souhaite au départ
Je lis dans le forum, beaucoup de problèmes faux ,,,,,,de manque de connaissances du logiciel ou peut-être même de patience
Je l'utilise depuis le départ la première version avec huit univers de 512 canaux jamais de plantage jamais de bug, et lorsqu'il manque une fonctionnalité, le logiciels, à l'avantage de pouvoir le créer soi-même
La communauté
Je lis dans le forum, beaucoup de problèmes faux ,,,,,,de manque de connaissances du logiciel ou peut-être même de patience
Je l'utilise depuis le départ la première version avec huit univers de 512 canaux jamais de plantage jamais de bug, et lorsqu'il manque une fonctionnalité, le logiciels, à l'avantage de pouvoir le créer soi-même
La communauté
Re: DL5 Developers
@ Willm
Responding to your responses.
"- Multi associations for Touch controls is possible already, if you right click on an existing mapping, then click 'Duplicate'- you can then assign the function to a new Touch control."
Ok i see now, kinda helps with stopping people from making mistakes. Still kinda slow and i feel you should be able to do everything in EDIT Touch Mode.
"- Touch function priority and releases is an interesting idea, and isn't one I've heard before. I'll log it into our suggestions list for consideration going forwards."
In MA you can have 2 master group faders but one takes precedence on another by changing its priority letter. If you can do it with scenes i think you can do it for your faders, encoders, buttons. ect ect.
"- Regarding Bank Master controls- could you be more specific as to what exactly you are referring to? I will mention in case it's helpful- it is possible to do a lot of 'Bank' controls through the mappings screen, so if for example you want to set the Speed control dial of all scenes in a Bank to the same Touch dial- you can do this by setting the 'Target' to 'Bank'."
Ok so i got this to work but its a bit confusing. If the bank itself had its own set of Master bank controls then there would be no need to even have a "bank" target. either way glad i know master bank control actually sorta does exist.
"- Live Mode resets can be done using the 'Reset all beams' or 'Reset selected beams' buttons (found immediately right of the beam on/off and centre beam buttons)."
Glad to see this exists however i was using this Butten in edit mode to reset a scene when programming. This can be dangerous if you think you are in live mode but are in edit mode. because when i make this a touch button if i am in edit mode it doesn't remember that i made the association in live mode. So maybe making a separate button or have touch remember what mode you made the association in so my lighting operator doesn't reset scenes by accident.
Some new things i suggest looking into would be scene locking. So no accidental changes are made. being able to lock a full bank of scenes or just individual scenes so no accidental programming changes to already finished scenes are made. Or maybe you can have a "SOLO" scene mode which locks the programmer to that scene until you take it out of "SOLO" mode so you cant accidentally click on another scene and change it.
Thanks for you help hope some of my recommendations open some ideas for the future.
Responding to your responses.
"- Multi associations for Touch controls is possible already, if you right click on an existing mapping, then click 'Duplicate'- you can then assign the function to a new Touch control."
Ok i see now, kinda helps with stopping people from making mistakes. Still kinda slow and i feel you should be able to do everything in EDIT Touch Mode.
"- Touch function priority and releases is an interesting idea, and isn't one I've heard before. I'll log it into our suggestions list for consideration going forwards."
In MA you can have 2 master group faders but one takes precedence on another by changing its priority letter. If you can do it with scenes i think you can do it for your faders, encoders, buttons. ect ect.
"- Regarding Bank Master controls- could you be more specific as to what exactly you are referring to? I will mention in case it's helpful- it is possible to do a lot of 'Bank' controls through the mappings screen, so if for example you want to set the Speed control dial of all scenes in a Bank to the same Touch dial- you can do this by setting the 'Target' to 'Bank'."
Ok so i got this to work but its a bit confusing. If the bank itself had its own set of Master bank controls then there would be no need to even have a "bank" target. either way glad i know master bank control actually sorta does exist.
"- Live Mode resets can be done using the 'Reset all beams' or 'Reset selected beams' buttons (found immediately right of the beam on/off and centre beam buttons)."
Glad to see this exists however i was using this Butten in edit mode to reset a scene when programming. This can be dangerous if you think you are in live mode but are in edit mode. because when i make this a touch button if i am in edit mode it doesn't remember that i made the association in live mode. So maybe making a separate button or have touch remember what mode you made the association in so my lighting operator doesn't reset scenes by accident.
Some new things i suggest looking into would be scene locking. So no accidental changes are made. being able to lock a full bank of scenes or just individual scenes so no accidental programming changes to already finished scenes are made. Or maybe you can have a "SOLO" scene mode which locks the programmer to that scene until you take it out of "SOLO" mode so you cant accidentally click on another scene and change it.
Thanks for you help hope some of my recommendations open some ideas for the future.
-
- Posts: 25
- Joined: Wed Mar 20, 2024 12:11 am
- Operating System: Windows
- Location: Germany
- Contact:
Re: DL5 Developers
Unfortunately, I share OP's opinion.
There are quite some features which have been requested years ago, and developers commented that said feature will come in DL5. However, it never happened. And we didn't get any updates.
Also, when you file feature requests via the support portal, you hear nothing back most of the time.
This is really sad because in my opinion, Daslight in general is a really solid software and I enjoy using it!
I feel like we could make the software even better if the team behind it would communicate more with the community.
Like, what about community events? What if we have a monthly online event where daslight users can join in and have a chat with the devs after they show new features that have been shipped. Basically like a Vendor-User sync, something like that.
Would be really cool!
As said, often times I'm getting a bit sad because Daslight does simply not make use of its full potential.
TL;DR: Daslight is amazing, but it could be even better if the Daslight crew would be closer to the users.
There are quite some features which have been requested years ago, and developers commented that said feature will come in DL5. However, it never happened. And we didn't get any updates.
Also, when you file feature requests via the support portal, you hear nothing back most of the time.
This is really sad because in my opinion, Daslight in general is a really solid software and I enjoy using it!
I feel like we could make the software even better if the team behind it would communicate more with the community.
Like, what about community events? What if we have a monthly online event where daslight users can join in and have a chat with the devs after they show new features that have been shipped. Basically like a Vendor-User sync, something like that.
Would be really cool!
As said, often times I'm getting a bit sad because Daslight does simply not make use of its full potential.
TL;DR: Daslight is amazing, but it could be even better if the Daslight crew would be closer to the users.
Re: DL5 Developers
I'm not sure I follow. If you create a Touch mode association (i.e. assign a Dimmer channel to a Touch fader, or a Scene to a Touch button)- this will always be remembered and stored (regardless of whether you are in Live or Edit mode). The reset Live Edit's button will only reset any fader values that have been set whilst in Live Mode. If you are in Edit mode, of course all fader changes are stored into the Preset.MOK5 wrote: ↑Sun Feb 23, 2025 3:32 am "- Live Mode resets can be done using the 'Reset all beams' or 'Reset selected beams' buttons (found immediately right of the beam on/off and centre beam buttons)."
Glad to see this exists however i was using this Butten in edit mode to reset a scene when programming. This can be dangerous if you think you are in live mode but are in edit mode. because when i make this a touch button if i am in edit mode it doesn't remember that i made the association in live mode. So maybe making a separate button or have touch remember what mode you made the association in so my lighting operator doesn't reset scenes by accident.
I really like the idea of locking individual scenes, with an option to right click on a bank and lock/unlock all scenes. Perhaps even we could make it so that any changes to specific faders would be stored as Live Edits whilst a locked scene is selected- this would also help with the other issue mentioned in this reply.MOK5 wrote: ↑Sun Feb 23, 2025 3:32 am Some new things i suggest looking into would be scene locking. So no accidental changes are made. being able to lock a full bank of scenes or just individual scenes so no accidental programming changes to already finished scenes are made. Or maybe you can have a "SOLO" scene mode which locks the programmer to that scene until you take it out of "SOLO" mode so you cant accidentally click on another scene and change it.
Kind regards,
Will
Re: DL5 Developers
Hello!Jamo wrote: ↑Mon Feb 24, 2025 12:29 pm Unfortunately, I share OP's opinion.
There are quite some features which have been requested years ago, and developers commented that said feature will come in DL5. However, it never happened. And we didn't get any updates.
Also, when you file feature requests via the support portal, you hear nothing back most of the time.
This is really sad because in my opinion, Daslight in general is a really solid software and I enjoy using it!
I feel like we could make the software even better if the team behind it would communicate more with the community.
Like, what about community events? What if we have a monthly online event where daslight users can join in and have a chat with the devs after they show new features that have been shipped. Basically like a Vendor-User sync, something like that.
Would be really cool!
As said, often times I'm getting a bit sad because Daslight does simply not make use of its full potential.
TL;DR: Daslight is amazing, but it could be even better if the Daslight crew would be closer to the users.
I'd be happy to look into any tickets that you have shared that did not get a response if you could please DM me the ticket numbers? I checked on your account associated with this email and only could find 2 tickets which are now resolved.
Unfortunately I don't think we currently would have the capacity for this sort of community event directly with developers, since we are a small team (3 developers and a handful of tech support staff). Perhaps it would be something that we could look into in the future though! We do now have a Discord which has been really great for communicating with users, sharing project files and encouraging more user-to-user interaction. You can join this if you havent already by looking at the top post on the Announcements section.
We take on board a tonne of feedback and feature suggestions every day from users. Whilst we would love to implement each and every suggestion, it is not something that would be possible for us to do for a number of reasons. To name a few- (again) we are a small development team, with each developer managing multiple other projects under the Nicolaudie Group that they develop- each with their own deadlines and work requirements. Further to that, many suggestions we receive are simply too big in scope and require massive changes to workflow or UI. Many of the suggestions we receive are also very user-specific, and could solve a certain problem for one user but also create a new problem for another. In short- there is a lot to balance, and we work hard to introduce the most useful and most requested features as a priority (it's worth noting that there have been significant and major changes from version 5.0 to now!). We'll always keep working to improve Daslight wherever possible, but we can of course never guarantee that all suggestions will make it into the program.
Kind regards,
Will
-
- Posts: 25
- Joined: Wed Mar 20, 2024 12:11 am
- Operating System: Windows
- Location: Germany
- Contact:
Re: DL5 Developers
Hi Will,
thanks for your extensive reply!
To be fair, it seems to change back to what it was slowly. Is it possible that your staff shortage was worse like a year ago? Because back than the forum seemed pretty abandoned in terms of interaction from the Nicolaudie team.
I want to emphasize that my reply was by no means meant to be mad or rude. As said, sometimes it just felt like the connection between us and the team behind Daslight fell off a bit.
While we're at it:
Is there anything one could help as a volunteer? For example having a look at the forum, looking for feature requests, to then submit them in a clean way in a ticket system or something?
While I don't have a huge amount of spare time, I'd be happy to assist wherever possible!
Best regards
thanks for your extensive reply!
To be fair, it seems to change back to what it was slowly. Is it possible that your staff shortage was worse like a year ago? Because back than the forum seemed pretty abandoned in terms of interaction from the Nicolaudie team.
I want to emphasize that my reply was by no means meant to be mad or rude. As said, sometimes it just felt like the connection between us and the team behind Daslight fell off a bit.
While we're at it:
Is there anything one could help as a volunteer? For example having a look at the forum, looking for feature requests, to then submit them in a clean way in a ticket system or something?
While I don't have a huge amount of spare time, I'd be happy to assist wherever possible!
Best regards

Re: DL5 Developers
willm wrote: ↑Mon Feb 24, 2025 2:40 pmI'm not sure I follow. If you create a Touch mode association (i.e. assign a Dimmer channel to a Touch fader, or a Scene to a Touch button)- this will always be remembered and stored (regardless of whether you are in Live or Edit mode). The reset Live Edit's button will only reset any fader values that have been set whilst in Live Mode. If you are in Edit mode, of course all fader changes are stored into the Preset.
Willm
I just tested this again to double check my concern. The "RESET ALL BEAMS" made into a Touch Button in Live Mode is not specifically assigned to Live Mode and is a RESET ALL BEAMS for both EDIT and LIVE modes! This is bad because you can accidently clear scenes out unintentionally if you are in EDIT mode. You must understand that not everyone who operates DL5 during events is the programmer. Your software's designated clientele are small to medium venues who most of the time will not want the LD to be present for all of there events mainly do to cost. That being said having a way to ideate proof the software for operators would help out the LDs from fixing stuff all the time.
And locking DL5 makes little sense, i would use it more if it was better. When i lock the software why does it always ask me to make a password when the software should have a saved password because now anybody can lock the desk with a random password and now you have to close the software when you shouldn't be able to close the software in locked mode.
Here is what i think lock mode should include.
1. You cannot close the program until you unlock it or the OS forces it to close like task manager.
2. At least be able to switch between CONTORL and TOUCH tabs.
3. If you have the Touch window separated you still cannot exit out of it and only minimize it.
4. Have a saved password and not keep making new passwords every time you lock it.
Hope these requests make sense.
Re: DL5 Developers
In fact you are correct, the reset all beams does work even in Edit mode- my mistake! I suppose then in that case the best option is to right click on the Edit button and disable the Lock Edit Mode function. This means that whenever you select or trigger a new scene on the Control window, the Edit mode will automatically jump to Live Mode. This should hopefully allow you to avoid accidentally resetting a scene in Edit mode.
I agree that lock mode can be improved, in fact it appears to have changed since the last time I checked it- I will pass on your suggestions to the dev team for consideration in future updates.
Kind regards,
Will
I agree that lock mode can be improved, in fact it appears to have changed since the last time I checked it- I will pass on your suggestions to the dev team for consideration in future updates.
Kind regards,
Will