Easy Snapshots For User Actors With User Actors Inside Them

DusX

Looks great!

Nice clean patching & powerful.

jtsteph

@Woland . As I am digging in to optimize all of this in izzy3, I decided to switch to a pair of midifighter twisters. They are very logically laid out so doing the patching is about 100% easier. The CC values for the Encoder, Push Encoder and Push Button are all the same for each bank, they just change the channel. I am wondering if there is a more elegant way to do the bank selection. I am using a router to feed triggers to tigger text with the given names of global variables for the cc id numbers. It's in the "Twister Bank Selector" user actor here. (I cannot seem to get the stills to display in the right order, so I have numbered them here)

# 3 Bank Selector

#1 Json Out

#2 Twister Bank Out

Juriaan

Hi there @jtsteph

This is the actor that I use for the Midi Fighter Twister, feel free to take a look :) (I absolute love my Midi Fighters !).

All the knobs are in my setup in "Super Knob mode". In the Twister Scene you see what I do with two seperate user actors, one is the main logic, one is the receiver. Just select the bank and the knob that you wish to receive and you are done. It also allows you to send it using a broadcaster to an other scene (Please be aware that the Twister scene needs to be active in the background)

MidiFighterTwister.izz

jtsteph

@juriaan. Thanks for this. I will check it out tomorrow!
Edit: just took a quick peruse. Super cool! I am not using superknobs - but am using push encoders and toggles. I am particularly interested in your Parser actor! Very powerful.

Woland

Upload your magnificent creation to the Plugin page ;)

jtsteph

@juriaan. Do you find the the broadcast/receiver actors slow things down for you at all? I will be using 2 twisters with encoders, push encoders and toggle buttons over 4 banks = 348 possible receivers from 8 senders ( i organized my jsons into small groups based on the banks - my javascript is not very good :-).

Juriaan

Hi there @jsteph,

I personally never tried it out with 348 possible receivers. I don't think that Isadora will take an massive hit, but with anything with Isadora, try it out and optimize if it seems that it doesn't work out.

If you ever need help with some JavaScript, hit me up at the forums or send me an email at hello@juriaan.me

DusX

@jtsteph said:

broadcast/receiver actors slow things down

Assuming you mean broadcast listeners, I think it is very unlikely that these actors will have any noticeable overhead. The grouping/ungrouping of the JSON is far more processing intensive, however; my testing indicates you can use loads of it before you see any real effect. Still its something to consider.. the ungrouping is heavier than grouping.

jtsteph

@juriaan. Thanks for your input and offer to help with some Javascript. I am going to work through my patch and see if there is not some way of optimizing it. Quick question for you. You are updating your actors based on a pulse. Is this to optimize overhead?

jtsteph

@dusx Yes. I mean the broadcast listeners. Thanks for your input on the overhead of the overhead of broadcast listeners vs Javascript JSON unpacking. Perhaps rather than unpacking single values from the JSON, I should unpack a bunch at once (IE a whole row from the Twister) and route them from there. I will run some tests.

Juriaan

@jtsteph

No that is because Isadora JavaScript actor has some gotcha's, the final input needs to be triggered for the code to run. Since I use Pressed / Released triggers this had to built in for the sole purpose of forcing Isadora to run the code and give me the correct values. If you remove that you won't get proper triggers :)