kgallen
-
Posts
1,812 -
Joined
-
Last visited
-
Days Won
70
Posts posted by kgallen
-
-
For Remove to work you have to tag every attribute of the fixture. So the approach is:
- select fixtures to remove
- HOME
- Update with Remove
As for your wider question I’m not quite sure I understand what you want to do (especially the bit about removing them!).
-
Great news! Not a problem at all. I learned something new too!
Hope you have a great show!
Kevin
-
The manual says this:
If any of the selected fixtures are not actually programmed in the applied palette, but there are one or more fixtures of the same type that are programmed, the fixture will use the values programmed for the first fixture of the same type.
https://www.zero88.com/manuals/zeros/palettes/using-palettes
-
I created my own groups and position palettes from scratch in the way I would usually do it, and it seems fine. I think the confusion is that the two groups contain a common fixture type (the Intimidator). This means the desk is perfectly able to apply a palette to any of those two groups that are selected, even though you only recorded the palette against one of the group. I only see the selected ones change position.
If I record a group that doesn't contain any of those Intimidator fixtures then the position palettes recorded with Intimidator groups don't highlight.
If I record a group with Intimidator plus other different fixtures, then when selected, the position palettes do highlight, because they can be applied to that fixture group - but they would only change the position of the Intimidators.
The palette isn't programmed against the group that was selected, it programmes against a fixture type. So if you had 6 groups that contained Intimidators, you'd only have to record the palette against one group then that position could be applied to Intimidators that were selected by a different group. HOWEVER, there will be some potential differences. If you are recording a position palette against a group with say a fan, if you then selected a different group of Intimidators, I don't know how that fan is applied to the new group. Possibly the position palette is applied across the fixtures in the same order as in the original programming. i.e. if you recorded a fan from fixtures 1,2,3,4,5, then applied that palette to a group with fixtures 6,7,8,9,10 I assume the position of 1 will be used as the position of 6 etc up to pos of 5 applied to the pos of 10. I don't have more than 4 movers of the same type so I've never really had to work out how a palette recorded on one fixture group gets applied to another fixture group!
Seems ok to me. What did I miss?
-
18 minutes ago, kgallen said:
Yes I'm seeing that, I'll investigate.
Hold on a sec, yes, that's fine - they are all exactly the same fixture type, so that means the desk could apply the position palette to any of them if you wanted to - even though you recorded that position palette using another group. But that other group did contain an Intimidator.
From what I worked through, I could select FRONT or REAR and apply either their "own" or the "other" position palette and only the selected ones are moved - in so far as I can tell from the Pan and Tilt values on the internal screen.
So this looks ok so far. I you are able to provide a Capture 2019 visualisation I can check that the non-selected fixtures aren't affected by the palette when not selected.
HTH so far...
-
1 hour ago, Uriahdemon said:
When even selecting one single Hybrid all position palettes highlight....??
Yes I'm seeing that, I'll investigate.
-
1 hour ago, Uriahdemon said:
Yes those are the ones although I deleted a whole more to get this fixed first. The problem seems to happen with any spec mover though. I will have a look at the Capture file although it is not really needed for this. When even selecting one single Hybrid all position palettes highlight....??
I’ll work through it and look for that. From what I’ve done so far I don’t see the pan and tilt values for the other group changing. I’ll look more and get back.
-
4 hours ago, Uriahdemon said:
My Capture version is 2019, you've got a newer version. Any chance you could write out your Capture file in 2019 version - I believe you can do that from the File menu.
Is it your groups HYBRIDS FRONT and HYBRIDS REAR you're having fun with?
Cheers, Kevin
-
I’d upload your showfile here, some folk might have chance to have a look and a play. Z88 folk aren’t going to respond until Monday earliest.
-
I’ve not got as many movers as you but I do use position palettes and groups a lot and I don’t think I’ve seen this. (FLX 7.13). But that in no way precludes that you’ve not identified a corner case bug!
My only suggestion would be to delete those groups and palettes and then carefully reconstruct the groups and then the palettes. Unless you are doing some blind programming with intensity off, I would expect you can leave SmartTag on. Snapshot however would almost certainly be a bad thing and could easily result in what you’re seeing.
-
One word... battery?
-
Think I’ve only posted (and edited) the once and it was ok.
…Or that might have been on another forum… 🤣 I dunno, I’ve been (vaguely) to sleep since Tuesday.
So here’s a post…!
… which seems to have worked from my phone which wasn’t the case before. So this is an edit…
-
2
-
-
Shift+GO
(Edward, it doesn’t say this on either the Master Playback or Playing Back Cues manual pages - could it be added? I’m sure it is stated somewhere, but I couldn’t find it. Also page next/previous buttons would make a real difference, it’s very slow to navigate the manual on a phone.)
Ah here it is, see Snap To Cue:
https://www.zero88.com/manuals/zeros/cues-playbacks/playing-back-cues/running-cue-stacks
-
Hi Jon, One example of a fail for me included a reply with a link to the FLX manual (the Output Window query on FLX S, Edward has posted that link now). I don't know if having a link in my reply was part of the issue (I suspect not), but mentioning it anyway.
You've also addressed the query on move on dark not only being for position, so that one is dealt with too 🙂
-
I still can't reliably add comments to posts. I tried several times over the past few days to help various posters. only to receive the Access Denied response.
I logged out and in again. Didn't help.
I cleared the Cache on Chrome. Didn't help.
-
Not quite what you're after but the only thing I can think of is to use the Effect Step On and set the offset to Random. You might need to wind up the speed a bit. This doesn't do all the things you want but might be a start?Talking rubbish again!
-
This is me from a normal window...
-
Test from iPhone chrome incognito tab.
-
The manpage for the USB Creator says that method doesn't work on FLX S.
FLX S came out after that legacy update procedure ended.
The ZerOS version number should show in the bottom right of the internal screen at startup, and under the Z button.
-
1
-
-
Forum is still pretty messed up. I can post on occasion then immediately after I can’t edit or post again.
-
1
-
-
Setup->Load
Can’t see you’d have 7.7 on S24, desk wasn’t out at that version. Must be at least 7.9. My FLX is older and that came with 7.8.4.
-
14 minutes ago, SimonH said:
Think it's only you and me on here!!
This thing keeps going down and keeps losing my posts, so I'm having one last try then I'm giving up until it gets more stable!
-
Nah it's dead again.
-
Retest
Adding & Removing Fixtures from Playbacks & Cues
in FLX
Posted
Manual is here and yes it’s even harder to find on Vari-lite site but it is the same URL as it was before if you have links in other threads
https://www.zero88.com/manuals/zeros?filter=3
The trouble with the manual is it’s more of a ‘reference manual’ than a ‘user manual’ since it’s laid out command for command rather than ‘I want to do this’. If you know what you want AND you know it exists then it’s findable with persistence. I wish the search prioritised commands in the results. If you search ‘remove’ or ‘update’, which are fairly generic words, then you get many pages of results and the early results are probably not what you’re looking for… gripe over (for now!).