Updated README.md

[FazlyMR]

I have tried to improve the wording for the README.md file and section of the repository.

Generally, beside improved wording, some specific changes are:

• Encoders list in "Installation" section now split based on format/codec (AV1, VP9/VP8)
• Added VMAF as optional supported components, including link to it's repository page.
  (Also marked as required for "Target Quality" mode. But correct me if I was wrong)

[shssoichiro]

Thanks! I think this looks fine, just a couple of cleanup items.

[redzic]

It looks like you're requesting to merge into a branch that isn't master, and I think you have to rebase your PR onto the current master as well.

[FazlyMR]

This is fine, thanks for the cleanup.

[FazlyMR]

It looks like you're requesting to merge into a branch that isn't master, and I think you have to rebase your PR onto the current master as well.

I intended to contribute to the master branch, and I'm also sorry but this is my first time ever contributing to any kind of project here and don't yet know how to rebase my PR to the current master too. Any kind of guidance/help would be appreciated.

[redzic]

I think for this PR you first need to change the base branch back to master through the github UI, and then in the terminal do something like this:

git remote add upstream https://github.com/master-of-zen/Av1an
git pull --rebase upstream master

And then push your changes back to your branch through the terminal.

Let me know if that works for you

[FazlyMR]

I think for this PR you first need to change the base branch back to master through the github UI, and then in the terminal do something like this:

git remote add upstream https://github.com/master-of-zen/Av1an
git pull --rebase upstream master

And then push your changes back to your branch through the terminal.

Let me know if that works for you

I've tried it but changed my mind about it since if I change the base to master then there are other files from the branch I'm committing from that are going to be pushed to the master when I don't intend to.

[redzic]

I think you have to change the base branch, since if you leave it as-is, if we merge the PR the master branch will not actually be changed, only the multiple-input-files,-sequencial-processing branch (which is unused now) will have the updated README. Rebasing in theory should fix the problems regarding unrelated files in the PR, but let me know if you get any merge conflicts when trying the commands I posted earlier.

[FazlyMR]

I think you have to change the base branch, since if you leave it as-is, if we merge the PR the master branch will not actually be changed, only the multiple-input-files,-sequencial-processing branch (which is unused now) will have the updated README. Rebasing in theory should fix the problems regarding unrelated files in the PR, but let me know if you get any merge conflicts when trying the commands I posted earlier.

I also never used Git before.

[redzic]

Sorry for the delay, I went ahead and rebased your PR for you since in this case it was a bit tricky since there were merge conflicts, hopefully that is OK with you. The PR looks good now though, thanks!

Fixed