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

stax76
30th August 2015, 17:03
No "QSV --avqsv --output-res -o - -c raw | NVEncC --y4m"?

T_T

I've added it but it performs very bad, using 1080p input and output I get 70 fps and about 30% CPU!

"D:\Projekte\GitHub\staxrip\bin\Apps\QSVEncC\QSVEncC64.exe" --avqsv --output-file - --codec raw --output-res 1920x1080 --input-file "D:\Temp\Encoding\test.mp4" | "D:\Projekte\GitHub\staxrip\bin\Apps\NVEncC\NVEncC64.exe" --cqp 20:23:25 --y4m --input-res 1920x1080 --fps 29.970030 --input "-" --output "D:\Temp\Encoding\test temp files\test_out.h264"

QSVEnc 2.11 (x64), based on Intel(R) Media SDK Encoding Sample 6,0,0,98947
OS Windows 10 (x64)
CPU Info Intel Core i5-6600K @ 3.50GHz [TB: 3.79GHz] (4C/4T) <Skylake>
GPU Info Intel HD Graphics 530 (24EU) 1150MHz (10.18.15.4274)
Media SDK QuickSyncVideo (hardware encoder), 2nd GPU, API v1.16
Async Depth 4 frames
Buffer Memory d3d11, 1 input buffer, 11 work buffer
Input Info avcodec video: H.264/AVC, 1920x1080, 30000/1001 fps
Output 1920x1080p 1:1 29.970fps (30000/1001fps)
NVEnc 1.10 (x64), using NVENC API v5.0
OS Version Unknown (x64)
CPU Intel Core i5-6600K @ 3.50GHz [TB: 3.80GHz] (4C/4T)
GPU GeForce GTX 960 (8 EU) @ 1240 MHz (355.60)
Input Buffers CUDA, 16 frames
Input Info y4m (yv12) -> nv12 [AVX2], 1920x1080, 30000/1001 fps
Output Info H.264/AVC high
1920x1080p 1:1 29.970fps (30000/1001fps)
Rate Control CQP
CQP I:20 P:23 B:25
GOP length 300 frames
B frames 3 frames
Ref frames 3 frames
MV Quality Q-pel
CABAC/deblock cabac / on
encoded 2384 frames, 70.71 fps, 745750.25 kbps, 7071.68 MB
encode time 0:00:34 / CPU Usage: 20.58
frame type IDR 2384
frame type I 2384, total size 7071.68 MB
encoded 2384 frames, 71.68 fps, 5577.59 kbps, 52.89 MB
encode time 0:00:33 / CPU Usage: 5.56%
frame type IDR 8
frame type I 8, avgQP 20.00, total size 0.86 MB
frame type P 596, avgQP 23.00, total size 18.59 MB
frame type B 1780, avgQP 25.00, total size 33.44 MB

Yups
30th August 2015, 17:35
QS HEVC VBR 5000

TU1= 38 fps
TU2= 38 fps
TU3= 75 fps
TU4= 75 fps
TU5= 75 fps
TU6= 150 fps
TU7= 150 fps

There are actually only three different quality modes in HEVC currently. From a performance point of view only TU6/7 makes sense, the others are too slow. CPU load is higher with faster TUs. Unfortunately some features like Lookahead or mbbrc doesn't work with HEVC, because of that I doubt it can beat a proper configured H264.

cegy
30th August 2015, 23:14
many thanks for the update stax76 but it seems you might of overlooked a setting which i can't find which we did talk about here (http://forum.doom9.org/showthread.php?p=1730144#post1730144) about disabling or maybe making automatic to work with the first indexer/filter that you want but if it fails it will bring up this dialog i've also noticed another thing thats different aswell. the main reason why i'm not that keen on it as if you've got alot of videos to encode with the same base settings .... its more of a nag when you just want to use the same basesettings each time also it seems it does remember/use the template that you wanted aswell like 1.1.8 did i think the startup template might of been the default template that it would of used i'm not quite sure.

however it works like this at the moment between the 1.1.8.0 vs 1.3.1.6 (at least for myself)

