iMac late 2013 - 27inch
modded to 16gb ram
(no additional monitors)
I had been working on a project on my imac using the latest version of Screenflow the other day and a message popped up on the screen saying something similar to, 'run time error' and a few other words, I just ignored it and continued working on my video, that was until I realised that the functions within the software were no long operating, I couldn't edit my text or adjust size of my clip, and most likely the whole program had shut down like that. Luckily I had just began this new project, so I thought it was just some bug.
I came back the next day and started again, I had got quite far into my work until it happened again. I would really appreciate it if anyone could send across the information to avoid getting this message or recover work from it or even how to overcome the whole issue.
Sorry you're experiencing this.
Please include ScreenFlow version number as well as OS version number. Some people believe they have the latest version and may have missed an update or upgrade.
Current version of ScreenFlow is 8 and macOS is 10.13.6.
Since there are a number of potential causes of runtime errors we need to know exactly what you were doing. Usually runtime errors are a repeatable sequence of events.
To recover work depends on whether you saved it or not. If saved, that saved document should be available. I strongly recommend saving after recording or importing as that moves the sources into ScreenFlow and saved the document with the media.
Otherwise the recording, an .scc file, is saved in a temporary location you can designate in ScreenFlow > Preferences > Advanced > Capture Scratch Disk
If you didn't save the document we have these instructions that will help you find the recording.
I was using the latest version of ScreenFlow as I had just bought it a few days before I messaged.
Also my Mac is working on the latest version of MacOS
I wasn't doing any voice overs I was just snipping editing text and other general things and the message popped up although the next day I opened the file trying to see if I can press anything and it will work but after opening it and messing around I found that the project was recovered and operational again.
Thank you for your quick response, It was very useful for my issue.