-
Newer is better, right?
-
[Erik Lindahl] “”Processing files for import” pops up. Now, the second time I imported the files, it went much faster however. Maybe it’s cached some info about the files somewhere?
“Sure.
In the event folder there’s thumbnail and “peaks data”.
I am wondering of it had to do with your fw drive having been “spun down” that first time?
While I agree that there’s some slowness in the fcpx UI sometimes, importing isn’t one of the areas where I feel things slow down all that much. It’s not as fast as 7, though, but its doing more than 7 when importing.
-
I’ve noticed the same thing: Importing for instance 100 XDCAM clips into FCP 7 just goes IMMEDIATELY. If you blink your eye, the importing dialogue box is gone.
In FCP X, it takes its time.But as others said, it’s doing a bit more then FCP 7 too, and I still am in love how in the audiowaveforms of FCP X you can immediately see where audio peaks. Still.
I hope, next to (hopefully) many requested new features in 10.0.6 (leaked in a Red Giant Movie tutorial video today), that there is still some optimizing of the software being done.
-
It’s actually not really true that FCPX does more during import than FCP in many cases it’s just the opposite.
Most people just import Alexa right away into any of both apps. With FCP you were able to use the Alexa XML, which slowed down the process by maybe 1 or 2 seconds but you got quite a lot of metadata ready to use.
FCP used to write the metadata into the QT file structure during import. That’s one the reason you see a new modification date on imported files even though you haven’t touched them.
An example: We used to sync Alexa and other files externally with BWAV files. Using XML it “forced” FCP to make the file match the given metadata. This for example allowed just to open a QT file in any project with SCENE/TAKE/NOTE automatically seen.Working with TC is kind of nightmare as well with FCPX.It can’t handle multiple TC tracks and doesn’t allow to use “virtual” TC tracks. With FCP that saved/saves us hours compared to FCPX.
In the beginning we did some XML import tests for subtitles average time with FCPX from import start to ready to work had been 6 Minutes (different machines same file) with FCP it had been around 10 seconds. Final rendering for this kind of job is still a kind of disaster. FCPX is about 150 times slower than FCP
Spherico
https://www.spherico.com/filmtools -
[Mathieu Ghekiere] “(leaked in a Red Giant Movie tutorial video today)”
?
-
[Andreas Kiel] “It’s actually not really true that FCPX does more during import than FCP in many cases it’s just the opposite.”
It is true, “more” is relative.
XML is certainly slower and less capable at the moment in FCPX.
What I meant by “more” is that with FCP7, when you import, there’s no “Copy” of the file being made, FCP7 just reads the QT files in place.
In X, you can choose to copy it in to the Event, or make an alias to it in the Event. Both of these processes are verified (or so it seems) and it seem to take longer. Making an alias is obviously faster, but it still seems to take time to make that connection and verify it.
In FCP7, waveforms are only created when you add the clip to the timeline and the waveforms are on, or if you load the audio in to the viewer.
X does this almost automatically right from the start.
Jeremy
-
[Jeremy Garchow] “[Mathieu Ghekiere] “(leaked in a Red Giant Movie tutorial video today)”
?
“
Of the two new videos on their site, one doesn’t appear to work, could that be it?
Steve Connor
‘It’s just my opinion, with an occasional fact thrown in for good measure” -
I saw the leak as well, at least the 2nd incarnation.
They did a tutorial for a new plugin and the splash screen was 0.6 and there are a few new buttons in the interface (audio mixing icon was one). Then it was changed and the splash screen had some odd number like 10.0.1.56 and then the video went private (was on Vimeo). The tutorial went up yesterday. I’d imagine if 0.6 isn’t out today it would be next week (I’d hope).
BTW I can’t help there’s going to be some noteworthy change about the plugin architecture since BorisFX had a “Pre” webinar showing CC running in FCPX that is now months back. I’d imagine the release delay is that there’s something in 0.6 they liked or needed.
A big day is coming soon. Probably should start another thread if we’re going to spin off into rumors though.
-
“It’s actually not really true that FCPX does more during import than FCP in many cases it’s just the opposite.
Most people just import Alexa right away into any of both apps. With FCP you were able to use the Alexa XML, which slowed down the process by maybe 1 or 2 seconds but you got quite a lot of metadata ready to use.”Yes, but if you simply drag the Alexa files into the FCP 7 browser, bypassing the XML import, none of this data is written into the media files. Thus a faster process in 7. Correct?
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I don’t think what you saw there was a mixer icon, Craig, but a new button for the info pane. It was highlighted the same way as the “i” used to be when the pane is slid out. Also, mixer sliders would be up and down, not left/right.
-
[Marcus Moore] “I don’t think what you saw there was a mixer icon, Craig, but a new button for the info pane. It was highlighted the same way as the “i” used to be when the pane is slid out. Also, mixer sliders would be up and down, not left/right.”
You mean like the HUD button in Motion?
Reply to this Discussion! Login or Sign Up