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

Closed Thread
 
Thread Tools Search this Thread Display Modes
Old 28th September 2019, 18:26   #981  |  Link
jlw_4049
Registered User
 
Join Date: Sep 2018
Posts: 391
Quote:
Originally Posted by -QfG- View Post
Use this Source Filter for force YUV 4.2.0 10-Bit (HEVC Input) and 10-Bit pipeline.
Is this nessecary to get the 10 bit pipeline for HDR?

Sent from my SM-G965U1 using Tapatalk
jlw_4049 is offline  
Old 28th September 2019, 19:12   #982  |  Link
-QfG-
QfG Group Germany
 
-QfG-'s Avatar
 
Join Date: Oct 2018
Location: Germany
Posts: 245
10-Bit Pipeline for 10-Bit Input. Every Retail movie with the HEVC Codec is encoded in 10-Bit (Also BT709 Content). With this string (colorspace = "YUV420P10") you Force Avisynth to the 10-Bit Input.
If you leave the string empty, FFVideoSource will Autodetect the Input. This works well, too.

Example:

If you convert a 1080p SDR 8-Bit movie with x265 to a 10-Bit HEVC SDR movie, you use the 8-Bit pipeline:
Quote:
FFVideoSource("%source_file%", cachefile = "%source_temp_file%.ffindex", colorspace = "YUV420P8")
The output bitdepth will be set with the x265 Codec Settings (--output-depth 10 & the Main10 profile).

INPUT=Avisynth
OUTPUT=Encoder

Last edited by -QfG-; 28th September 2019 at 19:15.
-QfG- is offline  
Old 28th September 2019, 19:46   #983  |  Link
jlw_4049
Registered User
 
Join Date: Sep 2018
Posts: 391
Quote:
Originally Posted by -QfG- View Post
10-Bit Pipeline for 10-Bit Input. Every Retail movie with the HEVC Codec is encoded in 10-Bit (Also BT709 Content). With this string (colorspace = "YUV420P10") you Force Avisynth to the 10-Bit Input.
If you leave the string empty, FFVideoSource will Autodetect the Input. This works well, too.

Example:

If you convert a 1080p SDR 8-Bit movie with x265 to a 10-Bit HEVC SDR movie, you use the 8-Bit pipeline:


The output bitdepth will be set with the x265 Codec Settings (--output-depth 10 & the Main10 profile).

INPUT=Avisynth
OUTPUT=Encoder
So I can leave the custom settings alone for the pipeline as long as its empty?

Sent from my SM-G965U1 using Tapatalk
jlw_4049 is offline  
Old 28th September 2019, 20:07   #984  |  Link
-QfG-
QfG Group Germany
 
-QfG-'s Avatar
 
Join Date: Oct 2018
Location: Germany
Posts: 245
Yes, in most cases FFVS will recognize the input correctly and x265 will automatically work with the data it gets from y4m.
-QfG- is offline  
Old 28th September 2019, 20:23   #985  |  Link
jlw_4049
Registered User
 
Join Date: Sep 2018
Posts: 391
Quote:
Originally Posted by -QfG- View Post
Yes, in most cases FFVS will recognize the input correctly and x265 will automatically work with the data it gets from y4m.
What way do you recommend then? The above instructions. Do you think it's good enough to leave it blank?

Sent from my SM-G965U1 using Tapatalk
jlw_4049 is offline  
Old 28th September 2019, 20:57   #986  |  Link
suarsg
Registered User
 
Join Date: Dec 2018
Posts: 21
Quote:
Originally Posted by jlw_4049 View Post
Shit. Wonder how many I've encoded with older versions.
You can go to your AppData/Roaming/StaxRip folder, the old logs might still be there. You can check for every encode you did if it was 8bit or 10bit.
suarsg is offline  
Old 28th September 2019, 21:01   #987  |  Link
jlw_4049
Registered User
 
Join Date: Sep 2018
Posts: 391
Quote:
Originally Posted by suarsg View Post
You can go to your AppData/Roaming/StaxRip folder, the old logs might still be there. You can check for every encode you did if it was 8bit or 10bit.
What string of words am I looking for?

Sent from my SM-G965U1 using Tapatalk
jlw_4049 is offline  
Old 28th September 2019, 21:18   #988  |  Link
-QfG-
QfG Group Germany
 
-QfG-'s Avatar
 
Join Date: Oct 2018
Location: Germany
Posts: 245
Quote:
Originally Posted by jlw_4049 View Post
What way do you recommend then? The above instructions. Do you think it's good enough to leave it blank?

Sent from my SM-G965U1 using Tapatalk
If you don't know what you do, leave it blank.

Quote:
What string of words am I looking for?
Search for the Line with your encoding log.
Quote:
-------------- Video encoding using x265 3.1+19 Wolfberry --------------

