-
Ok thanks. I have a few more questions.
1. How does the encoding process work? Do the videos get encoded one after another or do they get stacked up to encode multiple videos simultaneously?
2. The video options only encode into 480p and ouputs to .webm, correct? Is there a way to make it so the videos keep their original resolution? So if someone uploads a 4k video, the output will be in 4k, or 1080p would stay as 1080p.
3. does .webm have a benefit over .mp4?
4. So if my goal is to raise the max resolution to 2160p, output in .mp4 format, using 4 threads, is the code below correct?
a:3:{s:1:"h";s:3:"2160";s:10:"force_type";s:4:"mp4";s:14:"ffmpeg_options";a:1:{s:7:"threads";i:4;}}
5. What happens to the video if I raise the output resolution to 2160p? Would 720p videos encode to output 720p correctly or would the video be enlarged to 2160p?
-
1. Videos are added to the queue and processed one by one. At the same time only one vide os encoded.
2. You can try to remove "h" param at all, it maybe it will work.
3. Some browsers supports webm only this is the reason it's encoded to webm
4. You have incorrectly encoded string, it will not work, also you need to rise bitrate as well, default bitrate is 512k, you can specify it as 'video_bitrate' option, for example:
a:3:{s:1:"h";s:4:"2160";s:10:"force_type";s:3:"mp4";s:14:"ffmpeg_options";a:2:{s:7:"threads";i:4;s:13:"video_bitrate";s:5:"2048k";}}
5. I think it shouldn't stretch the video to a bigger size if it's smaller, but it's better to try.
-
When you say remove all "h" param, do you mean like this?
a:3:{s:4:"2160";s:10:"force_type";s:3:"mp4";s:14:"ffmpeg_options";a:2:{s:7:"threads";i:4;s:13:"video_bitrate";s:5:"2048k";}}
-
No, like this:
a:2:{s:10:"force_type";s:3:"mp4";s:14:"ffmpeg_options";a:2:{s:7:"threads";i:4;s:13:"video_bitrate";s:5:"2048k";}}
Please never edit this string directly, you need to use php functions unserialize to convert it to an array then edit php array then run serialize to make serialized array string.
-