We are currently experiencing an error that may as well be the same. We use the PJ-Link Actor on Isadora 3 on Windows 10. After using the Actor Isadora keeps working for some seconds. In that time it seems Isadora is completly functional, we can switch Scenes and edit Parameters. After a view seconds though it crashes and we are presented with the following Error Message:

screenshot-2024-10-08-214828.png

@bonemap

yes I encountered the same issue.

Best regards, 

Jean-François

@jfg

hi,

Thank you so much for demonstrating this workaround - I am wondering if you encountered the same issue and buggy behaviour working with the Color data type through the Data Array?

Best wishes

Russell

@bonemap

perhaps something like that:

in the Text Formatter:   P1:Z3 P2:Z3 P3:Z3 P4:Z3

Best regards, 

Jean-François 

@armando

I will make a comparison of building a dmx lighting system with json sets and Data Array sets to see what is possible. At present the system will be used for a show that deploys wdmx rgbwau led battery pars and multiple projectors for an outback touring circuit. Basically a virtual lighting board. So want the ability to preview, record, delete, insert, add, replace value sets that can be cued for performance. The Data Array is an obvious choice for this kind of functionality.

Best wishes

Russell

@woland said:

<p>@bonemap</p><p>Have you considered using the JSON Bundler and JSON Parser to bundle and unbundle the HSBA values for transportation through a single data line?</p>

 Hi @woland,

Thanks for your advice about using the json option for building a dmx system. I will definitely have a look at how that might work. The system I am designing uses the functionality of the Data Array to record, recall, delete, replace, add etc. for a series of WDMX rgbwau battery par lights. The values are previewed through the system and then recorded in value sets that can then be triggered as cue’s. Of course the Data Array has that functionality straight up so is an obvious choice. I found using the Color data type through the Data Array buggy.

Best wishes

Russell

@bonemap Hello, that is why I asked the collective wisdom to participate. I imagined (but didn't say) that in the window I proposed, a value (i.e."rate" property of an envelope generator),  when clicking an entry of the window,  hilights (selects) the right envelope generator in the patching window. Again, just an idea. Mark is generally great at imagining better and simpler ways to do that. Another idea is to highlight in red all the control id number in each control that are not yet connected to a property in an actor in the patching window is red until it is connected to a property.

And I'd love the same thing in the patching window. As a matter of fact, at the moment, if in the patching window, an actor has a property with a control id it it means that there is a control that it is linked to. But if I erase the control of the actor with the same control ID, said control ID keeps looking the same. Now, this has never been a problem, for me, but in a large patch with dozens of controls having a red control ID in actors AND in controls that become red if either have been erased could make us see immediately the problem visually. Instead of looking through numbers

Another advantage of this window could be reassigning id. I generally tend to separate with 10 or 100. The 100 is video stuff, the 200 is the audio stuff, 300 is light, 400 sensors, 500 mocap 600 scenes activation. etc. In this hypothetical window a search field could function as a multi-criteria filter.

one way to filter is by number. This could also be a way to sort by number all the control IDs. Another filtering could be by actor name (even with multiple trigger text actors, for instance they could be put in a list. Also filtering could be by control name and put in a list. Clicking on a control in the control widow could hilight the right control and the right actor that are connected with the same control ID.

I am just trying to think wth all of you.

All the best

@woland Hi woland. Working with Json anData array seem to me 2 very different things isn't it ? The best thing in Data array is that you can write (and overwrite) values in a specific line (say a bunch of dmx values to control light intensity and color. Of course Json bundles can read a json text file on the computer (never tried but in theory possible, isn't it?). The problem with the Json bundler reading a prerecorded file is that the said file needs to be updated manually in a text app if I want to change a cue, while DFata array allow me a quick editing of the file and an equally quick test of the updated values. Am I right ?

@bonemap +1 on working with JSONs. It is a really great way of muxing and unmuxing a bunch of values. You can also use the Javascript actor to pack an unpack the JSONs with custom math or logic to allow you to modulate and and modfy parameters all in one actor. Chat Gipity is quite good at assisting with building javascript patches.

@bonemap and @Armando 

I love the idea of unique addresses...like OSC. You could map the whole thing out in a spreadsheet this way, which is how I have been doing all my midi and OSC mapping. It's very powerful and flexible.

I have another idea that is not a programmatic solution, but perhaps something easier to implement (?) that would save time for users:  

Perhaps a functionality that would allow the user to create actor/controller connection by selecting an actor value with a combo-key-click in the patching window and then a combo-key-click in the controller window on the controller. When this is done, the user could be prompted for a CTL# or have isadora choose an free CTL#. 

In addition, for controllers than have multiple values (IE X/Y coorinates), when combo-key-click-ing the controller, the user would get a prompt to specify which controller value will be connected to the actor value.

Just thinking out loud.