Isadora gets jammed/stuck
-
Finally I came across with a way to produce the Isadora jam that has haunted me for a while. Sometimes after pausing Isadora, the application becomes stuck and many menu items are grayed out, for instance Resume Engine and Quit Isadora. It seems, however, that in this stuck situation I can still save the project.
Here’s at least one way how to produce the ”stuck state”:
1. Open Isadora and make a new project
2. Import media
3. Put ”Movie Player” and ”Projector” actors to scene
4. Pause Engine
5. Import media
=> Resume Engine grayed out, and Quit Isadora grayed out, and cannot close the project. So, only possible route to go is ”Force Quit” Isadora.
Or even a simpler way to produce the ”stuck state”:
1. Open Isadora and make a new project
2. Pause Engine
3. Import media
=> Resume Engine grayed out, and Quit Isadora grayed out, and cannot close the project. So, only possible route to go is ”Force Quit” Isadora.
I believe, this has something to do with ”Pause/Resume Engine” and making changes in paused mode. It has happened to me various times in various situations, but (if I remember right) always some time after selecting ”Pause Engine” and making changes to the project. At least it happens with the above described ways. (Isadora v2.6.1 and v2.6.2b01)
------------
Another thing I wanted to ask about the "Adobe alarm". Isadora seems to alarm if some Adobe apps/components are running, but it seems to warn only the first time I open Isadora after powering up the computer. It would be beneficial, if Isadora would alarm about the Adobe stuff every time I open Isadora (if Adobe apps/components are running) – not only the first time after powering up the computer and launching Isadora.
Best wishes,
Lauri
-
I was able to reproduce this issue on Isadora 2.6.1 USB on a Mac running OSX 10.11.4, El Capitan using the steps you described here. I had to Force Quit Isadora after running through both of the processes you described.
Re Adobe: I did receive the warning every time I opened Isadora.
Please use this link, or the one in my signature, to file a bug report with the same information you presented here. Please also include a link to this post in your bug report.
Thank you very much for helping us improve the Isadora experience for everyone.
Best wishes,
L Wilson-Spiro
-
@woland said:
I was able to reproduce this issue on Isadora 2.6.1 USB on a Mac running OSX 10.11.4, El Capitan using the steps you described here. I had to Force Quit Isadora after running through both of the processes you described.
Excellent recreate @Lauri . I've already implemented a fix. I can send you a beta if you would like to have it.
@Woland, you can also get the beta from me to test that I've really fixed it. Email me.
Best Wishes,
Mark -
@mark Thanks! Yes, it would be nice to have the beta, and I'll keep you updated if anything similar happens.
@mark @Woland I did not make the support ticket yet, so I suppose there's no need for that now, right?
@mark I sent you an email couple of days ago about the memory leak issue that seems still be there even in the beta v2.6.2b01, although not as heavy leak as before. Do you want me to do another support ticket on that or reply to the earlier posts?
Thousand thanks,
Lauri
-
-
-
-
-
@Woland Thanks! Your private email links to google account, but I need your approval to get the file from there.
-
-
@woland said:
I approved your access request! (Sorry, had to do it that way to avoid "anyone with the link can view".)
Lucas, in the future, if I instruct you to give out a beta to a user, you can just pass on the direct download links I've given the team. You don't need to upload it on Google, etc.
Thanks for taking care of this though. ;-)
Best Wishes,
Mark