I record this osprey nest webcam 24/7 with 1-hour auto-completes, never had this problem until just now.

The picture being recorded on the screen was normal, I was watching, but my usual freebie video editor couldn't open the latest, manually stopped, clip, so I put it thru a video converter which often rescues 'difficult' files... but this is what I got:




.
This may well not be Bandicam related, but I wonder if anyone with experience can diagnose what underlying problem might have caused this. The next section was fine.

Try using the file recovery. If that doesn't work, watch this video. It may help. https://www.youtube.com/watch?v=0jaUTAALNa0

I'm investigating your suggestions, Ukstavish, thank so much for troubling to respond.

Funnily enough, for years I've wished there was a repair program for when, say, a power outage or system crash leaves a video "unfinished".

I noticed that the person who did a review of Recover_mp4 said he'd post simpler instructions in the VideoHelp Guides but I haven't been able to find anything. In any case, I'll have to wait for time to devote to the installation and experimentation - can't afford to shut down at the mo.

Thanks again!

Hello clemenzina,

First, please try Bandicut to convert the recorded file to another format.

https://www.bandicam.com/bandicut-video-cutter/

Also please refer to the page below for the future recording.
https://www.bandicam.com/support/tips/video-editing/

Thank you.

Same thing happened to me! I let a colleague use it and a week later, this showed up. Never knew if it was related.

Hello,

If you'd like to edit the recorded video, please refer to the linked page.
https://www.bandicam.com/support/tips/video-editing/

Thank you.

If I may pop in - I know I'm a little late on this - and I am sorry to Reply after an 'official response' by Bandicam; but I ran into this issue when I was working with Keyframes and MPEG-4/H.264/AVC material.

It could possibly be related to the GOP (Group Of Pictures) and how the interframes are being handled (the images that are being retained between Keyframes or Information Frames).

I have never run into this with Bandicam's MPEG-4 though... Did this come from the output from your 'converter' program? It is possible to run into this with x264/h264 codecs, when setting a Long GOP (high keyframe distance amount) but I haven't run into this for a while. I hope it has been solved for you - or you are able to solve it, soon. Good luck