>>105690514
>That's very decent quality all things considered. Which encoding parameters did you use?
vp9_twopass () {
input="$1"
output="$2"
scale="${3:-1.0}"
duration=$(ffprobe -v error -show_entries format=duration -of default=noprint_wrappers=1:nokey=1 "$input")
target_bitrate=$(echo "scale=0; (0.95 * 32768 / $duration)" | bc)
echo " Duration: $duration seconds"
echo " Target video bitrate: ${target_bitrate}k"

# First pass
ffpb -y -i "$input" -c:v libvpx-vp9 -b:v "${target_bitrate}k" \
-vf "scale=iw*$scale:ih*$scale" \
-threads 4 -row-mt 1 -cpu-used 4 -tile-columns 1 -pix_fmt yuv420p -crf 30 -g 300 -pass 1 -an -f null - 2>&1 | progressline -s snake -t "First pass>

# Second pass
ffpb -i "$input" -c:v libvpx-vp9 -b:v "${target_bitrate}k" \
-vf "scale=iw*$scale:ih*$scale" \
-threads 4 -row-mt 1 -cpu-used 4 -tile-columns 1 -pix_fmt yuv420p -crf 30 -g 300 -pass 2 -an "$output".webm

# Cleanup
rm -f ffmpeg2pass-0.log ffmpeg2pass-0.log.mbtree
}
You need to install ffpb, to have nice progress if you want it.
progressline is something I just love to use.

I've done a LOT of testing, 10bit offer little visual improvement while taking twice as long, all other fancy options offered very little improvement in targeting specific file size, while adding anywhere from 10%-50% overtime.
I have shitty CPU, and minimal is better sometimes.
I like it since I can use it to make webm quickly from insta/tiktok and post it here, and it also depends on the source material, AV1 take the longest since I can't accelerated with HW decoding.
>>105688940
You're not alone.
PS3 is very funky with specific format.
What did you use?
you need these
-c:v libx264 -b:v 15M -c:a aac -b:a 128k
Or try using DivX
-c:v libxvid -vtag divx -q:v 3 -maxrate 4854k -bufsize 384k -c:a libmp3lame -q:a 2 -ac 2