@konrad

No problem. It would have also been possible to use fourteen Comparator actors (one looking for each number and triggering a Trigger Value actor with the translated number) but I had this JavaScript User Actor kicking around from something I did a while ago and it was easy enough to adapt it.

I added a second Scene named "Comparators" so you can understand the simpler way to accomplish this without the need for any coding:

adjust-midi-note-and-draw-to-stage-v3.izz

@Woland

Super! Thank you very much!

@konrad

Here you go: adjust-midi-note-and-draw-to-stage-v2.izz

@konrad

Oh wait, your numbers aren't sequential. One moment.

@konrad said:

"Note On Watcher" Delivers at pitch output these possible values:60,62,64,65,67,69,71,72,74,76,77,79,81,83,84

That range is what you're getting from whatever source you're getting your MIDI notes from. The actual possible range of outputs from the 'pitch' output of the Note On Watcher actor goes from 0 to 127.

This is how to draw the adjusted numbers to the Stage with a Text Draw actor: adjust-midi-note-and-draw-to-stage.izz

@Woland

Thanks for a value goes the suggested solution, But "Note On Watcher" Delivers at pitch output these possible values:
60,62,64,65,67,69,71,72,74,76,77,79,81,83,84

I would like to implement them like this.

At 60, a 1 should be output on the stage.

60 -> 1
62 -> 2 should be output on the stage.
64 -> 3 should be output on the stage.
65 -> 4 should be output on the stage.
67 -> 5 should be output on the stage.
69 -> 6 should be output on the stage.
71 -> 7 should be output on the stage.
72 -> 8 should be output on the stage.
74 -> 9 should be output on the stage.
76 -> 10 should be output on the stage.
79 -> 11 should be output on the stage.
81 -> 12 should be output on the stage.
83 -> 13 should be output on the stage.
84 -> 14 should be output on the stage.

Is there a solution for this?

@konrad

This is a screenshot of what @Juriaan was suggesting, which is also the way I'd do it:

@d8bit said:

I really think there's some problem/bug using the Blackmagic driver in Isadora (version 3 at least) in the Live capture settings.

The Blackmagic version we used was updated for Isadora 4, and there may be an issue with Blackmagic in Isadora 3.2.6 that we fixed in Isadora 4 as many improvements were made. I'd be interested to hear whether working with Isadora 4 in demo mode shows the same behavior or a better image.

Best wishes,

Woland

@paz Thanks a lot for the quick reply! Unfortunately, trying everything you've said (latest Blackmagic driver, using the native correct resolutions, etc), but in Isadora 3 latest version, I'm still having the same issue. Here, for you to see clearly what happens, I'm attaching two images, just capturing my own computer running Isadora. In the first image, I'm using Blackmagic drivers, getting this distortion. On the second, I'm using Apple drivers:

I would like to use Blackmagic drivers for the UltraStudio of course, as I get better performance and lower video delay.

Maybe the problem it's within Isadora v3 vs v4, but also unfortunately, right now I can't afford the upgrade. I will try the free version of Isadora 4 to check it nevertheless.

Any other ideas?

@konrad

Calculator actor with the mode set to sub, since it seems that you work in a set sequence, so we want to deduct a set offset

Value 1 your Note on Watcher output

Value 2 your static offset