Latest post Thu, Jan 24 2019 3:24 PM by Pat Horridge. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • Thu, Jan 24 2019 2:12 PM

    • Adrian Redmond
    • Not Ranked
    • Joined on Wed, May 28 2014
    • Channel 6 Television Denmark
    • Posts 162
    • Points 2,250

    Avid error messages

    When adjusting a clip volume today, I suddenly got an error prompt on the screen, which told me something like "Media Composer has encounted a structured exception... followed by a lot of code" I could not execute further actions and the error prompt kept popping up - even when I tried to close MC. In the end I had to use Task manager to stop MC and restart.

    Software engineers seem to be experts at creating error prompts that are totally meaningless to the user - and Avid seems to excel in this black art. Interpreting the meaning often requires googling or sending the prompt text to a forum, none of which is possible because the prompt cannot be pasted to the clipboard.

    Besdies eliminating these irksome message, could I suggest that error prompts be copy and pasteable - and that some of the more cryptic ones be published and explained for the benefit of users?



    Avid Media Composer v. 8.5.3. with Symphony Option on HP Z820 Dual Intel E5-2640 6-core HT 2.5GHz CPU 32GB RAM NVidia Quadro K4000 Graphics on Win7x64... [view my complete system specs]

    Adrian Redmond
    Owner / Producer / Editor
    Channel 6 Television Denmark

  • Thu, Jan 24 2019 3:24 PM In reply to

    Re: Avid error messages

    Having done some programing many years ago it may help if I explain what happens.

    When writing code there are always multiple outcomes of each instruction executed.

    The ones we expect to happen control the flow of the application as expected.

    We then add error trapping routines to catch outcomes we didn't exepct to happen but knew could happen.

    For these we generate a meaningful message to help the user understand why we generated an error.

    But that still leaves lots of potential errors we neither expected or planned for. Rather than just crash the application because the programme nolonger knows what to do next (based on what just happened) we raise a general error (or fatal error) and include the code that led to that step going wrong. This information is only useful to the programmer and even then only useful if the steps to creat that error can be reproduced and included.

    So yes it would be nice if unexpected fatal errors never happened but the nature of monthly updates and the fast development cycle make that almost impossible. And if not no errors then ore detailed error trapping but thats a lot of programming work spend not improving the software. So its a balance.

    ACI Moderator. I'm not employed by Avid or work for them. I just do this in my spare time. Normally using the current Media Composer version on My... [view my complete system specs]


    Broadcast & Post Production Consultant / Trainer  VET


    T 07581 201248 | E | W |

    Media Composer V8.2 Review Background Render


    Follow me on Twitter Pat_H_VET

Page 1 of 1 (2 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller