Just downloaded and installed. I'll be testing it in two jiffys.

http://bssc.sel.sony.com/BroadcastandBusiness/markets/10014/docs/XDCAM_Transfer.zip

Always nice to see Mike Curtis is looking out for us!

Well, it works. :-)

Looks like it has quite a bit more functionality than the Flip4Mac plugin.

Since I only have sample MXFs I can't comment on FAM access. Greg?

Just downloaded...give me a few minutes.

-gb-

OK, I have been doing some tests. Although they say it only supports clips in 25mb mode, I have imported a clip that was done at 60p overcrank. The bitrate is halved to 17.5 VBR from the 35mb VBR quality setting because the vertical resolution is halved on overcrank. But it unwrapped just fine. I am going to upload it to the server.

It's a 39mb file of lighting an artillery shell (consumer firework). I had the shutter off so it's equal the framerate.

-gb-

I tried importing 35mb 30p and 60i. I can view it in the viewer however an error message pops up stating that this version does not support the codec. Otherwise it seems to be working pretty well. Quick and easy to use...

Update: can't import 30p in 25mb only 60i and 24p

Okay...here is the Quicktime file produced by XDCAM Transfer from the original MXF clip.

http://media.dvinfo.net/slomofireworks.movx

Do not click the link, use right click and save as or else you'll see a browser window full of garbage. Download then remove the 'x' from the end of the filename to play it.

-gb-

I tried importing 35mb 30p and 60i. I can view it in the viewer however an error message pops up stating that this version does not support the codec. Otherwise it seems to be working pretty well. Quick and easy to use...

Update: can't import 30p in 25mb only 60i and 24p


That's correct Troy. This version doesn't support 35mb rate. That's why I was surprised to see it would do the slo-mo stuff. I was of the impression that this version does not support 18mb rate either. But clearly it knows how to handle 17.5mb vbr so perhaps it will do the 18mb vbr files as well.

I am going to do a quick test shot to see. What happens when you try to bring in 30p from 25mb mode?

-gb-

What happens when you try to bring in 30p from 25mb mode?

-gb-

Same error message. The 24p stuff works fine. It all seems to correspond to the preset XDCAM sequences that came with the software. I figured the 35mb stuff won't work yet but it was worth a try...

It won't accept the 18mb vbr stuff. They said it wouldn't, but like you, I had to try. Just seems odd that it will accept it when it's 35mb at half speed for slo-mo stuff. Both clips show as 17.5mb VBR.

-gb-

I think the whole thing is odd. I don't see why they bothered to release something that won't allow people to use the datarate that they will most often use.

Not good at all. The Mac is really getting a raw deal when it comes to XD.

Looks like Blackmagic doesn't like the overcranked shots.

Since the file is really 1440x540, it's more scaling than Blackmagic can manage in real time. when trying to play in viewer out to BM, it sticks on a still frame.

When put in a timeline, it invokes the orange RT bar. Renders out fine though. wonder how Kona does? FCP displays fine in viewer and canvas, though, without any complaints.

[edit: The Apple XDCAM HD whitepaper mentions this as it turns out. "Overcranked shots will have to be rendered"]

Looks like Blackmagic doesn't like the overcranked shots.

Since the file is really 1440x540, it's more scaling than Blackmagic can manage in real time. when trying to play in viewer out to BM, it sticks on a still frame.

When put in a timeline, it invokes the orange RT bar. Renders out fine though. wonder how Kona does? FCP displays fine in viewer and canvas, though, without any complaints.

[edit: The Apple XDCAM HD whitepaper mentions this as it turns out. "Overcranked shots will have to be rendered"]

Nate, when I play back an overcrank .MOV created by XDCAM XFER, its resolution is still reported as 1920X1080 with a VBR of 17.5mb

-gb-

If you look at the properties of the mov in Quicktime Pro, it reads 1440x540.

When it comes to Quicktime files, there's the true resolution of the file, what it's been scaled to view at by the file creator, and then what the file was modified to play at by the user. It's really kinda crazy, there's can be 3 sizes in a quicktime file.

Anyway, the different apps report them all differently at times. Check the file out in QT Pro.

If you look at the properties of the mov in Quicktime Pro, it reads 1440x540.

When it comes to Quicktime files, there's the true resolution of the file, what it's been scaled to view at by the file creator, and then what the file was modified to play at by the user. It's really kinda crazy, there's can be 3 sizes in a quicktime file.

Anyway, the different apps report them all differently at times. Check the file out in QT Pro.

I was referring to QT Pro playback earlier, all three sizes are being reported at 1920X1080. Have a look.

-gb-

I know, here's the info panel you get when you Apple-I:

They are 1440x540 with a pixel aspect of 0.666.

I'm running into a missing codec problem when trying to import overcranked 60p footage. Does anybody where I can obtain the proper codec?

You need Final Cut Pro 5.1.1 and the latest ProApps update

damn... so i guess windows users cannot view it huh?

They are 1440x540 with a pixel aspect of 0.666.

I know what the 'true' resolution is being recorded at. I was confused when I saw the 1920X1080 show up for the video track in Movie Properties. But when I did it the way Nate did, I got the same results that Nate did. IOW, I wondered why this was happening. I was never contesting the 'actual' resolution the camera produces during overcrank.

-gb-

Sorry Greg, I didn't mean to come across as if I was correcting you. Merely confirming how the files are.

Sorry Greg, I didn't mean to come across as if I was correcting you. Merely confirming how the files are.

No offense taken at all, Simon. I was just curious about 'reported resolution' being different than actual resolution on that one Quicktime dialog. Nate and I discussed it via IM the other night.

-gb-

damn... so i guess windows users cannot view it huh?

Avid Liquid 7 is supporting the camera files...even in 35mb mode if I understand Brian's posts correctly.

-gb-

You are right Greg. I have shot 50I 35mbit, and imported it into Avid without any problem.
When you look at the properties, the files keep their original 35mbit bitrate when imported.
It is even possibly to export the files from Avid Liquid 7, in a variable bitrate of 35 - 60mbit.

The only drawback to Avid is that it is extremely slow. I will say it is so slow that it is excluded from any serious work!

On Canopus website, they claim their version 4 of Edius broadcast is out, it will support XDCAM HD.
I have preordered an upgrade, as soon as I receive it, you will get a report about the capability to work with the HD files!

I am software only, so I don’t need to wait for the hardware support which will arrive later!

Brian,

I'm upgrading to liquid chrome, which I expect will help with the liquid speed when editing HD and also integrates well into my setup. I'm curious how you are doing the export you mentioned. Can you elaborate?

Thanks,
John

I was just going to make this thread. I'm really looking forward to being able to rent and import from the XD CAM directly into my PowerBook, soon to be MacBook Pro!