0

Screenflow 6 Unusable Because of Hanging Beach Ball

Hi folks.

Screenflow is basically unusable for me right now because the beach ball of death hangs for so long and so often.

Every time I try to move a clip or make a slight change on the timeline, it hangs for 5-20 seconds.

I'm combining A-roll and B-roll footage plus music.

The .screenflow file itself is about 24GB.

I'm using Screenflow 6 on an iMac Retina 5k 32 Ghz Core i5 with 24GB of RAM and an AMD Radeon R9 vcard.

I've got 397 GB free on my hard drive (which is also my scratch disk).

Any thoughts on how to fix this?

Thanks!

Anthony

17replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Anyone? I could really use a workaround because I've got a big project due next week!

    Like
    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 5 yrs ago
    • Reported - view

    Anthony Korahais I'd like to help but I'd need the exact version of ScreenFlow and OS.

    You should update to ScreenFlow 6.2.3 and test again.

    It's also possible certain files became corrupt or are difficult to decode so I'd need to know what types of imported files you're using.

    If fast response is a priority please do consider our Premium Support

    Like
  • I'm importing a variety of video files: .mov, .m4v, .mp4

    I'm on 6.2.2.

    When I try to upgrade, it tries to upsell me to 7. I can't find a way to upgrade to 6.2.3.

    And now it seems like you're trying to upsell me to Premium Support?

    I have to admit that I'm starting to see why so many people in my business groups are complaining about Screenflow...

    Like
    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 5 yrs ago
    • Reported - view

    Anthony Korahais ScreenFlow 6.2.3 download is under Previous Versions
    Premium Support may provide faster response than the forum and also offers remote login. If you're in a hurry there's value in that. You expressed you had a deadline so I offered you the possibility of faster and more detailed service not provided by the forum.

    Please update to 6.2.3 and test. If there's still an issue I'll have more things for you to try. It is possible that some sources can push an i5 processor very hard.

    Like
  • CraigS thanks for your help.

    I found 6.2.3 and I'll try that.

    Regarding the i5 processor, I have a CPU monitor and that's not the problem. I can clearly see it go up when exporting, but that's not when my problem occurs. 

    My problem occurs during routine editing on the timeline. And when it happens, the processor is typically under 10% usage.

    Like
  • Nope. The upgrade didn't help. To give you examples of what's happening...

    • I hit control T to zoom out to the entire timeline and I got the beach ball for 7 seconds. CPU never went above 10%.
    • I hit I and O to select in and out points, then hit ripple delete, and I got the beach ball for 28 seconds. CPU never went above 35%.
    Like
    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 5 yrs ago
    • Reported - view

    Anthony Korahais Let's try to clear out a few things. Make sure ScreenFlow isn't running. This should clear the cache and rest the preferences.

    Delete ScreenFlow Cache:
    1) Make sure ScreenFlow is not open. (save any work in progress)
    2) Open a new Finder window.
    3) Select the "GO" menu top of screen, Hold "Option" key with menu open, and select the "Library" that appears.
    4) In the Library folder open Caches folder.
    5) Delete ALL folders that start with “net.telestream.screenflow(4/5/6)”
    6) Empty trash.

    Part 2:

    Reset ScreenFlow Preferences:
    1) Make sure ScreenFlow is not open.
    2) Open Terminal and copy and paste this command and press Enter:To open "Terminal" (Finder > Applications > Utilities > Terminal).
    defaults delete net.telestream.screenflow6

    Like
  • CraigS thanks. I tried both tips. Unfortunately, neither one helped. 

    Like
    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 5 yrs ago
    • Reported - view

    Anthony Korahais Perhaps there's an issue with the project itself.
    How long is it and how much imported media do you have?

    Try creating a document only doing screen captures of an equivalent amount of media. This is to test if the media imported is at issue.

    Something else you might try is to download the free trial of ScreenFlow 7.1.1 since it should have improved media handling. One test would be making a copy and then importing the project (preserve the original so you can keep using it in 6.2.3). Another would be importing the media into a new document and testing that.

    Basically we need to determine if the imported media is the cause and/or the document.

    Like
  • CraigS I'll try those things. But this has been happening with various projects for some time. The only piece of media consistent to all of them is my logo watermark. I'll delete that and see, just to be sure.

    Like
    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 5 yrs ago
    • Reported - view

    Anthony Korahais see if 7.1.1 helps. If it's not happening to most users it may be source related. Logos should be near the actual size needed and at 72dpi. In other words if you have to scale down graphics significantly or have a much higher dpi (common for print but video is 72dpi equivalent) then they can tie up significant system resources. 

    Like
  • CraigS okay, now we may be on to something. Are you saying that large image files (pro quality) that I paste in as B-roll could be the problem? If so, then that's something I'll also try.

    Regarding 7.1.1 what if I do the free trial but it doesn't help? Can I go back to using 6.2.3 with no problems?  

    Like
  • CraigS that didn't work. I created a new document, cut and paste only the .mov video clips and .m4a audio clips, and I'm still having problems. So no pictures, no b-roll footage, no logo -- just a-roll audio and video. 

    So frustrating. I just want to get my work done. I guess I'll try 7, but I'm worried.

    Like
  • CraigS tried it with Screenflow 7.

     

    Got this runtime error:

    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 5 yrs ago
    • Reported - view

    Anthony Korahais Let's see if it's a user or system issue. Create a New User Admin account. Reboot and log into the new account. Start ScreenFlow with a new document and import one clip test, import the next test, etc. See if the error occurs in the new account and which file it occurs with.

    Like
  • CraigS I'll experiment, but that runtime error is pretty worrisome. Got any idea what it means? It happened regardless of the project. I couldn't even create a new document.

    I'm glad I saved the old 6.2.3 application file because I'm hearing a lot of complaints about Screenflow 7 through the grapevine. 

    Screenflow is such a great piece of software, but there are a lot of competitors out there now. I hope you guys can resolve these issues, and soon! I'd just assume stick with Screenflow, but if I can't get my work done, then I'll have to look at competitors. 

    Do I really need to pay for premium support to get this resolved? 

    Like
    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 5 yrs ago
    • Reported - view
    Anthony Korahais said:
    I'll experiment, but that runtime error is pretty worrisome. Got any idea what it means?

     Since it's a general error message we need to see what the pattern is. That's why I'm asking that you run through some tests. Others generally aren't experiencing it so we need to see more about your specific workflow and system.

    With 7.1.1 we fixed a lot of the issues with the initial release of 7 so most of those complaints about issues have been resolved. The runtime errors were not a typical error reporting even in 6.2.3 though. Hence the reason why I suspect there's some combination of sources and system to this issue.

    Generally shortly after a new release, development on the previous version does stop so we can commit all our resources to improving the current version. That's why testing in 7.1.1 is important.

    Like
Like Follow
  • 4 yrs agoLast active
  • 17Replies
  • 337Views
  • 3 Following