-
Apple to hold special event at NAB
-
If some of the rumour sites are to be believed then it could be a BIG announcement!
-
[tarik m. sykes] “Where is the sign up @ on the apple site!!!!”
nothing there yet.
Walter Biscardi, Jr.
https://www.biscardicreative.com
HD Editorial & Animation for Food Network’s “Good Eats”
HD Editorial for “Assignment Earth”“I reject your reality and substitute my own!” – Adam Savage, Mythbusters
-
Yeah the rumor sights are on fire… 4K displays… Cell chips…. Ninjas…. Final Cut edits by reading your brainwaves….
All I really want is bigger system fonts in the motion tab and the timecode tabs…. and a running timecode window when you’re digitizing or laying off. Plus the obligatory fixing of Media Manager once and for all. Really integrate Cinema Tools please… X and Y resizing without getting into that messy Distort tab.
-
No problem. Still a good feature request though.
The Autosave works differently on Avid, as its not saving the Project, only copies of the bins (bins are discrete files on Avid) to the Attic.
It may be slightly faster under some circumstances, but it can be a pretty long interruption if you have a lot of bins open.
-
[Rennie] “I’m not sure about 8 processor configuration but this technology is nothing new. … It’s all about power and flow.”
[Steve Connor] “it could be a BIG announcement!”
Hi
If it is its probably too soon – a reality distortion-field moment 🙁
Because as I read about it, multiple processors impose a significant cache-coherence latency, which requires real-time software to be re-written to give a real-world speed-bump.
Here’s a random google article:
https://www.blachford.info/computer/articles/bigcrunch1And because FCP needs something of a ground-up re-write anyway, to overcome its underlying circa-1997 project file architecture 🙁
I wrote a post earlier today (which I now realise has gone on the end of a long-dead thread from September last year)
likening an FCP project’s database to an Inca quipu – string with knots in it.No amount of rope-spinning, and extra-fancy knotting, is going to make it into a robust relational database, so likely we won’t get unbreakable media management integrity or project asset manipulation reliability.
Atahualpa speaks – “get knotting”, and so we’ll all get knotted! LOL
-
FCP feels sluggish and bloated. Large projects take ages to open and save, and having them open causes instability and can occationally crash.
RT Effects are great with SD DV. That’s about it. Anything higher, uncompressed or HD, it’s very sluggish and render times are horrible with most effects. Multicam, color correction, working with high-res stills. It’s painful. And mixing formats is a nightmare of course.
So yeah, I welcome a ground-up rewrite of FCP very much.
-
[Danrnw] “All I want from a new FCP version is AutoSave in the background.
It’s one royal pain to have to wait for it when you are trying -
[Chi-Ho Lee] “FCP does autosave in the background! At least on my systems. The only exception is when your project is very big around 100mb. Then I can see the autosave box pops up but otherwise it is autosaving in the background.”
Funny, been using FCP since version 1.2.5 and have never used Autosave. My autosave is Apple+S since my left hand is there anyway on the keyboard. I hit that every few edits and have never had a problem so I leave Autosave off on all our systems.
Walter Biscardi, Jr.
https://www.biscardicreative.com
HD Editorial & Animation for Food Network’s “Good Eats”
HD Editorial for “Assignment Earth”“I reject your reality and substitute my own!” – Adam Savage, Mythbusters
-
I cannot tell you how often autosave has saved my butt. I am not so in the habit of APPLE-S as I should be. I get pretty caught up in the cut.
Shane
Littlefrog Post
http://www.lfhd.net -
yes avid does not do it in the background. but saving avid projects takes a fraction of the time that fcp takes. lets be realistic here.
Reply to this Discussion! Login or Sign Up