1.1.8.0 (what made staxrip so nice to use)
1. drag file onto staxrip, file loaded, file added, next
2. next file, drag file onto staxrip, file loaded etc.. (same steps as #1 really, from all this it seems it uses the same template all the time with the same filter etc..)
3. encode the lot

1.3.1.6
1. drag file onto staxrip, dialog pops you asking for which preferred source filter, pick which one i want, file loaded, next
2. next file to load, drag file onto staxrip, dialog pops you asking for which preferred source filter, which template do i want to use, pick which one i want, file added, next
3. same steps as #2 over again
4. encode the lot

suggestion maybe add a option to assign a filter to a template which it would use by default (like 1.1.8.0?) and if it fails it would bring up the dialog box maybe ?

dejong12
31st August 2015, 00:19
I like your suggestion. As you described, the best way to do this I think, is when loading the first file you select an indexer and template and use that indexer/template for each subsequent file and when it fails, bring up the dialog to select another indexer/template.

stax76
31st August 2015, 01:42
How about changing the name from 'Automatic' to 'Manual' and show the filter selection dialog only when the current name is 'Manual'? Changing the new default from 'Manual' back to 'Automatic' would then bring the old behavior back.

JohnLai
31st August 2015, 04:02
I've added it but it performs very bad, using 1080p input and output I get 70 fps and about 30% CPU!



QSVEnc 2.11 (x64), based on Intel(R) Media SDK Encoding Sample 6,0,0,98947
OS Windows 10 (x64)
CPU Info Intel Core i5-6600K @ 3.50GHz [TB: 3.79GHz] (4C/4T) <Skylake>
GPU Info Intel HD Graphics 530 (24EU) 1150MHz (10.18.15.4274)
Media SDK QuickSyncVideo (hardware encoder), 2nd GPU, API v1.16
Async Depth 4 frames
Buffer Memory d3d11, 1 input buffer, 11 work buffer
Input Info avcodec video: H.264/AVC, 1920x1080, 30000/1001 fps
Output 1920x1080p 1:1 29.970fps (30000/1001fps)
NVEnc 1.10 (x64), using NVENC API v5.0
OS Version Unknown (x64)
CPU Intel Core i5-6600K @ 3.50GHz [TB: 3.80GHz] (4C/4T)
GPU GeForce GTX 960 (8 EU) @ 1240 MHz (355.60)
Input Buffers CUDA, 16 frames
Input Info y4m (yv12) -> nv12 [AVX2], 1920x1080, 30000/1001 fps
Output Info H.264/AVC high
1920x1080p 1:1 29.970fps (30000/1001fps)
Rate Control CQP
CQP I:20 P:23 B:25
GOP length 300 frames
B frames 3 frames
Ref frames 3 frames
MV Quality Q-pel
CABAC/deblock cabac / on
encoded 2384 frames, 70.71 fps, 745750.25 kbps, 7071.68 MB
encode time 0:00:34 / CPU Usage: 20.58
frame type IDR 2384
frame type I 2384, total size 7071.68 MB
encoded 2384 frames, 71.68 fps, 5577.59 kbps, 52.89 MB
encode time 0:00:33 / CPU Usage: 5.56%
frame type IDR 8
frame type I 8, avgQP 20.00, total size 0.86 MB
frame type P 596, avgQP 23.00, total size 18.59 MB
frame type B 1780, avgQP 25.00, total size 33.44 MB

Now that is strange....

How about resizing performance fps using QSV VPP? From 1920x1080 to 1280x720?

Since your source is 1920x1080, just use QSVEncC64.exe --avqsv --output-res 1280x720

As for NVEncC, no need to specifiy --input-res

cegy
31st August 2015, 11:05
How about changing the name from 'Automatic' to 'Manual' and show the filter selection dialog only when the current name is 'Manual'? Changing the new default from 'Manual' back to 'Automatic' would then bring the old behavior back.

not quite sure how you mean as such :confused: maybe give an example of how it would work maybe ?

stax76
31st August 2015, 11:14
Now that is strange....

How about resizing performance fps using QSV VPP? From 1920x1080 to 1280x720?

Since your source is 1920x1080, just use QSVEncC64.exe --avqsv --output-res 1280x720

As for NVEncC, no need to specifiy --input-res

resizing from 1080p to 720p runs with 130 fps.

JohnLai
31st August 2015, 11:49
resizing from 1080p to 720p runs with 130 fps.

Hmm......this is strange....

I was expecting the 1080p --> 720p to reach 188fps.

How about fps result from using total QSV path alone?

QSVEncC64.exe --output-res 1280x720 -c h264 --input-file "[1080p].h264" -o "[720p].h264"

stax76
31st August 2015, 12:13
@cegy
@dejong12

Regarding the source filter selection dialog I made the following changes:

add source filter profile name 'Manual' to AviSynth and VapourSynth filter profiles but did not reset the profiles, there are two different ways to reset them manually.
make 'Manual' the default in templates and reset templates, template backups are available

the source filter selection dialog is only shown when the source filter name is 'Manual'.

before opening a source file it's possibly to choose 'Manual', 'Automatic' or any of the available source filter profiles in the filters context menu

dejong12
31st August 2015, 12:15
@cegy
@dejong12

Regarding the source filter selection dialog I made the following changes:

add source filter profile name 'Manual' to AviSynth and VapourSynth filter profiles but did not reset the profiles, there are two different ways to reset them manually.
make 'Manual' the default in templates and reset templates, template backups are available

the source filter selection dialog is only shown when the source filter name is 'Manual'.

before opening a source file it's possibly to choose 'Manual', 'Automatic' or any of the available source filter profiles in the filters context menu
Thanks for adding this, could you provide us with the latest updated StaxRip for us to test?

stax76
31st August 2015, 12:22
Thanks for adding this, could you provide us with the latest updated StaxRip for us to test?

Yes, once I've tested it I can upload a test build.

@JohnLai

decoding with ffms2 encoding 1080p using nv 264 runs at 260 fps.

JohnLai
31st August 2015, 12:34
@JohnLai

decoding with ffms2 encoding 1080p using nv 264 runs at 260 fps.

Hmm...probably the copyback operation of '-c raw' has too much overhead.
>.<

There goes my hardware based resizer hope......

Sorry for the trouble, stax76.

cegy
31st August 2015, 13:13
Yes, once I've tested it I can upload a test build.

@JohnLai

decoding with ffms2 encoding 1080p using nv 264 runs at 260 fps.

this is great news and sure would be nice to test it out aswell :thanks:

stax76
31st August 2015, 17:06
@NikosD

I can't do much about the samples, 1 and 2 are source filter problems and 3 is MediaInfo reporting no audio. I've updated MediaInfo now but it did not help with sample 3. I'll take a look regarding QSVEncC.

NikosD
31st August 2015, 17:17
About 1) and 2)

