-
Notifications
You must be signed in to change notification settings - Fork 48
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
Segmentation Fault Converting h264 to VP9 to 4k #150
Comments
Can you try some more minimal reproduction cases? ffmpeg -i bbb-2m-4k-30fps.mp4 -an -c:v libsvt_vp9 -g 30 -minrate 6000k -maxrate 17400k -b:v 12000k -f null -
# and
ffmpeg -i bbb-2m-4k-30fps.mp4 temp.yuv
SvtVp9EncApp -w 3840 -h 2160 -i temp.yuv -fps 30 -n 100 -tune 0 -q 32 -b test.bin ? As a note, SvtVp9EncApp only supports yuv input |
Oh good to know!
This still seg faults.
This completes with the message
If I re-run it without
Full dump
|
I also ran it again after running
Just wondering if there is anything else I can look into, or any way to dump extra logs to find out what is going on? |
I am able to reproduce the issue even on bare metal, so I will try to see if I can debug further as a note, I was able to do so with just ./Bin/Debug/SvtVp9EncApp -i /dev/urandom -w 3840 -h 2160 -fps 1 -n 1 -tune 0 -q 63 so no need for any specific clip nor anything other than just the 4k part. However, the error message is not always the same ( |
Hi there
I'm trying to convert a 2 minute 30fps 4k h264 file to a 4k vp9 file using ffmpeg and I'm getting a segmentation fault around 42 seconds of video transcoded (3 minutes of processing time). The same video worked fine transcoding to 1440p video file.
ffmpeg command:
I also tried running
SvtVp9EncApp
and I get the following error:command:
error:
The full dump:
I'm running this in an EC2 m6i.xlarge instance running Ubuntu
CPU: Intel(R) Xeon(R) Platinum 8375C CPU @ 2.90GHz
RAM: 16GB
The video file is a 2 minute clip of Big Buck Bunny, trimmed in Quicktime so it shouldn't be a strange format causing the issue.
Any help or direction in debugging this issue would be helpful.
The text was updated successfully, but these errors were encountered: