[Charlie Austin]

[Peter Garaway] “Does this happen every time Premiere is open or are there any particular steps to make it happen?”

Hey Peter.. I do have Cuda installed and up to date. There doesn’t seem to be anything in particular that triggers it, but it does happen pretty regularly. Sometimes just hitting play clears it up for a while, but once it spreads beyond the source/record windows (to desktop, other apps etc.) a reboot is all that fixes it. Never saw it before installing Yosemite. Nothing unusual shows up in the logs anywhere and, as i said, hardware tests all check out fine. It only happens when I run Pr. Any ideas where i might look for clues? I’ll keep trying to figure out what’s up. Thanks!

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[James Ewart] “Or maybe nobody would have even bothered looking at FCPX and it would not have got off the ground at all.”

Actually, I think that’s probably why they did it the way they did to some extent. Perhaps they went a bit too far by stopping FCS sales right away though. Ah well… hindsight and all that…

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[James Culbertson] ” I get an error -50 some of the time.”

Well, For what it’s worth, here’s what that is…

paramErr = -50, /*error in user parameter list*/

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Oliver Peters] “The same is true of manufacturers. If you are Avid or Adobe, you get a pretty good hardware roadmap for development out of HP and Dell. Not so much (if any) from Apple.”

Agreed, and Apple has clearly ceded the “big Iron” server hardware market to others. But I’m not sure the hardware roadmap, other than connectivity (t-bolt x, USBx, etc) really matters much any more, at least in the market Apple is still playing in. What Apple does give out is a pretty comprehensive OS roadmap. It’s not a long roadmap, but long enough so that SW vendors can adapt. Seems like they EOL stuff and it takes about 3 years for it to disappear. Which gives FCP 7 about another year. 😉

I’m just idly speculating though… I do see your point.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Dave Gage] “whereas on the news, the strobe is merely on the subject and the background remains the same. “

Maybe because the BG is keyed in, so there are 2 sources. Strobe the talent, not the key.?

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Oliver Peters] “There’s another factor and that’s Apple’s hardware side. Growing with Apple hardware means accepting internal hardware changes in your sop that may or may not fit into the plans of many facilities. The changes with Xserve RAID, Xserve and the Mac Pro have turned off many people. Several customers of mine have or are considering changing to the PC platform, because a new HP or Dell better fits into their shop (replacing Mac Pro towers) than do iMacs or Mac Pro “tubes”.”

I hesitate to use this term, but I think that’s a crossroad that “legacy” companies will have. Anyone setting up a new shop who wants to use Apple hardware can use an off the shelf RAID/SAN etc. and plug it in with one cable.

And I really think they’re doing the right thing with hardware. It’s a hell of a lot easier to set up and maintain shared storage/servers than it was even 5 years ago. We had an Xserve/X RAID setup for years. It was expensive. We have the same functionality with a Mac Mini/OS X Server and some pegasus boxes. For about half the price or less. Our Fibrenetix RAID still works just fine too.

I get it, especially for facilities that need “big iron”. But the need for that is changing.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Andrew Kimery] ” When Apple launched X not only were they launching a new NLE they were hitting the reset button on the inroads FCP Legend had made.”

Agree, and I think even Apple would agree the launch of X could have been “tempered’ a bit. Like keeping 7 on sale for a while…

[Andrew Kimery] “I think within the next 3 years X will start becoming more viable in major US markets for long form work. You won’t be able to get the best paying gigs with it, but you’ll consistently be able to get decent paying gigs with it. “

Not sure about the timeline or pay grade, but that seems plausible. It could happen faster if someone “big” is seen as embracing X…

[Andrew Kimery] ” what does Apple do X becomes 10, 11, 12 years old? Will Apple blow it up again? Does the code base have longer legs than the code base for 7?”

I’m speculating here as well, but FCP 7 had tons of pre-OS X code in it. It’s kind of a miracle it still runs. FCP-X features seem to be being rolled out/updated as the underlying OS does, as a lot of it’s functionality is really dependent on OS level code/frameworks. In that sense i think it’s more likely that it’ll still be viable for a while.

I mean, Apple could decide to just sell phones, but I don’t see that happening. Even when I don my tinfoil hat. 😉

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Herb Sevush] “That’s the “heard” mentality, and is the result of the way the rollout was handled.”

Nah, at this point it’s the “herd” mentality, at least here. This still comes from people who absolutely know it isn’t true. They’re just resistant to learning how to use X. And until a major studio, or vendor, or competitor “validates” it, it’ll keep happening. FCP 1 got the same reaction in my niche. But since it had no precedent, the “it’s no good” vibe faded faster. It also had the “not too different” thing going for it, which helped. I can tell you from experience that people didn’t start switching from Avid until they heard other “peer” companies were doing so. Someone needed to be https://www.apple.com/hotnews/articles/2001/04/trailerpark/“>first.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Andrew Kimery] ” The biggest reasons are that PPro can most easily slip into their existing workflows (and these are places that have 2-3 production facilities around the country) and because the stable of freelancers they pull from can very quickly get up and running with PPro.”

I get this. What i don’t get is the resistance from 1 man bands and smaller 5-10 editor shops, of which there are many. What you describe is the “nobody uses it, because nobody uses it” syndrome. Pr is a great app, but for promo’s/trailers/etc there are huge workflow benefits in X now that are being ignored in favor of the “Pr is just like FCP 7 but kinda better” meme.

Again, I get it. I also think it’s really dumb. As soon as someone “big” in LA starts using X (and talking about it) watch how quickly the tide turns. Now, maybe that will never happen, but it would surprise me if it didn’t at some point. Whatever… I like it. 😉

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Herb Sevush] ” Because it matters to me doesn’t mean I am right, it simply means that X is not right for me.”

Yep, I agree.

[Herb Sevush] “My guess is that every editor in this forum could cut their next project on either X, Avid, or Ppro with sufficient training. I am also guessing that their reactions to the various NLe’s would be as polarized as the US congress.”

I’m already doing that to an extent, sometimes working in 2 or 3 NLE’s at once. I guess that’s why I have a hard time understanding the “irrational” aspect of resitance to X. I can see what it falls short at, but also what it crushes other NLE’s at. And I’m sure someone like you, with different workflow needs might see the complete opposite. But I hear the “It’s iMovie Pro and it sucks” resistance (still!) to X from FP 7 users who do exactly what I do, and it really makes no sense to me.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~