Sven76

Thanks for replying to me, Jon. Good to know it wasn’t my fault 😄 Maybe some option in „default settings“ to change this would be a great improvement? 🤔😉

Hi all did I just found a bug? On latest Version of zerOS on a FLXs 24 I just patched a couple of different generic LED fixtures (like some RGB and RGBW) and some generic Dimmers (beside others). In the Fixture schedule I then renamed all of them. Afterwards I auto created the groups. But the group names were all based on the original fixture type names. Is this intended? Or did I do something wrong? It took me quite some effort to afterwards rename all the groups manually again.

Regarding the title of this Thread: How do you define „soon“? 🤔😄

Actually I have a MacBook Pro M1 Max (32 GB)

Hi, yes. I have this running both on Windows 11 running on parallels without issues.

🥲

This would be great. I‘m waiting for this for years now 😏 especially Pixel mapping. But also effect! I still don‘t understand why someone would want to change effect speed and size if you chose your fader to be „Fader controls effect“! Maybe an easy „fix“ would be to create a option in the desk defaults settings if you want the fader to control fx speed or size or both.

😢

Is there actually a Zigbee sender/receiver in the Zeros-Server? Or do you need a bridge to talk to Philips Hue? 🤔

Intresting announcment from PLS today: I can't remember to see this in this wishlist here... 😜

Hi Edward, I could also provide the timeloard showfile and a capture showfile if this might help... Please just let me know. Best regards Sven

Hi all, we just created a showfile for an online event and discovered a strange behavior in regard of MTC using offsets. Unfortunately I can not remember if this behaved the same on the previous OS version. This is our setup: We have a PC running the "timeloard" software connected via MIDI to our ORB XF running zeros 7.10 On the timeloard we have 16 songs. All of them have an offset of 1 hour (so 1st starting with 00:00:00:00, 2nd with 01:00:00:00 and so on) On our ORB XF we have 16 cue stacks representing the 16 songs. Each cues in theses stacks are triggered with the related MTC offset This is what happens: if we start 1st song, first stack gets triggered ✅ If we after this start 2nd song, 2nd stack gets triggered ✅ and so on...✅ So if we play all songs in the "correct" order the stacks are called correctly BUT: If nothing was played so far and we for instance play song 15 (with offset 14:00:00:00) ALL stacks from 1 up to 15 get triggered simultaneously! ❌ So every time you start a random song all stacks with offsets less then the offset of the played song get triggered as well.❌ I think this is not how it should be?! Did anyone experienced something similar? Best regards Sven

Hi Edward thanks for this hint. We really have a couple of multicell fixtures. I will email the Showfile. Best regards Sven

Hi all I just started to prepare our desk for a new show based on 7.10 and realized it especially on recording a cue is pretty laggy. It sometimes really takes some seconds until the desk responds again. Does somebody else experience this? Best regards Sven

Hi all I hope this was not already added but I‘d have a which/proposal for color fanning on legacy devices with no multitouch available: What about if you just could click the two „endpoints“ of the color range one after the other? I know you could do it also with a connected Tablet but I think this might be not to hard to implement and would give some extra value 😉 Best regards Sven