Log in

View Full Version : StaxRip


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 [31] 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101

Caroliano
29th August 2016, 22:53
How to set up the Python location? I have WinPython installed with the latest version, but StaxRip detects only an older python instalation to Program Files. I tried to follow the "download Python" button, but it installs to my local user directory and again staxrip don't detects it.

Magik Mark
29th August 2016, 23:10
Hi Fred!

It has been more than a month since staxrip has been updated. x265 has new switches now

Thank you for your efforts

IbrahimKh
2nd September 2016, 15:37
Yea, it almost 3 month
waiting for new build

ilovejedd
3rd September 2016, 16:25
First of all, thank you very much for all your work on StaxRip. While it may not be as simple to use as Handbrake, it's definitely far more flexible. One thing, though, when using QTGMC, I encountered errors with the Avisynth script (Code 126, cannot load module or something). After much googling, I eventually traced it to missing Microsoft Visual C++ 2012 Redistributable which is needed for masktools2.dll. Perhaps a link to the VC 2012 redist download could be added in the Runtimes section like with the VC 2013 and VC 2015? Thanks!

JohnLai
6th September 2016, 15:50
@stax76, apparently, qsv --vpp-sub will cause error:


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Script
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

LoadPlugin("C:\Users\Anonymous\Desktop\Staxrip\Apps\Plugins\both\ffms2\ffms2.dll")
FFVideoSource("K:\test.mkv", cachefile = "L:\test_temp\test.ffindex")

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Script Properties
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

source frame count : 43015
source frame rate : 23.976024
source duration : 00:29:54.0840000
target frame count : 43015
target frame rate : 23.976024
target duration : 00:29:54.0840000

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Encoding using QSVEncC 2.55 x64
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

@echo off
C:\Users\Anonymous\Desktop\Staxrip\Apps\QSVEncC\QSVEncC64.exe --quality best --bframes 16 --ref 11 --b-adapt --scenechange --profile High --level 4.1 --vpp-sub "L:\test_temp\English.ass" --trellis all --fallback-rc --i-adapt --cqp 20:23:25 --sar 40:33 -i "K:\test\test.mkv" -o "L:\test_temp\test_out.h264"

cmd.exe /C call "L:\test_temp\test_QSVEncC.bat"

QSVEncC.exe finished with error!

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Error Encoding using QSVEncC 2.55 x64
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Encoding using QSVEncC 2.55 x64 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.

QSVEncC.exe finished with error!

Start: 10:44:18 PM
End: 10:44:18 PM
Duration: 00:00:00

I don't think I need to post full log. Stax76, you can test it by loading up any srt subtitle using qsv --vpp-sub (make sure QSV decoder being selected). I hope this can be fixed.

MOHAX777
10th September 2016, 10:30
StaxRip x64 : 1.3.8.7
OS : Windows 7 Home Premium
CPU : Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
GPU : Radeon (TM) RX 470 Graphics

--------------

with AMD x264 default profile got error:

----------------------------------------------------------
Error Encoding using VCEEncC 2.0 x64

StaxRip.ErrorAbortException: Encoding using VCEEncC 2.0 x64 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.

"--cqp" *Ґ пў«пҐвбп ў*гваҐ**Ґ© Ё«Ё ў*Ґи*Ґ©
Є®¬**¤®©, ЁбЇ®«*塞®© Їа®Ја*¬¬®© Ё«Ё Ї*ЄҐв*л¬ д*©«®¬.


в StaxRip.Proc.Start() в D:\Projekte\VS\VB\StaxRip\General\Proc.vb:строка 240
в StaxRip.AMDEncoder.Encode() в D:\Projekte\VS\VB\StaxRip\Encoding\AMDEncoder.vb:строка 76
в StaxRip.MainForm.Encode() в D:\Projekte\VS\VB\StaxRip\Forms\MainForm.vb:строка 2220
в StaxRip.MainForm.RunJobRecursive() в D:\Projekte\VS\VB\StaxRip\Forms\MainForm.vb:строка 3462

--------------------------------------------------


In temp-dir i found bat-file contain command string start with "--qcp .....". I add path to VCEEncC64.exe at start position, run this bat-file and encoded successes!

VelleX
13th September 2016, 09:06
is there an option to deactivate free disk space check? Because cant even convert a 18GB 1080p MKV to SD Resolution, which of course would not need 18GB of free disk space.
I know i am lack of hard disk space :P


I've added a Continue and Abort button to the task dialog.


Problem is if you have more than one Job, because you are asked every time to continue or abort, so you cant just batch convert over night.

spon
13th September 2016, 20:40
Hi everyone. I've read through a lot of this thread, but 99% of it is over my head. Are there any recommended settings for NVIDIA H265 Encoding? I see there are 37 options, but I'm not sure where to even start. I would prefer better quality over smaller file size. I'm currently using Handbreak and x265, but the process is soooooo slow. I'd be willing to give up some quality for encoding speed, but would like to test to see the visual difference.

If someone could point me in the right direction, I would greatly appreciate it.

Thanks!

JohnLai
14th September 2016, 04:39
Hi everyone. I've read through a lot of this thread, but 99% of it is over my head. Are there any recommended settings for NVIDIA H265 Encoding? I see there are 37 options, but I'm not sure where to even start. I would prefer better quality over smaller file size. I'm currently using Handbreak and x265, but the process is soooooo slow. I'd be willing to give up some quality for encoding speed, but would like to test to see the visual difference.

If someone could point me in the right direction, I would greatly appreciate it.

Thanks!

http://i.imgur.com/qaujIkT.jpg

You gonna have larger file compared to software based encoder......how large is the file size for comparable quality?
Here is rough calculation http://forum.doom9.org/showthread.php?p=1780493#post1780493

spon
14th September 2016, 05:07
http://i.imgur.com/qaujIkT.jpg

You gonna have larger file compared to software based encoder......how large is the file size for comparable quality?
Here is rough calculation http://forum.doom9.org/showthread.php?p=1780493#post1780493

Thank you! This is exactly what I was looking for.

JohnLai
14th September 2016, 07:02
Thank you! This is exactly what I was looking for.

Although Nvidia Video Codec SDK mentiones the VBR-CQ to be Constant Quality, it is wrong by definition. The method being used ought be called 'Constrained Quality' if you specify bitrate other than maximum 17500. It will behave as 'Constant Quality' if you specify 17500 as I shown in the strip.

Note: For some unknown reason, nvidia only allows CQ method to work with VBR single pass, it doesn't work work VBR two pass (If you use VBR2, it simply uses all of the bitrate 17500). But hey....we got a lookahead bitrate allocation....so there is no need for two pass in first place....

mcjordan
16th September 2016, 17:47
Dear JohnLai, thank you for good advice about NVEncC encoding in VBR-CQ mode.
About LTR in StaxRip/NVencC v2.11. It's working (--enable-ltr) but only if --level is set to unrestricted (or higher then L3.0 maybe - need some more tests).
Some recomendations for CABAC and Deblock (in good quality source situation)?

JohnLai
17th September 2016, 04:23
Dear JohnLai, thank you for good advice about NVEncC encoding in VBR-CQ mode.
About LTR in StaxRip/NVencC v2.11. It's working (--enable-ltr) but only if --level is set to unrestricted (or higher then L3.0 maybe - need some more tests).
Some recomendations for CABAC and Deblock (in good quality source situation)?

Only 1 frame being 'marked' as LTR in DPB.

Example:

NVENC HEVC Level 4.1 normally has maximum reference frames of 5 for 1920x1080p.
If LTR being specified, then you will need to drop the maximum reference number by 1. Thus, for lvl 4.1 with LTR, you will need to setup maximum reference frame of 4. (Just minus 1 from the maximum allowable frame for each level profile)

*I have no idea what being put in DPB by nvidia. From what I can see, nvenc's HEVC P-frame only make use of single/one previous frame.

I tested using unrestricted profile for both NVENC and HEVC by specifying 8 reference frames:
This is NVENC HEVC output:
NumNegativePics 8
NumPositivePics 0
NumDeltaPocs 8
UsedByCurrPicS0 1 0 0 0 0 0 0 0
UsedByCurrPicS1
DeltaPocS0 -1 -2 -3 -4 -5 -6 -7 -8
DeltaPocS1

