Just yesterday, we reported that a number of readers had sent in tips claiming that Apple had started issuing $299 refunds for the Mac App Store purchased Final Cut Pro X, released just several days ago. Following the backlash the firm has been receiving over the software, Apple last night quietly posted an FAQ section to Apple.com in an attempt to explain some of the decisions it made when creating the software.

Mirroring that of Pogue’s concerns posted earlier this week, Apple product managers go into specific detail about the new version, highlighting what can, can’t and will be able to be achieved in the future.

Highlights include:

Does Final Cut Pro X support multicam editing?

Not yet, but it will. Multicam editing is an important and popular feature, and we will provide great multicam support in the next major release. Until then, Final Cut Pro X offers some basic support with automatic clip synchronization, which allows you to sync multiple video and audio clips using audio waveforms, creating a Compound Clip that can be used for simple multicam workflows.

Can Final Cut Pro X export XML?

Not yet, but we know how important XML export is to our developers and our users, and we expect to add this functionality to Final Cut Pro X. We will release a set of APIs in the next few weeks so that third-party developers can access the next-generation XML in Final Cut Pro X.

Does Final Cut Pro X support OMF, AAF, and EDLs?

Not yet. When the APIs for XML export are available, third-party developers will be able to create tools to support OMF, AAF, EDL, and other exchange formats. We have already worked with Automatic Duck to allow you to export OMF and AAF from Final Cut Pro X using Automatic Duck Pro Export FCP 5.0. More information is available on the Automatic Duck website: http://automaticduck.com/products/pefcp/.

Check out the full FAQ over at Apple.com.

[9to5Mac via MacRumors]