To other C300 MKII folks... Just did the update to FCPX 10.2.3, inserted the CFast card from the C300 MKII and tried to import some footage. FCPX did not see the clips inside the Contents folder. I had to move the Clips folder to the top level and then it worked... This was the same with the pervious version. Not sure what I'm missing or doing wrong here... Thoughts? Thank you!
BenB wrote: Multiple YouTube accounts? Really? Who the f*!# needs that? Is that what programmers waste time on? Well, crossing figures we'll see major functionality improvements/enhancements just before NAB.
I upload to multiple client YouTube accounts regularly. However, I have never done a share to YouTube or Vimeo direct from FCPX. I never saw the point of that feature. I prefer to export a master, make a YouTube/Vimeo submission submaster and then upload manually. I prefer to set all my security/metadata stuff manually - and I like to have those master files archived for future use or sharing with the client. I don't like giving up that control.
I just upload ProRes masters. I have clients, they pay for my bandwidth, it isn't an issue for someone making a living. Unless you live way more rural than I do, and there's simply no such bandwidth. But yeah, I agree, who gives a fart about direct uploads to YT of FB? There are WAY more vital things we need. Better multicam, etc, would have been preferable to most then 3D text, which I, and most editors I know, use rarely.
I'm very disappointed that this update does not fix a bug that occurs when you rename a clip in the timeline. If you do that, after restarting the application the clip you renamed will have lost it's used medial indicator in the browser. This bug has been around for quite a while; I've reported it - and was told my report was a duplicate of another report. I was hoping for a fix. I could make good use of both renaming clips in the timeline and having the used media indicator working.
I say bugger all that, ask those that use the thing every day, or at least have a vested financial stake in the thing, that is the editors, you and me.
Sorry I so don't buy any logic that Apple cares, they care way way more about the musicians than with video editors, even though many are both, Logic has a better updating, listen to the users than the FCPX team.
150 days, is a long time, this minor update, what is has done is made the community more angry as the updating was long overdue, and basically fixed the timecode window, something we stopped caring about 149 days ago.
I agree, who gives a rose about multiple youtube accounts, how many blog to more than 1 account, hell I have trouble keeping up with 1 twitter account with about 100 followers, multiple youtube accounts, a nightmare, and this was important to Apple???
Something is not right, I can picture the same conference room, Jony comes in and says, get a fix out there to shut up the users, and so off they went, fixed the solution in less than a month, yet nothing was posted to fix.
Again I ask the question, we know months in advance about the new version of Mac OSX through the very public, very well reported beta system, no secrets in that aspect of Apple, so why with a tiny app called FCPX/Logic X?
Why not have 2 versions, public master 10.2.3 as it is today, and a public beta 10.3? We can see the updates, report on issues, it was be a form of internal voting, surely this helps guide workflow, I am confused, and wish I knew who asked for multiple youtube accounts???
Yet Richard Taylor and many others ask about scrolling timeline, like scrubbing on/off, yet this is not in, 1 timecode window, not two...a separate window for clip, timeline duration, instead of doing the control D, then having to press esc to exit, damn annoying.
Dammit Apple, choose one path, and stick with it, either no secrets or total secrecy...
Yes I would have preferred to have waited for a 1-2GB massive download for each of the 3, FCP, Motion, Compressor instead of this tiny update, which fixed basically a error in the timecode window. No saving workspace, no audio sliders, so I am bassically disappointed in this update! It did not need to happen. It could and should have been held back and released later.