Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Adobe CS5 Mercury Engine.

I am mainly a Premiere user, but I don't think that speed will be enough to kill a program like FC.
Apple will definitely make its move, just like Adobe did with Premiere (unless they intend to leave the pro video market for good).
As Cuneyt mentioned, there are other things to be considered besides performance.

The new technology will of course make many FC users begin using Premiere, and some will even switch..

One thing is sure, IMO. If Adobe and Apple continue in the same way,
FC and Premiere will switch their places in the pro market, and Premiere CS6 (or CS7),
supported by AE and PS, will be the NLE of choice..

So no death.. just some injuries.. ;)
 
Is it possible to do fullrez debayer in different qualitys? I wonder if the 4 redstreams they got was fulldebayer with maximum quality? I mean if it would be as good choiche as a RED Rocket™ if you dont have to output 4k just yet. Redrocket only works with redcinex yet. Right?
 
This is assuming Apple won't use OpenCL / 64bit in their next generation Final Cut (and looking at Snow Leopard, they are obviously ensuring the infrastructure is there).

And to stop people buying very expensive silicon, the quadro cards on Mac are far from optimised (see the pretty damning Ars Technica benchmarks):

http://arstechnica.com/apple/news/2009/12/a-second-look-at-the-nvidia-quadro-fx-4800-mac-edition.ars

Apple *do* need a kick, they've sat on a horrid mess of old code (still carbon), wonky UI inconsistency and poor multi-core and hardware optimisation. But if the rumours of the next final cut suite are true, they are going to be in a stronger position when that arrives...
 
couple of Q`s before announcing FCPs death:
can it read Timecode?
how does it behave on long timelines?
proper EDL/XML export?
autosync BWF files?
Datamanagement?

My questions exactly! The day this kind of stuff gets solved I'm over FCP for good.
 
Whenever I try to watch that video demonstration I start counting the "smooth"s after 30 sec... annoying!
 
Cs5 is definetly promising at 64 bit, but check this out Apples flagship music production software Logic pro was 32 bit at version 9.0 but version 9.1 is full 64 bit. I don't think apple is sleeping. Now the question is will they integrate sound track pro, color, motion and cinema tools into fcp? we wait to see
 
couple of Q`s before announcing FCPs death:
can it read Timecode?
how does it behave on long timelines?
proper EDL/XML export?
autosync BWF files?
Datamanagement?

So Kaya - I'm pretty sure that they have integrated all of these into the new CS5 package...the performance benchmarks with the Mercury Engine knocked the ball out of the park...are you ready for the FCP funeral.

I'm giving FCP one last gasp...but they are going to have to knock my socks off to prevent me from switching. Adobe killed it at NAB - just killed it. The new roto tool alone is worth the price of the whole box...
 
The Mercury engine is very smart and intelligent programming harnessing the power of the CPU and vast memory architecture. This is real computing muscle the better built your mother board's bus system and i/o architecture the better the performance. FCP will be just as powerful if its rebuilt to harness snow leopard's multi-core and 64bit memory architecture capabilities, but you will still be limited to Log and Transfer, doubling you media, Quicktime crazyness, etc. we live to see.
 
The CS5 engine is a good example of proper multiprocessor programming. It scales very well to use all those CPU cores in your system for increased performance. If only other software companies would give it a try. I'm impressed that Adobe is first to the watering hole with this one in the NLE world. Can't wait until they get the same sort of scalability incorporated in AE and across other apps and even into other aspects of Premiere. People keep yammering on about GPU acceleration, but it's not the GPU that's doing most of the work here. In fact, they demoed playback on Mercury at the RED Event for a few minutes with the GPU acceleration shut off. GPU is used for additional color transforms and FX acceleration, the actual playback is all CPU-based. Very nicely done.

I'm curious to know how well the renderer in the updated AME performs. I asked the Adobe guys at the RED Event and they were really dodgy in their response. It looks better than with CS4 and definitely seems to be more stable, but I don't think they have made it fully scalable yet on the same level as the Mercury engine.
 
Cs5 is definetly promising at 64 bit, but check this out Apples flagship music production software Logic pro was 32 bit at version 9.0 but version 9.1 is full 64 bit. I don't think apple is sleeping. Now the question is will they integrate sound track pro, color, motion and cinema tools into fcp? we wait to see

SIDE NOTE: As many Apple users are blinded by marketing, Cakewalk SONAR 6 released in 2007 was a 64-bit application (now on version 8.5.2). In addition, Steinberg Cubase has also been 64-bit for years. Also Photoshop CS4 is 64-bit on Windows.

So why would I want to checkout Logic? Because they just finally got it to 64-bit? Sorry but I've lost all respect for Apple when they released their iPhone OS 4.0 Terms of Service which only allows developers to use their machine, their sdk, their compiler, submit to their app store, etc.

Its kinda like if I was to build my house and I went into Home Depot to buy their lumber but they refused to sell it to me because I was using tools bought from Home Hardware or some other competitor.
 
SIDE NOTE: As many Apple users are blinded by marketing, Cakewalk SONAR 6 released in 2007 was a 64-bit application (now on version 8.5.2). In addition, Steinberg Cubase has also been 64-bit for years. Also Photoshop CS4 is 64-bit on Windows.

Yep. Apple is just slow when it comes to their pro apps division. I'm not too excited about any future development there. It will have to be truly amazing in order to contend with what Adobe and Avid are doing. Logic Pro is nothing special in the audio world, but all the Mac fanboys sure like it. It was the last of the major software in its market to make the 64bit transition.

Sorry but I've lost all respect for Apple when they released their iPhone OS 4.0 Terms of Service which only allows developers to use their machine, their sdk, their compiler, submit to their app store, etc.

This is a total hijack of this thread. But as for Apple's developer tools, it makes perfect sense. No one complains about most other platforms that have approved developer tools. Apple's are still rather open, it's still using GNU GPP for the compiler, which is open source. Code can be written in both Objective C and C++, both are open languages. Most Apple developers think they are locked into ObjC with Cocoa, but that isn't the case, there's full C++ language support there if they know what they're doing. Not only that, but the tools are free. And any decent programmer with a background in OOP, Java, C/C++ should be able to download the freely available SDK and be making functional iPhone/iPad apps almost instantly. IMO, I fail to see where a cross compiler could even be justified here given that there would be no practical ability for keeping current with iPhone OS changes or specific API calls -- something cross compilers just suck at.

All Apple did was say they would not approve apps built by cross-compilers, nor would they accept apps that are script-driven within a host application, which is what FLASH Builder apps are. Which totally makes sense, from multi-tasking and performance perspective, Adobe isn't even that pissed off over it, it's the Flash userbase that is. But I've always been of the opinion that if you make widgets that are scripted in FLASH and you call yourself an "application developer", you need to rethink yourself a bit. Adobe's CS5 FLASH Builder isn't a true cross-compiler. It is a self-contained FLASH player and package delivery system.

:jacked:
 
Back
Top