StaxRip

[Magik Mark]

Originally Posted by JohnLai

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]

Originally Posted by Washka

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]

Originally Posted by Magik Mark

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 ;

PHP Code:

[I]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[/I] 


*Deleted. I worry this will misled others.*

[ismail0100]

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

[Magik Mark]

Thanks JohnLai!

[JohnLai]

Originally Posted by Magik Mark

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

PHP Code:

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