-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Turn off videoCompression by default #26160
Comments
Would be amazing if this could be revisited while on the topic of video: #21976 |
We have decided to have In looking at this issue, we also fixed a bug where setting We also intend to fix this issue where the video location doesn't print when video compression is skipped, since this situation would apply to all users now. See issue We will also update the wording of what is printed to the terminal to say 'Compressing' instead of 'Processing' in the video terminal output. See issue. We'll also add a 'true' value to videoCompression which coerces the value to 32 CRF. See issue. |
The code for this is done, but this has yet to be released. We'll update this issue and reference the changelog when it's released. |
Released in Cypress 13.0.0. |
What would you like?
Cypress also automatically compresses the recorded video to a Constant Rate Factor (CRF) of 32. Cypress could turn off video compression by default for all users - having a
videoCompression
value set tofalse
in their configuration file.Why is this needed?
Recording video in low CPU resourced machines results in slower runtime of Cypress tests. Video compression is on my default and blocking, so it increases the time the tests take to run. And video compression takes longer the longer the video is, so these reasons are compounding the problem.
Other
Turning off video compression would result in larger video sizes, which still needs exploration as to the impact for users and Cypress.
The release and implementation strategy has not been decided, but this could result in a breaking change for users.
The text was updated successfully, but these errors were encountered: