not sure where this would go best, but its off topic, its general, and it seems like a piece for discussion, so where better to put it than general off-topic chat? So, you may or may not know im the proud owner of multiple quadcopters and camera drones. Naturally i have lots of video editors and all kind of software that helps run, fix, or edit things related to my quads. One particular software i have packs up raw h.264 files that haven't been packaged into a .mov or .mp4 because of some error that suddenly cut power to the camera. I haven't used this software in a while since my new camera drones allow video files to be fixed automatically within the aircraft. thats way more convenient anyway, i was sharing the app with someone who had the same quad as me but had their camera ripped off in a crash, so having the file repair itself wasn't an option. anyway i shared it, and explained it and someone corrected me on how it works. so i tested it on a file that i remember being corrupt and it produced an odd video. i don't know how i didn't notice this, but the corrupt file wasn't unpackaged, it was really corrupt. It wasn't just an extensionless file, it had a .mov extension, but wouldn't play in any media player. Also, it had '-Copy' at the end of the file, which i overlooked as being a mistake i made during sorting. So before i show the videos, my theory is that i started copying the video to the same folder (hence the '-copy' at the end), but the copy was interrupted not by canceling as that would delete the file automatically, but by a power cut. So it left a half copied file. this is also evidenced by the fact that A FILE WITH THE SAME NAME WAS PRESENT IN THE FOLDER THE WHOLE TIME. AND I DIDN'T NOTICE IT. Anyway, i fed it through the application, selected the correct settings for packaging and had the video 'fixed'. it produced (as it should) a raw h.264 file with an extension, that way it could be used. So it was "video1.h264". and when i played it back in vlc (vlc is the only media player i have that supports raw h.264 files) it resulted in a video that consisted of gray and white blobs and other artifacts. This is when i realized the file already had an extension "pre-fix". Its still weird im able to play it though. Here is the .h264 file (edit: turns out raw .h264 files are supported by the google drive media player, so you can watch it through your browser): https://drive.google.com/file/d/0B3RsVb_BcoK3ekJ6SUpfX21QLWM/view?usp=sharing So i got that video, and by now i knew it was corruption, not a failed packaging, and i noticed that it had an extension already. but, i decided i'd convert the .h264 file to a .mp4 anyway. So i did. the resulting video was mostly black, with some corrupted looking randomly colored squares towards the top, and a strip on the very top of the screen with ACTUAL FOOTAGE. like, real footage from the original video. This looks like something that would be produced by power getting cut during a file copy, if it were playable, and this is exactly that. the video im about to link is corruption in a watchable video. Link (also, somehow the converter knew to change the name bock to 'Video1 - copy' instead of 'Video1_repaired.mp4' which i found really strange): https://drive.google.com/file/d/0B3RsVb_BcoK3YkRSRmFFZlFzb3c/view?usp=sharing Cool right? i have the original working video, but i can't post it here. enjoy. Tl;Dr: Video got corrupted, but not how i thought it did, so i put it through a process not meant for corrputed footage, but rather unpakaged ones, and was met with an odd video: https://drive.google.com/file/d/0B3RsVb_BcoK3ekJ6SUpfX21QLWM/view?usp=sharing Further converting that to a .mp4 produced this: https://drive.google.com/file/d/0B3RsVb_BcoK3YkRSRmFFZlFzb3c/view?usp=sharing that video actually contains pieces of recognizable footage from the real video, but its corrupted. its cool.