"E:\VIDEOTOOLS\AVIS riPPen\StaxRip-x64-2.0.4.3-beta\Apps\Support\avs2pipemod\avs2pipemod64.exe" -y4mp "E:\Video\PitchBlack\Timeline 1_temp\Timeline 1.avs" | "E:\VIDEOTOOLS\AVIS riPPen\StaxRip-x64-2.0.4.3-beta\Apps\Encoders\x265\x265.exe" --crf 16 --preset slow --qcomp 0.7 --no-open-gop --chromaloc 2 --no-info --aud --input-depth 10 --no-strong-intra-smoothing --level-idc 5.1 --sar 1 --aq-mode 1 --selective-sao 0 --no-sao --me umh --repeat-headers --deblock -3:-3 --no-open-gop --uhd-bd --min-keyint 1 --keyint 24 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --range limited --bframes 4 --hrd --vbv-bufsize 35000 --vbv-maxrate 40000 --hdr --output-depth 10 --hdr-opt --max-cll "1000,400" --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --frames 1357 --y4m --output "E:\Video\PitchBlack\Timeline 1_temp\Timeline 1_out.hevc" -

avs2pipemod[info]: writing 1357 frames of 24000/1001 fps, 3840x2160,
sar 0:0, YUV-420-planar-10bit progressive video.
y4m [info]: 3840x2160 fps 24000/1001 i420p10 sar 1:1 unknown frame count

Last edited by -QfG-; 28th September 2019 at 21:23.
-QfG- is offline  
Old 28th September 2019, 21:26   #989  |  Link
jlw_4049
Registered User
 
Join Date: Sep 2018
Posts: 391
Quote:
Originally Posted by -QfG- View Post
If you don't know what you do, leave it blank.



Search for the Line with your encoding log.
Thank you!

Sent from my SM-G965U1 using Tapatalk
jlw_4049 is offline  
Old 29th September 2019, 02:05   #990  |  Link
Atlantis
Registered User
 
Join Date: Feb 2002
Posts: 758
Quote:
Originally Posted by suarsg View Post
I have now done some test encodes with the exact same settings in 2.0.4.0 vs 2.0.2.1 vs source. What I previously thought were just "encoding artefacts" turned out to be the result of some weird conversion. The 2.0.4.0 encoded sample, when comparing frame for frame zoomed in, looks much much closer to the original source. For example I can see there's some slight red banding in the source. The banding in the newer encode looks pretty much the same. The banding in the "8bit"-version looks very different and is even shifted. So there was definitely something wonky going on.
I'm glad you reached the same conclusion. What tool do you use to do the frame by frame comparison? Do you know anything better than the tool that is already provided with Staxrip?
Atlantis is offline  
Old 29th September 2019, 02:18   #991  |  Link
Atlantis
Registered User
 
Join Date: Feb 2002
Posts: 758
Question, does having more RAM result in faster encodes? (encoding with x265) I tested two almost identical PCs and one encodes faster.

encoded 1146 frames in 516.31s (2.22 fps), 20859.12 kb/s, Avg QP:27.55
encoded 1146 frames in 403.19s (2.84 fps), 20859.12 kb/s, Avg QP:27.55

The faster PC has everything the same except double the RAM and a little better Graphics Card which I suppose doesn't do anything in x265.
Atlantis is offline  
Old 29th September 2019, 02:23   #992  |  Link
jlw_4049
Registered User
 
Join Date: Sep 2018
Posts: 391
Quote:
Originally Posted by Atlantis View Post
Question, does having more RAM result in faster encodes? (encoding with x265) I tested two almost identical PCs and one encodes faster.

encoded 1146 frames in 516.31s (2.22 fps), 20859.12 kb/s, Avg QP:27.55
encoded 1146 frames in 403.19s (2.84 fps), 20859.12 kb/s, Avg QP:27.55

The faster PC has everything the same except double the RAM and a little better Graphics Card which I suppose doesn't do anything in x265.
Is the one with more ram faster ram perhaps? Is the one with less ram single channel memory vs the other dual channel memory?

Is CPU cooling in both computers the same or is the faster one possibly equipped with a better cooler?

Last edited by jlw_4049; 29th September 2019 at 02:31.
jlw_4049 is offline  
Old 29th September 2019, 02:40   #993  |  Link
Atlantis
Registered User
 
Join Date: Feb 2002
Posts: 758
The cooling is the same, all is the same except these 2.

one is
GSKILL RIPJAWS V DDR4-3000 PC4-24000 16GB x 4 = 64GB RAM

the other is
Corsair DDR4 8GB 2400MHZ Vengeance LPX CMK8GX4M1A2400C14 x 4 = 32 GB RAM

The Graphics Card doesn't matter, right?
Atlantis is offline  
Old 29th September 2019, 03:13   #994  |  Link
stax76
Registered User
 
