Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Guys, Apple is really listening!

  • Alex Hawkins

    April 29, 2012 at 9:46 am

    As opposed to user experience?

  • Leo Hans

    April 29, 2012 at 11:24 pm

    “The fact that some people get excited when a company like Apple gives some tech support must mean that it isn’t normal. Otherwise what is the big deal here?”

    Well, a lot of I-never-tried-FPCX-but-I-like-to-criticize-it people says Apple doesn’t provide support for editors. So, for me, that statement it’s not true anymore.

    “What were they doing for three hours before asking for the file?”

    I don’t know what were they doing, but tree hours after a bug report feedback is perfect for me. Avid nor Adobe never wrote me after reporting a bug.

    Leo Hans
    Editor AVID – Final Cut Pro
    https://www.leohans.com

  • Timothy Auld

    April 29, 2012 at 11:33 pm

    Bitter about Apple’s actions? Absolutely. But precisely whom did I personally affront?

    Tim

  • Eric Santiago

    April 30, 2012 at 3:27 am

    What no annoying pop-up window like Adobe’s when AE croaks or acts a resource pig and dies?
    Adobe should remember my email by now during the oh so awesome CS3 to CS4 upgrade that caused so many crashes in AE, I almost had to change to Fusion 😛
    The pop-up is still there and none of the problems we’r ever fixed.
    Never mind about the so called Apple/Apple flub on AFP.
    yes you are both to blame since you didnt own up to it quick enough.
    No warning, no foul?
    And please Adobe guys you know who I am, we still own a huge amount of seats you can rest assure we wont be leaving you.
    Just thank Photoshop, Illustrator and (gulp) Flash for that 😛

  • Andrew Richards

    April 30, 2012 at 4:56 am

    Three hour response time isn’t bad. Four hours or less is all some very expensive enterprise support plans will promise. Not that Apple promises anything…

    Best,
    Andy

  • Tony Sarafoski

    April 30, 2012 at 11:33 am

    I sent Apple a bug report today and also uploaded a video screen cast on YouTube (as unlisted), no views yet 😉 Video was uploaded April 30, 2012 2:27 PM it’s now 21:32 AEST, I’ll give them the benefit of the doubt being from Australia LOL….

  • Steve Connor

    April 30, 2012 at 11:48 am

    I’m not sure they actually respond to every bug report that quickly, if at all!

    Steve Connor
    “FCPX Professional”
    Adrenalin Television

  • Walter Soyka

    April 30, 2012 at 1:11 pm

    [Michael Gissing] “The fact that some people get excited when a company like Apple gives some tech support must mean that it isn’t normal. Otherwise what is the big deal here?”

    [Andrew Richards] “Three hour response time isn’t bad. Four hours or less is all some very expensive enterprise support plans will promise. Not that Apple promises anything…”

    This was not support. This was a developer following up on a bug report to get the assets necessary to reproduce the bug.

    It’s certainly a good thing, but I don’t think it’s as remarkable as some in this thread are making out to be. A good developer is doing his job. This doesn’t mean Apple is listening (in terms of the big-picture questions that come up here all the time), and it doesn’t mean they’re not — it just means they’re working on squashing bugs.

    [Leo Hans] “I don’t know what were they doing, but tree hours after a bug report feedback is perfect for me. Avid nor Adobe never wrote me after reporting a bug.”

    I have filed many, many bug reports with many different developers. I’ve seen many of those bugs fixed in subsequent releases, but I’ve only gotten direct responses from the developers on a handful.

    In my experience, developers tend to respond when they need more information, either to be able to reproduce the bug itself, or to understand the scope of the bug.

    Non-response doesn’t indicate anything. You may have provided all the information the developers needed in the initial report, they may already be aware of the issue, or they may have already fixed it in internal builds. If you submit a bug report that a dozen others have submitted before you, it’s very likely that the developers already have a good understanding of the bug and don’t need to query you for more information.

    This isn’t unique to Apple; this applies to all major developers.

    This is also all about a one-way flow of information. Getting information back from a developer about bug status is almost totally impractical without NDAs.

    Walter Soyka
    Principal & Designer at Keen Live
    Motion Graphics, Widescreen Events, Presentation Design, and Consulting
    RenderBreak Blog – What I’m thinking when my workstation’s thinking
    Creative Cow Forum Host: Live & Stage Events

  • Jim Giberti

    April 30, 2012 at 9:19 pm

    I believe Noah is Apple feedback, meaning he’s THE person that actually sits in real time and reads them.

  • Tony Sarafoski

    May 1, 2012 at 10:25 am

    update: The bug report I sent Apple which included a private YouTube link has now been viewed. No email from Noah 🙂

    Either they’ve had the bug reported before, or I’m yet to be contacted..?

    Bug being the audio waves blurred in a timeline at random times. Never experienced this in 10.0.3, only 10.0.4.

    Anyone else experience this?

Page 2 of 3

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