Absolutely....
I do that now with no issues.
Don't confuse setting a static IP on the controller with setting multicast for communication with the controller.
You can set the ESPIXELSTICK to have a static IP and set it to use Multicast. Setting it to a static IP is just so you know what that IP will be when you want to do any changes using the GUI.
the sACN priority has no effect on any of the DIY controllers commonly used around here. That's usually found in commercial architectural lighting systems. What it does is give the controller information on which data to use when there's two devices sending data. This is typically the building's automated lighting system, and a theater lighting system, and maybe an emergency system like from a fire alarm system. The controller will use the data with the highest priority. So if the house lights in a theater are getting data from a building lighting system with a priority of 100, it will use that data. But if any data comes in with a higher priority, it'll use that instead. So the theater lighting system might have a priority of 200. So whenever there's a production going on, it uses the data from the lighting console rather than the building system. The emergency system probably has a priority of 255 so that it overrides everything else and can turn the lights full on for an evacuation scenario. But again, none of the DIY type Christmas boards employ this feature. They all ignore it. Vixen includes it because we do have users who have the more advanced equipment and setups.
Yes it's possible to mix multicast and unicast. But when you're using multicast over wifi, you should limit, or altogether eliminate all unicast traffic on the wifi portion of the network. In other words, only use multicast devices as wifi clients. And close those web browsers watching their status pages while you're troubleshooting. That's always unicast.
My thinking was maybe if the same broadcast was hitting every controller the same maybe it was collision issues or something. I switched to Unicast thinking perhaps with traffic being specifically directed to an IP that would help filter traffic with the result being less lag or loss.
That's not really how it works. WiFi, being a radio medium, is inherently a broadcast topology. The Access Point can only send one thing at a time. And all clients can hear all data being sent. It's up to the client to decide whether it's meant for it or not and to act accordingly. That being said, an AP is a bridge between a wired and wireless network. The AP will only send data on the wireless network that's intended for clients it's servicing. (It keeps track of it's clients for this purpose)
The difference between unicast and multicast on WiFi is that unicast traffic is only intended for one client. So the AP waits for that client to respond that it got the data. If it didn't, it'll retry until it does get it, and gets it correctly. THis takes time and causes everything else to wait till it's done. Multicast is transmitted with the assumption that it can't possibly acknowledge all receivers and manage the retransmit as necessary, so it doesn't do that for multicast. It's a "spray and pray" mechanism. With sACN, since timeliness is more important than accuracy, it makes multicast more appropriate than unicast, even if there's only one client per universe. If the data is retransmitted, and arrives late, it's stale. You don't want to see that data anyhow. You're better off either using data you got, or using nothing at all at that moment. The next good one will eventually come thru, at the right time and your device will be using the right frame at the right time.
I am in the same situation and frantically looking for a resolution. This is a major deal breaker for my show! I am in back up mode trying to reconfigure wired controllers to pick up the slack! When in multicast the lag is horrible with lots of sequence errors. when in unicast the sequence errors drop but there is stil a 2 sec or more lag when running a sequence. I have a loco nano as my AP and the multicast settings are all correct. The router i am using is only in wired mode and there are no internet connections to the show computer. Can anyone help?
I had this once. I didn't have a problem in my (man) cave with an internet connection at the WAN side of my mikrotik router, but dit have it in different churches where we played Jesus Christ Superstar (without internet connection). I fixed it by connecting the lan side of a linksys router to the wan side of my mikrotik dhcp-server/router/modem. Once I did that, all problems moved away, when disconnecting problems returned. Never found out why it helped. So with cable 1 connected all worked, with cable 1 not connected I had a 3 second lag. I had 3 espixelsticks connected using a total of 4 universes
Update on my issue.
I switched to multicast and still had issues. Tried a different ESP and couldn't get it to work at all. Went to flash it again and realized didn't have the tool so re-downloaded and flashed. When it booted up it looked different and then I realized I had been using version 2 instead of 3! grrrr...... What ever my issue was before is gone now. Flashed all my ESPs to v3 and viola! (I blame the blinky flashies for my brain deficiencies)
If you guys are running v2 like me, upgrade! Here is the link, I did the 3rd from the bottom:
https://github.com/forkineye/ESPixelStick/releases
Hopefully this will help you guys too.

