Years ago, I recovered some pics from my honeymoon this way after we accidentally deleted them because I knew FAT worked this way so I just went looking for them.

I've never felt so happy to be a techie.

> For those old enough to remember, MSDOS came with undelete.exe which worked the same way.

Available in MS-DOS >= 5.0. If you had MS-DOS 3.3, you didn't get any cool stuff like that. Couldn't even see hidden files!

For convenience, I like to still have the files somehow marked 'already imported', so I've since modified my script to move the files on the card into an 'imported' folder. Then after the card gets full, I'll format it if I'm finished with the main project I'm working on.

I really wish modern cameras could stream over WiFi 6 or 7 (since it's just H.265 compressed, 50-100 Mbps) so I could either do NDI or a video stream off to my NAS. Still save to the card in the body, but also record over the network directly in-body!

He shares the title of "SBC Guy" with ExplainingComputers. Any time a new single-board computer comes out, especially a Raspberry Pi, they make videos with benchmarks etc. etc.

He's definitely got brand recognition. He's THE guy for Raspberry Pi and SBC stuff. I'd suspect more people would recognise him then Ebon Upton nowadays. Not ignoring the other stuff he's done, but anyone into Pi/SBC will know him.

Honourable mentions to ExplainingComputers and "Platima Tinkers".

Search his blog for his views on abortion, contraception, women, and gay people. You don't even need to look at archived versions. He keeps that shit up.

He's a freaky little neo-nazi religious nut who views women as owned by the man of the house and hates gays.

But he plays "normal guy" or "quirky nerd" on youtube.

The proprietary program has this blog post: https://www.cleverfiles.com/help/advanced-camera-recovery-in...

I think the key point is that cameras don't write the video files in one long contiguous block on disk. They internally split it up and write in an interleaved fashion. It even mentions low-level tricks like manipulating the FAT table so the moov atom which is written last appears at the beginning of the file.

I've found when you have a file with stops and starts, it's because the extraction process is not familiar with how the data is laid down on the storage media. So it sees 'I have a file'...and if it's better it sees 'the name of the file is here' and then 'it's this big' and then 'here's the linked list of clusters for that file'....or it starts at the first cluster and gets as far as it can before it runs off the tracks.

Considering the amount of personal data on people’s phones, plus how commonly people lose them in public, I would say that encryption by default is unambiguously a good thing, and it’s incredible that it took Google until Android 10.

Apple was killing it with iPhoto/Photos for this use case until a few years ago. Put in a memory card and Photos would import new photos, offer to delete after import, and ignore photos still on the card. Photo Stream made it possible to have a minimal set of photos in the cloud to have on other devices, which could be configured to sync various albums.

Then they moved to iCloud or manual sync and your forced to manage individual files again. Delete in iCloud, it’s gone everywhere. Want to keep your bad shots, but not have them on every device? Figure out how to move photos between multiple libraries while only being allowed to have one open at a time.

> because photos don't require highest speed cards

That hypothesis is certainly getting tested these days in specific niches. With high megapixel sensors, pre-capture, and cameras capable of pushing between 30fps and 120fps worth of compressed raws or high quality JPEGs, you can obliterate your camera's write buffer and CFExpress write bandwidth. You can make many bad photos of an animal, bird, or athlete with extreme ease -- and hopefully find that one winner in the haystack.

I would say the line between movies and photos is getting blurred, but it's unlikely you're using a shutter speed that allows for motion blur with these bursts of photos!

>and if you are shooting still (and not video) there's really no good reason to ever delete an image off an SD card

There are tons of good reasons.

When downloading images off the card, software has to read all the files on it - which can take a very long time if the card is full of photos you've already processed in a previous session.

Then there's that you shouldn't be keeping most of the shots you take. Unless you're a still life artiste, most people (including professionals) take multiple pictures to account for blinking, moving objects, slightly different angles, etc. You should keep the best shots and delete the rest - storage is cheap but having to go back through all the garbage to find the good shots in the future is pointless.

Modern cameras have large sensors that produce large files. It's wasteful to keep buying more and more SSD cards. Just build a NAS or pay for cloud storage.

> My advice is to have "some fair number" of SD cards and when you are done with the card in the camera, put it aside and install another card that hasn't been used in aw

Yeah, a kind of rotating workflow seems necessary when you doing professional camera stuff.

Of course, something like this can always happen; however, it's just as likely that an SD card will fail at some point.

The camera should record redundantly, and many semi-pro cameras already do this if you want them to. Then you can leave the second card untouched and have a spare one and rotate only the spares.

Yeah, after working through this blog post, I ordered 6 more cards, so I can have a queue and not delete footage until project completion!

> photos don't require highest speed cards

I photograph birds in flight at 25 or 50 FPS.

Even if I didn't do something that demands fast cards and fills them up quickly, I don't see much reason to keep photos on SD cards rather than my laptop's SSD with an external HDD as backup. I import and cull the photos, run a backup, and reformat the cards.

My advice is to run a script that automatically copies the files to the right place rather than hope you have the right window open at the time.

Except unpowered SD cards (and SSDs for that matter) don't claim to hold data for more than a couple of years.

I'm a big believer in thinking you have backups being worse than knowing you don't, so anything that encourages people to believe $(flash memory) is suitable as long-term cold storage is actually, really bad.

I agree there's no need to copy & wipe cards immediately, but treating them as "film" is inherently flawed and setting yourself up for failure. The amount of people that turn up in data recovery forums unable to access old, important, "backed up" (memory card/ssd on a shelf) photos is depressingly high.

First part hell no second part hell yeah. I wouldn't want to deal with current equivalent of Android 2.3 or 4.0.4 or eMMC failures or 5 minute bootup delay from battery insertion to first shutters with high end $1.5k cameras.

What's needed is USB-C host on iPhone. Then USB MTP or MSC to extract and upload. Which, is arguably already there. I think what's really missing is iOS/Android side willingness to ingest offline files.

Ironically, Android started as a DSLR OS.

There were cameras with FTP or WebDAV support, when connected to WiFi. I guess it’s just not really popular?

You don't need Android for that (thank god).