[Andy Mees]

If the target systems (either Mac or PC) all have the latest QuickTime version installed on them (or can be upgraded to the latest) then they will all be able to read a ProRes copy of your edited spot. They won’t have to download anything else as ProRes decode is already a part of the latest QuickTme.

There is also the option of purchasing and installing the necessary decode codecs on these other systems so that you can distribute and they may read a native XDCAM EX quicktime. For example: https://www.calibratedsoftware.com/QXD.asp

[Andy Mees]

heeee . nice tease Bouke.

[Andy Mees]

and go lurk on the pro-apps-dev list … plenty of knowledge and code gets shared there regularly

https://lists.apple.com/mailman/listinfo/pro-apps-dev

[Andy Mees]

I don’t have access to interlaced monitoring … but the broadcaster requires interlaced video.

Any suggestions welcome.

Get access to an interlaced monitor. Seriously Wayne, in one sentence you state you don’t have an interlaced monitoring solution, in another you state your broadcaster requires interlaced delivery … what planet do you live on? It may sound harsh but its meant as a reality check, not as a telling off.

[Andy Mees]

well over here in rose colour spectacled PAL land I rarely deal with issues of 24p/60i, and when I do I just pump it through our Terannex …

basically what you need to to is to add 3:2 pulldown but as I am wholly unfamiliar with that process then I’m probably not going to be the best person to advise you on it.

that said, one approach amy be to simply output your cut to tape via your Kona/Blackmagic/Matrox I/O device, and have said device add the pulldown on output. you can then recapture that 60i dub and output for DVD as required.

failing that, I’d be looking at a simple Export > QuickTime Movie using Current Settings and then take that into Compressor and do a Best Quality DVD preset encode

hold your horses for a bit though Patrick, there are lots of heads up there who live and breathe this stuff and will gladly steer you right

best
Andy

[Andy Mees]

I’m also very surprised why FCS 3 was release just before Leopard Snow that will have proper 64bit application support. FCS is a prime candidate for 64bit support — why not wait a few months and release with Snow?

There’s no logic to this argument Rob. Whether its was released now or later it doesn’t change the release itself. It is what it is … and at present that “is” is a 32 bit non cocoa native application. If they had released it after Snow Leopard was released would you have been any happier? or would you have been even more annoyed that it wasn’t more SL native? I’m betting the latter, and as such the decision to release earlier was well advised.

Sorry for the negative post, but I really feel cheated with this upgrade

So don’t buy it Rob! For goodness sakes, upgrades are not obligatory. If there is something in an upgrade that one likes, that would make a positive impact on ones work and workflow and offer an increase in productivity ie something that makes an upgrade worth the price then one goes ahead and upgrades. But don’t upgrade just because. We all might be a bit disappointed overall by the latest FCS release, but no one is being “cheated”. FCS2 works every bit as well as it did before the upgrade was released.

On a side issue, if you are doing a lot of H264 compression, you might want to consider investing the FCS upgrade price in an H264 encoding accelerator. There are a couple on the market right now and they may well offer you a significantly greater advantage than FCS (2009). have a look at the Matrox CompressHD and the Elgato Turbo .264 HD. The former is more expensive but seems to offer a slight speed/quality advantage, the latter is a very strong contender tho and is very reasonably priced.

Best
Andy

[Andy Mees]

24 (fps) x 4 minutes and 4 seconds (244 seconds) = 5856 frames
29.97 (frames) x 3 minutes and 16 seconds (196 seconds) = 5874 frames

too close to be a coincidence Patrick, the issue is the difference between your source and target frame rate

[Andy Mees]

Hey Jeff

>This was more than just trashing FCP prefs. I took out all the preference files from that folder and relaunched FCP again

For your future reference, that process is exactly what it referred to as “trashing your preferences” … there are number of helper apps around, both free and commercial, that make the process a breeze, plus add a lot of extra features (like backup and restore). My favorite is the excellent (and free) Preference Manager from Jon Chappell of Digital Rebellion:
https://www.digitalrebellion.com/pref_man.htm

Hope it helps
Andy

[Andy Mees]

>I go through all the steps, and click and it starts to covert, and when it’s done, I open the file and WHAMM there is my logo, not even in the IN&Out points, and the video did not even finish It’s 00:04:04:00 and it only went to 00:03:13:23 – ANY IDEAS?

Patrick, your post is a little difficult to decipher … one of those “you had to be there” situations!
As far as I can figure out, you are saying that you have marked a section within your ( DVCPRO HD 720p24 ?) sequence and are then using FCP 7’s Export > Quicktime Movie function to export that section as a ProRes 422 HQ (SD Anamorphic) movie … is that a correct summary? And that the exported file is not the marked section as you would have expected, but instead an export of the logo only? or of the timeline from the sequence start rather than the marked In point? and that the duration of the exported flle is less than the marked duration? Can you clarify if this is indeed a correct summary, and can you detail exactly what “all the steps” are, so the folks here can see if there are any obvious issues in the process?
Cheers
Andy

[Andy Mees]

the old PDF manuals are gone, replaced by html versions of the manuals … but whilst they are a re far cry from the perfectly good pdf manuals we had before you shouldn’t be having performance issues with them and you certainly shouldn’t need internet access

you can find the local FCP manual by right clicking the FCP application icon and choosing Show Package Contents from the context menu, then navigating to Contents/Resources/English.lproj/Resources/finalcutpro_help/usermanual … double click the file named index.html to open it in a browser window