Eager video preview on upload not processed - receiving "ignored: true"

Comments

1 comment

  • Avatar
    Tia Esguerra

    Hi Alexandre,

    Thanks for reaching out.

    Adding e_preview to an upload preset via the UI is not currently supported. I see that you have added it through the Admin API.

    The "ignored: true" in the response to the eager is expected but can be confusing if you have not seen it before. It is returned in cases where you are performing eager transformations and using e_preview.

    Before we can create the derived version with e_preview, we need to analyze the original video to find the interesting parts in it - if you haven't already requested a transformation using e_preview for that video before.

    The first time you request a transformation requiring video analysis, we run an asynchronous task to analyze the video and produce and output a histogram containing data about the interesting parts of it. That analysis output file is then used to generate the actual transformation that you request, in this case c_fill,e_preview,h_300,w_300.

    The "ignored: true" just means that we need to perform this asynchronous analysis even before we can process the eager transformation you requested, and thus, the eager is deferred or "ignored", but the actual analysis and eager will continue to be performed in the background. It's not an error response indicating an issue with the request or generation.

    To keep track of the completion of the derived for e_preview, you will also want to set a cloud-level Notification URL (Settings -> Upload tab in your account) and listen for the notification_type 'eager' because that will be used to send the final notification for the eager when it completes.

    Normally, you could set a notification in your upload preset, however, there is a bug on our side currently where the value of the eager_notification_url is not propagated correctly to the last 'eager', for requests using e_preview. In those cases, we will send the notification to the URL set in the cloud-level Notification URL which is why I suggested this as a workaround for the time being.

    I hope this helps. Let me know if you have any questions at all.

    Kind Regards, 

    Tia

    0
    Comment actions Permalink

Please sign in to leave a comment.