Forum Replies Created

Page 7 of 11
  • James Lackleter

    January 19, 2014 at 4:44 pm in reply to: fastest way to output

    lower bit rate, resolution, and profile (main opposed to high) will all speed it up. Do not change the name of your files if you are cutting with proxies okay, or your cut will be useless when you try to export xml.

  • James Lackleter

    January 19, 2014 at 11:52 am in reply to: To Editors thinking of switching to FCPX 10.1

    Gotham is Chicago.

  • James Lackleter

    January 19, 2014 at 8:02 am in reply to: Issues with FCPX 10.1, Maverick & USB 3.0

    I’ve had that happen in a shoot, big waist of time and really frustrating

  • James Lackleter

    January 18, 2014 at 7:50 pm in reply to: Issues with FCPX 10.1, Maverick & USB 3.0

    Could be drive. Seagates and WD tend to do unmount. Go with a G drive if you’re serious about editing.

  • James Lackleter

    January 18, 2014 at 5:51 pm in reply to: To Editors thinking of switching to FCPX 10.1

    Channel operations will change at random, the limiter filter registers over 0 decibels though it’s actually working, and occasionally random pops on clips with faders. These are the key issues I’ve found which worsen with the addition of tracks. They however can be avoided by breaking down the project scene by scene into separate projects.

    Also channel operations and effects not transferring into logic. Let me test an XML into logic with new version, one sec.

  • James Lackleter

    January 18, 2014 at 5:28 pm in reply to: To Editors thinking of switching to FCPX 10.1

    Oliver some very valid points. I watched some of your work and it looked like most of the projects you used FCPX for were stereo with limited tracks. It works perfectly for stereo projects with limited clips. Basically the more tracks you add, (or w/e, clips I guess) the more bugs will crawl out. And I don’t see the point having surround inside X when it can’t transfer to Logic.

    Also whoever accused me of spreading propaganda, I’ve been cutting all night and I feel awful. You gave me a good laugh with that and now I’m gleaming. Okay, back to facts, just had to share that.

  • James Lackleter

    January 18, 2014 at 4:47 pm in reply to: To Editors thinking of switching to FCPX 10.1

    You nailed it, I work for Adobe, Autodesk, and Avid… They pay me to mar Apple brands. Look, all I’m trying to do is save people time and energy. Many young ones may think because Final Cut 7 has a pristine name and is great program, that FCPX is too. It’s not, and it’s important for people to know this. I think what’s most important is why do these issues exist, why have they not been fixed. I’m dumbfounded as how anyone could buy this program and not be furious over the issues I’ve pointed out.

  • James Lackleter

    January 18, 2014 at 10:43 am in reply to: To Editors thinking of switching to FCPX 10.1

    I use the word fact because that’s what they are. If someone chooses to use it knowing those original statements, then gods speed. It’s my opinion it’s still in beta condition, and the only thing that is good and works is red code.

  • James Lackleter

    January 18, 2014 at 8:19 am in reply to: To Editors thinking of switching to FCPX 10.1

    In a science we use facts to back arguments, not insults. I’ve explained the wave problem earlier, I was the one who discovered it. I’ve poked this programs with more holes than swiss chess. To any would be editors, just look at the credits of those who discourage you from using X.

    Just another note, if you use X you will not get hired in NY, LA, or London.

    Avid, Prem, Smoke.

  • James Lackleter

    January 17, 2014 at 12:56 pm in reply to: To Editors thinking of switching to FCPX 10.1

    Last post on this thread for me because I’ve stated the facts for which are undeniably true. I mean I barely touched the tip of the iceberg, I could go one for pages. To all of the young ones who read this, and to the one person I convince to go with Avid, Prem, or Smoke. You’re welcome and God’s speed.

Page 7 of 11

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