Any recommendations for digitizing DV tapes?

Comments

• shundi82@sh.itjust.works ⁨3⁩ ⁨months⁩ ago

  Professional here, who’s been doing it for 20 years as part of his job.

  Use your cams DV in/out port (should be where you’d also find the svideo port according to your cam’s manual).

  Install a FireWire card into your PC (or an addon card, if you’re using a laptop).

  Connect both via a FireWire cable (usually 6 to 4).

  If your tapes are HD, stick to Sony’s software.

  If your tapes are SD, use ScenAlyzer Live (free and will even work on Windows 11): www.scenalyzer.com

  If you want to transfer your tape as one single AVI file, set the Audio sample rate to 44.1 kHz within ScenAlyzer - that way the audio will match across every frame, no matter how it was recorded. Trust me, it’s the only way to not have audio run out of sync once you convert into anything but DV.

  Alternatively you can automatically transfer scene by scene and convert each scene’s audio sample rate individually before editing/combining them. Just be aware, that in a scene to scene transfer you might end up with >200 scenes per tape. Which would make the next steps harder (or you’d need some batch preprocessing).

  Short tldr for the following part, where I just go through my ideal setup without much of a “how to” explanation:

  If you’re OK with not being up to date and “just” using QTGMC (without the +), here’s a tutorial on how to set it all up (only watched the first few minutes, but he sounds competent and the comments are very positive, too):

  youtube.com/watch?v=C4PyyQoz6eo

  End of the tldr.

  Next is deinterlacing. And nothing compares to QTGMC+, if you have the patience to set it up:

  github.com/Dogway/Avisynth-Scripts

  Make sure to also download all the filters it depends on and, of course, setup AVISynth+:

  github.com/AviSynth/AviSynthPlus/releases

  That, in turn, will also allow you to deal with crappy DCT artifacts, if you have them (vertical lines, colors - especially red - “bleeding” and being blocky) by rotating the image by 90°, cleverly blending lines and rotating back 270°.

  And really, AVISynth+ is great for every other step, you might want to add:

  Denoising via SMDegrain + pre filter, getting more details out of highlights via gamma/levels manipulation, deshake, deflicker, sharpen, dehalo, deringing, crop, trim and of course resizing (there’s even more stuff like tossing bad frames and interpolating new clean ones, but you get the idea).

  Regarding resizing within AVISynth+: I’m not a fan of artificial upres in videos unless I’m desperate (R-ESRGAN etc), so I mostly stick to Spline64Resize. It’s good, it’s fast, it’s reliable, it doesn’t introduce ringing.

  Once you’ve set everything up and created your script, you just need to pipe the script into the converter of your choice. Most will prefer ffmpeg (I use python to pipe as a watchdog, but that might be too elaborate for your case):

  www.ffmpeg.org/download.html

  source

  • shundi82@sh.itjust.works ⁨3⁩ ⁨months⁩ ago

    PS: Since AVIs don’t store the field order, QTGMC+ will fail at detecting the right field order.

    AVISynth+ will assume BFF, which is correct for pretty much any DV (there are very few exceptions). But QTGMC+ will try to be clever and assume the field order on its own. And might determine your field order to be TFF (since that is its default).

    If you need it, I’ll provide you with a script to change the field order to always be TFF.

    source
  • shundi82@sh.itjust.works ⁨3⁩ ⁨months⁩ ago

    OK, followup to my last “PS”. Even though no one asked, but I’ve got some upvotes:

    Here’s a short function I didn’t test extensively (can’t post the one I use, because that one’s specific to our work and is intertwined with more of our functions like checking a file’s extension and properties to automatically determine its field order and if it needs to be deinterlaced):

    It worked in a few short tests, so it should be OK, but if anyone notices a problem, feel free to add to that:

    function tff_for_all(clip c, string "fieldorder") {
      #Usage if source is TFF: tff_for_all("tff") | else if BFF:  tff_for_all() or tff_for_all("bff")
      fieldorder = default(fieldorder, "bff")
      c
      fieldorder == "bff" ? propSet("_FieldBased", 1).AssumeBFF().DoubleWeave().SelectOdd() : last
      propSet("_FieldBased", 2).AssumeTFF()
    }
    

    source
• jared@mander.xyz ⁨3⁩ ⁨months⁩ ago

  By chance does the camera have FireWire or usb? That way you may be able to rip cleaner files.

  source

  • Cort@lemmy.world ⁨3⁩ ⁨months⁩ ago

    Manual says it has mini USB, but may require software…

    source

    • jared@mander.xyz ⁨3⁩ ⁨months⁩ ago

      I’d look into that a bit, it’s Sony so the software may be out there somewhere. But you may run in to driver or windows version problems.

      source

      • -> View More Comments
• Emperor@feddit.uk ⁨3⁩ ⁨months⁩ ago

  One of my friends recently got his wedding video off a digital camera by daisy-chaining cables until he arrived at one that would plug in his computer. I think it took 4 cables.

  source