Digitize MiniDV Tapes with Linux
arsouyes.org
arsouyes.org
I digitized a large number of family MiniDV tapes a few years ago, since the quality of the footage on the original tapes is better than the DVD recordings made at the time (due to both the DVD MPEG2 recording scheme and the fact that the camera was connected to the DVD recorder over composite video). But some sections of a few of the tapes had suffered serious deterioration, rendering the resulting footage unwatchable.
Using DV Analyser was a great and quick way to identify the clips with a higher than expected number of errors, so I could try to re-grab those tapes, and (if that failed) go back to the DVD recordings. Much quicker than watching every video through in real-time!
There's also the DV Rescue tool [2] (also open source), which seems to actively assist in fixing detected errors, but I haven't got any experience with that.
I have a hundred or so MiniDV tapes awaiting ingestion...first need to figure out where to store the data.
Extending that to DV tapes: the DV format is interesting in that every frame is a keyframe, and encodes an entire image. That's in contrast to H.264 and friends, where frames can be predicted, and/or just the difference between a prior and future frame can be encoded. DV also encodes a timecode into each frame. So if you had multiple DV decks and were able to get a bunch of unclean imports, it seems like it'd be trivial to write a small tool that grabs all of the clean frames from each and stitches them together over the gaps in others, according to that timecode.
(Disclaimer: I've never done that, this is a pure spitball.)
I wonder if this is what DV Rescue (linked in my above post) is doing? If it's not doing this, it's certainly something that it should be doing.
You're also 100% spot on with the idea of using different drives to recover "tricky" tapes - I have two MiniDV camcorders exactly for that purpose. But I was doing it the "long" way of trying a tape in one, and if it didn't work well, trying it in the other. It didn't occur to me that I could try combining the results of both.
> dvmerge A script that takes multiple transfers of the same tape containing errors and combines them to create one file with the best information available for each problematic frame. dvmerge is part of dvrescue. See dvrescue -h on a recent build.
> dvplay A script that plays back and visualizes the DV errors as a stack of images. Running with the -x flag will produce JPEGs instead of just playing them.
> Snapshot daily builds are at https://mediaarea.net/download/snapshots/binary/dvrescue/.
Yeah, I was about to say it’s kind of strange to refer to this as digitization, since MiniDV holds digital data on it already.
I think transferring MiniDV tapes with Linux would be a better title. But I kind of get what they mean I guess.
For MiniDV I ended up using iMovie on my Macbook Pro and it worked surprisingly well. It automatically imported and spliced the different "cuts" of a single tape into different files. It even timestamped the videos with what the camera thought the time was (spoilers, tons of the times were clearly wrong).
I found a guide online somewhere, but I'd like to present the dongle beast I used between my Macbook and my camera: https://i.imgur.com/wZ9rJnH.png
Thunderbolt 3 -> Thunderbolt 2 -> Firewire
I just handed off my MiniDV hardware setup to a friend to try out on Windows for some of his tapes. What a blast!
For some reason it worked a lot better for me than the commercial video capture software I tried.
Technology Connections on youtube provides a much more complicated and expensive setup, but it might be a hair higher quality.
These systems will ingest anything that spits out composite video; Videogame consoles, VHS, DVD, old computers, TV set top boxes etc
The data on the MiniDV tape is already digital. Any FireWire interface (cheap dongles also available) will allow most operating systems an easy way to read the tape, and as well as retaining the original video quality, metadata like dates and times and each scene (each startrecord-stoprecord bit) are also transferred.
I transferred family MiniDV tapes in this way. It took about three sessions, spread over 3-4 years, to complete the task, and I used Linux, Windows and MacOS to transfer the data, depending on what computers were available. The output is the same regardless.
Anything that claims to adapt plain USB to firewire is bait for unsuspecting buyers, or maybe supported by some ancient obscure sony camcorder models.
The cheapest options for firewire these days are pci, cardbus, pcie, and expresscard in about that order. G3/G4 era macs up to 2012 models are common firewire machines. I know Sony and IBM had laptops with the interface in the core duo times.
I'd love to find an ultra-wide-scsi adapter to pull data from an old 4drive in 1 - setup as well.
Think I've got an old scsi card. not sure it'd match up with the newer motherboard connections though.
dvgrab will work with USB via the -V flag:
-V, -v4l2 capture DV from V4L2 USB device (linux-uvc)
USB was mostly fine for interactive capture. Firewire has been smooth for unattended transfer of whole tapes.Obtw - My Firewire port and Sony MiniDV didn't work with dvgrab until I explicitly commented out
blacklist raw1394
in
/etc/modprobe.d/blacklist-firewire.confBe warned, it does produce pretty large raw files, though, so after import, I ran ffmpeg to convert them all to mp4 files. No visible loss in quality, and about 90% size reduction.
betamaxthetape mentioned[0] DVRescue[1] which looks very useful for error correction. The tools expect the raw .dv files, so check before compressing.
[0] https://news.ycombinator.com/item?id=27971246 [1] https://github.com/mipops/dvrescue
[1] https://www.linux.com/news/using-camcorder-tapes-back-files/
[2] https://www.networkworld.com/article/2302563/using-a-camcord...
[3] https://www.linuxquestions.org/questions/linux-software-2/us...
I know that SCSI drives were made for DDS [2], which (at least, initially) used the same tapes as the DAT audio format. But those used 4mm tapes, so probably aren't what you have.
Alternatively, it could have been a custom built system that recorded data onto video 8mm tapes. That will probably be a bit harder to get the data off unless you know the details of the setup used.
[1] https://web.archive.org/web/20070226174943/http://www.exabyt...