[Ian Cook]

As I posted earlier we’ll be showing the updated workflows for both optical XDCAM and SxS next week. There should be no surprises. We also have production releases of the new components and they will be online in a few days.

[Ian Cook]

Hi Paul,

It sounds like either firmware or media. Under no normal circumstances should you get a ‘restore…’ message during recording. In most cases it’s a problem with the physical media and it seems to only happen with SD cards. Check your fw version and if necessary we can provide an update. Glad this had a happy ending, though. The bit that was lost was maybe whatever was in the internal record buffer plus whatever you missed switching slots. (Under normal circumstances you can cross cards without losing a frame, as I’m sure you are aware..)

Relieved,

Ian

[Ian Cook]

Thanks Greg..

Yes, the Calibrated decoders are not converting anything and not affecting copy/transfer time. You’re probably only seeing that in the properties because of the file association. In other words it’s a red herring..

As I wrote above, UDF is a file system and the UDF driver is a file system driver. The SxS Device driver is an actual hardware driver that speaks to the controller on the card when mounted in an e-card slot.

[Ian Cook]

The file system is not read correctly (if at all) without it

[Ian Cook]

JFYI the driver requirements shake out as follows:

SxS Device Driver: Required only when using an express card slot, regardless of UDF vs FAT status of media

SxS UDF Driver: Always required for viewing UDF SxS volumes, regardless of whether they are read over class compliant device (USB) connections. In other words you can have Fat 32 with no UDF driver but cannot do UDF without the UDF driver. It’s a file system driver whereas the Device driver is really just for talking to the card’s controller in an E-card slot..

Also when using both make sure the Device driver is installed first followed by UDF..

[Ian Cook]

No, there may be more data in the sense of higher bit rates and larger files but there is no hidden/raw data as there is with MXF on optical disc. I still think it’s an issue of overhead on your Mac. Have you tried a local copy to the desktop instead of USB–>Ext fw drive?

[Ian Cook]

Again, try not going fro USB to USB– any improvement? It may be a bus speed or driver overhead issue on the Mac. Generally we get about 2-2.5x

[Ian Cook]

Not really, the XDCAM Browser software will manage the copy but the only options you have for speed are the “Verification on/off” and “Priority in Move = Data Protection/Processing Speed” preferences. Are you going to an external drive, i.e. USB device to USB device? If you just do a drag and drop to the desktop do you see an improvement?

[Ian Cook]

I know this not the sweeping answer we’re looking for but those errors usually mean that the AMA plugin you need is not installed. It’s saying that the XDCAM optical (mxf) plug-in and the QT plugin don’t support the files you’re linking. Is it just those two files, while other files do link? Make sure you have the right version; at sony.com/xdcam-downloads and on the Avid site you can see whaich ones are req’d for different versions of Media Composer. If I’m wrong (entirely possible) I’m at a loss but feel free to contact me offline if you need to take this further.

[Ian Cook]

If you look in the Avid console what does it say after a failed AMA link? (Tools–>Console)