Forum Replies Created

Page 25 of 40
  • Lots of apps have tc issues with Quicktime files. I don’t know if the issues are related but most stem from the way Qt calculates TC, running time divided by frame count. If its a variable frame rate codec or there is an audio overlap without picture even by just a single frame you end up with an invalid tc.

  • Here is an official response from Adobe, one day after a single blog-post regarding a single bug.
    When others report total project and media corruption in X, Apple’s response is zero.
    Speaks volumes.

  • [Chris Harlan] ” But, what is Bill on about? Am I missing something? Is there some slight of hand that I’m not attuned to in the video? I mean, I really can’t see it.”

    You’re not missing anything. It Is NOT magnetic. It’s just a nice, little video add on with a nice litte timeline that has tracks and allows you to ripple.
    Oh, did I say it’s not magnetic???

  • [Bill Davis] “I *think* I get it.

    Everything Apple did regarding X was evil and wrong as witnessed by the countless deep arguments and hundreds of thousands of on-going posts where legions who feel violated by the revision must stand up and endlessly condemn the company and what they’ve done.

    but on the other hand, “there isn’t all the much “revolution” going on with X.”

    Pardon me for a moment, I need to go make sure I remember how to spell “cognitive dissonance”…”

    Adding 10 features to an app is certainly not the source of grief. Adding 10 while removing 20 others is.

  • [Bill Davis] “I thought magnetism was the singular spawn of the devil – the tool purpose built to wreck video editing for human beings for all time.

    And now it’s crept into a tool in the enemy camp. “

    a) Other NLEs had magnetic timeline capabilities long, long before X. Edius for example. Difference is: you can switch it off (and it’s off by default). Also single viewer mode btw., which is also there as an option, not a must.
    So, again, nobody has a problem with the magnetic timeline when it makes sense. People have a problem when it doesn’t make sense and you cannot switch it off. Plus, as Edius shows, you can have tracks and magnetic.
    There isn’t all that much “revolution” going on with X once you look around the “enemy camps”.

    b) That “magnetic” feature in Photoshop only applies to clips that are in one the same layer or video group and only when you ripple. If they’re not (ie. on different tracks) or you just move clips around no magnetism going on at all.

  • Frank Gothmann

    March 22, 2012 at 12:59 am in reply to: Baselight for FCP

    [Michael Gissing] “I would still use Color, if only to use the Tangent Wave controller and to have grades render whilst FCP is still active. Grading with a mouse sucks.”

    There’s Eucon support so you could use Avid’s control surfaces for grading. (No Eucon in X btw). Would be nice to see that as a plug for MC or PP6.
    Yep, it’s sad. I hope they’ll recoup some of the money when the version for Nuke comes out.

  • Frank Gothmann

    March 21, 2012 at 10:28 pm in reply to: FCPX or Not…

    [Bill Davis] “And in doing so they may damage the potential of FCP-X irreparably.

    Too many people are still hollering for it to be more and more like the editing systems we’ve had for decades.”

    Oh come on. Having an optional viewer and canvas and optional tracks might damage the potential? Options and features, as far as I remember, have never damaged the potential of anything, rather the contrary.
    You can’t shake the idea that people want what you call old fashioned because of habbit. I might be because it actually works.
    A wheel is a wheel and it is round for a reason. Reinventing it and making is square just so that it’s different and then asking third-party developers to supply the sandpaper doesn’t make sense.

    [Bill Davis] “FCP-X elevates “edit” more towards parity with concepts such as search, sort, find, alter and deploy.”

    As well as revolutionary concepts such as crash, corrupt, enjoy spinning beachball, reinstall from scratch, pull hair out and finally switch application.

  • [Steve Connor] “I like FCPX a lot, but if I was in your position it wouldn’t be in the running at the moment. As we keep saying a roadmap or at least a statement of future intent for FCPX would be very helpful for larger facilities like yours. As much as I like Apple Products, I think it’s ridiculous that they haven’t done this.”

    I agree with you. If X had been there in addition to 7… no problem with me. Also, a big problem is that Apple’s dominance and pricing policy kept certain apps away from the Mac completely. With Apple pulling the plug, there is currently no professional DVD authoring application on the Mac available anymore (Encore doesn’t cut it). Unlike NLEs where there is a choice, DVDStudio Pro was the only viable choice on the Mac.
    There never was and there never will be a pro Blu-ray authoring app, no high-end AVC encoding and zero MVC encoding on the Mac. Optical dics are big, big business for us so Apple signaling the want to see it dead and dropping support is not what we need.

  • [Steve Connor] “How so?”

    Because retraining people costs time and money. There are mistakes, things need to settle in, new workflows need to be tested and established. Entirely new software needs to be purchased, new plug-ins or hardware if plug-ins aren’t available etc.
    We have 80TB of shared storage, tuned to work perfect with FCP7. In order to work fine with other NLES things need to be changed and reconfigured. That’s not a problem technically, but those 80TB need to go somewhere to do that. Preferably while still being usable. Otherwise it’s a shutdown for several days. And even after that, since are not moving to Windows from one day to the next, the challenge is to make it work with several NLEs and platforms. And which software will it be? It’s time consuming to really evaluate things to the core. The FCP ecosystem grew with us as we grew and as the market grew. It has to be replaced with something that provides full functionality from day one while still maintaining compatibility with the Macs that are still in use bascially BECAUSE FCP7 still works and the Macs still work. If we had gone with Avid or Edius (or Premiere) from day one none of these considerations would be necessary now.

  • Because the discussion extends well beyond FCPX. It’s about Apple, hardware, other NLEs and stuff in general. That’s pretty unqiue. Plus you have people pro and con, lots of different views, backgrounds. Lots of consider, to rethink, to evaluate plus it’s just plain fun. As is the possibility to be able to vent among people who actually understand what you are talking about.

Page 25 of 40

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