Add H.265 recipe

[kfrn]

It's very similar to encoding H.264. Just did this on whim, do you think it's useful for ffmprovisr users?

[kieranjol]

I think that's it's totally worth adding. It could be useful to mention that you need to use '--with-x265' when building with homebrew in order to access the codec.

[kfrn]

Thanks @kieranjol and @retokromer, this indeed slipped my mind! Note added.

[kieranjol]

LGTM!

[ablwr]

So easy to forget about! I wonder if there's a place in ffmprovisr to explain these kinds of things, or if sufficient in each recipe?

[bturkus]

I had the same thought about Reto's installation instructions (--with-sdl2 --with-freetype --with-openjpeg --with-x265 --with-rubberband --with-tesseract). From an educational perspective, it'd be nice to break it down a little bit. Though I'm not trying to submit an issue to Reto's personal site ;)

…

On Mon, Jan 30, 2017 at 10:58 AM, Ashley ***@***.***> wrote: So easy to forget about! I wonder if there's a place in ffmprovisr to explain these kinds of things, or if sufficient in each recipe? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#139 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIkiXig8Rox-_qrD-PE5nLPy4t5zFzubks5rXjLfgaJpZM4Lw_XD> .

-- *Ben Turkus **| **Preservation Project Manager* *415.558.2158 **|** benturkus@bavc.org <benturkus@bavc.org> *

[kieranjol]

How about an 'install ffmpeg with homebrew' recipe, and each option that is required to run the commands in other recipes is explained? There could be a note about --HEAD too.

…

On 30 Jan 2017 19:02, "bturkus" ***@***.***> wrote: I had the same thought about Reto's installation instructions (--with-sdl2 --with-freetype --with-openjpeg --with-x265 --with-rubberband --with-tesseract). From an educational perspective, it'd be nice to break it down a little bit. Though I'm not trying to submit an issue to Reto's personal site ;) On Mon, Jan 30, 2017 at 10:58 AM, Ashley ***@***.***> wrote: > So easy to forget about! I wonder if there's a place in ffmprovisr to > explain these kinds of things, or if sufficient in each recipe? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#139 (comment)- 276155802>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AIkiXig8Rox-_qrD- PE5nLPy4t5zFzubks5rXjLfgaJpZM4Lw_XD> > . > -- *Ben Turkus **| **Preservation Project Manager* *415.558.2158 <(415)%20558-2158> **|** ***@***.*** < ***@***.***> * — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#139 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABEyvjkmSzmHAKDgUrSWOcZwbqq2llcpks5rXjPTgaJpZM4Lw_XD> .

[kfrn]

Sounds good! I leave it to one of you Mac users ;)

[retokromer]

Two remarks:

• The problem with --HEAD is that this is fine for geeks, but not for average users. I made very bad experiences recommending it, and now I prefer to recommend to use the last version of a currently maintained branch.
• It concerns not only macOS users, but also Linux (Linuxbrew is very similar but not identical to Homebrew) and Chocolatey as well.

[@bturkus: I‘ll update! Thanks for the hint!]

[kfrn]

I didn't know about Linuxbrew but I may have to check it out! Thanks @retokromer.

[retokromer]

@kfrn: There are some problems, but generally speaking Linuxbrew works well. I tried to oppose when it was expelled from Homebrew… I was part of the minority.

[retokromer]

@bturkus: I added a note on my website. I’m hesitating about putting it into the text itself, because when one is installing, usually (s)he is just starting with FFmpeg. I guess it would intimidate and/or confuse the beginner. Thoughts?

@kfrn: Should I copy this also into ffmprovisr, or is the link sufficient?

@kieranjol: Do you think ffmprovisr should recommend HEAD instead of the currently maintained branch? BTW: If we recommend both, then we should clearly explain pros and cons of each solution.

[kieranjol]

Hi Reto, I do not think that HEAD should be the default recommendation, but I think that it's useful to mention as a note. If anyone ends up asking for official support from ffmpeg-user, they will be asked to test git head first anyhow.

[retokromer]

You are right, since some months, HEAD or the last release has been replaced by HEAD only. That’s unfortunate, because I know this does intimidate many end users.

The numbering of the HEAD is, in my opinion, an expression of human stupidity. I suggested three times an easier readable versioning, but I failed miserably.

I’ll try to write it (including also how to update HEAD and how to go back from HEAD to releases).

[kfrn]

I agree with you all, HEAD is confusing for the novices, but it would be nice to have a note.

@retokromer, did you mean to add info to specific command(s), or were you thinking of adding an installation recipe as per #140 ? I'm in favour of either.

[retokromer]

@kfrn: I guess there are two different points here:

• In my opinion, if a command needs a specific parameter at compilation, then this should be mentioned in that command in any case, because this is user friendly.
• At the moment, in ffmprovisr there is a link to the installation instructions on my website, where I added a note about the parameters, as suggested by @bturkus. We can also add an installation recipe to ffmprovisr, and delete again the link to my website. I’m fine either way.

[kfrn]

@retokromer Right, gotcha. Agreed. As for the latter, either sounds good to me.