You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
only when using those ffmpeg releases, (on an updated debian 12). I tested it on multiple machine, it's clearly not the hardware ;)
The same video and live with the stock debian release of ffmpeg works fine.
Describe the expected behavior
This static version of ffmpeg is working great for other usages of ffmpeg (in my case, for a professionnal video streaming service for Focusgroups that I maintain, not peertube-related.) so I guess it's a compatibility issue between Peertube and those ffmpeg static builds (local or remote runner, both are crashing)
so ... basically peertube seems fine as long as people don't use that ffmpeg release. Maybe you could tell people NOT to use those static builds...
The text was updated successfully, but these errors were encountered:
vincib
changed the title
ffmpeg SIGSEGV on remote runner when using ffmpeg static build !
ffmpeg SIGSEGV on remote and local runner when using ffmpeg static build !
Mar 30, 2024
Describe the current behavior
I get a SIGSEGV on ffmpeg 5.1.1 or 6.1 downloaded from https://johnvansickle.com/ffmpeg/
only when using those ffmpeg releases, (on an updated debian 12). I tested it on multiple machine, it's clearly not the hardware ;)
The same video and live with the stock debian release of ffmpeg works fine.
Describe the expected behavior
This static version of ffmpeg is working great for other usages of ffmpeg (in my case, for a professionnal video streaming service for Focusgroups that I maintain, not peertube-related.) so I guess it's a compatibility issue between Peertube and those ffmpeg static builds (local or remote runner, both are crashing)
so ... basically peertube seems fine as long as people don't use that ffmpeg release. Maybe you could tell people NOT to use those static builds...
The text was updated successfully, but these errors were encountered: