What do you know!
There is an undocumented bugfix on this in v1.9.2.2
Must have been a known issue then.
Unfortunately this also leads me to the first bug-report.
Editing a Universal Color Phaser with the Color Picker destroys the phaser. (Deletes step 2)
There's always a chance I have misunderstood what's the Universal Preset type is meant for.
I thought it was a preset where you could store ONE physical value (pr attribute/step).
When applied this value is translated to represent that physical value on whatever fixture you have.
(I see how storing globals in the Preset is a way of doing this.)
This is also how it works until you edit and update it.
If I use the Universal Fixture to adjust the Preset and then Update, the Universal Fixture gets the new value but every other Fixture Type is now stored in the Preset with the OLD VALUE.
If I use one of the regular Fixture Types to adjust the Preset and then update, ONLY this Fixture type is changed.
What I have now is a Multi-Global Preset identifying as a Universal Preset.
What I would expect for this to be useful:
After editing with the Universal Fixture type all the (preferably hidden) Global values are updated
After editing with a regular Fixture this value is translated to the Universal Fixture and THEN all the Global values are updated.
(Multiple different values could be handled in some clever way - not important)
Please do join the discussion and enlighten me.
PS. I have work-around!
Store / overwrite (And lock the Preset to avoid unintentional updates)
You can use "Cleanup Preset x.y /Selective" to remove selective values out of presets.
Thanks Ryan, I'll remember that.
But why is it not possible to update a U-Preset without filling it with every FixtureType in the patch?
If I want Global I can use Global...
Known issue?
Maybe fixed in the last 6 months?
I too have a hard time understanding the logic if there is any - except I keep getting G + S presets when I don't want them.
I can not see the 'Global value by average' is working (below).
I wish there was a Force Global - setting too inside the Preset that did not allow ANY S-values
I find that Universal Preset is more messed up.
After updating it always ends up as a Multi-Global Preset but it still calls itself "U"
Thought I had a work-around, but not even in a World with only the Universal Fixture will this work as expected.
- - -
The global value is determined by the average across all values of attributes within the same activation group:
(Value of fixture 1 + Value of fixture 2 + Value of fixture 3 + ... value of fixture n) / Number of used fixtures = Average value
The value that is closest to the calculated average value will be the global value. The fixture with this value will then hold the global value. In the case of color, all color attributes are handled together when choosing the global value.
Use argument[1] and argument[2]
It even scales to more arguments if needed.
Multiple people might have asked for this, but now multiple people finds it annoying...so maybe worth a second thought?
As mentioned by Heart Lighting, working on a tracking sequence this is most likely not what I want.
I have the same problem with phasers getting active - but can see that useful in other situations.
An option to turn off this auto-grabbing so WE can decide what to store in next cue would be great!
(Encoder Link Values "Not at all" ?)
Hi
Maybe you find a clue here:
RE: Store and Label Recipe in a Cue
Dear GGGss_be
Did you read and understand the posts leading up to it?
I don't feel hit by your criticism. (Not now, not in your previous post)
If I complain about something I usually have a hard time getting my point through.
Now when I want to give credit for something I also have to argue hard....
Dear Ryan. I regret mentioning the Presets, and you keep ignoring my other points...
Never mind.
Allow me at least to say the change is undersold.
It should have it's own chapter named: PARTS - FINALLY USEFUL!
OK, there's a misunderstanding - I'm not talking about any Presets!
Just building a cue with multiple parts directly in the programmer (Programmer Parts-window / New ProgPart)
BUT It's the same building a cue with Presets actually!
Preset 1 Dim/Part 1
Preset 2 Pan/Part 2
Preset 3 Color/Part 3
If you activated those 3 in v1.6 everything ended in one of the parts in the programmer.
This is also (secretly) fixed in v1.7 
That is actually not new to v1.7! It's been that way for a few versions now.
It did not work in MY 1.6.3.7.....
You could add parts but everything went to Part Zero anyway.
(It was possible to store multiple Parts one by one, but not to work with multiple Parts in the programmer)
To which improvements are you referring?
(Thanks Ryan)
It's now possible to use multiple parts at the same time in the programmer. (E.g. Dim in Part 1, Pan/Tilt in Part 2.) and store both to a cue.
If you later update this cue the software seem to remember what part the attributes came from now!
Combined with the Content sheet it's starting to look promising.
There seem to be big improvements on Parts - wonder why that is not mentioned in the release notes..
Thanks for your answer Ryan, maybe that's the reason to the secrecy.
If I had unlimited 24/7 instant access to phone support I might say 'good points'.
I still think any known, unresolved issue should be listed in the release notes.
Maybe they are not considered limitations - but a new section with another name would do just fine for me..
We already know the software is constantly developed.
What would be the downside on such list??
More bug reports and feature requests are generated than there is time to fix or implement if the software is to be released in any reasonable amount of time!
So...when users start to report issues after the release there is a fair chance those issues are already known.
Still the 'Known limitations' part of the release notes are almost none existent...
How come??
In the 6 months before next release user after user encounters, researches and reports these issues.
Imagine the amount of wasted time that could have been easily avoided....
People all over the world are already using MA3 software, on small shows and large.
I would love to know about some large shows using MA3 software.
Particularly theater-style programming.
That's were I have most problems.
As soon as I push it a little bit strange things happen.
(With push I mean long sequence, update during playback..and other completely normal things)
Like this last time when half the console froze during show.
Good thing the playback side stayed alive.
I bought a MA3 Light 2 1/2 years ago with no intention to FIRST learn MA2 and then MA3.
It was fun for a while, now I've lost the spirit and just waiting for the next update to come and disappoint me.
Maybe 1.7 is a turning point.
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..
Dear Clintos
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?
Update:
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?