Would it be possible to adjust the error messages in a way that it could be easier for a user to understand such cases ?

Meaning that is not a problem/bug of StaxRip but of the source filter

And if it's possible to not crash the app completely.

The app crashes in a way that looks like an internal error of the app, not of the video source.

About 3)

MediaInfo can't read that file due to a checksum error, but eac3to handles this file without problems.

What is the relationship between MediaInfo and audio stream handling of StaxRip ?

Why is it important if MediaInfo recognises the audio stream and how come StaxRip using eac3to can convert the file but using batch file mode, fails.

About QSVEncC do whatever it's possible and useful for most people.

I remember telling me that those options of RC are not easy to change.

Thanks.

stax76
31st August 2015, 17:47
I'll try to improve the error handling. The eac3to demuxing code currently cannot be used without GUI, it could be changed but it could be a bit work and might not be worth the time... in batch mode or when the eac3to demuxer is disabled StaxRip will use the m2ts file as audio source, most container types like mkv and m2ts can be used as audio source files but it will only work if MediaInfo reports the containing audio streams. Regarding hiding QSVEncC modes, I'll take another look, if it's too difficult a message box could be shown when a invalid mode is selected.

NikosD
31st August 2015, 17:52
OK, now it's clear.

Regarding QSVEncC, you can check the RC options by using -check - features but now that you have Skylake, you can check by trial and error too.

Actually the hands on tests are always more reliable.

burfadel
31st August 2015, 22:55
@Stax,
There has been (for a little while) another setting for AQ in x265. The new setting is --aq-mode 3, which is a variation of auto variance AQ (aq-mode 2). The mode 3 adds bias for dark scenes.

cegy
1st September 2015, 11:51
stax76 i do have one small suggestion which might be nice which is when it comes to both dgindexim and dgindexnv is for it to look for the .dll in the same dir as the exe if its not found then ask the user to locate it

stax76
1st September 2015, 17:38
stax76 i do have one small suggestion which might be nice which is when it comes to both dgindexim and dgindexnv is for it to look for the .dll in the same dir as the exe if its not found then ask the user to locate it

