Skip to main content

Issue with eager transformations erroring out

John Marvstall

I have seen the previous support forum solutions to my problem but I'm still not able to fix it. Basically when uploading a video over 40mb (on a free account), I'm getting the error "Video is too large to process synchronously, please use an eager transformation with eager_async=true to resolve". 
In my upload presets I have specified Eager Sync: true and added my transformation:

Further, when I get the response from cloudinary after upload, it appears that my settings are being applied because the "eager" property is present:
If anyone could provide some insight, I'd greatly appreciate it!

1

Comments

4 comments

Date Votes
  • Official comment
    Akshay Joshi

    Hi John,

    From the screenshot you shared it looks like the eager is still processing.

    You can set :eager_notification_url to point to an HTTP URL on your side for receiving notifications when the eager generation is completed.

    Here is the documentation for it: https://cloudinary.com/documentation/notifications

    If you still face issues you can create a support ticket so that we can look at the logs and pinpoint the problem

     

  • John Marvstall

    Hi Akshay, thanks so much for your quick response. Is there a better way to deal with video transformations over the 40mb limit on free accounts? I don't seem to ever get a status of anything other than "processing" even after after upload completes, which then causes the 400 errors about "video is too large to process synchronously".

    0
  • John Marvstall

    I'm trying to implement the notification_url but can't get past a 400 error "Notification url parameter is not allowed when using unsigned upload. " even though I have this upload preset set as "Signed" in my account settings. Any idea why this would be?

    0
  • Mo Ip

    Hi John,

    Cloudinary sets an 'online' video transformation limit of 40MB for Free plans and 300 MB for our current 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.

     

    -1

Post is closed for comments.

Didn't find what you were looking for?

New post