Fabrizio D'agnano
Forum Replies Created
-
Before asking on the CC forum I searched a lot, and it seems it is a wide problem. Some address it to the OS, some to other reason. I found suggestions pointing to different approaches to the problem, from disabling App Nap to disabling “stop drives when possible”, but no real definitive solution. Today I worked all day with my raid with firmware flashed to “no sleep”, and everything was fine. However I was curious to know from other members of the forum about units that work flawlessly. I can’t believe it’s an OS problem that Apple did not solve after several OS upgrades in such an important area, nor that nobody is using USB 3.0 drives for editing.
Fabrizio D’Agnano
Rome, Italy
early 2008 MacPro, BM Intensity Pro, early 2008 iMac, 2014 MacBook Pro Retina, Blackmagic UltraStudio Mini Monitor, FCP7, FCPX, OSX 10.9.4 -
[Fabrizio D'Agnano] “I own a couple of USB 3.0 2 bay arrays, but they keep disconnecting randomly, most of the times after being put to sleep, sometimes during common operations.”
Maybe this can be interesting for anther people having problems with disconnecting USB 3.0 drives. I flashed the firmware on my two 2 bay RAID’s to a version with “no sleep after 15 min”.
I had no problems today, I’ll check them more thoroughly next week.Fabrizio D’Agnano
Rome, Italy
early 2008 MacPro, BM Intensity Pro, early 2008 iMac, 2014 MacBook Pro Retina, Blackmagic UltraStudio Mini Monitor, FCP7, FCPX, OSX 10.9.4 -
[Robin S. Kurz] “Which? I don’t see any features that were. Maybe moved, but not REmoved.”
Maybe it depends if one is referring to the process or to the final result. If you look at it as to the possibility to directly send the media to an external folder of one’s choice without quitting the import panel, going to the Library Property, modifying the Library destination folder, reopening the import panel, and eventually sending the clips in the desired folder, I see it as a removed option. Of course one can still take a longer route and eventually end up doing the same, so you can consider it as a moved option as well.
Fabrizio D’Agnano
Rome, Italy
early 2008 MacPro, BM Intensity Pro, early 2008 iMac, 2011 MacBook Pro, FCP7, FCPX, OSX 10.8.3 -
Yes, and it’s a pity that at least one of the features was already there and was killed…..
Fabrizio D’Agnano
Rome, Italy
early 2008 MacPro, BM Intensity Pro, early 2008 iMac, 2011 MacBook Pro, FCP7, FCPX, OSX 10.8.3 -
Yes, Craig.
Thank you, I think that’s the way to go. I always build camera archives of each card while I’m somewhere gathering footage, and keep a double copy of each archive on separated drives, other than the ones I import, sort, name and comment media onto. What I don’t like much of the process of switching the media destinations in the Library Properties is ending up with folders with the same name containing clips with the same names (ex. folder “original media”, subfolder “2014-07-21”, clip#1, clip#2 etc) but totally different media. That’s why I had abandoned this workflow at first, after replacing a wrong folder while building a backup copy on another portable drive. After reading your post, I checked once again. I found (and double checked a few seconds ago) I can actually rename the folders right after capture, without FCPX asking to relink the files, so that’s the most viable solution, and the naming is not really an issue, after all, just a few more clicks….Fabrizio D’Agnano
Rome, Italy
early 2008 MacPro, BM Intensity Pro, early 2008 iMac, 2011 MacBook Pro, FCP7, FCPX, OSX 10.8.3 -
[Craig Alan] “Or, and I think this fits your way of working: in the finder create the folders you want; even add tags to the folders and or files. Then when you open the import window you can leave files in place and optimize if needed.”
Thank you. While I like a lot the new options about render files, I still don’t know why the import destination folder option was removed. However, as you figured in your post, I found a way to deal with what seems to be a flaw for my very own workflow (I can see there are almost no complaints about this on the Creative Cow, so it’s not a shared problem). In the part of your post I’m quoting you’re maybe referring to imported files. If I ingest from a AVCHD card I can’t, and don’t want to, leave files in place. Or maybe there’s something I didn’t understand. However, this is where I ended: As you suggested, I create folders via the Finder in a general Media drive, or wherever outside of the library. I set one folder for import, another for “Underwater scenes”, another for “External shots”, etc. Then I import from the card. Right after the card import is over, without quitting FCPX, I go to the Finder, go to the Original Media folder FCPX has created, rename the folder containing the imported files from “2014-07-23” to something like “2014-07-23-UWCanon”, and then drag the folder onto the “Underwater scenes” I already created in my Media location. If I don’t rename the folder, when I import from the next card I won’t be able to drag it to the Media folder because there’ll be another with the same name. Now I rename the clips with date and time in the browser, and I am happy I don’t have to relink. It seems a longer route to me, and a more dangerous one than simply changing destination in the import window, and there’s no possibility to send some clips from the same card to the “Interviews” and other to the “Landscapes” folders without quitting. The reason I use this Media structure is because there’s some Media I keep in a handy location like a large external RAID for use in future projects, like most of the landscapes or UW scenes, and other that’s going to be archived with the current project, like interviews etc. The next option I want to explore is going for the “single media folder” strategy suggested by FCPX, and keep the whole library once deleted the render and optimized files in the handy Media RAID. Working with AVCHD source media, the tax on backup, archive and storage space should not be that large.
Fabrizio D’Agnano
Rome, Italy
early 2008 MacPro, BM Intensity Pro, early 2008 iMac, 2011 MacBook Pro, FCP7, FCPX, OSX 10.8.3 -
I recently bought a top of the line MBPr, to ingest and sort footage, and to build rough cuts on site to check the footage while on shooting trips, and it does the job flawlessly. I recently bought a Delkin TB adapter, and I’ve found the MBPr with two external displays, external drives, keyboard and mouse, and audio monitoring device, connected via a single TB cable, can go through more robust editing with no problem. I am ending up using it very frequently as my main machine.
Fabrizio D’Agnano
Rome, Italy
early 2008 MacPro, BM Intensity Pro, early 2008 iMac, 2011 MacBook Pro, FCP7, FCPX, OSX 10.8.3 -
Maybe there’s some misunderstanding, because it was actually possible in the previous version of FCPX to send the media to folders different from the library you could select on the fly without leaving the import window. I produce mostly underwater travel chronicles style documentaries. At the end of the day I have to gather shots coming from an underwater camera, an external camera, and a couple of GoPro’s, for both dry and wet use. Before, I used to ingest from the cards sending the media to relevant folders and to dedicate events. For example, if I needed to ingest from one of the uw cams, I used to send the media to a “2014-07-Gibraltar-UW” folder, external, in a general folder named something like “2014-07-Gibraltar-Media”. If I had to ingest from a card from a GoPro containing wet and dry footage, I could select one or more of the clips into the import window and choose to send the media to the “UW” or “Interviews” or “Landscapes” or whatever, without ever leaving the import window. The footage was sent to an external folder matching the Events structure, and once home I could copy the “UW” or “Landscapes” media folders onto another RAID set for future use in different projects, and use the “Interviews” that are not suitable for use in different projects along with the current one (no need to archive in a readily searchable RAID set). Now I can’t do that. I need to send the footage to a single folder, if I don’t want to make it managed (and I don’t want, since I often need to swap the drive between a MP and a MBPr). After ingesting, I need to move the folders FCPX created into the Library destination folder onto the desired folders. And if I have mixed footage, I have to manually select it one by one. Yesterday I had a problem because FCPX created a folder with the same name of a previously created and already moved one, so that I, for a mistake, replaced the first, that was containing different footage. While wondering why the possibility to choose a destination for the media without having to quit the import window, go to the Library inspector, etc. was removed, I am looking for the best possible way to set a workflow as free as possible of human mistakes, as was the previous one. I think I’m not the only one to have this maybe peculiar needs, and maybe somebody else already found a workaround or a different workflow.
Fabrizio D’Agnano
Rome, Italy
early 2008 MacPro, BM Intensity Pro, early 2008 iMac, 2011 MacBook Pro, FCP7, FCPX, OSX 10.8.3 -
Was it irrelevant also that you must now send your ingested media to a single external folder or to the library, and move it later to subfolders via the Finder? At the moment, I am ingesting to the storage destination that’s specified in the Library properties, and then have to move the media via the finder to more relevant subfolders matching the library Events structure for future archival management. Do you usually work with managed or external media?
Fabrizio D’Agnano
Rome, Italy
early 2008 MacPro, BM Intensity Pro, early 2008 iMac, 2011 MacBook Pro, FCP7, FCPX, OSX 10.8.3 -
Still trying to figure out an ingesting/renaming/archiving process that allows me to skip unnecessary and potentially dangerous Finder actions that I didn’t need in the previous release, I am curious to know if and how the new Media Management affected other editors workflows.
Fabrizio D’Agnano
Rome, Italy
early 2008 MacPro, BM Intensity Pro, early 2008 iMac, 2011 MacBook Pro, FCP7, FCPX, OSX 10.8.3