fbpx
3 Post Moderation Rule for New Boarders (25 Jan 2021)

New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.

MTS Files really slowing FCPX down, even with proxy

More
13 Jan 2015 19:05 #58383 by fcpguru
I've just imported a bunch of MTS files (not sure what the camera was) and FCPX comes to a crawl whenever I try to use them. Even generating proxy files and using those, the system drags the moment I work with that particular event and clips. Has anybody else experienced this and maybe have an idea for a solution?

Please Log in to join the conversation.

More
13 Jan 2015 19:27 #58386 by FernKraft
I have.

It usually happens when I receive MTS files that have been (for some unknown reason) taken out of the AVCHD folder/bundle, and given to me for ingest.
After I tell them not to do that ever again, I use Clipwrap to re-wrap the .MTS into a .MOV

This has been my work around. Clipwrap ain't free, so their may be other options.

www.divergentmedia.com/clipwrap

Why, when FCPX does the same it causes problem... I don't know.

all the best,

Please Log in to join the conversation.

More
13 Jan 2015 19:29 #58387 by fcpguru
Yup - that's probably it. They were outside the folder on the drive I received. I'll check out Clipwrap and see if I can do a swap media in FCPX

Please Log in to join the conversation.

More
13 Jan 2015 19:36 #58389 by fcpguru
Argghh - unfortunately ClipWrap adds some timecode metadata information that differs from the original clips already imported and edited, making a swap impossible.

Please Log in to join the conversation.

More
13 Jan 2015 20:05 #58390 by FernKraft
the only program I know of that MAY help you now is QtChange...

www.videotoolshed.com/product/42/qtchange

Hopefully others have a better idea of what to do...

Please Log in to join the conversation.

More
13 Jan 2015 20:10 #58392 by FernKraft
found a little note on the Qtchange website.

"FCPX only reads timecode if a reel name is present"

Try clipwrap again, but add a Reel name that matches the "original" files.

Best of luck,

Please Log in to join the conversation.

More
13 Jan 2015 20:20 #58393 by fcpguru
Thanks for your help - no dice I'm afraid. There isn't anything in the Reel name. I attempted to add one, but that didn't work. All the clips start at 00:00:00:00 and after clipwrap converts them, they have a starting timecode (11:23:02:11 etc). This is why FCPX won't relink them.

However I could use Pro Media Tools to batch alter the timecode and that will work. Pretty expensive fix tho between the two tools...

Please Log in to join the conversation.

More
13 Jan 2015 20:34 #58394 by FernKraft

Please Log in to join the conversation.

More
13 Jan 2015 20:49 #58398 by kozi006
Try optimizing the media. It worked for me.

Please Log in to join the conversation.

More
13 Jan 2015 20:50 #58399 by fcpguru
I tried making proxy files, that usually solves it, but not this time... i'll try optimizing and seeing if that helps

Please Log in to join the conversation.

More
13 Jan 2015 21:35 #58404 by ronny courtens
Just one thought: when you create Proxy media and you switch playback to Proxy, FCP X uses the proxy media which are separate ProRes Proxy files that are physically independent from your original media.

So if your system runs slow in Proxy mode there is something wrong with your system, and this has nothing to do with wether the proxies were generated from MTS or whatever other format.

- Ronny

Please Log in to join the conversation.

More
13 Jan 2015 21:39 #58405 by fcpguru
Ronny, I agree with you, but I can isolate the issue to this particular footage and the system is pretty snappy with all the other footage in the project (ProRes, 5D, RED, GoPro). That's what's particularly confusing and frustrating about it. In fact the whole system is performing better using unoptimized media than proxy for some reason. Maybe some of the proxy media had a bit of trouble converting. I noticed I can't even drop in the .MTS files into compressor and would have to use AME to transcode them if I wanted to try that route.

There is something funny going on under the hood, but it's hard to diagnose.

Please Log in to join the conversation.

More
13 Jan 2015 21:50 #58406 by ronny courtens
Ah, I see. Now that's interesting. Are your proxy and optimized media on a different drive than the original media?

- Ronny

Please Log in to join the conversation.

More
13 Jan 2015 21:52 #58407 by fcpguru
Yes, the original media is on a WD Thunderbolt drive and the proxy is on my promise RAID - could that have something to do with it?

Please Log in to join the conversation.

More
13 Jan 2015 22:02 #58408 by ronny courtens
Possibly. I'm just trying to narrow down the probable causes of this issue. You said everything seems to run smoother with original media than with proxy/optimized, so having the proxy/optimized media on a faulty drive could be one of the possible causes.

Is there sufficient space left on that drive?

Can you perform a drive speed test on it? You can use the BM speed test app: itunes.apple.com/nl/app/blackmagic-disk-...st/id425264550?mt=12

You can also use Disk Utility check and repair the drive.

I cannot guarantee that this is the cause of you problem, but it's certainly worth testing it out.

- Ronny

Please Log in to join the conversation.

More
13 Jan 2015 22:08 #58409 by fcpguru
I have about 1.8TB free of 9TB - BM speed test is showing read/write speeds around 400. My hunch is these .mts files aren't happy being out of their shell since every operation with them is just slow. Who knew C100 footage would be such a pain (well, I'm sure it's not when the camera team delivers it properly)

Please Log in to join the conversation.

More
13 Jan 2015 22:09 #58410 by joema

fcpguru wrote: ...just imported a bunch of MTS files...and FCPX comes to a crawl whenever I try to use them....


Is that when you import the entire group into your main library, or even a single MTS file in a test library is slow?

Maybe a quick test would determine whether it's an interaction with your larger project or every MTS file is slow in isolation. It also facilitates trying the imported MTS file on different hard drives. Just move the little managed test library to another drive and try it there.

Please Log in to join the conversation.

More
13 Jan 2015 22:09 #58411 by FernKraft
For what it is worth...
I had a project a while back where a single file of my transcoded media had become corrupt. When ever I accessed that Library everything was very sluggish and caused beach balling. I solved that problem by deleting the transcoded media, and re-transcoding.

I had isolated the transcoded media as the problem by moving the transcoded media folder to a different drive, and then unmouting that drive; Thus making it completely independent from FCPX.

Please Log in to join the conversation.

More
13 Jan 2015 22:12 #58412 by fcpguru
I'm not sure, but I will say this: when I imported the files I selected them all and FCPX took about 15 minutes to "Verify" the media before beginning the import process. Is that normal?

Please Log in to join the conversation.

More
13 Jan 2015 22:17 #58413 by ronny courtens
No, that's not normal. I have worked with extracted MTS files before, they import and play without any problems.

There definitely is something fishy with these files. If everything else in this project runs fine it may be a good idea to convert the MTS clips externally to ProRes and work with the converted clips instead.

- Ronny

Please Log in to join the conversation.