| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
there is a redundant 'the the' in this string, please advise
|
|
|
| |
Found via `codespell -q 3 --skip="./gtk/po`
|
| |
|
|
|
|
| |
fixes https://forum.handbrake.fr/viewtopic.php?f=11&t=37311
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts 0e072aa42e3affd6280447317375460753f9284b and implements a proper fix for some frames not being prefiltered correctly. Turns out it was an issue with an uninitialized variable.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The multi-lib change actually happend in build 153
|
|
|
|
|
|
|
| |
Requires NASM to build
Unified 8 and 10 bit library support
AVX-512 optimizations
Various other bug fixes and improvements
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CSM is a Conservative Smoothing filter with Median-like tendencies.
Conservative Smoothing is a basic noise reduction method that ensures a given pixel is within the values of those around it. A value higher than all the others is clamped to the maximum value in the neighborhood. Likewise, a value lower than all the others is clamped to the minimum value in the neighborhood. Basically, pixel values that seem to "fit in" are left alone, and extreme values are brought in line.
CSM takes this a step further. A pixel not affected by the previous part of the algorithm is subjected to additional thresholding. If the pixel value is closer to the minimum or maximum neighborhood value than the median, it is clamped to the half-way point. Finally, a pixel still not affected is subjected to a third level of thresholding, clamping to the half-way point between the median and the previous half-way point. Any other pixel value is deemed close enough to its peers and left alone.
In effect, this creates a "soft" median-like filter, where relatively similar values are left alone and increasingly disparate values are nudged closer together.
Practically, CSM is the best prefilter to date for improving weight decisions with sources containing a type or amount of noise proving difficult for NLMeans to uniformly dampen or completely remove on its own. Additionally, it does not significantly alter the strength metric in most cases, so it can simply be enabled wherever desired. From what I can tell in my limited testing, the algorithm respects proper detail and edges well enough that it seems to be safe with nearly any source. Perhaps it should be the default if I ever get around to creating NLMeans 2.
Unlike the mean and median prefilters where a larger neighborhood increases the strength of the prefilter, a larger CSM neighborhood merely takes more pixels into account, theoretically decreasing the strength of the filter. In practice, the provided 3x3 and 5x5 neighborhoods typically do not produce significantly differing results.
Basic usage: Add y-prefilter=16 to your desired parameters and NLMeans will use CSM for weighting decisions. Use y-prefilter=2064 if you want to see the output of the prefilter itself—the visual effect is mild. Adjust these values to 32 and 2080 for a 5x5 neighborhood; 3x3 works well in all cases I've tried.
|
|
|
|
|
|
|
|
| |
Explicitly set all relevant rate control parameters when
querying for availability of a given rate control method.
I still "blame" Intel, as the existing code managed to
query ICQ availability for the H.264 encoder just fine.
|
| |
|
|
|
|
| |
Closes #1088.
|
|
|
|
|
|
|
|
|
|
|
| |
When the prefilter passthru flag is enabled, write the nlmeans prefilter
result into the "main" memory buffer (mem) instead of the prefilter one
(mem_pre) so that the prefilter result will be output as if it was the
result of the nlmeans filter itself.
Otherwise, when the passthru flag is enabled, the prefilter result is
lost and the filter effectively just outputs its source input without
any changes.
|
|
|
|
|
|
| |
In commit 29a49a8, the nlmeans_prefilter() call in nlmeans_filter_thread()
was fixed, but a corresponding change was not made to the similar
call site in nlmeans_filter_flush().
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* add sdtp (sample dependency) box to mp4
The AppleTV 4K requires this box in order to play 2160p60 video.
|
|
|
|
|
|
|
|
| |
The probe did not inspect enough data and did not always detect all
streams.
Thanks to josephpaul0
Fixes https://github.com/HandBrake/HandBrake/issues/1023
|
| |
|
| |
|
|
|
|
| |
Fixes https://github.com/HandBrake/HandBrake/issues/1017
|
|
|
|
|
| |
The new audio attributes were not checked correctly and filtered out any
audio tracks that had the DEFAULT flag.
|
|
|
|
|
|
|
| |
"Adaptive streaming" allows changing video parameters mid-stream at IDR
boundaries. Such changes require new SPS and PPS NALs at the IDR. MP4
supports this with 'avc3' and 'hev1' sample entry types.
|
| |
|
| |
|
|
|
| |
This is useful for scripts and other frontends that need to parse CLI output.
|
|
|
|
| |
See https://github.com/HandBrake/HandBrake/issues/833#issuecomment-333193971
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces the "New Folder" option in the presets menu. It enforces
the folder structure we have agreed to and hopefully helps the user keep
things organized.
Note that users are allowed to save a custom preset to the same
"Category" as an official preset. When they do this, a new custom
category is created with the same name and the preset is saved in that
folder.
|
|
|
|
| |
Synching up with https://github.com/HandBrake/HandBrake/issues/833
|
| |
|
|
|
| |
Fixes https://forum.handbrake.fr/viewtopic.php?f=5&t=37034
|
| |
|
| |
|
|
|
|
| |
the EOF flag before reciving a valid frame.
|
|
|
|
| |
Allows setting number of frames to process in parallel. For testing and experts wanting to fine tune the pipeline; e.g., fewer NLMeans threads may make x265 run slightly faster. Realistically, the defaults are the best choice for most everyone.
|