Claude Lyneis
Forum Replies Created
-
The next time I went though the process,it did empty. It leaves the event name but at least it is empty.
-
With respect to using the finder to copy a few at a time, since there are some many I thought about using the technique to divide the files into 2, try to copy each, if one fails, divide and copy to test and the iterate the process. On the other hand, with 800 GB, that would still take a long time.
At the moment, I am using Super Duper to copy everything on the first disk to a new one. I don’t think it is as rigid as the finder about damaged files. If that works, it will accomplish what I tried to do with the finder copy process. Doesn’t eliminate the damaged file, but I may never need it.
-
I have a new Lacie 6TB 2 Big and ran the speed test on it. It seems to write about 340 MBs and read at 360 MBs, where as my Firewire 800 is about 55 and 60 MBs. So that is an impressive difference. Haven’t used it with FCPX enough to see the impact of that.
Meanwhile, one of my old USB 2 Western Digital has slowed to about 1 MBs and must be almost dead. Never seen that kind of failure before.
-
If you use consolidate to move the media somewhere else, is that somewhere else a library or just a folder? When you then look into the library with 10.1, how do you know where the media really is? Did Apple write this up in a white paper? Learning this by experiment makes me nervous.
-
Hmmm. So we go from multiple projects to multiple libraries? This will take some thought. Somehow, I wasn’t really paying attention and didn’t realize what a major change was in store with 10.1. The Duplicate function has moved under the Edit function and does make a copy, but doesn’t give a choice as to where it goes. It just stuffs it into the existing “project”. Move seems to has disappeared as well.
I look forward to more workflows from those on the bleeding edge.
-
I am not sure about the ultimate rendering speed, but the activity monitor no longer shows the activity of each core, instead it shows the sum of the cores. If you look at the individual apps using CPU time you will see numbers like 240% for compressord and 140% for compressor or some other app. I assume that means (in my case) the 4 cores are all close to 100%. Anyway, that is my assumption. It may be that under Mavericks it chooses to render more of the original, because I thought I saw some difference, but I also have been recording at a higher bit rate 24 or 28 Mbs and it seems to render those H.264 files into something like ProRes422. There is an earlier thread, where the experts said it was rendering the H.264 into ProRes and there are certainly large render files now residing in my newest projects.
-
I am guessing it is App Nap. That one got me.
-
If you make a new project from the project library and have an external hard disk selected, that is where the project is stored. I store projects and events together on the same external hard drive.
-
So if you import clips with create optimized media checked, FCPX generates Pro Res files and puts them in the event folder? If clips are loaded into an event without create optimized media checked and then FCPX renders them once they are in the time line, they end up as High Quality media and are stored in the Project folder? So if you are selective with what goes in the timeline, then there should be less time spent encoding all those clips, since many many may remain unused. Or am I over thinking this?
-
It is starting to make sense. I made a new project with the only clip being MP4, 29.97 p, 17 Mbs and FCPX did not bother to render it or make high quality video. That must be a FCPX compliant format, whereas the higher bit rates aren’t and it renders them. The good news is FCPX manages all of the formats, even if it needs to render them. Over the weekend, I tried a 24 Mbs clip on my 4 gB macbook air and it almost choked to death trying to render it. It took 8 or 10 hours just to render 26 minutes of film and about 12 hours to compress it.