[Craig Seeman]

Are you importing from Camera, Card Reader, Hard Drive (which involves copying of course)?

[Craig Seeman]

I’m now hearing a couple of reports that the issue is trying to import from the camera directly.
FCPX understands the directory coming from a card reader but has problems if you try to import from the card in the camera.

[Craig Seeman]

[Chris Church] “it takes a matter of seconds”

User intervention creates risk.
Import should work like any other supported camera.

Some people aren’t having the issue. Apparently others are still having import problems. I wouldn’t want to take the professional risk.

Perhaps you need to format the card in camera after firmware update. Perhaps all clips need to be the same setting. I don’t think Sony has provided those instructions.

People are reporting varying degrees of success and failure so there’s a variable that hasn’t been determined yet.

[Craig Seeman]

Don’t have the camera at this point. The workflow, to date, is too convoluted for fast turnaround work.

[Craig Seeman]

I’m seeing a scant few reports ranging from it works to same problem as before. Yours is yet another variant.

[Craig Seeman]

You can use Compressor 4 to create a DVD complaint file (separate video and audio).

I’m not absolutely sure of DVD Studio 4’s built in encoding would work on Yosemite. Keep in mind it may be problematic in that you’re using Final Cut Studio 2 and I suspect most who are on Yosemite are using Final Cut Studio that was released in 2009 (often called 3).

[Craig Seeman]

Apple has made major improvement to their H.264 encoding. Not only is the quality much better but Compressor 4.2 is generally faster than older versions.

[Craig Seeman]

Compressor 3.0.5 was never available in the app store and wasn’t the last iteration of the 3 series. I believe the last was version 3.5.3. Version 3.0.5 was part of Studio 2 series (FCP6 I believe). 3.0.5 may not be compatible with Yosemite.I believe the .05 update was released Nov 2008. 3.5.x may be as some people do have FCP7 running on Yosemite.

If you don’t have Studio (3 never actually called that though) then you may want to spring for the $50 and buy Compressor 4.2 from the App Store.

[Craig Seeman]

QT7 and QT10 are pretty much unrelated technologies at this point. QT7 is basically EOL.
QT7 is based on QT Frameworks and QT 10 is based on AVFoundation. The don’t handle frames or flags the same way.

I would target 640×480 and test in QT 10 and WMP 12. WMP 12 can play H.264 .mov files.
640×480 is a “universal” 4:3 Standard Def frame size.

[Craig Seeman]

[Carsten Orlt] “Why should they if you can’t?”

With a case number there’s nothing to remember. I’d have the case number emailed to me so I can use in any subsequent submissions on the same issue. This is common procedure with many companies I submit issues to.

[Carsten Orlt] ”
With all due respect I think “

Hmm, I think collectively we are important, probably much more so than individually. Developers certainly weigh the prioritization of both issue resolution and feature improvements, at least in part, based on the number of reports.

That’s why you have those most involved with FCPX making entreaty to us to fill out the Feedback Form. It’s only in numbers where we have most impact.

[Carsten Orlt] “Adding a case number would only add to the workload “

I’ve worked with support teams before. This is automated. Handing the issue itself might involve human intervention but the case numbers would be automatically generated. BTW there’s good reason why Apple has a series of question when you fill out the feedback form. It can immediately be categorized so they know any issues and basic specs vs any feature requests and the system the user has in context.

[Carsten Orlt] “My philosophy is that I give as little feedback as possible,”

From what I understand that’s the opposite of what hear being requested by Apple and those close to them. They want and encourage feedback. It’s part of the “market survey.”