kgallen

Hi Jon. Thank you. I guess you're aiming to handle the situation where multiple fixtures are selected and hence there isn't "one" Universe number or DMX address? OK, I understand, but I don't think that it's clear with the numeric field being empty, there should be something that indicates "retain current values". On the Universe number I should check again. I thought the Universe button in the top left always said "Universe 1" but I'm almost certainly wrong there and it would have had the current universe number in it. I don't remember what was in the numeric dialogue, I'm pretty sure it was blank too! I can confirm I only ever had one fixture selected though - or more correctly, I tapped on the universe/DMX address of one fixture in the Fixture Schedule - so I would have thought in this scenario the GUI should have presented the current value. Much appreciated. Regards, Kevin

Thanks Edward, I'll have more of a play. I renamed the device on the FLX but this didn't seem to reflect onto the NET-2. Maybe my name was too long! I worked out ok patching fixtures to different universes then outputting them on Art-Net and out of the NET-2. But as yet I didn't manage to reconfigure the NET-2 from the FLX, so I'll need to play some more. One comment on the fixture patching - I was moving some existing fixtures onto different universes when playing with this, but wanting to keep the DMX address, i.e. just change the universe. I found that the numeric dialogue box doesn't present the existing value. The number field is blank. After a bit I realised just pressing Enter kept the existing DMX address, but that box should really be showing that number (with the usual convention of having it selected for overtyping) rather than presenting a blank box. Same for the universe number - the numeric box should be prefilled with the exiting number, not blank. Could this get fixed for 7.14?

Seems to work well. FLX sees it. Not worked out how to configure it from FLX yet. Maybe I have to turn on RDM globally?

Ah interesting. Thanks Edward I’ll have a play!

I also recently purchased the Showtec NET-2 "Pocket" for my FLX to extend the number of universes available as DMX. I hope to play with this soon, so will report any issues. I can also confirm that the Showtec can be powered with PoE thus negating the need for the local "mains power brick". First impressions are favourable on build quality and features. I wasn't sure whether to use Art-Net or sACN, so I watched Edward's video again. I think I'll start with sACN as I don't have any (well 2) RDM fixtures. Kevin

I now need to "scrub my mind" of that concept. Thanks a lot @iank99 😁

(Apologies, Keith, there might be an XLS question coming your way too...! https://www.blue-room.org.uk/topic/77296-quick-qestion-for-anyone-with-a-deeper-understanding-of-lighting-desks-than-me-error-codes/#comment-602450 )

@iank99 is the STMain1 in a Frog likely to fit an Illusion 120?

Great news! We like keeping good kit running, especially Zero88 kit 😀 and we even less like good usable kit going in the skip… Let us know how you get on. Kevin

Some Frogs going begging in Leeds if you're in that neck of the woods. https://www.blue-room.org.uk/topic/77291-desks-for-spares/#comment-602410

Seemed to let me edit my post above. Also could edit again and add a video link which worked when it was expanded to embed YouTube. Looks promising, let's see. However I'm on a Win10 laptop here. Some of my weekend posts were from iPhone11 iOS 16.3.1

Minor heart attack when I misread the last line as ‘This will be the last significant release of ZerOS.’ 🤣🤦‍♂️ Looking forward to playing with 7.14. Any up-front Release Notes to tease us?

What is this "holiday" thing you speak of? Welcome back to the madness!

This comment can no longer be edited. It may have been moved or deleted, or too much time may have passed since it was posted for it to be edited.

This video? https://youtu.be/--EeATsqH-o

Won’t let me post a link to one of Edward’s videos on the tube. Issue there. Seems like I have to save very quickly before the video url expands to the embedded video clip.

That worked. I’ve been posting - normally works but get occasional access denied again. Also if editing a post, very quickly it says ‘this post can’t be edited, too much time has elapsed’ (or something along those lines) - when I’ve only just posted within the last minute the initial response! Yes, very annoying when trying to help out others… Trial edit. Trial edit add video link

I’m getting access denied again.

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!).

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!).

@Uriahdemon 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

@Uriahdemon 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?

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...

Yes I'm seeing that, I'll investigate.