Eugeny Korkhin
Forum Replies Created
-
[Jeremy Garchow] “The MXFImport component works like this in QT and fcp7 now. Using the QT framework, the component simply presented the information to the OS. It’s very slick. “
[Walter Soyka] “That’s a bit different than MXFImport, which was a QuickTime component and could actually work within the QuickTime framework. Since AV Foundation doesn’t support QuickTime components, I think they are going deeper, Inception-style, and virtualizing the media in a QuickTime wrapper, on-the-fly, on a virtual disk that must be mounted. “
May be you know that, but for those who doesn’t: if you have “MXF Import”, there’s an option to create QT Reference files in a specified folder or in the same folder the mxf file lies in. That happens almost on-the-fly: you need to “access” the file to initiate the process of creating references. That is either open it, or preview with quicklook. Or if you have a folder full of MXF files, the first time you open that folder finder builds thumbnails, thus “accessing” them. After that you have a bunch of MOV files which FCP X understands. Not so neat as VirtualMXF seems to be, but an option anyway.
Unfortunately, it doesn’t read or merge Avid mxf. XDCAM works.
This can be activated in CalibratedQMXFOptions on the auto-ref tab. -
What I miss here is the possibility to export ONE file referencing MANY. Would be nice to reference the whole timeline…
-
The future seems to have lost the skimmer.
-
I’m really glad it works for you.
-
Hi, David.
In the suggested working environment you should drop newly created files (files, not folders) into “the shared” Avid Mediafiles location: let’s say, for instance, “SAN -> Avid Mediafiles -> MXF -> 1″.
Or you can create a numbered folder inside of MXF folder, i.e. “2” and copy the files there – thus making them easy to locate in case something goes wrong.
Or you can rename your local “1” folder into “2” (in case you don’t already have a folder named “2” in shared place) and copy this folder into that same shared MXF folder.
Or you can use Consolidate feature inside Avid to gather new media to the shared storage.Hope that makes sence))
But don’t forget: It doesn’t prevent scanning, but only makes it controllable.
Feel free to ask,
Eugeny -
Christopher,
You should be more detailed in describing this kind of problems, because “everything is gone” of course sounds interesting, but not informative enough to tell “what the hell is going on”. Events disappeared? Project disappeared? All projects disappeared? Project is there, but empty? And so on… Lots of meanings of “everything is gone”. Define it, please.
-
Jeremy, you are absolutely right – They are speaking different languages, for sure. But what is even more surprising, is why would they still discuss the way they work with images in this exact thread? Who cares? You may be putting whatever you want in images, even your .doc files, but let’s get back to earth – John is still missing his events and projects and I think he wouldn’t mind some real advice, rather than read your arguing.
-
Let’s put it another way. This problem can be easily recreated. I have just tested that. Creating a new folder named DCIM in the root of the hard drive makes all the projects and events on that volume disappear for FCPX. Once you delete that folder, they are all back. So, make sure you don’t have DCIM in the root. And who knows what other names of folders or places they are located in can cause that trouble.
-
I never had this problem by myself, so I can only guess. But it seems to me that it relates to folder names, not files. And not only DCIM folder may cause trouble, but other camera-specific names as well.
That is a bug. No doubt. But Apple can call it a feature:) -
FCPX may treat your hard drive as a card from a camera if you have “camera related” folders (i.e. DCIM) on your drive. Check this thread for more info:
https://discussions.apple.com/thread/3279953?start=0&tstart=0