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 :)

Final Cut Pro X Released

I have to wonder if The Foundry saw this coming and that their master plan with STORM is to ultimately make it a full featured NLE. With how close they seem to be with RED we may see STORM turn into a dream come true for a lot of us...

I really hope I am right.
yep!! my last hope :/
 
Obviously, you're so blinded by your own believes, that you still not getting it. THERE IS NO SUPPORT FOR BAYERED MATERIAL AT ALL!!! It's not just RED...
As to why Apple not communicating the FCPx roadmap, when did they ever do that?

I don't have any beliefs, and I am not blinded about anything. It is you who believes something and I am simply asking questions. That said, everything you are saying makes very little sense to me; I better stay out of this and see how things unfold. I just want a working platform - as simple as that. And judging by the comments, FCP X is not it, today.

As it is today, this is how I see it - FCP X does not support R3D. Every other major NLE does. I will be back when FCP X does support R3D.
 
I'm playing with it now, for pure entertainment. It's bat sh*t crazy!
 
Keep's crashing on me at the office and now at home. Anybody else having problems?
 
its funny how people keep saying "Apple will get there, they will do this and they will catch up"... myself included, I've used Apple computers for almost 20 years and I've always said they bring out this and that and cater to my professional needs but to be honest they haven't and its clear they don't care too either.

If you want a professional tool, made for professionals then its clear Apple isn't the choice.
Apple stole market share from Avid but Avid was there before FCP and they are still here making a professional tool from release to release, unlike Apple.

I'm sorry but my bet is on Avid. Apple just have had too much of my time waiting for a professional tool
 
glad we're having Adobe listening to us. sorry apple....sounds ridiculous to me you're not supporting r3d's from the 1st version when we thought you were one of the first going to support it. you've lost once again all my trust.
 
Look at the iPhone, in 2007 it was an overly simplified $600 piece of tech, with just a clock, calculator and sms app. Now it is massive development platform with tons of apps. At the beginning of iPhone they even had those ridiculous "web apps" that they marketed before they created a native SDK

Let's hope it's something like this. Would be nice if someone from Red could confirm/deny that they know about this and are working on it.
 
Has anyone noticed total silence from Red, concerning the absence of R3D support in FCPx? Wouldn't Red already made some noise about it? Me thinks, that it could possibly be up to Red to provide this functionality. Can anyone in Red comment on this?
Funny you mentioned that, eight hours ago Graeme tipped me that the Canada App store was working. I was having probs buying this app (morning) :)
 
FCPX doesn't even support FCP.

Seriously, you can import an iMovie project but NOT a FCP project?
Isnt this due to the same code? The folks that worked on iMovie are the same on FCPX from my understanding.
 
Although, I have to say, Lion on my Macbook Pro, so far, runs flawlessly. Except iTunes:-)

How, how do you have this now? It's not released until next month!!! :)
 
Isnt this due to the same code? The folks that worked on iMovie are the same on FCPX from my understanding.

Quite possible, but I would think this capability would have been a priority so professional users could migrate projects into the new software, even if that meant some sort of intermediate step to do so.
 
...

If you want a professional tool, made for professionals then its clear Apple isn't the choice.
...

l

I will admit to being a bit disappointed that RED support is not built in yet. And I know everyone here has their own opinion and their own context for it, and that's great.

But, I have to say that a comment like this - in all the smugness of "I know everything..." is the kind of thing that just plain annoys me. I happen to think FCPX has a lot to offer and a lot of good features for streamlining work. And, there are a LOT of thing that I (and YOU), don't know about it yet - since it's been out for all of what, ten hours? And, as some are saying, there is great potential for it to grow from the 1.0 rewrite that it is. I am not making excuses for Apple. Like I said, I find there are some disappointments, too. But to say this is just plain insulting to everyone who sees it differently than you do.

FCP-X may not meet your needs. If not, you should definitely not buy it. But, please, to pretend to speak for all "pros" that it can't meet, or even improve on meeting, their needs. It's just plain... unprofessional. :furious3:
 
The question of linear or logarithmic doesn't arise with a single pixel with a single value (16 bits long, in this case).

Yes it does - what that stored value is in relation to the voltage output by the sensor's photosite is what it's all about. In principle: with lin, twice the voltage, twice the value. With log, the change in value as voltage doubles is always the same.

So, with each one stop increase of luminosity a lin pixel could be i.e. 16, 32, 64, 128, 256, 512 in value (doubling each time), while with the same input, a log pixel could be 16, 32, 48, 64, 80 (increasing by 16 each time).

Sensors are inherently linear (as said, they just count photons), so as far as i know, the raw data they output is also linear.
 

You can install it on same partition, there are just some additional steps you have to do to make that work. It's in that article if anyone needs to install that way.

If you are on a Mac Pro you should do a clean install onto a fresh drive, and run FCPx on that. That way you will find it easier to troubleshoot as you'll have the minimum when it comes to potential conflicts.
 
Has anyone noticed total silence from Red, concerning the absence of R3D support in FCPx? Wouldn't Red already made some noise about it? Me thinks, that it could possibly be up to Red to provide this functionality. Can anyone in Red comment on this?

I asked Graeme about this on twitter after he posted a comment about how FCPX Projects were stored (SQLite Databases). He made it very clear that it's in Apple's court and something we should bug Apple about not RED (again, apologies for bugging you Graeme). This is both native R3D support and any REDCINE-X/FCPX communication.
 
Back
Top