Forum Replies Created

Page 9 of 54
  • Mark Palmos

    June 23, 2011 at 8:50 am in reply to: FCPX REFUND request awaiting response…

    [David Roth Weiss] “FCP X is about the worst example ever. Heck, editors too often get paid to polish turds, they shouldn’t have to shell out 300 bucks to Apple for the privilege.”

    Hey there bud,
    Ja, with a deluxe set of rubber gloves, and a bunch of dosh at the end of the job, turds can even be quite appealing 😉

    what are you doing up at nearly 2am again?!

    Cheers
    Mark.

  • Mark Palmos

    June 23, 2011 at 7:48 am in reply to: FCPX REFUND request awaiting response…

    Who knows, in a year or two, fcpx may be ready for a pro market, and by then perhaps I will have grown tired of fcp7 and migrated to PP… we will see. In the meantime, I will have managed to get apple to agree to a refund for a product I feel is not useable. (I am keeping compressor and motion to mess with.)

    Here is the polite email Apple sent me today:

    Hello Mark,

    This is David from the iTunes Store Support Team. Please note I will be escalating your request, so if you have any other questions or concerns, you can reply to this email and it will come straight to me.

    Moving forward, I understand that you are not satisfied with the app “Final Cut Pro”. I can certainly appreciate you would like a refund, and I would be more than happy to help you out with this today.

    In five to seven business days, a credit of £179.99 should be posted to the credit card that appears on the receipt for that purchase.

    Please note that this is a one time exception because the iTunes Terms and Conditions state that all sales are final.

    Thanks for contacting the iTunes Store support and if you have any further concerns please write me back.

    Sincerely,

    David
    iTunes Store Customer Support

  • Mark Palmos

    June 22, 2011 at 9:54 pm in reply to: FCPX REFUND request awaiting response…

    36 hours later, no response from Apple. I wrote a second request for a refund today. The phone support say they cannot help at all with App Store customer service issues… so we have to fill in a form and hope for the best…

    Nice.

  • Mark Palmos

    June 22, 2011 at 9:27 am in reply to: No Keyframe editor? massive fail apple!

    [Matthew Sonnenfeld] “So after toying around with it, I have found the keyframe editor and I find it to be incredibly fast and easy…”

    Hello Matthew,
    I have seen that, but that is hardly what I would call a keyframe editor:

    You cannot expand any parameter that has more than one attribute (like crop or scale or position) – making it useless.
    You cannot add bezier handles to keyframes
    You cannot copy and paste keyframes
    When you copy and paste attributes, you have no choices as to how they will be pasted, etc… it is dismal.

    All in all, it is a step backwards from FCP where you had a terrible KFE, but could actually do more than you can now do with this lame software.

    Mark.

  • Mark Palmos

    June 22, 2011 at 8:52 am in reply to: It’s business… not personal

    Mate, I’m glad you are not my business manager!
    Is there something you did in this project that you could not do with fcp7? If so, I would be curious to know what!

    Mark.

  • Mark Palmos

    June 21, 2011 at 5:53 pm in reply to: No Keyframe editor? massive fail apple!

    FCP7 had the worst keyframing in the business, but fcpX has now taken the crown… pathetic!

  • Mark Palmos

    June 21, 2011 at 3:47 pm in reply to: my heart is sinking reading this

    [Joe Murray]
    But you’ll still run your Adobe product on Apple hardware, right? So either way, Apple wins”

    The ONLY reason I have an apple computer is for fcp… but with my 8 core now not new enough to take full advantage of the 64 bit rendering, and with fcpX seeming so lacking in features, I would definitely be going for a really fast 64bit PC… and premiere.et

    At the moment with fcpX it looks like I just wasted some money. FCP7 looks way better.

    Mark

  • Hi
    ja, gotcha, but i suppose that means no background rendering.
    Dang, I should have stuck to one post 😉

  • Mark Palmos

    June 21, 2011 at 10:52 am in reply to: buying a Mac Pro

    Hey buddy, yeah, what the hell are you doing up at this time of the morning!!!???

    Thanks for that info… I suppose in real terms it means not taking full advantage (or perhaps NO advantage) for background rendering and RT effects.

    I will probably look for a used 8 core with the 64 bit kernel once the new mac pros come out.

    Cheers,
    Mark.

  • [Chris Kenny] “All of Apple’s current hardware, desktop and laptop, can run 64-bit applications, and this has been true for the last several years. It will be interesting to see what the minimum system requirements are for FCP X, but 64-bit isn’t likely to be a major sticking point.”

    Hi Chris,

    AFAIK, only 2008+ computers ran run apps at 64 bit. Xeon 8 core mac pros like mine cannot, as the kernel is not 64 bit. In system profiler there has to be mention of 64 bit kernel, if there is no mention, the computer runs at 32 bit, regardless of the fact the xeons are 64 bit. That is AFAIK… but I do not know what the means for FCPX users.

    Mark.

Page 9 of 54

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