As a user I want to have easy to use presets for each encoder available to use.

1. offizieller Beitrag
    • Offizieller Beitrag

    Lets collect some useful presets per encoder here. I will make them available in the voukoder ui later on.

    Simply add you reply here and we can discuss and improve presets here.

    Please make sure you know exactly what these options are doing. Please don't post guesses. We want to collect really great presets here.

    Encoder Preset Options
    h264_nvenc Good Quality bf=2 preset=slow profile=high qp=19 rc=constqp g=%(fps*10)
    libx264 Best Quality / CPU Ratio (ABR 4 Mbit/s for 1080p30) b=4000000 preset=slower profile=high rc=abr tune=film x264-params=aq-mode=2:rc-lookahead=60:bframes=3:b-adapt=2:b-pyramid=2:ref=5:direct=auto:direct-8x8=1:me=esa:merange=24:subme=10:trellis=2:no-dct-decimate=1:no-fast-pskip=1
    ...

    This is going to be really nice. Using variables and math formulas in presets for certain settings. Combined with "Match Source" this is will be epic! I am excited about it. We could even do a bitrate calculation based on width and height.

    I have good settings for x264.

    These settings provide the best possible quality in my eyes with x264 without wasting CPU usage.

    Bitrate is set for 1080p 30fps in this case.
    Encoding with this settings take a while ;)

    Enable 2pass!

    Code
    b=4000000 preset=slower profile=high rc=abr tune=film x264-params=aq-mode=2:rc-lookahead=60:bframes=3:b-adapt=2:b-pyramid=2:ref=5:direct=auto:direct-8x8=1:me=esa:merange=24:subme=10:trellis=2:no-dct-decimate=1:no-fast-pskip=1

    I recommend to go a bit higher with the bitrate if your video has 60 FPS or if it's recorded gameplay.

    I think this is waste of time. There is no best settings for everything. Settings depends on the source, target quality/bitrate, individual perception, and so on.

    Zitat von Vouk

    make sure you know exactly what these options are doing

    People who knows what these options are doing do not need additional presets. People who don't knows - should use default encoder's presets or improve own knowledge about encoding and settings. You can open a new forum where people can share own settings and ask questions about encoders settings for their needs.

    However, presets for different video hosting service like youtube or vimeo based on their recommendations may be useful. Or presets for different devices.

    Einmal editiert, zuletzt von Digeridoo (24. April 2019 um 23:30)

    Zitat von Vogelforscher

    I have good settings for x264.

    Code
    b=4000000 preset=slower profile=high rc=abr tune=film x264-params=aq-mode=2:rc-lookahead=60:bframes=3:b-adapt=2:b-pyramid=2:ref=5:direct=auto:direct-8x8=1:me=esa:merange=24:subme=10:trellis=2:no-dct-decimate=1:no-fast-pskip=1

    Preset slower already includes: rc-lookahead=60, b-adapt=2, direct=auto, trellis=2. You do not need these options. bframes=3 is default for x264 - it also can be omitted. Setting ref to 5 you should increase level to 5.0, because level 4.2 for 1080p allow only 4 ref frames. This is about hardware compatibility.

    All these about knowledge what these options are doing...

    Zitat von Digeridoo

    Preset slower already includes: rc-lookahead=60, b-adapt=2, direct=auto, trellis=2. You do not need these options. bframes=3 is default for x264 - it also can be omitted. Setting ref to 5 you should increase level to 5.0, because level 4.2 for 1080p allow only 4 ref frames. This is about hardware compatibility.

    All these about knowledge what these options are doing...

    I set rc-lookahead=60, b-adapt=2, direct=auto, trellis=2 because in the Voukoder UI these settings didn't change when selecting preset slower. I have never said that I want hardware compatibility with these settings and level will be set automatic by x264 ;)

    Pretty much every new device can play videos with that level.

    • Offizieller Beitrag
    Zitat von Vogelforscher

    I set rc-lookahead=60, b-adapt=2, direct=auto, trellis=2 because in the Voukoder UI these settings didn't change when selecting preset slower.

    They most likely never will change. I explained it in the according feature request. This is just how the x264 presets works. The UI is just a tool to build an option string. The simple solution would to not use preset slow but each single option instead. But that would not be simple.

    My goal is to have some easy to use presets for users that don't have much insight in encoders, so the can just click on it and have a good, or fast, or whatever result the preset promises. So lets make then as good and as short and non-redundant as possible.

    But its good you guys are discussing and improving the presets. ;) But keep this on a respectful and professional level please.

    Zitat von Vogelforscher

    because in the Voukoder UI these settings didn't change when selecting preset slower

    It is another issue and this shouldn't be reflected on presets for encoders.

    Zitat von Vogelforscher

    I have never said that I want hardware compatibility with these settings

    I want. But your preset is not compatible for my needs. What I should to do?

    Zitat von Vouk

    But its good you guys are discussing and improving the presets.

    I am here is not for discussing presets options. I show you that presets are mostly useless. Not you nor me is guru in options. This situation will produce even more useless presets and you can not control it - example is above - you have added a quite strange preset.

    Also, you are not responded to my first message in this topic. Who will use your custom presets? It is more important then a lot of opened and even not responded bugs and feature requests?

    • Offizieller Beitrag
    Zitat von Digeridoo

    I am here is not for discussing presets options. I show you that presets are mostly useless. Not you nor me is guru in options. This situation will produce even more useless presets and you can not control it - example is above - you have added a quite strange preset.

    Then why are you posting to this topic? I am the project owner, so I decide what way this project goes. This project has both pro and non-pro users. There are alot of users who do not know to choose CRF or ABR, they just want to have a good video on YouTube. And I am trying to make it easier for them.

    Zitat von Digeridoo

    Also, you are not responded to my first message in this topic. Who will use your custom presets? It is more important then a lot of opened and even not responded bugs and feature requests?

    I already asked you to be more respectful and professional with your posts. I am not your paid developer. You will not decide what I am working on.

    Zitat von Vouk

    Then why are you posting to this topic?

    To stop you from doing a mistake. I thought it was obvious...

    Zitat von Vouk

    they just want to have a good video on YouTube

    Just create a preset for youtube as I proposed above. However about what we are talking. You are completely ignore my preposition, bugs and feature requests.

    Zitat von Vouk

    I am not your paid developer. You will not decide what I am working on.

    I am not your paid tester also. My time (as a lot of people who wrote feedback and waiting for you for months) costs too. I suppose it would my last feedback on this project. In Spite of you are doing a great job in general, you are not always ready to listen.

    2 Mal editiert, zuletzt von Digeridoo (25. April 2019 um 15:28)

  • Vouk 25. April 2019 um 15:29

    Hat das Label Geplant hinzugefügt.
    Zitat von Digeridoo

    You are not ready to listen

    Vouk is the leader and the only developer of this plugin, it's his child. He owes nothing to anyone, he listens to what he wants ; It's the rule, even if it's not your choices, like me you have to accept it.

    I'm wondering what problem that can have to have a preset for Youtube even for those who will not use it ?

    I understand the intention to have a solution of a simpler UI for those who do not master all these parameters many of which do not really have an impact on the export. This way is also chosen by many software.

    • Offizieller Beitrag
    Zitat von MyPOV

    Vouk is the leader and the only developer of this plugin, it's his child. He owes nothing to anyone, he listens to what he wants ; It's the rule, even if it's not your choices, like me you have to accept it.

    I see his point. I basically ignored everything version 1 related to get version 2 out. So that I don't have to work on two different versions. Now it's time to go over all pending version 1 topics and sort them out.

    Back to topic, please.

    As I said these presets above are not fixed. I just want to collect ideas, settings and discuss them. And later on even improve them. I personally would straight use for libx264 "crf=19" and done. But some users are just overwhelmed by all these hundreds of settings. It's too complex for some people. This is not even in development, this is just a theoretical discussion.

    To clarify...

    I am strictly against the following and think that it is a mistake:

    - integration of user's presets;

    - integration of presets like High Quality / Low quality and so on.

    Such presets are not standardized - results can vary depending on many things.

    Instead of this, I proposed to add only standardized presets, like:

    - youtube, vimeo and so on;

    - device specific (mobile phones, tablets, tv, etc.)

    - maybe some other standards.

    For simplifications of UI can be used another methods:

    - encoders have a lot of options which should be never touches until you know what are you doing. So such complex for the user and unnecessary options should be hidden from user (Simple and Advanced mode of UI).

    - wizard for the settings where user can choose what he wants as a desirable result.

    You can accept it or not. THE END.

    Zitat von MyPOV

    you have to accept it

    I always have a choice and more than one.

    2 Mal editiert, zuletzt von Digeridoo (25. April 2019 um 17:31)

    well, mine is

    X264:

    --level 5.1 --crf 16 --threads 0 --deblock 1:0 --bframes 16 --b-adapt 2 --ref 16 --qpmax 60 --rc-lookahead 60 --aq-mode 2 --aq-strength 0.7 --merange 32 --me umh --direct auto --subme 10 --trellis 2 --no-fast-pskip

    x265:

    --crf 16 --deblock 1:0 --bframes 10 --ref 8 --merange 44 --ctu 32 --me 3 --max-merge 4 --rdpenalty 2 --no-strong-intra-smoothing --rd 5 --rdoq-level 1 --limit-refs 0 --tu-inter-depth 3 --tu-intra-depth 3 --max-tu-size 16 --subme 5

    but voukoder doesn't allow me to change reframes in x265.

    Greetings to your friends I would like to ask you for help.

    You could write me the best settings at 30fps and 60fps for 2K so 2560x1440. I want videos at 28 Mbps

    I want to use Encoder video: NVENC hvenc

    30fps I need for my camera

    60fps I need for my gaming videos

    I don't know the other settings at all, so I don't know what to set next.

    Videos I want to publish on Youtube page

    Thank you very much for your help

    • Offizieller Beitrag

    I'd recommend the same as here: Iphone 4K video MOV to h265

    • Don't use levels when dealing with software decoders
    • Don't use bitrate based encodings when not aiming for a specific filesize (i.e. for BD authoring)

    It would be good to make a bitrate calculator. Like parameters in AME. Bitrate min, max, ect. I have already determined which values are suitable for me but I do not understand how to apply them here. (Sorry for the bad English).