My experience is that Preload can make the behaviour much worse. I would recommend to remove preloads.
Also, decrease the image resolution. I was panning large jpgs straight from a DSLR. The images where much larger than I required. After cutting the resolution by 50% playback became solid (300k to 1mb doesn't seem huge, but still perhaps useful if possible)
PLEASE, let us know if any repeatable cause/trigger can be found.
RESOLVE....and for all the MSI computer user : when I double click with a finger on the touchpad to open the actor user, it crash.....but when I double click on the button (like a mouse), it work.....just crazy.....
Thanks a lot for confirming that issue and for confirming the workaround. Makes me think that if Isadora can capture the stage to a movie it should be able to capture the input directly. I'll file a bug report. Thanks, Kevin! Cheers Mark (not him)
Thanks for the batch file @DusX! My onboard graphics are disabled in Bios, so only this card currently exists for the system. I never had a crossfire setup.
I experimented a bit and found that the problem occurs as soon as there is more than one display device connected. I have a two monitor setup, so I did not notice this before. One monitor: starts fine. As soon as I connect a second monitor or projector, it freezes.
It happens on both of my video cards, so I assume it is a problem of initiating the stages to the connected displays. If I set all stages to "none" in the preferences I can start up with 2 displays. If I then try to set stage 1 to the second display in Isadora I experience a regular crash. The crashdump references a lot of video related dlls and says that "the thread tried to read from or write to a virtual address without having the necessary access rights".
Thanks for jumping in here with that fix. I hadn't seen this thread until today, but you beat me to the punch.
The problem is that 10.9 cannot support HAP playback on AV Foundation. While we no longer officially support anything less than 10.10 (and that will become strict in September 2018 with the release of Isadora v3) I discovered the problem and fixed it for @artoo. Hopefully it will eliminate the issue for @DanielB.
Let me say it again: Isadora v3 will not run on anything earlier than 10.10. Please keep that in mind as we head towards that release.
What was the error message? I have been having an issue which sounds similar and I get the response "The media file could not be loaded because of an unexpected error.. May be corrupt" with error number = -108. If I don't close and re-open the patch, Isadora crashes or stops allowing me to save, though sometimes it shoots up its own collage of the images (some of which weren't part of the scene or bin the media was in) like some kind of AI modern art project before it does so...
The corrupted image (a digital cut and paste type thing of Isadora's own making as opposed to the nothing that shows up when I simply lose the media) happened far more frequently when I added HSL Adjust actors.
It happens with different still image file types and the resolution of the images seems to be irrelevant. For me the issue started when I was using 2.5.2 and I was told to update my Isadora to the newest version; however, I still get the error and it stays with the patch if I move to another computer.
There was an issue with font rendering being changed by Apple causing a draw slowdown that could be scene in the scene editor as you mention. Mark made some changes to address it and I belive an new high sierra update also helped.