A step backwards

[Paul Neumann]

No it’s not AVCHD. And I’ve been using FCPX with these cameras since day one. It’s broken now. Another thing with this is when I go to import selects (which it really won’t) it insists on copying the media to another location but if I import the entire CONTENTS folder it links to it.

I’ll check with Canon and see if there’s a new MXF utility for Mavericks. They had to put one out when X first came out, but eventually I think Apple took over making sure all Canon was supported.

[Glenn Grant]

A client gave me a thumb drive with .mts files on it and 10.0.9 would not recognize them, but 10.1 does. No fold structure or last clip.txt file just the .mts files and I can import them no problem. I am not sure what camera it was shot with but the according to FCPX it h.264

[Jeremy Garchow]

[Glenn Grant] “A client gave me a thumb drive with .mts files on it and 10.0.9 would not recognize them, but 10.1 does. No fold structure or last clip.txt file just the .mts files and I can import them no problem. I am not sure what camera it was shot with but the according to FCPX it h.264”

That’s because FCP 10.1 can read mts as well as mts2 files without the AVCHD folder structure.

[Matt Galuszewski]

(Paul Newmann) Another thing with this is when I go to import selects (which it really won’t) it insists on copying the media to another location but if I import the entire CONTENTS folder it links to it.

I have a XF100 and I can import selects either to a FCP X Library or an external location.

I am happy to answer any questions – maybe I am misunderstanding your problem.

Matt

[Mitch Ives]

[Jeremy Garchow] “I told you I was an idiot.”

Yeah, and I said I was because I didn’t understand your post.

I understand your point now. I think everyone agrees this is an improvement, the variable is how big a step someone thinks it is, and that seems to vary with who needed what?

I’m glad this works better for bigger houses. It doesn’t do much for me, but it doesn’t have to. If the price of making this a better collaborative tool for them is me wasting a day updating projects and manually relinking files… I can live with that.

As for performance I’m seeing a mix. Some things are quicker, but certain timeline updates seem slower. I guess everybody’s mileage my vary. As for the new MacPro, yes I’m guessing that’ll be a must. I was planning to get one, but the February thing is a bit disheartening. Hey, maybe I’ll have 10.1 figured out by then…

Mitch Ives
Insight Productions Corp.

“Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things.” – Winston Churchill

[Jeremy Garchow]

We haven’t ordered new hardware yet either. Mostly because we have been too busy to gather a list of all the necessary parts, and there will be necessary parts.

There’s a slight advantage as we can wait for the Thunderbolt 2 peripherals to trickle out.

My thinking right now is to get PCIe enclosures, but I go back and forth all the time.

Jeremy

[Mitch Ives]

My Pegasus2 ships tomorrow. I’ll have it next week.

I didn’t realize there is a TB to dual DVI cable from Apple. That means I can keep my 30″ display.

Here’s the tricky part. As it’s been explained to me, adding a TB1 device pulls down the TB2 to TB1 speeds. Since there are only three controllers for the six ports, you effectively get four TB2 ports, since any display or older TB1 device will pull down one controller (and thus two ports).

Ahhh… the things to think about…

Mitch Ives
Insight Productions Corp.

“Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things.” – Winston Churchill

[Jeremy Garchow]

[Mitch Ives] “Here’s the tricky part. As it’s been explained to me, adding a TB1 device pulls down the TB2 to TB1 speeds. Since there are only three controllers for the six ports, you effectively get four TB2 ports, since any display or older TB1 device will pull down one controller (and thus two ports).

Ahhh… the things to think about…”

Exactly. This is why I am trying to wait just a bit longer, and the delay might actually be a blessing in disguise.

If you haven’t seen it, here’s the TB2 port mapping for the new MacPro:

https://support.apple.com/kb/HT5918?viewlocale=en_US&locale=en_US

[Mitch Ives]

Until Apple gives us TB2 displays, I think we’re shot. I wonder if they’re even considering that?

Things like the IoXT, BM, etc. will all need updates as well…

Mitch Ives
Insight Productions Corp.

“Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things.” – Winston Churchill

[Paul Neumann]

First off I’m using a Early 2013 Macbook Pro Retina maxed out with 16gig ram/512 SSD updated with Mavericks and a November 2013 iMac i7/24gig with Mavericks. External Thunderbolt storage for both of them. Now that the gear is out of the way let me just say that this new FCPX is a total head scratcher.

on the iMac:
Sees cards (full copies of cards that is) from XF100 just fine and imports selects.
Sees cards from XA10 (AVCHD) fine but renames clips as “Clip #1, Clip #2…”

on the MBP:
Sees cards from XF100 but only imports first clip of however many selects you choose.
Doesn’t even recognize any AVCHD file structures on any number of drives I plug in.

The thing is just earlier this week I was mixing clips from both of these cameras on both of these machines with 10.0.9.

And for the record Prelude sees everything just fine. No problems at all.