Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Video Encoding > MPEG-4 Encoder GUIs

Reply
 
Thread Tools Search this Thread Display Modes
Old 24th December 2018, 08:29   #1761  |  Link
spoRv
Registered User
 
Join Date: Nov 2016
Posts: 113
Solved!

Indeed, I just put the (very few) necessary plugins for a very light script, and it works!

Now, I'm curious to know how to get rid of potentially harm plugins - not only for your software, but in general... but this could be material for a new thread (or is there an existing one?)
spoRv is offline   Reply With Quote
Old 24th December 2018, 18:56   #1762  |  Link
legend
Registered User
 
Join Date: May 2014
Posts: 17
Nice Gui
legend is offline   Reply With Quote
Old 26th December 2018, 14:08   #1763  |  Link
Rocinante
Registered User
 
Join Date: Jul 2018
Posts: 9
Hi, UI seem clean and wonderful to use.
Wondering if there is any way to add function on GUI to precisely limit the max bit rate of an encoding or the option is just not possible on x264 and we are stuck with unconventional way of limiting vbv maxrate+bufsize?
Thanks in advance.
Rocinante is offline   Reply With Quote
Old 26th December 2018, 15:08   #1764  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Quote:
Originally Posted by Rocinante View Post
Wondering if there is any way to add function on GUI to precisely limit the max bit rate of an encoding or the option is just not possible on x264 and we are stuck with unconventional way of limiting vbv maxrate+bufsize?
x264 does not have a "maximum bitrate" option (other than the VBV options). And the options available in the GUI are, of course, a strict sub-set of the options that x264 offers.

Note: You can not have something like a "maximum bitrate" without a properly defined buffering model. And that's exactly what VBV does. So you actually want VBV here

See also:
https://slhck.info/video/2017/03/01/rate-control.html
→ section "Constrained Encoding (VBV)"
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 26th December 2018 at 15:22.
LoRd_MuldeR is offline   Reply With Quote
Old 26th December 2018, 15:57   #1765  |  Link
Rocinante
Registered User
 
Join Date: Jul 2018
Posts: 9
Quote:
Originally Posted by LoRd_MuldeR View Post
x264 does not have a "maximum bitrate" option (other than the VBV options). And the options available in the GUI are, of course, a strict sub-set of the options that x264 offers.

Note: You can not have something like a "maximum bitrate" without a properly defined buffering model. And that's exactly what VBV does. So you actually want VBV here

See also:
https://slhck.info/video/2017/03/01/rate-control.html
→ section "Constrained Encoding (VBV)"
Thanks for explaining on x264 and linking the vbv related articles, I got a better understanding of using vbv now.

Mainly the problem that I'm facing is how to properly define the buffering model for different types of video. Like there is a CBR/2pass encoding to get accurate targeted average bitrate even though the quality will differ in encoding different sources, so I was looking for a similar function that can produce constant result for max bitrate, and perhaps there is something that I did wrong, I can't seem to get that with vbv.

Quote:
If your encode always “maxes out” your maximum bitrate, your CRF was probably set too low.-[Understanding Rate Control Modes (x264, x265, vpx)-section "Constrained Encoding (VBV)"]
I can cope with the fact that it maxes out the maximum bitrate, but in my case, sometimes it will exceed it depending on sources and that's what troubling me.

Thanks again for your time.

Last edited by Rocinante; 26th December 2018 at 16:00.
Rocinante is offline   Reply With Quote
Old 26th December 2018, 16:25   #1766  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Quote:
Originally Posted by Rocinante View Post
Thanks for explaining on x264 and linking the vbv related articles, I got a better understanding of using vbv now.

Mainly the problem that I'm facing is how to properly define the buffering model for different types of video. Like there is a CBR/2pass encoding to get accurate targeted average bitrate even though the quality will differ in encoding different sources, so I was looking for a similar function that can produce constant result for max bitrate, and perhaps there is something that I did wrong, I can't seem to get that with vbv.


