StaxRip

[Magik Mark]

JohnLai,

I'm now experimenting on CPU based encoding for x265. Can you assist on an optimum setting focusing on very good quality and very small file size. Thanks

[JohnLai]

JohnLai,

I'm now experimenting on CPU based encoding for x265. Can you assist on an optimum setting focusing on very good quality and very small file size. Thanks

-.-.....you should ask this question on (HEVC) subforum.

Anyway, I would propose you to use x264. Yes, you read it right. Reason being x264 is faster, mature, higher encoding speed (definition of higher encoding speed for software based encoding = real time 30fps or so..) and most importantly, better quality than x265 encoding right now.

x264 with slow preset, set higher reference frame (1080p = 4 frames, 720p = 9 frames, CRF = 20, use 10bit encoding (get x264 with --bit-depth=10, specifying -profile high10 later)

[NikosD]

New NVEncC v2.00β1 is out supporting HW decode and HW resize using CUVID.

HW accelerated codecs supported are:
H.264, MPEG1, MPEG2

[cegy]

@stax76 it seems i've came across a few bugs firstly... if you do set your demuxer/indexer to your favor demuxer/indexer it can cause issues when it comes to using the video comparison as it will try and use that demuxer/indexer which you set which can fail quite alot or badly however if its left as default (auto detect?) it will use ffms2 like it should do.... so would it be possible to set the default indexer only for the video comparison to ffms2 so there isn't any issues like this and works like it "should" do ever time no matter what demuxer/indexer you use ? :eek:

i've also notice that the default audio language being set for mkv/mp4 isn't being respected for some odd reason if i load a encoded audio file it will change from the default english (which i set) to undetermined which i find very odd as the only way to over come this is setting it to english every single time (not ideal if you only use one audio language) :confused: however... in 1.1.8 this wasn't an issue at all as it did respect the settings that the user set i.e english as even if the audio was encoded or the audio was auto loaded by itself it will keep it as english :cool: (both of these issues are still there even in the latest test version 2015-11-24)

p.s. i understand how you want the language detection to work when reading from the file to try and detect what language the audio is

[JohnLai]

New NVEncC v2.00β1 is out supporting HW decode and HW resize using CUVID.

HW accelerated codecs supported are:
H.264, MPEG1, MPEG2

Wow, I am totally amazed by nvencc v2.00β1 resizing speed.....[From 1080p to 720p]

nvencc64.exe -i test.mkv --avcuvid --output-res 1280x720 --codec h265 --cqp 20:22:25 -o output.mkv
Max B frames are 0 frames.
[100.0%] 34362 frames: 398.46 fps, 2136.07 kb/s, remain 0:00:00 2:13

encoded 34410 frames, 398.69 fps, 2133.29 kbps, 364.98 MB
encode time 0:01:26 / CPU Usage: 5.05

For comparison, staxrip with DSS2 LAVFilter DXVA Copy-Back + its built-in Bilinear resizer with setting below;

NVEncC64.exe --codec h265 --level 4.1 --bframes 0 --ref 0 --cqp 20:22:25

encoded 34409 frames, 314.94 fps, 2049.56 kbps, 350.64 MB
encode time 0:01:49 / CPU Usage: 29.87


Very impressive.....

Edit : CPU info = I5 3570K 4.2Ghz OC, just in case if someone wanna compare the Staxrip CPU based bilinear resizer.......and GTX970 in case anyone wanna check the gpu resizer?
Edit V2 : Hohoho........I wonder if rigaya can implement other form of resizing algorithm (bicubic? lanzcos? Catmul?), all hail rigaya!!~~
Edit V3 : Stax76~~~~I hope you can implement this functionality as soon as possible, seem like rigaya adds custom CUVID decoder to be used in conjunction with the gpu resizer. You might need to do extra coding XD.

[NikosD]

If you pipe QSV decoding and resizing with NVEncC encoding what is the speed ?

[JohnLai]

If you pipe QSV decoding and resizing with NVEncC encoding what is the speed ?

So, I simply check the staxrip's "Use QSVEncC as decoder", setting the resize and same nvenc encode options;

encoded 34404 frames, 338.14 fps, 265155.64 kbps, 45356.84 MB
encode time 0:01:42 / CPU Usage: 12.72
frame type IDR 34404
frame type I 34404, total size 45356.84 MB
encoded 34404 frames, 340.86 fps, 2255.76 kbps, 385.86 MB
encode time 0:01:41 / CPU Usage: 9.13

First 338.14fps with crazy amount of bitrate and size is QSVEncC decode usage.

Second 340.86fps is NvEncC encode usage.

But, QSVEncC VPP resizer is using better quality...the 8 tap polyphase thing?

Edit: In case you wanna know, it is a 24 minutes H.264 video without audio. So, I will not encounter the dreadful "Error in encoding pipeline".

[Magik Mark]

John can you assist on converting this handbrake preset to staxrip?

Preset 1
x265 Medium
CRF 26.5
aq_mode=1: aq_strength=2.00: qcomp=0.8: psy_rdoq=14.00
Denoise -> NLMeans -> Preset Ultra light -> Tune Film
Detelecine -> Default

Preset 2
x265 Fast
2 pass Ave bitrate 900kbps
aq_mode=1: aq_strength=2.00: qcomp=0.8: psy_rdoq=14.00
Denoise -> NLMeans -> Preset Ultra light -> Tune Film
Detelecine -> Default

[JohnLai]

John can you assist on converting this handbrake preset to staxrip?

Preset 1
x265 Medium
CRF 26.5
aq_mode=1: aq_strength=2.00: qcomp=0.8: psy_rdoq=14.00
Denoise -> NLMeans -> Preset Ultra light -> Tune Film
Detelecine -> Default

Preset 2
x265 Fast
2 pass Ave bitrate 900kbps
aq_mode=1: aq_strength=2.00: qcomp=0.8: psy_rdoq=14.00
Denoise -> NLMeans -> Preset Ultra light -> Tune Film
Detelecine -> Default

Wait a minute here......There are few problem with your so called "preset".

Preset 1 and 2
x265 Medium (x265 default preset, no issue here)
CRF 26.5 (The default recommended factor from x265 documentation is 28)
aq_mode=1: aq_strength=2.00: qcomp=0.8: psy_rdoq=14.00
Denoise -> NLMeans -> Preset Ultra light -> Tune Film
-.-? Why would you use these if you can simply use --tune grain

Oh...about deinterlacing part...........I wonder if you can use LAVF CUVID for the deinterlacing.....either this or wait rigaya to come out with his version of HW deinterlacing. Any comment before proceeding to staxrip guide or you wanna setup DSS2 LAVF CUVID?

[Magik Mark]

Thanks. I think CPU encoding is a lot better. We just have to be patient. Do you know any guides using x265 in transcoding videos? Maybe presets for different type of videos. Dark, action, dram etc.

[JohnLai]

Thanks. I think CPU encoding is a lot better. We just have to be patient. Do you know any guides using x265 in transcoding videos? Maybe presets for different type of videos. Dark, action, dram etc.

Sigh......I suggest you to wait 1 or 2 years before using x265. Current x265 still lack those "tune" preset compared to x264.


-.- Tell you something......using 10bit x265 -crf 28 -preset medium encoding to encode hevc 1080p (note: no resizing, source video is hardware decoded) with core I5-3570K 4.2Ghz is very slow. The encoding fps is averaging 5-8 fps. I not sure if the trade off is worth it.

You might want to take a look on some sample quality comparison here;

http://forum.doom9.org/showthread.php?p=1733375#post1733375

http://forum.doom9.org/showthread.php?p=1733664#post1733664

[Lupissimo]

After "upgrading" to Win 10 I got the following error trying a reencode:
------------------------------------------------------------
Environment
------------------------------------------------------------

StaxRip x64 : 1.3.1.7
OS : Windows 10 Pro
Language : German (Germany)
CPU : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
GPU : NVIDIA GeForce GTX 750

------------------------------------------------------------
Source file MediaInfo
------------------------------------------------------------

E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar.mkv

General
Unique ID : 193564096130464958721878217292158638466 (0x919F16C177DF236F9B582AFC921C9982)
Complete name : E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar.mkv
Format : Matroska
Format version : Version 2
File size : 3.44 GiB
Duration : 1h 55mn
Overall bit rate : 4 254 Kbps
Encoded date : UTC 2012-12-17 16:44:08
Writing application : mkvmerge v5.7.0 ('The Whirlwind') built on Jul 8 2012 20:08:51
Writing library : libebml v1.2.3 + libmatroska v1.3.0

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L3.1
Format settings, CABAC : No
Format settings, ReFrames : 2 frames
Muxing mode : Header stripping
Codec ID : V_MPEG4/ISO/AVC
Duration : 1h 55mn
Bit rate : 3 977 Kbps
Width : 1 276 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.181
Stream size : 3.22 GiB (93%)
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Muxing mode : Header stripping
Codec ID : A_AC3
Duration : 1h 55mn
Bit rate mode : Constant
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 44.1 KHz
Compression mode : Lossy
Stream size : 159 MiB (5%)
Language : English
Default : Yes
Forced : No

Text #1
ID : 3
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Language : English
Default : Yes
Forced : No

Text #2
ID : 4
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Language : Romanian
Default : No
Forced : No


------------------------------------------------------------
Demux audio using mkvextract
------------------------------------------------------------

"C:\StaxRip_x64_1.3.1.7_beta\Apps\MKVToolNix\mkvextract.exe" tracks "E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar.mkv" 1:"E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar ID2 English.ac3" --ui-language en

Extracting track 1 with the CodecID 'A_AC3' to the file 'E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar ID2 English.ac3'. Container format: Dolby Digital (AC3)

Start: 10:00:39
End: 10:01:34
Duration: 00:00:54

General
Complete name : E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar ID2 English.ac3
Format : AC-3
Format/Info : Audio Coding 3
File size : 155 MiB
Duration : 1h 53mn
Overall bit rate mode : Constant
Overall bit rate : 192 Kbps

Audio
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Duration : 1h 53mn
Bit rate mode : Constant
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 44.1 KHz
Compression mode : Lossy
Stream size : 155 MiB


------------------------------------------------------------
Demux subtitles using mkvextract
------------------------------------------------------------

"C:\StaxRip_x64_1.3.1.7_beta\Apps\MKVToolNix\mkvextract.exe" tracks "E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar.mkv" 2:"E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar ID3 English.srt" --ui-language en

Extracting track 2 with the CodecID 'S_TEXT/UTF8' to the file 'E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar ID3 English.srt'. Container format: SRT text subtitles

Start: 10:01:34
End: 10:01:41
Duration: 00:00:06


------------------------------------------------------------
Demux chapters using mkvextract
------------------------------------------------------------

"C:\StaxRip_x64_1.3.1.7_beta\Apps\MKVToolNix\mkvextract.exe" chapters "E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar.mkv" --redirect-output "E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar_Chapters.xml"


Start: 10:01:42
End: 10:01:42
Duration: 00:00:00


------------------------------------------------------------
Index with ffmsindex
------------------------------------------------------------

"C:\StaxRip_x64_1.3.1.7_beta\Apps\Plugins\both\ffms2\ffmsindex.exe" "E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar.mkv" "E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar.ffindex"

Writing index... done.

Start: 10:01:44
End: 10:01:51
Duration: 00:00:07


------------------------------------------------------------
Script
------------------------------------------------------------

FFVideoSource("E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar.mkv", cachefile = "E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar.ffindex")
Crop(0, 0, -4, -0)

------------------------------------------------------------
Script Properties
------------------------------------------------------------

source frame count : 166612
source frame rate : 23.976024
source duration : 01:55:49.1090000
target frame count : 166612
target frame rate : 23.976024
target duration : 01:55:49.1090000

------------------------------------------------------------
Audio Source File MediaInfo
------------------------------------------------------------

General
Complete name : E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar ID2 English.ac3
Format : AC-3
Format/Info : Audio Coding 3
File size : 155 MiB
Duration : 1h 53mn
Overall bit rate mode : Constant
Overall bit rate : 192 Kbps

Audio
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Duration : 1h 53mn
Bit rate mode : Constant
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 44.1 KHz
Compression mode : Lossy
Stream size : 155 MiB


------------------------------------------------------------
Encoding using NVEncC
------------------------------------------------------------

"C:\StaxRip_x64_1.3.1.7_beta\Apps\NVEncC\NVEncC64.exe" --cqp 20:23:25 --input "E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar_new.avs" --output "E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar_new_out.h264"

E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar_new.avs
NVEnc 1.10 (x64), using NVENC API v5.0
OS Version Unknown (x64)
CPU Intel Core2 Duo E8400 @ 3.00GHz (2C/2T)
GPU GeForce GTX 750 (4 EU) @ 1110 MHz (353.82)
Input Buffers CUDA, 16 frames
Input Info Avisynth 2.60 (yv12) -> nv12 [SSE2], 1272x720, 24000/1001 fps
Output Info H.264/AVC high
1272x720p 1:1 23.976fps (24000/1001fps)
Rate Control CQP
CQP I:20 P:23 B:25
GOP length 240 frames
B frames 3 frames
Ref frames 3 frames
MV Quality Q-pel
CABAC/deblock cabac / on

------------------------------------------------------------
Error Encoding using NVEncC
------------------------------------------------------------

Encoding using NVEncC failed with error code -1073741819

E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar_new.avs
NVEnc 1.10 (x64), using NVENC API v5.0
OS Version Unknown (x64)
CPU Intel Core2 Duo E8400 @ 3.00GHz (2C/2T)
GPU GeForce GTX 750 (4 EU) @ 1110 MHz (353.82)
Input Buffers CUDA, 16 frames
Input Info Avisynth 2.60 (yv12) -> nv12 [SSE2], 1272x720, 24000/1001 fps
Output Info H.264/AVC high
1272x720p 1:1 23.976fps (24000/1001fps)
Rate Control CQP
CQP I:20 P:23 B:25
GOP length 240 frames
B frames 3 frames
Ref frames 3 frames
MV Quality Q-pel
CABAC/deblock cabac / on


Start: 10:05:43
End: 10:05:43
Duration: 00:00:00

Any idea what I did wrong?

[JohnLai]

Any idea what I did wrong?

1073741819 is access violation error code.

-.- Anyway, you better update your staxrip first.....

https://github.com/stax76/staxrip/wiki/Development-Changelog

Scroll down to get the download link.....

AND UPDATE YOUR GPU DRIVER!

[stax76]

I've added different decoding modes to the NVEncC GUI and fixed the menu to copy and execute the command line, after execution the shell stays open.

I'm not sure if QSVencC and x265 still work, I'll shortly make similar changes to QSVencC and x265.

[JohnLai]

I've added different decoding modes to the NVEncC GUI and fixed the menu to copy and execute the command line, after execution the shell stays open.

I'm not sure if QSVencC and x265 still work, I'll shortly make similar changes to QSVencC and x265.

So....I selected CUVID as decoder......but I need to manually enter the --output-res 1280x720 for resizing to the "Custom Switches" section. Sliding around Resize slider (right click, select hardware encoder) doesn't work.

Strangely enough, the resize slider option works for QSVenc decoder. Too bad I can't really use QSVenc decoder.

Awaiting your next build.

Oh, and since you implement the decoder menu selection at 'basic', the 'use qsvencc as decoder ......' at 'advanced' section should be removed.

[stax76]

I looked for --output-res in the help and because it was missing I thought it's probably not yet supported.

[NikosD]

@Stax76

Anything new regarding my questions about:

1) Unicode support