it's a bit difficult, the DLL might or might not be in a 'x64 Binaries' sub folder, since dll and exe are internally different objects it would be a circular reference, probably not worth the effort

There has been (for a little while) another setting for AQ in x265. The new setting is --aq-mode 3, which is a variation of auto variance AQ (aq-mode 2). The mode 3 adds bias for dark scenes.

Thanks, I've added it.

dejong12
2nd September 2015, 14:44
I have strange issue. On my laptop, when I try to open a .ts file with DGSource indexer, nothing happens at DGIndexNV in the log files. When I remove the -a and -h arguments at Tools -> Settings -> Demuxing -> DGIndexNV, DGIndexNV.exe pops up, but nothing happens. Only when I drag the .ts file into DGIndex.nv, a .dgi is created and StaxRip loads the .dgi file, after I close DGIndexNV.exe manually.

Yups
2nd September 2015, 20:22
QSVEnc 2.12 has been released.

burfadel
2nd September 2015, 21:21
Mediainfo v0.7.77 released.

NikosD
3rd September 2015, 10:22
I'm getting a mess of artifacts using QSV HEVC encoding, was anybody more successful?

Yes there is a problem somewhere within the first 10 seconds which I believe is caused by fps*10= GOP Length from QSVEnc. Try Intels default 256 GOP, it seems to work.


According to the developer of QSVEncC, the artifacts produced by QSVEncC and HEVC HW of Skylake, seem to depend on the decoder.

He says for example, that using Win10 with WMP12 and the built-in H265 decoder or using CUVID decoder, there are no artifacts (!), but using libavcodec or iGPU / dGPU DXVA there are artifacts.

It probably needs a driver fix or tuning.

stax76
3rd September 2015, 11:04
According to the developer of QSVEncC, the artifacts produced by QSVEncC and HEVC HW of Skylake, seem to depend on the decoder.

He says for example, that using Win10 with WMP12 and the built-in H265 decoder or using CUVID decoder, there are no artifacts (!), but using libavcodec or iGPU / dGPU DXVA there are artifacts.

It probably needs a driver fix or tuning.

Latest QSVEncC fixes it. :)

NikosD
3rd September 2015, 11:06
Really ?

He posted his comments after 2.12 release, explaining what is still happening with artifacts.

I wouldn't be surprised if you see them again :)

stax76
3rd September 2015, 11:27
I tried one sample with a few different settings, so far it looks good.

stax76
3rd September 2015, 12:36
test build I promised:

https://www.mediafire.com/folder/0jakce45o99kb/StaxRip

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

cegy
3rd September 2015, 13:20
test build I promised:

https://www.mediafire.com/folder/0jakce45o99kb/StaxRip

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

