Recover contents of .scc file
Dear support & forum:
While recording a lecture of about 90 minutes, my laptop ran out of disk space. As a result, ScreenFlow failed to return to the main window and didn't save the recording.
I have rescued a 50 GB .scc file from the default scratch folder. However, so far I have not been able to recover the contents. I tried the following:
- Dragging the .scc file to the ScreenFlow app in the Dock -> An empty document is shown.
- Dragging the .scc file to the main window (media library) -> An empty document is shown.
- Replacing an existing .scc file in a ScreenFlow document with the copied one. -> A warning about a corrupt .scc file is shown.
Unfortunately, none of these attempts have succeeded.
Is there any technique to recover the file contents? I am working as a computer science professional, so I am open to any technical suggestion (except for reverse-engineering the proprietary .scc format).
I am using ScreenFlow 7.3 (31012) with the default scratch folder on OSX 10.13.4
Best regards, Konrad
ps. Note that if the recording is irrecoverably broken, I am tempted to change to another product for screen recording. Running out of space during a recording seems like an average problem that should be tackled by ScreenFlow without complete data loss.
Simon Sturmer said:
was thinking about is trying to reverse engineer the SCC format and see if we could make a tool to demux the individual streams from it.
That would be a valuable and probably very profitable recovery tool.
While we continue to improve SCC recoverability, I think you may find challenges similar to that our developers have met.
That would be a valuable and probably very profitable recovery tool. While we continue to improve SCC recoverability, I think you may find challenges similar to that our developers have met.
So, "valuable and very profitable", but for an outside indie developer. If I can crack the .scc and create a recovery tool, and sell it for a profit - I get sued for patent infringement or the like, then your company takes my code and offers it to their customers as "the fix you've been waiting for".
Is that what it's gonna take?
Or is it free reign to develop a tool and sell it to power users?
Here's my question: After having lost a VERY important training session that ran longer than I expected, when SF puked because it ran out of disk space, I was left with a 1.2GB SCC file after indicating I wanted it saved. WHY DOES THIS FILE EVEN EXIST/SAVE IF IT IS COMPLETELY WORTHLESS TO SALVAGE ANY OF THE CONTENT?
This is an astoundingly important point of application "half-bakedness"/failure that has apparently existed for years and Telestream has STILL not managed to address it??? IT IS A BUG! IT IS A FAILURE! Talk about giving the big middle finger to your captive users.