Map Fader Without Changing Current Scene

[Jamo]

Hey folks

I have a quick question.

Let's say I have some scenes which allow me to control movements, colors, gobos and so on for some beam lights.
Something like this:



Now, I want to map the master dimmer of all those beams to a fader on my midi controller.
That's done in just a few seconds, sure thing.

BUT now comes my issue:
When you're in the "control" tab, there's always an actively selected scene for editing.



That means that I'll change the dimmer value within the currently selected scene as soon as I use the mapped midi fader.

How can I prevent that from happening? I don't want the midi controller to affect any scene, I just want to select already defined scenes and move some sliders.

I hope my explanation made sense
All suggestions are welcome.

Best regards

[DJMan32]

makes sense, I have the same issue, unfortunately you just really have to be careful. this is like this by design so you can use it for programing scenes as the midi controller is just a physical control for the virtual controls.

[Jamo]

And it just got worse ...

When you map a fader to the dimmer for example, the mapping isn't specific to the currently selected fixtures. That means, that one and the same fader operates basically EVERY fixture, depending on what's currently selected in the selections window.

Thats very bad! This makes mappings for faders basically entirely useless!

One possible fix, that would at least partially solve it, would be to make mappings for dimmer limits a thing. That's not an option atm.



This issue really disappoints me

[Jamo]

Is there a way to escalate this to the Daslight Team? I can't be the only one who's facing this issue, right?
Scene-Unspecific fader mappings are crucial, at least in my opinion.

[DJMan32]

this is as far as we can escalate.

And yes, there needs to be a separation on the aspects panel to bind a control to just the current selected fixtures and all the fixtures. (midi binding follows that but the controls need to be fixed first)

[juls]

Hello,

If you selecte LIVE instead EDIT, you will be able to change parameters without change the contents of the selected scene.

Regards

[Jamo]

If you selecte LIVE instead EDIT, you will be able to change parameters without change the contents of the selected scene.

Well, yes, sure. But than my entire scene is useless.

[Jamo]

I have contacted Daslight support and they told me that this issue is known and there will be a fix in a future update
So let's wait and hope.

I'll post another reply once the Patch is published, just so that the thread is up to date.

[willm]

Hello,

This actually does not appear to be a bug, as this is how the software is designed to work (and for good reason, which I will explain below!)- I apologise if you have been informed that this was a bug, perhaps there was some confusion.

So, firstly to explain why the behaviour is like this:

There are three modes in the Daslight Control window- Edit, Blind Edit and Live.
- Edit allows you to create and edit your scenes. Any change made whilst in Edit mode will be permanently stored into the scene.
- Blind edit is the same as Edit mode, except the DMX output for the selected scene will not take affect allowing you to make changes on the go without affecting your show.
- Live allows you to trigger scenes and manually control faders without affecting the contents stored within the scene. This is why changes to faders in this mode are called 'Live Edits'.

MIDI controllers are generally speaking used for Live control, since you will use them to control fixtures or scenes on the go and will generally use them less for programming scenes. For this reason it is best if you enter Live mode when using the MIDI controller. You mentioned that doing this would make your scene useless- which I find confusing. You are able to trigger scenes whilst in Live mode, so is there a reason why the scene would be 'useless' whilst in Live mode?

I would also like to advise a potential solution... If you go to the Live Mixer tab (top right corner of the bottom right panel, where your faders are), you will see faders for each Group and one for 'All' fixtures as well. These controls are not stored within a scene, so are always in 'Live Edit' mode. You can map the fader here to your desired fixture group and use this whilst still in Edit mode.

Hope this is helpful! If you are still struggling or have other questions, please do let us know.

______________________________________________________

this is as far as we can escalate.

And yes, there needs to be a separation on the aspects panel to bind a control to just the current selected fixtures and all the fixtures. (midi binding follows that but the controls need to be fixed first)

Actually- the better way of contacting us/escalating issues is to raise a ticket with us at help.daslight.com. The forums are generally meant for user discussion and help so whilst we do monitor the forums, this is not our main method for supporting Daslight!

When mapping a feature to MIDI, you will notice that the symbol/image is mappable as well as the physical fader itself. If you select the symbol/image when making the mapping, you will notice that you now have the option to select the 'Target'. This can be used to set one of two options

- 'Beam' - The mapping will control the specific fixture(s) that were selected when the mapping was created.
- 'Selected' - The mapping will control whatever specific fixture(s) are selected (i.e. Select one fixture, move fader to adjust. Select another fixture, move fader to adjust. etc.)

______________________________________________________

Kind regards,
Will