@emtv

Feel free to open a support request, and we can look into your issue for you. (link in my signature)

@jtsteph said:

And just to confirm here, the output from the JSON Parser is always text? I am using the Text Parser to change the data type to integer currently. Is this best practice?

 Yes, JSON is text, and the data is untyped. Text Parser is a good choice to use, You can also pass the 'text' number into a JS actor, and simply pass if back out with out modification, the JS actor will allow you to mutate the value to a number. It sounds like you have it working well though.

@woland Very helpful. Thank-you!

Is this helpful?

momentary-trigger-with-values-and-text-2024-01-16-3.2.6.izz

@fred

thanks for the help Fred

I have tried many combinations of outputs: (and different computers both m1 and m2)

the native HDMI + usb-c to HDMI (adapters)

all Displaylink connectors

a combo of Displaylink (Pluggable interfaces using the DP drivers -- and the native HDMI)

all tested to both mixed projectors directly and via identical blackmagic HDMI to SDI converters

in all cases the result is the same (no combination was better or worse)

I get dropped frames on each screen separately and not on "one screen"
nor do I get synchronous errors across all screens (they happen randomly on all three screens after about two minutes)
such I do not believe it is the connections

Rather I think there is an error occurring in the system (it really may not be an Isadora fault - but rather a system OS problem)

My opinion is that there is some event in the control of the Thunderbolt Buses that is causing it to change "priorities" of service
Isadora is only using a small tiny percentage of the CPU or GPU -- so small that the OS may think it's ok to move to efficiency cores (?)

(we have seen something like this before in the move to AVfoundation in the past)

I am in contact with troikatronix and they seem to think there might be a fix to be had in a new beta release

I have not tried leaving the connections up - but only connecting one screen -- I will do later today

thanks

Garret

PS - for "most" video this would not be seen - in my case the video source is fast moving objects (cars) moving across screen as such any and all frames lost are easy to see)

so yes this is an edge case

That did it. Thank you so much!

@tr742

wav format is fine:

Never mind. I dug further into the LoupDeck programming and you can have the button push jump to 127 and the jump back to 0. If bundle this output into a JSON then go JSON PARSER->TEXT PARSER->COMPARATOR looking for 127 I get my button trigger. 

And just to confirm here, the output from the JSON Parser is always text? I am using the Text Parser to change the data type to integer currently. Is this best practice?

@jtsteph

I made them because I got tired of having to recall an actor with the right data type off the top of my head.