0

Screenflow cannot undo (in version 8.2.3) SCUndoManager 0x6000021309b0 is in invalid state

This article states the problem is fixed. However, I faced this issue in version 8.2.3

ScreenFlow can not undo. (2018, November 15). Retrieved 5 July 2019, from Telestream Community Forum website: https://telestreamforum.forumbee.com/t/k9b76x/screenflow-can-not-undo

 

My systems

Version 8.2.3 (31394)

MacOS Mojave 10.14.5 (18F132)

Technical help request case 00655687 submitted 2019-07-05 11:00 h NZT 

 

Antecedents

I'm editing a file 60 minutes long. Apple ProRes video 36 GB created from a oom webinar by using Finder Transcode service

You can view a mid-project Export here on Google Drive. Crash happened when I was working around minute 40 - 50 of the video.

 

Mellalieu, P. J., & Dodd, P. (2019). Improving Learning Outcomes from Group Assignments in Tertiary Education through Peer Feedback [Webinar]. Retrieved from https://drive.google.com/open?id=13vsmw6VHC7cbhk48fgrAEEx4mhDb0fkF

Here's what I vaguely recall what happened.....

Lots of edits done to date over about the previous 24 hours. See video above.

I created two items above the video line, at the same timecode. An image and a draw annotation.

I grouped the two actions.

I applied a video action... I wanted them both to scale at the same rate.

Then I may have tried to adjust the length of the two actions. Who knows. I would have been trying to get the zoom up video action, plus positioning to work. I had done this workflow very succesfully over the 24 of edits to date, BUT ONLY ON ONE action.

!@@#$% Crash bang wallop. $%^&@#

 

I am poised for your guidance

Currently, My ScreenFlow project cannot be saved, or duplicated. I cannot COPY ALL into a new document.

 

I await, with bated breath, guidance on what next. I'll be patient for a couple of days. 

 

I SUSPECT I can just force quit the project and HOPE I did a save that captures most of my work. I know I did quite a few saves. Who does save anymore?!!!!??

 

Messages, and what I tried

ScreenFlow has encountered a runtime error that can affect its ability to continue operating.  Please save your work and relaunch the application.  If the issue persists, please contact technical support and quote the message:

 

undo: SCUndoManager 0x6000021309b0 is in invalid state, undo was called with too many nested undo groups

 

The document “Better Feedback. Better Teams. Improving Learning Outcomes from Group Assignments in Tertiary Education through Peer Feedback 378930869.v2.screenflow” could not be saved. 

 

ScreenFlow encountered an internal validation error preventing it from saving the document.  Please try undoing your recent actions and then contact technical support with this message.

 

"actions is not valid."

 

redo: SCUndoManager 0x6000021309b0 is in invalid state, do not invoke this method while undoing

 

Attempted Save as. Failed at end of process.

 

Attempted Create New - OK

 

Attempted Select ALL - FAIL

 

Oh! Darn!

 

ScreenFlow has encountered a runtime error that can affect its ability to continue operating.  Please save your work and relaunch the application.  If the issue persists, please contact technical support and quote the message:

 

Cannot update for observer <NSArrayDetailBinder 0x60000267a460> for the key path "selectionsByTime.VideoAction" from <SCSelectionManager 0x60000303c510>, most likely because the value for the key "selectionsByTime" has changed without an appropriate KVO notification being sent. Check the KVO-compliance of the SCSelectionManager class.

 

Yeah, right!

7replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 3 yrs ago
    • Reported - view

    How much RAM does your system have and how much free hard drive space do you have on your system drive and any external drives you might be using?
    Also are you using any other media besides the Apple ProRes file?

    Like
    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 3 yrs ago
    • Reported - view
    Peter Mellalieu said:
    Lots of edits done to date over about the previous 24 hours.

     Did you save the document at any point? Was it left open for 24 hours?

    Like
  • CraigS 

    Question Set 1:

    RAM - 16 GB Type DDr4 2400 MHz.

    IMAC 18,3 Intel Core I5.

    System Disk SSD Free 62.17 GB of 499.96 GB

    The project is saved on a USB External Drive, partitioned in three.

    The partition upon which my project is saved has 811.45 GB used, 182.19 Available and Total 993 GB

    Other media -  32 still shots mostly png screengrabs, and a couple of JPGS

    Lots of annotations and all the clever wonderful Screenflow stuff. See Figure 1. The Scrubber shows approx where my crash appeared, soon after I grouped the two last items, then attempted a Video Action on the group.

    Hmm. Since the project size is close in size to my Free SSD space, perhaps I have a problem making a new copy? Though the copy is on my USB External Drive

     

    Question Set 2.

    The good news. YES I had regularly saved the document.... See below

    Mysteriously, after waiting 24 hours, I was able to Create New, COPY ALL, then PASTE to the new document. However, not all media (a) could be copied (the very first item from my Global Library). So I excluded that in my copy.

     

    Second, I could not save the resulting new file

    Third, there was errant behaviour at the start of the file. The re-imported intro video would not scale or play correctly.

     

    Somewhere along the line I got this message

    ScreenFlow has encountered a runtime error that can affect its ability to continue operating.  Please save your work and relaunch the application.  If the issue persists, please contact technical support and quote the message:

     

    Cannot update for observer <NSArrayDetailBinder 0x60000267a460> for the key path "selectionsByTime.VideoAction" from <SCSelectionManager 0x60000303c510>, most likely because the value for the key "selectionsByTime" has changed without an appropriate KVO notification being sent. Check the KVO-compliance of the SCSelectionManager class.

     

    I tried a second save. It appeared to hang.

     

    So, I bit the bullet.

     

    Forced Quit.

     

    Restarted Screenflow.

     

    Got the option of Restore, or go back to last saved version.

    I TRUSTED I had saved recently, and YES!!! Got a Saved Version pretty close to where my work had achieved.

    Seems to be behaving OK.

     

    So now:

    Anything else you'd like to know?

    Anything else you suggest?

    Otherwise, I'll just keep editing, saving and hope.

    Maybe I'll make a backup copy of where I am right now.

    In the meantime, I'll pause and wait for your advice. Minor urgency. Plenty of alternative work to do.

    Like
  • Now I have recovered my work, I tried to reproduce what I THINK I did to cause the fault in a separate little Screenflow project. No success. A mystery. I copied the bits of material around where the fault materialised, then did what I recall I did to create the original fault.

     

    I created two items above the video line, at the same timecode. An image and a draw annotation.

    I grouped the two actions.

    I applied a video action... I wanted them both to scale at the same rate.

    Then I may have tried to adjust the length of the two actions. Who knows. I would have been trying to get the zoom up video action, plus positioning to work. I had done this workflow very succesfully over the 24 of edits to date, BUT ONLY ON ONE action.

    So, It's not an identical case, as I don't have my original 1 hour of Apple Pro Res video in the timeline, as it takes a long while to copy.

    So, I must have just pressed an unusual combination of keys, perhaps.

    Like
    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 3 yrs ago
    • Reported - view
    Peter Mellalieu said:
    System Disk SSD Free 62.17 GB of 499.96 GB

     This is a bit on the low side. Ideally, you want 20% free space or more at all times. I can't say for certain that's a cause but it is cautionary and may well impact the issue.

    Peter Mellalieu said:
    The project is saved on a USB External Drive, partitioned in three.

     USB2 can be an issue. USB3 (especially 3.1 gen 2) is a bit more reliable. USB2 seems to have issues with sustained throughput. Sustained throughput is critical for video. Momentary issues can create problems.

    Peter Mellalieu said:
    Mysteriously, after waiting 24 hours, I was able to Create New, COPY ALL, then PASTE to the new document.

     Background OS tasks may have cleared up the issue. This is especially important when temp space may be in use.

    Peter Mellalieu said:
    Got the option of Restore, or go back to last saved version.

     It's possible something did become corrupted at some point. There are some vulnerable points in your configuration.

    Free space on system drive should always be over 20%
    Thunderbolt drive is better than USB3 which is better than USB2 (which should be avoided). Spinning disks should always be 7200rpm or faster (avoid 5400 or vari-speed drives). SSD is best. 

    Being able to repeat the issue can narrow down the determining factor.

    Like 1
  • CraigS .

    Hi Craig,

    I've not had a repeat of the problem first raised in this thread.

    About USB 3 and USB 2. I got curious

    I've tided up my main SSD, confirming that in ScreenFlow preferences my scratch disk is on my SSD Startup disk. So now I know I need to ensure ALWAYS plenty of space when doing Screenflow work.

    I examined my Apple Hardware configuration. The report shows my hub is connected as USB 2.0. But the disk drive upon which my ScreenFlow projects are saved is USB 3, a Seagate 4 TB Expansion Desk Drive. Furthermore, the Orico 7-port hub is specified as USB 3.0.... as you recommend in preference to USB.

    So my curiosity question is "Why is Apple seeing my Orico hub as USB 2.0?"

    First, I confirmed that the hub I bought is a USB 3.0 device "Orico 7 Port Commercial Heavy Duty Super Speed USB3.0 Premium Aluminium Hub With 12V/2.5A Power Adap"

    Second. Cabling. Looks dodgy. Probably not USB 3.0 functionality, just 'compliant'.

    I found a male-female cable connector between my iMac and the Orico hub. It appears to be USB 2.0 cable inscribed with "01-1384B-E301195 AWM 2725". I found that AWM 2725 is "High speed 2.0 cable (compliant with USB1.1, USB2.0, USB3.0)" which is unhelpfully evasive. And on another supplier Cable Spec: USB 2.0 22~28 AWG Transfer Speed: 480Mbps "Supports 5Gbps data rate".

     

    But, more importantly, I found THIS article from Apple

    This article might explain why I am not getting USB 3.0 performance from my configuration.

    Using USB devices with your Mac. (n.d.). Retrieved 23 July 2019, from Apple Support website: https://support.apple.com/en-us/HT201163

    Are USB 3 hubs supported?
    Hubs that conform to what is commonly referred to as the "2008 version 1 USB 3.0 specification" are supported.

    How do I get the best performance from the USB 3 ports?
    The first device you plug in will configure the port, so always connect USB 3-capable hubs or devices first.

    What happens if I plug in a USB 2 device into the USB 3 port first?
    If you plug in a USB 2 hub first, all devices connected or "daisy-chained" to that hub will operate up to the maximum transfer rate of USB 2 speed (480 Mbps).

    What happens if I plug my USB 3 device into a USB 2 port?
    Your device should be backwards-compatible with USB 2 ports. However, you won't get USB 3 speed and power may be limited to 500mA.

    So, lots of things to get wrong in terms of configuring the USB 3.0 port. This seems particularly poignant "What happens if I plug in a USB 2 device into the USB 3 port first? Apple says "If you plug in a USB 2 hub first, all devices connected or "daisy-chained" to that hub will operate up to the maximum transfer rate of USB 2 speed (480 Mbps)." Gloom! That's pretty dozy.

    Experiments

    Interesting, having unplugged the USB cable from the iMac to the Orico hub, the System Report still shows it as connected as USB 2. I quit the System Report, reopened, and there it was, gone.

    I reconnected the USB hub, restarted the hub with only the USB 3.0 Seagate Expansion drive connected. Gloom: Still configured as USB 2.0

    Success: I reconnected the USB hub, REMOVING the dubious male-female USB cable, Restarted the hub with only the USB 3.0 Seagate Expansion drive connected. Hub configured as USB 3.0, and the Seagate configured as USB 3.0 with speeds up to 5 GB/second. Wonderful!

    Conclusion and Action

    • Replace my cabling from the iMac to the Orico hub with a single cable of known USB 3.0 performance and conformance.
    • Ensure my Screenflow Seagate USB 3.0 disk is turned on FIRST before all other disks on the hub. (I unplugged all other devices from both the iMac and Orcon Hub)
    • Consider connecting the Screenflow USB 3.0 disk directly to the iMac
    • Check the USB Hub configuration is operating at USB 3.0 before I use Screenflow. What a drag!

    The images show my initial system configuration operating as USB 2.0 through to the successful reconfiguration of my hub as USB 3.0 as per my Conclusions above informed by Apple advice.

    Thanks for the hint in this direction, Craig! I hope this helps someone else.

    Goodness. And all for want of a cable!

    Now to go shopping for a long USB 3.0 cable.

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

    Peter Mellalieu Thanks for providing all those details including your troubleshooting technique and resolution to the issue.

    USB is subject to a lot of variables which certainly do require "investigation." Another variable is bus power to the hub and/or USB devices that rely on bus power. Cable quality, length and power load on the bus can also be factors in performance.

    Like
Like Follow
  • Status Answered
  • 3 yrs agoLast active
  • 7Replies
  • 23Views
  • 2 Following