2) File Batch mode (configuration like subtitles, demux and indexing)

3) Just Mux mode

Thanks

[stax76]

Unicode support

I can try to allow Unicode using VapourSynth, AviSynth+ don't yet support Unicode.

Is it possible to somehow configure the "File Batch" mode ?
For example, I have some files with embedded subtitles which in "File Batch" mode, the subtitles disappeared after transcoding. (No subs included)

Which subtitle languages are added can be defined in the options, by default it's local and English, adding all is possible (see tooltip), if it don't work it's either a bug or a limitation.

What is the use and gain of using "Demux and Index before creating jobs" option in "File Batch" mode?

It's useful when batch jobs need manual adjustment before processing.

Is it possible to avoid "indexing" when in video encoders profiles "Just Mux" is selected for both single file processing and "file batch" processing ?

In any case StaxRip opens always the video with either AviSynth+ or VapourSynth so the only way to avoid indexing is by choosing a source filter that don't index.

[cegy]

@stax76 these bugs i've listed here http://forum.doom9.org/showpost.php?p=1748123&postcount=755 even in the latest test version (2015-12-03) also i noticed it doesn't change the color you know like this is bad you can't mux ac3 to mp4 for example

[NikosD]

I've added different decoding modes to the NVEncC GUI and fixed the menu to copy and execute the command line, after execution the shell stays open.

