James Culbertson
Forum Replies Created
-
[Tim Wilson] “I think we’re getting warm. LOL”
Just think, in 5 years (long after AVID and Adobe are gone) when Bare Bones Software releases BBEditVideo and FCPX editors scream about what a toy it is, while all the kids think it is the new best thing, you won’t have to change the name of the forum again.
-
[Scott Witthaus] “In my mind, as I have stated, the debate about FCPX is over, if there was ever was one.”
This is true. But I realize that often in life, like this forum, names do not accurately reflect content. For my part, I have labeled this forum “Which NLE: the Debate” in my head for a year or so now as that is the most empirically accurate term I can find at this time. But if we have to throw a bone to those who want to keep FCPX in the name perhaps, “Used to be called ‘FCPX or not: the debate'” or even better, “FCPX debate: the history.” [Documentary approach]
Or since there is so much diversity of opinion on what to call this forum what about: “Anything but FCPX,” “Crazy Stupid FCPX debates,” or “FCPX: the Disagreement.” [Narrative Fiction approach]
Personally, since we probably won’t end up with an accurate forum title, I would vote we choose as entertaining a name as possible.
How about “Luddite Dinosaurs versus Editing Toy Fanboys”? …I mean, if you really want a debate forum.
-
I use ClipExporter constantly for exporting QT refs for use in SoundBite. ClipExporter 2.0 has deprecated QT ref support due to the switch to AV Foundation so I will be staying with the older version for now.
-
I sent Pegasus a service report for my two drives and they responded:
“One-bit ECC error was detected”
I’ve replied with a query asking them to give me some advice on what to do about it. 😉
Anyone else have any words of wisdom?
-
I sent Pegasus a service report for my two drives and they responded:
“One-bit ECC error was detected”
I’ve replied with a query asking them to give me some advice on what to do about it. 😉
-
[Jeremy Garchow] “Are the drives formatted as OS X extended?”
All of my drives including the Pegasus are Mac OS Extended (Journaled).
Most of the camera archive sneakernet drives are OSX Extended and 2-3 are NTFS. All of my drive dock backup disks are OS X Extended.
The key thing is my problems are a recent occurrence of the last two weeks or so. I’ve been working with all these drives for at least 6 months with no issues, one of the Pegasus arrays is a year old.
-
[Jeremy Garchow] “Wait, this drive won’t accept large files at all? This isn’t localized to just one Library?”
Ah, sorry. This is all finder related copying (not internal FCPX). I also tried using ChronoSync as that has sometimes been more dependable in the past. It effects multiple FCPX library packages on both drives (not sure if it is all libraries). I also cannot copy large AVCHD archives onto the drives at this point. …waiting to hear from Promise tech support.
-
10.9.5 did not fix things. I cannot copy large files to or from either Pegasus array or to or from any other external drive (via thunderbolt, USB3, or Firewire).
I can copy between other external drives without issue.
In the near term I am going to have to work off of a portable La Cie Rugged Thunderbolt drive.
-
10.9.2 to 10.9.5, yes.
Thanks Robin.
-
[Jeremy Garchow] ”
I think 10.9.3 was supposed to clear this up, but I can’t remember.”I just read that 10.9.2 has some kind of copy bug that Apple has acknowledged. I’ll go to 10.9.5 when I have the chance and see if that fixes things.