[Swami Kevala]

Sorry that path was 33 chars long.

I tried with this:
/Volumes/Caldigit/01.MP4 (24 chars)
and still the same problem

[Swami Kevala]

I moved the file to a shorter path:
/Volumes/Caldigit/YKC20036_01.MP4
and still get the same error

If I do a normal Quicktime export of the same file (using the same Matrox card settings) it works fine.

[Swami Kevala]

Hi Kevin,

Supposing we upgrade to the server version within 6 to 12 months, does it make any difference when migrating, how we have set up our catalogs while using the standalone version. Or does all the data from all the catalogs just get merged into the database irrespective of how we have split up the data over the catalogs. i.e. Does the concept of ‘catalog’ still exist in the server version?

Kind Regards

Swami

[Swami Kevala]

Thanks – that worked.

I needed to uncheck the “Preserve aspect ratio using” box.

[Swami Kevala]

Thanks for the RAW image functionality. That’s a huge advantage for us.

Swami Kevala

[Swami Kevala]

Hi Bouke,

Thanks for the response.

Our footage basically comes from 2 sources: our collection of miniDV tapes – which we are currently converting to MOV files, which are roughly an hour long; and a collection of XDCAM BPAVs. (The clips range anywhere from between a few seconds to about 13 minutes long). It’s a Sony XDCAM EX3.

I was also thinking that the video guys could just re-encode the clips they are interested in to an editing proxy like ProRes. But converting from H.264 takes quite a long time – and many times the videos that they produce might make use of potentially any of our archived footage over the last 10 years. Being able to drop any clip into the FCP edit line without needing to wait for it to be re-encoded would be a big advantage.

Timecode utility sounds great – that’s an issue that I had just about given up on.

Actually – I had originally intended using ffmpeg on a few linux machines with decent CPUs to do all the H.264 proxy encoding – but recently I found out about the Matrox compressHD card, which looks like it might do the job much faster using Compressor on the Mac. Do you have any experience with that?

I’m not sure what you mean by ‘ingested’:

“But with your amount of footage, if it’s not ingested, look into something that ingests the footage to proxy QT in one pass.”

Do you mean for the miniDV tapes – have a process that captures the tape to mov, and at the same time produces a proxy file?

Our aim is to have everything file-based (movs for the captured DVs and mp4s for the XDCAM) – all stored on LTO tapes. Our DVs/movs have succinct unique ID codes, so that’s not an issue. For the XDCAM stuff I was thinking about assigning a unique ID to each BPAV folder and then naming each proxy {BPAV-ID}-{MP4-name}.

I’m reasonably handy with the command line …

Do your utilities work with XDCAM EX3 footage?

Kind Regards

Swami

[Swami Kevala]

Hi Alex,

Thanks for the suggestion. I just had a brief look through the CatDV site. It looks very good – and highly relevant to what we want to do. Do you know if the video-editing functionality could be accessed over the network, in the same way as the intranet/webpage library?

We already have a custom xml-based ‘events’ database, which I was planning to extend to manage our media assets. (We categorize everything by event). But I suppose I could just link to the corresponding web pages produced by the CatDV app…

One more thing… We are already capturing our DV footage using Quicktime – to produce MOV files. We are then backing these up on LTO tapes (since our miniDV tapes are getting a bit old now). Could I import these into CatDV and still get it to make the proxies?

I think I’ll download the trial version and experiment a bit.

Thanks again

Swami