-
Range-based keywording: unique to FCP X?
-
[Oliver Peters] “I understand, but I really don’t care why it doesn’t work (that’s not directed at you). I’m sure ARRI what just as surprised as the rest of us! Makes it really hard to develop workflows around something you can’t rely on.”
Yep. It’s one of the reasons I think we see 10.0.3 in its rushed state.
Apple wanted to let people know that XML is there, not quite as robust, but it’s there and will be ready.
Some day.
Maybe soon.
Maybe not.
-
[Walter Soyka] “I’ll be there. Maybe we can get an FCPX or Not forum mini-meet going? Anybody else going and interested?”
I’m up for that – the more the merrier.
I’ve got plans Mon late evening and Tues from 4pm on – but daytimes, happy hours and Wed are cool.
God knows theres no lack of places along the monorail where some of us could assemble at a table for a chat.
Anyone’s welcome to raise a hand if they want in as far as I’m concerned.
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
[Bill Davis] “Anyone’s welcome to raise a hand if they want in as far as I’m concerned.”
That would be lots of fun. I can’t make it this year!
-
[Jeremy Garchow] “Apple wanted to let people know that XML is there, not quite as robust, but it’s there and will be ready.”
Interesting note on the QT reel number issue. The FCP X display (Event Browser column) does not display it, but it is read by the app, because it passes through the FCPXML. I just sent a test file with Alexa clips through Xto7 to FCP 7 and then exported an EDL from there. Reel number shows up in “Modify TC” and also in the EDL. Go figure.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Bill Davis] “I’m the contrarian here often, but I’m not convinced that 3D is ever going to be much more than a solution looking for a problem “
Here I totally agree with you. However increased frame rates – shooting 60 fps and viewing at 60 (showscan was the early prototype) as well as 4K viewing will use all the bandwidth modern systems can handle. But,as you stated, 3D for home TV viewing, as opposed to gaming, is the quadrophonic sound of the 21st century.
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. Bieberkopf -
[Herb Sevush] ” However increased frame rates – shooting 60 fps and viewing at 60 (showscan was the early prototype”
720p does it right now, today.
-
[Jeremy Garchow] “720p does it right now, today.”
Yes, I shoot 720P60 all the time, but as far as I know it’s never broadcast that way, it’s always converted to 1080i for broadcast, throwing out half the temporal information. What I’m talking about is 4KP60, in a theater.
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. Bieberkopf -
Depends on the channel.
I hear you about 4k60p, but I think we know what that will look like.
I’m curious to see 48p.
-
[Walter Soyka] “Jeremy seems to have a lot of confidence that future updates to FCPXML will allow third parties to deal with this. I’d love to see that, and I think that third-party developers are offering some really innovating solutions (like VirtualMXF), but I also think that splitting DAM duties between FCPX and a third-party app reduces the power of having a DAM in an NLE in the first place.”
From where I sit, FCPX is begging to be the client in a client/server setup where the heavy lifting of storing and serving media and metadata is on the server-side and FCPX is only mounting what the editor is working on (while everything else is a quick search away). The way it sits now, FCPX has a glass ceiling for volume. Fine for small-scale stuff, but a busy shop would find itself working around it with Event Manager X, the sparse image workaround, or SAN Locations on Xsan.
I’ve noted before that OS X already has the frameworks to enable this. FCPX interacts with its Events and Projects via CoreData SQLite persistent stores. But what if it could also read and write to a centralized PostgreSQL database? Live sharing of Event and Project databases would enable some killer workflow efficiencies!
[Walter Soyka] “I hope that this is an area that Apple intends to develop themselves in the future, because this is one of those maddening close-but-not-quite features.”
YES.
Best,
Andy -
” FCPX is begging to be the client in a client/server setup where the heavy lifting of storing and serving media and metadata is on the server-side and FCPX is only mounting what the editor is working on (while everything else is a quick search away). The way it sits now,”
The stupid part is that FCP 7 with FC Server works (worked) EXACTLY that way.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up