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.
Sorry this happened. It's possible that the file is corrupt and running out of hard drive space can cause this in any number of programs because the file isn't properly closed.
Generally you want to have at least 20% free space through the completion of recording. This is especially so when using the system drive because the drive also needs throughput for the OS, the program(s) running and the creation and access to temp files, caches, buffered files.
You certainly can and should explain your situation to our developers so they can consider possible future methods of prevention and recovery.
ScreenFlow Support Form
CraigS Thanks for the reply. I will try to contact the developers.
However, I'd like to add a comment here: In my view, common technical problems, such as decreasing file space during a recording, should not be handled by the user but automatically resolved by ScreenFlow.
I fail to understand why ScreenFlow cannot snapshot the recording every 5-10 minutes, such that not the whole recording is lost in case of an error. Moreover, ScreenFlow might also easily monitor the available file space during recording and take countermeasures once a critical state is reached.
Konrad Rieck said:
I fail to understand why ScreenFlow cannot snapshot the recording every 5-10 minutes,
It's quite possible that may further compound the file size disk space issue. ScreenFlow can recover projects but not always.
Monitoring space is an interesting idea but there can be pitfalls in that as well.
We don't want a scenario where a solution actually creates more problems especially given that there are certain OS functions that must be taken into account.
Here we are in 2020, middle of the pandemic, and the same thing happened to me during a live lecture recording, 1:30 minutes of recording lost. It is frustating that has not been addressed at all. A simple pop-up message every ten minutes showing a rough prediction of how many minutes more you have before crashing would already help. I would expect it to force-close the file at a given point, rather than destroying the recording.
Gustavo Wiederhecker Fill out the form and ask for a status update on reporting running out of drive space during recording or stopping recording when remaining drive space passes a point. I do believe implementing these present challenges though since the act of estimating may itself have an impact.
This literally happened to me right now except that it wasn't a space issue. The recording just decided to die. I saved the .scc file but it tells me that there's nothing I can do. I was recording a conversation with my family making important announcements and boom, it died. Now I can't recover anyone's reactions. Luckily I wasn't using this for a paying client.
This is a rather large pain point knowing that I have the .scc file but can do nothing about it. I understand that computers can fail, but a corrupted file on a captured stream, with solutions from experts in this thread should be part of a modern screen capture app.
Unfortunately, I cannot recommend this app due to this issue.
Tery Flip said:
and boom, it died.
Sorry to hear that but...
ScreenFlow recordings have data in them that are outside standard simple recordings such as MP4 or MOV files because they are recording screen information from the OS and the GPU including mouse and keyboard input. This is why the recovery methods are different. In some cases you can open a document and it will immediately offer recovery but in some cases, that's not possible currently.
It's not clear what "died." The computer? The drive?
Catastrophic failures are rare.
If you'd like help please explain.
CraigS As a long-time Screenflow user, I have also suffered from the inability to recover the gigabytes of video that have became irretrieveable because of crashes (as recently as this week). I am a former senior product manager at Adobe, and I have been on product teams that had to decide on the priority of features, bug fixes, enhancements. This issue is wholly about data loss, and in the companies I have worked in would have been treated as top Severity and top Priority to solve. Yet, there are years of notice about the problem and requests from users to provide a solution. I respectfully request that Telestream prioritize the creation of a solution to this above any other feature request, bug fix or product enhancement. Data loss like this is catastrophic, and clearly is not a "rare" event, given the length of time over which people have been asking for help with it.
Please forward this comment to your product management and engineering teams. Thank you.