thank you very much however i'm abit confused as what i need to do. i will admit that the "filter/source" windows doesn't pop up anymore and after checking here (http://forum.doom9.org/showthread.php?p=1736574#post1736574) for more details to make sure but its still asking for the template each time i add a new file which isn't like the old behavior and to clear up any mistakes from this (http://forum.doom9.org/showthread.php?p=1736526#post1736526) is that 1.1.8.0 never asks you to pick the template again once you add a new file as it would reuse the same template again :(

i've also notice that if your only using just say x264 on its own... that it won't tell you any stats etc... of the encode from x264 like the random spam at the bottom (at end of a encode) and the encoding fps with bitrate :o which you would normally see if you ran it from cmdline yourself. due to unsure when this "bug" ? happen i started to look back at other versions (only a few)

staxrip 1.1.8.0, 1.2.2.2 (32bit), 1.2.2.2 (64bit pipped) all show the info in the log file (like below)

avs [info]: 624x352p 0:0 @ 25/1 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
x264 [info]: profile High, level 3.1
x264 [info]: frame I:70 Avg QP:14.67 size: 28871
x264 [info]: frame P:3886 Avg QP:15.80 size: 6195
x264 [info]: frame B:8529 Avg QP:19.03 size: 1643
x264 [info]: consecutive B-frames: 6.8% 5.0% 4.0% 84.2%
x264 [info]: mb I I16..4: 17.4% 29.4% 53.2%
x264 [info]: mb P I16..4: 7.6% 2.9% 0.8% P16..4: 58.1% 0.0% 0.0% 0.0% 0.0% skip:30.6%
x264 [info]: mb B I16..4: 0.5% 0.2% 0.0% B16..8: 20.4% 0.0% 0.0% direct:13.6% skip:65.3% L0:32.2% L1:43.6% BI:24.2%
x264 [info]: 8x8 transform intra:26.0% inter:33.5%
x264 [info]: coded y,uvDC,uvAC intra: 44.4% 74.1% 62.8% inter: 15.3% 12.3% 2.1%
x264 [info]: i16 v,h,dc,p: 53% 28% 14% 4%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 15% 16% 38% 4% 5% 5% 5% 4% 6%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 28% 21% 11% 6% 6% 7% 7% 6% 7%
x264 [info]: i8c dc,h,v,p: 42% 28% 23% 6%
x264 [info]: Weighted P-Frames: Y:1.3% UV:0.7%
x264 [info]: kb/s:642.45
encoded 12485 frames, 80.51 fps, 642.45 kb/s

staxrip 1.3.1.5, 1.3.1.6 (few days ago), and now your latest 1.3.1.6 (test) don't show this info in the log file.

stax76
3rd September 2015, 20:34
but its still asking for the template each time i add a new file which isn't like the old behavior and to clear up any mistakes from this is that 1.1.8.0 never asks you to pick the template again once you add a new file as it would reuse the same template again

I thought 1.1.8.0 also showed the template dialog, I don't have tools for the old version so I can't compare it, I looked at the code at SourceForge and I can't find code that reuses the same template. Currently it shows always the template dialog unless only one template exists. Perhaps you had only one template? There are 3 possible actions that could happen when a new file is added:


show template dialog like it's now
load the default template
store the last state and load that


you say the old StaxRip used the last method, right? I can't see this in the old code however.

I'm not sure which of the three methods should be the default, a option using a checkbox would be easy to add, method three would be some work and I don't see much sense in method three. For me just loading the default template would be fine, I use always the default templates however, for people that use often different templates it might not be ideal.

i've also notice that if your only using just say x264 on its own... that it won't tell you any stats etc... of the encode from x264 like the random spam at the bottom (at end of a encode) and the encoding fps with bitrate which you would normally see if you ran it from cmdline yourself. due to unsure when this "bug" ? happen i started to look back at other versions (only a few)

either it behaves different on your system or I don't understand your description, I compared x264 running by StaxRip and running standalone with the command shell and could not see a difference, in both cases when it runs it show these lines:

avs [info]: 1920x1080p 0:0 @ 30000/1001 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
x264 [info]: profile Constrained Baseline, level 4.0

when it completes it outputs this in both cases:

x264 [info]: frame I:10 Avg QP:16.20 size:252777
x264 [info]: frame P:2377 Avg QP:18.99 size: 33216
x264 [info]: mb I I16..4: 100.0% 0.0% 0.0%
x264 [info]: mb P I16..4: 6.4% 0.0% 0.0% P16..4: 57.7% 0.0% 0.0% 0.0% 0.0% skip:35.9%
x264 [info]: coded y,uvDC,uvAC intra: 21.2% 61.6% 11.2% inter: 19.7% 27.5% 1.2%
x264 [info]: i16 v,h,dc,p: 33% 29% 24% 13%
x264 [info]: i8c dc,h,v,p: 33% 27% 24% 16%
x264 [info]: kb/s:8184.48
encoded 2387 frames, 258.87 fps, 8184.48 kb/s

cegy
3rd September 2015, 20:50
I thought 1.1.8.0 also showed the template dialog, I don't have tools for the old version so I can't compare it, I looked at the code at SourceForge and I can't find code that reuses the same template. Currently it shows always the template dialog unless only one template exists. Perhaps you had only one template? There are 3 possible actions that could happen when a new file is added:


show template dialog like it's now
load the default template
store the last state and load that


you say the old StaxRip used the last method, right? I can't see this in the old code however.

I'm not sure which of the three methods should be the default, a option using a checkbox would be easy to add, method three would be some work and I don't see much sense in method three. For me just loading the default template would be fine, I use always the default templates however, for people that use often different templates it might not be ideal.



either it behaves different on your system or I don't understand your description, I compared x264 running by StaxRip and running standalone with the command shell and could not see a difference, in both cases when it runs it show these lines:

avs [info]: 1920x1080p 0:0 @ 30000/1001 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
x264 [info]: profile Constrained Baseline, level 4.0

when it completes it outputs this in both cases:

x264 [info]: frame I:10 Avg QP:16.20 size:252777
x264 [info]: frame P:2377 Avg QP:18.99 size: 33216
x264 [info]: mb I I16..4: 100.0% 0.0% 0.0%
x264 [info]: mb P I16..4: 6.4% 0.0% 0.0% P16..4: 57.7% 0.0% 0.0% 0.0% 0.0% skip:35.9%
x264 [info]: coded y,uvDC,uvAC intra: 21.2% 61.6% 11.2% inter: 19.7% 27.5% 1.2%
x264 [info]: i16 v,h,dc,p: 33% 29% 24% 13%
x264 [info]: i8c dc,h,v,p: 33% 27% 24% 16%
x264 [info]: kb/s:8184.48
encoded 2387 frames, 258.87 fps, 8184.48 kb/s

load the default template << if this also means the start up template then yes this could why i don't see it asking me to pick another template (there's all the default templates and another 5 more and not just the one whiles using 1.1.8.0) also i find it odd how both 1.1.8.0 and 1.2.2.2 shows its fine in the log file... do you have any suggestions for me as i'm clueless as what else to try as all it shows is (rest of the log file is file its just the x264 part and nothing else)

