[Paul Dougherty]

Hi bryson, this is great! While you make a good point about re-wrapping cards for the archive I’d love to save that for another thread.

Even though it would be valid as a data model having a bunch of clips selected and listed in a card record (or under that “umbrella”) it might make the record a hard browse. Though if my organization one days okays a much more ambitious clip level description effort, this design would probably scale well. More likely one would want to define/describe sections of ‘like’ footage, call them clusters or as you say scenes. These would be represented by time code or maybe clip # ranges or brackets.

One of the main things I’m wrestling with is a subjective nature of going more granular in the card description. In real life different catalogers might overdo it or under-do it resulting in a catalog that is inconsistent, neither fish nor fowl.

[Paul Dougherty]

Thanks John, I just watched part 1, fantastic! Funny that it went up a few days before my post. Great timing:)

Paul

[Paul Dougherty]

Thanks Todd,

It’s a 400 to 800 fw connector but I’ll keep and eye peeled for looseness

Paul

[Paul Dougherty]

Thanks Jon, My mini-DV’s were recorded at standard speed. For reasons not clear to me the system is behaving better today. This is anecdotal, I was on the phone with Adobe support doing 2 min. test captures, not full 60min tapes. But two days ago, I couldn’t even capture a second of video. One tape in particular is giving me a hard time, I have to parse what is acting up, the system generally or certain problem tapes.

From the start I did not have “Abort capture on dropped frames” checked – so this should be more forgiving. btw a “batch log” has nothing to do with capturing in-to-out with individual tapes right?

Thanks,

Paul

[Paul Dougherty]

“DV tech isn’t on anyones priority lists anymore lol.” True. I persevere because I’m doing preservation work and tapes are either get saved or not

[Paul Dougherty]

Thanks Brent,

I don’t think I’ll take the FCP X plunge, but good to know. I wish Premiere (or some capture software alternative) had a setting that allowed for more tolerance of a flawed source. A workflow might go like this… after giving it the good ol’ college try with the standard (rigorous) software setting, failing that I could make the capture setting more forgiving and live with a ‘hit’ or dropped frames in the result… in the interest of getting a long (in my case 40->60min) continuous piece of media (in my case an interview).

Paul

[Paul Dougherty]

Sorry no, the problem is capturing. This has not been successful either way.

[Paul Dougherty]

I’m having this same issue on Avid 2018.8

[Paul Dougherty]

Hi Chuck,

Thanks for your offer, I will definitely give you a call. I wanted to collect my thoughts first. This outline will help, and provide for others some context for my original question. To recap – I’m working for a nonprofit that has 10 years worth of born-digital video projects, some final-cut but mostly premiere. So here is an outline of the current mission and some future possibilities…

1) secure the archive of past video projects and make the assets discoverable.

2) preserve these past projects such that they open and link correctly to media.

3) give editors access to this archive that resides on the QNAP so that…

3a) they can edit directly from it, or copy footage (if that’s required).

3b) access the Qnap to submit new projects to the archive.

4) gradually open the archive to others in the organization, ie. non-editors.

5) depending on demand and institutional support, make the assets (footage) more user-friendly by converting camera directories contents to a more standard format like ProRes.

6) (And this is where it gets both complicated and uncertain) Since editor’s project folders are probably not the best vessel or structure for general access and distribution of footage… this is where a DAM might come in one day.

By way of a footnote I should add that the interim arrangement that makes the wider access mission less urgent, is that some demand for footage is partially met by posting b-roll packages on the WebDam system designed for the photo archive. This is administered by a different department and I’m told that sometime next year they will be moving from WebCam to a Libris system

Thanks,

Paul

[Paul Dougherty]

Hi Bob,

First off, sorry re. the companies (list), as I was finishing the post I forgot to paste in that very list from you… “QNAP, Synology, Netgear” certainly never intended to connect you with Drobo.

I’m green to the storage forums on Creative Cow and stand corrected. Thanks for all the good advise, I’ll redirect to NAS and SAN forums.

“self heal” was a sloppy non-technical way of saying “automatically rebuild”

Best,

Paul

p.s. I might have thought drives would be in the mix on this forum re. the post of yours I mangled the reference to… “LTO Archive vs. drive based “near line” storage”