I see. I'm sorry - I tried to be specific.
Yes like that - like it is in MA2.
I might make a request, but I think it's sad and unnecessary that I have to..
BECOME PART OF THE COMMUNITY - Sign up here
I feel you are working hard to not understand me now..
The line above the one you quoted says: "E.g. Store dialog."
I thought that meant "Here is an example using the Store Dialog"
I'm talking about this:
Exactly where in that dialog is not important but why not in the grey area - after the word "Store".
If I use STORE PLEASE or any other syntax with no dialog I would not expect to see anything.
There will be no Store Dialog, and my example is not addressing that.
BTW. What does STORE PLEASE do when no Sequence is selected? Or when two sequences are selected?
As long as there is a 'Sequence 1' there is always one selected sequence.
When I deselect the last of my selected sequences the Default Sequence (#1) is automatically selected. Just didn't notice at first.
Maybe that's the purpose of it?
What do you mean?
I know I store to selected sequence (if not specified), but I want the dialog to tell me what sequence that is to avoid error.
I'm quite sure MA2 did that, and for me it's a extremely obvious thing to do.
It's particularly important because we can select multiple sequences and only one of them gets the data..
AND it's super easy to do multiple selection inadvertently - and no way to tell unless you happen to see the previously selected.
So what I mean is: When they implement a store dialog (or anything else), why not start at the standard we had, or better?
I highly doubt that someone would request an option to NOT see the sequence number and name.
there is also a different definition of ‘right’ from every user.
My point exactly!
That's why they should go straight to options as default, instead of spending time discussing how something should work.
Developers will hate me but I love me some options so I say a ‘reset speed/rate on off’ option would be awesome
Developers should have learned by now that they should not assume anything when it comes to our preferences..
Just make everything optional from the start and save time and trouble.
Speaking of developers, I kinda understand that they could not have every MA2 feature ready from v1.
But the ones they put in, why not just make it right the first time? (Right meaning as good as before)
E.g. Store dialog.
Do we REALLY have to do a feature request to see what Sequence we are about to store in??
Maybe that was planned for v2.3 from the start? I don't understand how they think....
Let's stay out of the rabbit hole Andreas - I'll execute plan B.
As I've said before - there's ALWAYS a workaround
Didn't need this now, but had to try
(Remember to enable DMX remotes - I didn't at first)
I noticed when I moved the Hue-fader in the Color Picker that System Monitor said:
Programmer::SetEncoderChannel system 1 channel 6 to X, 0 0
Is it possible to control this fader from command line / Lua ?
I ran into exactly this today.
Phone was showing only a few buttons.
iPad was better but reported resolution was 1104 x 716 and I believe the display is 2160x1620
Tried resolution setting 'unlimited' and 1080P.
This example shows how you can display faders on a dialog.
This was INDEED helpful.
I managed to integrate it in my code but I have a question about the fader-values.
How can I read out the current value of the faders and use it as a number in my main code?
I've catched it from the caller.value near the end of the script, but I just need the value after the fader is adjusted so I thought it might be a simpler way..
And - is it possible to set the initial value of the faders?
When using syntax "FaderTemp Sequence 67 At 10" I got some unexpected result.
FaderTemp moves X, XA, XB and TEMP
FaderX moves X, XA, XB and TEMP
Edit: I see now that they are linked when adjusting the actual fader also, but still...
Can see how XA+XB = X but don't understand connection to Temp.
I'm not surprised.
This is probably the reason for strange behavior on my last show.
Did not have the time to investigate - just had to repair and move on.
I noticed the urge to change already defined cuenames automatically to something useless has also gone one step further.
Sometimes TWO cues get new name during update now.
You need to set 'Allow Duplicates' to Yes for the cue.
But as I see it there is a lot of work to be done before Parts works in a meaningful way.
(E.g. the when editing)
I really hoped you were doing something wrong here but can only confirm that this extremely ugly bug exists.
When this can slip through who knows what else.
MY old desk had this since 2016 (LSC LX 600) so I'm also hoping for MA to make this happen because I miss that function.
Having the waveform alongside the events is very helpful - and the obvious way to do it in my opinion.
I was very surprised when I found out that MA lighting takes NO responsibility when it comes to supply of Fixture Types.
Every other light control developer in the world, regardless of price range, seems to do that - and have one ready for you in days.
I've exported from MA2, it could work but probably not very good (I get problems with multiple channel sets) and they're known to not work with cloning.
I'm using some of these but they usually needs some tweaking in the Editor.
I learned to make GDTF in the online builder, imported to MA3 and it was changed in the process and did not work. (Not bothered to try in last version)
Only thing that seems to work good is to make one yourself from scratch in Fixture Type Edit inside the MA3 software.
Use command 'Fix Executor X'
Easy to reproduce for me.
One or more fixtures missing from Fixture Sheet.
They show up when they get active values and disappear when I clear the values.