This is software x265 output (I set bframe to 0 to match nvenc lack of bframe support):
NumNegativePics 8
NumPositivePics 0
NumDeltaPocs 8
UsedByCurrPicS0 1 1 1 1 1 1 1 1
UsedByCurrPicS1
DeltaPocS0 -1 -2 -3 -4 -5 -6 -7 -8
DeltaPocS1
See the difference with x265?

For nvenc HEVC and H264 encoding, the P-frame cannot refer to multiple preceding frame. On the other hand, nvenc H264 B-Frame can refer to multiple preceding frames (no b-pyramid support, so no future frame referencing....)

EDIT: Don't bother with other setting such as deblock or cabac.
For H264 encode, use the new 'temporal adaptive quantization' if your gpu supports it.

mcjordan
17th September 2016, 11:41
John, thanks for the useful info and sorry for disturbance.

VelleX
17th September 2016, 16:57
@Stax76

i often have problems extracting audio from recorded TS Files. I think its because of FFMPEG Stream Order (or the original TS File Stream Order, which is different to Mediainfo), so wrong stream is choosed to demux. Sometimes it may be an audio Stream too, but the wrong of course, but sometimes its a subtitle stream so i got an error and Staxrip just aborts.

Output file #0 does not contain any stream

Leo 69
17th September 2016, 18:52
Fred hasn't visited the forum for straight 17 days already. Hope he's OK.

Leo 69
17th September 2016, 18:53
@Vellex, in these cases I extract necessary streams using TSMuxer manually.

VelleX
17th September 2016, 21:24
Maybe he's just on holidays. Everyone deserves them.

I looked at the log, to see what command line was used, and then changed the command line.

In my case the stream looked like this, and i wanted the 448kbps AC3 Stream, which is #0:5, but StaxRip64 used in the FFMPEG command line "-map 0:3"

Stream #0:0[0x13f7]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 100 tbc
Stream #0:1[0x13f8](deu): Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 192 kb/s
Stream #0:2[0x13f9](fra): Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 192 kb/s
Stream #0:3[0x13fa](deu): Subtitle: dvb_teletext ([6][0][0][0] / 0x0006)
Stream #0:4[0x13fb](deu): Subtitle: dvb_subtitle ([6][0][0][0] / 0x0006) (hearing impaired)
Stream #0:5[0x13fc](mul): Audio: ac3 ([6][0][0][0] / 0x0006), 48000 Hz, 5.1(side), fltp, 448 kb/s
Stream #0:6[0x13fd](mis): Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 192 kb/s
Stream #0:7[0x13fe](fra): Subtitle: dvb_subtitle ([6][0][0][0] / 0x0006)
Stream #0:8[0x13ff](deu): Subtitle: dvb_subtitle ([6][0][0][0] / 0x0006)

