[Greg Booth]

Hi,

That’s the demo watermark of our Calibrated{Q} DVCProHD Decode – once you purchase the full version then the watermark is removed.

Also, Jeremy, I dont think the Panasonic DVCProHD Decode component that comes with P2CMS works like you think it does – I tried it out awhile back and just now – and it’s never worked for me to open up DVCProHD QuickTime Movies in QuickTime Player or anywhere else.

Greg

Calibrated Software

[Greg Booth]

Hi Joe,

Open up your ‘Macintosh HD’ in Finder and look in your /Library/QuickTime folder – is there a CalibratedDVHDCodec.component? If so, delete it and restart.

Greg

[Greg Booth]

Hi Joe,

It looks like you installed our demo Calibrated{Q} DVCProHD Decode code (that’s the watermark pattern) – which isnt meant to be installed on computers with FCP. The uninstall instructions are in the ReadMe in the /Applications/Calibrated/Doc folder.

Cheers,
Greg

Calibrated Software

[Greg Booth]

Hi Hugh,

Calibrated{Q} MXF Import is a little more limited on Windows than it is on the Mac – it’s the same plugin; however QuickTime is much more pervasive on the Mac (its part of OSX) than it is on Windows – and this is reflected in Windows applications as well. On the Mac, many, many applications (including Final Cut Studio) are QuickTime ‘centric’ – meaning that applications will use QuickTime to decode video and open files (even files that are not .MOV). This is less of a case with Windows applications – where Windows applications tend to only use QuickTime to open and decode .MOV files. On Windows, the Calibrated{Q} MXF Import plugin is mainly used for giving QuickTime Player the ability to play MXF files for review and export them out to other formats (if you have QuickTime Player Pro) – there is also some limited QuickTime Reference Movie creation with the Calibrated{Q} MXF Import plugin that we hope to expand on later.

To answer the other questions:

The BPAV folders are the Camera Master and should never be deleted. This is the folder/file structure that many,many applications expect when working with XDCAM EX camera footage. Some applications can natively import XDCAM EX camera footage and others cannot, and even others choose a different route like FCP. The Final Cut Pro workflow is to re-wrap camera footage that is not .MOV files (i.e. P2,XDCAM HD, XDCAM EX ,RED) into .MOV files to edit with in FCP and use with other FC Studio applications. The .MOV files that FCP creates in the Log and Transfer process are not reference movies (they do not point back to the original MP4 or MXF files) – rather FCP takes the video/audio data and simply re-wraps the data into a .MOV files ( think of it as moving the contents from one container to another container)

Your PC CGI worker can read the .MOV’s created in this process with our Calibrated{Q} XD Decode codec – well, really the application reads the .MOV files and simply asks our codec to decode the video. As stated before, on Windows it’s most likely that he wont be able to read the MXF Files unless (a) the application he is using can natively read the MXF files (which it seems his can’t) or (b) the application is more QuickTime ‘centric’ and can use our Calibrated{Q} MXF Import plugin to open the MXF Files (which it seems it can’t either). As stated before, the Calibrated{Q} MXF Import plugin can auto-create QuickTime Reference Movies (small .MOV files that point back to the original MXF Files) which can be used by applications that support QuickTime to ‘work’ with the MXF files. But this feature is rather limited at the moment but we’re looking to expand on this feature at a later date. There are other Windows 3rd party software that can batch create QuickTime Reference Movies from MXF files as well.

>>>Is it better to edit with the MXFs as opposed to the Movs?

Well, that’s really a question you have to ask yourself and look at in terms of your workflow and what you’re trying to accomplish. For example – If you’re just using FCP in a small section of your workflow among a lot of other applications that natively support MXF then it probably would be better edit natively in MXF; or if FCP and FC Studio apps are a large part of your workflow and only a small part is on Windows than .MOV’s might be better. But these are just a couple of examples as everyone has lots of different variables in their workflows.

Well, hopefully that answered some things without being too long-winded or leaving anything out. You can always email me at info@calibratedsoftware.com for more questions.

Cheers,
Greg

[Greg Booth]

Hi,

The gray pattern is demo watermarks for Calibrated{Q} XD Decode, but you don’t need the codec if you have FCP installed and it specifically states our codecs are not for use when FCP is installed. The uninstall instruction are in the ReadME folder in the /Applications/Calibrated/DOc folder.

Cheers,
Greg

Calibrated Software

[Greg Booth]

Hi,

Glad you’re using our freeware application Calibrated MXF QuickStat. You can also download a demo (not freeware) of our plug in Calibrated{Q} MXF Import here:

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

this will allow direct importing of MXF files into FCP with timecode, and married video w/ audio. Another company called MXF4MAC also makes a MXF importer for FCP. If you just need P2 MXF video clips without the need for timecode or marrying audio with video clips then download and install Panasonic’s free P2CMS software as it includes a P2 MXF Importer as well but it does not support timecode.

Cheers,
Greg

Calibrated Software

[Greg Booth]

Hi,

Your AE designers can download a free demo of our Calibrated{Q} DVCProHD Decode codec for Mac or Windows here:

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

Also, Premiere Pro CS4 and AE CS4 can natively import DVCProHD QuickTime movies except for 1080p24,1080p25,and 1080p30 DVCProHD QuickTime Movies and another company called DVFilm has a DVCProHD QuickTime codec for Windows.

Cheers,
Greg

Calibrated Software

[Greg Booth]

Hi,

Both DVFilm and my company, Calibrated Software, offer DVCProHD QuickTime Codecs for Windows. Also, PPro CS4 can read DVCProHD QuickTime Movies (except for 1080p24,1080p30, and 1080p25). Also, our DVCProHD QuickTime codec is available on OSX as well.

You can download a free demo of our DVCProHD QuickTime codec here for OSX or Windows:

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

Cheers,
Greg

Calibrated Software

[Greg Booth]

Yeah, it probably has to do with the fact that he’s using 720p50 footage – which uses 25FPS timecode even though its 50FPS for the video and then PPro uses a 50FPS timeline for editing 720p50 (not a 25FPS timeline) and then not too sure if FCP exports out a 50FPS or 25FPS EDL for 720p50 video (but if its a CMX 3600 EDL it should be 25FPS). Anyway I think PPro is probably just adjusting the timecode’s representation in the Project bin to match the EDL and timeline FPS.

Without actually looking at the MXF file and QuickTime file to see what they are reporting in the files themselves – its’ kind of hard to say.

Cheers,
Greg

[Greg Booth]

Hi Shane,

I think there is some confusion :

the Calibrated{Q} DVCProHD Decode codec is a QuickTime Codec that decompresses DVCProHD video in QuickTime Movies – thus is does not use timecode or report it – just as any other quicktime codec. Since timecode is not used by a codec. The timecode is embedded already in the QuickTime Header as the TimeCode Track.

the Calibrated{Q} MXF Import – DOES use and report timecode of the MXF File. This quicktime plugin enables users to open up MXF files in QuickTime Player and create QT Reference Movies on the PC. But the user must still have the correct video codec installed to decompress the video. On the PC, this plugin is only used in QuickTime Player and not used in PPro (unlike on the Mac side where the plugin DOES work with FCP)

I sell a combo pack for Windows of both those plugins together but it seems based on his workflow description – he is using DVCProHD QuickTime movies in Premiere Pro that were generated on FCP thru Log and Transfer. If this is the case then only the Calibrated{Q} DVCProHD Decode codec is being used in PPro to decompress the DVCProHD video of the QuickTime Movies and PPro itself is reading and interpreting the timecode track of the quicktime file.

Cheers,
Greg