[LOGGED] Warning about pjlink
-
I don't have any issue stepping through our file (latest build of Windows 10).
However, I have no media connected, and no projectors at the moment.
I will plan to run some pjlink tests with my Panasonic projectors when I have a free period.When Isadora quits, are you presented a crash reporting dialog?
If so, DM me your email entered to submit these reports, so I can look into the report data. -
@zedociel said:
Something changed. I don't know if it is in the panasonic firmware, or windows updates but it's really weird.
If something changed recently, it couldn't have been on our end, since the last time we released an update to the Send PJLink plugin was October of 2021.
Best wishes,
Woland
-
I know. I had a show in december with the latest izzy version and shutter control and hadn't any issue with it (same computer, older panasonic projectors). That's why it took me so long to find out what was wrong.
-
This post is deleted! -
Did you get any resolution to this issue? I tried to implement video mute and AV mute (both on and off) commands last night with two Epson ProL1405 projectors and have the same issue. I tried delaying the command to one projector so that the responses wouldn't overlap to no avail. (To be clear, the commands "work" the projectors will mute (or unmute) but then Isadora crashes to desktop.)
I'm happy to share my file if it's of any use...
-
I can confirm that I've experienced similar behavior in during the past several months. I first encountered it while using Isadora on Windows 10 computers, but then found it would also occur on some but not all Mac OS computers (using similar OS versions). It would only happen when I would jump to a new scene and had an enter scene trigger into the PJ link actor. I went about a couple different methods of resolving this including creating a second instance of Isadora that would sit in one scene and just send shutter commands when necessary, and also similar to what @Woland suggested--introducing a very short delay between the enter scene trigger and the PJ Link actor.
I'd submitted crash logs and created a topic and found a couple other folks on the forum having trouble with this, so I thought I'd chime in here to add a plus one and hope this can be addressed. It's been okay with the work-arounds, but it had been working very well previously, so I'd love to help find a solution for this.
-
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?
