[Paul Dickin]

[Al Bergstein] “…briefing 3rd party developers at the WWDC on how to program to this new app…”
Hi
Surely what Apple is doing at WWDC is giving developers a thorough grounding in the new iOS5/10.7 APIs, so that they understand enough to take ANY individual app SDK and turn out functional bug-free code.
If you don’t understand the big-picture basics then there’s no chance of the specifics being done right. 😉

Further to that it seems to me (=uneducated guess) that FCP X/Motion X/etc are at their fundamental level going to turn out to be GUI/toolsets which for the most part utilise the underlying OS’s built in routines as the application ‘engine’ – hugely powerful and common across ALL GUI/apps, and built on a common OS CoreData metadata-database – so if you don’t understand the OS you don’t know nuttin’…
(This is a paradigm shift from the way that things have been done in the past.)

Which is why the forward development of FCS X has been inherently waiting for the new cool super-efficient/unbloated codebase of iOS to percolate upwards into Mac OS X. 🙂

(fan)
Which maybe will leave Avid and Adobe and their legacy cobbling as yesterday’s (neanderthal) men?
(/fan)
Hehe

[Paul Dickin]

Hi
Final Cut Pro v3 (dating from about 2002/30)?
There were two versions, one for OS 9 and v 3.0.3 or 3.0.4 that was on a different disc for OS X.

At that time I seem to remember the Apple original install disk had to be present for installation to be permitted. Do you have the original Apple-branded OS X install disk?

I seem to remember that a previous-version serial number was needed for a full retail upgrade.

All this is from memory so I may be a bit rusty remembering what exactly we had to do all those years ago – part of the reason FCP 4 was introduced with just a simple S/N install procedure was that lots of people had difficulties with the complexity of the FCP 3 install security.

[Paul Dickin]

Hi
I’ve just done an upgrade to FCS 3/FCP 7 from FCS1 (FCP 5.1.4, using the S/N that came with FCP 5.0) and it worked fine (with UK-bought software).
Changing from a G5 to a new Mac Pro.

[Paul Dickin]

Hi
LT? Log & Transfer – isn’t that what you are doing, sort of, but different….

[Paul Dickin]

[David Roth Weiss] “Just when we thought…”

Hi
Maybe…
Quote:
Unfortunately the OWC report propagated by several news channels is just wrong. Several people, me included, have successfully proven that it is possible to add an SSD or to replace / upgrade the iMac’s HDD.
https://forums.macrumors.com/showthread.php?t=1152520#2

[Paul Dickin]

[Craig Seeman] “…Premiere will have disadvantages to FCPX on iMac”
[Dennis Radeke] “any other reasons or thoughts about why FCP X might be faster.”

Because PPro – at least at first, until a rewrite – will still be stuck with the old 32-bit QuickTime legacy way of doing things?
(That’s a question, not a statement.)

[Paul Dickin]

Hi
YouTube re-encodes your movie altering any QT metadata, so the only way to get YT viewers to visit your web site is:
a) subtitle your movie with the URL, and add it as an end caption.
b) write the URL in the description of your movie that you can add to the YT page.

[Paul Dickin]

Hi
No. Not again. Not now, anyway.

This quote from that long thread sums it up IMO. 😉
“…now would probably be a good time to remember that what Jobs is creating here isn’t just “magical devices”… he’s embarked on defining the “Post PC Era”…

It’ll be interesting to see where all this leads, but my take on it is that it might not even feel much like a “platform switch” by the time we arrive there…”

[Paul Dickin]

Hi
QuickTime, and video creation/screen-capture programs based on QT, can have frames of variable duration (= variable frame rate). This is incompatible with FCP’s need for a stable fixed frame rate.

The best solution I’ve found is to use Cinema Tools to conform such video files to a proper frame rate before transcoding for import into FCP.

If using MPEG Streamclip always set an Export frame rate, never let it use the current frame rate.

The biggest change with FCP X appears to be the EOL’ing of QuickTime and all its foibles in favour of a much more robust metadata-database based successor AVFoundation.

[Paul Dickin]

Hi
The QuickTime Pro player has an export facility inbuilt to create something called a QuickTime Media Link.

This is a .qtl file that when embedded on a web page acts as a pointer to a .mov video file (and starts it playing). It can also associate metadata onto the video file it plays – including a URL to link to if the video player is clicked.

Disclaimer: This has been in QT for years, and older QT technology seems to be being superceeded these days.

Page 222/223 of this pdf has an explanation of the dialogue box you get when you use this Export format:
https://imedia.tamu.edu/support/documentation/quicktime/whatsnewinquicktime6.pdf/at_download/file