[Doug Metz]

Hi Jerry,

Here’s the boring background… bear with me. In addition to editing, I run quite a few corporate meetings which I support through PowerPoint or Keynote (depending on the client), typically with lots of linked video. For the last 2 years, I have been unable to use PowerPoint’s ‘Presenter Tools’ because my linked SD video files would drop frames during playback, and HD video would drop frames even if I was mirroring my displays. This is something that had worked perfectly with my old PowerBook and Office:2004, albeit with SD video only. When I upgraded to an Intel MacBook Pro, PowerPoint started dropping frames like mad when I used Presenter Tools. I searched the web and found nothing. Eventually, I chalked it up to Office:2004 being a buggy, non-Intel-native suite. Office:2008 was due for release shortly thereafter, so I decided to wait and see if it performed any better. When it came out and exhibited the same problem, I got irritated with Microsoft and started using Keynote (which I love, BTW) whenever possible. Unfortunately, clients being clients, I am still required on occasion to use PowerPoint. So I decided, with the release of Office:2011 (and the continuation of the problem), to audit my QuickTime components and plugins. I again searched the interwebs for answers and found nothing. Nobody else is experiencing this problem, so it must be me.

I checked my root Library QuickTime folder, and my System Library QuickTime folder (there’s nothing in my User Library QuickTime folder), and I found two components in the root library that were suspicious – an MPEG2 component and a ProRes 422 component. They were suspicious because I have newer versions of both of these – one in the root library (AppleProResCodec) and the other in the System library (MPEG2). So I moved the old ones to the trash and performed a deep system flush (PRAM zap, fsck, permissions repair, cache flush, vm refresh, etc.), which I do regularly – about once per quarter – and then tested PowerPoint again. IT WORKS! Oddly, I don’t use ProRes or MPEG2 compression in any of my video output for PPT. Usually, it’s H.264, but whatever. It was QuickTime that shot me in the foot, not Microsoft. Which is even more irritating. ;o)

I have finally fixed the problem, and the culprit was outdated QuickTime components. That is why I’m asking about these DVCProHD oddballs. If they’re needlessly stepping on each other and hobbling my rig, I want the old cruft gone.

Thanks for reading.

Doug

Doug Metz

Anode

[Doug Metz]

Thank you, Chris!

We’d tried adding noise, and that helped some, but I hadn’t considered the other bit. Genius!

Doug Metz

Anode

[Doug Metz]

Hey Chris,

I’ve tried at least 10 different variations on H.264 – some with Apple’s version, some with MainConcept, and even a couple of Sorenson’s.

The file was generated in AfterEffects CS5. It’s not something we want to add noise to, though the designer did try to add a bit of blur to the background to try to help smooth it out. I’m comparing the source clip and transcoded output in QuickTime 7, so I don’t suspect the media player. The problem wouldn’t be so bad if it didn’t cover 2/3 of the image. We’ll be projecting on a 20′ screen, so I really want it to look as close to perfect as possible.

I’m going to look at the source again and shift the gamma a bit to see if it’s a problem that we can fix in AE.

Thanks,

Doug Metz

Anode

[Doug Metz]

Also be sure to check that your sequence settings are set to progressive, square pixels.

Doug Metz

Anode

[Doug Metz]

As you have discovered, FCS3 isn’t compatible with PowerPC-based Macs (not entirely surprising, since all of their products have been Intel-based for the last 5 years). Unfortunately, there is no way to run FinalCut Studio 3 on your older hardware.

Since you can’t return the software, your alternatives are:
1. Sell your FCS3 software, and continue using what you’ve got, or
2. Sell your G5 and get a new (or new-ish) Intel Mac.

Doug Metz

Anode

[Doug Metz]

Are you compressing it for edit? Delivery to a client/friend/relative? Archive? It would be helpful to know what you’re compressing it for in order to make a good recommendation.

Doug Metz

Anode

[Doug Metz]

Well, that’s the rub, Arnie.

When I remove the duplicate frames from the 60fps source, I see perfect 3:2 pulldown on the resulting output. The problem comes when I try to remove the pulldown to get to 23.976.

I’m seeing one in four frames as interlaced on the 23.976 output (see above post).

So I’m trying some other things (field order change, primarily) to see if that changes things for the better.

Any other ideas?

Thanks guys!

Doug Metz

Anode

[Doug Metz]

That seems to have the desired result – exporting directly from QuickTime at half the frame rate does, too.

Now to figure out why I can’t cleanly remove the pulldown… every fourth frame is interlaced on my 23.976 output – be it from Compressor, JES Deinterlacer, or Cinema Tools. Actually, Cinema Tools spits out a file that is exactly opposite – every fourth frame is progressive, all else is interlaced.

Ugh.

Doug Metz

Anode

[Doug Metz]

Quick question:

I am wondering if this update is compatible with FCP 6.0.6 / OS 10.5.8. I know the release notes say FCS 3 – but the release notes for the ioHD 7.1 update said the same thing, yet it is backward compatible.

I’ll be upgrading next quarter to 10.6.x and FCS3 anyway, but was wondering about this update in the mean time.

Thanks,
Doug

Doug Metz

Anode

[Doug Metz]

I avoided updating because I’m still on Leopard w/FCS 2, and all of the ioHD release notes say FCP 7.0.1 or later… Ugh.

Updating now.