[Paul Dickin]

Hi
Here’s another CoreMelt info page:
https://forums.dvdoctor.net/showthread.php?t=45234

[Paul Dickin]

Hi
With older versions of FCP clicking/double-clicking on the FCP dock icon brought it back to life.

[Paul Dickin]

Hi
CatDV http://www.squarebox.co.uk

[Paul Dickin]

Hi
Conform your QT movie’s frame rate using Cinema Tools to the timeline frame-rate.
The only time I’ve had rendering General Error problems is with dodgy frame-rate source clips.

[Paul Dickin]

Hi
When using MPEG Streamclip to Export to QuickTime to get a FCP-friendly file transcode make sure you set the Frame Rate box with your timeline frame rate (this is not set by default).
Set the Frame Rate options to Best as well.

[Paul Dickin]

Hi
Having the source clips and the destination folder on different drives/different SATA channels helps.

[Paul Dickin]

[Peter Wiggins] “Qucktime will still exist with QuicktimeX, it is designed for things like the iphone. “
Hi
I get the feeling its the QuickTime file format that’s the millstone that drags down development 🙁

It seems to me that QT’s file structure is like the old 3/4″ tape paradigm – a timecode track that is still as basic as the tape counter (start time + offset),
and metadata that’s about a sophisticated as the writing on the box label.
OK there are ‘control track’ like data tracks as well, and a lot more sound channels these days…

But no VITC.
You can’t give a FCP project or FCServer database a Tape name and a Timecode and expect it to recognise the shot in any Capture of footage from that tape. FCP/FCServer have to have a Clip Name because QT can’t recognise the off-tape footage in a global context.

That means that FCP’s Media Management is currently eternally mangled by being restricted to the U-Matic tape library paradigm.

Until QT is given a wider VITC-like managed databased structure within which to exist – which can fully comprehend MXF/etc advanced metadata in any form.

At least the iPhone’s need for GPS metadata may give us cause for real hope…

[Paul Dickin]

[Steve Braker] “I’m sorry, Paul. I had missed something in your post. I can’t see anything in Apple sales lit about Server handling capture and logging. If it’s there it’s worth more attention….
“
Hi
Apparently that will be a Telestream(?) add-on – there’s an ‘open’ API to FCServer to allow developers to produce add-on s/w or black boxes….

[Paul Dickin]

[Steve Braker] “Among the attractions is that the metadata stays with the media (inside the file, wow!) and that (to us) complicated and expensive server setups for logging aren’t necessary. “
Hi
The currently-on-the-road World Tour demo of Final Cut Server shows FCP 6.0.3 (+QT 7.4.5 presumably as a vital ingredient) taking in logging notes etc with Log&Capture/Log&Transfer and adding the metadata into the QT file, not into the FCP project – they don’t Save the FCP project – but FCServer subsequently can see the log notes within the QT files.

So something along these lines has just happened within the Apple scheme of things
(cue drumroll/fanfare!!!).

Obviously I guess it won’t be ‘compatible’ with anyone else’s metadata (MXF etc), by hey…

And I suppose only FCP or FCServer can reveal the riches within, unless the likes of the CatDV guys are allowed to get stuck in.

[Paul Dickin]

Hi
Do a google search on Intel’s Nehalem processor range – reportedly a ‘big leap’ forward in processing power.
The consensus seems to be that there will be new Mac Pros with this by early next year.
https://www.tgdaily.com/content/view/36726/135/ 😉 😉