avs [info]: 624x352p 0:0 @ 25/1 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
x264 [info]: profile High, level 3.0

Start: 15:30:02
End: 15:33:58
Duration: 00:01:55

and not the full thing

avs [info]: 624x352p 0:0 @ 25/1 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
x264 [info]: profile High, level 3.0
x264 [info]: frame I:70 Avg QP:14.67 size: 28871
x264 [info]: frame P:3886 Avg QP:15.80 size: 6195
x264 [info]: frame B:8529 Avg QP:19.03 size: 1643
x264 [info]: consecutive B-frames: 6.8% 5.0% 4.0% 84.2%
x264 [info]: mb I I16..4: 17.4% 29.4% 53.2%
x264 [info]: mb P I16..4: 7.6% 2.9% 0.8% P16..4: 58.1% 0.0% 0.0% 0.0% 0.0% skip:30.6%
x264 [info]: mb B I16..4: 0.5% 0.2% 0.0% B16..8: 20.4% 0.0% 0.0% direct:13.6% skip:65.3% L0:32.2% L1:43.6% BI:24.2%
x264 [info]: 8x8 transform intra:26.0% inter:33.5%
x264 [info]: coded y,uvDC,uvAC intra: 44.4% 74.1% 62.8% inter: 15.3% 12.3% 2.1%
x264 [info]: i16 v,h,dc,p: 53% 28% 14% 4%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 15% 16% 38% 4% 5% 5% 5% 4% 6%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 28% 21% 11% 6% 6% 7% 7% 6% 7%
x264 [info]: i8c dc,h,v,p: 42% 28% 23% 6%
x264 [info]: Weighted P-Frames: Y:1.3% UV:0.7%
x264 [info]: kb/s:642.45
encoded 12485 frames, 80.51 fps, 642.45 kb/s

Start: 15:30:02
End: 15:33:58
Duration: 00:01:55

i've even deleted all the settings folders i can find and started from fresh which still resulted in the same outcome

stax76
3rd September 2015, 21:08
it could be threading issue happening only on a few systems, not being able to reproduce it makes it very difficult for me to find the reason.

cegy
3rd September 2015, 21:14
it could be threading issue happening only on a few systems, not being able to reproduce it makes it very difficult for me to find the reason.

yah which can be a a pain in the backside to try and fix, i'm not to sure if there's anything else i can try as this is from a fairly fresh install of windows 7 (just over a week ago)

i did notice one thing between the logs from the older versions there's a space after the first 3 lines whiles still keeping the stats from x264

avs [info]: 624x352p 0:0 @ 25/1 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
x264 [info]: profile High, level 3.0

