@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
new screenshot attached. Will check your recomendation, thanks!
Hello all,
I was curious if anyone has an approach they use for midi cc latching, i.e. preventing a midi cc value from changing until the incoming CC value matches where it was previously left off. Picture a midi controller where the same 8 knobs control different parameters in different isadora scenes. If I leave scene A, use the midi controller in scene B, and then come back, the values of the knobs could be much different than when I left scene A. Using any of these controls then will create a large jump in value that is often undesirable for me. I would like to be able to implement a behavior such that moving those controls when returning to scene A would have no effect until it reaches the value previously set upon leaving that scene, then pick right up from there and function normally. I imagine this would be some combination of gate and comparator actors, but I'm stuck at how I can store and poll the data about the last held CC value when entering a scene. Has anyone else implemented a similar function in one of their patches? Any help or guidance would be much appreciated, as this is something that would make operating my patches live much smoother.
Best,
JP
Can you post a screenshot showing what the rest of the video input options are for you when you go to select one in Live Capture?
@stj said:
What would you use as an alternative?
I've always used AirBeam Pro.
Here's a revised version that incorporates restarting videos at the start of crossfades: https://www.dropbox.com/scl/fi/zgbnwx2x07tvqepq370oi/Virtual-Stage-Crossfades-v2-2024-03-14-3.2.6.zip?rlkey=rcaqgtwtksevbk2d2wv9h031y&dl=0
Also this file of mine shows a few different ways to do crossfades with video that you might be able to recycle: https://troikatronix.com/add-ons/random-media-random-duration/
The driver you need for this is the 1.8 version. That I can tell you certainly.
I am unable to run a test on Windows 11 with the Kinect 1414 until tomorrow. Once I am able to run through the setup again, I will update you with anything I find.
In the meantime you may want to run DISM and SFC to ensure you don't have any corrupt system libs.
see: Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support