Hello,
last night i used the latest version of Daslight (the 3 May 2017 version) and i experimented few bugs:
1 - In the show tab, when you switch to full screen, disable it and go back to full screen, the full screen does not work properly (see attachments).
2 - In the effect tab > add a matrix effect: It is impossible to remove the first 2 colors even when there are more than two.
About the Edit tab:
you should spend more time testing it. Indeed, daslight version after version is still unstable in this mode. I had many crashes when programming the scenes. Randomly, I had crashes when:
- i tried to add a new group. I tried to reproduce the steps to get to the crash without success (2 times it crashed, 2 times it worked correctly). For debug: i had 2 scenes actives in live mode: Dimmer 100 & Shutter open (for my moving heads) and i try to add scene to create a position. The auto save was disabled at this moment.
- i tried to create a scene and move a fader.
- autosave is active: Daslight crashed randomly when i try to add scene or new group (I think it was the autosave process that tried to save my show at the same time as my attempt to create scene).
Suggestions / Feature request:
1 - Make the autosave's process more discreet: The autosave's popup is not convenient. Seeing it every minute while programming a show is really inconvenient. Perhaps replacing the popup with a loader or an icon near the Daslight's logo ?
2 - Change the default value of BPM mode: Can you change the default value from BPM (0) to 120 ? Having to re-tap a tempo every time you open a show is a time that could be won (especially when you just want to do some tests).
3 - Adding additional values to the time signature: Can you add the following values: "4/1", "8/1", "16/1", "32/1" to the time signature ? This would make it possible to have steps that change every 4 beats, 8 beats, etc. An example of what I often do: open the shutter of n projectors, then, 4 beats later, close and open N others. To achieve this, I have to define the time signature at 1/1 and duplicate 4 times each step i made.
My hardware:
- MacBook Pro (13 pouces, mi-2012) on Mac OSX Serria (10.12.4 [16E195]).
- 2,5 GHz Intel Core i5
- 16 Go 1600 MHz DDR3
- Intel HD Graphics 4000 1536 Mo
That's all ... for now. Thanks again for this great software and thanks for listening to your users and improve the stability and the use of Daslight.
feedback and suggestions
feedback and suggestions
- Attachments
-
- screenshot-2.jpg (166.96 KiB) Viewed 8976 times
-
- screenshot-1.jpg (171.1 KiB) Viewed 8976 times
Re: feedback and suggestions
Hey Mokab,
First of, thanks alot for your feedback.
Suggestions
For Daslight 4, this would be too big work. We are now focusing on improving the stability of our software. But I'll definitely add this to our list of ideas for future versions.
We actually already had a default value back a few months ago, but if a scene is set to "BPM triggering" then the show started automatically, based on the default BPM set at startup. This was not great, so we took away the defalt BPM. Doesn't take much time to set it by hand (unless you use MIDI clock, which is more or less instantanious).
I'll submit this idea and implement it if possible. If not, I'll add it to our list of ideas for future versions.
Bugs
We will look into those as soon as possible. Could you please provide us with the showfile you were using when the crashes occured ? This would help a lot.
Thank you for your input, have a great day.
Regards,
First of, thanks alot for your feedback.
Suggestions
1 - Make the autosave's process more discreet: The autosave's popup is not convenient. Seeing it every minute while programming a show is really inconvenient. Perhaps replacing the popup with a loader or an icon near the Daslight's logo ?
For Daslight 4, this would be too big work. We are now focusing on improving the stability of our software. But I'll definitely add this to our list of ideas for future versions.
2 - Change the default value of BPM mode: Can you change the default value from BPM (0) to 120 ? Having to re-tap a tempo every time you open a show is a time that could be won (especially when you just want to do some tests).
We actually already had a default value back a few months ago, but if a scene is set to "BPM triggering" then the show started automatically, based on the default BPM set at startup. This was not great, so we took away the defalt BPM. Doesn't take much time to set it by hand (unless you use MIDI clock, which is more or less instantanious).
3 - Adding additional values to the time signature: Can you add the following values: "4/1", "8/1", "16/1", "32/1" to the time signature ? This would make it possible to have steps that change every 4 beats, 8 beats, etc. An example of what I often do: open the shutter of n projectors, then, 4 beats later, close and open N others. To achieve this, I have to define the time signature at 1/1 and duplicate 4 times each step i made.
I'll submit this idea and implement it if possible. If not, I'll add it to our list of ideas for future versions.
Bugs
We will look into those as soon as possible. Could you please provide us with the showfile you were using when the crashes occured ? This would help a lot.
Thank you for your input, have a great day.
Regards,
TomHat
--
Daslight Support
Mail : [email protected]
Phone (French) : +33 (0) 616 427 588
Phone (English) : +44 (0) 7 481 811 500
--
Daslight Support
Mail : [email protected]
Phone (French) : +33 (0) 616 427 588
Phone (English) : +44 (0) 7 481 811 500
Re: feedback and suggestions
Sure.
You'll find my show in attachment of this message.
Ok ... It's a shame but if the stability of the software improves and the crashes reduce, the autosave will no longer be necessary.
It makes sense. I had not thought about this scenario.
Hope your developers will implement it.
Of course. You will find it here:
https://wetransfer.com/downloads/329113 ... 146/6c1a91
You'll find my show in attachment of this message.
For Daslight 4, this would be too big work. We are now focusing on improving the stability of our software. But I'll definitely add this to our list of ideas for future versions.
Ok ... It's a shame but if the stability of the software improves and the crashes reduce, the autosave will no longer be necessary.
We actually already had a default value back a few months ago, but if a scene is set to "BPM triggering" then the show started automatically, based on the default BPM set at startup. This was not great, so we took away the defalt BPM. Doesn't take much time to set it by hand (unless you use MIDI clock, which is more or less instantanious).
It makes sense. I had not thought about this scenario.
3 - Adding additional values to the time signature: Can you add the following values: "4/1", "8/1", "16/1", "32/1" to the time signature ? This would make it possible to have steps that change every 4 beats, 8 beats, etc. An example of what I often do: open the shutter of n projectors, then, 4 beats later, close and open N others. To achieve this, I have to define the time signature at 1/1 and duplicate 4 times each step i made.
Hope your developers will implement it.
We will look into those as soon as possible. Could you please provide us with the showfile you were using when the crashes occured ? This would help a lot.
Of course. You will find it here:
https://wetransfer.com/downloads/329113 ... 146/6c1a91
Re: feedback and suggestions
Hello,
a nice feature would be to add the following values: "4/1", "8/1", "16/1", "32/1" to the time signature!
This would make it possible to have steps that change every 4 beats, 8 beats, etc.
bye,
Heiko
a nice feature would be to add the following values: "4/1", "8/1", "16/1", "32/1" to the time signature!
This would make it possible to have steps that change every 4 beats, 8 beats, etc.
bye,
Heiko
Re: feedback and suggestions
xeidos wrote:Hello,
a nice feature would be to add the following values: "4/1", "8/1", "16/1", "32/1" to the time signature!
This would make it possible to have steps that change every 4 beats, 8 beats, etc.
bye,
Heiko
I totally agree. I would love to have those time signatures added. At least "4/1" and "8/1".
Regards,
Zignature
Re: feedback and suggestions
Zignature wrote:xeidos wrote:Hello,
a nice feature would be to add the following values: "4/1", "8/1", "16/1", "32/1" to the time signature!
This would make it possible to have steps that change every 4 beats, 8 beats, etc.
bye,
Heiko
I totally agree. I would love to have those time signatures added. At least "4/1" and "8/1".
Regards,
Zignature
Any update/news about this feature request?
I'm not an application programmer so I really wouldn't know but it seems so easy to do. The logic is already there.
Right now it's the only thing missing for me.
Regards,
Zignature
Re: feedback and suggestions
Hello,
First of, thank you for your interest in our software. Regarding this feature, please note that we've stopped adding features to Daslight4 as it's now been release for several years and we'd rather work on its stability.
We'll think of this for later versions, though.
Best regards,
First of, thank you for your interest in our software. Regarding this feature, please note that we've stopped adding features to Daslight4 as it's now been release for several years and we'd rather work on its stability.
We'll think of this for later versions, though.
Best regards,
TomHat
--
Daslight Support
Mail : [email protected]
Phone (French) : +33 (0) 616 427 588
Phone (English) : +44 (0) 7 481 811 500
--
Daslight Support
Mail : [email protected]
Phone (French) : +33 (0) 616 427 588
Phone (English) : +44 (0) 7 481 811 500