x264 [info]: frame I:70 Avg QP:14.67 size: 28871
x264 [info]: frame P:3886 Avg QP:15.80 size: 6195
x264 [info]: frame B:8529 Avg QP:19.03 size: 1643
x264 [info]: consecutive B-frames: 6.8% 5.0% 4.0% 84.2%
x264 [info]: mb I I16..4: 17.4% 29.4% 53.2%
x264 [info]: mb P I16..4: 7.6% 2.9% 0.8% P16..4: 58.1% 0.0% 0.0% 0.0% 0.0% skip:30.6%
x264 [info]: mb B I16..4: 0.5% 0.2% 0.0% B16..8: 20.4% 0.0% 0.0% direct:13.6% skip:65.3% L0:32.2% L1:43.6% BI:24.2%
x264 [info]: 8x8 transform intra:26.0% inter:33.5%
x264 [info]: coded y,uvDC,uvAC intra: 44.4% 74.1% 62.8% inter: 15.3% 12.3% 2.1%
x264 [info]: i16 v,h,dc,p: 53% 28% 14% 4%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 15% 16% 38% 4% 5% 5% 5% 4% 6%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 28% 21% 11% 6% 6% 7% 7% 6% 7%
x264 [info]: i8c dc,h,v,p: 42% 28% 23% 6%
x264 [info]: Weighted P-Frames: Y:1.3% UV:0.7%
x264 [info]: kb/s:642.45
encoded 12485 frames, 80.51 fps, 642.45 kb/s

NikosD
4th September 2015, 06:15
test build I promised:

https://www.mediafire.com/folder/0jakce45o99kb/StaxRip



Regarding the new build:

Thanks for the new additions and updates of the companion apps.

1) About QSVEncC GUI

a) You added the "Profile" setting but only for H.264.
For HEVC and MPEG2 formats, profile setting is missing.

b) You added the "Level" setting for all formats, but with the same values.

There is no level value of L6.0 or L6.1 or L6.2 for H.264 and the level values of MPEG2 are not numbers AFAIK.

c) Now, with the new GUI, sometimes when I use the "Execute Command Line" option, the QSVEncC CLI is crashing, while executing transcoding process via StaxRip using QSVEncC GUI is fine .

But not always, so I can't tell you how to reproduce it for sure.

I'm just mentioning it in order to pay attention and maybe manage to reproduce it.


2) The error handling routines, seem unchanged.

NikosD
4th September 2015, 14:34
@Stax76

Update:

The -level and profile strings are:
(using Google translator for this page)

http://rigaya34589.blog135.fc2.com/blog-entry-337.html

The values are all in English.

--level

h264: auto, 1, 1b, 1.1, 1.2, 1.3, 2, 2.1, 2.2, 3, 3.1, 3.2, 4, 4.1, 4.2, 5, 5.1, 5.2

HEVC: auto, 1, 2, 2.1, 3, 3.1 , 4, 4.1, 5, 5.1, 5.2, 6, 6.1, 6.2

mpeg2: auto, low, main, high, High1440


--profile

h264: auto, Baseline, Main, High

HEVC: auto, main

mpeg2: auto, Simple, Main, High

I asked for adding those values in help switch -h and rigaya told me that he will do it in the next version.

Lupissimo
4th September 2015, 17:01
Quote:
Originally Posted by Lupissimo View Post
Why have the deinterlace options: "Select even" and "Yadif"
been omitted in version StaxRip.1315? At least "select even" is absolutely neccessary for 720p HDTV encodings.
Next version will have select even, you can integrate yadif as profile, it can be downloaded here:
UnQuote

I have downloaded 1.3.1.7 but cannot find "select even" deinterlacer!?

stax76
4th September 2015, 20:41
@NikosD

Thanks for the feedback, here is a further improved build:

https://www.mediafire.com/folder/0jakce45o99kb/StaxRip

@Lupissimo

It should be there when you reset the profiles, there is a reset button in the profiles editor.

NikosD
4th September 2015, 21:01
@NikosD

Thanks for the feedback, here is a further improved build:

https://www.mediafire.com/folder/0jakce45o99kb/StaxRip


No bugs for QSVEncC and you definitely improved error handling - it's more descriptive.

Thanks.

Lupissimo
4th September 2015, 21:23
After using the "restore defaults" button ( I cannot find a "Reset" button) the profile looks like this:
[Field]
IVTC = Telecide(guide=1).Decimate()
TDeint = TDeint()
FieldDeinterlace = FieldDeinterlace()
SangNom2 = SangNom2()
vinverse2 = vinverse2()

Probably I am looking in the wrong place??!!

stax76
4th September 2015, 21:52
It's in the 'Misc' section, I'll move it to the field section. :)

