Brad Davis
Forum Replies Created
-
I’d like to see improvements on audio management. It’s better than the original release but still not correct.
-
With the audio updates…Have you discussed/overhauled audio routing management? Primarily, we bring in a multichannel QT’s. The audio gets reassigned in Premiere and exported to different than SMPTE. Also, have you addressed nesting 5.1 without to rename the sequence?
-
That has been one of the million dollar questions as of late. With all the hubub about Mountain Lion this morning one of my colleagues found a link (whether true or not remains to be seen) but any towers that predate 2007, won’t work with the new OS. Also, with the increased production turn around times for current Mac Pro towers usually indicates the refresh is coming or something new is on the horizon.
There appears to be a change in how they handle PR recently and I hope it continues. For business to take Apple seriously in a business environment they have to transparent to a degree before companies drop large sums of cash on infrastructure. Steve Jobs was well known for not working well with businesses but with the iPhone, they’ve had to change their tune some.
-
Get ready for the Mac Pro refresh…
https://www.mactrast.com/2012/02/mountain-lion-will-not-support-older-graphics-chips/
-
My guess…They want to keep the price of the App at $300 and if you want that level of functionality you can buy it from someone else and they pay the licensing fees. Hence why the Pro Tools app is $99
-
I doubt we will see OMF directly in FCPX ever again. In the article previously posted by the 7 Editors take a look at FCPX…OMF licensing is owned by AVID. This would drive up the price of the software. I honestly think the entire exercise of FCPX was to purge all the 3rd party licensing built into years of Final Cut Studio iterations so that Apple can own and manage the base software. However, I am sure, someone out there will develop an OMF solution through the App Store that will deal with the licensing separately (in addition to many of our transcoding/exporting quirks we deal with in this medium.
-
I’m kind of chuckling over this and didn’t realize it. Most if not all PR departments do that but Apple chose not to (until recently) to contain their public image. Maybe its a result of the fiasco or that Mr. Jobs isn’t around anymore and that perception needs to change for the business sector.
-
B
Not a fan of how the audio is handled in FCP X in general right now. Really cannot use it in my shop because of it.
-
Dave- How did Apple reorganize the PR department over this? Just curious because this is the first I’ve heard of it.
Thanks,
Brad
-
This announcement, release list and further announcements by 3rd party companies gave us insight on how FCPX is going to be developed as a product. FCPX is never going to be a “complete package” as FCP 7 was. Apple decided to strip the engine make it a basic editor, if you want the bells and whistles beyond what’s provided, your on your own. They’ll keep adding to it but it will never be like FCP 7. If you want backward compatibility to the legacy, there’s an App for that in 7toX. You want high end color grading, go purchase BMD DaVinci. If you want formal audio support to Pro Tools, there’s an App for that as well. It falls into their business model of making hardware and base applications and letting anyone develop and sell through their means (ie. The App store.) This also further my previous conclusion 8 months ago that the entire FCS was dumped because of legal and licensing of the previous software more than anything.