I'm not sure if QSVencC and x265 still work, I'll shortly make similar changes to QSVencC and x265.

That version - the latest 03/12/2015 - broke completely the Intel H.264 template.
When you select that template, even the import modes don't work (single file, file batch etc)

It just imports the file without the screen of sources selection and it doesn't even display the path of the file in the source and destination fields!


I can try to allow Unicode using VapourSynth, AviSynth+ don't yet support Unicode.


I use AviSynth+, haven't installed yet VapourSynth, but that move could be useful to others, probably.
Waiting for AviSynth+ to support it then.


Which subtitle languages are added can be defined in the options, by default it's local and English, adding all is possible (see tooltip), if it don't work it's either a bug or a limitation.


It seems that it's a file type specific bug, the subtitle is recognized as "undetermined" and even using the magic word "all" doesn't work. It's a PGS sub.

So, here is a sample:
https://www.sendspace.com/file/wgkspi


It's useful when batch jobs need manual adjustment before processing.


How ? Can you give me an example ?


In any case StaxRip opens always the video with either AviSynth+ or VapourSynth so the only way to avoid indexing is by choosing a source filter that don't index.

You mean DSS/DSS2 ?
Because I think all the others use indexing (haven't tried DG*)

[NikosD]

NVEncC v2.00β2 is out supporting CUVID deinterlacing and NVCUVID decoding under Windows 10, as it is based to NVIDIA Video Codec SDK 6.0 which adds following new features.

Unified SDK for video encoding and decoding
Windows 10 official support
Support for H.264 Motion Estimation only mode
Support for input surfaces in RGB format
Support for SEI and VUI fields for H.265
Support for Adaptive Quantization for improved subjective visual quality with H.265 (adaptive quantization for H.264 is already supported)
GPUs supported for H.265 (HEVC) encoding
GeForce GTX 960, GTX 980. GTX Titan X
Quadro M4000, M5000, M6000
Tesla M4, M6, M60
Various quality and performance improvements in encoding
SDK samples no longer require the CUDA toolkit installed in order to build.

https://developer.nvidia.com/nvidia-video-codec-sdk

[JohnLai]

Eh? GTX 970 and 950 is missing from the list?

So...before this SDK.....adaptive quantization for hevc encoding didn't work in the first place? Oh my.....

Well, I am still waiting for staxrip --output-res sliders support for nvencc+cuvid. ^.^

Eh? CUVID 6.0 finally add HEVC decoding, not sure hybrid decode is supported.

*OH darn, only GM206 based gpu support cuvid hevc decode.

[kartola]

Hi guy,

I have to change my video card.
Is it possible to encode with staxrip using GPU at the same quality of cpu encoding (no streaming)? I use to encode with x264 1080 50p or 50i video.

Do you suggest to buy a nvidia gtx970 or ATI r9 390? Or it's the same for encoding because it's better to use CPU?

thx

[luigizaninoni]

just installed vapoursynth r29; staxrip seems to work fine. Only issue, crop editor no longer works, it shows a blank screen

[Blowis]

Is that there's a scheduled update.
You made the updated only when there's enhancements or bug.
For I have updated the apps MKVToolNix, x264 and X265. It's true that compared to other software can do it manually.

For a month I use for my encoding according to my test is faster than XMedia Recode (which is also a very good simple software primarily to normalize the sound with an analysis that calculates the db and subtitle part) . With XMedia Recode I still make the analysis of his to add or remove db I put on StaxRip and makes encoding.
I wish I had the same thing on a part StaxRip and subtitle.
Thank you for this software.

[Magik Mark]

JohnLai,

tried the cuvid decoder and its 10x faster. May I know if you have any info on image quality? What benefits do you get from avisynth / vaporsynth as decoders

[JohnLai]

JohnLai,

tried the cuvid decoder and its 10x faster. May I know if you have any info on image quality? What benefits do you get from avisynth / vaporsynth as decoders

=.=......well for one........it turned out the adaptive quantization was not working for HEVC in the first place for nvenc SDK 5.0 and any driver version lower than R358.

Just make sure you update the driver to latest version first, otherwise the adaptive quantization will not work (there isn't any indicator whether it is working or not, blame nvidia for it)

Now, the answer to your question.
First, update the nvencc64.exe first
http://rigaya34589.blog135.fc2.com/blog-entry-710.html
Latest beta uses SDK 6.0 with proper support for adaptive quantization for hevc.
Now, since stax76 hasn't implement the resize slider functionality for nvencc yet....you will need to manually enter --output-res 1280x720 at 'Custom Switches" if you wanna take advantage of hardware based resizer. It turns out cuvid gpu based hardware resizer is using bilinear algorithm (I compared it with avisynth cpu based bicubic and bilinear, the cuvid hardware resizer result almost similar to avisynth cpu based bilinear resizer). Rigaya CUVID decoder only support H.264 / MPEG1 / MPEG2 for now. I speculate rigaya CUVID is using direct memory copy (zero copy) for decode+resize+encode. (complete nvidia gpu transcoding)

AVISYNTH/VAPORSYNTH are the normal stuff we used in previous version. The decoders depends on Source Filters ; https://github.com/stax76/staxrip/wiki/Source-Filters

There shouldn't be any different in decoding quality output. (Except post processing stuff = color space conversion, resize?). The only benefit of avisynth/vaporsynth = can support more format? For example, nvencc CUVID decoder will crash if the input file has AVI extension where avisynth doesn't.

[bungie240]

Can anyone help with the error I receive below?


Thanks





Error Demux M2TS using eac3to

Demux M2TS using eac3to failed with exit code: 1 (0x1)

The exit code might be a system error code: STATUS_WAIT_1

The exit code might be a system error code: Incorrect function.

M2TS, 1 video track, 4 audio tracks, 1 subtitle track, 2:04:42, 24p /1.001
1: Chapters, 20 chapters
2: h264/AVC, 1080p24 /1.001 (16:9)
3: DTS Master Audio, English, 7.1 channels, 24 bits, 48kHz
(core: DTS, 5.1 channels, 1509kbps, 48kHz)
4: AC3 Surround, English, 2.0 channels, 192kbps, 48kHz, dialnorm: -27dB
5: AC3, English, 2.0 channels, 192kbps, 48kHz, dialnorm: -27dB
6: TrueHD/AC3, English, 5.1 channels, 96kHz
(embedded: AC3, 5.1 channels, 448kbps, 48kHz)
7: Subtitle (PGS), English
Creating file "C:\Users\Livingroom-PC\Desktop\DVDFab 9.2.1.8\MOVIE DEMUX\OBLIVION_Chapters.txt"...
s07 Extracting subtitle track number 7...
a03 Extracting audio track number 3...
v02 Extracting video track number 2...
v02 Muxing video to Matroska...
a03 Creating file "C:\Users\Livingroom-PC\Desktop\DVDFab 9.2.1.8\MOVIE DEMUX\OBLIVION ID3 English.dtsma"...
s07 Creating file "C:\Users\Livingroom-PC\Desktop\DVDFab 9.2.1.8\MOVIE DEMUX\OBLIVION ID7 English.sup"...
Unfortunately the Haali Muxer cannot handle this source file.
It doesn't contain enough seek/recovery points.
The "-seekToIFrames" option may work around that.
However, using this option may result in artifacts when seeking.
Aborted at file position 23160946688.



StaxRip.ErrorAbortException: Demux M2TS using eac3to failed with exit code: 1 (0x1)

The exit code might be a system error code: STATUS_WAIT_1

The exit code might be a system error code: Incorrect function.

M2TS, 1 video track, 4 audio tracks, 1 subtitle track, 2:04:42, 24p /1.001
1: Chapters, 20 chapters
2: h264/AVC, 1080p24 /1.001 (16:9)
3: DTS Master Audio, English, 7.1 channels, 24 bits, 48kHz
(core: DTS, 5.1 channels, 1509kbps, 48kHz)
4: AC3 Surround, English, 2.0 channels, 192kbps, 48kHz, dialnorm: -27dB
5: AC3, English, 2.0 channels, 192kbps, 48kHz, dialnorm: -27dB
6: TrueHD/AC3, English, 5.1 channels, 96kHz
(embedded: AC3, 5.1 channels, 448kbps, 48kHz)
7: Subtitle (PGS), English
Creating file "C:\Users\Livingroom-PC\Desktop\DVDFab 9.2.1.8\MOVIE DEMUX\OBLIVION_Chapters.txt"...
s07 Extracting subtitle track number 7...
a03 Extracting audio track number 3...
v02 Extracting video track number 2...
v02 Muxing video to Matroska...
a03 Creating file "C:\Users\Livingroom-PC\Desktop\DVDFab 9.2.1.8\MOVIE DEMUX\OBLIVION ID3 English.dtsma"...
s07 Creating file "C:\Users\Livingroom-PC\Desktop\DVDFab 9.2.1.8\MOVIE DEMUX\OBLIVION ID7 English.sup"...
Unfortunately the Haali Muxer cannot handle this source file.
It doesn't contain enough seek/recovery points.
The "-seekToIFrames" option may work around that.
However, using this option may result in artifacts when seeking.
Aborted at file position 23160946688.


at StaxRip.Proc.Start() in D:\Projekte\GitHub\staxrip\General\Proc.vb:line 259
at StaxRip.MainForm.Showeac3toDemuxForm(String playlistFolder, Int32 playlistID) in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:line 5202

[Magik Mark]

Thanks a lot JohnLai. Have you noticed that using qaac encoder doesn't work? It keeps getting an error about controlaudiotoolbox not found

Does the ff filters work on nvidia:

1. Remove Grain
2. TDeint
3. Spatio-Temporal Noice filter

[JohnLai]

Thanks a lot JohnLai. Have you noticed that using qaac encoder doesn't work? It keeps getting an error about controlaudiotoolbox not found

Does the ff filters work on nvidia:

1. Remove Grain
2. TDeint
3. Spatio-Temporal Noice filter

With nvencc integrated CUVID? Sorry, I don't think those filters will works.

[Magik Mark]

With nvencc integrated CUVID? Sorry, I don't think those filters will works.

Thanks for that info. I would assume then setting the decoder to Aysynth/VapourSynth would allow us to use those? Encoding with this option takes around 30min.

Do you happen to have a list of filters that work with nvencc cuvid as decoders and Aysynth/VapourSynth as decoder? And of course running under nvidia hardware acceleration

[Washka]

With latest StaxRip beta i re-encoded H264 from GoPro 2 1080p 30 Fps to Nvidia H265 VBR2, adaptiv quantization checked @4000 bitrate with Nvidia Titan X and got 100-102 Fps. Strange is that Fps are same as mine GTX 960 4Gb.

[Magik Mark]

Can somebody teach us how to add filters? I'm trying to use "removegrainhd". Thanks

[NikosD]

Strange is that Fps are same as mine GTX 960 4Gb.

The hardware responsible for transcoding is the same for the two cards.

The 3D GPU performance is irrelevant for transcoding using Nvidia cards.

[Magik Mark]

Nvenc b3 has been released. What does the ff do:

--qp-init, --qp-max, the --qp-min

Whats the syntax in staxrip?

[JohnLai]

Nvenc b3 has been released. What does the ff do:

--qp-init, --qp-max, the --qp-min

Whats the syntax in staxrip?

I email rigaya about those options and this is his reply ;

Hello,

For –qp-max & --qp-min, you can think it as similar to x264,
limiting the range of QP the encoder can use on vbr, vbr2, cbr mode.

Default: no limit, therefore –qp-min 0, --qp-max 51.
You can use this to improve vbr ratecontrol behavior.

For example, by setting –qp-min, you can avoid the encoder unnecessary using bitrate on the still image part of the video.

--qp-init can be used with vbr, vbr2, cbr mode.

It is used as the initial qp, qp used in the first part of encoding.

If the encoder gives too much or too low bitrate to the initial part of the video, you can use this to adjust it. I don’t know the default, not documented.

rigaya


*Deleted. I worry this will misled others.*

[ismail0100]

How can i do Hevc 10bit? Any pic for this?

[Magik Mark]

Thanks JohnLai!

[JohnLai]

Thanks JohnLai!

Ah, one more thing that I am trying to confirm with rigaya. Apparently, I noticed we can't use 0 value for --qp-init, --qp-max and --qp-min either. It seems to revert back to CQP mode if 0 being specified for the qp-init,max,min.
I am waiting for rigaya reply on my finding.


For now, try playing around with --qp-init 1 --qp-min 1 and --qp-max 20:23:25 with adaptive quantization and normal vbr or vbr2. I not sure what goes wrong, but using these options with normal vbr (not vbr2) actually is way too slow.

EDIT: hmmmmmm.......perhaps I am wrong in using 0 or 1 values for bitrate....oh well

Setting --vbr value to 0 or 1 is not an appropriate value.

0 kbps encoding does not make any sense (actually it might be better to treat it as an error), and 1kbps is too small bitrate for most (or all) videos.

Please set parameters to more realistic values.
More bitrate is required, at least around 1000kbps for HD, 2000kbps for fullHD.

rigaya

And so...Mark.....revert back to previous bitrate value.....as for QP section, I have no idea......

[Yups]

I have to say that HEVC encoding with TU7 and ICQ or CQP bitrate mode is insanely fast with Quicksync, impressive stuff. I just need Lookahead, a bugfixed VBR mode and more than three target usage options. I hope Intel can do this for the next API version.

[Yups]

@stax76


Could you implement a Maximum bitrate option into the GUI for Quicksync? I noticed that VBR Bitrate= Maximum Bitrate in HEVC which results in poor results.

[RieGo]

hi everyone, i'm trying to reencode an hevc file to a lower res h264 file.
video works just fine. but it seems staxrip has a problem with extracting audio:

------------------------------------------------------------
Demux audio using MP4Box
------------------------------------------------------------

"C:\StaxRip\Apps\MP4Box\MP4Box.exe" -single 1 -out "D:\XMas15\SAM_4516 temp files\SAM_4516 ID1 English.m4a" "D:\XMas15\SAM_4516.MP4"

ICC colour profile not supported[iso file] Read Box "colr" failed (Feature Not Supported)
[iso file] Read Box "hvc1" failed (Feature Not Supported)
[iso file] Read Box "stsd" failed (Feature Not Supported)
[iso file] Read Box "stbl" failed (Feature Not Supported)
[iso file] Read Box "minf" failed (Feature Not Supported)
[iso file] Read Box "mdia" failed (Feature Not Supported)
[iso file] Read Box "trak" failed (Feature Not Supported)
[iso file] Read Box "moov" failed (Feature Not Supported)
Error opening file D:\XMas15\SAM_4516.MP4: Feature Not Supported

------------------------------------------------------------
Error Demux audio using MP4Box
------------------------------------------------------------

Demux audio using MP4Box failed with exit code: 1 (0x1)

The exit code might be a system error code: STATUS_WAIT_1

The exit code might be a system error code: Unzulässige Funktion.

ICC colour profile not supported[iso file] Read Box "colr" failed (Feature Not Supported)
[iso file] Read Box "hvc1" failed (Feature Not Supported)
[iso file] Read Box "stsd" failed (Feature Not Supported)
[iso file] Read Box "stbl" failed (Feature Not Supported)
[iso file] Read Box "minf" failed (Feature Not Supported)
[iso file] Read Box "mdia" failed (Feature Not Supported)
[iso file] Read Box "trak" failed (Feature Not Supported)
[iso file] Read Box "moov" failed (Feature Not Supported)
Error opening file D:\XMas15\SAM_4516.MP4: Feature Not Supported


Start: 12:48:38
End: 12:48:38
Duration: 00:00:00



is this a staxrip problem or does mp4box just not support this kind of container?

edit: works fine when remuxed to mkv first, as expected

[luigizaninoni]

Hmm, Stax's last post on the forum was on 4th dicembre 2015, I wonder if something happened to him

[RieGo]

but Last Activity: Today 13:58

so i don't think we need to worry :)

[Morpheus_xx]

I'm using StaxRip x64 : 1.3.1.7 to encode TV captures to h.265 by Intel Quicksync encoder. Encoding works fine, but I found an issue with muxing the result:

My source file contains 4 audio streams, I want to use the AC3 stream without reencoding. So I selected "mux only" for the AC3 stream. Unfortunately the resulting file had a MP2 audio included.

I could remux the files by taking the command line of mkvmerge from log and decreased the track number by 1:

"StaxRipX64\Apps\MKVToolNix\mkvmerge.exe" -o "F:\Capture\Batch\S2E1.mkv" --noaudio --nosubs --no-chapters --no-attachments --no-track-tags --no-global-tags --default-duration 0:50.000000fps "F:\Capture\Batch\S2E1 temp files\S2E1_out.hevc" --novideo --nosubs --no-chapters --no-attachments --no-track-tags --no-global-tags --audio-tracks 3 --language 3:ger "F:\Capture\Batch\S2E1.ts" --ui-language en

I had to modify the bold 3 -> 2.

It looks to me like a common difference between starting counting by 1 vs. 0:

mkvmerge -i shows:
File 'F:\Capture\Batch\S2E2.ts': container: MPEG transport stream
Track ID 0: video (MPEG-4p10/AVC/h.264)
Track ID 1: audio (MP2)
Track ID 2: audio (AC3/EAC3)
Track ID 3: audio (MP2)
Track ID 4: audio (MP2)

In staxrip log:
Audio #3
ID : 66 (0x42)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3

Is this a known error? Do you need more information, full log, mediainfo or project file?

[ShamisOMally]

I suggest everyone manually update FFMPEG as an exploit has been released into the wild where a infected media file if its accessed by FFMPEG will cause it to upload files of the persons choosing to a remote server

2.8.5 this issue has been patched, so I suggest manually updating until Stax gets around to it

[Magik Mark]

Stax,

When can we expect another update? Thank you for your awesome work

[Marban]

x265 [info]: HEVC encoder version 1.8+212-792f6ead9c50
x265 [info]: build info [Windows][GCC 4.8.2][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZCNT BMI2
x265 [warning]: Specifying a decoder level with constant rate factor rate-control requires
x265 [warning]: enabling VBV with vbv-bufsize=25000kb vbv-maxrate=25000kbps. VBV outputs are non-deterministic!
x265 [info]: Main 10 profile, Level-5 (Main tier)
x265 [info]: Thread pool created using 8 threads
x265 [info]: frame threads / pool features : 3 / wpp(17 rows)
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 3 inter / 3 intra
x265 [info]: ME / range / subpel / merge : star / 57 / 5 / 4
x265 [info]: Keyframe min / max / scenecut : 25 / 250 / 40
x265 [info]: Lookahead / bframes / badapt : 60 / 8 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 1
x265 [info]: References / ref-limit cu / depth : 5 / 0 / 1
x265 [info]: AQ: mode / str / qg-size / cu-tree : 1 / 0.9 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-19.0 / 0.60
x265 [info]: VBV/HRD buffer / max-rate / init : 25000 / 25000 / 0.900
x265 [info]: tools: rect amp limit-modes rd=6 psy-rd=1.00 rdoq=2 psy-rdoq=1.15
x265 [info]: tools: signhide tmvp b-intra strong-intra-smoothing
x265 [info]: tools: deblock(tC=-1:B=-2) sao


I get 2 warning messages, can anybody say me, what is wrong?

[Marban]

x265 [info]: HEVC encoder version 1.8+212-792f6ead9c50
x265 [info]: build info [Windows][GCC 4.8.2][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZCNT BMI2
x265 [warning]: Specifying a decoder level with constant rate factor rate-control requires
x265 [warning]: enabling VBV with vbv-bufsize=25000kb vbv-maxrate=25000kbps. VBV outputs are non-deterministic!
x265 [info]: Main 10 profile, Level-5 (Main tier)
x265 [info]: Thread pool created using 8 threads
x265 [info]: frame threads / pool features : 3 / wpp(17 rows)
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 3 inter / 3 intra
x265 [info]: ME / range / subpel / merge : star / 57 / 5 / 4
x265 [info]: Keyframe min / max / scenecut : 25 / 250 / 40
x265 [info]: Lookahead / bframes / badapt : 60 / 8 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 1
x265 [info]: References / ref-limit cu / depth : 5 / 0 / 1
x265 [info]: AQ: mode / str / qg-size / cu-tree : 1 / 0.9 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-19.0 / 0.60
x265 [info]: VBV/HRD buffer / max-rate / init : 25000 / 25000 / 0.900
x265 [info]: tools: rect amp limit-modes rd=6 psy-rd=1.00 rdoq=2 psy-rdoq=1.15
x265 [info]: tools: signhide tmvp b-intra strong-intra-smoothing
x265 [info]: tools: deblock(tC=-1:B=-2) sao


I get 2 warning messages, can anybody say me, what is wrong?

[Trench]

Using StaxRip_x64_1.3.1.7_beta, I've noticed I'm unable to select "just mux" when using a MKV with HEVC video content as the source file, and wanting to create an MP4 as the output.

Selecting "just mux" is fine while the container is still MKV, but as soon as I select MP4 as the container, the UI shows the warning:

"The encoder outputs 'rteam_outh265', but the container 'MP4' supports only ts, m2ts, mpg, m2v, avi, ac3, mp4, m4a, aac, 264, h264, avc, 265, h265, hvec, mp2, mpa, mp3."

This is not consistently the message; I've also seen it report simply an empty string ('') instead of 'rteam_outh265', and other variations of a string that ends in "265".

I think it's actually a mis-parsing of the file name string that arrives at the incorrect "type". For example, when the UI reported "rteam_outh265", the source MKV file name was "test.2015.1080p.test.6ch.hevc.x265.rmteam.mkv". As though something neglected to put a period before h265, or was confused by all the other periods that were already present.

I'm attaching a log from an example of where this happened today. Not that there is any failure "in the log"; it just confirms the MKV contained HEVC encoded video. The "error" is simply in the UI, and prevents me from proceeding with any further action that would have ended up in the log.

I can of course manually get the h265 stream out of the MKV using mkvextract, and put together the MP4 myself with mp4box. It's "just a UI issue" of not being able to recognize that what's available from the MKV is in fact h265.

The question I'm guessing you want to know the answer to: I'm simply selecting "Choose automatically" when asked which import filter to use. The source .avs ends up containing the following if that's important:

LoadPlugin("C:\Users\Encoder\StaxRip_x64_1.3.1.7_beta\Apps\Plugins\both\ffms2\ffms2.dll")
FFVideoSource("C:\Files\Ripping\test.2015.1080p.test.6ch.hevc.x265.rmteam.mkv", cachefile = "C:\Files\Ripping\test.2015.1080p.test.6ch.hevc.x265.rmteam temp files\test.2015.1080p.test.6ch.hevc.x265.rmteam.ffindex")

Thanks. -Trench