Jeremy Garchow
1
After Effects Coin
72
Apple Final Cut Pro X Coins
74
COW Coins
1
Solve Coin
Forum Replies Created
-
Yes it seems odd unless something “broke” the metadata to trick FCPX in to thinking it’s a different file? Did any other app touch the files before you tried to relink?
What might help is an xml of the clip from your library, and an xml if that clip from their library. Select the clip in the browser and export an xml of only that clip.
-
No, but please request this to Apple. Would be great to have and is a long standing feature request!
-
[Bret Williams] “But are those TCs or in’s and outs?”
I’ll take both for 200, Alex.
-
Have you tried making a new project and copying/pasting the old timeline in to it?
Sometimes deleting cache will help too.
-
Do you know which clip?
Sometimes, it’s best to set act clip back to normal and remake the speed ramp.
-
As a control, have the editor send a project in a transfer library vs an XML and see what happens.
The tc is definitely off between those two files you’re showing.
-
[Michael Gissing] “All the more reason why having to buy a new case, screen, keyboard etc is silly when the most likely thing that needs to adhere to the old 18months churn is the GPU.”
GPU is even more specialized than CPU. Increased specs aren’t a direct correlation to more performance.
-
[Tim Wilson] “I don’t think it has anything to do with the economy, but more of a recognition that the stuff we have works pretty well, and moving to new platforms/devices/operating systems without NEEDING to causes more problems than it solves. “
Well, when you say “economy” do you mean overall growth (or loss), or overall price of goods and services (including video services)?
I think that while yes, computer refresh is down, productivity with that one machine is up. Way up.
I remember the new computer every 18 months cycle. It was the time of g3 to g4, or single core to dual core, or SCSI to PCI to PCIe. There were real infrastructure changes that would ripple out to almost everything you owned. There were shifts like editing uncompressed SD to editing uncompressed HD and changing the entire infrastructure to accommodate. Buying a new computer also meant buying the new infrastructure around it.
Now, all of that is done with a single cable and perhaps an adapter or breakout box. It is a bit of a different world. Specialization is greatly reduced. One computer can do a whole lot more these days than those days, and ironically, the profit margins of yore could do a whole lot more than the profit margins of today. So while having stuff that works pretty well today is good, it means that you have to do a whole more with it in order for it to turn the business crank. There are also real world limits of processing power, corporate responsibility (waste, power management, etc) now that everything a chip in it, as well as having to buy everything else you need to run your business these days.
-
[Oliver Tosh] “VTDecoderXPCService is still running up the CPU and this all started after the last update. “
This usually indicates some sort of transcode.
Do you have Compressor on your machine?
Also, what is in the project? Do you have multicams? Is the preference set to make optimized media on multicams?
Are there any background processes running (hit command-9 to bring up the background tasks window).
Jeremy
-
[Tim Wilson] “This isn’t to denigrate the efforts of Apple’s third-party outreach and support efforts. Those people do care. But I think it’s important in a debate to make the value-neutral observation that limits exist to the kinds of help or access that they’re able to provide. “
What’s interesting, if we are talking specifically about the claims on Laforet’s blog, is that Red support is third party support in FCPX. You have to download and install a plugin from Red, not Apple, to use Red footage within FCPX. Out of the box, FCPX can not read r3d natively.
The other NLEs in question use their own media readers, and implement Red’s SDK to gain access to the raw controls for Red, and then offload processing to their media encoders and decoders.
So, while BMD is closer (as their software works more quickly) this is what is meant when people say that Adobe doesn’t develop for the Mac, which sounds weird. Yes, they develop software that works on the Mac (and Windows), but they don’t develop using the tools available to them in the OS. They write around it, because they have to, in order to develop one software that’s cross platform than develop multiple softwares for multiple platforms. This is certainly a business choice by Adobe, and not because Apple doesn’t allow access to all the switches.