Tangier Clarke
Forum Replies Created
-
Yeah, we are really scratching our heads at the office about the speed of FCP X copying ability.
Tangier
-
Yep! It doesn’t solve my problem, but I’ve been using NeoFinder for years in conjunction with FileMaker – since it was called CDFinder.
T
Tangier
-
Took me a minute to figure out why you meant, but I got it. I had to hit the ALT key as you suggest and choose “none” then choose NAME-CONTAINS “_PST”.
That’s a cool trick. There’s so many little hidden tricks like that on the Mac – like holding option for the audio menu bar or option to show inspector (after right clicking) rather than get info.
Very cool. Thanks for the solution.
Tangier
-
Hey Nikolas. I new I was playing with fire tampering with the contents of the package, but it was on test media used to see how FCP X works; a little more in depth I suppose.
That being said what is more important is I did the above based on my experience(s) with FCP X legacy and it’s horrid slow speed in moving files around; moving files at the Finder level as a force of habit. That being said I should have tested managing media in FCP 10.1 first because….
I cannot believe how blazingly fast moving events from one library to another is I just realized literally within the last hour. In fact it’s so fast that it doesn’t make any kind of sense as I am watching what’s happening in the packages in the Finder.
I moved 186 GB in what seemed like barely a minute. Something is not adding up here and this is on a single drive not a RAID. It’s like FCP 10.1 is masking file moves. There’s no progress bar only a rendering wave forms background task.
My coworkers can’t make sense of how it’s doing this because the only option FCP presents when I drag an event from one library to the other is to copy the media. The ability to “move” in the File menu is greyed out for me for some reason, but not on other machines in the office.
I double checked and yes, there are two instances of the files – one in the old library and the new library. They are not aliases.
Case in point: moving files in FCP 10.1 seems very viable now albeit unexplainably fast.
Mac Pro early 2009/2 x 2.26 GHz Quad-Core Intel Xeon/16 GB RAM/ATI Radeon HD 5770/
FCP 10.1Tangier
-
I see a lot of reviews about Pegasus, G-Tech, OWC and a handful of other RAIDs for thunderbolt, but never one that I’ve liked very much – Rocstor’s Arcticroc.
Right now we have an Arcticroc 4T for our server but I was thinking of getting one of the Hybrid 7T models to go along with a new Mac Pro. I’ve been very happy with their product build, reliability, quiet fan (compared to some others) and customer service, but haven’t used it in an NLE environment.
Have any of you used these this way or any of their similar products and or considered them?
Tangier
-
Didn’t take it as a diss, though your comments are a good reminder about checking our attitudes towards change. Frankly that’s why I love the technology component of editorial. It’s constantly changing; keeps us learning and something is always new (though these days not new for long).
Tangier
-
Understand your point Bill. For the record I’ve loved and been a big proponent FCP X since day one even with the quarks and things I missed from FCP 7 because I saw in real use how it helped me.
The pluses far outweigh the minuses in my opinion.
Tangier
-
01 – You have finder access to your media. Your media doesn’t need to be in the FCP bundle.
Thank you for that correction. I was addressing using the bundle structure.02 – I’ve done it several times and there’s nothing wrong with it at all. It’s just like messing around in the old event folders. Only difference now it that multiple events can be grouped in the same bundle.
Good to hear. I did too. I just was more careful of my use of the Finder event and project folders while FCP was open – would cause an occasional project corruption problem.03 – I don’t see these as similar or part of a larger strategy. FCP bundles keep things all together making them easier to move from system to system if needed. The library hide was a little more like child-proofing. I don’t understand AVCHD comment.
Just noticing a trend – Apple making things “easier” by further abstracting what’s inside. It adds more complexity in some ways in my opinion. But who am I? I am sure they spend more money on R&D than I do. Quicktime X introduced “bundling” the contents of the “private” folder for AVCHD cards. Now you have to “show package contents” to get to the .mts files which on rare occasions is necessary when FCP can’t ready a card, but Toast 10 or 11 can read the mts files just fine (and transcode them)04 – Not here yet. Rest assured, there will be rejoicing in the streets if this ever gets put back. However, I wonder if they will.
05 – In past versions, the sparse disk served that function. Personally I’m a fan of a more cohesive organizational structure of FCP projects.
Not of a fan of sparse disk model. Tried it. To each their own.06 – I don’t understand this. Can you elaborate?
We backup our cards to hard drives and then clone that/those drives.
If we want to restore an old project where the media is offline, FCP X has never been able to reimport the media from the backed up folder. You only have two choices: a) turn your backed up folders into camera archives so that FCP X will recognize them b) import your backed up card(s) into the old or a new event simply for the purpose of creating Quicktimes that you can then point your old project to to rebuild the offline files.For storage/cost sake after a project is complete we do not backup all of the original media and transcoded media that we shot because we have the reels from which to recreate that media.
It’s very cumbersome really. For a project that has many reels this is horrid; being forced to create camera archives (and not in a batch fashion) takes a lot of time. Once media for a project is offline, you cannot rebuild that project using the reimport feature without the camera archive data type or a connected camera.
It’d be nice for Apple to release that and bring back the FCP 7 method where you can have a completely offline project and use log and transfer to just point FCP 7 to the reel folders. FCP X does not let you reimport from the original card structure (represented as a folder in the Finder) from which we made our initial import to begin with.
This is very strange and has never been addressed.
07 – dupe color doesn’t exist in the timeline, but we now have used clip markers in the event browser. This would seem to serve a similar function (if you’re worried about using the same shots).
Viewing marked ranges isn’t quite the same. Although helpful it’s not what I am looking for.
08 – Yeah, I think that one’s gone for good. I don’t see any reason why it wouldn’t exist in 10.1 if they were going to keep it.09 – If you want to apply affects to an angle in a multicam, why not just apply it in the angle editor?
Yep. Tha’t’s what I’ve been doing. I guess I was focusing on making sure only the portion I need being rendered rather than making the entire clip needing to be rendered. I know that’s a moot point though since once you exit the angle editor it’s FCP does not continue rendering the entire angle.10 – Based on your set up, I’d say your RAM is a little low. I have nearly the same set up, but with 32 GB RAM instead of 16. There could be all sorts of problems causing your slow downs. It’s hard to say.
I thought about just upping my RAM too. The iMacs (i5 processors with 1 GB VRAM and less RAM than my machine) in the office are butter smooth with FCP X 10.1 and prior. I have the same VRAM hence GPU memory. I am so used to having to move a clip or select something and having to wait for a few seconds. This has been since before 10.1 and I’ve done a full OS refresh. It just doesn’t move as fast as I do. I spend a lot of time waiting for it to keep up.Thanks for taking the time to reply Andy.
Forgot one more thing
11 – Batch export projects.
Strange too – since the FCP X 10.1. update FCP 7 and the Apple Qmaster system preference no longer work.
Andy
Tangier
-
This is an issue that has bothered me as well and here’s why below (I posted this on a Larry Jordan Blog and I am sure a COW page at some point)
I realize media management is the biggest change and I am not personally a fan of bundled data as FCP is now, but I’ll live. I still like the new workflow, but I like having clear and direct access to my file/folder structures to get to my Quicktimes and other media. That said, Larry do you have any speculation as to why up to this point Apple has not addressed (to my knowledge) these points below which (at least the first two) should have been rolled into this release?
Some things I really want and hoped to see in this release:
1 – Media management that can truncate clips to just what we need for archiving (a la FCP 7).
2 – Reimport from folders as reels (as in the case of a card backup) rather than being forced to create camera archives first.
3 – Color marker for duplicate clips in the storyline (a la FCP 7)
4 – Search dialogue for words or phrases by typing it in (wishful thinking)
Thanks Larry.Larry Jordan says:
January 9, 2014 at 10:45 am
Tangier:
#3 exists in the new version – its in the View menu.
#1 would require transcoding the clips to create just the truncated clips for all but a very few codecs. Apple decided they didn’t want to touch the source media.
#2 I’m not sure this is a true statement, I’ll need to do some research.
#4 is because, currently, speech to text conversion is highly inaccurate, as Adobe discovered.
LarryTangier Clarke says:
January 9, 2014 at 11:12 am
I believe #3 is only for the browser and only tells us if that portion of the clip is used in the project. What I mean is something more like FCP 7 whereas on the sequence itself you could now (by color marker) if you’ve used a clip twice (whether on purpose or by accident) in the same sequence.Re #2
We backup our cards to hard drives and then clone that/those drives.
If we want to restore an old project where the media is offline, FCP X has never been able to reimport the media from the backed up folder. You only have two choices: a) turn your backed up folders into camera archives so that FCP X will recognize them b) import your backed up card(s) into the old or a new event simply for the purpose of creating Quicktimes that you can then point your old project to to rebuild the offline files.
For storage/cost sake after a project is complete we do not backup all of the original media and transcoded media that we shot because we have the reels from which to recreate that media.It’s very cumbersome really. For a project that has many reels this is horrid; being forced to create camera archives (and not in a batch fashion) takes a lot of time. Once media for a project is offline, you cannot rebuild that project using the reimport feature without the camera archive data type or a connected camera.
It’d be nice for Apple to release that and bring back the FCP 7 method where you can have a completely offline project and use log and transfer to just point FCP 7 to the reel folders. FCP X does not let you reimport from the original card structure (represented as a folder in the Finder) from which we made our initial import to begin with.
This is very strange and has never been addressed.
Tangier
-
This isn’t what I am asking, but thanks anyway. I read many of the changes and features. What I don’t know yet though is in the process of archiving (duplicate project with used clips) is FCP 10.1 able truncate media now. As for the process of reimporting, can FCP now reimport from a folder as a reel rather than being forced to create a camera archive first; this being very time consuming on large shoots.
Consider this – after a project is complete we only backup the final Quicktimes and media we didn’t shoot because we’ve already backed up the raw camera cards to folders as unique reels on backup and cloned drives. So to rebuild a project currently we have to reimport the media from our camera reel folders.
Problem is, with the 10.0.x model, duplicating a project with clips still keeps the entire clip even if only a portion was used in the edit. This is horrible for backing up large projects with media we don’t need; hence why we only archive content we didn’t shoot or don’t have the camera original backed up.
Tangier