{"id":47,"date":"2009-08-14T18:42:54","date_gmt":"2009-08-14T23:42:54","guid":{"rendered":"http:\/\/blogs.bu.edu\/ryeany\/?p=47"},"modified":"2009-08-14T19:03:28","modified_gmt":"2009-08-15T00:03:28","slug":"screenflow-bug-report-vent","status":"publish","type":"post","link":"https:\/\/blogs.bu.edu\/ryeany\/2009\/08\/14\/screenflow-bug-report-vent\/","title":{"rendered":"ScreenFlow bug report \/ vent"},"content":{"rendered":"

ScreenFlow<\/a>, at version 1.5.4, still occasionally gives me that Beta feel. While working on the overview screencast for Restricting Access today, I found two bugs. It was not a fun day. TGIF. I’ve reproduced my error report\/vent to the ScreenFlow support team below.<\/p>\n

Two major, unrecoverable errors were encountered today and I lost hours of work.<\/p>\n

1)<\/p>\n

I had 3 text items selected and changed the font size on all of them at the same time. The text itself was not highlighted — the bounding boxes around each were selected because I had Command+clicked them to make a multiple selection.<\/p>\n

Well apparently applying a font size change to a multiple selection (all text items) is a VERY BAD THING. While it appeared to work visually, I was then unable to move the items, or delete the items, or save my file, or anything else without a whole host of runtime errors.<\/p>\n

I had saved the file before attempting this multiple-item font size edit, so I force-quit the application, rebooted and re-started Screenflow. When I attempted to re-open the file, it started to open (I see stage and timeline, with all my items in place) but then Screenflow just crashes with a standard MacOS alert box “The application ScreenFlow quit unexpectedly…” with the Ignore, Report, and Relaunch options.<\/p>\n

——<\/p>\n

After starting again from scratch and working a couple more hours (saving the file regularly) on the same presentation (and vowing to never attempt to apply font size change to multiple text items) I encountered another error.<\/p>\n

2)<\/p>\n

I needed a small, static screen capture included in my screencast. I used Skitch (which is a great screen capture tool) to do a small screencap. I changed the file type to PNG, and dragged the screencap from Skitch into my ScreenFlow media library. I then placed it on the stage and began editing it in the timeline (video transition, etc.).<\/p>\n

When I attempted to save the file, it would not save. I regret not writing down the specific error message, but it was general in nature and did not refer to a specific error (cannot save your file for unknown reason, or something along those lines).<\/p>\n

As before, I force-quit the application and rebooted, thinking I could open the file and at least get the previously-saved version. But no, when I attempt to open my file the same thing is happening as in error #1 — it begins to open the file, I see stage and timeline, but then ScreenFlow crashes with the same “application quit unexpectedly” error.<\/p>\n

I AM able to open and edit several other ScreenFlow projects I have previously worked on.<\/p>\n

——<\/p>\n

This is indeed frustrating because I think ScreenFlow is a fantastic program and there is nothing else out there that compares.<\/p>\n

I’ll keep using it, but I’ve got a growing list of quirky things I need to avoid doing because of these bugs. Don’t apply changes to multiple text items at once. Don’t copy\/paste from Skitch. Apparently I should just copy any and all content into the project folder and ONLY add it to my library via the tools in ScreenFlow. And only edit one thing at a time. Etc. And I’ll be saving multiple versions of each project in the hopes that if I can’t open my previously-saved version, maybe I would be able to open another copy that’s a half hour old.<\/p>\n

<\/vent><\/p>\n

Ron Yeany
\nryeany@bu.edu<\/p>\n","protected":false},"excerpt":{"rendered":"

ScreenFlow, at version 1.5.4, still occasionally gives me that Beta feel. While working on the overview screencast for Restricting Access today, I found two bugs. It was not a fun day. TGIF. I’ve reproduced my error report\/vent to the ScreenFlow support team below. Two major, unrecoverable errors were encountered today and I lost hours of… Continue reading ScreenFlow bug report \/ vent<\/span><\/a><\/p>\n","protected":false},"author":101,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1595],"tags":[],"_links":{"self":[{"href":"https:\/\/blogs.bu.edu\/ryeany\/wp-json\/wp\/v2\/posts\/47"}],"collection":[{"href":"https:\/\/blogs.bu.edu\/ryeany\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.bu.edu\/ryeany\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.bu.edu\/ryeany\/wp-json\/wp\/v2\/users\/101"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.bu.edu\/ryeany\/wp-json\/wp\/v2\/comments?post=47"}],"version-history":[{"count":3,"href":"https:\/\/blogs.bu.edu\/ryeany\/wp-json\/wp\/v2\/posts\/47\/revisions"}],"predecessor-version":[{"id":50,"href":"https:\/\/blogs.bu.edu\/ryeany\/wp-json\/wp\/v2\/posts\/47\/revisions\/50"}],"wp:attachment":[{"href":"https:\/\/blogs.bu.edu\/ryeany\/wp-json\/wp\/v2\/media?parent=47"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.bu.edu\/ryeany\/wp-json\/wp\/v2\/categories?post=47"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.bu.edu\/ryeany\/wp-json\/wp\/v2\/tags?post=47"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}