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. |
6th April 2020, 21:32 | #1641 | Link |
Registered User
Join Date: Aug 2005
Posts: 37
|
Here's some good settings for dynaudnorm when converting full dynamic range to laptop
After some analysis, I've arrived at some great settings when converting full dynamic range audio to something that's usable on a laptop:
Original audio was the first episode of Picard. Original audio specs after converting to Stereo, DPLII below: True Peak: 0.0dB Integrated Loudness [LKFS]: -23.6 (this is very quiet) Max momentary [LKFS]: -8.8 Max Short-term [LKFS]: -12.7 Loudness range [LU]: 22.1 (WAY too dynamic for comfortable listening on any laptop) After processing with dynamic audio normalization: True Peak: +2.1dB (technically this is not the best, but someone would need to integrate the ability to oversample or something to find true peak into dynaudionorm) Integrated Loudness [LKFS]: -14.3 (very close to Spotify standards) Max momentary [LKFS]: -4.6 Max Short-term [LKFS]: -6.5 Loudness range [LU]: 12.5 (usable and comfortable dynamic range) Settings used to reach this result: Frame Length: 145 Gaus filter win size: 31 Target Peak: 1.00 (when set lower, you'll get stronger peaks and less evenness in volume) Max gain factor: 60.0 (20, 30, and 40 work well but result in a greater LU range and Integrated Loudness of -15, -14.8, and -14.4 respectively) Compress factor: 30.0 I suspect there's likely a formula that could be applied for all the settings to reach optimal Integrated Loudness LKFS/LUFS, LU, and Max Momentary and Short-term LKFS/LUFS based on the original if we did enough testing and collected data on different tracks to find correlations... |
7th April 2020, 00:19 | #1642 | Link | |
Registered User
Join Date: Sep 2018
Posts: 391
|
Quote:
|
|
7th April 2020, 04:08 | #1644 | Link |
App Digger
Join Date: Sep 2018
Posts: 411
|
2.1.0.5 Tools > Folders > Templates default command line is wrong
In 2.1.0.5 beta, Tools > Folders > Templates menu tries to open a wrong folder, TemplatesV2.
Of course I can manually fix this by changing the default command line from Code:
"%settings_dir%TemplatesV2" Code:
"%settings_dir%Templates" |
7th April 2020, 15:58 | #1646 | Link |
Registered User
Join Date: Feb 2002
Posts: 758
|
Question, in StaxRip Remove Grain Repair is added something like this by default
FFVideoSource("............. Processed = RemoveGrain() Repair(Processed) ------------------------------------------------- In the manual of RgTools it suggests using it in another way. Passing the untouched video like this Unprocessed = FFVideoSource("............. Processed = RemoveGrain(Unprocessed) Repair(Processed, Unprocessed) ------------------------------------------------- I have tested both scripts and I get 2 different results. The second method noted in the manual gives more details and seems better. Anyone knows why? In the first method inserted by Staxrip, the unprocessed clip is not passed to Repair() function? Doesn't Repair() get the current clip by default if you don't mention it? |
7th April 2020, 18:42 | #1647 | Link | |
Registered User
Join Date: Sep 2018
Posts: 391
|
Quote:
--crf 16 --level-idc 5.1 --output-depth 10 --vbv-bufsize 50000 --vbv-maxrate 60000 --bframes 8 --ref 5 --max-luma 1023 --hdr-opt --no-rect This is set to a medium preset and my crf I adjust according to the size I want of my file. I test until it hits a bit-rate I like then I stick with that crf. Depending on the film it's as low as 9 all the way up to 19. My file sizes are usually in the 15 to 20gb size depending on film. |
|
7th April 2020, 19:17 | #1648 | Link |
Registered User
Join Date: Jan 2015
Posts: 286
|
A request:
I have compiled the new x265.exe 3.3 + 18 (x265_git branch) and always get an error message when using the bit depth 10 bit and 12 bit. If you have the time and desire, please download and test x265.exe 3.3 + 19 (x265_hg branch), the error also occurs here. You can report briefly if possible. |
7th April 2020, 21:02 | #1649 | Link | |
Registered User
Join Date: Feb 2002
Posts: 758
|
Quote:
What is your processor and memory? Mine: CPU : Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz GPU : NVIDIA GeForce GTX 980 Ti Interestingly staxrip log does not include the memory. RAM 64GB |
|
7th April 2020, 21:34 | #1650 | Link | ||
App Digger
Join Date: Sep 2018
Posts: 411
|
Quote:
I downloaded x265-3.3+19-1d2f556_gcc100-AVX2.7z, put the files in D:\Work\tmp\ and test-encoded a UHD HDR video via avs2pipe with the following command line: Quote:
Code:
avs2pipemod[info]: writing 500 frames of 25/1 fps, 1280x720, sar 0:0, YUV-420-planar-10bit progressive video. avs2pipemod[info]: finished, wrote 500 frames [100%]. avs2pipemod[info]: total elapsed time is 93.899 sec. Program 'x265-10b.exe' failed to run: Exception of type 'System.OutOfMemoryException' was thrown.At line:1 char:152 + ... Demo.avs" | D:\Work\tmp\x265-10b.exe --crf 27 --output-depth 10 --mas ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~. At line:1 char:1 + D:\Utilities\StaxRip\Apps\Support\avs2pipemod\avs2pipemod64.exe -y4mp ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ResourceUnavailable: (:) [], ApplicationFailedException + FullyQualifiedErrorId : NativeCommandFailed I ran the same encode using the x265 build by Patman, which does not produce any error run in StaxRip, but I get the same error in PowerShell as well. What the heck is going on? Well, this is something I wasn't aware of, but at least I can say that x265-3.3+19-1d2f556_gcc100-AVX2.7z is OK (at least the 10-bit version). Last edited by JKyle; 7th April 2020 at 23:20. |
||
8th April 2020, 16:59 | #1653 | Link | |
App Digger
Join Date: Sep 2018
Posts: 411
|
Quote:
Code:
x265 [info]: HEVC encoder version 3.3+19-1d2f556ffb12 x265 [info]: build info [Windows][GCC 10.0.1][64 bit] 8bit+10bit+12bit x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2 x265 [error]: internalBitDepth must match compiled bit depth x265 [error]: x265_encoder_open() failed for Enc, aborted at input frame 1, output frame 0 Code:
x265 [info]: HEVC encoder version 3.3+10-g08d895bb6 x265 [info]: build info [Windows][GCC 10.0.1][64 bit] 12bit x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2 x265 [info]: Main 12 profile, Level-3.1 (Main tier) x265 [info]: Thread pool created using 4 threads ... Yours can but the official x265 cannot. Last edited by JKyle; 8th April 2020 at 17:17. |
|
8th April 2020, 18:39 | #1654 | Link | |||
Registered User
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
|
Quote:
https://forum.doom9.org/showthread.php?t=180438 Quote:
Quote:
Code:
cmd /s /c --% "regular command line between this quotes" That is similar to what staxrip does, calling cmd /s /c "" with the dotnet Process class with shellex disabled, it uses CreateProcess in Win32. I think it was quot27 who gave me this clue. In the next build there are some terminal related improvements: https://github.com/staxrip/staxrip/b...r/Changelog.md
__________________
https://github.com/stax76/software-list https://www.youtube.com/@stax76/playlists Last edited by stax76; 8th April 2020 at 18:41. |
|||
8th April 2020, 19:31 | #1656 | Link |
Registered User
Join Date: Jan 2015
Posts: 286
|
THX for testing JKyle, that's the point. I want to update my x265 builds, but with this known error i won't to build new versions. I hope the x265 devs can help with this problem. Till version x265-3.3+15 everything works fine, but after that version the error ocurrs. The offical build worked also fine till version 3.3+10. I hope other users can confirm this error.
Last edited by Patman; 8th April 2020 at 19:35. |
8th April 2020, 20:27 | #1657 | Link | |
App Digger
Join Date: Sep 2018
Posts: 411
|
Quote:
Thank you for the pointer. |
|
8th April 2020, 21:03 | #1659 | Link | |
Registered User
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
|
Recently yes, and also thanks for the command line example.
Quote:
__________________
https://github.com/stax76/software-list https://www.youtube.com/@stax76/playlists |
|
9th April 2020, 06:44 | #1660 | Link | |
Registered User
Join Date: Sep 2018
Posts: 391
|
Quote:
For encoding 4K you pretty much are going to be encoding for ever regardless. |
|
Tags |
aac, hdr, hevc, nvenc, staxrip, x264, x265 |
Thread Tools | Search this Thread |
Display Modes | |
|
|