Forum Replies Created

Page 223 of 258
  • Charlie Austin

    April 1, 2013 at 8:15 am in reply to: FCPX and very occasional lag.

    [Julian Bowman] “this forum will be more useful than annoying, and people will be less antagonised by your dogmatic fundamentalism, which is always a flawed position to take anyway.”

    Well, I hope I don’t come off as a dogmatic fundamentalist. I don’t think I’ve ever claimed that X is perfect, it’s clearly not. And I’ve said before that I’m not a big fan of people who crow that X is the most wonderful thing ever. I do happen to like it though, and it works really well for what I do. Also, my reply above was an honest one, I was, until recently, using X on a machine maybe almost exactly like yours, and I didn’t experience the lag you’ve spoken about. My longest projects are about 10 minutes though, mostly much less, so there may be performance issues I don’t see.

    I’m with you on the X timeline. The first version sucked, and it’s only really been useable since .4. I guess I just don’t see the inherent design flaws everyone else does. I like where they’r going with it. I do see plenty of things that need improvement and/or refinement, which I think I’ve been upfront about.

    Anyway, If I ever come off as some sort of blinded fanboy, please let me know. I think blind love, and blind hate are both pretty worthless when it comes to computer programs… 🙂

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

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

  • Charlie Austin

    April 1, 2013 at 6:02 am in reply to: FCPX and very occasional lag.

    [Aindreas Gallagher] “BUT – the system should be in a position to reliably accept plug-ins.
    Up until three days ago that was not true of a serious amount of third party plugin software.”

    You say that like it *never* reliably accepted plugins which, as you know, is patently false. Something broke 3 months ago. It seems pretty obvious that the X folks had to wait for an OS update to fix it. OS X 10.8.3 was released on 3/14. 2 weeks later, FCP X 10.0.8 was released, fixing the issue. Seems pretty responsive to me. Now maybe you’ll argue that Apple should tell everyone the technical details and give progress reports for every bug that comes up, but I’m not sure there’s a commercial SW vendor on earth that gives out that info unless you’re a developer.

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

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

  • Charlie Austin

    April 1, 2013 at 5:50 am in reply to: FCPX and very occasional lag.

    [Carsten Orlt] “The real advantage that FCPx gives me is that I actually have to think less about the mechanics than about the content I’m creating. This is the real revolution. “

    That’s it in a nutshell for me as well. There certainly are things that I think can be improved or added. But really, if there is something lacking in X that is specific to your workflow, or you just plain don’t like it or don’t think it’s worth the effort to learn it, use something else. It’s not like you don’t have a choice.

    I get that a lot of people are mad at Apple for EOL’ing their favorite NLE. I know the feeling. When I was mixing I used, and loved, Avid AudioVision. It was amazing, specifically for editing and mixing for Film and TV. Then, they bought Digidesign’s ProTools (or SlowTools as we all derisively called it), and killed AV. PT wasn’t at all the same, like, not even close, but the world kept turning, and everyone moved on. I can only imagine the vitriolic, inane internet ranting that would have occurred had forums like this existed back then.

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

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

  • Charlie Austin

    April 1, 2013 at 3:49 am in reply to: FCPX and very occasional lag.

    [Rafael Amador] “[Charlie Austin] ” as this is yet another thread about how FCP X is horribly, catastrophically flawed. Carry on…”
    You are right.
    People like Julian should shut up and keep their complains for them self.
    Only praises should be posted.
    rafael”

    Uh… I never said that. In fact I believe I said the opposite. Let’s see …” Not to diminish the importance of Julians, and probably others, issues, “ Yep. Anyway, Julian did not start this thread, Aindreas did, with a specific, though IMO loaded question about FCP X responsiveness. Which, after a couple actual responses, seemed to be turning into another X bashing fest, to which I reacted. Sorry if it bothered you somehow. I’ve never believed that only praises should be posted, hearing of problems folks are having is helpful, not only for the poster in hopefully finding solutions, but also for others to hear of potential pitfalls. Hearing random uninformed biased opinions about how awful FCP X is are not. At least to me. I’m really not sure what purpose they serve. Now, if you’ll pardon me, I’m of to the MC forum to post about how awful it is… :-/

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

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

  • Charlie Austin

    April 1, 2013 at 2:25 am in reply to: FCPX and very occasional lag.

    [Gary Huff] “That’s fine, but I find great benefit from the plugins I use and find the idea to not use 3rd party plugins to be patently ridiculous.

    It is ridiculous, and I use them all the time with no issues.I don’t think we’re talking about a problem with X, but a problem with some peoples installations. Not to diminish the importance of Julians, and probably others, issues, but I haven’t experienced these problems. There are plenty of other people who’s installations run just fine as well. But I guess that’s off topic, as this is yet another thread about how FCP X is horribly, catastrophically flawed. Carry on…

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

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

  • Charlie Austin

    April 1, 2013 at 2:20 am in reply to: FCPX and very occasional lag.

    [John Davidson] “Charlie it sounds like your setup is pretty similar to ours. Are you doing sparse disks? I’m sure you probably told me all about it the other week and I completely forgot. Last few months have been a blur!”

    Nope, Events and Projects are local, but all media is central and referenced, not copied to local event folders. We haven’t totally switched to X, so Sparse Discs might be an option, but now that X .08 can duplicate projects and events using the symlinks, ie. without trying to copy all the actual source clips into the duplicate -which broke the links to the central media-, we can probably just use our old fashioned sneakernet method. To share a sequence, just duplicate project +used clips without renders, give new project and new “clips for project” event to other editor, etc. etc. Almost exactly like handing off a sequence in 7.

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

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

  • Charlie Austin

    April 1, 2013 at 1:34 am in reply to: FCPX and very occasional lag.

    [Aindreas Gallagher] “do you get system slow down or interface breaks? Do Apple have anything to address here?”

    Well… Other than the first press of the spacebar or L key after opening the app, I don’t get any appreciable slowdown in X at all. And I often use all sorts of crazy 3’rd party and native plugins. To be fair, I don’t do a lot of CC. On a 2009 Mac Pro originally, and for the last couple weeks on a new 27″ iMac. There are some complicated piles of FX and/or compositing which either require setting the playback quality to better performance, or rendering the problematic section. This is stuff which would never play at all without rendering in 7, and just plays choppily -sometimes- in X. My experience is that X, at it’s slowest, performs at least as well as 7, and usually performs much better. Source is generally HD of some flavor served over Gb ethernet from a NAS RAID. The only interface slowdown I notice is the first load of the project library if there are more than 10 or 15 sequences in it. After the first load it’s generally snappy, more so on the new iMac.

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

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

  • [Ned Miller] “Thank you everyone!!! I will be today’s project.

    Well, better have some other projects scheduled, since swapping the RAM will take you all of about 3-5 minutes. 🙂 It’s really easy.

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

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

  • Charlie Austin

    March 27, 2013 at 10:34 pm in reply to: Apple and databases

    [Steve Connor] “That’s what I used, it’s when you drill down to some of the data it get’s scary!”

    I’m going back in! Then i’m gonna change something! And open the project!!!! Or not. lol

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

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

  • Charlie Austin

    March 27, 2013 at 10:27 pm in reply to: Apple and databases

    [Steve Connor] “[Charlie Austin] “I actually just opened an X project database in an SQLite database browser. I don’t know what any of it meant, but it looked cool…

    Nice idea, I just tried it as well on a big event file, it was like something from “The Matrix”!”

    That’s what it looks like in a text editor, but in a database viewer it’s all organized and pretty. And indecipherable to me. XML I can read, databases… not so much. My nerd-fu is limited 🙂 Here:

    https://sourceforge.net/projects/sqlitebrowser/

    don’t open anything important! lol

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

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

Page 223 of 258

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy