Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro XDCam EX

  • XDCam EX

    Posted by Chris Jeremy on April 22, 2012 at 3:17 am

    My NLE of choice is Sony Vegas Pro 9.0e, so when a potential client asked if I could edit some material shot on a Sony HDCAM EX3, I said yes. Unfortunately only the second (smaller) of the two files of the spanned clip would import into Vegas or even Sony XDCAM EX ClipBrowser 2.6 (and even MediaInfo came up with nothing), so I told the potential client that one of his files must be corrupt and passed on the job.

    I was subsequently surprised to find that the whole spanned clip imported quite happily into Final Cut Pro using PDZKP1 XDCAM Transfer on a Mac.

    So why does Sony’s own NLE and browser software on a PC reject what can be seemingly effortlessly imported into the opposition’s software on a Mac?

    Chris Jeremy replied 14 years ago 3 Members · 3 Replies
  • 3 Replies
  • Jeff Schroeder

    April 22, 2012 at 3:46 am

    I don’t know how old that camera is, but it may be that you are two versions back.

    I’m sure I could have had that job with VP 11.

    Jeff

    2-Xeon X5680 @ 3.33 MSI Mobo 48GB DDR3 GTX 580 3072MB 16TB Attached Storage Win7 Vegas 11 x64

  • Mike Kujbida

    April 22, 2012 at 10:38 am

    Were you given only the original files or (preferably) the entire folder (master folder is, as I recall, BPAV, with other folders inside)?

  • Chris Jeremy

    April 23, 2012 at 8:24 am

    Complete BPAV folder structure with sub-folders and files on a DVD (presumably copied directly from the original disc). Exactly this same DVD was used on the Mac (and produced usable .mov files for FCP via XDCAM Transfer) as was used on the PC (which produced only the second part of the spanned clip either directly in Vegas or via ClipBrowser 2.6). Incidentally, only the second of the spanned files either played on VLC or showed up in MediaInfo on the PC, which is why I thought the file was corrupted in some way. But BOTH files worked just fine on the Mac when converted. Go figure.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy