Comments

1 comment

  • Avatar
    Loic Verger Del Bove

    Hi Ilja,

    When Cloudinary returns an error for an image URL that failed to load due to a problem with the image or URL, we return an HTTP header containing more information about why the request failed.
    We also return this header for requests where an image was returned but there was a warning, such as when the default image placeholder was sent instead of the requested image.

    This information is sent in the `x-cld-error` header, and you can see the value by using your browser's web developer tools to examine the request and response for the image which didn't load correctly.

    I've taken a look at your example, and in this case, the specific error is `Resource not found - w_300/alef/pexels-ron-lach-6660746_wfqkaw`. 

    This is due to the transformation being after the version number so we are searching for the folder `w_300`. 

    The right URL to use is https://res.cloudinary.com/dj14kojpw/video/upload/w_300/v1616690349/alef/pexels-ron-lach-6660746_wfqkaw.mp4 but this will still lead to a 400 error with the following error: `Video is too large to process synchronously, please use an eager transformation with eager_async=true to resolve`.

    Cloudinary sets an 'online' video transformation limit of 40MB for Free plans and 100 MB for paid plans. This is not a limit on the size of videos you can upload into your account but is the maximum size of a video that can be transformed synchronously/on-the-fly.

    For videos larger than this limit you must request that the derived versions are created before they're requested, which we call 'eagerly', and that the processing takes place in the background ('asynchronously'). When using asynchronous eager transformations you can manipulate videos as large as your account's maximum video file size limit.

    Eager transformations can be requested for new videos in the upload API call or configured in an upload preset, including an upload preset that is used when you upload to Media Library.
    For existing videos, you can request eager transformations via the explicit API method.
    Once the video is transformed eagerly/asynchronously it will be available via the URL as normal.

    Hope that helps.

    Best,

    Loic

    1
    Comment actions Permalink

Please sign in to leave a comment.