Latest post Tue, Nov 12 2019 3:25 PM by Marianna. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • Tue, Nov 12 2019 10:10 AM


    I'm getting an error that doesn't allow me to play the timeline as soon as I have more than a couple of layers of video or add a simple effect. The error says:


    Exception: SFPlayConsumer::Execute TIMEOUT


    The media is consolidated, so I'm not sure why it's not able to handle it.


    Any idea why this is happening?


    Thank you in advance,


    Avid MC 2019.8.0 | Mac Pro 2012 | 12-Core 3.33 GHz Intel Xeon | 64GB RAM | Nvidia GTX 1080ti | Blackmagic Design Decklink 8K | 500GB Sandisk Pro PCIe... [view my complete system specs]
  • Tue, Nov 12 2019 1:59 PM In reply to

    Re: error in the composer window

    What is the format/frame rate of your project, and what is the format/frame rate/resolution of your clips?

    Media Composer 2019.12 w/Symphony/SS/PF options, HP Envy 17t-j100 Quad Edition laptop, Windows 10 Pro, Intel Core i7 2.4GHz, 16 GB RAM, nVidia GeForce... [view my complete system specs]

    "There is hardly anything in the world that some man cannot make a little worse and sell a little cheaper, and the people who only consider the price are this man's lawful prey."  - John Ruskin (1819-1900)


    Carl Amoscato | Freelance Film & Video Editor | London, UK

  • Tue, Nov 12 2019 3:25 PM In reply to

    • Marianna
    • Top 10 Contributor
    • Joined on Thu, Oct 13 2005
    • Avid
    • Posts 10,935
    • Points 227,490
    • Avid Beta Moderators
      Avid Customer Advocate
      Avid Developer Moderator

    Re: error in the composer window

    Unfortunately, SFPlayConsumer::Execute TIMEOUT is a pretty generic error, indicating that there was a stall in the pipeline somewhere between storage and display. 

    Whatever caused the stall didn't register any specific errors, so the end-of-pipe just times out. 

    Not a lot of useful debugging info in just that message. Simplifying the pipeline (e.g. disabling hw) can sometimes help narrow the cause down.  

    Do you have any I/O devices attached?

    Clear your bin memory....    then look for corrupt effect renders. The problem is to try and figure out where it is. 

    Try exporting sections of your timeline "same as source" as it's quicker and should allow you to find the cuprit without wasting days.

    Director of Online Communities and Forums/Customer Advocate [view my complete system specs]

    mobile 813-493-6800

    Twitter:  avidmarianna

    Facebook: Marianna Montague   |  Connect 2019 | April 6-7 | Aria, Las Vegas, NV


Page 1 of 1 (3 items)

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