[Paul Dickin]

[lightning ad] “…importing the material with the anamorphic option in your (clip) settings switched off.”
Hi
Dohh! Blindingly simple lateral thinking….
The Preview window will be just like watching TVs for sale in the electrical superstores – every one scaling differently 🙂
Cheers

[Paul Dickin]

[us3productions] “Can anyone tell me how to get my videos to run as 16:9 quicktimes?”
Hi
With QuickTime Player Pro you just have to Shift-click drag the bottom right corner to get the movie size right (Cmd+J>Select Video Track>Visual Settings>Display Size gives you some precise figures).

Once it looks right, Save the movie, and it will henceforth play as you have adjusted it.

[Paul Dickin]

Hi
I wish the code magician of MPEG Streamclip could find an abandoned PCI-X/PCI-e capture card to write drivers for – his DC30+ software (G4 Macs only) was amazing…

[Paul Dickin]

[santellavision] “I would understand how a monitor card would possibly put up nicer images on the computer monitors, but not how it would effect the speed of processor calculations on an effect render?”
Hi
Broadly speaking you may be right.
However the advantage of a PCI-e rather than an AGP buss for the graphics card is that it is two-way, so the CPU can have direct fast-bandwidth access to calculations and data processing that the GPU has done to create the display. Thereby passing render calculations back to the CPU and memory to minimise overall render time.

Something like that – like you I only really understand analogue processes 😉

[Paul Dickin]

Hi
I was talking to a colleague who has this sort of problem last night – it had been suggested to him that he set up a new OS X User account, and try the FCP project from there.

The inference being that this might be an OS X + FCP problem, not just an FCP issue.

[Paul Dickin]

Hi
Having just read Jason P’s General Error Blues thread nearby I realise I forgot the ‘unmount all media drives, and try to open the dodgy project with everything offline’ step.’

[Paul Dickin]

Hi
Open a new blank project, then try to get the old corrupt project to open from the FCP File menu Open command.
If it does then Copy any Sequences that can be opened to a new Sequence in the new project.
Most likely a Sequence may not open or crash everything.

In which case repeat the procedure, but maybe you can Export a QT movie from that dodgy Sequence without opening it (or from part of it with Sequence In/Outs set). That would give you a record of your edit decisions, if you have to bring an old project up to date.

But! Somewhere in your movie or still assets you’ve probably got a corrupted QT file, or still image.
Working your way through all your captured movie with QT Player may show you which one it is. Ditto Photoshop for stills.

If you find anything dodgy trashing it may allow you to be able to open your corrupt project far enough for the Copy-into-New-Project strategy to work.

Last time it happened to me was in a QT movie made by using Macromedia Director to export its animation to QT. Reexporting/recompressing that dodgy movie in QT Player Pro recovered it for me.

[Paul Dickin]

Hi
https://www.virtualvtr.com/
Here’s some workflow details:
http://www.apple.com/uk/pro/profiles/tourdefrance/index2.html

[Paul Dickin]

Hi
This is old infromation, but is probably causing your problem:
Quote:
“The header for an AVI file includes a 32 bit AVI file length, imposing
a restriction of 4GB on the AVI file size.
VirtualDub can read and write AVI files with hierarchical, 64-bit
indexing specified in the OpenDML 1.02 standard and supported by
both ActiveMovie (Windows Media Player) and QuickTime. This means
you can capture and process files beyond the infamous 2-gigabyte
barrier, and work on video in one segment.”

So all current Windows AVI-creation software, like Windows NLE’s, can cope with long multi-segment AVIs.
Unfortuately QuickTime didn’t – and presumably doesn’t to this day 🙁

[Paul Dickin]

Hi
Also worth noting:
Pro Application Update 2007-01 updates the following components:
Apple ProRes 422:
Delivers improved encoding performance for Power Mac G5 computers.

Helium.framework:
Delivers improvements for SmoothCam. This update is required for customers using Motion 3.0 and Final Cut Pro 6.0.