Tapio Haaja
Forum Replies Created
-
I guess I’m also still hoping that Apple will fix bugs and bring the needed features in next update of FCPX… But also this the best. most passionate and most professional forum I’ve found in Interwebs where editors talk about future of editing.
Best
Tapio HaajaOn-Air Promotion Producer
https://avseikkailuja.blogspot.com/ -
Sorry, but that’s year old stuff sneak peaking ‘upcoming’ CS5.5 that came out last April 🙂
Best
Tapio HaajaOn-Air Promotion Producer
https://avseikkailuja.blogspot.com/ -
This is also one feature I’d like to see in CS6.
Best
Tapio HaajaOn-Air Promotion Producer
https://avseikkailuja.blogspot.com/ -
I really hope Adobe some day releases their own high quality cross platform DI codec. In the meantime I hope they’ve licensed Prores from Apple for CS6 so they can build native support for it and bypass old Quicktime. I think licensing for Mac Premiere shouldn’t be an issue because Avid already introduced native Prores support in MC6 for Mac.
Another thing is I/O performance and stability. At the moment performance and stability with AJA, Blackmagic and Matrox is very poor.
Actually If Adobe introduces DI codec or native Prores support and I/O works as it should I’m ready to jump to Premiere.
Really waiting for CS6.
Best
Tapio HaajaOn-Air Promotion Producer
https://avseikkailuja.blogspot.com/ -
Actually one of my biggest hope for Premiere CS6 is that Adobe implements full ProRes support natively like Avid did with MC6. That way Premiere wouldn’t need Quicktime for decoding and propably we wouldn’t have these strange problems.
Best
Tapio HaajaOn-Air Promotion Producer
https://avseikkailuja.blogspot.com/ -
I’ve this same problem. Prores and also some other codecs look jagged on Premiere Pro program monitor but exports fine. And also jagged edges usually goes away if I add some filter, change field interpolation etc. So I guess when Adobe Premiere Pro’engine ‘kicks in’ and doesn’t just show codec.
We had discussion about this same problem couple months ago:
https://forums.creativecow.net/thread/3/919303#919427Best
Tapio HaajaOn-Air Promotion Producer
https://avseikkailuja.blogspot.com/ -
I think only big difference to buy now or later would be if Apple starts using Nvidia CUDA Compatible Graphic Cards. There are some rumours flying next MacPro will have Nvidia CUDA Compatible Graphic Card as default so maybe high end iMac could also have one? Just wild guess. I have absolutely no information. Anyway this would be big thing for at least people using Adobe Premiere, Davinci Resolve and some other softwares.
Best
Tapio HaajaOn-Air Promotion Producer
https://avseikkailuja.blogspot.com/ -
[Walter Soyka] “As the resident graphics guy, I’d love to see dynamic link expanded to include something like FCPX/M5’s rigging/effects-publishing integration.
Being able to build titles, effects, and transitions in AE for use in Premiere Pro — without requiring the editor to actually work in AE — could be really cool.
“Yeah I second this. This would be killer feature! We see already how FCPX gains quickly great new effects, transitions etc. because FCPX/Motion 5 collaboration.
Best
Tapio HaajaOn-Air Promotion Producer
https://avseikkailuja.blogspot.com/ -
Who cares? If you’re editing with FCS why should you upgrade to Mountain Lion? Actually why should you update even to Lion? I think all ‘pro’ softwares still work in Snow Leopard. Even Avid MC6 works in Snow Leopard although Lion is recommended. So no hurry 🙂
Best
Tapio HaajaOn-Air Promotion Producer
https://avseikkailuja.blogspot.com/ -
There are still some memory and CPU bugs in FCPX. Last week one day I wasn’t doing anything and my MacPro almost halted completely. I looked activity monitor and all 8 cores were used 100% and FCPX wasn’t processing anything. I could barely move my mouse pointer. Restarted FCPX and everything was running okay once again.
But yeah you should give feedback to Apple so they know they must spend some serious time with these issues.
Best
Tapio HaajaOn-Air Promotion Producer
https://avseikkailuja.blogspot.com/