Forum Replies Created

Page 85 of 97
  • Chris Kenny

    June 22, 2011 at 4:00 am in reply to: Python and XML references in FCP X binary file

    [Andrew Richards] “Nice find, methinks you are onto something. Now try running sqlite3 against a project file or event file…”

    I tried that this afternoon, but while those are SQLite data files, they’re pretty clearly generated by CoreData, which produces structure that’s fairly incomprehensible to humans. If you’ve had more luck figuring them out, I’d certainly be interested in anything you might have discovered, through.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read our blog.

  • Chris Kenny

    June 22, 2011 at 3:06 am in reply to: FCPX Text Inspector broken?

    [Jonathan Dortch] “Every time I add text to the timeline and try to use the inspector to modify text… seeing nothing. A few times it has popped up an inactive control panel, but can’t get to the Title / Text inspector. Link appears at the top of the pane but non-responsive. Will crash the software completely out if you keep trying to inspect the text to change any properties. “

    Yeah, the box to enter text doesn’t show up in the inspector sometimes. But double-clicking the text in the viewer works fine, at least for me.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read our blog.

  • Chris Kenny

    June 22, 2011 at 2:46 am in reply to: A ‘pro’ app with missing features

    [Adam Claude Jones] “Let me guess. Gluetools will not with with FCP-X either?”

    I don’t use Gluetools and haven’t tested it, but given how different the app is, I wouldn’t think so.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read our blog.

  • Chris Kenny

    June 22, 2011 at 2:45 am in reply to: one more kick in the groin.

    [Peter Blumenstock] “I don’t consider the ability to export a file with 4 discreet audio channels a high-end workflow. It’s part of the most basic feature set a NLE can have in the year 2011. It doesn’t get more basic than that.”

    Look, I find this omission annoying as well, but realistically, It’s a feature oriented around a certain type of deliverable that most of Final Cut’s user base probably doesn’t deliver.

    Meanwhile, exporting a surround mix, which was not especially intuitive in FCP 7, has gotten a lot easier.

    [Peter Blumenstock] “It part of the same attitude Apple shows with regard to lots of other things that are not part of the i-consumer hype.”

    You’re misreading Apple’s behavior. Apple takes the same conservative approach to feature implementation with its consumer products as well. Daring Fireball jokingly linked to this Google search about iOS 5 today.

    [Peter Blumenstock] “The broadcast and post house market will run a mile a from FCP X”

    Meh. I doubt it. This sounds entirely too much like past Apple-related Internet flame-fests. Unless Apple really never implements any of these missing workflow features, I doubt there will be much long-term damage.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read our blog.

  • Chris Kenny

    June 22, 2011 at 1:46 am in reply to: Steve Martin’s first look

    [John Pale] “Apple has burned a lot of bridges with this release”

    Honestly, I’ve seen a lot of Apple-related Internet firestorms over the years, and the long-term damage rarely amounts to much. Assuming Apple plugs some of the workflow holes over the next 12 months… most editors/facilities weren’t going to upgrade to such a radical new release in the first 12 months anyway, so shipping the 1.0 without these features won’t have made much difference.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read our blog.

  • [Tom Babauta] “Let us stop being disillusioned here. Its been 2 years since the last major upgrade, they had all the time to listen. Its clear that its not our market they are after anymore.”

    That’s one interpretation, but it’s not the only one. The bulk of the work done in FCP X is useful (and much-needed) in a high-end pro app. So it’s not like Apple has spent the last three years writing code that’s useless to our market. They’ve spent is writing code that will be extremely useful to our market once they write a bit more code.

    Personally, I consider it unlikely that they’re going to give up the high-end pro market because they’re too lazy to implement XML exporting, etc. It’s far more likely they shipped as soon as they had a product useful to some people, and are planning to make it useful to more people in the future.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read our blog.

  • Chris Kenny

    June 22, 2011 at 1:37 am in reply to: External Monitoring – Question

    [Nate Weaver] “Its the timebases of the Mac desktop output not jiving with what the AJA has to convert it to to make an SDI out. Closer they are the better, I’d think.”

    My guess is that what’s going on with all of this is that AVFramework (Apple’s new QuickTime replacement) doesn’t quite support video I/O yet. I assume they’re working on this. In fact, I wouldn’t be stunned to learn it worked in Lion. (But I also wouldn’t be stunned to see it take them six months.)


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read our blog.

  • Chris Kenny

    June 22, 2011 at 1:33 am in reply to: Reality

    [Herb Sevush] “Actually that sounds like a horror show to me. I like to be able to choose what material is in front of me when I work on a project, not have everything I’ve ever worked on loaded every time I start my NLE.”

    It’s not like everything is some disorganized mess. Everything is well organized. Or you can hide the Events pane (for which there’s a keyboard shortcut) and focus only on clips from a single event or even only on clips tagged with a particular keyword.

    People need to stop freaking out without using (and understanding) it. Yes, it’s missing several important workflow features, but it’s clear a lot of time went into the UI/editing features.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read our blog.

  • Chris Kenny

    June 22, 2011 at 1:29 am in reply to: A ‘pro’ app with missing features

    [Adam Claude Jones] “If it has DPX exporting, does it mean it can also import and work with DPX?”

    There doesn’t appear to be any DPX importing at present.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read our blog.

  • Chris Kenny

    June 22, 2011 at 1:16 am in reply to: A ‘pro’ app with missing features

    [Herb Sevush] “This is just typical Apple arrogance – just more of the same style over substance crap”

    That makes no sense. The new UI has substantial new functionality. It’s not ‘style over substance’.

    The whole “I don’t want to learn something new” thing is expected, but having invested a bit of effort in the new UI this afternoon, there do seem to be some real improvements.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read our blog.

Page 85 of 97

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