Auto reopen on crash
-
No problem. I didn't do much really to be honest.
I'm not sure how you would change what version to open though. -
i'll experiment with a patch made in of25 etc etc.
-
Because the applescript is telling finder to open the patch, finder uses the first application it finds that will open the file by going through the application folder in the order they appear. The lower numbered earlier version is listed before the more recent version so it uses that. If you rename the old version so it is listed after the newer one (for example calling it olderisadora) then the finder will use the newer version. It will also mean when you double click an izzy file the newer version will be used as well.
HTH -
@nick thank you :)
-
[EDIT: attached new version of script with instructions embedded in the script.]Dear All,
Good one Graham. Here's a slightly improved version (as an Applescript file... you can paste this in the the Automator I guess) where you can specify the exact path to the Isadora application you wish to use, thus avoiding the problem mentioned by Nick above.There are two "property" statements at the top. There you can specify both the Isadora application you wish to use, and the document that will be opened. Editing the first of these will determine the specific copy of the Isadora app that will run.These app and document files are specified as normal Unix paths... which I think is more convenient than the standard Applescript method.Cheers,MMedia Artist & Creator of Isadora
Macintosh SE-30, 32 Mb RAM, MacOS 7.6, Dual Floppy Drives -
thanks for this mark.
i got it working after i checked "enable assistive devices" in the mouse and trackpad section of the universal access of the system preferences and i made the document path "/Applications/Isadora/Isadora watcher/test.izz"this is well sweet :) -
if i had a patch that used inputs from osculator, am i correct in thinking that i could add stuff about osculator into this script too ?
i see the benefit of this script as a start after crash and start at the beginning of the day.most excellent :) -
I cant see why you couldn't add osculator to the workflow.
Or maybe make an app all of its own and make both of them run at start up. -
I have turned Marks script into an App. Just for those who find it easier to work with; I use it this way so on start up the machine automatically loads this app and kick stats isadora.5a886c-isadora-watcher-mc.app.zip
-
I now have a new problem..... After about two hours of running an Isadora patch it is locking up. No crash. Just goes still and as soon as I move the mouse I get the spinning beach ball.
This patch needs to run for 8 hours a day; best I can get is 2 hours. Bit worried. Does anyone know if I can make automator look for "not responding" instead of crash... because Isadora isn't even crashing.I have a feeling this is a Quicktime issue.... -
i wish i could help skulpture but i feel all i can do is offer supportive words in a post following yours. can i ask what the patch is doing, sorry i mean what does isadora output and is the 2 hour thing in any way related to a mulitiple of the loop time of the piece, i have of course gone for the big assumption of a looping video....
-
The patch is doing quite basic stuff;
- Pick 1 of 6 videos and plays it.- If no video is chosen after 2 mins it plays a demo video.But it will be running all day 5 days a week. It keeps hanging up after *about* two hours.I am sure I will sort it out but I can't seem to understand why its happening right now. -
i sounds quite a quandary. could it be at all related to a system thing like put hard disc to sleep after 2 hours? r u testing the patch by letting the demo run every two minutes ? does this all take place in the same scene ? my approach here is asking questions with the intention of doing things with the stuff u already know.
-
Nope all energy saving and screen savers stuff is off; checked that.
Demo video is running every 2 mins with me now and again triggering a video.Videos are in various scenes, so no not just one.Weird huh? -
oh yes ! do you suspect it to be connected to quicktime memory leakage filling up the ram ?
-
have you looked at the console output ot see of there are any clues in there ?
-
@particlep - I have a feeling that's it.
@nick yes but it doesn't mean much to me. My coding/programming skills are next to nothing... -
i"m only aware of it as i"m remembering a post somewhere on the original forum by mark about it. as a way of testing it, if u were to make a demo video file that is twice the size of the existing demo file, what do u see happen to the mean time to hang ?
-
In fact it just did it now.... lasted about 3hrs25mins (approx).
Again no crash, just pauses and then beach ball.I have saved the crash file console output (wont let me attach it here as a ZIP for some reason) -
Attached it.... 01d33d-izzy-crash-gt.rtf
