Skip to content
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

Opening a rendered video inside Studio throws "Unexpected error: content-length is null" #4828

Open
kuzzmi opened this issue Jan 28, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@kuzzmi
Copy link

kuzzmi commented Jan 28, 2025

Bug Report 🐛

Regardless of the OS: MacOS, Windows or Linux, whenever I press on a link to open a video inside Studio, I get this message.

I'm using bun, but it's the same for node as well. I don't think I'm doing anything particularly wrong or undocumented. Essentially, I render from the studio, but can't open the rendered output in it.

Image Image
@kuzzmi kuzzmi added the bug Something isn't working label Jan 28, 2025
@JonnyBurger
Copy link
Member

Just tested, not getting this in the latest version! Which version are you in?

@kuzzmi
Copy link
Author

kuzzmi commented Jan 30, 2025

Just tested, not getting this in the latest version! Which version are you in?

I'm on 4.0.252, but after upgrading to 4.0.255 nothing has changed. That is a plain blank template with updated default Composition, and everything's fine, the video file is fine:

╭─ Starting render 
│ Bundled code         ━━━━━━━━━━━━━━━━━━ 2058ms
│ Composition          Audio-Visualizer
│ Codec                h264
│ Output               out/Audio-Visualizer.mp4
│ Concurrency          5x
│ Rendered frames      ━━━━━━━━━━━━━━━━━━ 14509ms
│ Downloaded assets    ━━━━━━━━━━━━━━━━━━ 1 file
│ Encoded video        ━━━━━━━━━━━━━━━━━━ 1345ms
│ ○                    out/Audio-Visualizer.mp4 889 kB
╰─ Done in 18317ms.

@JonnyBurger
Copy link
Member

I think you are running the studio with bun (in package.json remotionb studio was set when initialiting with Bun)

And I think this is a Bun bug, maybe in a recent version, we are indeed setting the content length header.
I am getting a similar error with the renderer in the latest Bun version.

Temporary workaround: Replace remotionb with remotion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants