Daniel Bernard
Forum Replies Created
-
Sorry it took me so long to answer, but thank you very much, it’s exactly what i was looking for.
-
Thank you, I’d be curious. What HDD speed test software do you use to make those tests?
I may try my tests again with the Blackmagic one and post the results. -
Thanks everyone for the help.
I ended up figuring this out with a colleague.
With anyone who has this problem, it’s an issue that can occur when FCPX read some XML files. (Yeah, I see now I had forgotten to say that the event was created based on a XML translated to FCPXML, my bad. I guess it hadn’t crossed my mind since it was a media issue, which, I believe, had nothing to do with XML files)I rexported the XML and things went swell, I just had tom redo the keywording a little.
Thank you all for you help.
Dan
-
Thanks to you both, I find it interesting to hear about other’s experience with such a workflow.
Andreas Kiel says it’s only a little slower, when the test speed from HDD speed test from Black magic gave me results which were around 30% slower. I’ve read that those test software aren,t always right, i guess it’s a clear case here.
And you write
“I tend to have projects that primarily use one Event. However, I’m currently working on a Year in Review video that will pull from dozens of bundles. I don’t know if having multiple Sparse Bundles on the same drive negatively impacts performance.”That is VERY interesting. The project the editor was working on had 5 bundles from the same drive, with each contained a certain numbers of events. It may be that more than the sparse bundle themselves that slowed things down.
I find it odd though that it took twice of thrice as much times with the sparse bundle solution than the one we use right one. Does the software used to generate sparse bundle could make the difference?
Thanks
-
Nah, I actually just used the same file, which doesn’t make any sense.
Thanks for your help. Tried the Compressor method, doesn’t do any good.
I’ve seen FCPX doing weird stuff since I’ve started working with it, but this….
Any other idea of what I could try? I’m running out of idea…
-
It seems unlikely it’s a clip corruption since if I take the exact same ProRes 422 file and reimport it in FCPX as is (which mean same file with same name in same location in same event), the clip plays fine.
It seems to be FCPX considering my clips like if they were JPEGs or something. I will still try the compressor method and get back to you about it.
-
Have you been working for a while with FCPX and Sparse bundles?
I was the first workflow we worked on at my job but we ended up changing how we manage things around. Quick test with Harddrive test speed software (like the one from blackmagic) showed us that the Read/Write speed on Sparse Bundles was dramatically slower than on the disk itself, therefore making FCPX runs much much slower.
I am curious about your experience with such a workflow since space bundles seems like a good solution to manage Events within FCPX.
Thanks
EDIT: Maybe I shoud mention we’re often working on pretty big project with hundreds of clips, effects, overlays, etc…
-
Ahah totally got all of it. Solution I hadn’t thought of. Would’ve tested it tomorrow at the office if you hadn’t done it yourself by pure curiosity, so thank you for trying it.
The project is just way too big (10 episodes of 45 minutes each) for me to spend that much time fiddling around mwith media that much. I’ll just Proxy the hell out of my 4444 and change their blending mode to Add.
Will do the trick. I just find it stupid mthat it isn’t allowed inside FCPX. Sometimes, I don’t understand what software developper are thinking about.Thanks for the help
-
By the way, I do have a workaround where I actually convert 4444 clips to Proxy and then change the blending mode to Add. It is just tedious and I believe a solution where my timeline read whatever is on it, bet it Proxies or ProRes 4444 just seems like it’s the way it should be which makes me believe there is something I am not getting somewhere.
-
Thank you the fast answer. It’s what I thought. Had a hard time getting to exactly 50.
—
Dan