@tr742
this issue could be elsewhere in the chain - I don't know if you are on Mac or Windows. On Mac, it is possible to calibrate the Display Settings to compensate for different beamers.
within Izzy, a quick hack to increase brightness of a particular stage is to run 2 Projector actors from the same feed, set to the same stage. this gives an additive blend which may work, depending on what your imagery is.
@armando @Woland - OP states that they are not using a camera - i assume it is a HDMI out from another computer, into a capture device.
this is why a BCR2000 sometimes works better than a Korg Nano, despite being 20 times the size and weight.
@armando this!! But also most controllers that have continuous encoders (not faders as this is not possible, but rotary encoding that has knobs you can just keep turning and show you the level with lights) also have a midi in. This means that you can send the value that you left the scene on back to the unit and go from where you left off.
@zedociel I Blackmagic cameras every day in 4k and everything os and looks great on a mac....
I know this is the expensive approach, but this topic is so important that I decided to invest. in a motorized fader machine So I don't have to deal with that. My 2go machines are Behringer xtouch and it's grandad BCF2000. It might sound stupid but being able to have the faders buttons and encoders all in the right -l;ace at the beginning of every scene is priceless.
@Woland I appreciate your reply but I'm not quite sure it works for my purposes, it seems to still jump around when I try and replace the simulated value change with a control watcher. Perhaps I'm missing something. That thread was an interesting read though, and I learned that 'soft takeover' is the term I was looking for instead of CC latching.
@jtsteph That's a good shout, I've been meaning to dig into those anyway as a means to more easily switch groups of midi controls to different functions within a patch, so this is just another push to take a closer look.
Either way, making this post gave me the extra thinking juice I needed to kludge together a patch of my own that seems to work as I need it to. I've attached a screenshot & user actor below in case anyone else wants to take a look at my solution. v2 would ideally remove the dependence on the enter scene value so that I can use it to stop jumping when reassigning controls within the scene, but I have a good idea on how to do that already.
If you are looking to store and poll previous states of your midi controller, you might find @Dusx's and @woland's JSON method useful. It's a very powerful and flexible way of storing midi data for saving, snapshots, comparison etc. The short story of the method is that you create a JSON that stores all the controller states of your midi controller. You can then access or store and recall these states by accessing the JSON. It's very light on system resources and gives you a lot of flexibilty.
I think what I posted in this thread might be useful: https://community.troikatronix.com/topic/1588/relative-midi-encoders/9?_=1710439233279