I can cope with the fact that it maxes out the maximum bitrate, but in my case, sometimes it will exceed it depending on sources and that's what troubling me.

Thanks again for your time.
If you use 2-Pass RC, there normally is no need to set VBV at all. And the same applies to CRF mode.

Just set the target average bitrate as needed (via "--bitrate" option) in order to hit the desired target file size, and let the encoder optimally distribute the available bits. If the encoder creates some bitrate "spikes" or bitrate "drops", then this is the perfectly normal and expected behavior of 2-Pass ABR (or CRF) mode – it happens for a reason! It's because the bits are "moved" to where they are actually needed

With VBV enabled, you are effectively forcing the encoder to create a more "uniform" distribution of the available bits. This avoids strong bitrate "spikes" or bitrate "drops", yes. But it also means that the distribution of the available bits is going to deviate from the "optimal" distribution that the encoder would have chosen without the VBV restrictions – sometimes more, sometimes less

In other words: VBV can only make the resulting video quality worse. In the best case, VBV won't affect video quality in a noticeable way. But, certainly, VBV restrictions do not improve video quality!


VBV is required for two scenarios:
  • Streaming: Here you necessarily need to avoid bitrate "spikes" that exceed the available network bandwidth in order to ensure "smooth" playback.
  • Hardware Players: These players read video data from the disc at a certain (maximum) speed, and they have limited buffering capabilities. So, again, strong bitrate "spikes" are to be avoided in order to ensure "smooth" playback.

(In both of these scenarios, we choose VBV as the lesser of two evils. And, in both scenarios, the required VBV parameters are obvious from the use case)
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 26th December 2018 at 17:05.
LoRd_MuldeR is offline   Reply With Quote
Old 26th December 2018, 17:45   #1767  |  Link
Rocinante
Registered User
 
Join Date: Jul 2018
Posts: 9
Quote:
Originally Posted by LoRd_MuldeR View Post
If you use 2-Pass RC, there normally is no need to set VBV at all. And the same applies to CRF mode.

Just set the target average bitrate as needed (via "--bitrate" option) in order to hit the desired target file size, and let the encoder optimally distribute the available bits. If the encoder creates some bitrate "spikes" or bitrate "drops", then this is the perfectly normal and expected behavior of 2-Pass ABR (or CRF) mode – it happens for a reason! It's because the bits are "moved" to where they are actually needed

With VBV enabled, you are effectively forcing the encoder to create a more "uniform" distribution of the available bits. This avoids strong bitrate "spikes" or bitrate "drops", yes. But it also means that the distribution of the available bits is going to deviate from the "optimal" distribution that the encoder would have chosen without the VBV restrictions – sometimes more, sometimes less

In other words: VBV can only make the resulting video quality worse. In the best case, VBV won't affect video quality in a noticeable way. But, certainly, VBV restrictions do not improve video quality!


VBV is required for two scenarios:
  • Streaming: Here you necessarily need to avoid bitrate "spikes" that exceed the available network bandwidth in order to ensure "smooth" playback.
  • Hardware Players: These players read video data from the disc at a certain (maximum) speed, and they have limited buffering capabilities. So, again, strong bitrate "spikes" are to be avoided in order to ensure "smooth" playback.

(In both of these scenarios, we choose VBV as the lesser of two evils. And, in both scenarios, the required VBV parameters are obvious from the use case)
Yes, I understand vbv is hurting the encoding quality and I can get accurate average bitrate with 2pass RC, but not maximum bitrate.

I'm in a third case scenarios now that due to a website streaming policy, they request a limit for a "maximum bitrate" value (such as all video max bitrate needs to be below 15Mb/s and below 8Mb/s average bitrate) instead of matching buffering capabilities or like a certain fixed vbv value used in bluray.

Last edited by Rocinante; 26th December 2018 at 17:47.
Rocinante is offline   Reply With Quote
Old 26th December 2018, 20:27   #1768  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Quote:
Originally Posted by Rocinante View Post
I'm in a third case scenarios now that due to a website streaming policy, they request a limit for a "maximum bitrate" value (such as all video max bitrate needs to be below 15Mb/s and below 8Mb/s average bitrate)
That's exactly the "streaming" scenario. So, VBV is what you want/need here.

