[LOGGED] Warning about pjlink
-
I just had the same thing occur on our show. We installed the Send PJLink plugin and started getting both a) crashes with no warnings or b) all the actors in the scene would disappear and Isadora would stop responding and we would have to force quit.
For us, the crashing errors would occur even in scenes without the plugin actor.
We're currently in tech, running Isadora 3 USB Key, and unfortunately I can't give you system details right now but we're running Windows. I'll try to get in tomorrow morning to update this with more information!
-
Please send in a support ticket using the link in my signature if you don't have one in already.
As a fallback, you can also try @Juriaan's homemade User Actors for PJLink that predate the native PJLink plugin. You can find instructions on this thread (just ignore the parts that mention the new PJLink plugin, as that's the one you're already using), and I believe this is the download link from that thread: https://community.troikatronix.com/assets/uploads/files/1527701581637-pjlink-examples.izz
Best wishes,
Woland
-
@woland Just to add my two cents, I have had an equivalent experience with the pjlink actor. Every time I use a "Enter Scene Trigger" with a "Send PJLink" Actor, Isadora crashes. I will upload a crash report when I am out of the theater. I currently am outsourcing it via Companion.
(additionally, when I am using the Send PJLink actor, Isadora stops being able to receive OSC commands. Before it gets triggered, everything works well. After it is triggered, nothing responds. I have had to shut down Isadora and redo stream communication to get OSC commands back into Isadora. I don't know if there is an actual causal relationship between these two things but in the heat of the moment, they feel connected)
Isadora 3.0.7, Radeon RX 480, MSI, Windows 10
-
@wwachalovsky Just following up on this as it continues to be an issue for me. In my experience the crashes only occur when jumping between scenes at the same time as sending a plink command. I've come up with a successful workaround by creating a second instance of Isadora that only sits in one scene, but receives command via a listener (or OSC) from the main show file which broadcasts the desired triggers to the pj link actor in this secondary instance. It's maybe a little clumsy, but it has resolved my issue. I can share a file to give you an example of how this works if that's useful.
-
@wwachalovsky said:
additionally, when I am using the Send PJLink actor, Isadora stops being able to receive OSC commands
Yes, we've had other reports of this issue and are looking into it.
-
Thanks for offering to share your workaround. It would be wonderful if you could post the file here for others to use if/when they run across this thread.
-
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:
-
@woland are there any news on this bug?
-
This is the first I've seen this error, and I don't know of any workaround or fix currently.
You are using an USB version of Isadora?
If so do you get this error if you run the project in a non usb version (demo mode is fine)?
-
@dusx Yes we are using USB edition. Actually there is one other Thread connecting this Error to PJ-Link: https://community.troikatronix...
I currently rehearsing but will try DEMO aferwards.
-
@dusx I just tested the Actor in the demo - it did not crash instantly, but after aprox. 10 triggers the Program crashed. This time it did not show that HASP Error, instead it generated a crash report that i submited. unfortunatly that did delete the crash-log from AppData so i was not able to read it first?
