Andreas Kiel
Forum Replies Created
-
-
Again, as the others said: great job Logan.
I’m not editing that much anymore and these jobs I do unfortunately never reach the public because of NDAs. In any case they are quite boring and so the public won’t miss them.
They are complicated to do with any NLE. With FCPX in the current state they can’t be done.But I do like a lot of ideas and features of FCPX. Keyword collections are great once you understand, connection with Motion for generators, transitions etc is very cool. Handling DSLR footage is fast, I also love to edit my GoPro stuff with it. Next month we will do some 3D stuff with the GoPro and it seems – after some tests – that it will work smoothly.
The other side of the medal is for example working with P2 formats. It takes even longer than with the old fashioned Log&Transfer. Apple claims that they are working with native formats. In case of P2 it’s true BUT all the clips are copied to a QT container. So IMHO there is no progress. All clips are automatically renamed with no option for the user. You can re-rename them manually. P2 clips do have quite a lot metadata. My hope was that all this metadata would be transferred – unfortunately not. But at least there are more visible compared to previous versions and other NLEs.
Another thing is workflow.
Many people here said it’s only about story telling. I mostly agree. But to get to the point to start telling a story it might take some time to be organized – especially in a collaborative environment. And the story often has to be finished in a collaborative environment.
Here FCPX does clearly have several lacks which either can be fixed by Apple itself or third party developers. But the third party companies have to catch up, which will take a bit of time. For the third party people I do not mean those which create effects (maybe you even don’t need them that often anymore as you create effects by our own with Motion). I mean those which create workflows.The current update does give me some hope both for more metadata handling and workflow support with third party apps.
I do understand those people who like FCPX and do see a bright future and I think there is a least some future stuff which will be amazing.
I also understand those people who say it’s not ready for prime time and not even a version which can be called a 1.0 release. For the latter ones I see a problem in so far that Apple is not too responsive. Adobe said “if you see a chance take it” – and they did. Avid did somehow the same in another way. This makes the situation even more complicated. Many people gave up to convince (email to) Apple that some features are needed (and use forums like this to complain), therefore Apple thinks these features are not needed, which leads again to new complaints.I can understand all arguments, and I’ve to live with bugs and lacks of FCPX – if I want to use it. If I don’t want, I still can run FCP7 for some time or switch to another app. Using FCPX, Premiere, Avid, Media100 etc can take some time to get familiar with. Sometimes time is money and sometimes time matters. Latter can be interpreted in whatever way you like.
Again: Logan, great work.
Spherico
https://www.spherico.com/filmtools -
Andrew Richards wrote:
“What were the critical workflow capabilities missing from 10.0?XML I/O = solved
…”Hmm, at least for this point I can’t say it’s solved. It’s there, but that doesn’t mean it’s working as expected by some users.
I think it’s good step, but no solution.
If you can’t do a XML round trip from FCP X to FCP X that doesn’t sound like a solution – at least for me.Not that I dislike FCP X. For example I love how the did the Motion interactive FCP generator options – they are not perfect yet, but pretty cool. Everybody can build effects now.
Regarding the shop and updates I got a mixed feeling. If I’m in a region where internet connection is slow and expensive it’s bad – very bad. My temporary provider tried to charge me about 4000 USD for the FCPX download (took 10 days).
On the other hand it could be very convenient and maybe a bit more environment save.
Spherico
https://www.spherico.com/filmtools -
David,
It’s not totally correct. Both are XML (7 and X) but it’s different language.
To interchange from 7 to x or the other way round will be basic because of the different structure and features.
So it’s something like updated EDL stuff.Spherico
https://www.spherico.com/filmtools -
What kind of shock?
The iPad is quite a good control surface, in some cases an excellent one.
But if I would do editing I would miss a keyboard, as the current way (of most tablets) is not convenient for editing as it always covers a big part of the screen and with the iPad you have to toggle between letters and numbers.
That’s definitively no fun, and what’s about the material? Where does it come from?Andreas
Spherico
https://www.spherico.com/filmtools -
Dear Kim,
I’ve read the thread roughly.
I do understand and agree that things are changing constantly and all of us have to be open minded.
What I didn’t understand was the way you typed in your replies.
All lower case, no breaks, wrong ellipses. Looks like an old fashioned Morse Code which is hard to read by normal humans.As an editor you understand that within a story there are scenes, cuts, effects etc. With communication it’s the same.
If you write a story that way you communicate, the story won’t be a success.On the other hand you can even go a step further with your way of writing and disregard spaces between words like it was done in ancient Hebrew. This will help to make people in a future world to make studies about what was meant with this text.
No offense, just a thought.
-Andreas
Spherico
https://www.spherico.com/filmtools -
Looks pretty cool.
I tried with a simple sequence and it seems to work.Andreas
Spherico
https://www.spherico.com/filmtools -
As I said earlier, Layered TIFF is a very useful format.
Andreas
Spherico
https://www.spherico.com/filmtools -
Mark,
You always (since PhotoShop 5) can save as layered TIFF. That will keep all informations a PSD file has. When you want to do changes on a layer, an effect, a style or with text, everything works like with a PSD file.
In FCP classic the file shows up as flat. In FCPX as well.Spherico
https://www.spherico.com/filmtools -
@ Sean
I didn’t want to be offensive, not at all. But you wrote some comments and I commented your comments. :).
Just adding my comments to help people to think about metadata.‘AXEL’ is still not born and I don’t know how long it will take to ‘incubate’ and how it will look like. Only thing I know: It will be the replacement of the legacy ‘xmeml’ XML way Apple used with FCP – and it is easier to pronounce.
I know Helmut Kobler since a while and I do know a bit of his work(flow).
He does know something about the way I interpret metadata and manage them.The main thing at this point is: when will Apple release specs. Without specs no tools can be released. With no tools available there can’t be any interchange or collaborative work.
In former times Apple supplied 2 kind of ‘hooks’ for developers. One for very selected developers to create importers/exporters, the other one for handling XML (to communicate with FCP without clicking buttons, menus, files) for the rest of the world.The quote you used from Walter Biscardi Jul 28th who obviously quoted another person.
Apple will be releasing the XML code, or “hooks” to developers in 2 weeks so they can start developing third party XML apps – Evan Schectman from Outpost Digital.Funny thing is that Outpost Digital is way closer to Apple than me, but they do use a metadata helper app I created – and now trying to work with FCPX it’s not working for them. There is no metadata exchange at this time.
And metadata (as data over data) where made for this.Regards
AndreasSpherico
https://www.spherico.com/filmtools