stax76's Avatar
 
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
Code:
### 2.0.4.5 Beta

Thanks to Patman for providing the download links of the tools !!!

- update: JPSDR 3.1.3
- update: nvenc 4.50
- update: AVSMeter 2.9.6
- update: DGHDRtoSDR 1.12
- update: mvtools2 2.7.41
- update: FFT3dFilter 2.6.7
- update: TIVTC 1.0.14
- update: RgTools 0.98
- update: havsfunc r32
- update: DFTTest r6
- update: TCanny r12
- update: BM3D r8
- update: L-Smash Works 2019-09-17 HolyWu
- update: x265 3.2+3-fdd69a76688 Patman
- update: ffmpeg 2019-09-27 Patman

- new: x265 switch --selective-sao added
- new: L-Smash Works parameters prefer_hw 3 HW auto added to menu
- new: the way --vbr-quality works in nvenc was changed,
       if it's value is -1 the bitrate in the main dialog is used,
       if it's higher then -1 the bitrate is set to 0
- new: add support of video track title/name using MP4Box
- new: simple QP mode added to nvenc to use one instead of three QP values
- new: the menu renderer has now Win 10 style arrows for sub menu indication
- new: icons added to filter list and script editor, shortcuts added to script editor
- new: the preview can be closed by clicking in the top right corner
- new: in the script editor there are now two players available,
       mpv.net and whatever is registered for mkv, mpc-be supports vpy playback
- new: the way filters are added, replaced and inserted in the script editor
       was changed in order to improve the menu performance
- new: in the main menu a sub menu was added: Apps > Script Info,
       it contains avsmeter, vspipe and avs2pipemod for showing
       info about the currently active AviSynth or VapourSynth script,
       vspipe and avs2pipemod show parameters like bit depth, colorspace and framecount.
       In the script editor there is a new 'Script Info' menu item (Ctrl+I) doing the same.
- new: the mediainfo dialog shows the formats in the tab captions
- new: the mediainfo dialog has a new feature to move
       to the next and previous file via menu and shortcut

- fix: docs weren't built automatically
- fix: some bugs were fixed in the nvenc command line import feature
https://www.dropbox.com/sh/4ctl2y928...dd3yqcAHa?dl=0

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR
stax76 is offline  
Old 29th September 2019, 04:24   #995  |  Link
jlw_4049
Registered User
 
Join Date: Sep 2018
Posts: 391
Quote:
Originally Posted by Atlantis View Post
The cooling is the same, all is the same except these 2.

one is
GSKILL RIPJAWS V DDR4-3000 PC4-24000 16GB x 4 = 64GB RAM

the other is
Corsair DDR4 8GB 2400MHZ Vengeance LPX CMK8GX4M1A2400C14 x 4 = 32 GB RAM

The Graphics Card doesn't matter, right?
Yeah it's the RAM speed that's causing the difference. Honestly its such a small difference I I wouldnt worry about it.

If you're any good at it you could try overclocking that kit of RAM but in my opinion it's not worth it. Especially for an encoding machine as you want maximum stability.
Quote:
Originally Posted by stax76 View Post
Code:
### 2.0.4.5 Beta

Thanks to Patman for providing the download links of the tools !!!

- update: JPSDR 3.1.3
- update: nvenc 4.50
- update: AVSMeter 2.9.6
- update: DGHDRtoSDR 1.12
- update: mvtools2 2.7.41
- update: FFT3dFilter 2.6.7
- update: TIVTC 1.0.14
- update: RgTools 0.98
- update: havsfunc r32
- update: DFTTest r6
- update: TCanny r12
- update: BM3D r8
- update: L-Smash Works 2019-09-17 HolyWu
- update: x265 3.2+3-fdd69a76688 Patman
- update: ffmpeg 2019-09-27 Patman

- new: x265 switch --selective-sao added
- new: L-Smash Works parameters prefer_hw 3 HW auto added to menu
- new: the way --vbr-quality works in nvenc was changed,
       if it's value is -1 the bitrate in the main dialog is used,
       if it's higher then -1 the bitrate is set to 0
- new: add support of video track title/name using MP4Box
- new: simple QP mode added to nvenc to use one instead of three QP values
- new: the menu renderer has now Win 10 style arrows for sub menu indication
- new: icons added to filter list and script editor, shortcuts added to script editor
- new: the preview can be closed by clicking in the top right corner
- new: in the script editor there are now two players available,
       mpv.net and whatever is registered for mkv, mpc-be supports vpy playback
- new: the way filters are added, replaced and inserted in the script editor
       was changed in order to improve the menu performance