spon
21st September 2016, 03:10
@johnlai (or anyone) - are there recommended settings for Intel h265 hardware encoding similar to the Nvidia that you shared? I happen to have both a GTX 960 and Intel Skylake CPU and am trying to find out which gives me the best combination of quality, speed and size (ranked in order of importance.

Thanks!

JohnLai
21st September 2016, 03:58
@johnlai (or anyone) - are there recommended settings for Intel h265 hardware encoding similar to the Nvidia that you shared? I happen to have both a GTX 960 and Intel Skylake CPU and am trying to find out which gives me the best combination of quality, speed and size (ranked in order of importance.

Thanks!

Post your skylake QSV features support first...I havent bought Skylake yet....waiting for cheaper skylake to come out at my local shop....

How to check?
http://i.imgur.com/cmP8zYG.jpg

I want to verify if weight-p and weight-b have been made available for skylake yet. (So...make sure your Intel IGPU driver is up to date)
The last time I checked with my friend pc, it only had i-adapt and b-adapt.

EDIT: Don't forget to update the QSVenCC first, I haven't update mine because the latest update doesn't have anything interesting for my Haswell IGPU.....

spon
21st September 2016, 05:50
Post your skylake QSV features support first...I havent bought Skylake yet....waiting for cheaper skylake to come out at my local shop....

How to check?


I want to verify if weight-p and weight-b have been made available for skylake yet. (So...make sure your Intel IGPU driver is up to date)
The last time I checked with my friend pc, it only had i-adapt and b-adapt.

EDIT: Don't forget to update the QSVenCC first, I haven't update mine because the latest update doesn't have anything interesting for my Haswell IGPU.....

Thanks John. I just updated the igpu driver (new one just came out) but I'm not entirely sure how to update QSVenCC. Staxrip has 2.54 and I do see that 2.56 is out. I downloaded it, but am not sure what to do now as most of it is in a different language. Should I just extract and replace the files in the Staxrip Apps folder? Or do I need to run the auto installer?

JohnLai
21st September 2016, 06:15
Thanks John. I just updated the igpu driver (new one just came out) but I'm not entirely sure how to update QSVenCC. Staxrip has 2.54 and I do see that 2.56 is out. I downloaded it, but am not sure what to do now as most of it is in a different language. Should I just extract and replace the files in the Staxrip Apps folder? Or do I need to run the auto installer?


-.-......hmmm.....
http://rigaya34589.blog135.fc2.com/blog-entry-830.html
https://onedrive.live.com/?id=6BDD4375AC8933C6%21482&cid=6BDD4375AC8933C6
Extract/Replace everything in \Staxrip\Apps\QSVEncC

Do I really need to 'sponfeed'
http://i.imgur.com/gCGtXO9.jpg

spon
21st September 2016, 07:20
Thanks again. Here are the results

QSVEncC available features attached.

JohnLai
21st September 2016, 07:34
Thanks again. Here are the results

QSVEncC available features attached.

Attachment pending approval --> This gonna take forever.
So....pastebin to the rescue?

spon
21st September 2016, 17:51
Attachment pending approval --> This gonna take forever.
So....pastebin to the rescue?

Oops! I didn't even notice that. Here is the link:

http://pastebin.com/h05rgkT4

Thanks again

JohnLai
21st September 2016, 19:18
Oops! I didn't even notice that. Here is the link:

http://pastebin.com/h05rgkT4

Thanks again

-.-???What the hell?
Few months ago, supported features were :
http://rigaya34589.blog135.fc2.com/blog-entry-672.html
Take a look on rigaya website detailing his skylake IGPU feature support and compare it with yours.

Why in the world the latest driver disable Trellis, B-adapt and I-adapt? Even Ext_BRC got disabled.

:confused:
Instead of adding features, existing feature got removed instead.
Originally, I plan to advice HEVC TU1 target usage (Only TU1 enables usage of 32X32 CTU blocks, other TU only make use up to 16x16 CTU block size), Trellis=all, scenechange, B-adapt (then we can enable B-frame=16, higher is better, after all, QSV HEVC make use of Generalized P/B (GPB)--> it means instead of using P frame, it substitutes P-frame with B-Frame) , I-adapt, higher reference frame around 5-16 depending on profile level and resolution (contrary to nvenc and vce, intel qsv's reference frame setting actually works), mbbrc and ICQ rate control at default 23.

Now this is troublesome.....

spon
21st September 2016, 19:24
-.-???What the hell?
Few months ago, supported features were :

Take a look on rigaya website detailing his skylake IGPU feature support and compare it with yours.

Why in the world the latest driver disable Trellis, B-adapt and I-adapt? Even Ext_BRC got disabled.

:confused:
Instead of adding features, existing feature got removed instead.
Originally, I plan to advice HEVC TU1 target usage (Only TU1 enables usage of 32X32 CTU blocks, other TU only make use up to 16x16 CTU block size), Trellis=all, scenechange, B-adapt (then we can enable B-frame=16, higher is better, after all, QSV HEVC make use of Generalized P/B (GPB)--> it means instead of using P frame, it substitutes P-frame with B-Frame) , I-adapt, higher reference frame around 5-16 depending on profile level and resolution (contrary to nvenc and vce, intel qsv's reference frame setting actually works), mbbrc and ICQ rate control at default 23.

Now this is troublesome.....

I'll double check when I get home tonight to verify that I updated to the latest version correctly and report back.

spon
22nd September 2016, 03:52
I'll double check when I get home tonight to verify that I updated to the latest version correctly and report back.

Looks like I was updated to the latest video drivers and QSVEncC. Here i a fresh pastebin just in case.

http://pastebin.com/uFi0c64u

Maybe I should roll back to an earlier driver?

Thanks

JohnLai
22nd September 2016, 05:56
Looks like I was updated to the latest video drivers and QSVEncC. Here i a fresh pastebin just in case.

http://pastebin.com/uFi0c64u

Maybe I should roll back to an earlier driver?

Thanks

I am not sure about rolling back, there must be reasons on why Intel disabled those features.

Well...have to make do with current available feature.
Thus, http://i.imgur.com/OaGdzPs.jpg

Edit: Since B-adapt feature is no longer available.....I am not sure if setting B-Frame = 16 will cause error under Lvl 4.1. It should works....otherwise, set it to 8 B-Frames.
Edit2 : I was hoping for Weight-p and Weight-b to be available... (Successor to B-adapt, I didn't expect b-adapt to be removed...) Same with Trellis quantization too.
Edit3 : Correction! After reading latest Intel Media SDK --> it turns out i_adapt and b_adapt are ignored if 'scenecut' (known as SceneChange) is specified. I wonder when Intel made such changes. SDK doesnt mention why Trellis quantization is missing though. Trellis can only be enabled in TU1. It is disabled in TU2 - TU7. Most of Intel SDK only mention H264 Trellis, no mention on HEVC Trellis.

spon
22nd September 2016, 07:09
I am not sure about rolling back, there must be reasons on why Intel disabled those features.

Well...have to make do with current available feature.
Thus,

Edit: Since B-adapt feature is no longer available.....I am not sure if setting B-Frame = 16 will cause error under Lvl 4.1. It should works....otherwise, set it to 8 B-Frames.
Edit2 : I was hoping for Weight-p and Weight-b to be available... (Successor to B-adapt, I didn't expect b-adapt to be removed...) Same with Trellis quantization too.
Edit3 : Correction! After reading latest Intel Media SDK --> it turns out i_adapt and b_adapt are ignored if 'scenecut' (known as SceneChange) is specified. I wonder when Intel made such changes. SDK doesnt mention why Trellis quantization is missing though. Trellis can only be enabled in TU1. It is disabled in TU2 - TU7. Most of Intel SDK only mention H264 Trellis, no mention on HEVC Trellis.

Thanks a lot! I noticed that Weight P and weight b do have checkboxes available in the motion search section.

I'll give it a try as soon as I can. Having some other issues with Staxrip where I can't load a file using Automatic AviSynth+ because it's reporting my Visual C++ 2015 is not updated, but the update link doesn't work. Downloaded it manually but Staxrip is not recognizing it. I need to sort that out first and then I'll test it.

Thanks again.

JohnLai
22nd September 2016, 07:42
Thanks a lot! I noticed that Weight P and weight b do have checkboxes available in the motion search section.

I'll give it a try as soon as I can. Having some other issues with Staxrip where I can't load a file using Automatic AviSynth+ because it's reporting my Visual C++ 2015 is not updated, but the update link doesn't work. Download it manually but Staxrip is not recognizing it. I need to sort that our first and then I'll test it.

Thanks again.

Even if you check those boxes, it will not function.

As for VC++ 2015 Runtime....is this the one you downloaded?
https://www.microsoft.com/en-us/download/details.aspx?id=48145

The official link above should work.
If I am not mistaken, staxrip needs vc++ 2015 runtime minimum version of 14.0.24210.

EDIT: -.-....read this for solution instead https://github.com/stax76/StaxRip/issues/104


Don't forget to set Source Filter to FFVideoSource too.

JohnLai
22nd September 2016, 18:35
Oh wow.....rigaya-san just released Nvencc 3.00....this is going to take a while to test all of those options;

One of the most interesting feature
・さまざまなリサイズアルゴリズムを追加。(--vpp-resize)
リサイズアルゴリズムを選択。

--vpp-resize <string>

標準で使用可能なもの
default 自動的に適切なものを選択
bilinear 線形補間
spline36 6x6 Spline補間
nppi64_80.dll導入で追加されるもの(x64のみ)
nn 最近傍点選択
npp_linear nppの線形補間
cubic 4x4 3次補間
cubic_bspline 4x4 3次補間 (B=1, C=0)
cubic_catmull 4x4 3次補間 (B=0, C=1/2)
cubic_b05c03 4x4 3次補間 (B=1/2, C=3/10)
super nppのsuper sampling(詳細不明)
lanczons Lanczos法 (参照点数不明)

I think the resize algorithm speaks for itself (no need translation) d^.^

*Note: Need to download NPP package separately.

Other than that.....noise filter and gaussian filter?

More on rigaya-san website
http://rigaya34589.blog135.fc2.com/blog-entry-832.html

Edit: From Rigaya-san email ;
--vpp-resize <string>

[CUDA resizer]

bilinear, spline36

[npp resizer]

nn, npp_linear, cubic, cubic_bspline, cubic_catmull, cubic_b05c03,super, lanczos

When using npp library, it is necessary to use x64 version since npp library is only supported on x64.
Also, please download npp64_80_dll.zip and put the dlls to the directory which NVEncC64.exe exists.

NikosD
22nd September 2016, 18:39
Vpp resize is been supported by QSVEncC for Intel GPUs years before.

What's new ?

JohnLai
22nd September 2016, 19:00
Vpp resize is been supported by QSVEncC for Intel GPUs years before.

What's new ?

AMD APU and FX-series buyers can finally make use of full hardware better resizers with their dedicated Nvidia GPU? After all, they don't have Intel IGPU..... :p

Okay, jokes aside :D ...the problem with QSVEncC --> It is limited to single algorithm, if I not recall wrongly, something about 8taps polyphase scaling filter with adaptive filter ringing suppression.

In nvidia case, there are several resizing algorithms can be chosen through NPP library https://developer.nvidia.com/npp , although ringing might still be an issue. It all about choices, really. Oh...and it is quite fast too.

EDIT: (some grammer correction)
Okay...initial testing....
In QSVencc case, the VPP is done in decode stage. Which means if one want to use QSV VPP Resize, one must use QSVENC hardware decoder. But what if the video format (let say 10bit H264) is incompatible with QSVEncc hardware decoder? In such case, there is no way to make use of QSV hardware based VPP filter.

Now, latest NVENCC is different. One can use ffmpeg+avisynth for software decoding, then send it to GPU resizing (labeled as copyHostToDevice), straight away send to NVENC chip for encoding.

IbrahimKh
23rd September 2016, 08:12
does anybody know what Staxrip filter I can use to make my video from like this http://i.imgbox.com/Cn5VWYEw.png to this http://i.imgbox.com/oxaKOa4F.png?

Leo 69
23rd September 2016, 08:31
does anybody know what Staxrip filter I can use to make my video from like this http://i.imgbox.com/Cn5VWYEw.png to this http://i.imgbox.com/oxaKOa4F.png?

LSFMod

Yups
23rd September 2016, 15:26
-.-???What the hell?
Few months ago, supported features were :
http://rigaya34589.blog135.fc2.com/blog-entry-672.html
Take a look on rigaya website detailing his skylake IGPU feature support and compare it with yours.

Why in the world the latest driver disable Trellis, B-adapt and I-adapt? Even Ext_BRC got disabled.



These features never worked for H265.


HEVC TU1 is dead slow, not recommended. There is too much shader work required which will cause a huge slowdown on a GT2.

JohnLai
23rd September 2016, 18:35
These features never worked for H265.


HEVC TU1 is dead slow, not recommended. There is too much shader work required which will cause a huge slowdown on a GT2.

Agree, TU1 perform more unknown works than TU2-TU7. Not sure where the slowdown comes from. It is very unlikely enabling additional 32x32 Prediction Unit sizes for HEVC encoding can cause that much slow down. Intel media sdk doesn't exactly describe what each TU specifically do.

Then again....among big 3 hardware encoders, only Intel HEVC reference frame option actually works.

IbrahimKh
25th September 2016, 06:57
LSFMod

thanks
I discovered it and having problem implementing to staxrip (considering I'm really new on video conversion)

I put Lsfmod line to filter profiles like this
http://s21.postimg.org/44670fd1z/screenshot_44.png

But I'm not sure what should I do with plugin (where can I download and put it on staxrip folder)
http://s21.postimg.org/cay6s034n/screenshot_45.png

A little help will be appreciated

AMED
27th September 2016, 08:08
Just wondering if anyone has seen a memory leak in Staxrip?

http://s21.postimg.org/5whg2rqjb/Staxrip.png

I saw this after doing 2 days straight of encoding.

StaxRip x64 : 1.3.8.7
OS : Windows Server 2012 R2 Standard
Language : English (New Zealand)
CPU : Intel(R) Xeon(R) CPU E5645 @ 2.40GHz
GPU : Microsoft Basic Display Adapter
I'm encoding with Vapoursynth R33.1 and resizing with spline36 and denoising with mvdegrain.

Magik Mark
28th September 2016, 00:59
Stax,

A new milestone has been released for x265

rayman3003
1st October 2016, 08:27
Hi to all

I want to rip some VCD videos (MPEG1)[AVSEQ01.DAT] with Staxrip to x264 (MKV)[AviSynth+] But the problem is that after convert, It has no sound!

Staxrip shows 0 bitrate for Audio and I don't know how to change the settings to bring back the audio for converted files.

Could somebody help me here? :rolleyes:

Here is a short sample of MPEG1 videos that I want to rip:

http://uptobox.com/1n4eclqeo2dp

Leo 69
1st October 2016, 09:18
Hi to all

I want to rip some VCD videos (MPEG1)[AVSEQ01.DAT] with Staxrip to x264 (MKV)[AviSynth+] But the problem is that after convert, It has no sound!

Staxrip shows 0 bitrate for Audio and I don't know how to change the settings to bring back the audio for converted files.

Could somebody help me here? :rolleyes:

Here is a short sample of MPEG1 videos that I want to rip:

http://uptobox.com/1n4eclqeo2dp

Hi,

Change the extension of the file from .dat to .mpg. This will help.

rayman3003
1st October 2016, 09:55
Hi,

Change the extension of the file from .dat to .mpg. This will help.

Thank u very much. It worked. :p

lordalibaski
4th October 2016, 02:47
Explain this

I tried to convert this file.


Format : MPEG-PS
File size : 1.13 GiB
Duration : 6mn 12s
Overall bit rate mode : Variable
Overall bit rate : 26.2 Mbps

Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : Variable
Format settings, picture struc : Frame
Duration : 6mn 12s
Bit rate mode : Variable
Bit rate : 25.2 Mbps
Maximum bit rate : 8 700 Kbps
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 4:3
Frame rate : 25.000 fps
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 2.432
Time code of first frame : 00:59:59:00
Time code source : Group of pictures header
GOP, Open/Closed : Closed
Stream size : 1.09 GiB (96%)

Audio #1
ID : 189 (0xBD)-128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Muxing mode : DVD-Video
Duration : 6mn 12s
Bit rate mode : Constant
Bit rate : 224 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Compression mode : Lossy
Stream size : 9.93 MiB (1%)

Audio #2
ID : 189 (0xBD)-129 (0x81)
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Muxing mode : DVD-Video
Duration : 6mn 12s
Bit rate mode : Constant
Bit rate : 224 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Compression mode : Lossy
Stream size : 9.93 MiB (1%)

Text #1
ID : 189 (0xBD)-32 (0x20)
Format : RLE
Format/Info : Run-length encoding
Muxing mode : DVD-Video

Text #2
ID : 189 (0xBD)-33 (0x21)
Format : RLE
Format/Info : Run-length encoding
Muxing mode : DVD-Video

Menu



With these settings



Complete name : D:\Beef Bonus DVD-01-.mkv
Format : Matroska
Format version : Version 4 / Version 2
File size : 79.4 MiB
Duration : 6mn 11s
Overall bit rate : 1 791 Kbps
Encoded date : UTC 2016-10-04 01:39:33
Writing application : mkvmerge v9.3.1 ('Mask Machine') 64bit
Writing library : libebml v1.3.4 + libmatroska v1.4.5
DURATION : 00:06:11.954000000
NUMBER_OF_FRAMES : 32065
NUMBER_OF_BYTES : 83006528
_STATISTICS_WRITING_APP : mkvmerge v9.3.1 ('Mask Machine') 64bit
_STATISTICS_WRITING_DATE_UTC : 2016-10-04 01:39:33
_STATISTICS_TAGS : BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 6mn 11s
Bit rate : 1 755 Kbps
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 4:3
Original display aspect ratio : 4:3
Frame rate mode : Constant
Frame rate : 86.207 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Bits/(Pixel*Frame) : 0.049
Stream size : 77.8 MiB (98%)
Writing library : x265 2.0+5-98a948623fdc:[Windows][GCC 5.4.0][64 bit] 8bit+10bit+12bit
Encoding settings : wpp / ctu=64 / min-cu-size=8 / max-tu-size=32 / tu-intra-depth=1 / tu-inter-depth=1 / me=1 / subme=2 / merange=57 / no-rect / no-amp / max-merge=2 / temporal-mvp / no-early-skip / rskip / rdpenalty=0 / no-tskip / no-tskip-fast / strong-intra-smoothing / no-lossless / no-cu-lossless / no-constrained-intra / no-fast-intra / open-gop / no-temporal-layers / interlace=0 / keyint=250 / min-keyint=25 / scenecut=40 / rc-lookahead=20 / lookahead-slices=0 / bframes=4 / bframe-bias=0 / b-adapt=2 / ref=3 / limit-refs=3 / no-limit-modes / weightp / no-weightb / aq-mode=1 / qg-size=32 / aq-strength=1.00 / cbqpoffs=0 / crqpoffs=0 / rd=3 / psy-rd=2.00 / rdoq-level=0 / psy-rdoq=0.00 / no-rd-refine / signhide / deblock=0:0 / sao / no-sao-non-deblock / b-pyramid / cutree / no-intra-refresh / rc=crf / crf=22.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ipratio=1.40 / pbratio=1.30
Default : Yes
Forced : No



It came out like this

https://www.sendspace.com/file/07p8mk

brucethemoose
7th October 2016, 04:28
Anyone else experiencing a memory leak in the last StaxRip test? (1.3.8.7)

I caught it using 14GB of memory by itself... when it wasn't even encoding anything:

https://github.com/stax76/StaxRip/issues/111

AMED
7th October 2016, 06:24
Anyone else experiencing a memory leak in the last StaxRip test? (1.3.8.7)

I caught it using 14GB of memory by itself... when it wasn't even encoding anything:

https://github.com/stax76/StaxRip/issues/111

Just wondering if anyone has seen a memory leak in Staxrip?

http://s21.postimg.org/5whg2rqjb/Staxrip.png

I saw this after doing 2 days straight of encoding.

StaxRip x64 : 1.3.8.7
OS : Windows Server 2012 R2 Standard
Language : English (New Zealand)
CPU : Intel(R) Xeon(R) CPU E5645 @ 2.40GHz
GPU : Microsoft Basic Display Adapter
I'm encoding with Vapoursynth R33.1 and resizing with spline36 and denoising with mvdegrain.Yup i'm seeing on both my machines. The dual quad core CPUs running Server 2012R2 leaks worse than my quad core I7 running windows 10.

Windows 10 machine has been encoding for 3 days and memory usage is 2559 MB
Server 2012R2 machine has been encoding for 1 1/2 days and memory usage is 1572.6 MB.

Leo 69
7th October 2016, 06:52
I haven't got any leaks.. Encoding the movie for 3 days already with x265 and Staxrip.exe usage is 265.5 Mb.
Quad-core i5 on Windows 10 Pro.

AMED
7th October 2016, 08:56
Is that 1 encode job for 3 days or multiple encode jobs?

burfadel
7th October 2016, 09:15
Is that 1 encode job for 3 days or multiple encode jobs?

Surely it wouldn't be a single movie. If it were a 2 hour movie and took 72 hours (3 days) to complete, the speed of compression is 1/36 real time. If the movie is at 23.976 fps, that means an encode rate of 0.666 fps. Devilishly slow :devil: :D