As said before, there is no such thing as an "instantaneous" bitrate. Instead, a "bitrate" is always an average, computed/measured over a certain time interval.

More precisely: Every picture has a certain size, in bits, in the encoded bitstream. And, whenever the decoder is about to start decoding the next picture, we have to ensure that all bits required to decode that picture already are present in the buffer. That's what VBV is all about! And that's also why "--maxrate" (i.e the network bandwidth, i.e. the max. rate at which the buffer can be filled) is not useful without knowing/setting the "--bufsize" (size of the buffer) as well.

See also:
https://pdfs.semanticscholar.org/830...807507dfed.pdf
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 26th December 2018 at 20:53.
LoRd_MuldeR is offline   Reply With Quote
Old 14th January 2019, 13:30   #1769  |  Link
cadet51
Registered User
 
Join Date: Jan 2016
Posts: 5
Hello,
Since the x265 3.0+ versions, my simple x264 / 265 launcher gives me an error and I can not run an encode. Here is the error that appears.
With versions 2.9, no problem.
cordially
Quote:
[2019-01-14] [13:20:08] Simple x264 Launcher (Build # 1138), built 2018-10-12
[2019-01-14] [1:20:08 p.m.]
[2019-01-14] [13:20:08] Job started at 2019-01-14, 13:20:08.
[2019-01-14] [1:20:08 p.m.]
[2019-01-14] [13:20:08] Source file: D: \ Encode \ Avs And Graph \ 4K.avs
[2019-01-14] [13:20:08] Output file: D: \ Encode \ Encode in progress \ trans2.hevc
[2019-01-14] [1:20:08 p.m.]
[2019-01-14] [13:20:08] --- SYSTEMINFO ---
[2019-01-14] [1:20:08 p.m.]
[2019-01-14] [13:20:08] Binary Path: C: \ Program Files (x86) \ MuldeR \ Simple x264 Launcher v2
[2019-01-14] [13:20:08] Avisynth: Yes
[2019-01-14] [13:20:08] VaporSynth: No
[2019-01-14] [1:20:08 p.m.]
[2019-01-14] [13:20:08] --- SETTINGS ---
[2019-01-14] [1:20:08 p.m.]
[2019-01-14] [13:20:08] Encoder: x265 (HEVC / H.265), 64-bit (x64), 10-bit
[2019-01-14] [13:20:08] Source: Avisynth (avs)
[2019-01-14] [13:20:08] RC Mode: 2-Pass
[2019-01-14] [13:20:08] Preset: medium
[2019-01-14] [13:20:08] Tuning: <None>
[2019-01-14] [13:20:08] Profile: <Unrestricted>
[2019-01-14] [13:20:08] Custom: --no-slow-firstpass --level-idc = 5.1 --high-tier --block -3: -3 --ctu 64 --min -cu-size 8 --bframes 4 --b-adapter 2 --rc-lookahead 60 --lookahead-slices 1 --scenecut 40 --ref 4 --limit-refs 2 --merange 57 --subm 7 - -rect --amp --max-merge 5 --hevc-aq --qp -adaptation-range = 1.00 --tu-intra 4 --tu-inter 4 --limit yourself 4 --me umh --hdr --hdr-opt --master-display = G (13250,34500) B (7500,3000) R (34,000,16000) WP (15635,16450) L (10,000,000,1) --min-luma 0 - max -luma 1023 --gop-lookahead 54 --weightp --weightb --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --sar 1: 1
[2019-01-14] [1:20:08 p.m.]
[2019-01-14] [13:20:08] --- CHECK VERSION ---
[2019-01-14] [1:20:08 p.m.]
[2019-01-14] [13:20:08] Detect video encoder version:
[2019-01-14] [1:20:08 p.m.]
[2019-01-14] [13:20:08] Creating process:
[2019-01-14] [13:20:08] "C: \ Program Files (x86) \ MuldeR \ Simple x264 Launcher v2 \ toolset \ x64 \ x265_x64.exe" --version
[2019-01-14] [1:20:08 p.m.]
[2019-01-14] [13:20:08] x265 [info]: HEVC encode version 3.0_RC + 10-672ce0547e97
[2019-01-14] [13:20:08] x265 [info]: build info [Windows] [GCC 8.2.1] [64bit] 8bit + 10bit + 12bit
[2019-01-14] [13:20:08] x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[2019-01-14] [1:20:08 p.m.]
[2019-01-14] [13:20:08] FAILED TO DETERMINE VERSION INFO !!!
cadet51 is offline   Reply With Quote
Old 4th February 2019, 15:13   #1770  |  Link
kebulek
Registered User
 
kebulek's Avatar
 
Join Date: Oct 2008
Posts: 34
Quote:
4. Tune: introduce --tune animation option which improves encode quality for animated content
@LoRd_MuldeR: Please add this option to x265 GUI, thank you.
kebulek is offline   Reply With Quote
Old 8th February 2019, 13:35   #1771  |  Link
redbtn
Registered User
 
redbtn's Avatar
 
Join Date: Jan 2019
Location: Russia
Posts: 124
LoRd_MuldeR thank you for amazing GUI! Cant wait new build with native support x265 3.0+
-------
I'm sorry. I am stupid. Did not read the documentation before the question.

Outdated:
Only one question, is it possible to "Custom Encoder Parameters" input make in two lines, or resizeble?
If I have a lot of parameters, I can't see them all. Unfortunately it is very inconvenient, I have to copy them into a notepad and back to change

Last edited by redbtn; 19th February 2019 at 08:37.
redbtn is offline   Reply With Quote
Old 19th March 2019, 20:32   #1772  |  Link
fauxreaper
Registered User
 
Join Date: Oct 2014
Posts: 15
With x265 3.0 I'm seeing this error and can't run an encode.

[2019-03-19][16:18:40] x265 [info]: HEVC encoder version 3.0_Au+14-c7e5878bdd31
[2019-03-19][16:18:40] x265 [info]: build info [Windows][MSVC 1920][64 bit] 10bit
[2019-03-19][16:18:40] x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[2019-03-19][16:18:40]
[2019-03-19][16:18:40] FAILED TO DETERMINE VERSION INFO !!!
fauxreaper is offline   Reply With Quote
Old 27th March 2019, 02:42   #1773  |  Link
Chouonsoku
Registered User
 
Join Date: Sep 2007
Posts: 39
Quote:
Originally Posted by cadet51 View Post
Hello,
Since the x265 3.0+ versions, my simple x264 / 265 launcher gives me an error and I can not run an encode. Here is the error that appears.
With versions 2.9, no problem.
cordially
Quote:
Originally Posted by fauxreaper View Post
With x265 3.0 I'm seeing this error and can't run an encode.

[2019-03-19][16:18:40] x265 [info]: HEVC encoder version 3.0_Au+14-c7e5878bdd31
[2019-03-19][16:18:40] x265 [info]: build info [Windows][MSVC 1920][64 bit] 10bit
[2019-03-19][16:18:40] x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[2019-03-19][16:18:40]
[2019-03-19][16:18:40] FAILED TO DETERMINE VERSION INFO !!!
Launch with --skip-version-checks, no problem with x265 v3.0 builds here.
Chouonsoku is offline   Reply With Quote
Old 14th April 2019, 09:40   #1774  |  Link
r0lZ
PgcEdit daemon
 
r0lZ's Avatar
 
Join Date: Jul 2003
Posts: 7,349
Each times I launch the program, I see now a dialog with "Your version of Simple x264 Launcher is more than 6 months old!" and the Discard button is disabled, so the only choice is to click the Check for updates button. After the long check, the answer is always that I have already the latest version. Frustrating !
Could you please release a new version, just to get rid of that irritation dialog, and with the possibility to click the Discard button in the future ? Thanks !
__________________
r0lZ
PgcEdit homepage (hosted by VideoHelp)
BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV
r0lZ is offline   Reply With Quote
Old 14th April 2019, 16:56   #1775  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Quote:
Originally Posted by r0lZ View Post
Each times I launch the program, I see now a dialog with "Your version of Simple x264 Launcher is more than 6 months old!" and the Discard button is disabled, so the only choice is to click the Check for updates button. After the long check, the answer is always that I have already the latest version. Frustrating !
Could you please release a new version, just to get rid of that irritation dialog, and with the possibility to click the Discard button in the future ? Thanks !
Sorry, I'm panning to release a new version soon.
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Old 15th April 2019, 15:15   #1776  |  Link
StainlessS
HeartlessS Usurer
 
StainlessS's Avatar
 
Join Date: Dec 2009
Location: Over the rainbow
Posts: 7,267
From 1st post.
Quote:
System Requirements:

* Windows XP with Service Pack 2 or any later Windows system
* 64-Bit Windows is highly recommended (32-Bit Windows works as well)
* The CPU must support at least the MMX and SSE instruction sets
* Avisynth input only available with Avisynth 2.5+ installed
* VapourSynth input only available with VapourSynth R19+ installed
* YV16/YV24 color spaces require Avisynth 2.6 (see section 10)
From current version Readme
Quote:
2 System Requirements

Simple x264 Launcher is 100% standalone, i.e. it does not require Mircrosoft.NET, Java Runtime Environment or other "external" dependencies.

The required Qt DLLs as well as the encoder binaries are included with the application. Frameservers, like Avisynth or VapourSynth, may need to be installed separately though.

The minimum system requirements to run Simple x264/x265 Launcher are as follows:

Windows Vista with Service Pack 2 or any later Windows system – note that Windows XP is not supported anymore!
64-Bit editions of Windows are highly recommended, though 32-Bit editions will work as well
The CPU must support at least the MMX and SSE instruction sets
Avisynth input only available with Avisynth 2.6 installed – Avisynth 2.5.x is not recommended!
VapourSynth input only available with VapourSynth r24+ installed – Python is a prerequisite for VapourSynth!
YV16/YV24 color spaces require Avisynth 2.6 (see section 10)
Maybe update first post.
__________________
I sometimes post sober.
StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace

"Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???
StainlessS is offline   Reply With Quote
Old 16th April 2019, 22:13   #1777  |  Link
szabi
Registered User
 
Join Date: Nov 2004
Posts: 221
Hi

The latest program using x264-2935 which released 25-Sep-2018.
However newer version is available: x264-r2969 released 12-Mar-2019.
Can "x264_x86.exe" file be exchanged in "C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x86" directory to a new one with changing name of course?
Also can the "x264_x64.exe" exchanged?
Going to work it properly?

EDIT:
Anyway I did never try it, so are there any encoding speed advance by using 64bit architecture?


bye
szabi

Last edited by szabi; 16th April 2019 at 22:24.
szabi is offline   Reply With Quote
Old 16th April 2019, 22:23   #1778  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Quote:
Originally Posted by szabi View Post
Can "x264_x86.exe" file be exchanged in "C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x86" directory to a new one with changing name of course?
Also can the "x264_x64.exe" exchanged?
Going to work it properly?
Probably yes. Anyway, a new build of Simple x264/x265 Launcher will probably be soon™.
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Old 16th April 2019, 22:36   #1779  |  Link
szabi
Registered User
 
Join Date: Nov 2004
Posts: 221
Quote:
Originally Posted by LoRd_MuldeR View Post
Probably yes. Anyway, a new build of Simple x264/x265 Launcher will probably be soon™.
Hi

It was a really quick answer during editing my post, thanks.

bye
szabi
szabi is offline   Reply With Quote
Old 16th April 2019, 22:47   #1780  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Quote:
Originally Posted by szabi View Post
Anyway I did never try it, so are there any encoding speed advance by using 64bit architecture?
Yes, quite significant.
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 23:47.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.