- new: in the main menu a sub menu was added: Apps > Script Info,
       it contains avsmeter, vspipe and avs2pipemod for showing
       info about the currently active AviSynth or VapourSynth script,
       vspipe and avs2pipemod show parameters like bit depth, colorspace and framecount.
       In the script editor there is a new 'Script Info' menu item (Ctrl+I) doing the same.
- new: the mediainfo dialog shows the formats in the tab captions
- new: the mediainfo dialog has a new feature to move
       to the next and previous file via menu and shortcut

- fix: docs weren't built automatically
- fix: some bugs were fixed in the nvenc command line import feature
https://www.dropbox.com/sh/4ctl2y928...dd3yqcAHa?dl=0

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR
Wow! Massive update! I'm solid on 2.0.4.0 so I might wait for next stable release.
Sent from my SM-G965U1 using Tapatalk
jlw_4049 is offline  
Old 29th September 2019, 07:50   #996  |  Link
JKyle
App Digger
 
JKyle's Avatar
 
Join Date: Sep 2018
Posts: 411
Quote:
Originally Posted by stax76 View Post
Code:
### 2.0.4.5 Beta

- new: the way --vbr-quality works in nvenc was changed,
       if it's value is -1 the bitrate in the main dialog is used,
       if it's higher then -1 the bitrate is set to 0
- new: add support of video track title/name using MP4Box
- new: simple QP mode added to nvenc to use one instead of three QP values
Good. Smart insertion of the --vbr-quality parameter.

BTW, I'd appreciate it if I can see the quality parameter value in the output file info pane on the main window when I set --vbr-quality to a positive number. It currently shows '0' instead of a really value.

JKyle is offline  
Old 29th September 2019, 08:24   #997  |  Link
stax76
Registered User
 
stax76's Avatar
 
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
It's a quality mode and I missed setting the main window to quality mode view, 2.0.4.6 Beta is available.
stax76 is offline  
Old 29th September 2019, 17:01   #998  |  Link
Atlantis
Registered User
 
Join Date: Feb 2002
Posts: 758
Quote:
Originally Posted by jlw_4049 View Post
Yeah it's the RAM speed that's causing the difference. Honestly its such a small difference I I wouldnt worry about it.
Oh it's a huge difference. Encoding a 2 hours movie

with 2.22 fps takes 22 hours.
with 2.84 fps takes 17 hours.

The difference is 5 hours and it's worth it, every second counts.

If your source is 1080 8bit, it doesn't matter much but if you are encoding 4K HDR 10bit, everything counts and it takes a long time.

Question for suarsg. With your encoding test, did you also write down the speed? Did you notice that with the new correct method, it takes longer to encode?

Not only we have to redo all our previous work, we didn't even realize that the speed was not right and it was not the real speed. We have to redo all and with even slower speed!
Atlantis is offline  
Old 29th September 2019, 18:31   #999  |  Link
Patman
Registered User
 
Patman's Avatar
 
Join Date: Jan 2015
Posts: 286
Quote:
Originally Posted by Natty View Post
I've updated my builds and add two versions of x265. The one from git (x265-3.2...) and the modifided version (x265_custom_...) with custom progress bar like MeteorRain uses. THX for code @ MeteorRain
__________________
Tools for StaxRip | x264 - x265
Patman is offline  
Old 29th September 2019, 19:59   #1000  |  Link
suarsg
Registered User
 
Join Date: Dec 2018
Posts: 21
Quote:
Originally Posted by Atlantis View Post
Question for suarsg. With your encoding test, did you also write down the speed? Did you notice that with the new correct method, it takes longer to encode?

Not only we have to redo all our previous work, we didn't even realize that the speed was not right and it was not the real speed. We have to redo all and with even slower speed!
For me the speed hasn't changed much. Maybe yours are faster now because of a different x265-feature or some default changes? (like aq-mode defaults to 2 instead of 1 now)

As for your comparison question: I don't like the intergrated tool because you can't zoom in at 100%, which is really needed for comparing 4k. So what I'm doing: I use MPC-HC with madVR, open two videos, Ctrl+G to jump to a specific frame number, Alt+I to save a PNG of the frame in both players, and then open both PNGs in Photoshop, put them into one so I can quickly switch between the 2 layers and zoom around see the difference with just 1 click. You can also navigate 1 frame forward and 1 frame backward in MPC-HC which allows me to compare subsequent frames easily for both files. It's kinda tedious, but so far the most effective way I found.

It'd be amazing if the Video Comparison-Tool in StaxRip let me have pixel-perfect 100% zoom and drag around the frame (4k image on a non-4k-monitor). But I feel like the StaxRip-tool already has so many good features, I didn't wanna bother the dev with such a small quality-of-life issue

Last edited by suarsg; 29th September 2019 at 20:07.
suarsg is offline  
Closed Thread

Tags
aac, hdr, hevc, nvenc, staxrip, x264, x265

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 00:26.


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