| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
Assum 16:9 instead
Fixes https://forum.handbrake.fr/viewtopic.php?f=11&t=37836
|
| |
|
|
|
|
|
|
|
|
| |
ffmpeg doesn't set a default channel layout for audio that has no
explicit layout (e.g. pcm_216le). So we need to guess it from the
number of channels.
Fixes "no audio" in https://github.com/HandBrake/HandBrake/issues/1387
|
|
|
|
|
| |
*really* fix https://github.com/HandBrake/HandBrake/issues/1374 this
time.
|
|
|
|
| |
ffmpeg now requires this for video
|
|
|
|
| |
Fixes https://github.com/HandBrake/HandBrake/issues/1357
|
|
|
|
| |
check codec_name and profile_name for NULL before strstr search.
|
|
|
|
|
|
|
|
|
| |
ffmpeg is inconsistent in the format of returned profile names.
Sometimes the profile name includes the codec name and sometimes it does
not. So search for the codec name in the profile name and add codec
name if it's not there. Ugh!
Fixes https://github.com/HandBrake/HandBrake/issues/1375
|
|
|
|
|
|
|
|
|
|
|
|
| |
We had a hash of limited size where we stored frame durations in
encx264. This hash has not been necessary since we moved to using
libavformat for muxing. Since the limited size of the hash put
constraints on how short frame durations could be, I've eliminated it.
This means that after the encoder, hb_buffer_t s.stop and s.duration are
no longer valid. But since they are not used during muxing, this is not
a problem.
Fixes https://github.com/HandBrake/HandBrake/issues/1374
|
| |
|
|
|
|
|
| |
lzma may be used by the ffmpeg tiff decoder which can be used in
matroska files.
|
|
|
|
|
|
|
| |
If an audio track exists, but we receive no audio packets for that
track, this causes a condition that results in a NULL dereference.
Fixes https://github.com/HandBrake/HandBrake/issues/1358
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
avcodec_close(..)
Hence rename hb_avcodec_close -> hb_avcodec_free_context and pass the required ptr-ptr.
avcodec_free_context(..) ensures releasing of all resources attached to the context.
|
| |
|
|
|
|
|
|
| |
This fixes issue https://trac.ffmpeg.org/ticket/6304
See https://github.com/HandBrake/HandBrake/pull/981#issuecomment-347364763
See https://github.com/HandBrake/HandBrake/issues/974#issuecomment-353986772
|
|
|
|
|
|
|
|
| |
Patch 1/2 for https://github.com/HandBrake/HandBrake/issues/974
moving to FFMPEG 3.4.1 from LIBAV 12.2.
The re-ordering of to be linked modules was required to solve
statically linked dependencies. See libhb/module.defs etc.
|
|
|
|
|
|
| |
Previous value maxed out at lossless x264 4K or so, new value should be large enough for lossless x264 8K.
Fixes #1334.
|
|
|
|
|
|
|
| |
It's just wrong to begin with. And it may not be an escape char anyway.
Could be a directory separator.
Fixes https://github.com/HandBrake/HandBrake/issues/1249
|
| |
|
|
|
|
| |
filter_param_get_entry() was using the preset count for bounds checking.
|
| |
|
|
|
| |
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.
|