Scene behaviour with dlive & ip8

Hi all,

first post in the new forum, but dlive user since 2018…
We’re using a c3500 for foh and an IP8 for Monitoring. To switch the monitors we’re using scenes, which can be selected in the IP8, so far so good.
Now our team wants to change the layout of the IP8. Therefore some scenes were changed, meanwhile it was noticed, that fireing up a new scene directly from the c3500 doesn’t show up the layout change in the simulator mode. Only if the scene is selected directly on the IP8 / or in the simulator screen at the mixer it does the layout change.
Is this behaviour as intended or a bug?

Thanks

First, is the IP8 connected/assigned to the C3500 or the Mixrack?

Second, are you recalling the exact same scene on both the IP8 and the C3500 or are they different scenes? I would say to double check your scene filter (if there is any) as well as your global filter settings. It is easy to mess up the scene filter because there are both Surface and Mixrack IP controller filters and you want to make sure you are actually allowing changes to the exact unit you want to change.

PS - we have a similar setup to yours and don’t have a problem recalling the exact same scene either from the IP8 controller (scene assigned to a button) or from various Director software instances. (We are actually a “surface-less” setup). Recalling the same scene from either device will result in the same results. Those scenes are for IP8 layouts only, so we have the scene filter set up to block everything except the specific IP8 controller that we want to change.

Sorry, I forgot to mention that the IP8 ist connected to the mixrack. Yes, we’re recalling the same scene from the IP8 and the surface. The scene filter is set up to block all except the IP8.

Not to beat a dead horse, but are you sure the filter is set correctly. There are LOTS of controller options listed in the filter section and it is easy to accidentally select the wrong fitler. For example, there is an filter to select the “first” IP8 Controller under both the Mixrack section and the Surface section. It’s entirely possible that someone selected the filter for the Surface’s “IP8 Controller #1” device instead of the Mixrack’s “IP8 Controller #1” device.

I’ve fallen “victim” to this mistake myself and I am reasonably confident this is the root of your problem.