NikosD
5th September 2015, 05:33
I don't know if I'm doing something wrong, but for me the main drawback left for StaxRip is the lack of flexibility regarding video source changes in the same session.

For example, I choose a video source from the "Automatic" menu of options or a specific source manually.

If for whatever reason I want to change to another one (due to an error in the specific source regarding the specific file or to test which source is faster to the specific file etc) I always (almost) have to CLOSE the app, DELETE the temp files and RE-OPEN StaxRip just to change source!

Because if I don't to do that sequence of operations, the most probable thing to happen is a crash of the app.

There are only a few times that I can change video source without closing the app and deleting temp files and StaxRip allows me to continue without crashing.

This is a time-consuming and mainly frustrating situation and I think that StaxRip should have a more robust workflow allowing video source change in the same session, especially when the app has a broad choice of video source by design and counts on them in order to read a video file.

Because if a source fails to open a file, there is a possibility another source to manage to open it and sometimes you have to check all of them in order to achieve maximum compatibility and performance.

stax76
5th September 2015, 10:17
I can't follow you here, if you want another source filter you can just use the context menu, a new feature is that this works even with DGDource, you can switch from FFVideoSource to DGDource dynamically and vice versa from DGSource to FFVideoSource, indexing happens automatically if necessary. If you want another source file, you can just open it on.

NikosD
5th September 2015, 10:24
OK.

I use FFVideo source and all things go well and finishes the transcoding.

Without closing the app, I want to try on the same clip, just after FFVideo another source like LWLib or LSMASH etc so I change source from the left menu.

The change of source for the same already transcoded clip is crashing the app.

How could I do that without crashing StaxRip ?

stax76
5th September 2015, 10:45
If it's reproducible for me I can take a look, if it's not reproducible for me like a few issues reported recently then it will be difficult.

NikosD
5th September 2015, 10:49
First of all I'm doing the tests with the default settings, after decompression of the app without any change in the preferences.

It happens "all the time" with me, maybe because I usually try difficult clips, that it is possible that some sources (or all of them) can't handle properly.

I'll try again with easier clips and report back.

On the other hand, a good test would be to transcode a clip with one source successfully, close the app and rerun the transcode successfully choosing another source.

If the app fails to successfully transcode the clip twice in one session using two different sources, then it's definitely an issue for the app.

stax76
5th September 2015, 11:03
If you use TS regularly which I think you do than it's the first explanation for why you see problems, TS is notorious for causing problems, best source filter for TS is clearly DGSource.

cegy
5th September 2015, 12:11
@NikosD

Thanks for the feedback, here is a further improved build:

https://www.mediafire.com/folder/0jakce45o99kb/StaxRip

@Lupissimo

It should be there when you reset the profiles, there is a reset button in the profiles editor.

hi, stax76 i can confirm both the template dialog isn't being asked when giving it another new file (uses the template from before ;)) which is nice and i was shocked to notice the x264 stats which i was on about are also now showing in the log file :D
many :thanks: once again for the understanding of what we've missed from the older staxrip (only a few things really :p)

p.s. for the codec comparison is there away for it to detect if vapoursyth is installed or not and if not tell the user its needed before using the codec comparison (one minor thing)

stax76
5th September 2015, 13:31
hi, stax76 i can confirm both the template dialog isn't being asked when giving it another new file (uses the template from before ;)) which is nice and i was shocked to notice the x264 stats which i was on about are also now showing in the log file :D
many :thanks: once again for the understanding of what we've missed from the older staxrip (only a few things really :p)

p.s. for the codec comparison is there away for it to detect if vapoursyth is installed or not and if not tell the user its needed before using the codec comparison (one minor thing)

There is now a option in the settings dialog for either showing the template selection dialog or loading the default template.

I'm glad the x264 log problem is gone and hope it don't happen again (I've not changed any relating code).

For the video comparison VapourSynth shouldn't be needed, I checked the code, it's always using AviSynth+ and FFVideoSource.

cegy
5th September 2015, 13:40
There is now a option in the settings dialog for either showing the template selection dialog or loading the default template.

I'm glad the x264 log problem is gone and hope it don't happen again (I've not changed any relating code).

For the video comparison VapourSynth shouldn't be needed, I checked the code, it's always using AviSynth+ and FFVideoSource.

oh i wasn't aware of that lol