[Andy Mees]

Silly question perhaps, but you have relaunched FCP since the install right? FCP needs to load these components when it starts up that app … if you installed but didn’t restart then the app won’t have loaded the components.

Assuming thats not the issue, check your /Library/Application Support/Final Cut Pro System Support/Plugins folder … do you see two specific components installed there, being SonyImportPlugin.bundle and SonyExportPlugin.bundle?

[Andy Mees]

Hey Jason
As per the specs, the up/down/cross has always been there for output. It’s up/down/cross on input that is currently being added to the drivers. Its looking good … loving my MXO2. Very active development is good. Not a new box, just new features!
Great stuff.
Andy

[Andy Mees]

look for the Bloom filter

[Andy Mees]

Doh! sorry Will, quoting website addresses from memory there and that one was a bit of a longshot!
Shane’s blog post is here: https://lfhd.blogspot.com/2009/03/matrox-mxo2-early-observations.html

[Andy Mees]

Will

The current drivers don’t support up/down/cross convert on capture … thats in the next release (amongst some other goodies!)
Shane’s been blogging about it already … read more at https://www.lfhd.com

Best
Andy

[Andy Mees]

Mark\
You seem to have the converse problem … you actually NEED Calibrated Software’s IMX component.
If you use a Quicktime wrapped IMX file on a PC then you’ll need a Quicktime Component that can decode that format … thats what the Calibrated Software IMX Decode Component is for:

https://www.calibratedsoftware.com/QIMX.asp

Best
Andy

[Andy Mees]

Knew it was here somewhere (Thanks Bjoern) …

https://forums.creativecow.net/thread/8/1007928#1007983

[Andy Mees]

You can trick FCP into letting you edit in a non standard editing timebase such as 15 fps by creating a dummy project and saving it as an XML file, then edit that XML file in a text editor and change sequence’s rate >> timebase property and timecode >> rate >> timebase property to 15 (or whatever you need)
Import that XML back into FCP (ignore the errors) and the new sequence created will be the one you need.

[Andy Mees]

[Shayne Cantly] “I’ve downloaded the file, and copied it into the folder, but it’s not coming up where you’ve said it should. “

Thats odd … just in case it didn’t happen automatically, did you remember to unzip it first?

[Shayne Cantly] “I even looked at the file info to see where you had it installed, and everything seems to correct on my end, but it just won’t show up!! I’ve restarted the computer as well….still no luck. “

Are you 100% certain you have installed in the right folder? you have a couple of options:
/Library/Application Support/Final Cut Pro System Support/Plugins (thats the Library folder at the root level of your system hard drive .. and the plugin goes inside that Plugins folder at the give path)
or ~/Library/Preferences/Final Cut Pro User Data/Plugins (thats the Library folder thats inside your home/user folder .. and again, the plugin goes inside that Plugins folder at the give path)

[Shayne Cantly] “When I double click on the file, it says Wrong Type within FCP. “

Its not an exceutable in that way, it needs to be in the Plugins folder as above, and is loaded by FCP when the app launches

[Shayne Cantly] “Is there any light you can shed?? “

Hopefully one of the above comments?

[Shayne Cantly] “Is it still compatible with the current version of FCP? “

Absolutely.

Best
Andy

[Andy Mees]

Tel

You might want to also take a look at Convergent Design’s nanoFlash and Flash XDR solutions … not cheap tho.

Andy