StaxRip

[stax76]

About

StaxRip is a video encoding GUI for Windows, it executes and controls console apps like x265, NVEnc, mkvmerge or ffmpeg and uses the scripting based frame servers AviSynth and VapourSynth for video processing.


Website

https://github.com/staxrip/staxrip

[Groucho2004]

All AviSynth plugins except ffms2 and l-smash are gone

Why? There are quite a number of working 64 Bit plugs, see here (http://forum.doom9.org/showthread.php?t=169832) for example.

The latest AviSynth+ binary build is here:
http://forum.doom9.org/showthread.php?p=1711770#post1711770

Nope, the latest builds are here (http://www.avs-plus.net/builds).

[stax76]

I've not known this links so thanks again, did you notice AVSMeter x64 is included (Tools/Advanced/AVSMeter)? :)

[Groucho2004]

I've not known this links so thanks, did you notice AVSMeter x64 is included (Tools/Advanced/AVSMeter)? :)
I don't use GUIs so I did not download it. However, quite a number of people seem to be using staxrip and this way 64 Bit AVS+ will get a lot more testing.

[NikosD]

Frank, I have sent you an email regarding DSS2 mod which I think it works with x64

[stax76]

Thanks, it works! Next version will have ffms2, l-smash, DSS2, SangNom2, checkmate, RgTools, DGDecNV works and DGDecIM will be integrated shortly.

[NikosD]

Great!

Have you contacted Rigaya for the HW encoders not being able to use AVS with x64 versions ?

[stax76]

I mailed him 22 hours so hope he replies soon otherwise I might have to use piping with ffmpeg meanwhile.

[NikosD]

From your first posts I can see that maybe your decision of abandoning completely the x86 version of a program that is based so much upon Avisynth, is probably rushed.

I think the release of madVR x64 and the obvious weakness of LAV HEVC x86 decoder, have created a "madness" with 64bit version for everything, but that seems to not working so good at the moment.

I suggest to reconsider the maintenance of x86 version, at least on fixing latest bugs and then updating components (apps, filters etc) in the future without adding new features.

At least until StaxRip x64 reaches the functionality of StaxRip x86

[stax76]

For madvr, Firefox and StaxRip this is the year of x64. I'll probably make some 32-Bit maintenance releases.

[huhn]

did your old version used the x265 build with 8 bpp?

[NikosD]

The x86 version had both executables (8bit and 10bit) for both encoders (x264 and x265) and you could select whatever you want for each encoder.

I don't know why Frank decided to include only one executable for each encoder and not both in x64 version.

[huhn]

i was asking about 16bpp or 8bpp. while 10 bit should always be 16bpp you could choice it for 8 bit and the 8bpp version is pretty bad.

[stax76]

The download size and hard drive space is huge, I added new plugins and might be able to restore old plugins because I found 64 bit versions, I've also added xvid encraw and DivX265, AviSynth+ is gonna be 18 MB, so altogether it's 70 MB now. The source is on github now, probably I should give up sourceforge completely, I don't know if github allows that much traffic, many people here use mediafire, mkvtoolnix uses fosshub, maybe BitTorrent could be a way.

What I'll much likely do is allow tools not used being deleted, I added xvid encraw only because it was requested at least once a week so still used by many people, if people request separate 8-Bit and 10-Bit frequently I have to put it back, the poll showed there are x264 10-Bit users, if I add this people might enable it not even knowing it has little to no hardware support (right?) so I would have to add a warning at least. It's not looking there are many people using x265 8-Bit, HEVC is all about 10-Bit, right?

[huhn]

What I'll much likely do is allow tools not used being deleted, I added xvid encraw only because it was requested at least once a week so still used by many people, if people request separate 8-Bit and 10-Bit frequently I have to put it back, the poll showed there are x264 10-Bit users, if I add this people might enable it not even knowing it has little to no hardware support (right?) so I would have to add a warning at least. It's not looking there are many people using x265 8-Bit, HEVC is all about 10-Bit, right?

yes there is liberally no h264 10 bit hardware support,

but nearly all hardware decoder can't decode 16 ref frames so do you have a warning for this too?
just add a (if you didn't already have) presets for devices like megui did. there are multiply settings you can't use for some hardware devices using x264 8 bit.

if someone is changing settings he has to deal with the result no need to hold there hands.

10 bit x264 is used quiet a lot.

some/most decoder can't decode 10 bit HEVC like lentoid or UHDcode. so there is a reason to use 8 bit HEVC but please use the 16 bpp version.

do you think about adding AMD VCE to your hardware decoder list? the people on the OBs forum liked it and i wouldn't be shocked if AMD VCE 2.0 is better than NVenc kampler and haswell.

[NikosD]

Do you know any tool in CLI form that supports VCE ?

[huhn]

Do you know any tool in CLI form that supports VCE ?

sadly no.

but OBS has a version with VCE support and it's open source and the used "encoder" there should be usable for things like staxrip.

using the SDK should be possible too.
http://developer.amd.com/community/blog/2014/02/19/introducing-video-coding-engine-vce/

[NikosD]

The developer of QSVEncC and NVEncC (rigaya) hasn't built a CLI tool for VCE but only an aviutil plugin - VCEnc.

[burfadel]

What about deinterlacing filters like YADIF, and IVTC processing?

[stax76]

@huhn

There is devices support applying some restrictions, I try to add at least some tooltips and help. I like adding new encoders even with GUI, my design makes this a very very easy task, I'm not really C++ programming (future maybe...) so no AMD support until there is a tool (which I didn't search hard for).

What about deinterlacing filters like YADIF, and IVTC processing?

There is a good chance most comes back in the next release.

[huhn]

@huhn

There is devices support applying some restrictions, I try to add at least some tooltips and help. I like adding new encoders even with GUI, my design makes this a very very easy task, I'm not really C++ programming (future maybe...) so no AMD support until there is a tool (which I didn't search hard for).

maybe useful for you maybe not: https://obsproject.com/forum/threads/obs-branch-with-amd-vce-support.13996/

[burfadel]

There is a good chance most comes back in the next release.

That's good, deinterlacing vital for encoding :).

[stax76]

There are various plugins but I don't know yet the quality of the port and the compatibility.

https://sites.google.com/site/avisynth64bitplugin/download
http://web.archive.org/web/20130922222259/http://yo4kazu.110mb.com
http://members.optusnet.com.au/squid_80
https://code.google.com/p/avisynth64/wiki/PluginLinks

[luigizaninoni]

Hello, I have been using Staxrip for some months, and so far I have been very pleased with the results.
My usual workflow is as follows:
- record movie from DVB-T with dvbviewer
- remove ads with Videoredo
- encode with Staxrip-32bit – avisynth qtgmc – x265 10bit slow - crf 19

The introduction of Staxrip 64-bit is very welcome (qtgmc is so slooooow … and x265 10bit does not help). However I am trying to have it work properly but I am totally stuck – I am not a total noob, but certainly I am not an expert either.

My difficulties:
- How can I install Avisynth+, given that the existing installer is very old and not updated to most recent version ?
- How do I implement Qtgmc ? As far as I can understand, I would need Mvtools, MaskTools v2, NNEDI3, RemoveGrain + Repair, SSE2Tools, NNEDI2, NNEDI, EEDI3, EEDI2, Tdeint. All 64-bit plugins. I do not use the other plugins. I have been able to find some of these plugins in 64-bit version, but where can I find all of them ?

[stax76]

I try to get a newer installer, Qtgmc and x64 might be a problem.

[Reel.Deel]

My difficulties:
- How can I install Avisynth+, given that the existing installer is very old and not updated to most recent version ?

I used the AviSynth+ r1576 installer (make sure you install 32 and 64-bit) and then I manually replaced the respective files using the updated build from here (https://cloud.pados.hu/index.php/s/0e0d5588307a7b0474742711731699b6?path=%2Fr1779-MT-release). 32-bit avisynth.dll and devil.dll go in the SysWOW64 folder, 64-bit goes in the System32 folder. Also replace the core plugins in the AviSynth autoload folder with the included plugins.


- How do I implement Qtgmc ? As far as I can understand, I would need Mvtools, MaskTools v2, NNEDI3, RemoveGrain + Repair, SSE2Tools, NNEDI2, NNEDI, EEDI3, EEDI2, Tdeint. All 64-bit plugins. I do not use the other plugins. I have been able to find some of these plugins in 64-bit version, but where can I find all of them ?
Really you don't need all these plugins for it to work, QTGMC() with all default settings only needs MVtools2, MaskTools2, RemoveGrain/Repair, and NNEDI3. Some of the other plugins like NNEDI, NNEDI2, EDDI2 can be considered deprecated. SSE2Tools is only used to process YUY2, it's closed source and the author is no longer around so we won't see a 64-bit version of that (this is probably a good thing, it was just an ugly hack anyways).

Anyways you can download the core plugins here:

MaskTools2 (https://github.com/tp7/masktools/releases)
MVTools2 (http://forum.doom9.org/showpost.php?p=1718402&postcount=1054)
RgTools (https://github.com/tp7/RgTools/releases) - includes RemoveGrain, Repair, and VerticalCleaner
NNEDI3 (http://forum.doom9.org/showthread.php?t=170083)

[luigizaninoni]

:thanks:

[luigizaninoni]

Ok, thanks to Reel.Deel, now Avisynth+ and Qtgmc "might" be in place.

However, I am still stuck with Staxrip 64-bit. When I try to open a source I get this error message:

Exception

Overflow di un'operazione aritmetica.

System.OverflowException: Overflow di un'operazione aritmetica.
in System.IntPtr.op_Explicit(IntPtr value)
in StaxRip.TaskDialog`1.AllocateAndMarshalButtons(List`1 structs) in C:\Daten\Projekte\GitHub\staxrip\UI\TaskDialog.vb:riga 379
in StaxRip.TaskDialog`1.MarshalDialogControlStructs() in C:\Daten\Projekte\GitHub\staxrip\UI\TaskDialog.vb:riga 361
in StaxRip.TaskDialog`1.Show() in C:\Daten\Projekte\GitHub\staxrip\UI\TaskDialog.vb:riga 302
in StaxRip.MainForm.OpenSourceFiles() in C:\Daten\Projekte\GitHub\staxrip\Forms\MainForm.vb:riga 4858
in StaxRip.MainForm.lTip_Click() in C:\Daten\Projekte\GitHub\staxrip\Forms\MainForm.vb:riga 5297
in StaxRip.MainForm._Lambda$__163(Object a0, EventArgs a1) in C:\Daten\Projekte\GitHub\staxrip\Forms\MainForm.vb:riga 0
in System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
in System.Windows.Forms.Control.WndProc(Message& m)
in System.Windows.Forms.Label.WndProc(Message& m)
in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[stax76]

Looks like a bad pointer size so 64-bit port bug number two, this kind of bug was to be expected, I'll upload a fix shortly.

[stax76]

The code works here, which OS are you using and what were you doing when it happens?

[luigizaninoni]

The code works here, which OS are you using and what were you doing when it happens?

Windows 8.1 64-bit. Main windows of staxrip, click on "source-single file" or right-click on "source-open"

[stax76]

It's the same line of code described here:

https://github.com/aybe/Windows-API-Code-Pack-1.1/issues/3

What I don't understand is why it's another type of exception, my code was casting to int while the code that is said to work uses intptr.ToInt64, maybe the integer size is different on your system, I don't get it, anyway, I upload a build in a few minutes which I hope will work.

[stax76]

alpha 1.3.0.1

http://1drv.ms/1DwnJsY

[luigizaninoni]

alpha 1.3.0.1

http://1drv.ms/1DwnJsY

now source opens, thanks

I'll try an encode with qtgmc and report back

[luigizaninoni]

alpha 1.3.0.1

http://1drv.ms/1DwnJsY

source opens now, thanks

I'll try an encode with qtgmc and report back

[luigizaninoni]

thanks, now no error while opening source.

However, tried to encode (with qtgmc); gives error message "AviFile open failed" (strange, because it's a .ts and it should open with directshowsource)

[luigizaninoni]

Exception

AVIFileOpen failed

System.Exception: AVIFileOpen failed
in StaxRip.AVIFile..ctor(String path) in C:\Daten\Projekte\GitHub\staxrip\General\AVIFile.vb:riga 66
in StaxRip.AviSynthDocument.Synchronize() in C:\Daten\Projekte\GitHub\staxrip\General\AviSynth.vb:riga 146
in StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean autoMode) in C:\Daten\Projekte\GitHub\staxrip\Forms\MainForm.vb:riga 1946

[stax76]

Is there a full log file you can upload to pastebin?

[luigizaninoni]

loaded crash.srip to dropbox:

https://dl.dropboxusercontent.com/u/2189315/Comuni%20a%20tutti%20i%20PC/crash.srip

[stax76]

Is there a log file?

*_StaxRip.log

Try to remove all plugins from the auto load folder, it could be a problem with your system or avisynth.

[luigizaninoni]

Here is the log:

https://dl.dropboxusercontent.com/u/2189315/Comuni%20a%20tutti%20i%20PC/13-25-00-Star%20Trek%20%20Primo%20contatto_Rai%204%20%28ita%29_StaxRip.log

[stax76]

LoadPlugin("C:\Users\admin\Desktop\Video\Staxrip 64bit\Tools\DGMPGDec\DGDecode.dll")
MPEG2Source("C:\Users\admin\Desktop\13-25-00-Star Trek Primo contatto_Rai 4 (ita) temp files\13-25-00-Star Trek Primo contatto_Rai 4 (ita).d2v")
QTGMC( Preset="Slow" ).SelectEven()
Crop(0, 0, -0, -0)

AviSynth Plugins: masktools2, mvtools2, nnedi3, RgTools

First try to not use QTGMC, if the problem persists then remove all plugins from the auto load folder and try again.

Try to load the avs file with MPC 64-Bit, problem is the script generally don't work I suspect.

[luigizaninoni]

I removed all plugins, and tried this simple avs:
LoadPlugin("C:\Users\admin\Desktop\Video\Staxrip 64bit\Tools\DGMPGDec\DGDecode.dll")
MPEG2Source("C:\Users\admin\Desktop\13-25-00-Star Trek Primo contatto_Rai 4 (ita) temp files\13-25-00-Star Trek Primo contatto_Rai 4 (ita).d2v")

It does not open in MPC-HC64. So probably I didn't install Avisynth+ correctly ? Or anyway there is a problem with avisinth+ ?

[stax76]

Try loading a avs file with mpc 64-bit containing just:

Version()

Reel.Deel described exactly how to install AviSynth+, try uninstalling AviSynth+ and just install the installer and nothing else.

[luigizaninoni]

at first version() avs did not load in mpc.

After uninstall and reinstall of avisynth+ it now works.

[luigizaninoni]

tried to encode a 2-minute video at default settings, gives again:
Overflow di un'operazione aritmetica.

I think I'll stick with Staxrip-32bit for the moment, it is a great software anyway

I'll try again 64bit when the setup procedure is more streamlined and mature

Thanks anyway for your kind help, Stax76

[stax76]

Maybe there is something special on your side, I've integrated 13 plugins meanwhile, dgdecode and autocrop are back, I'll integrate 4 more plugins and QTGMC, everything is working perfectly, I've not expected there are that few problems and few things missing, maybe 64-Bit AviSynth is more ready then many people think it is, great job from everybody building and porting.

[detmek]

Hi stax76. First, thanks for Codec Comparisson tool! Its fantastic! Second, is it postible for StaxRip x64 to use portable Avisynth or Avisynth+, like MeGUI does?

[stax76]

Hi, portable AviSynth isn't supported, would this have an advantage? StaxRip from now on requires AviSynth+ 64-Bit.

There are two users reporting an arithmetic overflow returned from IAvisynthClipInfo, both are on win 8.1, one has provided a log file, nothing special to see there, ffms2 failing to load a old mkv/avc movie, maybe only Win 7 works. First I need a AviSynth+ installer.

[stax76]

There is a ffms2 memory leak, workaround: Tools/Settings/Filter/default > LWLibavVideoSource

[detmek]

Right, Avisynth is not supported. But MeGUI uses Avisynth+ portable (or at least it shows that).
Here is MeGUI log:
[Warning] Log
-[Warning] Versions
--[Information] [4/26/2015 5:13:40 PM] MeGUI: 2534
--[Information] [4/26/2015 5:13:40 PM] Operating System: Windows 7 x64 SP1 (6.1.65536.7601)
--[Information] [4/26/2015 5:13:40 PM] .NET Framework: 4.0 (4.0.0.0)
--[Information] [4/26/2015 5:13:40 PM] .NET Framework: 4.5.x (4.5.51209)
--[Information] [4/26/2015 5:13:40 PM] AviSynth: 2.6.0.6 (31-03-2015) (inactive)
--[Information] [4/26/2015 5:13:40 PM] AviSynth+ portable: 2.6.0.5 (02-01-2014) (active)
--[Information] [4/26/2015 5:13:40 PM] AvisynthWrapper: (02-01-2009)
--[Warning] [4/26/2015 5:13:40 PM] Haali Matroska Splitter not installed properly.
--[Warning] [4/26/2015 5:13:40 PM] Therefore DSS2() and certain functions of FFVideoSource() and the HD Streams Extractor may also not work.
--[Warning] [4/26/2015 5:13:40 PM] Please download and install it from http://haali.su/mkv/
--[Information] [4/26/2015 5:13:40 PM] Haali DSS2: 2.0.0.10 (13-01-2013)
--[Information] [4/26/2015 5:13:40 PM] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
--[Information] [4/26/2015 5:13:40 PM] MediaInfo: 0.7.73.0 (09-04-2015)
--[Information] [4/26/2015 5:13:40 PM] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
--[Information] [4/26/2015 5:13:40 PM] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
--[Information] [4/26/2015 5:13:40 PM] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
--[Information] [4/26/2015 5:13:40 PM] 7z: 9.20 (18-11-2010)
-[Information] Update detection
--[Information] [4/26/2015 5:13:40 PM] Using cached update config and server: http://megui.tmebi.de/test/
--[Information] [4/26/2015 5:13:40 PM] No package requires an update
And inside avs folder (MeGUI tools) there is avisynth.dll which, when you click on properties, it shows Avisynth+ 2.6 as Product name.

This way you can ship any version of Avisynth+ you want with Avisynth+ compatible plugins and avoid forcing people to install Avisynth+ x64 if they need to use regular Avisynth or AvisynthMT for compatibility with some plugins or scripts.

[stax76]

I can only guess what AviSynth portable does, I suspect in involves feeding the encoder via pipe, this works very well and is the only way to use x265, even if there is no real benefit I favor encoders opening avs instead using piping.

[noee]

I used the AviSynth+ r1576 installer (make sure you install 32 and 64-bit) and then I manually replaced the respective files using the updated build from here (https://cloud.pados.hu/index.php/s/0e0d5588307a7b0474742711731699b6?path=%2Fr1779-MT-release). 32-bit avisynth.dll and devil.dll go in the SysWOW64 folder, 64-bit goes in the System32 folder. Also replace the core plugins in the AviSynth autoload folder with the included plugins.


Really you don't need all these plugins for it to work, QTGMC() with all default settings only needs MVtools2, MaskTools2, RemoveGrain/Repair, and NNEDI3. Some of the other plugins like NNEDI, NNEDI2, EDDI2 can be considered deprecated. SSE2Tools is only used to process YUY2, it's closed source and the author is no longer around so we won't see a 64-bit version of that (this is probably a good thing, it was just an ugly hack anyways).

Anyways you can download the core plugins here:

MaskTools2 (https://github.com/tp7/masktools/releases)
MVTools2 (http://forum.doom9.org/showpost.php?p=1718402&postcount=1054)
RgTools (https://github.com/tp7/RgTools/releases) - includes RemoveGrain, Repair, and VerticalCleaner
NNEDI3 (http://forum.doom9.org/showthread.php?t=170083)


How is this mvtools2 compiled? Fails on my old AthlonII. Illegal instruction when calling MAnalyze (QTGMC line 415).

[Reel.Deel]

How is this mvtools2 compiled? Fails on my old AthlonII. Illegal instruction when calling MAnalyze (QTGMC line 415).

I think it was compiled with Intel Parallel Studio XE 2015 Composer Edition for C++.

[stax76]

Here is a new build for those who had problems with onedrive:

http://www.mediafire.com/download/7a4i25ef1otedkx/StaxRip_1.3.0.2_alpha.7z

1.3.0.2 alpha


Added xvid_encraw 1.2.0.0
DivXH265 encoder added
AVSMeter stays open when finished
15 plugins are now integrated


I don't know yet what is causing the arithmetic overflow, it's not happening on my system.

[stax76]

This fixes the Win8/Win10 crashes:

https://www.dropbox.com/sh/xiyz10pghli8pvf/AAB3k0Dg-TRF-vh6srbITYDBa?dl=0

I had to install Windows 10 and Visual Studio using wmware player to track it down.

Unfortunately nnedi3 and TIVTC also crash on Win8/Win10, someone should make a bug report if these plugins are still maintained.

[stax76]

It's approaching beta. :)

1.3.0.3 alpha


Fixed Win8/Win10 crash
Added AviSynth+ v0.1.0 r1779 installer


http://www.mediafire.com/download/0u4028jkjwkk6ja/StaxRip_1.3.0.3_alpha.7z

[NikosD]

It would be helpful to update the first post too, especially whenever you do version updates.

[stax76]

Yes thanks

Hey everybody,

I've ported StaxRip to 64-Bit, I tried to maintain a 32-Bit version but it showed that it would be too much work to build, too much work to maintain, that it would have too many potential problems and too much complexity. Keeping 32-Bit would have meant spending half my time just for this and making only half the progress in the future. If necessary there will be a 32-Bit maintenance release.

The newest build can be found here:

http://www.mediafire.com/download/0u4028jkjwkk6ja/StaxRip_1.3.0.3_alpha.7z

The only known bug is a ffmsindex.exe (ffms2) memory leak, l-smash can be used instead like so:

Tools/Settings/Filter/default > LWLibavVideoSource

Don't forget to install AviSynth+ 64-Bit, it can be found in the Tools directory.

[luigizaninoni]

just wish to confirm that now avisynth+ installs totally fine on windows 8.1 and that encoding and basic plugins work too (tried only a few). Very good results in a very short time, Stax76 !

[stax76]

Luigi, thanks for testing and confirming.

[luigizaninoni]

Managed to get QTGMC to work.

avs file:
LoadPlugin("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\DGMPGDec\DGDecode.dll")
MPEG2Source("C:\Users\luigi.TZMS\Desktop\burosch1 temp files\burosch1.d2v")
QTGMC( Preset="Slow" , TR2=3 , EZDenoise=0.65).SelectEven()

Put MaskTools2, MVTools2, RgTools, NNEDI3 (as downloaded from Reel.deel post) into C:\Program Files (x86)\AviSynth+\plugins64+ folder

If you want EZdenoise, put in same folder also fft3dFilter.dll, and put libfftw3f-3.dll into c:\windows\system32 folder (both downloaded from here: https://code.google.com/p/avisynth64/wiki/PluginLinks )

Well I can't explain how it works, given that Nnedi3 plugin should not work in windows 8.1; however the nnedi3.dll in avisynth+ folder is different from the one in Staxrip64\Tools\Plugins\nnedi3 so who knows ....

Have not tested speed yet; tonight I'm going to do speed comparison vs. staxrip32 and report back

[dejong12]

I get this error when trying to encode with NVEnc x264 and not selecting crop:

Error Encoding using NVEncC
Encoding using NVEncC failed with exit code 1
Invalid crop value.: 0x0, Crop [0,0,0,0]

StaxRip.ErrorAbortException: Encoding using NVEncC failed with exit code 1

Invalid crop value.: 0x0, Crop [0,0,0,0]
bij StaxRip.Proc.Start() in C:\Daten\Projekte\GitHub\staxrip\General\Proc.vb:regel 226
bij StaxRip.NvidiaEncoder.Encode(String args) in C:\Daten\Projekte\GitHub\staxrip\General\VideoEncoder.vb:regel 892
bij StaxRip.NvidiaEncoder.Encode() in C:\Daten\Projekte\GitHub\staxrip\General\VideoEncoder.vb:regel 882
bij StaxRip.MainForm.Encode() in C:\Daten\Projekte\GitHub\staxrip\Forms\MainForm.vb:regel 2231
bij StaxRip.MainForm.RunJobRecursive() in C:\Daten\Projekte\GitHub\staxrip\Forms\MainForm.vb:regel 3493

[luigizaninoni]

Stax76, just mailed to your address the nnedi3.dll I put into avisynth+ plugins64+ folder. The other nnedi3.dll is the one contained in your installer. The two files are different.

[stax76]

@dejong12

The hardware encoders with GUI don't work at the moment because the 64-Bit encoders don't support avs input, I'm waiting for a answer or update from the author. There is a CLI encoder included that can be used meanwhile.

@luigizaninoni

Thanks, I'll try it when my encode finishes (also using QTGMC).

[luigizaninoni]

made some tests.

First of all there is a problem with Crop filter: autocrop definitely does not work. Error message:

Crop: Destination width is 0 or less.
(E:\Tolta pubblicità\prova temp files\prova.avs, line 3)

Second, I made a SD and HD test. The HD looks fine, much faster and same quality as Staxrip32

The SD test however is puzzling: speed is actually higher in Stax32 (not multithreaded) than Stax64.

I definitely need to perform some more tests.

[stax76]

First of all there is a problem with Crop filter: autocrop definitely does not work.

It works here on Win10, I just tried, maybe specific to a particular source?

[luigizaninoni]

no, autocrop filter did not work on any file I tried. They were all .ts though

[stax76]

avc ts by default should be first muxed to mkv before it's opened, for this StaxRip should have ask you to install haali splitter.

mpeg-2 ts is handled by DGMPGDec (DGIndex/DGDecode) by default.

[kalehrl]

Added xvid_encraw 1.2.0.0
Why not the latest 1.3.3?

[stax76]

Why not the latest 1.3.3?

I couldn't find a x64 build.

[stax76]

@kalehrl

Next build has XviD 1.3.3 and a additional XviD 2 pass profile.


"%app:xvid_encraw%" -smoother 0 -max_key_interval 250 -nopacked -vhqmode 4 -qpel -lumimasking -notrellis -max_bframes 1 -bvhq -bquant_ratio 162 -bquant_offset 0 -threads 1 -i "%avs_file%" -pass1 "%working_dir%%target_name%.stats" -bitrate %video_bitrate% -par %target_sar% -turbo
"%app:xvid_encraw%" -smoother 0 -max_key_interval 250 -nopacked -vhqmode 4 -qpel -lumimasking -notrellis -max_bframes 1 -bvhq -bquant_ratio 162 -bquant_offset 0 -threads 1 -i "%avs_file%" -pass2 "%working_dir%%target_name%.stats" -bitrate %video_bitrate% -par %target_sar% -avi "%encoder_out_file%"

[Patman]

Thats great Stax. I've found xvid_encraw 1.3.3 x64 too. And i think the pipe option caused the error. Because of the search, it was a short night :-D

[stax76]

The nnedi3 problem happens only in vmware so QTGMC works on Win8 and Win10.

Next StaxRip release will have:

ffms2 is fixed
NVEncC and QSEncC are reverted to use piping with ffmpeg
StaxRip 64-Bit will use a different settings then StaxRip 32-Bit, currently the settings are shared which is problematic. I guess it's possible to use AviSynth 2.6 32-Bit side by side with AviSynth+ 64-Bit

Did I miss any problem or is everything solved then? The port would be complete then and could be released as beta.

[luigizaninoni]

Autocrop of .ts still not solved (autocrop of .mp4 works fine)
https://dl.dropboxusercontent.com/u/2189315/Comuni%20a%20tutti%20i%20PC/Incensurato%20cercasi_StaxRip.log

Crop: Destination height is 0 or less.
(C:\Users\luigi.TZMS\Desktop\Incensurato cercasi temp files\Incensurato cercasi.avs, line 4)

[stax76]

Can you upload this source, I probably can't do something but want to keep the file in case I start AviSynth programming, unfortunately AutoCrop as far as I know hasn't a maintainer (not sure about it).

[luigizaninoni]

uploaded 1 minute clip:
https://dl.dropboxusercontent.com/u/2189315/Comuni%20a%20tutti%20i%20PC/Incensurato%20cercasi.ts

Stax64 is still usable, you can always find the correct crop with some other software, and then manually edit the avs script

[stax76]

it's DGDecode failing to decode in Win8 and Win10, Win7 is fine. Take a look in the preview, everything is green! Use this workaround:

in the settings on the demux tab make this changes:

add projectx (use add button)
move projectx above DGIndex (use up button)
remove m2v extension from DGIndex (use edit button)

now you are good, open a source, sit down a minute and try to understand how all this works, study the log file

you can always find the correct crop with some other software, and then manually edit the avs script

is there any software with a more comfortable and powerful manual cropping dialog then StaxRip? I doubt so! Press F1 in the crop dialog, always use mousewheel together with control and shift key.

[stax76]

What I don't get is why is the preview of the script in StaxRip and MPC all green and AutoCrop don't work but still x264 encodes it all fine.

[luigizaninoni]

now ts autocrop works fine, thanks a lot!

[stax76]

this handles only mpeg2 however, for avc you should enable dsmux

[luigizaninoni]

yes, thanks very much for pointing out; now encoding AVC ts as well, gave no error message so I think it works (encoding not finished yet though)

[NikosD]

When you release the next version, add to the first post what StaxRip x64 supports, all the basic features and what features are not supported compared to x86 version.

Also the known bugs of StaxRip x64 and the differences of implementation for the same features supported by x86 would be useful too.

Can we work and compare the two versions together at the same time on the same system ?

[stax76]

When you release the next version, add to the first post what StaxRip x64 supports, all the basic features and what features are not supported compared to x86 version.

Also the known bugs of StaxRip x64 and the differences of implementation for the same features supported by x86 would be useful too.


I'll improve the first post, yes.

Can we work and compare the two versions together at the same time on the same system ?


Yes, when you first start the next release you'll see this:

http://thumbnails107.imagebam.com/40679/fb69a4406789096.jpg (http://www.imagebam.com/image/fb69a4406789096)

[burfadel]

Stax, in case you miss it:
Avisynth+ r1825 http://forum.doom9.org/showthread.php?p=1719768#post1719768

[stax76]

:thanks:

http://www.mediafire.com/download/hvnjb8wy54ys7gl/AviSynth+_v0.1.0_r1825-MT.exe

Should I include all plugins needed for QTGMC? nnedi3 alone is 13 MB.

[luigizaninoni]

imho a large download is no problem at all. I mean, we are not talking of gigabytes ...

[NikosD]

The new INDE 2015 Update 2 includes new MSDK as well, with API v1.15 documentation, mainly about HEVC encoding of Skylake.

So, it's official:
Skylake supports HW H.265 encoding.

Release notes:
https://software.intel.com/sites/default/files/managed/48/ce/mediasdk_release_notes.pdf

[luigizaninoni]

Finally got Avisynth+ multithreaded working properly

I am impressed with the speed improvement:

My usual encoding (mpeg2 .ts --> staxrip64 --> qtgmc x265-10bit) single threaded speed was about 7fps
With multithreaded about 18 fps

CPU usage went up from about 35% to nearly 100%

Really didn't expect such an improvement

[stax76]

Hey everybody, here is a new release I was working on:

1.3.1.0 beta


Added QTGMC, masktools2, mvtools2, RGTools and nnedi3
Added new AviSynth editor
Added new macros: fps, fpsnum, fpsden, temp_file is now everywhere used where previously %working_dir%%target_name% was used
Added DGDecIM integration
Added 'Hardware Encoder' resize filter to AviSynth filter profiles which does nothing with AviSynth but enables the Quick Sync resizer
Added option to audio context menu to play audio together with the AviSynth script
Added possibility to use different settings directories for StaxRip 32-Bit and StaxRip 64-Bit
Added x265 options --qpstep and --qg-size
Updated ffms2 which fixes a critical memory leak
Updated AVSMeter to version 2.0.0
Updated AviSynth+ to version v1825
Updated XviD to v1.3.3
Updated x265 to v1.6+298
Updated hardware encoders supporting 64-Bit avs reading
Enabled dsmux to handle any kind of TS
Improved frame rate detection by using fpsnum and fpsden parameters on FFVideoSource and LWLibavVideoSource instead of AssumeFPS which did not work with some interlaced sources
Forced subtitles from DVDs are now added automatically but only if the forced subtitle is the language of the current locale and maximum one forced subtitle is added and the subtitle is added with a forced flag


http://www.mediafire.com/download/daxdakah0n71hpu/StaxRip_1.3.1.0_beta.7z

It handles all TS with DSMux which is a experiment, before DGDecode was used but 64-Bit DGDecode don't work on Win8/Win10, this also means VOB files cannot be opened, it's anyway better to rip with MakeMKV and open mkv. There are probably other methods to process VOB, maybe it's time to retire DGMPGDec altogether.

[NikosD]

I think I'm going to try that version probably against x86.

But why did you change the working directory ?

It was a good way to avoid writing to SSD (C: ), I have all my files to D:\ (HDD)

I didn't see a new version of QSVencC to rigaya's site.
Did he add AVS support to x64 versions ?

[stax76]

But why did you change the working directory ?

You mean settings directory? It is necessary that StaxRip64 uses a different settings directory then StaxRip32 because the settings are not compatible. In case you mean the macro change, it resolves to the same directory, the new %temp_file% resolves to exactly the same as %working_dir%%target_name% which was used in many scripts and command lines, it's much shorter and simpler now.

Did he add AVS support to x64 versions ?

I wrongly assumed both don't do x64 but in reality only nvencc was lacking it.

[burfadel]

@stax76
Thanks for the new build!

HOWEVER :)
How come you are using qaac 32-bit in Staxrip64, when there is a 64-bit available? Without thinking I installed the 64-bit required application support, and wondered why it was still saying it wasn't installed (as it was expecting the 32-bit version).

The archive containing the 32-bit and 64-bit versions is here:
https://github.com/nu774/qaac/releases/download/v2.47/qaac_2.47.zip

The latest 64-bit application support is just as easy to get as the 32-bit :). The filenames have changed though, they're all the same except with 64 on the end (such that it is qaac64.exe).

Thanks!

[stax76]

@stax76
Thanks for the new build!

HOWEVER :)
How come you are using qaac 32-bit in Staxrip64, when there is a 64-bit available? Without thinking I installed the 64-bit required application support, and wondered why it was still saying it wasn't installed (as it was expecting the 32-bit version).

The archive containing the 32-bit and 64-bit versions is here:
https://github.com/nu774/qaac/releases/download/v2.47/qaac_2.47.zip

The latest 64-bit application support is just as easy to get as the 32-bit :). The filenames have changed though, they're all the same except with 64 on the end (such that it is qaac64.exe).

Thanks!

I believe I was looking for 64-Bit Apple Application Support and only found people writing that it's 32-Bit only, it would be helpful to get some info as private message, I can release a pre-release fixing this then.

[burfadel]

I believe I was looking for 64-Bit Apple Application Support and only found people writing that it's 32-Bit only, it would be helpful to get some info as private message, I can release a pre-release fixing this then.

There is a separate 64-bit installer to the 32-bit installer. The people saying it is 32-bit only are, how can I put this? looking in the wrong place?

I'll PM you the info.

[Patman]

Hi Stax,

thanks for the new release. I saw that mkvtoolnix is 32-bit and not 64-bit. I changed to 64-bit and everything works well so long. L-Smash was updated to version 785

L-Smash Works Download (https://www.dropbox.com/sh/3i81ttxf028m1eh/AAABkQn4Y5w1k-toVhYLasmwa?dl=0)

[burfadel]

Hi Stax,

thanks for the new release. I saw that mkvtoolnix is 32-bit and not 64-bit. I changed to 64-bit and everything works well so long. L-Smash was updated to version 785

L-Smash Works Download (https://www.dropbox.com/sh/3i81ttxf028m1eh/AAABkQn4Y5w1k-toVhYLasmwa?dl=0)

Yeah, for the official 64-bit mkvtoolnix, you have to scroll a little further down the page for mkvtoolnix-amd64-7.8.0.7z
https://www.bunkus.org/videotools/mkvtoolnix/win32/

the pre folder contains newer beta versions.

Mkvtoolnix can just be directly replaced, the filenames and commands etc are the same. I was actually using the 64-bit version (along with the 64-bit version of ffmpeg) with the 32-bit Staxrip (it allowed running the 64-bit application from it).

[burfadel]

There is a separate 64-bit installer to the 32-bit installer. The people saying it is 32-bit only are, how can I put this? looking in the wrong place?

I'll PM you the info.

PM Sent :). Hope it made sense!

[Lupissimo]

Just tested this new version. There is still the problem, that when one uses "select even" to change a 50fps ts.file to 25fps and after that edit the movie with cutting, the audio files are still "on 50fps" and therefor the output is only half of the length.

[stax76]

There is a separate 64-bit installer to the 32-bit installer. The people saying it is 32-bit only are, how can I put this? looking in the wrong place?

I'll PM you the info.

Thanks for the links, I made all changes including description for qaac in the applications dialog:

qaac is a command line AAC encoder frontend based on the Apple AAC encoder. qaac requires libflac which StaxRip includes and it requires AppleApplicationSupport64.msi which can be extracted from the 64-Bit iTunes installer using the context menu within the 7zip file manager.

There is however a problem with qaac 64-Bit, the command shell window pops up and StaxRip don't receive any output, I don't think I can do anything here other then report it to the author which I already did, waiting for a reply now.

thanks for the new release. I saw that mkvtoolnix is 32-bit and not 64-bit. I changed to 64-bit and everything works well so long. L-Smash was updated to version 785

L-Smash Works Download

Good to know it works, when there is a new mkvtoolnix release I'll use the 64-Bit version.

I'll update l-smash-works, thanks for the hint.

Mkvtoolnix can just be directly replaced, the filenames and commands etc are the same. I was actually using the 64-bit version (along with the 64-bit version of ffmpeg) with the 32-bit Staxrip (it allowed running the 64-bit application from it).

Using the same filenames is IMO the best approach, 32-Bit StaxRip using 64-Bit ffmpeg is a bad idea, look at one of the current defaults:

"%app:ffmpeg%" -i "%avs_file%" -f yuv4mpegpipe -pix_fmt yuv420p - | "%app:NVEncC%" --sar %target_sar% --codec h265 --y4m --cqp 36 --input - --output "%encoder_out_file%"

Most people will use the NVEncC GUI, the nice thing about this profile is it teaches people that piping is possible and simple, ffmpeg interfaces with AviSynth here (loading the AviSynth library via COM+), 64-Bit applications can only load 64-Bit libraries (at least without black magic).

Just tested this new version. There is still the problem, that when one uses "select even" to change a 50fps ts.file to 25fps and after that edit the movie with cutting, the audio files are still "on 50fps" and therefor the output is only half of the length.

I think the problem is people often forget to change the frame rate before cutting, there is a simple solution, just change the frame rate after the trim functions and not before! If you have real 50 fps and not just duplicated frames it's no problem to encode it with 50 fps, it doubles the encoding time but file size goes only up like 10%, you get much smoother motion for this 10%.

http://oi62.tinypic.com/2db1378.jpg

[burfadel]

Thanks for the links, I made all changes including description for qaac in the applications dialog:

There is however a problem with qaac 64-Bit, the command shell window pops up and StaxRip don't receive any output, I don't think I can do anything here other then report it to the author which I already did, waiting for a reply now.

Hope it isn't too much of an issue to resolve!

Using the same filenames is IMO the best approach, 32-Bit StaxRip using 64-Bit ffmpeg is a bad, look at one of the current defaults:

"%app:ffmpeg%" -i "%avs_file%" -f yuv4mpegpipe -pix_fmt yuv420p - | "%app:NVEncC%" --sar %target_sar% --codec h265 --y4m --cqp 36 --input - --output "%encoder_out_file%"

Most people will use the NVEncC GUI, the nice thing about this profile is it teaches people that piping is possible and simple, ffmpeg interfaces with AviSynth here (loading the AviSynth library via COM+), 64-Bit applications can only load 64-Bit libraries (at least without black magic).

Ah okay! I didn't think of that, I don't use NVEnc, I mainly used ffmpeg for forced audio decoding. I found decoding to .wav first was more reliable for some sources than encoding the audio directly from the source file. For practicality, I just had it enabled by default :).

[stax76]

Hope it isn't too much of an issue to resolve!

I hope it's not but this one could be difficult.

Ah okay! I didn't think of that, I don't use NVEnc, I mainly used ffmpeg for forced audio decoding. I found decoding to .wav first was more reliable for some sources than encoding the audio directly from the source file. For practicality, I just had it enabled by default

Another location where ffmpeg interfaces with AviSynth is the cut feature because for cutting mkvmerge needs a video file so StaxRip creates a 16x16 pixel AVI file with AviSynth and ffmpeg, decoding with ffmpeg isn't necessary in my experience but should be fine doing and has the advantage of most accurate cut points. I have to test if the new FLAC automatic gets in the way here.

[Patman]

I've tested xvid_encraw a bit with quality mode and 2-pass mode. The app worked as it should. In my opinion it's very easy to customize the settings. I made some changes for better quality.

:thanks:

[luigizaninoni]

I spoke too soon about the benefits of multithreaded Avisynth+

The speed benefits are there, but it is hardly stable. With Prefetch=3 or above, it invariably crashes in a few minutes. With prefetch=2 it is usually stable, however last night I launched a long encode and found that after a couple of hours it had crashed.

Maybe I am doing something wrong, or avisynth+ MT is not mature yet, or am using the wrong MT_MODE for some filter.

Anyhow, I am back to Staxrip with avisynth+ single-threaded, doing two encodes at the same time to fill CPU. Rock solid.

[burfadel]

I hope it's not but this one could be difficult.

I am trying out the beta you posted for this, it works well so far! The issue with QAAC64 is of minor annoyance only (having that command window pop up). On the other hand, it starts encoding the video while the audio is still encoding, so you have accidental mutlithreading there!

So there's no way of just outputting just the title bar information, and hiding the window?

[thomy22]

I test the new Version thanks for that.

But why the Files are so big? I have the same options and the File on the Old version are 300-350 MB (for 23min DVD File on X264) now i have 750 MB.

on the Old Version i have this Filters here centrodiperditadipeso.info (http://www.centrodiperditadipeso.info)

FieldDeinterlace
Crop Boarders
DeGrainMedian

now i have the standart Filters:

TDeint
Crop
Remove Grain

Are the Filters not work the same like the Old one or why the Files are so big now?

All other Settings are the Same CRF 19 and B-Frames and R-Frames 16 on Present Slower Tune Film

[burfadel]

I notice that even though tfm is listed in the filter menu, the plugin isn't included. I believe tdecimate is also in the same package as tfm, so there should be an option in the filter menu for inverse telecining and decimation (which can be done with these two filters). Without inverse telecining and decimation, people will be doing a lot of bad encodes of telecined material!

[burfadel]

@Stax
I found out something 'important' regarding the QAAC issue, I'll send a PM :)

[burfadel]

@Stax
(from the private PM, glad the qaac issue was super simple to fix!)

I came across the flash3kyuu deband filter, and am extremely impressed with the results on a poor quality video I had. The compression is good too, I used dither_algo=2 as suggested (it's better for standard bitrates, algo 3 is better for high bitrate outputs).

Anyways, the doom9 page is here:
http://forum.doom9.org/showthread.php?t=161411

Both x64 and x86 versions are available. Help file is inside.

Now, I've come across a more updated version of it, still from the same sources as in the linked doom9 post, just that post hasn't been updated!

Topic here:
https://www.nmm-hd.org/newbbs/viewtopic.php?f=7&t=239

The version I used was the 2.0pre+b98d6bc x86/x64, inside which has the x64 and x86 dll's. It's up to date too! 2015-05-02, so only 2 days old.

If anyone is wondering, I see the removing the banding and other issues present in poor quality videos as important. Some say it's pointless because you may introduce banding with encoding anyway, but that is rather an old thought on the manner. If there is banding present in the source, when you encode you are going to encode the banding as well! If you have a debanded source, with a very mild light dither, modern encoders (especially 10-bit versions of x265 etc) will produce markedly better file outputs.

EDIT: Done a few more encodes, not only do I get a better quality output, but the output file size is actually smaller! I guess it makes sense since it's not using bits encoding the banding artifacts. I think it's well worth it going from 8-bit sources to 10-bit x265. It's also fast :), especially the 02 Msy 2015 build. This is using dither_algo=2.

[luigizaninoni]

I made further findings on Avisynth+ MT issues.

I found that problems arise (encode crashes) ONLY when Qtgmc AND SelectEven() are both enabled.

So:
Script with only Qtgmc --> MT works fine, even with Prefetch(4)
Script with only SelectEven() --> MT works fine
Script with Qtgmc AND SelectEven() --> encode crashes

What's going on ? I have no clue. Is this a problem with Avisynth+ or with Staxrip ?

[Reel.Deel]

I made further findings on Avisynth+ MT issues.

I found that problems arise (encode crashes) ONLY when Qtgmc AND SelectEven() are both enabled.

So:
Script with only Qtgmc --> MT works fine, even with Prefetch(4)
Script with only SelectEven() --> MT works fine
Script with Qtgmc AND SelectEven() --> encode crashes

What's going on ? I have no clue. Is this a problem with Avisynth+ or with Staxrip ?

This sounds like an AviSynth+ problem. Have you tried SelectOdd instead? Also you can try SelectEvery (http://avisynth.nl/index.php/Select) as an alternative? If that fails how about QTGMC(FPSDivisor=2) (http://avisynth.nl/index.php/QTGMC#Shutter_Speed_Motion_Blur_.2F_Frame_Rate)?
QTGMC()
SelectEvery(2, 0) # identical to SelectEven()
#SelectEvery(2, 1) # identical to SelectOdd()

[luigizaninoni]

Thanks for the suggestion.

However, SelectOdd, SelectEvery and FpsDivisor all crash after a few hundred frames, just like SelectEven

[stax76]

@luigizaninoni

There is a similar report in the AviSynth+ thread, please post a full script, I want to test it too.

@burfadel

Thanks for the plugin suggestion and the help with qaac, I can add many more plugins, no problem. Regarding TDecimate, there is a crash in Win8/Win10 it seems so I removed the plugin and forgot to remove the filter. Some plugins have some CPU related parameters I need to try, overall there were many issues on Win8/Win10 not happening on Win7 so I decided to migrate to Win10 preview as main OS to investigate all problems.

@thomy22

if the quality looks good then filters cannot make such a big difference in file size, it's most likely related to source complexity and crf.

@Patman

Thanks for the tip about the new DLL.

[burfadel]

I just tried the StaxRip_2015.05.04_20-32 beta, and it errors as a result of AssumeFPS(%fps%) on existing projects. Even completed projects it says invalid argument because of this.

Just noticed that I reclicked the source filter I was using, saved the template, and recreated the projects that were in the queue, and they are encoding fine now. I guess assumefps(%fps) was a change between the last beta and this one :).

[stax76]

I've removed all those macros because they are not needed any longer, instead of always using the frame rate from MediaInfo with macros I add AssumeFPS dynamically now only if correction is needed, the correction logic is following:

if frame rate from AviSynth is approximately 2 times more then frame rate from MediaInfo then StaxRip adds SelectEven().AssumeFPS(fpsFromMediaInfo)

this corrects a bug where ffms2/ffmpeg duplicates interlaced frames

the second correction fixes wrong PAL frame rates, NTSC I leave now which might improve or worsen things, I don't know too much about NTSC.

[luigizaninoni]

Here is the script:
Import("C:\Users\admin\Desktop\Video\Stax beta\Tools\Plugins\QTGMC\QTGMC.avsi")
LoadPlugin("C:\Users\admin\Desktop\Video\Stax beta\Tools\Plugins\masktools2\masktools2.dll")
LoadPlugin("C:\Users\admin\Desktop\Video\Stax beta\Tools\Plugins\mvtools2\mvtools2.dll")
LoadPlugin("C:\Users\admin\Desktop\Video\Stax beta\Tools\Plugins\nnedi3\nnedi3.dll")
LoadPlugin("C:\Users\admin\Desktop\Video\Stax beta\Tools\Plugins\RgTools\RgTools.dll")
LoadPlugin("C:\Users\admin\Desktop\Video\Stax beta\Tools\Plugins\ffms2\ffms2.dll")
SetFilterMTMode("DEFAULT_MT_MODE",2)
SetFilterMTMode("FFVideoSource",3)


FFVideoSource("C:\Users\admin\Desktop\Interceptor (1979) temp files\Interceptor (1979).m2v", cachefile = "C:\Users\admin\Desktop\Interceptor (1979) temp files\Interceptor (1979).ffindex", fpsnum = 25, fpsden = 1)
QTGMC(Preset="Slow")
SelectEven()
Crop(2, 70, -2, -70)
Prefetch(4)

[stax76]

@luigizaninoni

I might have found something, putting SelectEven and Crop after Prefetch!

edit:

too bad, it's also freezing. :(

[NikosD]

this corrects a bug where ffms2/ffmpeg duplicates interlaced frames



The new method of 1.3.1.1 works fine with interlaced H.264 files and ffms2, just like the previous 1.3.1.0, but the new method is a lot faster I think.

[luigizaninoni]

Where is the new beta? I can't find it

[stax76]

there is a dropbox folder where I often upload bug fixes, it's here:

https://www.dropbox.com/sh/xiyz10pghli8pvf/AAB3k0Dg-TRF-vh6srbITYDBa?dl=0

[luigizaninoni]

there is a dropbox folder where I often upload bug fixes, it's here:

https://www.dropbox.com/sh/xiyz10pghli8pvf/AAB3k0Dg-TRF-vh6srbITYDBa?dl=0

:thanks:

[luigizaninoni]

but ... with 1.3.11 now Avisynth+ MT works ! Great job, Stax !

[stax76]

I couldn't get it working with prefetch as last statement but putting SelectEven after prefetch I was mostly successful, I'm still experimenting with filter order and have yet to encode a full movie to prove that it can work.

[luigizaninoni]

I'll try an encode of a full movie, too. P.S. Beta of 05.05 says "AVSmeter not found"

[stax76]

AVSMeter x64 has the original filename AVSMeter64.exe, new StaxRip builds use original names, if you don't want the newest built you can just rename the old.

[burfadel]

Stax, avsmeter has been updated to 2.0.1, the version with Staxrip64 is 2.0.0.

2.0.1 was just released yesterday (well today for most of you), 05 May 2015.

As from the Doom9 thread, versions are here:
https://www.sendspace.com/folder/4vem0i

[stax76]

Locally I have it already updated. :)

[burfadel]

QAAC 2.48 out as well :)

[NikosD]

Rigaya kept his promise he gave me and he started experimenting with HW decoding using QSV besides HW encoding.

He published some benchmark numbers with fully HW accelerated transcoding pipeline which give a big performance boost to least powerful CPUs and a smaller boost for CPUs like 4770K.

One important thing is the extremely low CPU usage in fully HW accelerated scenario in all cases.

After his tests, I believe the testing version will go public.

[AMED]

I seem to get a CAVIStreamSynth: System Exception - Access Violation error or AVISynth returned empty image data message whenever I try and preview the script below
LoadPlugin("D:\StaxRip\Tools\Plugins\mvtools2\mvtools2.dll")
LoadPlugin("D:\StaxRip\Tools\Plugins\ffms2\ffms2.dll")
# SetFilterMTMode("DEFAULT_MT_MODE", 2)
# SetFilterMTMode("FFVideoSource", 3)
FFVideoSource("I:\Star Trek (2009) (1)-003.mkv", cachefile = "I:\Star Trek (2009) (1)-003 temp files\Star Trek (2009) (1)-003.ffindex")
BicubicResize(1280, 720, 0, 0.5)
super = MSuper(pel=2)
backward_vec2 = MAnalyse(super, isb = true, delta = 2, overlap=4)
backward_vec1 = MAnalyse(super, isb = true, delta = 1, overlap=4)
forward_vec1 = MAnalyse(super, isb = false, delta = 1, overlap=4)
forward_vec2 = MAnalyse(super, isb = false, delta = 2, overlap=4)
MDegrain2(super, backward_vec1,forward_vec1,backward_vec2,forward_vec2,thSAD=400)

ConvertToRGB(matrix="Rec709")

When i run the script though AVSmeter there is no problems

Staxrip v1.3.1.1

[stax76]

QAAC 2.48 out as well

:thanks:

@AMED

I think some scripts fail only if a application requests random frames, if you would open the script with VirtualDub x64 I would guess you would see the same AviSynth error, only a AviSynth dev could help here.

You could try using LWLibavVideoSource instead of FFVideoSource, by default StaxRip uses FFVideoSource for MKV but the default can be changed in the settings on the filters tab.

[AMED]

LoadPlugin("D:\StaxRip\Tools\Plugins\mvtools2\mvtools2.dll")
LoadPlugin("D:\StaxRip\Tools\Plugins\L-SMASH-Works\LSMASHSource.dll")
# SetFilterMTMode("DEFAULT_MT_MODE", 2)
# SetFilterMTMode("LWLibavVideoSource", 3)
LWLibavVideoSource("I:\Star Trek (2009) (1)-003.mkv")
super = MSuper(pel=2)
backward_vec2 = MAnalyse(super, isb = true, delta = 2, overlap=4)
backward_vec1 = MAnalyse(super, isb = true, delta = 1, overlap=4)
forward_vec1 = MAnalyse(super, isb = false, delta = 1, overlap=4)
forward_vec2 = MAnalyse(super, isb = false, delta = 2, overlap=4)
MDegrain2(super, backward_vec1,forward_vec1,backward_vec2,forward_vec2,thSAD=400)
Still gives me the same access violation error (different memory address though) with the preview, AVSMeter still processes it ok.

I opened the above script in VDubx64 and it displays the video fine. if i seek to random places on the video it's still fine.

Just checked with FFMSVideoSource and that script also loads correctly in vDubx64.

[stax76]

Does this script utilize nnedi3? There are some unresolved x64 related issues still being investigated, I'm working on it. :)

[NikosD]

New QSVEncC will be implemented keeping frames in GPU, like DXVA native mode, so it could reach HandBrake's performance.

It will accelerate in HW both MPEG2 and H.264 video formats for decoding.

Rigaya told me that he was trying to accelerate HEVC in HW using MSDK but with no success (probably due to MSDK or driver's error) but he will add that too, when it will be more mature.

There will be no SW fall - back, so for every other video format, we will keep on using the other source filters of StaxRip.

[AMED]

Does this script utilize nnedi3? There are some unresolved x64 related issues still being investigated, I'm working on it. :)just using FFMS2VideoSource or LWLibavVideoSource and MVtools2. the only plugins in the AVISynth+ plugin folder are the default plugins from the install.

[stax76]

15 years ago StaxRip was the first .NET application on doom9 and it was a bit difficult, now StaxRip is early adopting AviSynth x64 with .NET and it's again I bit difficult. I made a sample application with MeGUIs interop layer which is completely different then my layer and the problem persists and it's not only managed applications producing the problem, you should also see it with MPC, it's more likely the problem is native code and not managed (.NET) code.

[Groucho2004]

it's more likely the problem is native code and not managed (.NET) code.
No idea what that means. Could you elaborate?

[videoh]

http://en.wikipedia.org/wiki/Managed_code

Native code is the Avisynth DLL, the plugin DLLs, and the avifile DLL. The rest is the managed application that uses .NET (VB .NET?). Apparently stax76 needs some kind of "interop layer" (is that staxrip76's avifile interface stuff?) to access the native code from his application code. But VB .NET can make Avisynth DLL calls directly without any such layer.

It seems to me that stax76's insistence on the avifile interface is misguided, as Groucho2004 pointed out. He should invoke the Avisynth DLL directly. There are a lot of code examples for it. Realistically, nobody is going to debug avifile.dll, so unless staxrip76 wants to do that, he should transition to direct access of the Avisynth DLL. That has little to do with managed versus native code, because he already accesses the avifile.dll natively. staxrip says he ported MeGui's "interop layer", by which I suppose he means the Avisynth interface, but he hasn't shown us this code.

staxrip76 has not yet identified the faulting module. On the other thread I suggested ways to find out. Hopefully, he is interested in that.

[Groucho2004]

The part I don't understand is "it's more likely the problem is native code". Which native code exactly? Blaming the plugins, which work properly with other client programs, is not going to help track down the problem.

[videoh]

It could still be a plugin problem, though unlikely. Blaming other code can be effective if you can motivate the developer to look into it, so I don't fault that (personally, I'm not motivated to debug VB .NET + avifile + "reflection hack"), unless it is used as an excuse to not do what you can to check things in your own code. What I fault is the apparent total lack of any debugging skills whatsoever, and the inability to make germane responses to helpful questions and suggestions.

Most likely, avifile is not compatible with the modern versions of Avisynth. Solution: get rid of avifile. But if the developer cannot run a debugger, can he re-engineer for direct Avisynth access?

[stax76]

@videoh

I don't know your programming background but from all your post it's clear you know absolutely NOTHING about dotnet so it's pretty pointless to argue over it.

[videoh]

That's disappointing that you consider my opinions not worth hearing. Nevertheless, good luck with your {VB .NET + avifile + "reflection hack"} project. Despite any differing perspectives we may hold, surely the video community applauds your efforts.

[NikosD]

Frank, good news!

QSVEncC v2.00β is out in public adding QSV decode for H.264, MPEG2 and HEVC.

Here:http://1drv.ms/1FcV6XN

I told rigaya to use the plugin for HEVC HW decoding and he managed to implement QSV decoding for that format too in this version.

The new commands are:

--avqsv set input to use avcodec + qsv

--audio-file <string> extract audio into file.
could be only used with avqsv reader.

--trim <int>:<int>[,<int>:<int>]...

trim video for the frame range specified.
frame range should not overwrap each other.
could be only used with avqsv reader.

In his blog says that for HEVC needs elementary stream, but for MPEG2 and H.264 uses avcodec to demux .mp4/.mkv etc

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

Not sure how you are going to do your magic and integrate this new version to StaxRip.

Waiting for your feedback!

[stax76]

good news indeed, I think it mostly involves generating the command line with StaxRip's crop and cut values.

[burfadel]

New version of NNEDI3
http://forum.doom9.org/showthread.php?t=170083

10/05/2015 v0.9.4.9

+ Bug correction in x64 ASM file, thanks to jackoneill and HolyWu

Don't forget MKVToolNix 7.9.0. They changed the name of the archive so it is a little lost in their upload folder:
https://www.bunkus.org/videotools/mkvtoolnix/win32/
(just so others know, the 64-bit versions are also under win32).

[burfadel]

Stax, Avsmeter has been updated once again to v2.0.2

[detmek]

Hi Stax. I see that Staxrip requires Apple Application Support (AAS) to be installed in order to use QAAC. The point is - you can use QAAC even if AAS is not installed as long as you have correct files in qtfiles folder alongside qaac. Can you implement checking for those files before Staxrip asks for AAS installation?

P.S. You can run from command line qaac64.exe --check.

[stax76]

@burfadel

thanks for the updates

@detmek

I don't know if the last build already supports it, the next will sure support the folder QTfiles64, I'll also write it to the description so people know it from start.

[detmek]

I don't know if it is the latest but I use 1.3.1.1 beta and it does not support QTFiles64. It asks for AAS.

[stax76]

Hello everybody,

I'm releasing a new pre-release build today, a pre-release isn't tested by me so potentially has more issues then a beta.

pre-releases are now always full bundles, I created a dedicated public folder on MediaFire which can be found here:

https://www.mediafire.com/folder/0jakce45o99kb/StaxRip_pre-releases

If necessary I can provide a download mirror, free cloud drive providers are problematic because the bundle is 81 MB now so I don't know exactly where else I could upload it.

For the next beta release I'll try to use FossHub as mirror and finally release it on StaxRip's github page to complete the migration from sourceforge to github. I'll try to sync the code on github every time I make a release so github has currently the code for 1.3.1.1.

StaxRip x64 1.3.1.1 pre-release (2015-05-15)


Added DGAVCIndex as AVC TS demuxer, dsmux is still available but disabled by default
Added plugin flash3kyuu_deband v1.5.1
Added QSVEncC hardware decoding bypassing AviSynth and using StaxRip's cut/trim and crop values. On my Win10 development OS it don't work however and I didn't test on Win7
Changed DGIndex to demux and output m2v because DGDecode does not work on Win10, this means the old DVD workflow is fully supported again, MakeMKV is still recommended instead
Instead of always adding AssumeFPS it's now only added if necessary
The Applications dialog was renamed to Apps and Version and Description info was improved (only 50% completed)
Improved AviSynth editor and filter profiles
Improved 'Just Mux' feature supporting more formats
Fixed qaac executed with command window, improved qaac description in applications dialog
Fixed crash in preview window caused by AviSynth, StaxRip shows a error message instead now
Fixed crash caused by stream title containing character that are illegal in windows file system
Fixed two bugs in the 'Execute Command Line' command of StaxRip's command engine which powers StaxRip CLI, various menus and event commands
Updated MP4Box to 0.5.2-DEV-rev376 static mingw build, I made some basic tests which succeeded, Selur said -hint don't work but nobody ever requested -hint support in StaxRip.
Updated MKVToolNix 7.9.0 x64
Updated nnedi3 0.9.4.9 x64, nnedi3 and DGDecNV are now working on Win8 and Win10, DGDecNV 2049 has to be re-downloaded
Updated AVSMeter 2.0.2 x64, the main menu can be customized to add custom CLI switches
Updated qaac 2.48 x64 and improved integration
Updated l-Smash-Works 785 x64

[burfadel]

Any reason for there being the nnedi3.dll (the 10 May 2015 update) and _nnedi3.dll (01 December 2013) files?

[stax76]

Just forgot to remove it, thanks.

[videoh]

DGDecode does not work on Win10 That's hard to believe. Can you please tell us specifically what is not working for you?

[stax76]

That's hard to believe. Can you please tell us specifically what is not working for you?

StaxRip is now x64 only, if I remember right then DGDecode x64 ported by JoshyD worked on Win7 but on Win10 it's not working at all.

DGDecIM x64 is currently also not working with StaxRip, it's the same or similar problem as DGDecNV x64 had I would guess.

[videoh]

Ah, the 64-bit hacked one, OK. Thanks for the clarification.

I will fix DGDecIM right now and upload it. Thanks for pointing it out.

[videoh]

OK, please re-download DGDecIM b50. It has the same fix as we made for DGDecNV. Thank you for your testing.

[stax76]

Ah, the 64-bit hacked one, OK. Thanks for the clarification.

I will fix DGDecIM right now and upload it. Thanks for pointing it out.

Thanks for reading here and fixing it.

edit:

it works!

[detmek]

Hi Stax. I tried a few things with this pre-release and it works.
I encoded movie with x264 and just mux audio and worked (MKV to MKV).
QSVEncC supports cutting and resizing. I tried to manually enter cropping values as my test clip didn't need any cropping but nothing was passed to QSVEncC.

[stax76]

Hi, the whole QSVEncC change I made was like ten lines very simple code:

https://github.com/stax76/staxrip/blob/master/General/VideoEncoder.vb#L1371

I could not get it working so I thought maybe it's a Win10 only problem, I had also problems to create a fake monitor connection on Win10, on Win7 I had never problems with it, unfortunately I have quite many small issues on Win10, with Visual Studio 2015 RC I have no issues at all.

The generated command line looked good, it can be seen in the config dialog or log file. It adds the crop values from the cropping dialog and the trim values from the preview dialog.

[detmek]

For some reason encoder show error if I use QSV decoding and cropping. If I turn of QSV decoding it works but trimming can not be used.
Here is a log file:
MARINA VISKOVIC - GDE SAM GRESILA_StaxRip.log (http://www.4shared.com/file/MIot-bWlce/MARINA_VISKOVIC_-_GDE_SAM_GRES.html)

[stax76]

For some reason encoder show error if I use QSV decoding and cropping. If I turn of QSV decoding it works but trimming can not be used.
Here is a log file:
MARINA VISKOVIC - GDE SAM GRESILA_StaxRip.log (http://www.4shared.com/file/MIot-bWlce/MARINA_VISKOVIC_-_GDE_SAM_GRES.html)

I couldn't manage to download from 4shared, for log files there is nothing better then pastebin with auto expire. ;)

Unfortunately I already found the first problem, crop and trim should only be applied when hardware decoding is used, I upload a new build tomorrow.

edit:

fixed build using crop and trim only when hardware decoding is used:

http://www.mediafire.com/download/g8ijb2y2adxln12/StaxRip_QSVEncC_fix.7z

[detmek]

Still error:

https://www.dropbox.com/s/pzdnzatsaz84hw7/MARINA%20VISKOVIC%20-%20GDE%20SAM%20GRESILA_StaxRip.log?dl=0

Does Dropbox works?

[stax76]

DropBox is great (with large traffic they lock files quickly though). The command line looks good except -sar is used even when resizing is enabled, this should be a bug. I had the same error and don't really know what's wrong but we'll find out.

[dejong12]

With 1.3.1.0 and 1.3.1.1 the encoding speed with NVEnc drops to ~30fps with TDeint enabled. Version 1.2.2.2 with Yadif keeps the speed at around ~105fps while both versions have ~135fps without a deinterlace filter. All other settings are the same on both versions. Any reason why the x64 versions have such low encoding speeds? Indexing also takes three times longer on the x64 than on the x32 version too. The video is a 1080i AVC TV recording in MKV format.

[detmek]

It seams that it won't work only when crop is used. Maybe my CPU does not support crop?

P.S. I switched OS to Windows 7 SP1 due to a problems with WiFi adapter. Crop won't work even under Win 7.

[stax76]

With 1.3.1.0 and 1.3.1.1 the encoding speed with NVEnc drops to ~30fps with TDeint enabled.

Did you try to investigate it with AVSMeter? You can find AVSMeter at Tools/Advanced/AVSMeter. You could also try DSS2 using LAV Filters which you can configure at Tools/Advanced/LAV Filters config, Nikos reported that deinterlacing works with it. Overall I think there are quite a few options for deinterlacing.

Indexing also takes three times longer on the x64 than on the x32 version too. The video is a 1080i AVC TV recording in MKV format.

you mean ffms2? You can compare the ffms2 indexing speed against l-smash-works, it depends also on the source, there are differences. Can you record directly as MKV? I never knew a software that can do it.

It seams that it won't work only when crop is used. Maybe my CPU does not support crop?

P.S. I switched OS to Windows 7 SP1 due to a problems with WiFi adapter. Crop won't work even under Win 7.

What CPU do you use? I'll try it with my Ivy Bridge CPU.

[detmek]

Intel Pentium G3220 Haswell.

[dejong12]

Did you try to investigate it with AVSMeter? You can find AVSMeter at Tools/Advanced/AVSMeter. You could also try DSS2 using LAV Filters which you can configure at Tools/Advanced/LAV Filters config, Nikos reported that deinterlacing works with it. Overall I think there are quite a few options for deinterlacing.

This is being outputted with TDeint enabled in 1.3.1.1.
D:\StaxRip 1.3.1.1>"D:\StaxRip 1.3.1.1\Tools\AVSMeter\AVSMeter64.exe" "D:\Record
ed TV\Korra S4 FHD\De Legende van Korra - S04E01 temp files\De Legende van Korra
- S04E01_new.avs"

AVSMeter 2.0.2 (x64)
AviSynth+ 0.1 (r1825, MT, x86_64) (0.1.0.0)

Number of frames: 33247
Length (hh:mm:ss.ms): 00:22:09.880
Frame width: 1280
Frame height: 720
Framerate: 25.000 (25/1)
Colorspace: YV12

Frame (current | last): 7137 | 33246
FPS (cur | min | max | avg): 26.78 | 13.70 | 41.64 | 32.40
Memory usage (phys | virt): 114 | 117 MB
Thread count: 9
CPU usage (current | average): 35% | 35%

Time (elapsed | estimated): 00:03:40.312 | 00:17:06.157

Press 'Esc' to cancel the process...

And this is being outputted with Yadif enabled in 1.2.2.2.
D:\StaxRip 1.2.2.2 beta>"D:\StaxRip 1.2.2.2 beta\Tools\AVSMeter\AVSMeter64.exe" "D:\Record
ed TV\Korra S4 FHD\De Legende van Korra - S04E01 temp files\De Legende van Korra
- S04E01_new.avs"

AVSMeter 1.9.8.0 (x86)
AviSynth+ 0.1 (r1825, MT, i386) (0.1.0.0)

Number of frames: 33247
Length (hh:mm:ss.ms): 00:22:09.880
Frame width: 1280
Frame height: 720
Framerate: 25.000 (25/1)
Colorspace: YV12

Frame (current | last): 15099 | 33246
FPS (cur | min | max | avg): 112.0 | 65.88 | 118.1 | 101.4
Memory usage (phys | virt): 91 | 89 MB
Thread count: 9
CPU usage (current | average): 58% | 56%

Time (elapsed | estimated): 00:02:28.858 | 00:05:27.753

Press 'Esc' to cancel the process...


you mean ffms2? You can compare the ffms2 indexing speed against l-smash-works, it depends also on the source, there are differences. Can you record directly as MKV? I never knew a software that can do it.
Yeah with ffms2, but it's faster than I initially said, but a second slower than 1.2.2.2.

I can only record in .wtv because I use Windows Media Center and I haven't found a suitable successor yet. I use VideoRedo to cut out the commercials and save the resulting video in .mkv without recoding.

[stax76]

@detmek

Rigaya replied that it’s a bug of QSVEncC

@dejong12

It seems TDeint is rather slow, you could try Yadif with DSS2.

[detmek]

Thanks. So, we are waiting for a new version.

[NikosD]

A lot of fixes in latest β3 QSVEncC update, among them the crop issue:
http://rigaya34589.blog135.fc2.com/blog-entry-623.html

[Washka]

A lot of fixes in latest β3 QSVEncC update, among them the crop issue:
http://rigaya34589.blog135.fc2.com/blog-entry-623.html

Testing :)

[luigizaninoni]

Made some more tests on Staxrip 64 bit. In my opinion there are a few important issues:

For the following tests the configuration is: StaxRip x64 pre-release or Staxrip x32 1.2.2.0 - i7-4770S – x265 slow preset – Encode clip 1h 41m (same clip used throughout the tests)

Script:
LoadPlugin("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\Plugins\ffms2\ffms2.dll")
Import("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\Plugins\QTGMC\QTGMC.avsi")
LoadPlugin("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\Plugins\masktools2\masktools2.dll")
LoadPlugin("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\Plugins\mvtools2\mvtools2.dll")
LoadPlugin("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\Plugins\nnedi3\nnedi3.dll")
LoadPlugin("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\Plugins\RgTools\RgTools.dll")
FFVideoSource("C:\Users\luigi.TZMS\Desktop\sherlock temp files\sherlock.m2v", cachefile = "C:\Users\luigi.TZMS\Desktop\sherlock temp files\sherlock.ffindex")
QTGMC(Preset="Slow") (InputType=1 for progressive)
SelectEven() (only for interlaced)
RemoveGrain()


ISSUE N.1: AVISYNTH+ GRADUALLY SLOWS DOWN


To show the progressive slowdown of Avisynth+ I made two checkpoints: one at 5.000 frames and one at 150.000 frames (near the end of the encode)

Single-threaded Avisynth+:
Progressive: Encode starts at full steam: CPU at average 75%, fps 19,20 at 5.000-frame checkpoint. CPU is split into about 60% x265, and 15% avs4x26x

However encode gradually gets slower: fps and cpu keep going down. At 150.000-frame checkpoint we have CPU 50% (x265:35% and avs4x26x:15%) and fps 14,50. Fps have gone down 25%

Interlaced: At 5.000 frame checkpoint CPU at average 48% (32% x265 and 16% avs), fps 10,46. Obviously processing interlaced requires more work, so avs produces less frames for x265 to work on. The slowdown of the encoding becomes quite serious on interlaced: at 150.000-frame checkpoint fps are 2,65. Fps have gone down 75% !!

It seems that Avisynth+ is producing less frames over time, so x265 becomes less busy. The more complex the avs script, the more Avisynth+ slows down over time.

I repeated the same test with traditional Avisynth (not plus), and the problem does not exist:
Progressive: 17,75 fps at first checkpoint, 17,89 at second checkpoint. CPU steady around 70%
Interlaced: 11,44 fps and 11,51 respectively; cpu around 51-54%

ISSUE N.2: MULTITHREADED AVISYNTH+ CRASHES TOO OFTEN

For multithreaded scripts add:
SetFilterMTMode("DEFAULT_MT_MODE", 2)
SetFilterMTMode("FFVideoSource", 3) (at start of script)
Prefetch(6) (at end of script)

This issue has already been discussed in this thread, but the problem has not been solved yet. Encoding starts very fast, nearly 22 fps. However at a certain unpredictable point it crashes: it may be at the very beginning, it may be after a couple of hours, it seems totally random. If you are doing a very short encode, you might even manage to complete it without errors. Anyway MT Avisynth+ can’t be trusted at the moment.

ISSUE N.3: SOME 64-BIT PLUGINS ARE NOT AVAILABLE

For my workflow, I sometimes use MCTemporalDenoise for some noisy clips. I managed to find most 64-bit plugins required. However, I haven’t been able to find DCTFilter-64bit, so MCTD can’t be used. Is there any workaround, by the way ?

Although 64bit versions exist for most plugins, there is a still a fair number of 32bit-only dlls. So for more complex workflows you need to stick to avisynth-32bit.

CONCLUSIONS
Although very promising, Staxrip 64bit is not ready for prime time. The problems, it seems to me, lie not in Staxrip itself, but rather in Avisynth+ and/or its plugins (I don’t know exactly where the problem/s lie)

So in my opinion Staxrip 32bit should be kept alive at least for the time being, until problems are solved; not necessarily with the introduction of new features, but at least issuing maintenance releases.

Thanks Stax76 for your great work. Staxrip32 is an excellent program, and I am sure that, eventually, Staxrip64 will become very good,too

[stax76]

@luigizaninoni

Thanks for all the testing and feedback. I really hope these problem can be fixed within a few months, otherwise I will consider making StaxRip builds for both 64x and x86 or start with C++ programming.

StaxRip x64 1.3.1.2 pre-release (2015-05-19)


Added x265 switch --output-depth to choose between 8bit and 10bit output
Improved 'Demux Configuration' dialog
Fixed and changed cropping and resizing with QSVEncC, there is now for both crop and resize a special AviSynth filter profile 'Hardware Encoder' but if AviSynth is bypassed by enabling hardware decoding in QSVEncC then it's not necessary to use this special profiles, any crop or resize profile will do in this case.
Fixed bug audio streams not being detected for M2TS files
Updated x265 to x265_1.7+2
Updated QSVEncC to 2.0 beta 3


http://code.fosshub.com/StaxRip/downloads

https://github.com/stax76/staxrip/releases

[burfadel]

@Stax

QAAC 2.49 was just released yesterday.

[stax76]

Thanks, how did you find out? I've enabled a 'Watch' feature now on the qaac github page, I'm not sure what is does exactly though.

[burfadel]

I saw a new version of Staxrip, and just thought I'd check out the pages for QAAC etc, since I know it's in active development :). In other words, I wasn't expecting it, but since I use Firefox all I had to do was type in qa in the address bar and it was the first thing to show :).

I notice there still isn't an inverse telecine and decimate filter in the latest build. This is vital if encoding telecined (29.97 fps) material. The filter you had in the 32-bit Staxrip, Decomb, was fine :). There is a 64 bit version of it:
http://avisynth.nl/index.php/AviSynth%2B#AviSynth.2B_x64_plugins

I also notice you changed the 'tools' folder to 'apps'. If people just extract over what they already have, they may have a superfluous 'tools' folder... easy fixed I know, but may be worth mentioning :).

[Alexander]

@ Frank

[StaxRip x64 1.3.1.2 pre-release (2015-05-19)

with me DGDecodeNV does not work
error message

[Window Title]
StaxRip

[Main Instruction]
Failed to open source, try another method?

[Content]
DGSource: Invalid index file!
(Source.avs, line 2)

[stax76]

@Alexander

There is a issue you can fix yourself:

Tools > Settings > Demuxing > select DGIndexNV > Edit > Input Formats and Input File Types must be comma separated.

I'm still getting errors however, I try to find what's wrong.

@burfadel

I'm not sure Decomb works on Win10, I only include things that work on Win10, I'll try it. I didn't think renaming Tools to Apps could break something. Microsoft uses the name 'App' for both mobile and desktop applications, they will also allow to add desktop applications to the app store. When Win10 arrives I will try to add StaxRip to the app store, I don't know if it will work.

[videoh]

I'm not sure Decomb works on Win10, I only include things that work on Win10, I'll try it. It seems to work just fine on Win8.1 64-bit, so there's no reason it shouldn't work on Win10.

[stax76]

It seems to work just fine on Win8.1 64-bit, so there's no reason it shouldn't work on Win10.

I was getting all kind of crazy errors that all went away after reboot, Win10 is fairly buggy, I'm not having a great experience but it's OK.

I have a question to you however, I notice StaxRip is receiving progress from your indexing applications, the code is old and I don't remember if I monitor the title of the application or if this progress comes from stderr/stdout, if it comes from stdout/stderr which API do you use for this? I was suggesting to l-smash to send progress but nobody really knew how to do it.

edit:

I thought you were referring to my post about DGDecNV, I had problems with it that went away after reboot, I'm now trying Decomb.

edit 2:

Decomb x64 works on Win10

[videoh]

I have a question to you however, I notice StaxRip is receiving progress from your indexing applications, the code is old and I don't remember if I monitor the title of the application or if this progress comes from stderr/stdout, if it comes from stdout/stderr which API do you use for this? I was suggesting to l-smash to send progress but nobody really knew how to do it. Every 30 frames, this function is called to write to stdout:

void OutputProgress(int progr)
{
static int lastprogress = -1;

if (progr != lastprogress)
{
char percent[20];
DWORD written;

sprintf(percent, "%d\r", progr);
WriteFile(GetStdHandle(STD_OUTPUT_HANDLE), percent, (DWORD) strlen(percent), &written, NULL);
lastprogress = progr;
}
}

progr is an int 0-100 indicating the percent completed. The caller determines the percent complete from the ratio of the current file position and the size of the file. That way you don't need to know the number of frames in the file.

Decomb x64 works on Win10 Sweet.

[stax76]

Every 30 frames, this function is called to write to stdout:

void OutputProgress(int progr)
{
static int lastprogress = -1;

if (progr != lastprogress)
{
char percent[20];
DWORD written;

sprintf(percent, "%d\r", progr);
WriteFile(GetStdHandle(STD_OUTPUT_HANDLE), percent, (DWORD) strlen(percent), &written, NULL);
lastprogress = progr;
}
}

progr is an int 0-100 indicating the percent completed. The caller determines the percent complete from the ratio of the current file position and the size of the file. That way you don't need to know the number of frames in the file.

Sweet.

Thanks, would be a great improvement for L-Smash-Works, I'll forward it.

[Alexander]

@Frank


Ok, thank
I did not see that there are missing commas

[luigizaninoni]

Stax, have you seen Rean's reply on Avisynth+ thread ?:

Quote:
ISSUE N.1: AVISYNTH+ GRADUALLY SLOWS DOWN
It is not an Avisynth problem. It is because the user uses very complex QTGMC script with many plugins. Many MT processing = many bottleneck states. And x264 is extreme optimized software.

ISSUE N.2: MULTITHREADED AVISYNTH CRASHES TOO OFTEN
It is a non-compatibility of FFVideoSource with some video sources and MT. I was getting constant crashes with this plugin. Therefore, I stop using it.
But, the majority of Avisynth crashes is that in 32 bits there is no free memory for all plugin buffers and frame cache.

----------------------------------------------------------
I thought that perhaps he was right about FFvideosource, so in Staxrip64 I tried with Frimsource instead of FFVideoSource (installed intel media sdk and so on)

Well, he really was right: no more slowdowns, fps steady at 19,10 (qtgmc progressive) and cpu at 67% throughout the encode. Speed improvement of 7% over classic Avisynth, not a great deal but still appreciated.

Then I thought, if Ffvideo source is causing the slowdown, it might also be the cause of the crashes in MT.

Look and behold, tried Frimsource MT and encode is not yet finished but it is at 21fps, cpu 100% and no sign of slowdown or crashes.

So I may have incorrectly blamed Avisynth+, while the real culprit was FFVideoSource

So, if this is the situation, I'd like to ask your advice for my .ts qtgmc encodes:

1- I can't use Frimsource, because it works only on QTGMC progressive. If I try QTCMC interlaced, if fails with message:

MergeLuma: Images must have same width and height!
(C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Apps\Plugins\QTGMC\QTGMC.avsi, line 394)
(C:\Users\luigi.TZMS\Desktop\Film\sherlock temp files\sherlock.avs, line 8)

Have you any solution for this error ? Any idea what might be the cause ?

2- If there is no solution, what other source filters could I try instead of FFVideoSource ?

[stax76]

@Frank


Ok, thank
I did not see that there are missing commas

There was a bug separating the file types by space only, that's the only problem I'm aware, I tested it and it worked.

@luigizaninoni

Thanks for the info and investigation, keep going, I'm looking into it once I finish a few other things I currently investigate.

[stax76]

The version of xvid_encraw included does not support the "-metric [integer]"

I replaced it with your version.

An xvid_encraw encoding process cannot be aborted via the GUI.

It should work in recent builds, for two command lines you have to abort two times.

While the "filters" edit window now postions itself properly on the screen

You mean the new editor? It adjusts the vertical size automatically every time enter or backspace is pressed, what it lacks so far is auto adjust for cut and paste. I'm willing to improve it but would need a detailed description.

The sample code for xvid_encraw does not include a sample for the compressibility check.

I've added it.

edit:

both builds work but Patman's is newer.

[jkilez]

Thanks for the quick update! Sorry if I was in the wrong thread--I am playing catch-up on what you have done. Good stuff.
You mean the new editor? It adjusts the vertical size automatically every time enter or backspace is pressed, what it lacks so far is auto adjust for cut and paste. I'm willing to improve it but would need a detailed description.
I mean the AviSynth Editor window, which (unless you have already fixed it) looks like this:
http://i.imgur.com/AXTGRji.png

My filters are difficult to edit in that space as they often have long chains that look like this:
b1.trim(0, 620) ++ \
b2.trim(621,622) ++ b1.trim(623,623) ++ b2.trim(624,626) ++ b1.trim(627,627) ++ b2.trim(628,658) ++ \
mt_merge(b1.ColorYUV(gamma_y=-6),last.ColorYUV(off_y=-2),mask,luma=true,chroma="process").trim(659,660) ++ \
mt_merge(b2.ColorYUV(gamma_y=-1),last.ColorYUV(off_y=-1),mask,luma=true,chroma="process").trim(661,665) ++ \
mt_merge(b1.ColorYUV(gamma_y=-5),last,mask,luma=true,chroma="process").trim(666,666) ++ \
mt_merge(b1,last,mask,luma=true,chroma="process").trim(667,2026) ++ \
b2.trim(2027,2033) ++ b3.trim(2034,2101) ++ b5.trim(2102,2821) ++ b4.trim(2822,8300) ++ trim(8301,0)

[Patman]

Hi Stax,

ffms2 was updated to version 2.21 before 5 days. Which version of ffms2 do you use? msvc or icl?

[stax76]

Hi Stax,

ffms2 was updated to version 2.21 before 5 days. Which version of ffms2 do you use? msvc or icl?

Hello Patman,

IIRC I updated to 2.21 MSVC

[NikosD]

Hello.

Using latest StaxRip x86 (1.2.2.2) /x64 (1.3.1.2) and latest nightly HandBrake x64 svn7214 I tested QSVEncC x86 (v1.33) /x64 (v2.00β3) in both modes SW and HW decoding for x64 version.

The system used is Core i7 4790 – Win 8.1 x64 Pro – iGPU HD 4600@1.5GHz – Drivers 4206

I used CQP encoding mode which is available for both applications using the value of 24 with Balanced target usage and everything else set to Auto (default)
I didn’t use Audio encoding (Just Mux option or Auto Pass-through)

For HandBrake I used the command la=0 in order to disable LookAhead option, but the result was the same like the default setting which had LookAhead enabled (at least in the older versions), so probably LookAhead was used resulting in lower performance for HandBrake.

The CPU decoding mode used all 8 cores (HT) with the default sources for StaxRip x86/x64 (usually FFVideoSource/ LSMASH). The HW decoding mode used CPU at about 2-3% for both StaxRip and HandBrake except in HEVC (look below)
For HEVC I used another decoder which is LAV v0.65 DXVA copy-back decoder with DSS2 source filter.

I tested all three video formats available for HW decoding (H.264, MPEG2, H.265) with progressive clips.

I also tested the scaling option (resize) for all apps using always in all cases the HW resizer.


H.264 – Chimei inn-2160p clip – 50Mbps


StaxRip x64 QSV 84 fps – Time 15s
HandBrake x64 72 fps – Time 21s
StaxRip x64 51 fps – Time 25s
StaxRip x86 48 fps – Time 26s


Same clip 2160p -> 1080p


StaxRip x64 QSV 169 fps – Time 7s
HandBrake x64 155 fps – Time 11s
StaxRip x64 61 fps – Time 21s
StaxRip x86 61 fps – Time 21s


H.264 – Eclectic-1080p clip – 11Mbps


StaxRip x64 QSV 301 fps – Time 11s
HandBrake x64 240 fps – Time 14s
StaxRip x86 239 fps – Time 14s
StaxRip x64 229 fps – Time 14s


Same clip 1080p -> 720p


StaxRip x64 QSV 462 fps – Time 7s
HandBrake x64 393 fps – Time 9s
StaxRip x86 268 fps – Time 12s
StaxRip x64 268 fps – Time 12s


MPEG2 – 1080p30fps – 22Mbps


StaxRip x64 QSV 275 fps – Time 12s
StaxRip x64 227 fps – Time 14s
StaxRip x86 216 fps – Time 15s
HandBrake x64(CPU) 198 fps – Time 16s


HEVC – Girls – 1080p – 11Mbps


StaxRip x64 173 fps – Time 68s
StaxRip x86 112 fps – Time 106s
StaxRip x64 QSV 90 fps – Time 132s CPU 15%
HandBrake x64(CPU) 90 fps – Time 132s
StaxRip x64 (DSS2+LAV(CB) 86 fps – Time 138s CPU 22%


So, the huge difference is in resizing and the CPU usage (which drops near 2-3%)

For HEVC the x64 CPU decoders are much faster than hybrid GPU decoders, besides HandBrake which is x64 but has a very slow CPU HEVC decoder
The x86 CPU decoders are much closer to hybrid decoders.

HandBrake supports only H.264 in HW decode mode.

[Patman]

Hello Patman,

IIRC I updated to 2.21 MSVC

Ah okay. The date that was shown was 2015-05-02 but the latest version is 2015-05-16. That's the reason why i'm asking.

[NikosD]

QSVEncC v2.00β4 is out fixing 10bit HEVC decoding for Broadwell among a few things.

[stax76]

Hello everybody,

I was working on a couple of improvements and uploaded a new beta. I still like GUI programming so I improved the AviSynth editor a lot.

I'm pausing StaxRip now again for a while but don't worry, I'll be back and catch up with unanswered questions.

StaxRip x64 1.3.1.3 beta (2015-05-21)

Added Decomb x64 plugin
Greatly improved AviSynth editor
eac3to dialog is now suppressed in batch mode
Improved frame rate correction
Replaced DGAVCDec with dsmux
Re-added backup feature to keep backup of filter, audio and video encoder profiles. It means when filter, audio or video encoder profiles are reset, previous profiles are still available in a Backup sub menu, the menu structure is customizable so profiles of the backup sub menu can be moved to top level using the profiles editor which supports multi-select.
Fixed wrong DGIndexNV demux configuration
Updated ffms2 to 2.21

http://code.fosshub.com/StaxRip/downloads

http://www.mediafire.com/folder/0jakce45o99kb/StaxRip_beta

[burfadel]

I'm running Windows 10 TP, and updated to build 10122 that just came out. Just thought I'd let people know there seems to be a strange issue with Staxrip and QAAC. I mentioned this in the LAV filters thread, but I was all over the place about what was causing it. QAAC seemed to stop part way through the actual encode process, and staxrip would throw the error. When copied and pasted the command line to the command line, it worked fine! Now, I thought it was one thing then thought it was another, but in reality it seems to work properly all the time... for now... when it is minimised to the system tray! I normally have it this way anyway, but since it goes pretty quickly etc it never occurred to me initially that it was the cause. So, for the times I did find it working as mentioned, it was probably because it was minimised? I can't remember!

Anyways, so it seems there may be a new bug in the new build with, or affecting, NET Framework. I guess it's with the new build of NET Framework 4.6 (which is the Windows 10 version of NET Framework 4.5).

I'll let you know how the new Staxrip version goes.

[stax76]

I'm running Windows 10 TP, and updated to build 10122 that just came out. Just thought I'd let people know there seems to be a strange issue with Staxrip and QAAC. I mentioned this in the LAV filters thread, but I was all over the place about what was causing it. QAAC seemed to stop part way through the actual encode process, and staxrip would throw the error. When copied and pasted the command line to the command line, it worked fine! Now, I thought it was one thing then thought it was another, but in reality it seems to work properly all the time... for now... when it is minimised to the system tray! I normally have it this way anyway, but since it goes pretty quickly etc it never occurred to me initially that it was the cause. So, for the times I did find it working as mentioned, it was probably because it was minimised? I can't remember!

Anyways, so it seems there may be a new bug in the new build with, or affecting, NET Framework. Not sure what version of NET Framework is now used for Staxrip...

I'll let you know how the new Staxrip version goes.

Minimum .NET version is 4.5, I'll use qaac for my next encodes and don't minimize, maybe I can reproduce it.

[burfadel]

Any reason for the 1.3.1.3 build using the old QAAC 2.48? It happens with 2.48 as with 2.49.

The error is now happening again, but only after I closed Staxrip so I could use the new version!

Error Audio encoding using qaac

Audio encoding using qaac failed with exit code 255

qaac 2.48, CoreAudioToolbox 7.9.9.6
2006-02-19 - s13e05 - Utrecht, The Netherlands - The Boat On The Rhine ID2 English_out.m4a
Scanning maximum peak...
127172608/127172608 samples processed in 0:00.797
Peak value: 0.279785
AAC-LC Encoder, TVBR q64, Quality 96



StaxRip.ErrorAbortException: Audio encoding using qaac failed with exit code 255

qaac 2.48, CoreAudioToolbox 7.9.9.6
2006-02-19 - s13e05 - Utrecht, The Netherlands - The Boat On The Rhine ID2 English_out.m4a
Scanning maximum peak...
127172608/127172608 samples processed in 0:00.797
Peak value: 0.279785
AAC-LC Encoder, TVBR q64, Quality 96


at StaxRip.Proc.Start() in D:\Projekte\GitHub\staxrip\General\Proc.vb:line 226
at StaxRip.GUIAudioProfile.Encode() in D:\Projekte\GitHub\staxrip\General\AudioProfile.vb:line 612
at StaxRip.MainForm.Encode() in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:line 2220
at StaxRip.MainForm.RunJobRecursive() in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:line 3446

The above message only shows the first pass for the normalisation. It's the second, slower pass that fails. It failed at 17.6 percent in this case. As I said, even if it constantly fails in Staxrip, the same command line constantly works from the command prompt!

Any chance of a couple of different builds (just staxrip) using different compiler/compiler settings? Just curious :)

[stax76]

It must be specific to your system, here everything is fine:

http://pastebin.com/ukmKMK65

[burfadel]

Probably an issue in the update process, apparently it's been finicky and not working/not working properly for a lot of people.

It's interesting yours says:
v4\Client : 4.6.00073
v4\Client\1031 : 4.6.00073
v4\Full : 4.6.00073
v4\Full\1031 : 4.6.00073
v4.0\Client : 4.0.0.0

and mine says:
v2.0.50727 : 2.0.50727.4927
v3.0 : 3.0.30729.4926
v3.5 : 3.5.30729.4926
v4\Client : 4.6.00073
v4\Full : 4.6.00073
v4.0\Client : 4.0.0.0

Of course I realise you don't have the 3.5 installed, I'm referring to the 4.6 entries. Language pack? Anyways, it's now working again. I won't touch it!

[stax76]

StaxRip redirects the output from qaac but qaac is still a separate process, it's hard to tell why it works with cmd.exe, there might be different environment variables. What can be done is attaching a debugger to a running process, I can only do it with Visual Studio which is a huge download and setup and it's not clear it would catch a exception. Did you check the windows event log?

edit:

If it don't terminate instantly maybe you could make a crash dump, the windows task manager has a option in the context menu.

Also remember you can still use Nero or FDK AAC.

[Washka]

With Latest beta: StaxRip x64 1.3.1.3 beta (2015-05-21) I got problems with all *.mkv files. I upload encoded sample. Any other version have no this problem. Mp4 have no problems.
I upload sample video to dropbox, audio is Just Mux since it`s ac3.

https://www.dropbox.com/s/1e5ch01jy8nmuid/Sample_StaxRip.log?dl=0
https://www.dropbox.com/s/4ggq0kgrgdjaasj/Sample.mkv?dl=0

First one second is double than audio is not in sync.

[Havokdan]

StaxRip x64 have support for TextSub/Vobsub plugin? I dont see in filtters.

[burfadel]

Also remember you can still use Nero or FDK AAC.

I was thinking that exactly!

When it doesn't work, it doesn't work consistently, but when it does work it works consistently between encodes. Since the audio encoding happens first, I think I'll just start it again until it works! It's obviously something very minor, I just can't pinpoint what it is. I'm heavily suspecting it's a new bug, I guess that's expected on a beta OS.

[stax76]

With Latest beta: StaxRip x64 1.3.1.3 beta (2015-05-21) I got problems with all *.mkv files. I upload encoded sample. Any other version have no this problem. Mp4 have no problems.
I upload sample video to dropbox, audio is Just Mux since it`s ac3.

https://www.dropbox.com/s/1e5ch01jy8nmuid/Sample_StaxRip.log?dl=0
https://www.dropbox.com/s/4ggq0kgrgdjaasj/Sample.mkv?dl=0

First one second is double than audio is not in sync.

I made test where everything worked as usual, the frame rate detection was changed, when you double click the filters you can see StaxRip added AssumeFPS because ffmpeg returns often values that cause problems, maybe it has something to do with this. Maybe I can find something if you post a source clip and log file.

StaxRip x64 have support for TextSub/Vobsub plugin? I dont see in filtters.

I first removed the plugin and code but later found a x64 version so I re-added the plugin and code, I've not used it recently but believe it should work

[Havokdan]

I first removed the plugin and code but later found a x64 version so I re-added the plugin and code, I've not used it recently but believe it should work

Thanks

[luigizaninoni]

Remember the three issues with .ts ?:
1-slowing down
2-MT crashing
3- 64-bit plugins missing

Issue n.1 imo is solved:
Instead of FFVideoSource use DSS2mod. Speed is steady throughout the encode. Be very liberal in "cache" and "preroll" parameters. Demux with dsmux. Works with QTGMC, both interlaced and progressive mode.

If it does not saturate CPU, you can run 2 parallel encodes without problems.

Tried also MT, but with filter mode 3 does not even start. With modes 1 and 2 it starts but crashed after a few seconds.

Anyway n.2 is partially solved, given that you can use FrimSource for Qtgmc progressive (not for interlaced, unfortunately.)

N.3 still stands.

[jkilez]

Using the new 1.3.1.3 beta, I am getting 7 frames (300ms) of blank video added to the beginning of encoded videos causing audio sync issues. Actually the framecount stays correct (it cuts 300ms at the end), so the problem is more that the video is offset by 300ms. So far I have only had a chance to check this with an AVC source. The problem does not appear when previewing, only in the final encodes and happens regardless of output (1-pass/2-pass, Xvid/x264, AVI/MKV, AC3/MP3/None).

The problem appears to be with the ffms2 indexer that was updated. If I replace the /Apps/Plugins/ffms2 directory with the version that came with 1.3.1.0, there is no delay.

ETA: Just compared encodes from an MPEG-2 (DVD) source:
1.1.9.0 = 0 extra frames
1.3.1.0 = 0 extra frames
1.3.1.3 = 2 extra frames

[Washka]

Using the new 1.3.1.3 beta, I am getting 7 frames (300ms) of blank video added to the beginning of encoded videos causing audio sync issues. Actually the framecount stays correct (it cuts 300ms at the end), so the problem is more that the video is offset by 300ms. So far I have only had a chance to check this with an AVC source. The problem does not appear when previewing, only in the final encodes and happens regardless of output (1-pass/2-pass, Xvid/x264, AVI/MKV, AC3/MP3/None).

The problem appears to be with the ffms2 indexer that was updated. If I replace the /Apps/Plugins/ffms2 directory with the version that came with 1.3.1.0, there is no delay.

ETA: Just compared encodes from an MPEG-2 (DVD) source:
1.1.9.0 = 0 extra frames
1.3.1.0 = 0 extra frames
1.3.1.3 = 2 extra frames

Got same problems. I write about that at Post #201

[stax76]

Until the problem is solved I suggest using LWLibavVideoSource instead, go to:

Tools > Settings > Source Filters

Replace FFVideoSource every where with LWLibavVideoSource.

[burfadel]

Just giving feedback on the issue I was having with QAAC. Seems to be resolved now. I did all the stuff you shouldn't need to do (in-depth maintenance and repair stuff related), and it seems to work. Not sure what fixed it, and as long as it works reliably I don't care now :D! It appears it wasn't a 100 percent successful transition from build 10074 --> 10122. I guess you should expect things to possibly get muffed, but not sure how going from Windows 7 and 8.1 will be like. Microsoft really needs that to be effectively, 100 percent reliable.

[jkilez]

Hello everybody,

I was working on a couple of improvements and uploaded a new beta. I still like GUI programming so I improved the AviSynth editor a lot.

I'm pausing StaxRip now again for a while but don't worry, I'll be back and catch up with unanswered questions.

StaxRip x64 1.3.1.3 beta (2015-05-21)

Added Decomb x64 plugin
Greatly improved AviSynth editor
Thanks for the editor improvements--it is much more usable now.


One quick GUI bug...

Opening the log file for the current project using the menu item Tools->Files->Log File does not work as it is using the wrong file name "%source_name%_StaxRip.log" vs "%target_name%_StaxRip.log".


ETA: Another little bug...

When editing the "XviD 2 pass" encoder profile through "Edit Profiles..." section, it brings up a window listing "Codec Configuration", "Run Compressibility Check", and "Container Configuration" options. The "Codec Configuration" option brings me right to the "Batch Encoder" editing page as expected, but the "Run Compressibility Check" option just runs the compressibility check (if there is one defined) instead of taking me to the edit page.

[Patman]

Using the new 1.3.1.3 beta, I am getting 7 frames (300ms) of blank video added to the beginning of encoded videos causing audio sync issues. Actually the framecount stays correct (it cuts 300ms at the end), so the problem is more that the video is offset by 300ms. So far I have only had a chance to check this with an AVC source. The problem does not appear when previewing, only in the final encodes and happens regardless of output (1-pass/2-pass, Xvid/x264, AVI/MKV, AC3/MP3/None).

The problem appears to be with the ffms2 indexer that was updated. If I replace the /Apps/Plugins/ffms2 directory with the version that came with 1.3.1.0, there is no delay.

ETA: Just compared encodes from an MPEG-2 (DVD) source:
1.1.9.0 = 0 extra frames
1.3.1.0 = 0 extra frames
1.3.1.3 = 2 extra frames

Got the same problem. Every mkv file is async. Damn... :mad:

Edit1: Run test with updated ffms2... will report later...

Edit2: I've tested two encodes with the new ffms2 2.22 rc1. There were no async in mkv-files anymore... :) I'll test some other files...

Edit3: With ffms2 2.22 rc1 mkv-files still minimal async... go back to ffms2 2.20... Hope for solution

[stax76]

I noticed it too today, ffms2 2.20 is fine, the issue was introduced with 2.21, it's also fine to use LWLibavVideoSource: Tools > Settings > Source Filters

[jkilez]

Another bug: The "Options->Misc->Auto Forced Film Threshold (Percent)" is not being honored. MPEG-2 (DVD) sources with a DGIndex "Video Type" of between 95% and 99% Film are listed with a frame rate of 29.97 when they should be 23.976. The same sources work properly in 1.1.9.0.

[stax76]

Another bug: The "Options->Misc->Auto Forced Film Threshold (Percent)" is not being honored. MPEG-2 (DVD) sources with a DGIndex "Video Type" of between 95% and 99% Film are listed with a frame rate of 29.97 when they should be 23.976. The same sources work properly in 1.1.9.0.

StaxRip x86 modifies the d2v file for this. With DGDecode x64 there are problems on Win10, on Win7 probably too so it's not used until somebody fixes it.

Both ffms2 and L-Smash-Works have a parameter dealing with NTSC, I can add the parameter to the filter profiles but I don't know yet if it can be automated to set the parameter. I admit I'm pretty clueless about NTSC so how well NTSC is supported depends much on the quality of the feedback I get for it.

[Anakunda]

HI STAX
Trying to load demuxed project into latest beta (.dgi + .h264 file). On source open I get error System eception - Accesss Violation, H:\video\(workset)\test\encode_Source.avs, line 2)

encode_Source.avs is
LoadPlugin("D:\media\DGDecNV\x64 Binaries\DGDecodeNV.dll")
DGSource("H:\video\(workset)\test\source.dgi")


source.dgi is correctly referring to source.h264

What's wrong?

avisynth.dll in C:\Windows\System32\ is version: AviSynth+ 0.1 (r1825, MT, x86_64)

http://i.imgur.com/nL7DsHh.png http://i.imgur.com/uYQTa8d.png http://i.imgur.com/T9kvOSf.png

[stax76]

There was a problem with DGDecodeNV x64, a new build of DGDecNV was uploaded addressing this problem, it will work if you re-download DGDecNV.

[Anakunda]

Which build? 2047? I already have it.

+ I can't find DGIndexIM anywhere, all links in doom9 thread seem dead, a working mirror?

[Groucho2004]

Which build? 2047? I already have it.
2049, Link here (http://rationalqm.us/binaries.html). 2047 is ancient.

[Groucho2004]

+ I can't find DGIndexIM anywhere, all links in doom9 thread seem dead, a working mirror?
Probably from here (http://rationalqm.us/board/viewtopic.php?f=4&t=405).

[Reel.Deel]

Probably from here (http://rationalqm.us/board/viewtopic.php?f=4&t=405).

The link on that thread is dead. I believe the latest DGDecIM is always here: http://rationalqm.us/mine.html

Hmm, whats up with the naming scheme? b21 in March and b50 in May? :confused: Either a lot of development or something else...

[Groucho2004]

The link on that thread is dead. I believe the latest DGDecIM is always here: http://rationalqm.us/mine.html
Oops, didn't realize it pointed to the old build. Anyway, the thread might have some valuable info.

[videoh]

Hmm, whats up with the naming scheme? b21 in March and b50 in May? :confused: Either a lot of development or something else... The numbers are arbitrary but they do increase monotonically. :) The bigger the number jump, usually the more things changed functionally.

[jkilez]

I admit I'm pretty clueless about NTSC so how well NTSC is supported depends much on the quality of the feedback I get for it.
Let me know if there is something that I can do to assist. I have crates of NTSC DVDs.

[burfadel]

@Stax

New NNEDI3 9.9.4.10
http://forum.doom9.org/showthread.php?p=1662264#post1662264

[jkilez]

Another quirk...

FFmpeg does not like muxing to AVI. It creates an ostensibly usable file, but the audio tags are messed up which causes some programs/devices to not properly recognize the audio codec.

MP3 muxes have a minor issue in that they lack a "Frame Count" parameter which can cause CBR encodes to report as VBR. This does not appear to affect actual performance. The greater issue is muxing AC3 into AVI. In this circumstance, FFmpeg uses codec tags that may be completely foreign to some players causing them to balk with an error.

Here are the tags created by a VirtualDub mux (as shown from MediaInfo):
Codec ID : 2000
Codec : AC3
Codec : AC3
Codec/Family : AC3
Codec/Info : Dolby AC3
Codec/CC : 2000
And here is the same section from an FFmpeg mux:
Codec ID : 00001000-0000-0020-8000-00AA00389B71
Codec : AC3
Codec : AC3
Codec/Family : PCM
Codec/Info : Extensible wave format
Codec/CC : FFFE
From what I can research, this is a known issue with FFmpeg and the developers have basically said, "suck it--AVI is dead".

Given that I use Xvid/AVI just to maximize compatibility, I wish to use VirtualDub as the muxer instead of FFmpeg. To make this happen automatically, I have made an ad hoc muxing script using the old VirtualDubMod. This section of code can be added to the bottom of the XviD Batch Encoder sections:
set VD=<PATH TO VIRTUALDUBMOD.EXE>
set VCF=%temp_file%.vcf
set track1=%encoder_out_file_track1%
if "%track1:~-3%"=="ac3" ( set atype=0x00000203 ) else ( set atype=0x00000202 )
set txt=VirtualDub.Open("%encoder_out_file%","",0);
set txt=%txt% VirtualDub.video.SetMode(0);
set txt=%txt% VirtualDub.stream[0].SetSource("%track1%", %atype%, 0);
set txt=%txt% VirtualDub.stream[0].SetMode(0);
set txt=%txt% VirtualDub.stream[0].SetInterleave(1,500,1,0,%delay1%);
set txt=%txt% VirtualDub.SaveAVI("%target_dir%\%target_name%.VD%encoder_ext%");
echo %txt:\\=\\\\% > "%VCF%"
"%VD%" /x /s"%VCF%" && copy "%track1%" "%encoder_out_file%"
The output file that it creates has "VD" inserted before the extension so that you know which muxer created it. As listed, the code has a performance hack where it replaces the encoder output file with the audio file so that the native FFmpeg muxer can still quickly mux something without throwing an error.

[jkilez]

Another bug: The "Options->Misc->Auto Forced Film Threshold (Percent)" is not being honored. MPEG-2 (DVD) sources with a DGIndex "Video Type" of between 95% and 99% Film are listed with a frame rate of 29.97 when they should be 23.976. The same sources work properly in 1.1.9.0.

StaxRip x86 modifies the d2v file for this. With DGDecode x64 there are problems on Win10, on Win7 probably too so it's not used until somebody fixes it.

Both ffms2 and L-Smash-Works have a parameter dealing with NTSC, I can add the parameter to the filter profiles but I don't know yet if it can be automated to set the parameter. I admit I'm pretty clueless about NTSC so how well NTSC is supported depends much on the quality of the feedback I get for it.
A more significant problem is that even if I force it to use the proper frame rate, it does not count frames properly causing an A/V sync issue. When comparing a 1.3.1.3 encode against a 1.1.9.0 encode, sometimes the 1.3.1.3 is a couple frames ahead and sometimes it is a couple frames behind. The 1.1.9.0 encode stays in A/V sync throughout.

[burfadel]

@Stax

I came across this interesting bit of information regarding cropping:
http://avisynth.nl/index.php/Resize

Say you wanted to use Spline36resize, instead of:
Crop(%crop_left%, %crop_top%, -%crop_right%, -%crop_bottom%)
Spline36Resize(%target_width%, %target_height%)

You can use:
Spline36Resize(%target_width%, %target_height%, %crop_left%, %crop_top%, -%crop_right%, -%crop_bottom%)

It works for all internal resize filters (Sincresize, Lanczosresize, Blackmanresize etc). Would this be possibly, in general, more suitable than using the separate function?

[jkilez]

It works for all internal resize filters (Sincresize, Lanczosresize, Blackmanresize etc). Would this be possibly, in general, more suitable than using the separate function?
What advantage would it give?

I can see one possible disadvantage: any pre-resize filters would now also be pre-crop, which is simply disadvantageous if your filter is slow to begin with, but can be catastrophic if your source is mod 2 and your filter requires mod 8.

[burfadel]

I didn't mean as a replacement, just as an option :).

[ShamisOMally]

I managed to fix the audio sync problem by going and downloading the newest version of FFMS2 from Github.

Also come on, when am I going to be able to post without the damn random questions being asked of me?

[stax76]

New NNEDI3 9.9.4.10
http://forum.doom9.org/showthread.php?p=1662264#post1662264

updated and tested locally. :thanks:

FFmpeg does not like muxing to AVI

What about avconv, VirtualDub x64 or maybe even other tools, ideal would be CLI and small file size.

A more significant problem is that even if I force it to use the proper frame rate, it does not count frames properly causing an A/V sync issue. When comparing a 1.3.1.3 encode against a 1.1.9.0 encode, sometimes the 1.3.1.3 is a couple frames ahead and sometimes it is a couple frames behind. The 1.1.9.0 encode stays in A/V sync throughout.

1.1.9.0 used DGDecode which doesn't really work on x64, there are various other source filters, unfortunately I don't have NTSC experience but I've test material I want to experiment with.

I came across this interesting bit of information regarding cropping:

It's not easy to integrate it, do you think there is a worthwhile performance gain?

I managed to fix the audio sync problem by going and downloading the newest version of FFMS2 from Github.

Which version did you download?

[jkilez]

FFmpeg does not like muxing to AVI
What about avconv, VirtualDub x64 or maybe even other tools, ideal would be CLI and small file size.
avconv has the same issue as FFmpeg. VirtualDub x64 v1.10.4 (http://sourceforge.net/projects/virtualdub/files/virtualdub-win/1.10.4.35491/VirtualDub-1.10.4-AMD64.zip/download) with FccHandler's AC3 plug-in v1.9 (http://sourceforge.net/projects/fcchandler/files/Virtualdub%20Ac3%20plugin/) appears to work. The distribution size for the combo is less than 3MB compressed. As far as I can tell, VeeDub64 cannot mux from the command line as it still requires an external script file. The syntax is virtually identical to that of VirtualdubMod.

I will do some more testing with VeeDub64, if there is a possibility it will be incorporated into a release. If you have no real interest in it, I am content to stick with my current workaround.

[jkilez]

An xvid_encraw encoding process cannot be aborted via the GUI.
It should work in recent builds, for two command lines you have to abort two times.
A few notes here...

First, the abort now mostly works for the encoding process, but still does not work when using the "Run Compressibility Check" option.

Second, you could eliminate the need to abort twice for two pass encodes by simply adding "|| exit" to the end of the first pass line. As a general rule, you would want to do this anyway because it makes no sense to run the second pass if there was an error running the first pass.

Your example code would look like this:
"%app:xvid_encraw%" -smoother 0 ><...snip...>< -pass1 "%temp_file%.stats" -i "%avs_file%" || exit
"%app:xvid_encraw%" -smoother 0 ><...snip...>< -pass2 "%temp_file%.stats" -i "%avs_file%" -avi "%encoder_out_file%"

Third, the abort code just willy-nilly kills processes with the %app% name, whether they are tied to the current instance or not. If I have three encoding instances running, it will try to kill all three in sequence, starting with a random instance.

ETA: I was hoping that I would have a solution to the third problem before posting, but so far no luck. The problem would be trivially easy to resolve if there was just some mechanism in VB that would allow you to find Parent Process IDs.

ETA2: OK, here is stab at it from someone who has no way to check this stuff. The gist of the method is to use PerformanceCounter to find the PPID. First you need to find the unique instance of the process, then you can use that to find the parent. This is then compared to the PID of the CMD process that initiated the batch job. The code may be bad, but I believe the method is valid.

In file "General\Proc.vb" lines 282- (changes in red)

Sub KillAndThrow()
TrowException = True

Try
If BatchCode <> "" Then
Dim code = BatchCode.ToLower

For Each i In System.Diagnostics.Process.GetProcesses()
Try
If code.Contains(i.ProcessName.ToLower + ".exe") Then

Dim procName = System.Diagnostics.Process.GetProcessById(i.id).ProcessName
Dim procsByName = System.Diagnostics.Process.GetProcessesByName(procName)
Dim procIndexdName As String = Nothing
Dim tempIndexdName As String = Nothing

For idx As var = 0 To procsByName.Length - 1
tempIndexdName = If(idx = 0, procName, Convert.ToString(procName) & "#" & idx)
Dim procId = New System.Diagnostics.PerformanceCounter("Process", "ID Process", tempIndexdName)
If CInt(procId.NextValue()) = i.id Then
procIndexdName = tempIndexdName
End If
Next

Dim parentId = New System.Diagnostics.PerformanceCounter("Process", "Creating Process ID", procIndexdName)
Dim ppid = CInt(parentId.NextValue())

If ppid = Process.id Then

If Not i.HasExited AndAlso Msg("Confirm to kill " + i.ProcessName + ".exe",
MessageBoxIcon.Question,
MessageBoxButtons.OKCancel) = DialogResult.OK Then

i.Kill()
Thread.Sleep(2000)
End If

End If

End If
Catch
End Try
Next
Else
Process.Kill()
End If
Catch
End Try
End Sub

[ShamisOMally]

Which version did you download?

Whatever one was the newest on the page. I just downloaded the newest zip package of all the files and extracted the key files from it and replaced it

[stax76]

First, the abort now mostly works for the encoding process, but still does not work when using the "Run Compressibility Check" option.

should be fixed now.

Second, you could eliminate the need to abort twice for two pass encodes by simply adding "|| exit" to the end of the first pass line. As a general rule, you would want to do this anyway because it makes no sense to run the second pass if there was an error running the first pass.

Unfortunately I don't know the command shell and batch language really well. I've added this trick now to the xvid profile but without forcing to reset the video profiles.

OK, here is stab at it from someone who has no way to check this stuff. The gist of the method is to use PerformanceCounter to find the PPID. First you need to find the unique instance of the process, then you can use that to find the parent. This is then compared to the PID of the CMD process that initiated the batch job. The code may be bad, but I believe the method is valid.

Thanks for the patch. :thanks:

I didn't really try to understand it or test it thoroughly but it seems to work.

it's on github, only change since the last release since I'm still taking a break.

I will do some more testing with VeeDub64, if there is a possibility it will be incorporated into a release.

Adding new tools is problematic since the size is growing all too fast, what is no problem is adding features and show the Apps dialog asking for the path in case the feature is actually used, integrating VirtualDub this way would be fine. It would be very helpful if you can test it.

[Patman]

Hi everyone,

i've updated ffms2 to latest version (http://forum.doom9.org/showthread.php?p=1724587#post1724587) which was released by Myrsloik. Since that no further audio delays in final encoded files. I hope the same for you ;)

[stax76]

Hello patman,

I tested it too, the delay issue is fixed, since the bug was fatal I made a small release:

StaxRip x64 1.3.1.4 beta (2015-05-31)


Added feature to choose which source filter to use when a single file is opened, this gives more MeGUI manual workflow like control without giving up much of StaxRip's automated character
Fixed failing to show log file from main menu
Updated qaac to 2.49
Updated ffms2 to 2.22 RC2


http://github.com/stax76/staxrip/releases

I've a better understanding of NTSC now and some ideas how to make it easier to deal with. Also I've been thinking about more control and manual workflow for a very very long time now and implemented a first feature today, what will follow is a demuxing dialog for mkv/mp4 and maybe more formats similar to the eac3to dialog, this way demuxing might be skipped without modifying the settings, this is useful for instance if the file was previously opened and demuxed. It' not gonna be a paradigm shift, the automatic workflow will remain, there will be just some new options for more control and flexibility.

[Patman]

Hello patman,

I tested it too, the delay issue is fixed, since the bug was fatal I made a small release:

StaxRip x64 1.3.1.4 beta (2015-05-31)


Added feature to choose which source filter to use when a single file is opened, this gives more MeGUI manual workflow like control without giving up much of StaxRip's automated character
Fixed failing to show log file from main menu
Updated qaac to 2.49
Updated ffms2 to 2.22 RC2


http://github.com/stax76/staxrip/releases

I've a better understanding of NTSC now and some ideas how to make it easier to deal with. Also I've been thinking about more control and manual workflow for a very very long time now and implemented a first feature today, what will follow is a demuxing dialog for mkv/mp4 and maybe more formats similar to the eac3to dialog, this way demuxing might be skipped without modifying the settings, this is useful for instance if the file was previously opened and demuxed. It' not gonna be a paradigm shift, the automatic workflow will remain, there will be just some new options for more control and flexibility.

Hi Stax,

:thanks: so much for your continuous work on StaxRip x64 but a break looks different :D

[jkilez]

Another bug: The "Options->Misc->Auto Forced Film Threshold (Percent)" is not being honored. MPEG-2 (DVD) sources with a DGIndex "Video Type" of between 95% and 99% Film are listed with a frame rate of 29.97 when they should be 23.976. The same sources work properly in 1.1.9.0.

StaxRip x86 modifies the d2v file for this. With DGDecode x64 there are problems on Win10, on Win7 probably too so it's not used until somebody fixes it.

Both ffms2 and L-Smash-Works have a parameter dealing with NTSC, I can add the parameter to the filter profiles but I don't know yet if it can be automated to set the parameter. I admit I'm pretty clueless about NTSC so how well NTSC is supported depends much on the quality of the feedback I get for it.
A more significant problem is that even if I force it to use the proper frame rate, it does not count frames properly causing an A/V sync issue. When comparing a 1.3.1.3 encode against a 1.1.9.0 encode, sometimes the 1.3.1.3 is a couple frames ahead and sometimes it is a couple frames behind. The 1.1.9.0 encode stays in A/V sync throughout.
1.1.9.0 used DGDecode which doesn't really work on x64, there are various other source filters, unfortunately I don't have NTSC experience but I've test material I want to experiment with.

It looks like adding "rffmode = 2" to the FFVideoSource options achieves the same as "Force Film" in DGIndex. I just did a comparison with a new encode--setting "rffmode = 2" gave the same results as the 1.1.9.0 index for a 99% film source.

Problem solved!

[jkilez]

avconv has the same issue as FFmpeg. VirtualDub x64 v1.10.4 (http://sourceforge.net/projects/virtualdub/files/virtualdub-win/1.10.4.35491/VirtualDub-1.10.4-AMD64.zip/download) with FccHandler's AC3 plug-in v1.9 (http://sourceforge.net/projects/fcchandler/files/Virtualdub%20Ac3%20plugin/) appears to work. The distribution size for the combo is less than 3MB compressed. As far as I can tell, VeeDub64 cannot mux from the command line as it still requires an external script file. The syntax is virtually identical to that of VirtualdubMod.

I will do some more testing with VeeDub64, if there is a possibility it will be incorporated into a release. If you have no real interest in it, I am content to stick with my current workaround.
It turns out you can mux with vdub64 without using an external file. As long as your script is short enough, you can just cram it on the command line after the "/cmd" option.

So far, everything looks good with vdub64. Here is an updated muxing "hack" that can be added to the end of the Xvid encoding section:
set VD=<PATH TO VDUB64.EXE>
set track1=%encoder_out_file_track1%
if "%track1:~-3%"=="mp3" ( set atype=DAAAAE1QM08AAAAA ) else ( set atype=0 )
set txt=VirtualDub.Open('%encoder_out_file%','',0);
set txt=%txt% VirtualDub.audio.SetSource('%track1%', '', '%atype%');
set txt=%txt% VirtualDub.video.SetMode(0);
set txt=%txt% VirtualDub.audio.SetMode(0);
set txt=%txt% VirtualDub.audio.SetInterleave(1,500,1,0,%delay1%);
set txt=%txt% VirtualDub.SaveAVI('%target_dir%\%target_name%.VD%encoder_ext%');
set txt=%txt:\\=\\\\%
"%VD%" /cmd "%txt%" && copy "%track1%" "%encoder_out_file%"

[stax76]

It looks like adding "rffmode = 2" to the FFVideoSource options achieves the same as "Force Film" in DGIndex. I just did a comparison with a new encode--setting "rffmode = 2" gave the same results as the 1.1.9.0 index for a 99% film source.

Problem solved!

I played around with NTSC and that was one of the things I found out, I'm not sure if and how I can auto detect what setting to use but I plan making editing much easier: StaxRip will know about various important filter parameters so if the user right-clicks FFVideoSource the menu will show the options 'Enable Force Film' and 'Honor Pulldown Flags' or if the user right-clicks DGDource there will be the options 'Enable hardware deinterlacing' and 'Enable hardware cropping'. This and a few other things are planed for AviSynth editing.

It turns out you can mux with vdub64 without using an external file. As long as your script is short enough, you can just cram it on the command line after the "/cmd" option.

So far, everything looks good with vdub64. Here is an updated muxing "hack" that can be added to the end of the Xvid encoding section:
set VD=<PATH TO VDUB64.EXE>
set track1=%encoder_out_file_track1%
if "%track1:~-3%"=="mp3" ( set atype=DAAAAE1QM08AAAAA ) else ( set atype=0 )
set txt=VirtualDub.Open('%encoder_out_file%','',0);
set txt=%txt% VirtualDub.audio.SetSource('%track1%', '', '%atype%');
set txt=%txt% VirtualDub.video.SetMode(0);
set txt=%txt% VirtualDub.audio.SetMode(0);
set txt=%txt% VirtualDub.audio.SetInterleave(1,500,1,0,%delay1%);
set txt=%txt% VirtualDub.SaveAVI('%target_dir%\%target_name%.VD%encoder_ext%');
set txt=%txt:\\=\\\\%
"%VD%" /cmd "%txt%" && copy "%track1%" "%encoder_out_file%"

Interesting script, I've updated and committed the command line muxer, it's now batch based too like audio and video batch encoding.

If you like you can create a .NET sample application implementing the VirtualDub script generation, making a muxer would then be easier for me, C# would be fine too, SharpDevelop 4.4 has a extremely cool code translator.

edit:

Hi Stax,

:thanks: so much for your continuous work on StaxRip x64 but a break looks different :D


You are welcome, too much rain I guess. :)

[ShamisOMally]

FYI: This is near useless to use if you are doing batch encodes with two audio tracks, and want to select one

Its fine if you just need to do one file, as you can manually select the audio track, but if there's more than one file being processed it automatically forces you to use the first track and there is no way to select the second one.

There should be a drop down option under audio to be able to select a second track without having any text in the "Audio" area

*EDIT* annnnnnnd now its working after I let it do two files. The hell?

*EDIT2* Nope. Even if I right click and select other track its still making me use track 1 in a file batch

[stax76]

FYI: This is near useless to use if you are doing batch encodes with two audio tracks, and want to select one

What would the criteria be to decide which track to use?

[NikosD]

The new HandBrake will have AMD's VCE support for HW transcoding, for those interested.

http://arstechnica.com/information-technology/2015/06/sixth-time-lucky-amd-details-the-carrizo-apu/1/

[JohnAStebbins]

The new HandBrake will have AMD's VCE support for HW transcoding, for those interested.

That's news to me. Where did you hear this?

[NikosD]

That's why I posted the link above :)


AMD's in-house benchmarks show that Carrizo can transcode a 10Mbps 1080p H.264 file down to 5Mbps at around 162 FPS, versus just over 140 FPS for a Core i5-5200U, one of Intel's latest mobile Broadwell processors. This does, however, rely on a version of the popular video encoding application Handbrake that isn't actually out yet: AMD's tests were done using a beta version of Handbrake that's able to directly tap into AMD's Video Coding Engine (VCE) hardware, but the company doesn't know when it will actually be publicly released. Not to mention that older Kaveri systems would probably see the same uplift in performance, given they feature VCE hardware too.

[Dogspoin]

I'm using onlinetvrecorder.com to record and download movies from TV, some movies are offered in HD (1080p50, every frame just doubled). With Staxrip up to Version 1.1.9.0 I could activate the filter ChangeFPS(25) to delete every second frame, make some cuts and the resulting audio matched perfectly.
Now I'm using 1.3.1.4 beta and the resulting audio is only half as long as it should be. Would be great if this behaviour could be changed like it was before.
EDIT: tried with SelectEven(), same error.

[stax76]

I don't know what's wrong with audio, with 50p every second frame doubled, I'm not sure if SelectEven/SelectOdd or ChangeFPS is the best option if there even is a difference. If you cut and change the frame rate afterwards you must change the frame rate after the trim functions and not before.

[Dogspoin]

I changed the order for frame rate change and cutting but the audio track is still only half as long it should be.

I attached two images, as you can see the order is identical, 1.1.9.0 produces audio track as expected but 1.3.1.4 beta not.

[JohnAStebbins]

That's why I posted the link above :)
I didn't read to the second page, so I missed the HandBrake quote.

Once again, someone at AMD is operating in a vacuum. No patches for this have been socialized. Current HandBrake svn has none of this.

Not only is this really bad form to announce HandBrake support before discussing it with the HandBrake developers. But it also makes it impossible to independently validate any of their claims.

And if their patch resembles what they have delivered in the past, It *will not* get merged into HandBrake. We already have some really awful code for OpenCL scaling, DXVA decode, and QSV encode that is all substandard that must be fixed before we add more crap on top of crap.

[NikosD]

We already have some really awful code for OpenCL scaling, DXVA decode, and QSV encode that is all substandard that must be fixed before we add more crap on top of crap.

I agree with most you wrote, but one.

QSV encode is substandard and awful code ?

It's the first time I hear this, given that the code produced by a collaboration of Intel and Handbrake devs.

Are you sure about that ?

It's a little off - topic because we are posting at StaxRip's thread, but you really surprised me.

[stax76]

I changed the order for frame rate change and cutting but the audio track is still only half as long it should be.

I attached two images, as you can see the order is identical, 1.1.9.0 produces audio track as expected but 1.3.1.4 beta not.

Please mail me the log file, my email address can be found in the main menu, you can also post it to pastebin with auto expire enabled. For images you can use email, a image hoster or a cloud drive.

[JohnAStebbins]

I agree with most you wrote, but one.

QSV encode is substandard and awful code ?

It's the first time I hear this, given that the code produced by a collaboration of Intel and Handbrake devs.

Are you sure about that ?

It's a little off - topic because we are posting at StaxRip's thread, but you really surprised me.
Right, we should take this elsewhere (like HandBrake forums) if it continues.

There are many things I am not happy about with the QSV code in HandBrake. But it's my own fault for not taking the time to review it properly when it was introduced. At the time, I was busy with other things and just couldn't be bothered.

[stax76]

@Dogspoin

You are the second reporting the exact same problem, I'll think about how it can be improved, unfortunately it's a bit tricky, I believe these two methods will currently work:

1. change frame rate within the source filter section before you cut with the preview.

2. change frame rate after the cutting filter section after you cut with the preview.

[stax76]

@Dogspoin

Next version captures the frame rate and frame count that was used in the preview for cutting and uses this values for the blank script used for mkvmerge cutting. It should not matter where and how the frame rate was changed and StaxRip will detect when it was changed after cutting was performed and will show a assistant message:

The frame rate was changed after cutting was performed, please ensure that this change is happening after the Cutting filter section in the AviSynth script.

I hope it will solve the entire problematic, I'm not sure about crazy NTSC but hope it will be mostly fine.

[Dogspoin]

Great, both methods solved the problem.
Looking forward to next version. :)

@Dogspoin

You are the second reporting the exact same problem, I'll think about how it can be improved, unfortunately it's a bit tricky, I believe these two methods will currently work:

1. change frame rate within the source filter section before you cut with the preview.

2. change frame rate after the cutting filter section after you cut with the preview.

[ShamisOMally]

Having a bunch of problems here with batch encodes

If you set up the profile for encoding before you import, or even after you select the files, whatever you selected for Variable/average bitrate is discarded, and it sets some ungodly high number like 2982929 for it

If you do it one file at a time, it keeps the VBR setting you used, but any more than one file and it goes nuts

Also if you want my suggestion in the GUI with the audio track problem do what mediacoder does, have a drop down option and allow you to pick track 1 or track 2 before you start encodes, and then it will always take track 1 or track 2 etc depending on what you picked.

For some reason thet "Prefer english" option is not working, it just grabs the first audio track every time.

[stax76]

If you set up the profile for encoding before you import, or even after you select the files, whatever you selected for Variable/average bitrate is discarded, and it sets some ungodly high number like 2982929 for it

This looks like the same topic discussed a few days ago here:

http://forum.videohelp.com/threads/369913-StaxRip-x64-based-on-AviSynth-x64?p=2393151&viewfull=1#post2393151

Also if you want my suggestion in the GUI with the audio track problem do what mediacoder does, have a drop down option and allow you to pick track 1 or track 2 before you start encodes, and then it will always take track 1 or track 2 etc depending on what you picked.

This is currently not supported and I'm not gonna think about it unless somebody describes a very detailed scenario why it would be worthwhile. This looks like being incompatible with StaxRip's way of doing things and in any case would be huge amount of work with doubtful benefit.

If you describe your scenario in detail I might be able to help you, picking up tracks by language works. Please tell us the complete story starting what the source media is looking like in detail and how the source media was created.

[Jeroi]

Stax does the ripper be capable to do recursive encoding already? And organise the file structure like the original folder structure?

Edit seams not.

And I report again the batch encoder don't remember bitrate level fro encoder. I try to use --bitrate 900 in 2 pass mode but encoder keeps outputting 12000 bitrates and huge files. Please fix the 2 pass encoding mode.

To the audio encoding I would like check boxes that reads encode or allow or similar to prevent multiple audio track appearing in mp4 encodes. Currently it encodes always 2 tracks weather you want or not.

[stax76]

Stax does the ripper be capable to do recursive encoding already? And organise the file structure like the original folder structure?

There isn't direct support yet but the dialog for adding files for batch encoding supports drag and drop. It's possible to use windows explorer search to find all files including files in all sub-directories, the search result can then easily be added for batch processing via drag and drop.

And organise the file structure like the original folder structure?

I'm not sure what you mean.

[NikosD]

I tried using MP4 container with DTS and DTS-HD audio stream, but StaxRip didn't allow it.

I had to convert it to a different format in order to continue processing.

[stax76]

I can enable it if somebody confirms that MP4Box can mux it.

[jones1913]

In the past DTS audio was not supported by mp4box, I dont know if this has changed meanwhile.

L-Smash (https://github.com/l-smash/l-smash) muxer has support for DTS in mp4.

[stax76]

Here is a small guide on how to use StaxRip's MediaInfo GUI in windows explorer. Customizing the context menu of windows explorer can be done with the registry but there are some disadvantages and limitations. It's also possible with a shell extension and this is what I prefer. There is a generic shell extension called Open++ described here:

http://www.guidingtech.com/1363/add-items-customize-right-click-menu

and there is a Open++ alternative that can be downloaded here:

http://www.mediafire.com/download/9gna9modyj1sbvq/StaxExplorerMenu.7z

I've built it myself but never released it even though it wasn't simple to build, source code is included.

My configuration looks like so:

http://oi60.tinypic.com/2uzcd3p.jpg

The file types use macros which are defined in the options like so:

%video% = mpg avi ts vob mp4 d2v divx mkv avs 264 mov wmv part m2ts flv ifo h264 asf webm dgi m2ts mpeg mpv y4m avc hevc 265 h265 m2v mts
%audio% = mp2 mp3 ac3 wav m4a dts dtsma dtshr dtshd eac3 thd thd+ac3 ogg mka aac opus flac
%subtitle% = sub sup idx ass aas srt

The GUI has menu options to register and unregister the shell extension, it's a normal COM+ component so it simply calls regsvr32 with admin privileges. The shell extension is native/unmanaged and the GUI is a separate process so at no time the .NET CLR is loaded into explorer process space, I choose this design for memory efficiency.

I don't remember having tried Open++ but from the screenshot it don't seem to support top level menu which my extension does, it does however not support icons and dynamic arguments which does not really interest me.

Screenshot how my menu looks like (I struggled too many Win10 bugs so I'm back on Win7...):

http://oi60.tinypic.com/2zr14qp.jpg

I don't know what other MediaInfo GUIs exist, StaxRip offers a tab for every stream and it has a filter function:

http://oi60.tinypic.com/2l9oabl.jpg

Here is another related tool of mine, locally I have a slightly improved version, I use this mainly to easily clean up my menu, I hate it when applications trash it:

http://www.stax76.bplaced.net/index.php?slab=filetyperegistryviewer

http://www.stax76.bplaced.net/files/applications/FileTypeRegistryViewer/FileTypeRegistryViewer.png

Also useful sometimes the MediaInfo folder view found in StaxRip's advanced menu. It features a context menu with various options. I plan to add user defined custom columns and make it optionally recursive to include sub-folders and to add a filter feature to find any property including properties not shown.

http://oi58.tinypic.com/282nci8.jpg

[SeeMoreDigital]

In the past DTS audio was not supported by mp4box, I dont know if this has changed meanwhile.

L-Smash (https://github.com/l-smash/l-smash) muxer has support for DTS in mp4.Word to the wise...

Although it's possible to place DTS audio within the .mp4 container, it can only be done as a 'private stream', as it's not officially supported by the standard ISO/IEC 14496 MPEG-4 standard.

Which means there's no obligation for hardware playback devices to support it!


Cheers

[Kurtnoise]

Hi SMD,

Word to the wise...

Although it's possible to place DTS audio within the .mp4 container, it can only be done as a 'private stream', as it's not officially supported by the standard ISO/IEC 14496 MPEG-4 standard.

Which means there's no obligation for hardware playback devices to support it!

It's time to update your skills...;) This has been officially supported since 2011 according to the specs (http://www.etsi.org/deliver/etsi_TS/102100_102199/102114/01.03.01_60/ts_102114v010301p.pdf). Thats why it's implemented in l-smash tools.


And I confirm, DTS is not supported yet by the GPAC tools...

[SeeMoreDigital]

Hi SMD,


It's time to update your skills...;) This has been officially supported since 2011 according to the specs (http://www.etsi.org/deliver/etsi_TS/102100_102199/102114/01.03.01_60/ts_102114v010301p.pdf). Thats why it's implemented in l-smash tools.Oh wow, my profuse apologies... How did I miss this? What was I doing in August 2011?

Does anyone have any conformant samples I can test with my hardware playback devices. A channel check sample would be nice?

Cheers

[NikosD]

Also useful sometimes the MediaInfo folder view found in StaxRip's advanced menu. It features a context menu with various options. I plan to add user defined custom columns and make it optionally recursive to include sub-folders and to add a filter feature to find any property including properties not shown.



I've been looking for those features of MediaInfo folder view.
The ability to include sub-folders and the addition of interlaced property and scan type.

A user defined column and a filter to find properties are very useful.

[ShamisOMally]

Stax does the ripper be capable to do recursive encoding already? And organise the file structure like the original folder structure?

Edit seams not.

And I report again the batch encoder don't remember bitrate level fro encoder. I try to use --bitrate 900 in 2 pass mode but encoder keeps outputting 12000 bitrates and huge files. Please fix the 2 pass encoding mode.

To the audio encoding I would like check boxes that reads encode or allow or similar to prevent multiple audio track appearing in mp4 encodes. Currently it encodes always 2 tracks weather you want or not.

Ditto, I am getting this as well. Makes doing batch encodes impossible

[stax76]

Stax does the ripper be capable to do recursive encoding already?

Yes, in the next release.

And I report again the batch encoder don't remember bitrate level fro encoder. I try to use --bitrate 900 in 2 pass mode but encoder keeps outputting 12000 bitrates and huge files.

I'll investigate it.

Currently it encodes always 2 tracks weather you want or not.

There is a audio profile called 'No Audio'.

[tamasnemeti]

Hello, I am new to this forum and I am not a power user or an encoding enthusiast. I am trying to save space by converting stuff to HEVC and cutting down audio quality in some cases as well.

So far everything is working perfect, only had one problem yet (still have it).

Basically I have an episode of Archer on my hand, with two audio streams. If I want to reencode the streams to a lower bitrate (did not test higher) then StaxRip uses the raw output (? not sure here) which is around 4500kpbs. I don't see why it would do that, but it definitely does. It also includes a PGS sub which does not seem to be supported (?), but I can do without it and remove it. They might be in connection(?). Just muxing the audio does what it is designed to.
Here is two pictures:
https://p1.picsto.re/4bt5d.png
https://p1.picsto.re/pUgrD.png

On all other movies/series it works just fine...am I missing something?

I have a second question about batch encoding. I understand I can modify the container to include two subs (manually browsing the additional ones) for single encodes, but is it possible to include them automatically when doing a batch? Lets say, from the temp folders?

[stax76]

Hello and welcome,

I guess it's a bug in ffmpeg, please mail me the log file.

It also includes a PGS sub which does not seem to be supported.

You mean not supported by MP4 or your playback device/software?

I have a second question about batch encoding. I understand I can modify the container to include two subs (manually browsing the additional ones) for single encodes, but is it possible to include them automatically when doing a batch? Lets say, from the temp folders?

It's supposed to add subtitles automatically so it could either be a configuration problem or a bug. The routine that adds the subtitles is identical in normal and batch mode. In the options under subtitles the languages to add can be configured, the default is English and your local system language. There is also a convert option which might help with the problem PGS being not supported. It makes a difference if subtitle demuxing is enabled which is the default, next version will have a new GUI for audio and subtitle demuxing.

[tamasnemeti]

Thank you for the prompt reply!

This is what I get when trying to encode while a sub with .sup extension is included during the process.
Checking the "Convert Sup (PGS/Blu-ray) to Sub (IDX/DVD)" box did not make a difference either.
https://p1.picsto.re/g1NKZ.png

About the subtitles: thank you for enlightening me, it works just fine now!

You can find a log attached (includes the .sup error and the high bitrate stream 'bug' as well). Let me know if this isn't the log you are looking for...

Edit.: It seems to note that
Writing the destination file failed.
Aborted at file position ******.

I am running the application as Admin.

[stax76]

It can take a while until attachments get approved so I recommend to use mail or pastebin. Regarding PGS support in mkvmerge, I believe mkvmerge will mux PGS ripped with MakeMKV or eac3to, I don't know what could be the problem, you have to convert the subtitles somehow, I also don't know why StaxRip's sup to sub routine failed here, I can test if the routine works when I see the log file. You absolutely don't need to run StaxRip or any included application as admin.

[NikosD]

StaxRip complains about MKVmerge with this file, but MKVmerge works fine as Mosu said in his thread:

http://forum.doom9.org/showthread.php?p=1726889#post1726889

The file is this:
http://www.filedropper.com/1latraviata

The complain is this:

mkvmerge v7.9.0 ('Birds') 64bit
Error: The file 'D:\Video\Test Audio Video\Video HD test\1080i\H.264\1.La Traviata temp files\1.La Traviata ID3 English.sup' has unknown type. Please have a look at the supported file types ('mkvmerge --list-types') and contact the author Moritz Bunkus <moritz@bunkus.org> if your file type is supported but not recognized properly.

------------------------------------------------------------
Error Muxing using mkvmerge
------------------------------------------------------------

Muxing using mkvmerge failed with exit code 2

mkvmerge v7.9.0 ('Birds') 64bit
Error: The file 'D:\Video\Test Audio Video\Video HD test\1080i\H.264\1.La Traviata temp files\1.La Traviata ID3 English.sup' has unknown type. Please have a look at the supported file types ('mkvmerge --list-types') and contact the author Moritz Bunkus <moritz@bunkus.org> if your file type is supported but not recognized properly.

[sneaker_ger]

No lines = 0 byte extracted file = cannot be detected as sup

[stax76]

Adding messages would be difficult since adding subtitles can happen from different locations and in different modes so I just changed it to silently ignore 0 byte subtitles.

edit:

When there are no normal subtitle files StaxRip checks mkv and mp4 for subtitles and adds mkv and mp4 as subtitle source, this will result in mkvmerge adding the empty subtitle without error code, I can't do much here.

[tamasnemeti]

It can take a while until attachments get approved so I recommend to use mail or pastebin. Regarding PGS support in mkvmerge, I believe mkvmerge will mux PGS ripped with MakeMKV or eac3to, I don't know what could be the problem, you have to convert the subtitles somehow, I also don't know why StaxRip's sup to sub routine failed here, I can test if the routine works when I see the log file. You absolutely don't need to run StaxRip or any included application as admin.

Here it is.
http://pastebin.com/7nzJU7RK

[stax76]

It's unclear why eac3to don't transcode from DTS to AC3, maybe it works with the latest StaxRip version. I'm not sure but the default processing method for this type of operation might have changed using ffmpeg instead of eac3to, you can also force to use ffmpeg, there is a option for this in the audio dialog but you should use the latest StaxRip version.

[Patman]

Here it is.
http://pastebin.com/7nzJU7RK
Hi tamasnemeti,

I saw that you use arcsoft decoder with eac3to. Which version do you use? The newer ones make some problems.

[stax76]

the bulk of the work of VapourSynth integration is done, the biggest problem is distribution of everything needed which is VapourSynth, Python and plugins to run QTGMC. There are few options:


make one big package and integrate everything
make one big installer with install options
provide download links and setup instructions for AviSynth+, VapourSynth, Python, plugin bundles, etc. Some people might have problems to follow download and install instructions and some people might use outdated components which might fail to work, this is more experience rather than being overly pessimistic

[luigizaninoni]

provide download links and setup instructions for AviSynth+, VapourSynth, Python, plugin bundles, etc.
[/LIST]

I must be missing something: why would you want to install both Avisynth+ AND Vapoursynth ?

[stax76]

Some things are currently not working at all with AviSynth+ x64, QTGMC is practically unusable even in single threaded mode, some goes for other complex scripts and plugins. In VapourSynth x64 QTGMC and various other things work just fine. VapourSynth development is very active while there isn't much if any visible AviSynth+ development. Python is more difficult than AviSynth but also more powerful and extremely popular especially for people with Linux background, in StaxRip it's not making a big difference because most things can be done with the GUI, it's possible to switch between scripting engines even if files are already loaded, not even the index must be recreated, profiles and menus are completely separated, so when VapourSynth is used nothing AviSynth related is visible.

[luigizaninoni]

I see, I like the idea of being able to switch between the two engines.

I have no experience with Vapoursynth, and it seems to me that it is still lacking some avs plugins and scripts that I occasionally use (smoothadjust, MCTD et al.).
However, given that, as you say, it is in very active development, I am willing to try, they might fill the gaps in a relatively short time.

From my point of view solution n.1 (or maybe n. 2) would be the easiest. In my opinion it ought to be the best also for the general public: I think that a noob would be more scared by the idea of downloading and installing programs, plugins, bundles etc. rather than by the mere size of a single download. ymmv, of course.

[stax76]

The downside of 1. and 2. is a download size of 100-150 MB and disc space up to 400 MB which is somehow insane. :)

StaxRip itself is very efficient in regard of file size I believe, it should be around 50 000 lines code resulting in 1,3 MB executable, it has a lot more features than many applications at comparable size.

What also could be done is a dynamic dialog that analyses the environment and list everything missing, outdated or damaged, it would have descriptions and instructions and download links.

[tamasnemeti]

Hi tamasnemeti,

I saw that you use arcsoft decoder with eac3to. Which version do you use? The newer ones make some problems.

I am not quite sure how to downgrade it to be honest.
Also, forcing ffmpeg has no effect on it whatsoever.

If I just mux the audio that is working fine, but the DTS audio eats up 220 megs of space, where the video stream is around 180-200 per episode. AC3 448kbps would be around 70 megs, which is a nice improvement and the quality would be good enough for me. You see, the size difference would be around 10-15 gigs for the whole series which is not negligible for me.

Not sure what to do..

[stax76]

Please remux to a 50 MB file using mmg or mkmerge-gui and retry re-encoding with the latest StaxRip release 1.3.1.4, if the problem persists then please upload the 50 MB file to dropbox or somewhere else and send me the link as private message.

[Lupissimo]

As can be seen by the attached logs, the latest version 1.3.1.4 changes the fps from 23.976 to 25fps, whereas the 1.2.2.2 version encodes correctly:

[Patman]

I am not quite sure how to downgrade it to be honest.
Also, forcing ffmpeg has no effect on it whatsoever.

If I just mux the audio that is working fine, but the DTS audio eats up 220 megs of space, where the video stream is around 180-200 per episode. AC3 448kbps would be around 70 megs, which is a nice improvement and the quality would be good enough for me. You see, the size difference would be around 10-15 gigs for the whole series which is not negligible for me.

Not sure what to do..

Hi,

use command eac3to.exe -test and you will see which version is installed. ArcSoft version 1.1.0.0 works fine. If you want you can send me a link as private message and i will test to encode the audio file.


As can be seen by the attached logs, the latest version 1.3.1.4 changes the fps from 23.976 to 25fps, whereas the 1.2.2.2 version encodes correctly:

Hi,

i can't open attached files, please use pastebin.

[stax76]

first alpha/tech preview adding full first class VapourSynth support. I'm not aware of broke or missing things but quite a bit code was changed or added...


New: Added full first class VapourSynth support including plugins and profile for QTGMC
New: Added possibility to switch dynamically between any source filter back and forth including DGSource and DGSourceIM. Indexing is triggered automatically in case no index file is present
New: Added vinverse plugin to remove residual combing from NTSC
New: Added GUI for demuxing MKV and MP4
New: Added feature to easily enable certain parameters for certain filters in the AviSynth editor. Currently supported are FFVideoSource and DGSource, more parameters and filters might be supported on request. Use it by right-clicking on FFVideoSource or DGSource in the AviSynth editor, the menu shows then NTSC options and hardware cropping and resizing options.
New: Added Play option for MPC playback in the AviSynth editor
New: Added two new options in the dialog to define files for batch processing to add a entire folder and a entire folder including sub-folders
New: Added new subtitle UI based on data view
New: Added option to generate subtitle names based on the subtitle language
Fix: Disabled audio demuxing for MKV and MP4 by DGIndexNV and DGIndexIM because it's already demuxed by MP4Box and mkvextract
Fix: Tools/Directories/Plugins wasn't pointing to the AviSynth+ plugin directory
Update: QSVEncC 2.0 beta 7
Update: x265 1.7+207
Tweak: DTS bitrate is now unrestricted
Tweak: Moved field processing filters to dedicated category like before in StaxRip x86
Tweak: Replaced LinkLabels with Buttons in eac3to dialog
Tweak: The help for all included AviSynth plugins can now be accessed per menu in the AviSynth editor
Tweak: ProjectX is enabled by default in case Java exists, otherwise dsmux will handle MPEG-2 TS
Tweak: In the dialog to define files for batch processing the 'Create Jobs' option was renamed to 'Demux and index before adding jobs', regardless of if this option is enabled jobs are always created
Tweak: Removed x86 and VS C++ 2013 from AviSynth+ installer bringing it from 18 MB down to 4 MB. Very often VS C++ 2013 is already installed and in case it ain't already installed StaxRip will show the Apps dialog which has a download button for VS C++ 2013.
Tweak: replaced avs4x26x with ffmpeg


http://thumbnails108.imagebam.com/41765/adee8a417643493.jpg (http://www.imagebam.com/image/adee8a417643493) http://thumbnails105.imagebam.com/41765/f4d9a1417643496.jpg (http://www.imagebam.com/image/f4d9a1417643496) http://thumbnails108.imagebam.com/41765/c7cf22417643498.jpg (http://www.imagebam.com/image/c7cf22417643498) http://thumbnails108.imagebam.com/41765/f5d8ed417643500.jpg (http://www.imagebam.com/image/f5d8ed417643500) http://thumbnails105.imagebam.com/41765/3415cd417643501.jpg (http://www.imagebam.com/image/3415cd417643501) http://thumbnails108.imagebam.com/41765/f9b9bb417643505.jpg (http://www.imagebam.com/image/f9b9bb417643505) http://thumbnails108.imagebam.com/41765/dc720a417643508.jpg (http://www.imagebam.com/image/dc720a417643508) http://thumbnails105.imagebam.com/41765/c5a7b0417643509.jpg (http://www.imagebam.com/image/c5a7b0417643509)

http://www.mediafire.com/download/2fsqchz4juse7m2/StaxRip_x64_tech_preview.7z

[Lupissimo]

@patman: https://www.dropbox.com/s/h2nzff8y1fbdcly/Logs.zip?dl=0

[stax76]

@Lupissimo

What the latest release does is it demuxes VOB with DGIndex to m2v, this is a pretty bad idea, the latest alpha shows a message box every time a user opens VOB stating clearly that it has many disadvantages over ripping with MakeMKV, there are some alternative methods to MakeMKV involving tools like AnyDVD, DVD Shrink, DVDSubEdit, ProjectX, BDSup2Sub++, it can be absolutely done and works even with DVD structures that have problematic timestamps, it's just MakeMKV is much more convenient. What the old StaxRip did different with the fps is using MediaInfo to detect it but this causes issues with other sources so I can't do anything here. Also StaxRip x86 was using DGDecode for DVDs which is not available for x64, ffms2 works just as well and I added a new feature for changing FFVideoSource and DGSource parameters dealing with NTSC conveniently with the context menu in the new scripting editor, it can be seen in one of the screenshots and it can be expanded for other filters on request. It's not clear if DGIndex or ffms2 causes the fps problem, if you really want to process this way you can try another source filter or manually add AssumeFPS to the script. For properly processing VOB automatically I would basically have to write a demuxing tool which currently don't exist in order to successfully handle DVD structures with problematic timestamps. Pretty much all tools don't handle this properly with few exceptions like Handbrake and VidCoder which I believe do also handle other issues properly like erroneous TS files so I think the Handbrake engine is fairly good.

[burfadel]

The new Staxrip doesn't encode to x265 properly.

This is using the default settings for x264 and x265. Also, no filters, resize, cropping etc apart from deinterlacing (did this for the filters and encoder to isolate the issue):
X264: https://www.dropbox.com/s/wf35tsn15286y4b/NewStax-x264.mkv?dl=0
x265: https://www.dropbox.com/s/0id29obdafxyh8p/NewStax-x265.mkv?dl=0

Of course, it makes sense it is related to the piping from ffmpeg to x265, since x264 does not have the piping. It worked fine in the latest non-tech preview Staxrip.

[burfadel]

@Stax
Oh wait! I found the solution :)

You need to add:
--y4m

to the x265 command line in the tech preview. Problem solved!

Also, very importantly, for x265 rev 211 onwards (not 207 as in the tech preview), you need to add:
--output-depth 10
http://x265.readthedocs.org/en/latest/cli.html#cmdoption--output-depth
for 10-bit output, otherwise it will default to 8 bit output. So, an option needs to be added.

Also, there is a recently new option:
--limit-refs
http://x265.readthedocs.org/en/latest/cli.html#cmdoption--limit-refs

[stax76]

@burfadel

I was hoping replacing avs4x26x with ffmpeg would be fine, I've seen this effect before with piping but am rather clueless what it is and how it can be fixed other then reverting to avs4x26x, does anybody know what's happening here?

VapourSynth has a own piping tool, maybe you want to try VapourSynth, it has great potential as far as I can tell, everything I tried just worked wonderfully, I definitively want to add more plugins for both AviSynth+ and VapourSynth, as long as the download is below 100 MB it's no problem I guess, currently it's "only" 60 MB.

[stax76]

@Stax
Oh wait! I found the solution :)

You need to add:
--y4m

to the x265 command line in the tech preview. Problem solved!

Also, very importantly, for x265 rev 211 onwards (not 207 as in the tech preview), you need to add:
--output-depth 10
http://x265.readthedocs.org/en/latest/cli.html#cmdoption--output-depth
for 10-bit output, otherwise it will default to 8 bit output. So, an option needs to be added.

Also, there is a recently new option:
--limit-refs
http://x265.readthedocs.org/en/latest/cli.html#cmdoption--limit-refs

OK, thanks

[burfadel]

I also notice in the default filter list, you have crop listed before 'Field' (deinterlacing). Shouldn't deinterlacing be done before cropping?

[stax76]

I also notice in the default filter list, you have crop listed before 'Field' (deinterlacing). Shouldn't deinterlacing be done before cropping?

I'm not sure, for mod 2 it's probably a problem depending on used filters but for mod 16 it's faster to crop first when you use a slow deinterlacer like QTGMC, I always crop with mod 16 and never resize.

[burfadel]

I'm not sure, for mod 2 it's probably a problem depending on used filters but for mod 16 it's faster to crop first when you use a slow deinterlacer like QTGMC, I always crop with mod 16 and never resize.

Ah ok! Come to think of it, since it's cutting by mod 16 etc it would be better to crop first :).

I notice in the tech preview that abort doesn't work with x265 either. I guess it was pointing to the old pipe method? If you pause and abort ffmpeg, it pauses and aborts x265 cleanly :).

[Jeroi]

Looks promising, thank you for recursive encoding, does the encoding support orginal filestructure at final folder ie: original/folder/*.avi -> final/folder/*.avi and original/*avi -> final/*.avi?

One thing about the batch prosessing tho: Could you add obtion to not index the files when adding batch? It freeses currently the computer for couple mins while adding 300 video files... Better aproach could be index files when encoding not when doing template setups for encoding. Batch could use one template and when encoding started it iterates the files againts template and does the job. One approach could be separate batch job window, where you can select template and you import only filepath hiearachy to the rows and then setup output folder and click do jobs.

[stax76]

I notice in the tech preview that abort doesn't work with x265 either. I guess it was pointing to the old pipe method? If you pause and abort ffmpeg, it pauses and aborts x265 cleanly :).

the abort code is from jkilez or at least partly and I have only a raw idea what it does, it worked always for me so far, I'll investigate it.

[burfadel]

Looks promising, thank you for recursive encoding, does the encoding support orginal filestructure at final folder ie: original/folder/*.avi -> final/folder/*.avi and original/*avi -> final/*.avi?

One thing about the batch prosessing tho: Could you add obtion to not index the files when adding batch? It freeses currently the computer for couple mins while adding 300 video files... Better aproach could be index files when encoding not when doing template setups for encoding. Batch could use one template and when encoding started it iterates the files againts template and does the job. One approach could be separate batch job window, where you can select template and you import only filepath hiearachy to the rows and then setup output folder and click do jobs.

With batch, the indexing only occurs when you start encoding. The pause you experience is because it is creating the project files for 300 videos, as well as creating the temp folders. It isn't instant, and does take a little while, but it shouldn't take a few minutes. A few minutes would suggest heavy fragmentation or something...

[Jeroi]

I report still the batch prosessor bug:

"G:\Ohjelmat\staxrip\Apps\x264\x264.exe" --pass 1 --bitrate 22489 --sar 12:11 --stats "E:\rip_temp\video.stats" --output NUL "E:\rip_temp\video.avs"

------------------------------------------------------------
x264 Second Pass
------------------------------------------------------------

"G:\Ohjelmat\staxrip\Apps\x264\x264.exe" --pass 2 --bitrate 22489 --sar 12:11 --stats "E:\rip_temp\video.stats" --output "E:\rip_temp\video.h264" "E:\rip_temp\video.avs"


Look that huge bitrate that it is using While my template should be bitrate 900.

[stax76]

Looks promising, thank you for recursive encoding, does the encoding support orginal filestructure at final folder ie: original/folder/*.avi -> final/folder/*.avi and original/*avi -> final/*.avi?

The default target dir is the source dir, there is a option to define a identical target dir for all jobs, a particular folder structure isn't supported, StaxRip has some flexible tools like event commands (main menu > Tools > Advanced) but on top of my head I can't say much about something special like this, so far I added all requested events and commands I think but only when I get a clear description what is needed.

One thing about the batch prosessing tho: Could you add obtion to not index the files when adding batch? It freeses currently the computer for couple mins while adding 300 video files... Better aproach could be index files when encoding not when doing template setups for encoding.

well there is a option "Demux and index before creating jobs", the caption and behavior of this check box was changed recently, I'm not sure when the change happened and if it's in the changelog so I suggest to try the alpha.

edit:

I forgot to investigate the bitrate issue, I'll have to go a few posts back to see what else I missed.

[burfadel]

well there is a option "Demux and index before creating jobs", the caption and behavior of this check box was changed recently, I'm not sure when the change happened and if it's in the changelog so I suggest to try the alpha.

I didn't know that :)

For me, it's not indexing when creating batch jobs, only when the job starts. I hadn't changed that.

[luigizaninoni]

encode x265 deblock 0 0 : OK
encode x265 deblock -1 -1 : CRASH

Error x265

x265 failed with exit code 1

C:\Users\luigi.TZMS\Desktop\Video\Staxrip64>"C:\Program Files (x86)\VapourSynth\core64\vspipe.exe" "C:\Users\luigi.TZMS\Desktop\Sipario2 temp files\Sipario2.vpy" - --y4m | "C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Apps\x265\x265.exe" --crf 22 - -Deblock -1: -1 --psy-rd 0.35 --y4m --input-res 720x576 --frames 14963 --fps 25.000000 --sar 16:11 --output "C:\Users\luigi.TZMS\Desktop\Sipario2 temp files\Sipario2_out.hevc" -
Syntax: x265 [options] infile [-o] outfile
infile can be YUV or Y4M
outfile is raw HEVC bitstream
Executable Options:
-h/--help Show this help text and exit
-V/--version Show version info and exit
Output Options:
-o/--output <filename> Bitstream output file name
-D/--output-depth 8|10 Output bit depth (also internal bit depth). Default 10
--log-level <string> Logging level: none error warning info debug full. Default info
--no-progress Disable CLI progress reports
--csv <filename> Comma separated log file, if csv-log-level > 0 frame level statistics, else one line per run
--csv-log-level Level of csv logging, if csv-log-level > 0 frame level statistics, else one line per run: 0-2
Input Options:
--input <filename> Raw YUV or Y4M input file name. `-` for stdin
--fps <float|rational> Source frame rate (float or num/denom), auto-detected if Y4M
--input-res WxH Source picture size [w x h], auto-detected if Y4M
-f/--frames <integer> Maximum number of frames to encode. Default all
--seek <integer> First frame to encode
Quality reporting metrics:
--[no-]ssim Enable reporting SSIM metric scores. Default disabled
--[no-]psnr Enable reporting PSNR metric scores. Default disabled
Profile, Level, Tier:
-P/--profile <string> Enforce an encode profile: main, main10, mainstillpicture
--level-idc <integer|float> Force a minimum required decoder level (as '5.0' or '50')
--[no-]high-tier If a decoder level is specified, this modifier selects High tier of that level
--[no-]allow-non-conformance Allow the encoder to generate profile NONE bitstreams. Default disabled
Threading, performance:
--pools <integer,...> Comma separated thread count per thread pool (pool per NUMA node)
'-' implies no threads on node, '+' implies one thread per core on node
-F/--frame-threads <integer> Number of concurrently encoded frames. 0: auto-determined by core count
--[no-]wpp Enable Wavefront Parallel Processing. Default enabled
--[no-]pmode Parallel mode analysis. Default disabled
--[no-]pme Parallel motion estimation. Default disabled
--[no-]asm <bool|int|string> Override CPU detection. Default: auto
Presets:
-p/--preset <string> Trade off performance for compression efficiency. Default medium
ultrafast, superfast, veryfast, faster, fast, medium, slow, slower, veryslow, or placebo
-t/--tune <string> Tune the settings for a particular type of source or situation:
psnr, ssim, grain, zerolatency, fastdecode
Quad-Tree size and depth:
-s/--ctu <64|32|16> Maximum CU size (WxH). Default 64
--min-cu-size <64|32|16|8> Minimum CU size (WxH). Default 8
--max-tu-size <32|16|8|4> Maximum TU size (WxH). Default 32
--tu-intra-depth <integer> Max TU recursive depth for intra CUs. Default 1
--tu-inter-depth <integer> Max TU recursive depth for inter CUs. Default 1
Analysis:
--rd <0..6> Level of RDO in mode decision 0:least....6:full RDO. Default 3
--[no-]psy-rd <0..2.0> Strength of psycho-visual rate distortion optimization, 0 to disable. Default 0.3
--[no-]rdoq-level <0|1|2> Level of RDO in quantization 0:none, 1:levels, 2:levels & coding groups. Default 0
--[no-]psy-rdoq <0..50.0> Strength of psycho-visual optimization in RDO quantization, 0 to disable. Default 0.0
--[no-]early-skip Enable early SKIP detection. Default disabled
Coding tools:
-w/--[no-]weightp Enable weighted prediction in P slices. Default enabled
--[no-]weightb Enable weighted prediction in B slices. Default disabled
--[no-]cu-lossless Consider lossless mode in CU RDO decisions. Default disabled
--[no-]signhide Hide sign bit of one coeff per TU (rdo). Default enabled
Temporal / motion search options:
--max-merge <1..5> Maximum number of merge candidates. Default 2
--ref <integer> max number of L0 references to be allowed (1 .. 16) Default 3
--limit-refs <0|1|2|3> limit references per depth (1) or CU (2) or both (3). Default 0
--me <string> Motion search method dia hex umh star full. Default 1
-m/--subme <integer> Amount of subpel refinement to perform (0:least .. 7:most). Default 2
--merange <integer> Motion search range. Default 57
--[no-]rect Enable rectangular motion partitions Nx2N and 2NxN. Default disabled
--[no-]amp Enable asymmetric motion partitions, requires --rect. Default disabled
Spatial / intra options:
--[no-]strong-intra-smoothing Enable strong intra smoothing for 32x32 blocks. Default enabled
--[no-]constrained-intra Constrained intra prediction (use only intra coded reference pixels) Default disabled
--[no-]b-intra Enable intra in B frames in veryslow presets. Default disabled
--[no-]fast-intra Enable faster search method for angular intra predictions. Default disabled
--rdpenalty <0..2> penalty for 32x32 intra TU in non-I slices. 0:disabled 1:RD-penalty 2:maximum. Default 0
Slice decision options:
--[no-]open-gop Enable open-GOP, allows I slices to be non-IDR. Default enabled
-I/--keyint <integer> Max IDR period in frames. -1 for infinite-gop. Default 250
-i/--min-keyint <integer> Scenecuts closer together than this are coded as I, not IDR. Default: auto
--no-scenecut Disable adaptive I-frame decision
--scenecut <integer> How aggressively to insert extra I-frames. Default 40
--rc-lookahead <integer> Number of frames for frame-type lookahead (determines encoder latency) Default 20
--bframes <integer> Maximum number of consecutive b-frames (now it only enables B GOP structure) Default 4
--b-adapt <0..2> 0 - none, 1 - fast, 2 - full (trellis) adaptive B frame scheduling. Default 2
--[no-]b-pyramid Use B-frames as references. Default enabled
Rate control, Adaptive Quantization:
--bitrate <integer> Target bitrate (kbps) for ABR (implied). Default 0
--crf <float> Quality-based VBR (0-51). Default 28.0
--vbv-maxrate <integer> Max local bitrate (kbit/s). Default 0
--vbv-bufsize <integer> Set size of the VBV buffer (kbit). Default 0
--vbv-init <float> Initial VBV buffer occupancy (fraction of bufsize or in kbits). Default 0.90
--pass Multi pass rate control.
- 1 : First pass, creates stats file
- 2 : Last pass, does not overwrite stats file
- 3 : Nth pass, overwrites stats file
--stats Filename for stats file in multipass pass rate control. Default x265_2pass.log
--[no-]slow-firstpass Enable a slow first pass in a multipass rate control mode. Default disabled
--[no-]strict-cbr Enable stricter conditions and tolerance for bitrate deviations in CBR mode. Default disabled
--analysis-mode <string|int> save - Dump analysis info into file, load - Load analysis buffers from the file. Default 0
--analysis-file <filename> Specify file name used for either dumping or reading analysis data.
--aq-mode <integer> Mode for Adaptive Quantization - 0:none 1:uniform AQ 2:auto variance. Default 1
--aq-strength <float> Reduces blocking and blurring in flat and textured areas (0 to 3.0). Default 1.00
--qg-size <int> Specifies the size of the quantization group (64, 32, 16). Default 64
--[no-]cutree Enable cutree for Adaptive Quantization. Default enabled
Loop filters (deblock and SAO):
--[no-]deblock Enable Deblocking Loop Filter, optionally specify tC:Beta offsets Default enabled
--[no-]sao Enable Sample Adaptive Offset. Default enabled
VUI options:
--sar <width:height|int> Sample Aspect Ratio, the ratio of width to height of an individual pixel.
Choose from 0=undef, 1=1:1("square"), 2=12:11, 3=10:11, 4=16:11,
5=40:33, 6=24:11, 7=20:11, 8=32:11, 9=80:33, 10=18:11, 11=15:11,
12=64:33, 13=160:99, 14=4:3, 15=3:2, 16=2:1 or custom ratio of <int:int>. Default 0
--videoformat <string> Specify video format from undef, component, pal, ntsc, secam, mac. Default undef
--range <string> Specify black level and range of luma and chroma signals as full or limited Default limited
--colorprim <string> Specify color primaries from undef, bt709, bt470m, bt470bg, smpte170m,
smpte240m, film, bt2020. Default undef
--transfer <string> Specify transfer characteristics from undef, bt709, bt470m, bt470bg, smpte170m,
smpte240m, linear, log100, log316, iec61966-2-4, bt1361e, iec61966-2-1,
bt2020-10, bt2020-12. Default undef
--master-display <string> SMPTE ST 2086 master display color volume info SEI (HDR)
format: G(x,y)B(x,y)R(x,y)WP(x,y)L(max,min)
--max-cll <string> Emit content light level info SEI as "cll,fall" (HDR)
Bitstream options:
--[no-]repeat-headers Emit SPS and PPS headers at each keyframe. Default disabled
--[no-]info Emit SEI identifying encoder and parameters. Default enabled
--[no-]hrd Enable HRD parameters signaling. Default disabled
--[no-]temporal-layers Enable a temporal sublayer for unreferenced B frames. Default disabled
C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Apps\x265\x265.exe: unknown option -- 1



StaxRip.ErrorAbortException: x265 failed with exit code 1

C:\Users\luigi.TZMS\Desktop\Video\Staxrip64>"C:\Program Files (x86)\VapourSynth\core64\vspipe.exe" "C:\Users\luigi.TZMS\Desktop\Sipario2 temp files\Sipario2.vpy" - --y4m | "C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Apps\x265\x265.exe" --crf 22 - -Deblock -1: -1 --psy-rd 0.35 --y4m --input-res 720x576 --frames 14963 --fps 25.000000 --sar 16:11 --output "C:\Users\luigi.TZMS\Desktop\Sipario2 temp files\Sipario2_out.hevc" -
Syntax: x265 [options] infile [-o] outfile
infile can be YUV or Y4M
outfile is raw HEVC bitstream
Executable Options:
-h/--help Show this help text and exit
-V/--version Show version info and exit
Output Options:
-o/--output <filename> Bitstream output file name
-D/--output-depth 8|10 Output bit depth (also internal bit depth). Default 10
--log-level <string> Logging level: none error warning info debug full. Default info
--no-progress Disable CLI progress reports
--csv <filename> Comma separated log file, if csv-log-level > 0 frame level statistics, else one line per run
--csv-log-level Level of csv logging, if csv-log-level > 0 frame level statistics, else one line per run: 0-2
Input Options:
--input <filename> Raw YUV or Y4M input file name. `-` for stdin
--fps <float|rational> Source frame rate (float or num/denom), auto-detected if Y4M
--input-res WxH Source picture size [w x h], auto-detected if Y4M
-f/--frames <integer> Maximum number of frames to encode. Default all
--seek <integer> First frame to encode
Quality reporting metrics:
--[no-]ssim Enable reporting SSIM metric scores. Default disabled
--[no-]psnr Enable reporting PSNR metric scores. Default disabled
Profile, Level, Tier:
-P/--profile <string> Enforce an encode profile: main, main10, mainstillpicture
--level-idc <integer|float> Force a minimum required decoder level (as '5.0' or '50')
--[no-]high-tier If a decoder level is specified, this modifier selects High tier of that level
--[no-]allow-non-conformance Allow the encoder to generate profile NONE bitstreams. Default disabled
Threading, performance:
--pools <integer,...> Comma separated thread count per thread pool (pool per NUMA node)
'-' implies no threads on node, '+' implies one thread per core on node
-F/--frame-threads <integer> Number of concurrently encoded frames. 0: auto-determined by core count
--[no-]wpp Enable Wavefront Parallel Processing. Default enabled
--[no-]pmode Parallel mode analysis. Default disabled
--[no-]pme Parallel motion estimation. Default disabled
--[no-]asm <bool|int|string> Override CPU detection. Default: auto
Presets:
-p/--preset <string> Trade off performance for compression efficiency. Default medium
ultrafast, superfast, veryfast, faster, fast, medium, slow, slower, veryslow, or placebo
-t/--tune <string> Tune the settings for a particular type of source or situation:
psnr, ssim, grain, zerolatency, fastdecode
Quad-Tree size and depth:
-s/--ctu <64|32|16> Maximum CU size (WxH). Default 64
--min-cu-size <64|32|16|8> Minimum CU size (WxH). Default 8
--max-tu-size <32|16|8|4> Maximum TU size (WxH). Default 32
--tu-intra-depth <integer> Max TU recursive depth for intra CUs. Default 1
--tu-inter-depth <integer> Max TU recursive depth for inter CUs. Default 1
Analysis:

--[no-]cutree Enable cutree for Adaptive Quantization. Default enabled
Loop filters (deblock and SAO):
--[no-]deblock Enable Deblocking Loop Filter, optionally specify tC:Beta offsets Default enabled
--[no-]sao Enable Sample Adaptive Offset. Default enabled
VUI options:
--sar <width:height|int> Sample Aspect Ratio, the ratio of width to height of an individual pixel.
Choose from 0=undef, 1=1:1("square"), 2=12:11, 3=10:11, 4=16:11,
5=40:33, 6=24:11, 7=20:11, 8=32:11, 9=80:33, 10=18:11, 11=15:11,
12=64:33, 13=160:99, 14=4:3, 15=3:2, 16=2:1 or custom ratio of <int:int>. Default 0
--videoformat <string> Specify video format from undef, component, pal, ntsc, secam, mac. Default undef
--range <string> Specify black level and range of luma and chroma signals as full or limited Default limited
--colorprim <string> Specify color primaries from undef, bt709, bt470m, bt470bg, smpte170m,
smpte240m, film, bt2020. Default undef
--transfer <string> Specify transfer characteristics from undef, bt709, bt470m, bt470bg, smpte170m,
smpte240m, linear, log100, log316, iec61966-2-4, bt1361e, iec61966-2-1,
bt2020-10, bt2020-12. Default undef

.......................................................


in StaxRip.Proc.Start() in D:\Projekte\GitHub\staxrip\General\Proc.vb:riga 244
in StaxRip.x265.x265Encoder.Encode(String passName, String args, VideoScript script) in D:\Projekte\GitHub\staxrip\General\x265.vb:riga 80
in StaxRip.x265.x265Encoder.Encode() in D:\Projekte\GitHub\staxrip\General\x265.vb:riga 46
in StaxRip.MainForm.Encode() in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:riga 2352
in StaxRip.MainForm.RunJobRecursive() in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:riga 3644

[stax76]

- -Deblock -1: -1

looks like StaxRip generates a incorrect command line here

[burfadel]

looks like StaxRip generates a incorrect command line here

"(app-path)\ffmpeg\ffmpeg.exe" -i "(path\file.avs)" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | (app-path)\x265\x265.exe" --crf 21 --tu-intra-depth 2 --b-intra --aq-mode 2 --qg-size 16 --nr-intra 400 --nr-inter 400 --subme 3 --max-merge 5 --weightb --bframes 8 --rc-lookahead 40 --ref 6 --keyint 600 --psy-rd 0.8 --output-depth 10 --limit-refs 1 --y4m --input-res 864x480 --frames 52700 --fps 25.000000 --output "(path\output).hevc" -

I've also noticed an anomaly in the x265 command line, however it doesn't seem to affect encoding. Note that I did censor the program path and file path, just to make things neater. The highlight bold, over sized '-' is what is important (had to highlight it like that because it is easily overlook otherwise). It adds it at the end of the ffmpeg pipe, as well as the end of the x265 command line, at least according to the log.

[luigizaninoni]

can't I use mpeg2source with VS ? that's a big disappointment, because of its "cpu6" mode, that deblocks and derings well and fast (at least for my needs)

[stax76]

I've also noticed an anomaly in the x265 command line, however it doesn't seem to affect encoding. Note that I did censor the program path and file path, just to make things neater. The highlight bold, over sized '-' is what is important (had to highlight it like that because it is easily overlook otherwise). It adds it at the end of the ffmpeg pipe, as well as the end of the x265 command line, at least according to the log.

My dos/batch knowledge is rather poor but as far as I know two dashes are typically needed for piping so it looks alright, the first dash is where normally the output file path for ffmpeg is and the second dash is where normally the input file path for x265 is.

can't I use mpeg2source with VS ? that's a big disappointment, because of its "cpu6" mode, that deblocks and derings well and fast (at least for my needs)

I'm pretty new to VapourSynth so I don't know yet which filters are available and working. Currently I don't have great plans for adding new features, I want to add quite a few more plugins and filters however for both AviSynth+ and VapourSynth.

[burfadel]

My dos/batch knowledge is rather poor but as far as I know two dashes are typically needed for piping so it looks alright, the first dash is where normally the output file path for ffmpeg is and the second dash is where normally the input file path for x265 is.

Ah ok! I wasn't aware of that :).

[stax76]

I report still the batch prosessor bug:

Look that huge bitrate that it is using While my template should be bitrate 900.

If it is what I think then it's by design, you have to go in the codec config dialog and enter the bitrate as custom command line argument, this works for x264 and x265, with GPU encoding the custom switches are applied at the beginning instead of the end where it should be, I hope I can fix this easily. I probably said already that it's probably better to use crf and possibly restrict --vbv-bufsize and --vbv-maxrate, seriously.

The option for demuxing directly when batch processing works, only the tooltip was bad/outdated.

[stax76]

Ah ok! Come to think of it, since it's cutting by mod 16 etc it would be better to crop first :).

I notice in the tech preview that abort doesn't work with x265 either. I guess it was pointing to the old pipe method? If you pause and abort ffmpeg, it pauses and aborts x265 cleanly :).

aborting x265 works here

[NikosD]

Lots of interesting changes in this version, still some issues reported by email haven't been fixed yet.

I will give you some general issues, because specific issues for specific files are too many and maybe not interesting.

M2TS

1) When a .m2ts file contains a TrueHD/AC3 in a single audio stream, then in single file mode using eac3to or batch file mode processing, you always truncate the AC3 stream from the MKV output which contains only TrueHD, instead of two audio streams - one with THD and the other with AC3.

Since MKVmerge v7.7.0 (01/03/2015), there is an option to keep and mux both THD and AC3 streams as different audio tracks in the same MKV file.
You have to enable this muxing option because you 're still using the MKVMerge in the old way.


TS


2) It seems that .ts MPEG2 files are "hardcoded" to use ProjectX in both single/batch file processing, resulting bad crashes for someone with no Java installed, even if ProjectX is disabled in settings.

In single mode, only if you select "Auto" and not specific source filter, the app uses dsmux instead of ProjectX in order to avoid a hard crash.


DSMUX

3) Using dsmux adds always English as language in both audio/ video streams, when the streams have no language.

Also, it usually produces VFR video files (not smooth playback) in many cases, especially in "Just Mux" mode (but not explicitly)

You must find another tool, especially for H.264 (progressive & interlaced)


QSVEncC GUI


4) You have to remove the option of "VQP" encoding mode, when HW decoding is used because it is incompatible.
You can leave it in SW decoding mode or remove it completely.

Also, you removed the automatic addition of -tff switch in command line when someone selects a HW de-interlace mode, resulting in a progressive -nterlaced output if someone forgets to select it manually.

The previous GUI added that automatically, I think an auto selection of the most common -tff would be useful.

The addition of both tff/bff is nice in order to output interlaced content.


Requests

5) You changed MediaInfo Folder View, adding more columns and sub-folders processing, but still you can't add/remove your own columns or change the order of the columns or the other things discussed in previous posts.

I hope in your next version to add more flexibility.

6) Is it possible to add a "Trim GUI" like Crop or even Resize for QSVEncC trim function or StaxRip in general ?


P.S

QSVEncC has been updating almost every Sunday the last few weeks and the new version is b11, by now.

[sneaker_ger]

Since MKVmerge v7.7.0 (01/03/2015), there is an option to keep and mux both THD and AC3 streams as different audio tracks in the same MKV file.
You have to enable this muxing option because you 're still using the MKVMerge in the old way.
It's not a switch you can just turn on AFAIK. It will simply be handled like two different tracks, i.e. you have to use the usual track selection options mkvmerge offers to activate/deactivate the tracks you want/don't want.

[stax76]

Since MKVmerge v7.7.0 (01/03/2015), there is an option to keep and mux both THD and AC3 streams as different audio tracks in the same MKV file.
You have to enable this muxing option because you 're still using the MKVMerge in the old way.

MediaInfo and command line showing how it works would be helpful.

2) It seems that .ts MPEG2 files are "hardcoded" to use ProjectX in both single/batch file processing, resulting bad crashes for someone with no Java installed, even if ProjectX is disabled in settings.

In single mode, only if you select "Auto" and not specific source filter, the app uses dsmux instead of ProjectX in order to avoid a hard crash.

It was a bug causing demuxers to run when they shouldn't.

You have to remove the option of "VQP" encoding mode, when HW decoding is used because it is incompatible.
You can leave it in SW decoding mode or remove it completely.

If I remember right then the problem was that it's technically not simple to come by, not worth the trouble.

5) You changed MediaInfo Folder View, adding more columns and sub-folders processing, but still you can't add/remove your own columns or change the order of the columns or the other things discussed in previous posts.

I hope in your next version to add more flexibility.

at the moment I don't plan to improve it sorry, I have lot's of good ideas like using a data view instead of a list view and adding csv export but unfortunately I don't have much need for the features and therefore little motivation. With the new VapourSynth support and the new manual workflow features I feel StaxRip has become more complete then ever, I hardly miss anything except things I can only fix with C++ which would mean very slow StaxRip development for very long time.

Is it possible to add a "Trim GUI" like Crop or even Resize for QSVEncC trim function or StaxRip in general ?

I'm not sure what you mean here, can't you cut in the preview with QS HW decoding?

I remember implementing and testing this, most of this stuff were one liners anyway, see here:

https://github.com/stax76/staxrip/blob/master/General/VideoEncoder.vb#L1442

[stax76]

I fixed a few issues and added a few things since yesterday hoping it's stable enough because I'm releasing it now.

StaxRip x64 1.3.1.5 beta (2015-06-25)


New: Added full first class VapourSynth support including plugins and profile for QTGMC
New: Added possibility to switch dynamically between any source filter back and forth including DGSource and DGSourceIM. Indexing is triggered automatically in case no index file is present
New: Added vinverse plugin to remove residual combing from NTSC
New: Added GUI for demuxing MKV and MP4
New: Added feature to easily enable certain parameters for certain filters in the AviSynth editor. Currently supported are FFVideoSource and DGSource, more parameters and filters might be supported on request. Use it by right-clicking on FFVideoSource or DGSource in the AviSynth editor, the menu shows then NTSC options and hardware cropping and resizing options.
New: Added Play option for MPC playback in the AviSynth editor
New: Added two new options in the dialog to define files for batch processing to add a entire folder and a entire folder including sub-folders
New: Added new subtitle UI based on data view
New: Added option to generate subtitle names based on the subtitle language
New: x265 switch --limit-refs added
Fix: Disabled audio demuxing for MKV and MP4 by DGIndexNV and DGIndexIM because it's already demuxed by MP4Box and mkvextract
Fix: Tools/Directories/Plugins wasn't pointing to the AviSynth+ plugin directory
Fix: Wrong command line generated for --deblock
Update: QSVEncC 2.0 beta 11
Update: x265 1.7+234
Tweak: DTS bitrate is now unrestricted
Tweak: Moved field processing filters to dedicated category like before in StaxRip x86
Tweak: Replaced LinkLabels with Buttons in eac3to dialog
Tweak: The help for all included AviSynth plugins can now be accessed per menu in the AviSynth editor
Tweak: ProjectX is enabled by default in case Java exists, other dsmux will handle MPEG-2 TS
Tweak: In the dialog to define files for batch processing the 'Create Jobs' option was renamed to 'Demux and index before adding jobs', regardless of if this option is enabled jobs are always created
Tweak: Removed x86 and VS C++ 2013 from AviSynth+ installer bringing it from 18 MB down to 4 MB. Very often VS C++ 2013 is already installed and in case it ain't already installed StaxRip will show the Apps dialog which has a download button for VS C++ 2013.
Tweak: replaced avs4x26x with ffmpeg


http://thumbnails108.imagebam.com/41765/adee8a417643493.jpg (http://www.imagebam.com/image/adee8a417643493) http://thumbnails105.imagebam.com/41765/f4d9a1417643496.jpg (http://www.imagebam.com/image/f4d9a1417643496) http://thumbnails108.imagebam.com/41765/c7cf22417643498.jpg (http://www.imagebam.com/image/c7cf22417643498) http://thumbnails108.imagebam.com/41765/f5d8ed417643500.jpg (http://www.imagebam.com/image/f5d8ed417643500) http://thumbnails105.imagebam.com/41765/3415cd417643501.jpg (http://www.imagebam.com/image/3415cd417643501) http://thumbnails108.imagebam.com/41765/f9b9bb417643505.jpg (http://www.imagebam.com/image/f9b9bb417643505) http://thumbnails108.imagebam.com/41765/dc720a417643508.jpg (http://www.imagebam.com/image/dc720a417643508) http://thumbnails105.imagebam.com/41765/c5a7b0417643509.jpg (http://www.imagebam.com/image/c5a7b0417643509)

http://github.com/stax76/staxrip/releases/tag/StaxRip_x64_1.3.1.5_beta

[noee]

I'm getting failures to extract audio files from mkvs, pcm and ac/3. Looks like it's trying with mkvextract, failing and falling back to ffmpeg which then fails with this error:

"C:\Users\......\staxrip\Apps\ffmpeg\ffmpeg.exe" -i "C:\Output\austria.mkv" -c:a copy -vn -sn -y "C:\Output\austria temp files\austria ID2.wav"
.
.
.
Stream mapping:
Stream #0:1 -> #0:0 (copy)
Could not write header for output file #0 (incorrect codec parameters ?): Error number -40 occurred

edit: looks like AC/3 is working, sorry.

[noee]

If I choose Vapoursynth as source, let it extract the tracks, then go to the crop dialog, I get a python error that fmtconv.dll is already loaded and I can't dismiss the dialog and the only recourse is to kill staxrip in taskmanager.

[NikosD]

MediaInfo and command line showing how it works would be helpful.


Here is a .m2ts sample with TrueHD/AC3
https://www.sendspace.com/file/ukfaf6

Here is the same file in MKV (how it should be)
https://www.sendspace.com/file/ntr01v


If I remember right then the problem was that it's technically not simple to come by, not worth the trouble.


I thought removing just an encoding mode like VQP in HW decoding would be easy, if it's not then leave it.

I never use that mode, I posted that in terms of completeness of StaxRip.


I'm not sure what you mean here, can't you cut in the preview with QS HW decoding?

I remember implementing and testing this, most of this stuff were one liners anyway, see here:

https://github.com/stax76/staxrip/blob/master/General/VideoEncoder.vb#L1442

Perfect!
This is exactly what I was looking for, but never thought it would be already there.

I think there are a lot more "hidden", undocumented beautiful features like that in StaxRip.

Also, did you see that ?


You removed the automatic addition of -tff switch in command line when someone selects a HW de-interlace mode, resulting in a progressive -nterlaced output if someone forgets to select it manually.

The previous GUI added that automatically, I think an auto selection of the most common -tff would be useful.



One last question:

Is there somewhere a rotate/ flip function that I can't see ?

[noee]

Here's another one. I trying to encode a dvd (interlaced) that has been previously muxed with mkvtoolnix using VapourSynth and QTGMC. Extract works great, but when I check the QTGMC filter, the status line shows "Avisynth error" (cosmetic I guess) and with the same "fmtconv.dll already loaded" similar to my crop dialog bug in the post above. Can go no further after that.

Edit:
Got a little further by checking and unchecking the QTGMC filter a few times, at least the status error went away.

Now, clicking next adds the job. When I click start, I get this:

Error x264

x264 failed with exit code -1

C:\Users\Mike\Documents\Utils\staxrip>"C:\Program Files (x86)\VapourSynth\core64\vspipe.exe" "C:\Temp\_stax_temp\corea temp files\corea_new.vpy" - --y4m | "C:\Users\Mike\Documents\Utils\staxrip\Apps\x264\x264.exe" --preset veryfast --tune film --crf 26 --sar 10:11 --demuxer y4m --frames 240 --output "C:\Temp\_stax_temp\corea temp files\corea_new_out.h264" "-"
Script evaluation failed:
Python exception: Plugin C:\Users\Mike\Documents\Utils\staxrip\Apps\Plugins\vs\fmtconv\fmtconv.dll already loaded (fmtconv)
Traceback (most recent call last):
File "vapoursynth.pyx", line 1467, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:24719)
File "C:\Temp\_stax_temp\corea temp files\corea_new.vpy", line 5, in <module>
core.std.LoadPlugin(r'C:\Users\Mike\Documents\Utils\staxrip\Apps\Plugins\vs\fmtconv\fmtconv.dll')
File "vapoursynth.pyx", line 1366, in vapoursynth.Function.__call__ (src\cython\vapoursynth.c:23214)
vapoursynth.Error: Plugin C:\Users\Mike\Documents\Utils\staxrip\Apps\Plugins\vs\fmtconv\fmtconv.dll already loaded (fmtconv)
x264 [error]: could not open input file `-'



StaxRip.ErrorAbortException: x264 failed with exit code -1

C:\Users\Mike\Documents\Utils\staxrip>"C:\Program Files (x86)\VapourSynth\core64\vspipe.exe" "C:\Temp\_stax_temp\corea temp files\corea_new.vpy" - --y4m | "C:\Users\Mike\Documents\Utils\staxrip\Apps\x264\x264.exe" --preset veryfast --tune film --crf 26 --sar 10:11 --demuxer y4m --frames 240 --output "C:\Temp\_stax_temp\corea temp files\corea_new_out.h264" "-"
Script evaluation failed:
Python exception: Plugin C:\Users\Mike\Documents\Utils\staxrip\Apps\Plugins\vs\fmtconv\fmtconv.dll already loaded (fmtconv)
Traceback (most recent call last):
File "vapoursynth.pyx", line 1467, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:24719)
File "C:\Temp\_stax_temp\corea temp files\corea_new.vpy", line 5, in <module>
core.std.LoadPlugin(r'C:\Users\Mike\Documents\Utils\staxrip\Apps\Plugins\vs\fmtconv\fmtconv.dll')
File "vapoursynth.pyx", line 1366, in vapoursynth.Function.__call__ (src\cython\vapoursynth.c:23214)
vapoursynth.Error: Plugin C:\Users\Mike\Documents\Utils\staxrip\Apps\Plugins\vs\fmtconv\fmtconv.dll already loaded (fmtconv)
x264 [error]: could not open input file `-'


at StaxRip.Proc.Start() in D:\Projekte\GitHub\staxrip\General\Proc.vb:line 244
at StaxRip.x264Encoder.Encode(String passName, String args, VideoScript script) in D:\Projekte\GitHub\staxrip\General\x264.vb:line 65
at StaxRip.x264Encoder.Encode() in D:\Projekte\GitHub\staxrip\General\x264.vb:line 37
at StaxRip.MainForm.Encode() in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:line 2352
at StaxRip.MainForm.RunJobRecursive() in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:line 3643

[stax76]

can't I use mpeg2source with VS ? that's a big disappointment, because of its "cpu6" mode, that deblocks and derings well and fast (at least for my needs)

I had to do some improvements to make d2vsource.dll work so in the next release I can tell you how to use it. One limitation currently is the source filter automation is restricted to AviSynth+, this might change in the future. d2vsource.dll and DGMPGDec in general cannot deal with DVDs with bad timestamps and quite many DVDs depending on Studio producing the DVD exist. DGIndex when used manually will show a nice warning to trim manually which is incredible useful considering all your subtitles are out of sync when you actually do this. Best option is to use MakeMKV and ffms2, to handle bad timestamps without MakeMKV the best way is to use AnyDVD and use DVD Shrink to rip as a single VOB file and use DVD Shrink's trim feature to trim the studio intro with bad timestamps, subtitles can then be handled with DVDSubEdit and BDSup2Sub++, this whole process is much more cumbersome then simply using MakeMKV and that's why I have some doubts including d2vsource.dll directly.

[stax76]

@noee

regarding the pcm issue please upload the full log file to pastebin, if you want you can use sublime text's or notepad++'s search and replace feature to obfuscate the file name and you can use pastebin's auto expire feature.

If I choose Vapoursynth as source, let it extract the tracks, then go to the crop dialog, I get a python error that fmtconv.dll is already loaded and I can't dismiss the dialog and the only recourse is to kill staxrip in taskmanager.

What looks your script like before you open the file and what is the mediainfo of the file you open, there might be a log file with both of this info. I've not experienced a problem with fmtconv or another plugin being already loaded, are these plugins present in your auto load folder, maybe this is a problem for VapourSynth, for AviSynth it don't matter, in any case StaxRip uses manual loading so maybe the problem is manual loading fails because it was already auto loaded. For any problem seeing a log file is always the most important for me and second most important is always having a sample in case the log file don't help.

Here is a .m2ts sample with TrueHD/AC3
https://www.sendspace.com/file/ukfaf6

Here is the same file in MKV (how it should be)
https://www.sendspace.com/file/ntr01v

I've quite a few M2TS samples including thd+ac3. It's not a topic I have special interest and experience and I don't want to spend much energy in topics not frequently requested so if you would like me to investigate it you would have to make it simple enough for me to understand what the problem is and how it can be solved.

I thought removing just an encoding mode like VQP in HW decoding would be easy, if it's not then leave it.

I don't have all details in mind, I think it's not simple to remove an item from the menu when the menu is already constructed. This dialog is like the x265 dialog based on 2 special frameworks I designed, automatic GUI construction from code which again is automatically constructed from the CLI model which also generates the command line automatically, things that appear simple often would require to improve the framework which is often not worth the effort.

You removed the automatic addition of -tff switch in command line when someone selects a HW de-interlace mode, resulting in a progressive -nterlaced output if someone forgets to select it manually.

The previous GUI added that automatically, I think an auto selection of the most common -tff would be useful.

I don't remember how it works and why it was changed.

Is there somewhere a rotate/ flip function that I can't see ?

AviSynth and VapourSynth can do it certainly but there aren't presets or something in StaxRip.

[NikosD]

I've quite a few M2TS samples including thd+ac3. It's not a topic I have special interest and experience and I don't want to spend much energy in topics not frequently requested so if you would like me to investigate it you would have to make it simple enough for me to understand what the problem is and how it can be solved.


If you try to transcode a .m2ts file with thd+ac3 stream to .mkv file with StaxRip you will get only thd audio.
The ac3 stream is gone.

I know that apps using Mkvmerge can preserve the ac3 stream.

Maybe you could ask Mosu or Tebasuna who has already made this in his eac3to GUI.


I don't remember how it works and why it was changed.


QSVEncC needs the -tff/bff switch in order to detect the input stream as interlaced.
So when you select a de-interlacing mode, you should put -tff or -bff because otherwise, the app thinks that the input is progressive and no HW deinterlacing occurs.

Just auto - select the tff box whenever a deinterlacing mode is selected.
Nothing else.


AviSynth and VapourSynth can do it certainly but there aren't presets or something in StaxRip.

Thanks.

[stax76]

If you try to transcode a .m2ts file with thd+ac3 stream to .mkv file with StaxRip you will get only thd audio.
The ac3 stream is gone.

I know that apps using Mkvmerge can preserve the ac3 stream.

Maybe you could ask Mosu or Tebasuna who has already made this in his eac3to GUI.

I changed it like so: if the audio source file is M2TS and the selected stream is THD+AC3 then the resulting mkv will have a THD and a AC3 stream, if the audio source file is .thd+ac3 then the resulting mkv will also have a THD and a AC3 stream.

QSVEncC needs the -tff/bff switch in order to detect the input stream as interlaced.
So when you select a de-interlacing mode, you should put -tff or -bff because otherwise, the app thinks that the input is progressive and no HW deinterlacing occurs.

Just auto - select the tff box whenever a deinterlacing mode is selected.
Nothing else.

I changed it like so: if deinterlacing mode is normal or bob and tff and bff is disabled then tff gets enabled, if deinterlacing mode is not normal and not bob then tff and bff get disabled.

[NikosD]

I changed it like so: if the audio source file is M2TS and the selected stream is THD+AC3 then the resulting mkv will have a THD and a AC3 stream, if the audio source file is .thd+ac3 then the resulting mkv will also have a THD and a AC3 stream.


It sounds OK, but it must also work OK in batch processing mode automatically (where there is no manual selection of THD+AC3)


I changed it like so: if deinterlacing mode is normal or bob and tff and bff is disabled then tff gets enabled, if deinterlacing mode is not normal and not bob then tff and bff get disabled.

If deinterlacing is "none", then tff and bff shouldn't be auto selected, BUT the two boxes should be displayed in order to be able to output interlaced content (for interlaced input).

You shouldn't hide bff/tff options completely, even if deinterlacing is none.

[Havokdan]

Virus?!?:

http://i.imgur.com/6FwXykO.png

[stax76]

False positive maybe? Here is the support thread for nnedi3 for VapourSynth:

http://forum.doom9.org/showthread.php?t=166434

[NikosD]

There is a new version of QSVEncC v2.03, which among other things adds two new video editing functions.

a) A 180 degrees rotation (vpp-half-turn)

b) A removal of half-transparent logos from video

[SuLyMaN]

Hi guys. I'm a bit late to the party. While I have read the features, it appears that Radeon GPU is not supported... Can someone confirm if this is definetely the case? Thanks

[NikosD]

Yes it is.

[SuLyMaN]

Damn. Too bad I guess! Thanks.

[chummy]

Can't make Staxrip work with Debugmode FrameServer, it's incompatibility or just me. Just to compare Megui works fine.

[Vulpix]

Having trouble figuring how to do a target bitrate encode for a batch of files. Seems the "file size" parameters always overwrites the bitrate :D

I never used bitrate for encoding but I'm trying to batch-encode a bunch of videos and I want all of them to be 1500kbps, but I can't figure out how to do it (using latest beta and nvidia h264)

Any tips? It's not as easy as it seems, I even set a new menu option for "target bitrate", but it still takes size as the primary factor and overwrites the bitrate...

[Atak_Snajpera]

stax76
Could you add option in your Video Comparison tool seek to key-frames? (Shift+right/left). Also frame number in yellow in right top corner would be useful.

[stax76]

stax76
Could you add option in your Video Comparison tool seek to key-frames? (Shift+right/left). Also frame number in yellow in right top corner would be useful.

I've added it to the todo list and investigate it.

Having trouble figuring how to do a target bitrate encode for a batch of files. Seems the "file size" parameters always overwrites the bitrate :D

I never used bitrate for encoding but I'm trying to batch-encode a bunch of videos and I want all of them to be 1500kbps, but I can't figure out how to do it (using latest beta and nvidia h264)

Any tips? It's not as easy as it seems, I even set a new menu option for "target bitrate", but it still takes size as the primary factor and overwrites the bitrate...

I gave up ;), next version has:

New: Added option for fixed bitrate even though using a fixed bitrate is not recommended. It was added because over the years it was requested dozens of times. StaxRip will show a warning telling to rather use quality mode and constrain the maximum data rate if necessary.

Can't make Staxrip work with Debugmode FrameServer, it's incompatibility or just me. Just to compare Megui works fine.

Is this a AviSynth plugin, how does it work?

Hi guys. I'm a bit late to the party. While I have read the features, it appears that Radeon GPU is not supported... Can someone confirm if this is definetely the case? Thanks

I believe AMD improved their encoder for recent or up-coming APUs but it don't look like they provide a CLI app that GUIs could use, maybe somebody else will build a CLI app. AMD has announced Handbrake support, Intel is still best for video encoding followed by NVIDIA.

There is a new version of QSVEncC v2.03, which among other things adds two new video editing functions.

a) A 180 degrees rotation (vpp-half-turn)

b) A removal of half-transparent logos from video

I don't know how logo removal works, I can add the rotate option but I will have to add a sidebar for tab navigation like it is used in the x265 options.

[NikosD]

I don't know how logo removal works, I can add the rotate option but I will have to add a sidebar for tab navigation like it is used in the x265 options.

I don't think it worths the trouble.

It's a rarely used (I think) slow (unoptimized) process.

Only if you would like to add more options giving the chance of a new GUI.

I may ask rigaya how logo removal works.

The truth is that I don't have any such clip to test.

[chummy]

Is this a AviSynth plugin, how does it work?

Yes, this a bit strange, i'm started using staxrip few weeks ago for the first time, then i see a 2012 video and this "method" was working fine in this period with staxrip. But new version i'm using is not compatible, at least for me.

P.S: Just tested it with version 1180 and worked fine. Something is incompatible in new version.

[fredlkrue]

I encode videos to XviD/.avi in order to play them in my Samsung Galaxy Player. With the previous version "StaxRip 1.1.9.0" worked fine, but with the latest beta version I am having two issues. 1. In my media player for some reason it doesn't show thumbnails but the video plays fine. 2. The second issue is with the MP3 encoder (lame) with BeSweet, I use this encoder because it automatically sets the gain and normalizes for better sound. The output file plays a "noise" at the very beggining for like a second, but the rest of the file is fine. I tried with different videos with the same result, I also encoded to AAC using BeSweet and it doesn't have this issue.

[stax76]

Yes, this a bit strange, i'm started using staxrip few weeks ago for the first time, then i see a 2012 video and this "method" was working fine in this period with staxrip. But new version i'm using is not compatible, at least for me.

P.S: Just tested it with version 1180 and worked fine. Something is incompatible in new version.

Maybe your plugin wasn't x64?

edit:

I encode videos to XviD/.avi in order to play them in my Samsung Galaxy Player. With the previous version "StaxRip 1.1.9.0" worked fine, but with the latest beta version I am having two issues. 1. In my media player for some reason it doesn't show thumbnails but the video plays fine. 2. The second issue is with the MP3 encoder (lame) with BeSweet, I use this encoder because it automatically sets the gain and normalizes for better sound. The output file plays a "noise" at the very beggining for like a second, but the rest of the file is fine. I tried with different videos with the same result, I also encoded to AAC using BeSweet and it doesn't have this issue.

The reason could be StaxRip x64 uses ffmpeg to mux AVI, before it was using VirtualDubMod, I consider to use VirtualDub x64 because there are now problems reported by at least 2 people.

If you use ffmpeg for MP3 encoding which is the default I believe, then normalize should be performed as well, normalize is a separate processing step in this case and therefore there should be a normalize section in the log file.

[fredlkrue]

Thanks for the reply, but I don't think it sets the Gain setting like BeSweet does.

[stax76]

Thanks for the reply, but I don't think it sets the Gain setting like BeSweet does.

Does BeSweet something special?

[fredlkrue]

Does BeSweet something special?

Automatically sets the Gain and the output file is louder then the encoded file with ffmpeg.

[stax76]

StaxRip normalizes when ffmpeg is used as audio encoder!

http://pastebin.com/kpZS0CUK

[fredlkrue]

StaxRip normalizes when ffmpeg is used as audio encoder!

http://pastebin.com/kpZS0CUK

Weird, then why I am hearing loader on files encoded with BeSweet?

Edit: Nevermind this issue then, thanks for your help.

[cegy]

so today i tried staxrip x64 1.3.5.1 and tried it out. i copied most of the "settings/things i like" between the old 1.1.8 which i've always enjoyed using to find out there was quite a few things thats not there anymore its more of the basic things which might of expected to still be there like.


drag and drop a file on to the gui it asks you which index/demuxer/filter you wanna use (not in 1.1.8 it would use the first one and if that fails it falls back to the next filter/option i think...)
like this http://i.imgur.com/esri2Mi.png

so when your done encoding your file it doesn't seem to bring the gui to the front nor is there a option for this (did this in 1.1.8)

when you do load your video file up it won't auto detect if there's a already audio file with the same sort of name (like "this.video.file.mkv" it would auto detect "this.video.file_audio.ac3" and load it and it doesn't do this anymore) it would however try and load? the audio from the input file (no options for this i think...)

[stax76]

drag and drop a file on to the gui it asks you which index/demuxer/filter you wanna use (not in 1.1.8 it would use the first one and if that fails it falls back to the next filter/option i think...)

If a few people request it I can add a setting to disable the dialog. Most of the time I just click Automatic but there are occasions where it's very useful being able to manually select a alternative filter.

so when your done encoding your file it doesn't seem to bring the gui to the front nor is there a option for this (did this in 1.1.8)

This was changed in case somebody watches a movie. If it's possible to reliably detect which process is in the foreground, then StaxRip could bring it to foreground only when not a known player is in the foreground, I'll investigate if such a API exists, if it's not possible I can add a option if a few people request it.

when you do load your video file up it won't auto detect if there's a already audio file with the same sort of name (like "this.video.file.mkv" it would auto detect "this.video.file_audio.ac3" and load it and it doesn't do this anymore) it would however try and load? the audio from the input file (no options for this i think...)

This should still work, what's the file path of your audio and video file?

[cegy]

If a few people request it I can add a setting to disable the dialog. Most of the time I just click Automatic but there are occasions where it's very useful being able to manually select a alternative filter.

it would be nice to have it as a option so a user can pick or use the first default? indexer and if that fails then ask maybe?

This was changed in case somebody watches a movie. If it's possible to reliably detect which process is in the foreground, then StaxRip could bring it to foreground only when not a known player is in the foreground, I'll investigate if such a API exists, if it's not possible I can add a option if a few people request it.

you could even add this as a option for the user aswell maybe?


This should still work, what's the file path of your audio and video file?

the video and the audio is in the same dir/path as each other please take a look here for a small example as all it showing is staxrip 1.1.8 vs 1.3.1.5 about this issue? http://gfycat.com/SplendidCircularDalmatian#?speed=0.25 (http://gfycat.com/SplendidCircularDalmatian#?speed=0.5)


p.s is there a way to disable autocrop so it never runs without having to untick crop ? as with crop being ticked it trigger even in the settings/options with it turned off it still triggers the only way it won't trigger at all it seems if for the user to untick crop which is abit odd...

[stax76]

it would be nice to have it as a option so a user can pick or use the first default? indexer and if that fails then ask maybe?

I consider to add a option and investigate if the dialog can be shown easily in case of an error.

For window activation I wrote the code, I hard coded mpc and vlc, for other players people have to tell me the executable name. Adding still a option depends on requests.

About detecting the audio file there was a bug, it should work in the next release.

p.s is there a way to disable autocrop so it never runs without having to untick crop ? as with crop being ticked it trigger even in the settings/options with it turned off it still triggers the only way it won't trigger at all it seems if for the user to untick crop which is abit odd...

I believe there was a option for auto crop which was removed so yes, the only way now to disable auto crop is to uncheck the crop filter in the main dialog. I don't remember why it was changed, the new way looks simple, maybe just needs time to get used to it?

[cegy]

I consider to add a option and investigate if the dialog can be shown easily in case of an error.

For window activation I wrote the code, I hard coded mpc and vlc, for other players people have to tell me the executable name. Adding still a option depends on requests.

About detecting the audio file there was a bug, it should work in the next release.


I believe there was a option for auto crop which was removed so yes, the only way now to disable auto crop is to uncheck the crop filter in the main dialog. I don't remember why it was changed, the new way looks simple, maybe just needs time to get used to it?

the auto crop thing seems like a bug as if u disable it in the options which it tells you to in the status window thing ? yet it still uses it isn't that an bug of some sort ? or maybe wording what you "really" need to do might be better ?

i've also noticed the languages are not set in a mp4 container unlike 1.1.8 unsure how this would be different as there's no option for it but it seems to left it blank like the user didn't set it (maybe there's a option it reads from and uses that i think....)

the window "bring to front" when done was a nice option to have... sure if its hard coded to some "players" but maybe the user likes the idea of it to alert them that his/her encode is done and not being left in the background thinking "this is taking a long time" which is sort of ideal if you busy and you only want to check to see if the gui pops up or not which gives another valid reason to bring back the option or at least let the user pick how he/she wants it to reaction after its done encoding :eek:


also the codec comparison sure is nice :thanks: to have and use but would it be possible to have like a offset frames (if they don't line up frame by frame by they are a few frames out) and also if it detects the wrong fps for the file like to reduce it from 50fps down to 25fps (maybe also the other way around aswell ?)to match each other so your able to match them more closer together this is only a few suggestions towards and maybe make it as a standalone for other users to enjoy for both 32bit and 64bit (not keen on having to use vapoursynth myself) ?

[stax76]

the auto crop thing seems like a bug as if u disable it in the options which it tells you to in the status window thing ? yet it still uses it isn't that an bug of some sort ? or maybe wording what you "really" need to do might be better ?

I can't follow you here, what is the exact name of the option you refer to (you can copy names of options from the help)?

i've also noticed the languages are not set in a mp4 container unlike 1.1.8 unsure how this would be different as there's no option for it but it seems to left it blank like the user didn't set it (maybe there's a option it reads from and uses that i think....)

I think there was a issue with mp4box languages reported in the MeGUI thread but I tested it and StaxRip wasn't effected. For such problems I need a log file which you can mail me or post to pastebin, if you use pastebin then please obfuscate the file paths if necessary using a text editor or send me the link as private message, also please enable pastebin's auto expire feature.

As for the other suggestions I can't add very special features that aren't at least requested by a few users due to lack of time and because I want to avoid feature creep. It's likely that I will build a TS demuxing app, my current plan is converting the ProjectX Java code to VB.NET using a automatic code converter, GUI and related features like editing will be removed.

[cegy]

I can't follow you here, what is the exact name of the option you refer to (you can copy names of options from the help)?



I think there was a issue with mp4box languages reported in the MeGUI thread but I tested it and StaxRip wasn't effected. For such problems I need a log file which you can mail me or post to pastebin, if you use pastebin then please obfuscate the file paths if necessary using a text editor or send me the link as private message, also please enable pastebin's auto expire feature.

As for the other suggestions I can't add very special features that aren't at least requested by a few users due to lack of time and because I want to avoid feature creep. It's likely that I will build a TS demuxing app, my current plan is converting the ProjectX Java code to VB.NET using a automatic code converter, GUI and related features like editing will be removed.


the languages options i might of mistaken for the title which was always set as the language as the title i think if no stream name is set maybe use the language so it isn't blank ?
(audio edit > stream name > "%language_english%") << i'm unsure if i ever set this or not but i did notice this (this is from 1.1.8 yet in 1.3.1.5 the stream name is blank by default)
here's a picture

http://i.imgur.com/0lrYRav.png

the auto cropping part at the moment says

"Autocrop sometimes hangs depending on source file and source filter. In case it hangs uncheck the crop filter or disable it in the options."

the last part i would say is wrong or maybe a bug as if the user does disable it in the options it doesn't disable the autocrop checking thingy? which seems like a minor error of some sort as it doesn't disable it nor does respect that the user has set it to disable in the options.

the way i understand it maybe is like this....


default: auto crop check?
disable auto crop in options: doesn't run auto crop (the user did tell it disable in the options so it respected even if the crop filter is still ticked)
disable crop filter: nothing to do with cropping triggers (normal)


then you get how it works at the moment which seems to be more like


default: auto crop check?
disable auto crop in options: auto crop check runs (it isn't respect that the user has disabled it)
disable auto crop in options and untick crop filter: nothing to do with cropping triggers (now its respecting some sort of options guessing due to the crop filter being unticked)
disable crop filter: nothing to do with cropping triggers


i hope this helps you out stax76 another thing i've noticed say that you did encode something and the gui was at front and you did encode something for some odd reason it would restore back to where it was (i'm not saying bring to front i don't think) it's more about it minimizing after its done when :(

[stax76]

the languages options i might of mistaken for the title which was always set as the language as the title i think if no stream name is set maybe use the language so it isn't blank ?
(audio edit > stream name > "%language_english%") << i'm unsure if i ever set this or not but i did notice this (this is from 1.1.8 yet in 1.3.1.5 the stream name is blank by default)
here's a picture

I compared the source code that generates the command line, what was changed is in case of a empty title StaxRip adds a space character because MP4Box writes otherwise the gpac version to the title. The default title was empty a short test showed so you must have set the language with a macro.

MP4Box has too many shortcomings that I gave up spending resources on it but I'm open for suggestions.

"Autocrop sometimes hangs depending on source file and source filter. In case it hangs uncheck the crop filter or disable it in the options."

the last part i would say is wrong or maybe a bug as if the user does disable it in the options it doesn't disable the autocrop checking thingy? which seems like a minor error of some sort as it doesn't disable it nor does respect that the user has set it to disable in the options.

the way i understand it maybe is like this....

default: auto crop check?
disable auto crop in options: doesn't run auto crop (the user did tell it disable in the options so it respected even if the crop filter is still ticked)
disable crop filter: nothing to do with cropping triggers (normal)


then you get how it works at the moment which seems to be more like

default: auto crop check?
disable auto crop in options: auto crop check runs (it isn't respect that the user has disabled it)
disable auto crop in options and untick crop filter: nothing to do with cropping triggers (now its respecting some sort of options guessing due to the crop filter being unticked)
disable crop filter: nothing to do with cropping triggers

I removed the log message. The option in the options dialog for auto crop was removed, the check box in the main dialog is now used to trigger auto crop, I hope this is sufficient.

Your description isn't very clear so sorry if I miss something, please try to describe it much clearer if you think it should be improved.

[cegy]

I compared the source code that generates the command line, what was changed is in case of a empty title StaxRip adds a space character because MP4Box writes otherwise the gpac version to the title. The default title was empty a short test showed so you must have set the language with a macro.

MP4Box has too many shortcomings that I gave up spending resources on it but I'm open for suggestions.



I removed the log message. The option in the options dialog for auto crop was removed, the check box in the main dialog is now used to trigger auto crop, I hope this is sufficient.

Your description isn't very clear so sorry if I miss something, please try to describe it much clearer if you think it should be improved.


yep this all seems fine don't forget you can use ""Autocrop sometimes hangs depending on source file and source filter. In case it hangs uncheck the crop filter." now the mp4 box suggestion i would say if the title isn't set just set it to the language of the audio maybe so it isn't blank ? (i know mp4 sucks :confused:)

[Fishman0919]

getting an error... trying to convert Big Hero 6 BluRay to mkv for my media player

http://i467.photobucket.com/albums/rr37/fishman0919/first_zpsqqscxukf.png (http://s467.photobucket.com/user/fishman0919/media/first_zpsqqscxukf.png.html)

http://i467.photobucket.com/albums/rr37/fishman0919/2_zpstmtvxksr.png (http://s467.photobucket.com/user/fishman0919/media/2_zpstmtvxksr.png.html)

[stax76]

yep this all seems fine don't forget you can use ""Autocrop sometimes hangs depending on source file and source filter. In case it hangs uncheck the crop filter." now the mp4 box suggestion i would say if the title isn't set just set it to the language of the audio maybe so it isn't blank ? (i know mp4 sucks :confused:)

I changed it writing a empty string instead of a blank, in this case MediaInfo don't show a Title property. If the user has a empty stream name then this should also be passed to the muxer, substituting something for a empty stream name is probably not a good idea. Adding a default stream name would of course be possible but it would effect all muxers and I don't know if it's a good idea, I don't think it was ever requested.

@Fishman0919

Please upload the log file to pastebin.com, enable pastebin's auto expire feature and send me the link as private message.

[Fishman0919]

@Fishman0919

Please upload the log file to pastebin.com, enable pastebin's auto expire feature and send me the link as private message.


Sent to PM

[stax76]

@Fishman0919

If you create a avs file with only Version() as content and open it in MPC x64, does it show version 1825?

[Fishman0919]

@Fishman0919

If you create a avs file with only Version() as content and open it in MPC x64, does it show version 1825?

Nope

http://i467.photobucket.com/albums/rr37/fishman0919/test_zpszgmisrev.png (http://s467.photobucket.com/user/fishman0919/media/test_zpszgmisrev.png.html)

I reinstalled and then uninstalled AviSynth_260 again... then reinstalled AviSynth+_r1825.

Now it can't render the file. there's no AviSynth.dll in SysWOW64

[stax76]

You can install and use AviSynth x86 2.60 and AviSynth+ x64 r1825 in parallel, x86 is installed to SysWOW64, x64 is installed to System32, MPC x86 loads AviSynth from SysWOW64, MPC x64 loads AviSynth from System32. A x64 executable can only load x64 DLLs so StaxRip x64 can only load AviSynth+ x64 and AviSynth+ x64 can only load x64 plugins. You can install AviSynth 2.60 but you don't have to but you have to install the AviSynth version that StaxRip includes, this 4MB installer contains only AviSynth+ x64 and no C++ runtimes. The order in which you install the AviSynth versions should not matter. StaxRip checks however if AviSynth x64 is installed so there might be something broke on your system.

edit:

here is a new wiki page with a cleaner explanation:

https://github.com/stax76/staxrip/wiki/Scripting-Engine

[GatorGuy]

Stax (or anyone else familiar). I have a Sandy Bridge Intel CPU, but a Nvidia GTX960 recently added (for encoding purposes). What I didn't realize at the time, HEVC hardware accelerated H.265 seems geared toward real-time encodes. I've gotten great results doing X265 encodes on slow / quality settings, but they take a week!

Is there a way to create a command line for NVENC (or GTX960 in general) to maximize the GPU Video Engine to do a super high-quality / slower encode? I'd assume this has something to do with the difference between software and hardware encoding, but I'd think there would be some way to tap that horsepower and get similar results to CPU encoding, just hopefully at a slightly faster speed (I could care less about real-time encoding, I just don't want it to take a week!).

I'd appreciate any advice -- command line examples or alternatives to maximize the GTX960 in high-quality / lower file size encodes. I love Staxrip. It's the only software that has been rock solid in support for NVENC encoding including HEVC. Just too darn fast / too big of files for low-loss encodes.

[JohnLai]

Stax (or anyone else familiar). I have a Sandy Bridge Intel CPU, but a Nvidia GTX960 recently added (for encoding purposes). What I didn't realize at the time, HEVC hardware accelerated H.265 seems geared toward real-time encodes. I've gotten great results doing X265 encodes on slow / quality settings, but they take a week!

Is there a way to create a command line for NVENC (or GTX960 in general) to maximize the GPU Video Engine to do a super high-quality / slower encode? I'd assume this has something to do with the difference between software and hardware encoding, but I'd think there would be some way to tap that horsepower and get similar results to CPU encoding, just hopefully at a slightly faster speed (I could care less about real-time encoding, I just don't want it to take a week!).

I'd appreciate any advice -- command line examples or alternatives to maximize the GTX960 in high-quality / lower file size encodes. I love Staxrip. It's the only software that has been rock solid in support for NVENC encoding including HEVC. Just too darn fast / too big of files for low-loss encodes.

Unfortunately, the HEVC encoding block by Nvidia NVENC doesnt support B-Frame and B-pyramid.
Thus, there is no way of getting high quality encode with lower file size.

[GatorGuy]

Unfortunately, the HEVC encoding block by Nvidia NVENC doesnt support B-Frame and B-pyramid.
Thus, there is no way of getting high quality encode with lower file size.

Ewww, that's no fun. Thank you though John.

[NikosD]

Rigaya is shooting again, this time even with two new versions in a week!

Latest QSVEncC v2.06 adds API v1.15 support, HEVC encoding for Skylake and MPEG2 encoding for all.

Also, it adds audio encoding/ bitrate.

The check routines have added report for HEVC encoding parameters, audio encoders/decoders and muxers/demuxers

[Lupissimo]

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.

[stax76]

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:

http://avisynth.nl/index.php/AviSynth%2B#AviSynth.2B_x64_plugins

in the profile editor you can add a profile like so:

yadif =
LoadCPlugin("D:\Temp\Downloads\yadif_1.7_x64_asm\yadif\yadif.dll")
yadif()

I believe it works only on Win7 and not on Win8 or higher, that's why I did not include it, I hope somebody fixes it, I'm not 100% sure however, I'll retry once Win10 is released officially.

[dejong12]

RgTools.dll cannot be found, while RemoveGrain is selected, even though RgTools does exist in the Apps subfolder.

[telarium]

Unfortunately, the HEVC encoding block by Nvidia NVENC doesnt support B-Frame and B-pyramid.
Thus, there is no way of getting high quality encode with lower file size.

Is this a hardware limitation or something to be added to the NVENC API?

I'm seeing encoding speed increases on orders of magnitude with a 980 ti.

[JohnLai]

Is this a hardware limitation or something to be added to the NVENC API?

I'm seeing encoding speed increases on orders of magnitude with a 980 ti.

No idea, only Nvidia know about how the black box NVENC works. Developer only makes do with nvenc documentation published by nvidia.

When NV_ENC_CAPS_NUM_MAX_BFRAMES is used to probe the b-frame support, NVENC HEVC/H265 responded with 0.

Current documentation states only H264 encoding supports B-Frame. The same enum responded with max b-frame of 4 for H264 encoding.

B-Pyramid is never supported since the inception of NVENC.

[JohnLai]

@NikosD,
What I had done ;
Just installed Win10, Secondary active Intel HD Graphic 4000 using default win10 drivers. (not using headless display workaround since win8 onwards support direct access to second gpu)
Main display is using GTX970. LAVfilters is set as default directshow handler using Win7DSFilterTweaker_5.9.
At lavfilter, set Intel Quicksync for hardware decoder.

Staxrip source = DSS2 or directshow.
Drag and drop H264 8bit Lvl 4.1 compliant video into staxrip.
Start transcode video.
For some reason I not sure of......instead of usual 250fps I got when using win7 (with the headless display workaround), win10 only gives out 128-140fps.
Switching to Copy-Back (using main display GTX970) at lavfilter for win10, I can get 250fps.

GPUz graph shows when Quicksync decoder is being used, Intel HD4000 gpu load is at average 50% with gpu core clock stuck at 350Mhz most of time with little bit jump to 650Mhz.
*No resizing filter is being used*
When in win7 before, this wasn't the case whereby gpu core clock run at max 1050mhz with 99% load.

Strangely, if I use handbrake QSV, I can get 300-320fps.

So, @NikosD, does your HD4000(ivy) or HD4400,4600 (haswell) exhibits the same problem?

[NikosD]

Hello.

I don't own an Ivy CPU I only have HD 4600 (Core i7 4790-Haswell) and HD 2000 (Core i5 2400-SandyBridge)

With a Win 10 x64 - HD 4600@1500MHz - Drivers 4256 (latest) I get these results:

StaxRip x64 1.3.1.5 beta with QSVEncC v2.00 beta 11 - default settings for both apps
LAV filters 0.65.36
Test file: 1920 x 1080 - H.264@L4.1 - 11.1Mbps

DSS2 LAV QS: ~167fps GPU@max 1500MHz ~67%
DSS2 LAV CB: ~177fps GPU@max 1500MHz ~70%

StaxRip in HW decode mode: ~242fps GPU@max 1500MHz ~80%

OS is not recognized by QSVEncC version and a lot of instability in HW decode mode. It drops to 200fps sometimes.

Changed to QSVEncC v2.05, but besides OS recognition, nothing changed to the results.

Using latest QSVEncC v2.06 performance dropped a lot.

QS: 155 fps
CB: 161 fps
HW: 201 fps

[JohnLai]

I see....so, this issue might be unique to HD4000 series.
Hmm.....Guess I have to wait intel to release proper Ivy Bridge gpu driver for win10. Doesnt seem to have one right now.

Your QS,CB and HW results are similar with mine except my intel igpu utilization is a bit weird.

Oh well, cant do much now.

Thanks for the reply,NikosD.

[NikosD]

If you use Chrome with Google translator or Bing translator you can visit QSVEncC site and see that there is a specific problem with Ivy, if I understood correctly the translation.

There is also a QSVEncC v2.0.7 version which I think it fixes a problem with Ivy, but you have to search a little in the comments of the QSVEncC posts.

Or you can email rigaya and ask him directly about Ivy.

[JohnLai]

If you use Chrome with Google translator or Bing translator you can visit QSVEncC site and see that there is a specific problem with Ivy, if I understood correctly the translation.

There is also a QSVEncC v2.0.7 version which I think it fixes a problem with Ivy, but you have to search a little in the comments of the QSVEncC posts.

Or you can email rigaya and ask him directly about Ivy.

Okay....got it. Will do.....Thanks. ^.^

[NikosD]

A few more changes to latest QSVEncC v2.08

Added the option to control the async depth of the QuickSync pipeline and renamed the -lookahead-ds to -la-quality.

The most important addition is the isolation of the three functions of the QuickSync HW.

DECode, ENCode, VPP

Now with latest version, you can use the HW DEC and HW VPP but using the -c raw option you can output Y4M after DEC and VPP and pipe it to x264/x265 or other encoder, for the final encoding.

So, you can use QuickSync HW for HW DEC and HW VPP, but use a SW encoder, for encoding.

You can use any combination of DEC, ENC, VPP HW functions of QuickSync and not strictly all of them.

[JohnLai]

Generally I do this ;

QSV decode my decrypted BD contents ---> VPP resize ----> NvEnc H265.

Balance between speed and quality. XD

EDIT: The only sad part is the rigaya QSV encoder doesnt hybrid accelerate 8bit H265 stuff. So, sometime, I need to use i3-4330 igpu hd4600 to decode HEVC content using LAVfilter hybrid DXVA before piping it to Nvencc (GTX 960).
If use gtx 960 to do the decoding and encoding, the framerate tanks too much.

[NikosD]

QSV decode my decrypted BD contents ---> VPP resize ----> NvEnc H265.



How do you do that ?
Can you describe it ?


EDIT: The only sad part is the rigaya QSV encoder doesnt hybrid accelerate 8bit H265 stuff.


QSVEncC can HW decode H.264/MPEG2/ HEVC (8bit only)

You must you the -avqsv option to do that.

[JohnLai]

How do you do that ?
Can you describe it ?



QSVEncC can HW decode H.264/MPEG2/ HEVC (8bit only)

You must you the -avqsv option to do that.

....Not sure how am I suppose to explain using staxrip.....but the command is quite simple as you mentioned....

In case if the attachment too blurry, the command I use is :

QSVEncC64.exe --avqsv --output-res 560x304 --input-file "FF7.H264" -o - -c raw | NVEncC --y4m --codec h265 --level 4.1 --bframes 0 --ref 5 --cqp 20:23:25 -i - -o "FF7.H265"

Turn out QSV VPP resizing is quite fast.....from 1920x1080 to 560x364. (Only when using win7...)

Originally, I used QSVencc "--NV12" command, but "-c raw" command output it to YV12. So, it is pointless to specify --nv12.

But, nvencc converts YV12 ---> NV12 again.
This make me wonders why "-c raw" output to YV12 even though I explicitly set --NV12 only for it to be converted to YV12.
Waste of color conversion cycle during nvencc encode.

Hmmmm.....how to use the avspipemod again? I should have save the list of commands somewhere in my pc.........
So, NikosD, any suggestion to stax76 for afforementiond commands using avisynth or avspipemod? XD

EDIT: the current test video i use is dvd resolution video 720x480 downscale to 560x364. Just showing the QSV is doing the resizing during decoding stage before sending the data for nvenc

EDIT: The issue with HD4000 for win10 as I mentioned. In the past before OS upgrade, the QSV decode + VPP resizing from 1080 to 720 should be encode around 250 to 300fps when I was using win7. But since upgrading to win10, I got weird QSV decoding result as shown at second attachment. The igpu clock stucks at 650Mhz for most of time even with super low CPU utilization at temperature of 55Celcius. So, this is not throttling caused by high temperature. As shown in the attachment, win10 average QSV decode + VPP resize + Nvencc encode results in average 84fps. In win7 before, the igpu clock can reach 1.15 GHz. What a pity. *Ignore the red QSVencc finished with error. I was canceling the previous decode+encode task by pressing CTRL + C*

[NikosD]

Ah..OK.

The way you replied in your previous post, made me think you've been doing that for years! :)

So, you are based on latest QSVEncC in order to do it because it has the flexibility to allow different encoder than QuickSync, while using QuickSync decoder and VPP.

Now, it's clear.

You were too fast in adopting and using the new version and you tricked me.

[JohnLai]

Ah..OK.

The way you replied in your previous post, made me think you've been doing that for years! :)

So, you are based on latest QSVEncC in order to do it because it has the flexibility to allow different encoder than QuickSync, while using QuickSync decoder and VPP.

Now, it's clear.

You were too fast in adopting and using the new version and you tricked me.

(?_?) Perhaps I should clarify.
Previously, I was using full QSV decode + vpp resize (1080 to 720) + QSV encode video at high bitrate with fps of 250-300fps. Then DSS Lavfilter QSV decoded the resized video + Nvenc encode to HEVC = final output (350-400fps).

A problematic go/work-around because cpu based resizing filter tanks the fps too much until it takes too way long to complete.

In fact, it is way faster if I do a full QSV decode + vpp resize + QSV encode, finally using DSS LAVfilter QSV for decoding and nvencc for encoding to HEVC.

*Remember my complaint about resizing performance issue? >.<

Thus, the bottleneck in encoding fps falls with my GTX 970 and 960 because DSS lavfilter QSV can decode the resized video faster than nvenc can encode to hevc.

I setup a simple script to do the decoding and encoding process TWICE. Quality is compromised a bit though.
But, clean install of win10 right after upgrading from win7 caused everything to go missing including my previous script to do the decoding and encoding process twice. (I recalled I did use avspipemod for something to repeat the transcode process twice)

Yesterday, you told me about rigaya just released new version of qsvencc, so I played around with the -c raw option and y4m output.

So, I ended up with the command;
QSVEncC64 --avqsv --output-res 560x304 --input-file "FF7.H264" -o - -c raw | NVEncC --y4m --codec h265 --level 4.1 --bframes 0 --ref 5 --cqp 20:23:25 -i - -o "FF7.H265"

But, due to my weird intel HD4000 issue on win10, you will notice my average fps with rigaya latest version of QSVencc (2.08) of QSV decode + VPP resize (1080--->720) + Nvenc encode directly is mere 84fps. However, my dvd resolution video 720x480 resizes to 560x304 transcode process results in 357 to 360fps.

Ironically, with afforementioned 84fps result, I could get better transcoding fps using cpu based resizer instead. (-.- Even GTX970 copyback DXVA lavfilter, bicubic resize and Nvenc encode (hevc) can provide 150-160fps)

[stax76]

Looks like Skylake CPUs and boards are now available. :)

[NikosD]

Desktop Skylake is not simply a failure or just a big failure.

It's a fraud.

[stax76]

What's the the problem? I was reading in forums that people are not impressed because there are little gains but as far as I know there are at least some improvements like a H265 encoder and a better GPU, also the new motherboards have various improvements.

[NikosD]

After the initial shock of reviews with the low performance desktop Skylake CPU, I wouldn't call that processor a big failure.

I would call it a fraud.

Because how else could I call a CPU, which is slower in gaming and discrete card performance than a 2 generations older CPU (Haswell) ?

Also, in IPC is slower in some cases than the previous generation Broadwell (check Anandtech's review)

The iGPU performance is about 20% - 25% faster than Haswell and a lot, lot slower than iGPU of Broadwell.

The last significant point of sales for Skylake and HTPC is HEVC transcoding.

But even that, they made it wrong!

No HW acceleration of 10bit HEVC and no HDMI 2.0 - which means no BluRay UHD support.

This is the result of no competition and the monopoly of desktop CPUs.

I have written a lot of times recently that we need back AMD and we need it now.

I hope my next system to be based on an AMD processor, but I won't change if AMD is not competitive.

[Groucho2004]

Desktop Skylake is not simply a failure or just a big failure.

It's a fraud.
I think Intel have dropped the ball because there is no competition. Between 2003 and 2006, AMD were kicking Intel's butts with their Athlon line and Intel was really under pressure. Once they introduced their C2D, AMD started to fade and has not recovered since.

[NikosD]

Exactly.

Intel is like a monopoly and Skylake is the raw result of no actual competition.

Core 2 Duo hit hard AMD and SandyBridge finished it forever (?)

We have to pray day and night for AMD to bring something good with Zen cores...

[ShamisOMally]

Whelp, hate to say it but this outright refuses to work on Windows 10

*EDIT* Got it working after manually resetting all options and deleting all settings folders

[lojelo]

Hi everyone

Would like to thank everyone for any help with this small issue.

Now I have been using version 1.2.0.0 because of a view options I still use like field - deinterlace and also the option to save the bitrate at 256.

I convert only old vhs tapes and try and keep the audio bitrate the same rate as the dvd recorder records at. I have tried the just mux option but when I do this audio seems to go out of sync! so I use the edit option and set it at (AC3) 256k with Normalize unticked and the audio is perfectly fine all the time.

So going back to why I have come here for help and advice is when I am using my vob cutting software, which is Boilsoft video splitter well this is the reason why I don't use the latest version.

The problem is when I install the latest version it corrupts the Boilsoft software any vob file I try to open just fails!! I think it's something to do with the newer version of Avisynth rev. 2.

Anyone got any idea why this could be messing about with Boilsoft.

Thanks

Lojelo

[burfadel]

Skylake is pretty dismal considering that you go from Haswell --> Haswell Refresh --> Broadwell --> Skylake. Intel have pushed back the next CPU which is known as Cannonlake until the end of 2017, with the successor to Skylake now being Kaby Lake. So, in terms of Intel, they really have stagnated. I hope AMD Zen brings something special. With the desktop processors there is currently an APU and a FX (maybe under a different name) processor series planned. The APU will likely max out at four true cores (plus Intel like hyperthreading making 8 concurrent threads) + GPU, with the FX processor being 8 true cores (16 threads). The price difference may not be as much as it may sound either, as the GPU cores are just replaced with more CPU cores.

Depending on how things turn out, there may be advantages to getting the APU over the FX processor. The first is if there is an increased uptake in HSA programming, the second is if AMD bring in load balancing between the AMD APU and a discrete AMD card (this is NOT the same as the feature in DirectX 12, as it will work with any DirectX 11 or 12 workload). In any case, I really hope it just doesn't equal Intel performance, but is actually faster. Only if it is faster will Intel actually be kicked into gear again! Even if AMD Zen matches Intel performance, there is Zen+ the following year which has a further 10 percent performance boost.

[ShamisOMally]

Burf: The problem with Skylake is so far everyone is reporting its slower than Haswell, just it takes far less power to run.

Which is like getting a smaller more power efficient truck when the last one was bigger/faster, but used more gas.

*EDIT* How do I disable Staxrip from asking me for a template?

If I encode one file, then want to encode another one, I have to restart the whole program every time, otherwise it bugs me for a template when I try to import video

Is there a way to avoid/disable this? Or do I just have to keep restarting the program if I want to do a new batch of files?

[stax76]

Burf: The problem with Skylake is so far everyone is reporting its slower than Haswell, just it takes far less power to run.

Which is like getting a smaller more power efficient truck when the last one was bigger/faster, but used more gas.

*EDIT* How do I disable Staxrip from asking me for a template?

If I encode one file, then want to encode another one, I have to restart the whole program every time, otherwise it bugs me for a template when I try to import video

Is there a way to avoid/disable this? Or do I just have to keep restarting the program if I want to do a new batch of files?

If you restart the default template is loaded so when the dialog asks for a template instead of restarting you can choose the default template.

Would like to thank everyone for any help with this small issue.

Now I have been using version 1.2.0.0 because of a view options I still use like field - deinterlace and also the option to save the bitrate at 256.

I convert only old vhs tapes and try and keep the audio bitrate the same rate as the dvd recorder records at. I have tried the just mux option but when I do this audio seems to go out of sync! so I use the edit option and set it at (AC3) 256k with Normalize unticked and the audio is perfectly fine all the time.

So going back to why I have come here for help and advice is when I am using my vob cutting software, which is Boilsoft video splitter well this is the reason why I don't use the latest version.

The problem is when I install the latest version it corrupts the Boilsoft software any vob file I try to open just fails!! I think it's something to do with the newer version of Avisynth rev. 2.

Anyone got any idea why this could be messing about with Boilsoft.

I guess it's a bug in the Boilsoft software, you could try to contact Boilsoft.

[ShamisOMally]

Thanks Stax.

[spida_singh]

Hi Guys

Any idea what the following error would mean?

+
------------------------------------------------------------
Environment
------------------------------------------------------------

StaxRip x64 : 1.3.1.5
OS : Windows 10 Pro
Language : English (United Kingdom)
CPU : Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
GPU : Intel(R) HD Graphics 4000
LAV Filters : LAV Filters 0.65

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

D:\Simi 21st.m2ts

General
ID : 0 (0x0)
Complete name : D:\Simi 21st.m2ts
Format : MPEG-TS
File size : 35.6 GiB
Duration : 3h 11mn
Overall bit rate mode : Variable
Overall bit rate : 26.7 Mbps
Maximum Overall bit rate : 26.7 Mbps

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.2
Format settings, CABAC : Yes
Format settings, ReFrames : 2 frames
Codec ID : 27
Duration : 3h 11mn
Bit rate mode : Variable
Bit rate : 24.9 Mbps
Maximum bit rate : 26.3 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 50.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.240
Stream size : 33.3 GiB (93%)

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Codec ID : 129
Duration : 3h 11mn
Bit rate mode : Constant
Bit rate : 448 Kbps
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Compression mode : Lossy
Delay relative to video : 9ms
Stream size : 613 MiB (2%)


------------------------------------------------------------
Process M2TS file using eac3to
------------------------------------------------------------

"D:\StaxRip_x64_1.3.1.5_beta\Apps\eac3to\eac3to.exe" "D:\Simi 21st.m2ts" -progressnumbers

TS, 1 video track, 1 audio track, 3:11:16, 50p
1: h264/AVC, 1080p50 (16:9)
2: AC3, 5.1 channels, 448kbps, 48kHz, 8ms

------------------------------------------------------------
Demux M2TS using eac3to
------------------------------------------------------------

"D:\StaxRip_x64_1.3.1.5_beta\Apps\eac3to\eac3to.exe" "D:\Simi 21st.m2ts" 2: "D:\Simi 21st temp files\Simi 21st ID2 Invariant Language (Invariant Country).ac3" -progressnumbers

TS, 1 video track, 1 audio track, 3:11:16, 50p
1: h264/AVC, 1080p50 (16:9)
2: AC3, 5.1 channels, 448kbps, 48kHz, 8ms
a02 Extracting audio track number 2...
a02 A remaining delay of +8ms could not be fixed.
a02 Creating file "D:\Simi 21st temp files\Simi 21st ID2 Invariant Language (Invariant Country).ac3"...
Video track 1 contains 573802 frames.
eac3to processing took exactly 2 minutes.
Done.

Start: 20:51:15
End: 20:53:16
Duration: 00:02:00


------------------------------------------------------------
Index LWLibav
------------------------------------------------------------

"D:\StaxRip_x64_1.3.1.5_beta\Apps\ffmpeg\ffmpeg.exe" -i "D:\Simi 21st temp files\Simi 21st.avs"

ffmpeg version N-72623-g7495e72 Copyright (c) 2000-2015 the FFmpeg developers
built with gcc 4.9.2 (GCC)
configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libdcadec --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmfx --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-lzma --enable-decklink --enable-zlib
libavutil 54. 26.101 / 54. 26.101
libavcodec 56. 41.101 / 56. 41.101
libavformat 56. 34.100 / 56. 34.100
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 16.101 / 5. 16.101
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 1.100 / 1. 1.100
libpostproc 53. 3.100 / 53. 3.100
Input #0, avisynth, from 'D:\Simi 21st temp files\Simi 21st.avs':
Duration: 03:11:16.04, start: 0.000000, bitrate: N/A
Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 1920x1080, 50 fps, 50 tbr, 50 tbn, 50 tbc
At least one output file must be specified

Start: 20:53:16
End: 20:55:11
Duration: 00:01:54


------------------------------------------------------------
AviSynth Filters
------------------------------------------------------------

LWLibavVideoSource("D:\Simi 21st.m2ts")

------------------------------------------------------------
AviSynth Properties
------------------------------------------------------------

source frame count : 573802
source frame rate : 50.000000
source duration : 03:11:16.0400000
target frame count : 573802
target frame rate : 50.000000
target duration : 03:11:16.0400000

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

General
Complete name : D:\Simi 21st temp files\Simi 21st ID2 Invariant Language (Invariant Country).ac3
Format : AC-3
Format/Info : Audio Coding 3
File size : 613 MiB
Duration : 3h 11mn
Overall bit rate mode : Constant
Overall bit rate : 448 Kbps

Audio
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Duration : 3h 11mn
Bit rate mode : Constant
Bit rate : 448 Kbps
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 613 MiB (100%)


------------------------------------------------------------
x264
------------------------------------------------------------

"D:\StaxRip_x64_1.3.1.5_beta\Apps\x264\x264.exe" --crf 20 --output "D:\Simi 21st temp files\Simi 21st_out.h264" "D:\Simi 21st temp files\Simi 21st.avs"

avs [info]: 1920x1080p 0:0 @ 50/1 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
x264 [info]: profile High, level 4.2

------------------------------------------------------------
Error x264
------------------------------------------------------------

x264 failed with exit code 255

avs [info]: 1920x1080p 0:0 @ 50/1 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
x264 [info]: profile High, level 4.2


Start: 21:54:26
End: 21:54:26
Duration: 00:00:00


M2TS created by Powerdirector, im trying to convert to a smaller mkv

Cheers

[stax76]

@spida_singh

You can try to ask in the x264 thread what error code 255 means. Possibly the source filter causes the error because transport streams often cause problems, a possibly solution might be to remux to mkv or to demux to h264 elementary stream.

[JohnLai]

@stax76

Is it possible to design an option to take advantage of rigaya QSVencc -c raw command, y4m output, --avqsv (decoding section), --output-res (qsv resizing is the fastest) before piping to other encoder (encoding section) such as nvenc or even x264 later?

[stax76]

@JohnLai

I'll think about it, I've not worked much on StaxRip recently but ordered Skylake hardware which should get me back into StaxRip.

[ShamisOMally]

@JohnLai

I'll think about it, I've not worked much on StaxRip recently but ordered Skylake hardware which should get me back into StaxRip.

I'll give you a free game right now, cause while I have no cash currently on hand, I got some steam games from previous sales.

Its fucking worth it IMO, Staxrip has saved me so many headaches vs using other gui's that beg like a 5 year old at the store asking for a toy

[amango]

I tried the latest version. I usually convert in batches. If I want to convert files with subtitles (Anime) these are also included in the destination files, however the latest version don't set any default flags into the destination files and I don't see any options how I can activate them. The destination files now plays without any activated subtitles in MPC, I have to activate them manually every time, or to remux each single file.

That worked well in older verions of StaxRip, I never had to set any default flags for subtitles, they were always activated in the destination files. So the old versions basically took over the data from the old files and also the prefered default subtitle track data.

[Anakunda]

Hi stax76, just trying to use DGDecNV index (.dgi) as source and having problem with latest beta. I have meet same problem in the past but can't remind how it was solved.
In Filters Source=Automatic
In Tools>Apps>Plugins>AviSynth>DGDecodeNV Location is set to DGDecodeNV.dll instance (64b), Status OK
In Tools>Settings>Source Filters dgi is assigned DGource (default)

Source section in filter profiles:
[Source]
DGSource = DGSource("%source_file%")
DGSourceIM = DGSourceIM("%source_file%")
DirectShowSource = DirectShowSource("%source_file%", audio = False)
LSMASHVideoSource = LSMASHVideoSource("%source_file%")
LWLibavVideoSource = LWLibavVideoSource("%source_file%")
AVCSource = AVCSource("%source_file%")%newline%Crop(0,0, -Width % 8,-Height % 8)%newline%ConvertToYV12()
FFVideoSource = FFVideoSource("%source_file%", cachefile = "%temp_file%.ffindex")
FFVideoSource(MT) = SetMTMode(5,2)%newline%FFVideoSource("%source_file%", cachefile="%working_dir%%source_name%.ffindex")%newline%AssumeFPS(%source_framerate_mediainfo%)%newline%Crop(0,0, -Width % 8,-Height % 8)%newline%ConvertToYV12()
MPEG2Source = MPEG2Source("%source_file%")%newline%Crop(0,0, -Width % 8,-Height % 8)%newline%ConvertToYV12()
AviSource = AviSource("%source_file%", Audio = False)
DSS2 = DSS2("%source_file%")
Advanced | DGSource(interlaced) = DGSource("%source_file%",deinterlace=1)
Advanced | MPEG2Source Deblocked = MPEG2Source("%source_file%", CPU=6)
FFAudioSource = FFAudioSource("%source_file%")
LSMASHAudioSource = LSMASHAudioSource("%source_file%")
LWLibavAudioSource = LWLibavAudioSource("%source_file%")

After picking my .dgi source I get unexpectedly "Choose preferred source filter" dlg - offering Automatic, FFVideoSource, LWLibavVideoSource, DSS2, ffms2 but not DGSource.
So I choose Automatic and StaxRip tries all source filters from the dlg in this order, ending up with LWLibavVideoSource (FFVideoSource fail)....recreates own index from .h264.
The situation is same if I force Filters>Source as DGSource (and same filter picker)
Looks like StaxRip doesn't want to use DGDecNV tho paths to plugin properly set (DGDecNV build 2049). Any ideas?

[stax76]

@Anakunda

I wanted to test it but my license don't work, I reinstalled Windows often recently (migrated to Win10 and currently migrating to skylake hardware but having trouble with bad RAM), the problem is the URL for license key generation is dead (http://neuron2.net/licensing.html).

@amango

You mean file batch mode? In normal mode there is a new data view in the muxing dialog, this data view has columns to set default and forced flags.

@ShamisOMally

Jesus, last game I played and can remember by name was Half Live! Thanks for the offer. There are three games I want to try at some time: GTA V, Metal Gear Solid V and Mindcraft.

[sneaker_ger]

@Anakunda
the problem is the URL for license key generation is dead (http://neuron2.net/licensing.html).
He moved his site:
http://rationalqm.us/
http://rationalqm.us/licensing.html

[Anakunda]

@Anakunda

I wanted to test it but my license don't work, I reinstalled Windows often recently (migrated to Win10 and currently migrating to skylake hardware but having trouble with bad RAM), the problem is the URL for license key generation is dead (http://neuron2.net/licensing.html).


Okay I'll try to wait, If I recollect right previous issue was obolete DGsource version. Upgraded to suggested build and apparently new build doesn't solve anything.
From the temporary script I see StaxRip tries DGdecNV but fails. Playing .dgi files using 32bit DGDecodeNV works.

Edit: ffplay encode_Source.avs is playable! Problem must be on StaxRip side.
LoadPlugin("C:\Program Files (x86)\DGDecNV\x64 Binaries\DGDecodeNV.dll")
DGSource("H:\video\(workset)\MadMaxFuryRoad\source.dgi")

[stax76]

@Anakunda

first please try if it also happens with a recent build, I tried it and it works here.

http://www.mediafire.com/download/kb4a641slubzmob/StaxRip_x64_2015.08.18.7z

https://onedrive.live.com/redir?resid=604D4754F64B0ABC!1606&authkey=!AF8gcK4OyAy5UTg&ithint=file%2c7z

[dejong12]

Stax, two questions:

1. Did you see my post two pages back about RGTools?
"RgTools.dll cannot be found, while RemoveGrain is selected, even though RgTools does exist in the Apps subfolder."
EDIT: This now works on the build you posted before me.

2. When using DGSource, after trying to load a video into StaxRip, it fails and gives me the following error:
System exception - Access Violation
(C:\PATH_TO_VIDEO\video.avs, line 2)

DGSource("C:\PATH_TO_VIDEO\video.dgi")
Any idea what's going on? It does this for every video I feed to StaxRip. I've got the latest DGDecNV 2049 set up correctly.
EDIT: This is still happening on the build you posted before me.

[stax76]

1. Did you see my post two pages back about RGTools?
"RgTools.dll cannot be found, while RemoveGrain is selected, even though RgTools does exist in the Apps subfolder."

I don't remember it, I tried RemoveGrain for both AviSynth and VapourSynth, it works and my plugin directories have only the default plugins included with AviSynth and VapourSynth.

When using DGSource, after trying to load a video into StaxRip, it fails and gives me the following error:

There was a updated 2049 build so re-downloading might help, when StaxRip ask for the location don't forget you need the x64 build.

[dejong12]

There was a updated 2049 build so re-downloading might help, when StaxRip ask for the location don't forget you need the x64 build.
I've downloaded the latest build just half an hour ago again to try and that build gives me the error. I've also used the x64 binaries.

[stax76]

Can MPC x64 open the avs file?

[videoh]

Just FYI...

AVG 2015 has started blocking DGIndexNV 64-bit. You may need to add an exception for it.

[dejong12]

Can MPC x64 open the avs file?
Nope, MPC-HC x64 can't render the file.

Just FYI...

AVG 2015 has started blocking DGIndexNV 64-bit. You may need to add an exception for it.
I don't use any antivirus except for Windows Defender.

[stax76]

Does MPC show the same error message and can VirtualDub x64 open it?

[Anakunda]

When using DGSource, after trying to load a video into StaxRip, it fails and gives me the following error:
System exception - Access Violation
(C:\PATH_TO_VIDEO\video.avs, line 2)

DGSource("C:\PATH_TO_VIDEO\video.dgi")
Any idea what's going on? It does this for every video I feed to StaxRip. I've got the latest DGDecNV 2049 set up correctly.
EDIT: This is still happening on the build you posted before me.

That's the same what's happening to me, having latest DgTools and paths set correctly also. I assume StaxRip rejects the output for some reason.

Just FYI...

AVG 2015 has started blocking DGIndexNV 64-bit. You may need to add an exception for it.
I confirm that's not A/V issue, using no A/V, beyond that as I wrote feeding the temporary script StaxRip creates into ffplay64, the source video can pass through to screen.

[stax76]

Are you sure you re-downloaded 2049 and set the path to the correct x64 DLL? There was a memory access violation raised by DGDecodeNV, this memory access violation was only happening under special circumstances like running Windows 8 or higher but not Windows 7, it was happening only in certain clients like .NET applications or MPC but not in all clients, VirtualDub x64 was not affected for instance. Donald has fixed it and re-uploaded 2049. If you absolutely cannot get it working then please send a log file.

[dejong12]

Does MPC show the same error message and can VirtualDub x64 open it?
MPC shows the same message. VirtualDub x64 opens the .avs fine.

Are you sure you re-downloaded 2049 and set the path to the correct x64 DLL? There was a memory access violation raised by DGDecodeNV, this memory access violation was only happening under special circumstances like running Windows 8 or higher but not Windows 7, it was happening only in certain clients like .NET applications or MPC but not in all clients, VirtualDub x64 was not affected for instance. Donald has fixed it and re-uploaded 2049. If you absolutely cannot get it working then please send a log file.
I'm 100% sure I've downloaden the latest 2049 and correctly set up the path to the x64 binaries.

I can't send you a log file because StaxRip does not create one. When it asks to try using another source, it fails by giving the same error. No video is then imported into StaxRip.

[Groucho2004]

MPC shows the same message. VirtualDub x64 opens the .avs fine.
What does AVSMeter (x64) have to say?

[dejong12]

What does AVSMeter (x64) have to say?
AVSMeter works just fine.
http://i.imgur.com/6sDba41.png

I'm using Windows 10 btw, I don't know if that matters?

[Anakunda]

Virtualdub64, AvsMeter64, ffmpeg64 work with DG NV source for me also and also no log is created on testing preferred filter

[Groucho2004]

I'm using Windows 10 btw, I don't know if that matters?No idea, wait for stax to figure it out. :)

[stax76]

the last changed date of the DLL must be exactly 2015.05.10

http://forum.doom9.org/showthread.php?p=1721117#post1721117

[dejong12]

the last changed date of the DLL must be exactly 2015.05.10

http://forum.doom9.org/showthread.php?p=1721117#post1721117
Mine is from 19-03-2015. I've downloaded it again to reconfirm and that one also shows 19-03-2015. The .exe has a later date: 27-05-2015.

[Groucho2004]

Mine is from 19-03-2015. I've downloaded it again to reconfirm and that one also shows 19-03-2015. The .exe has a later date: 27-05-2015.
Confirmed. Stax, you'll have to notify Don Graft on his forum. Maybe he mixed things up with the latest slipstream.

[amango]

@amango

You mean file batch mode? In normal mode there is a new data view in the muxing dialog, this data view has columns to set default and forced flags.


Yes I mean file batch mode. I made a profile that just should encode any file to H265.

I select many files to convert in file batch mode. All this files have one subtitle track (Anime).

The current version of StaxRip just remux the subs with this command in batch file mode.

-default-track 0:0

What I need is that all the converted files should be remuxed using this command

-default-track 0:1

And the older version of StaxRip I used never had that problem, it successfully took over the subtitles status from the old files.

EDIT: MKVMerge 8.3 does not seem to be compatible with StaxRip 1.3.1.5

[diloume]

Hello,

is the CBR mode working under nvidia h265 coding ? Since version 1.3 The software always impose a bitrate..

What can-i do ?

Thank for answer..

[diloume]

Sorry, I found the answer of my question..

[videoh]

Confirmed. Stax, you'll have to notify Don Graft on his forum. Maybe he mixed things up with the latest slipstream. That's right, it got messed up on a subsequent DGIndexNV slipstream.

The corrected package is now online.

[stax76]

Yes I mean file batch mode. I made a profile that just should encode any file to H265.

I select many files to convert in file batch mode. All this files have one subtitle track (Anime).

The current version of StaxRip just remux the subs with this command in batch file mode.

-default-track 0:0

What I need is that all the converted files should be remuxed using this command

-default-track 0:1

And the older version of StaxRip I used never had that problem, it successfully took over the subtitles status from the old files.

EDIT: MKVMerge 8.3 does not seem to be compatible with StaxRip 1.3.1.5

iirc mkvmerge enables default flags if nothing is specified, that's probably what you were getting before. If somebody can tell me the logic mkvmerge uses I consider to apply the same logic (or an alternative).

[dejong12]

That's right, it got messed up on a subsequent DGIndexNV slipstream.

The corrected package is now online.
Thank you, it works now!

EDIT:
Now that DGDecNV is working again with StaxRip, I face a problem with 1080p AVC videos.
The DG log file in the temp folder correctly shows 34492 total frames, but the imported file only shows 34478 frames when I preview the video and after the encoding,
effectively missing 14 frames in the beginning of the video.
All the other sources handle these kind of videos correctly. What's going on?

[videoh]

The DG log file in the temp folder correctly shows 34492 total frames, but the imported file only shows 34478 frames when I preview the video and after the encoding,
effectively missing 14 frames in the beginning of the video.
All the other sources handle these kind of videos correctly. What's going on? Try it manually without staxrip for debugging. Just make a basic script with DGSource() and then open the script in VirtualDub. How many frames do you see? If it is still off, then please post the DGI file.

Also, where are the missing frames, at the beginning or the end?

[dejong12]

Try it manually without staxrip for debugging. Just make a basic script with DGSource() and then open the script in VirtualDub. How many frames do you see? If it is still off, then please post the DGI file.

Also, where are the missing frames, at the beginning or the end?
The frames are missing at the beginning.
Opening the video in DGIndexNV.exe directly shows that frames are missing.
However, after demuxing it says 34492 total frames. And opening the file in StaxRip with other sources, the preview shows 34493 frames.
VirtualDub says 34478 frames.

[videoh]

Please post a link to the unprocessed source file. If it is too large then please cut the first 200MB using DGSplit. Also, I asked for the DGI file. Did you miss that?

There are several possibilities to explain what is happening but I cannot guess which applies. It's up to you to provide the requested materials if you want your issue to be analyzed/resolved. Thank you.

Also, if this occurs without staxrip then it would be better to open a thread in the DGIndex subforum so as not to clutter this thread.

[dejong12]

Please post a link to the unprocessed source file. If it is too large then please cut the first 200MB using DGSplit. Also, I asked for the DGI file. Did you miss that?

There are several possibilities to explain what is happening but I cannot guess which applies. It's up to you to provide the requested materials if you want your issue to be analyzed/resolved. Thank you.
Yep, I missed that, my apologies. Here (https://www.dropbox.com/s/iijwvvme52hn994/test.rar?dl=0) is the .rar file with the video (split to 200mb) and the .dgi from the original video.

[videoh]

Thanks, investigating...

[videoh]

Did you cut an MKV with DGSplit? Sorry, that is not a valid operation. I suppose I shouldn't assume people know this. You can validly do a binary split only on a stream file, not one with global headers.

In any case, there aren't frames missing at the start. It's just that the 3 leading B frames have been replaced with the first decodable frame. Given that, I'm going to need the whole file. Your DGI indicates something fishy at the end of the file, and so I will need the whole file.

Is your capture device giving you MKV, or did you get this somewhere else?

[dejong12]

Did you cut an MKV with DGSplit? Sorry, that is not a valid operation. I suppose I shouldn't assume people know this. You can validly do a binary split only on a stream file, not one with global headers.

In any case, there aren't frames missing at the start. It's just that the leading B frames have been replaced with the first decodable frame. Given that, I'm going to need the whole file. Your DGI indicates something fishy at the end of the file, and so I will need the whole file.

Is your capture device giving you MKV, or did you get this somewhere else?
Before doing anything wrong again, I should split the .264 file?

My capture device gave me a .ts file (or when using WMC .wtv). I cut the series with VideoRedo.

EDIT: When cutting the .ts file in VideoRedo and remuxing it back into .ts, DGIndexNV shows the first frame correctly. So it looks like something is going wrong when remuxing it into .mkv.

[videoh]

I need the TS file that came out of VideoRedo. The entire TS file please.

If VideoRedo makes an MKV then give me the entire MKV file. Thanks.

[dejong12]

I need the TS file that came out of VideoRedo. The entire TS file please.

If VideoRedo makes an MKV then give me the entire MKV file. Thanks.
Read my edit above your post. I can send both if you want.

[videoh]

I told you that the fishiness is at the end of the file but you keep going on about the start of the file.

If you want me to help you, please give me the TS file that comes out of VideoRedo. Then I can try remuxing to MKV etc. to try to see what is happening.

Usually, the frame count discrepancy comes because of a bad cut at the end, and the loss of a few frames at the end is inconsequential.

[dejong12]

I told you that the fishiness is at the end of the file but you keep going on about the start of the file.

If you want me to help you, please give me the TS file that comes out of VideoRedo. Then I can try remuxing to MKV etc. to try to see what is happening.

Usually, the frame count discrepancy comes because of a bad cut at the end, and the loss of a few frames at the end is inconsequential.
I've cut 2 minutes from the series and put both .ts and .mkv in the .rar for you to compare. Both are created with VideoRedo.

Link (https://mega.nz/#!9ERUFT5Y!T2q732KsgKIEcz3AvAcSseJwOm0o8SwiBlSgCv8UYTI)

[videoh]

I can't help if you don't give me what I ask for. I'll say it one more time. I need the entire TS file for the episode that comes out of VideoRedo. If you can't or won't provide it then you are on your own.

In any case, your link just gives me a blank page.

[dejong12]

I can't help if you don't give me what I ask for. I'll say it one more time. I need the entire TS file for the episode that comes out of VideoRedo. If you can't or won't provide it then you are on your own.

In any case, your link just gives me a blank page.
Link (https://www.dropbox.com/s/4b7ej6sbnviguts/episode.ts?dl=0)

[videoh]

Sweet, thank you! Downloading...

[videoh]

If you demux the AVC ES from the TS and then convert that to MKV with mmg.exe everything is fine and acts exactly the same as if you index the TS.

If you feed the TS directly into mmg.exe then everything gets hosed, and frames are lost at the start.

Conclusion: Your guess was correct. mmg.exe is not properly reading the TS. It is not unusual for applications to fail miserably at parsing interlaced transport streams. Apparently mmg.exe is yet another example. You should demux the audio and video, apply a delay correction to the audio as needed (or do it when muxing MKV), and then mux them into an MKV.

[dejong12]

If you demux the AVC ES from the TS and then convert that to MKV with mmg.exe everything is fine and acts exactly the same as if you index the TS.

If you feed the TS directly into mmg.exe then everything gets hosed, and frames are lost at the start.

Conclusion: Your guess was correct. mmg.exe is not properly reading the TS. It is not unusual for applications to fail miserably at parsing interlaced transport streams. Apparently mmg.exe is yet another example. You should demux the audio and video, apply a delay correction to the audio as needed (or do it when muxing MKV), and then mux them into an MKV.
Thank you for investigating the issue and providing a solution! I'll raise the issue at the creator of MKVToolnix.

[videoh]

My pleasure. Good luck with your projects and thank you for bringing to light the bad version I had online.

[stax76]

I think mkvmerge uses time codes so it works fine for playback but is unusable for encoding. dsmux muxes it better allowing for encoding afterwards, unfortunately it fails on certain sources and it's discontinued.

[dejong12]

I think mkvmerge uses time codes so it works fine for playback but is unusable for encoding. dsmux muxes it better allowing for encoding afterwards, unfortunately it fails on certain sources and it's discontinued.
I've just tried to remux the .ts into .mkv with dsmux and I can confirm that the resulting .mkv works correctly in DGDecNV, so there's a problem with mkvmerge. And my apologies for hijacking the thread.

[sneaker_ger]

I'm not seeing what you are seeing.
Downloaded episode.ts, used "mkvmerge -o episode.mkv episode.ts" (mkvmerge 8.3.0).
Opened using lwlibavvideosource(), both files show exactly 34500 frames. Mkv timecodes are 100% regular.

[dejong12]

I'm not seeing what you are seeing.
Downloaded episode.ts, used "mkvmerge -o episode.mkv episode.ts" (mkvmerge 8.3.0).
Opened using lwlibavvideosource(), both files show exactly 34500 frames. Mkv timecodes are 100% regular.
It only happens when using DGSource as a source filter.

[sneaker_ger]

Maybe videoh can add his knowledge about what exactly is wrong with the mkvmerge output to your bug report:
https://github.com/mbunkus/mkvtoolnix/issues/1409

What does DGSource do when a stream does not start on a recovery point?

[stax76]

I've just tried to remux the .ts into .mkv with dsmux and I can confirm that the resulting .mkv works correctly in DGDecNV, so there's a problem with mkvmerge. And my apologies for hijacking the thread.

It's not really a bug or something as far as I can see, it's more a limitation and a better implementation is rather unlikely because it should be very hard to do even for a master programmer like Mosu, you can create a ticket but don't expect much.

[dejong12]

Stax, another "problem". I've imported yadif x64 into the latest StaxRip version, but it's not deinterlacing correctly. I can see some color (de)blending happening. Neither deinterlacer works 100% correctly. When using the last x86 version of StaxRip (1.2.2.2) and using the same encoding settings with yadif, the deinterlacing works as it should, deinterlacing the source file 100% correctly.

[videoh]

I'm not seeing what you are seeing.
Downloaded episode.ts, used "mkvmerge -o episode.mkv episode.ts" (mkvmerge 8.3.0).
Opened using lwlibavvideosource(), both files show exactly 34500 frames. Mkv timecodes are 100% regular. I used 7.9.0.

[videoh]

It only happens when using DGSource as a source filter. Nah. I simply used mmg on your TS. DGSource didn't enter at all. And you said you have no issue when using dsmux to create the mkv.

[videoh]

What does DGSource do when a stream does not start on a recovery point? Any frames before the first decodable one are replaced with copies of the first decodable frame.

[dejong12]

Nah. I simply used mmg on your TS. DGSource didn't enter at all. And you said you have no issue when using dsmux to create the mkv.
I'm just saying that when you convert the uploaded TS to MKV (not with DSMux) and import that MKV into StaxRip the problem only shows when using DGSource. The other source filters handle the MKV fine.

[stax76]

muxing ts to mkv using mkvmerge is probably not a good idea if you want to encode afterwards, it should get async with other source filters too, not necessarily always but probably often, I experimented a while with it with little success, in this time I found out about dsmux.

[Groucho2004]

muxing ts to mkv using mkvmerge is probably not a good idea if you want to encode afterwards
I was wondering about that - why re-mux the .ts to mkv?

[stax76]

I was wondering about that - why re-mux the .ts to mkv?

because most tools fail on ts producing async output, dsmux at least sometimes helps to get around this, people without DGDecNV license or other payware like TS-Doctor or VideoRedo don't have great choice. At one point I wanted to code a TS demuxer myself, I would probably done it already, the problem is I practically never have TS sources personally so my motivation working on it is rather limited.

[Ajvar]

stax76, can you please tell me, does this 64 bit version provides video comparison feature (aka Codec comparison) and if you ever make a separate app for this? Last version I used was 1.2.2.2 beta and you wrote that you updated that coparison afterwards however I never could successfully download your Alphas of x86.

Thank you.

EDIT: It is working fine after installing Avisynth+.

[dejong12]

Videoh, could you take a look at what the creator of mkvmerge had to say about the issue?
https://github.com/mbunkus/mkvtoolnix/issues/1409

[videoh]

I'll look into it later today.

[videoh]

You gave me the full episode file episode.ts. It is fine in every way. It starts with SPS/PPS as it should. If you index it with DGIndexNV you get all the frames.

But Moritz is talking about a file test.ts. I don't know what that is and so cannot comment on Moritz's findings. You should give him the same file you gave me, or give me the same file you gave him.

[Fadeout]

I'm getting crazy trying to figure this out, so someone please help...

I'm trying to convert a 1080i 50fps file into something my TV player can read, so a 1080p at 30fps (or 25 to better match the reduction?).

I have a slow CPU, but a 750 Ti videocard, so I'm guessing the best option I have is to use NVENC, right? I'm using StaxRip x64 and the first problem I had is that by default the program doesn't come with Yadif, and so I couldn't properly deinterlace the image.

Now, the thing is, since then I managed to find a 64 bit version of Yadif and so deinterlace the image, but consider these two conversions:

1- did not use Yadif, so the original source, but with SelectEven. so I get a "progressive" 1080p 25fps, because I take only 1 field.
2- used Yadif, getting a progressive 1080p 25fps.

The problem is that the first video, with deinterlacing FORCED on a PC media player produces a result that is IMMENSELY better and smoother, even if the two files are a similar size.

But of course I can't do that on a normal player I need to use, so with the first file I only get an interlaced image.

This doesn't make a lot of sense to me. There should be a way to code the file as a "real" progressive by retaining the quality of the first file. How is it possible that a 1080p 25fps forced to deinterlace during playback gives substantially better results than a 1080p 25fps that was instead properly deinterlaced during the encoding, and with same file size?

Also, is it normal I barely get 1.3x encoding speed on a E8400 CPU with a 750 Ti? Are there better options than FFVideoSource? I can manage to have better speed (around 1.5) with MediaCoder because it offers different deinterlacers that seems to perform better (including Yadif, that is immensely slow on StaxRip. So I'm looking for suggestions on what the best options are.

[Fadeout]

Also, a conversion from 1080i 50fps to 1080p 50fps, using yadif reduces the smoothness of the movement.

Whereas the 1080i 50fps converted without previously deinterlacing to 1080p 25fps, when deinterlacing forced in the player is MUCH smoother than 1080p 50fps.

So that doesn't make any sense, there's something wrong that loses that information in the process and there must a way to make a better conversion.

EDIT:
Deinterlacing with MPC-HC and MadVR = super smooth
Deinterlacing with MPC-HC and without MadVR = super smooth
Deinterlacing with default Windows Media Player = super smooth
Deinterlacing with VLC and Yadif = loses smoothness (tried all other deinterlacers, same result)

The fourth case is what I get with my encodes. So what the hell are WMP and MPC-HC using to deinterlace that produces so much better results?

Is there a way to edit the file so to turn it from progressive to interlaced, so to force the deinterlacing normally? Because that's my whole problem: I have a perfect file that says it progressive but that would look perfect when forcing interlacing, but of course my TV player can't deinterlace unless the video is properly flagged as interlaced. So I'd need the option to change that flag in the file and turn on deinterlacing.

[NikosD]

A new QSVEncC v2.10 is out mainly for Skylake.

It uses a new mode of HW encoding enabled only in Skylake which leverages the fixed-function HW during encoding, without the use of GPU EUs.

This is the only mode supported by Nvidia from the beginning of their HW encoders and this is the mode of all HW decoders (AMD, Nvidia, Intel)

The old mode is PG-mode (Processor Graphics) and the new one is FF-mode (fixed function)

It can be used for H.264 only, as I read.

For the first time in HW encoders, it uses a programmable adaptive rate control in order to trigger a second pass if needed to achieve the targeted bitrate, without using any CPU or GPU processing, only fixed function HW.

The reason Intel added this mode is for "power saving", because the GPU load is extremely low, but it is possible that performance maybe drops that way and perhaps quality too.

We need a Skylake to test it.

Intel calls this mode as a low latency, real time encoding.

Actually, I had asked Intel about that a few months ago:
https://software.intel.com/en-us/forums/topic/542414

[Yups]

Isn't QSVEncC japanese or chinese?

[NikosD]

Japanese

[Yups]

Without japanese reading skills how do do think could someone try it out?

[NikosD]

The help file which lists all possible commands is in English and you can print it out in your screen via the CLI.

All the CLI switches are in English of course.

No need to know Japanese.

If you need to browse his site, just use Chrome with the auto translation.

[Yups]

Staxrip is using QSVEnc 2.00 beta12 or can I manually copy a new QSVEnc version into the folder?

[NikosD]

Yes you can do that and copy an updated version of QSVEncC, but without GUI support of the new functionality of the updated version.

We have to "push" Frank (stax76) to update the QSVEncC GUI to include the latest functionality of QSVEncC CLI.

[Yups]

My browser blocks QSVEncC 2.10 download because of a virus (possibly a false alarm). I better wait for an updated Staxrip.

[videoh]

Videoh, could you take a look at what the creator of mkvmerge had to say about the issue?
https://github.com/mbunkus/mkvtoolnix/issues/1409 Did you lose interest in this?

[stax76]

Yes you can do that and copy an updated version of QSVEncC, but without GUI support of the new functionality of the updated version.

We have to "push" Frank (stax76) to update the QSVEncC GUI to include the latest functionality of QSVEncC CLI.

I'm working on it. ;)

[NikosD]

Nice!

So, you got your Skylake ? ;)

[stax76]

I've still problems with the new PC, I received new RAM modules (http://www.crucial.com/usa/en/bls4k4g4d240fsa) today, unfortunately the symptoms are still there, blank screen and error beep codes. 4 long beeps and one short beep, after the short beep it restarts. I don't know exactly what the error codes mean, the info I found is somehow vague, according to the Gigabyte website (http://www.gigabyte.com/products/product-page.aspx?pid=5496#sp) the bios is AMI.

[JohnLai]

I've still problems with the new PC, I received new RAM modules (http://www.crucial.com/usa/en/bls4k4g4d240fsa) today, unfortunately the symptoms are still there, blank screen and error beep codes. 4 long beeps and one short beep, after the short beep it restarts. I don't know exactly what the error codes mean, the info I found is somehow vague, according to the Gigabyte website (http://www.gigabyte.com/products/product-page.aspx?pid=5496#sp) the bios is AMI.

You mean exactly like this https://www.youtube.com/watch?v=QMvy403xMyQ ?

The video is for older socket 775, is the beep sound the same?

Just asking......have you clear CMOS?
Using 8 pins power (ATX_12V_2X4) for the CPU?
Try different RAM socket? (one RAM at a time?)
If you didn't install any RAM, does it still beep 3 long 1 short?
Are pins on the cpu socket itself in good condition?
Try reseating your CPU yet?

In any case, you better stick with gigabyte Qualified Vendors List (QVL) for RAM.
Did your previous RAM is listed by gigabyte QVL?
Cause your current Crucial Module P/N. is not listed at QVL.

[stax76]

The long beeps are different, I think I found the problem, whenever I use RAM socket 1 or 3 the error occurs, socket 2 and 4 are OK, dual channel needs 1+2 or 3+4 so I absolutely have to return the motherboard.

[JohnLai]

The long beeps are different, I think I found the problem, whenever I use RAM socket 1 or 3 the error occurs, socket 2 and 4 are OK, dual channel needs 1+2 or 3+4 so I absolutely have to return the motherboard.

Before that....wanna try update the bios first?
There is an update for the board for RAM compatibility.......

[stax76]

Before that....wanna try update the bios first?
There is an update for the board for RAM compatibility.......

Sounds like a good idea.

edit:

Did not help. :(

[JohnLai]

Sounds like a good idea.

edit:

Did not help. :(


Hmm.....go RMA the board...

Still, it is weird running in single channel mode works while dual channel doesnt.
Either your CPU cooler shorting out something behind the board. (cpu cooler metal backplate for instance? Try using stock cooler from haswell,ivy bridge?)
Or the CPU doesnt have proper contact with the socket pins (integrated memory controller in the cpu)

[stax76]

First I tried the new motherboard/CPU/RAM in my current PC which uses a old Scythe CPU cooler with quick mounting system not using a backplate. After this failed I realized hardware problems happen way to often so I decided that from now on I don't change my current PC but always build a second PC whenever I change the motherboard, the second/new PC uses a Thermalright HR-02 Macho Rev. B cooler with mounting system using a backplate. I'll receive another board (GA-Z170X-UD3) in two days...

[Yups]

QSVEnc 2.11 is available with HEVC support for SKL.

[NikosD]

An interesting comparison of HW encoders (HEVC, H.264) vs SW encoders (x265, x264) in terms of performance and quality using QSVEncC v2.11

It looks like that on Skylake both QSV H.264 modes - PG and FF - have the same speed and QSV HEVC encoding has half speed of QSV H.264.

Compared to SW encoders, QSV HEVC is 2x faster than x264 and 12x (!) faster than x265.

Quality pictures and performance numbers here:
http://rigaya34589.blog135.fc2.com/blog-entry-673.html

[Yups]

His picture quality tests are nonsense nevertheless. 1080p is required at least with some proper video material and not some cartoon crap where low bitrate does fine.

[stax76]

I'm getting a mess of artifacts using QSV HEVC encoding, was anybody more successful?

[NikosD]

Anime is extremely popular to the East and makes a lot of sense there.

[Schattenspieler]

But the contentual popularity does not positivley affect (-> reduce) the general lack of detail in animes compared to real HD source material. And for that reason they could be used as an example (among others), but if you want to show the general quality of encondings, you would have to use different image sources, e.g. others with high details level. Otherwise such a comparison of image quality is not senseless but to some degree pointless. Just my 2 cent though …

[Yups]

I'm getting a mess of artifacts using QSV HEVC encoding, was anybody more successful?


How did you use HEVC and what driver do you have installed?


But the contentual popularity does not positivley affect (-> reduce) the general lack of detail in animes compared to real HD source material. And for that reason they could be used as an example (among others), but if you want to show the general quality of encondings, you would have to use different image sources, e.g. others with high details level. Otherwise such a comparison of image quality is not senseless but to some degree pointless. Just my 2 cent though …


Exactly this, plus for a better comparison something bigger than 720p.

[stax76]

How did you use HEVC and what driver do you have installed?

I did not use special settings and tried two different modes and two different sources with same results.


QSVEncC (x64) 2.11 by rigaya, build Aug 26 2015 20:34:15
based on Intel(R) Media SDK Encoding Sample 6,0,0,98947
avi reader: enabled
avs reader: enabled
vpy reader: enabled
avqsv reader: enabled [H.264/AVC, HEVC, MPEG2]

Environment Info

OS : Windows 10 (x64)
CPU: Intel Core i5-6600K @ 3.50GHz [TB: 3.89GHz] (4C/4T)
RAM: Used 2708 MB, Total 8069 MB
GPU: Intel HD Graphics 530 (24EU) 1150MHz (10.18.15.4274)

Media SDK Hardware API v1.16
Supported Enc features:
Supported Vpp features:
Media SDK Software unavailable.


I installed the driver from the Gigabyte site:

15.40.5.1.64.4274
2015/08/19


The Intel driver from the Intel site is older:

15.40.4.64.4256
8/12/2015

[Yups]

I will try once there is Intel H265 build into the GUI.

[stax76]

Hey everybody,

I uploaded a new release, it does not have big new features but many small improvements and updated tools of course, sorry if I missed some posts.


StaxRip x64 1.3.1.6 beta (2015-08-30)


New: HEVC and MPEG-2 encoding modes added to Intel encoder
New: KNLMeansCL plugin added
New: Added option for fixed bitrate even though using a fixed bitrate is not recommended. It was added because over the years it was requested dozens of times. StaxRip will show a warning telling to rather use quality mode and constrain the maximum data rate if necessary
New: Added option to process a audio profile using the context menu in the main dialog
Tweak: Play feature adds resize filter to VapourSynth play script if the source PAR is non 1:1
Tweak: Added clear feature to audio file context menu to easily remove a audio file
Tweak: Added screen bounds magnet docking feature
Tweak: When jobs are completed StaxRip activates now the main window again like it did before but now StaxRip checks if a player is in the foreground and prevents activation if true, it works with MPC, VLC and MediaMonkey, other players might be added on request
Tweak: ProjectX and dsmux are always enabled by default but StaxRip checks only if Java and Haali is installed in case of ProjectX and dsmux are actually executed
Tweak: Improved DGDecNV and DGDecIM integration
fix: filenames with characters like ä ü ö not working VapourSynth
fix: fullscreen mode in preview was not working in Windows 10 because the task bar was in front
Update: x264 r2597
Update: x265 1.7+433
Update: AVSMeter 2.1.0
Update: ffmpeg 2015-08-28
Update: qaac 2.52
Update: NVEncC 1.09
Update: QSVEncC 2.11
Update: MKVToolNix 8.3.0



https://github.com/stax76/staxrip/releases

I will try once there is Intel H265 build into the GUI.

The new release has a new profile 'Intel H.265' but I did not reset the profiles so the new profile is only available if the profiles are manually reset.

[Yups]

Just a quick test on one video, I can say no artifacts issue for me with HEVC.

[stax76]

Which CPU and driver do you use?

[dejong12]

NVEncC 1.10 was released 12 days ago by the way.

[stax76]

Seems the artifacts I get with the Intel HEVC encoder happen only in the first 10 seconds so I can make a codec comparison.

NVEncC 1.10 was released 12 days ago by the way.

I've updated it locally now. I like that it has a VapourSynth reader, I believe it's the first and maybe the only encoder (besides QSVEncC) with VapourSynth reader, this should allow me to remove the piping solution making the copy command line and execute command line feature in the options dialog work again.

[JohnLai]

Hey everybody,

I uploaded a new release, it does not have big new features but many small improvements and updated tools of course, sorry if I missed some posts.



https://github.com/stax76/staxrip/releases




No "QSV --avqsv --output-res -o - -c raw | NVEncC --y4m"?

T_T

[NikosD]

Hey everybody,

I uploaded a new release, it does not have big new features but many small improvements and updated tools of course, sorry if I missed some posts.

https://github.com/stax76/staxrip/releases




Nice work and thanks for the fixes.

A few things regarding the new version:


BUGS


1) This HEVC .ts clip (and a few others like this) crashes badly the default (automatic) video source (LWLibav).


https://www.sendspace.com/file/49zvqy

It gives this error and closes StaxRip x64.



Exception

Arithmetic operation resulted in an overflow.

System.OverflowException: Arithmetic operation resulted in an overflow.
at StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean isNotEncoding, VideoFilter preferredSourceFilter) in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:line 2097



Also it crashes the LSMASH video source giving this error but without closing the app (I can select another source)



------------------------------------------------------------
Error opening source
------------------------------------------------------------

System exception - Access Violation
(D:\Video\Out of BD spec clips\L5.1\Beyond 1080p\4K (3840x)\H.265\140512_hm130_4s_sao_dbf temp files\140512_hm130_4s_sao_dbf_Source.avs, line 2)

LSMASHVideoSource("D:\Video\Out of BD spec clips\L5.1\Beyond 1080p\4K (3840x)\H.265\140512_hm130_4s_sao_dbf.ts")



The other video source options (non-commercial) FFVideo and DSS/DSS2 work fine.



2) Unfortunately, I wasn't so lucky regarding some 10bit HEVC files.

For example this file (and a lot of others) can't be opened by any non-commercial video sources:

https://www.sendspace.com/file/8vv7qp



3) This clip can be handled without problems, using the "single-file" mode of StaxRip x64 by eac3to automatically (no user selection)

https://www.sendspace.com/file/vb152k

BUT when I choose the "batch-file" mode selecting this clip along with others, at the final conversion the audio part is missing completely (without errors) (!)

The video part is OK, only the audio is missing.


Requests for QSVEncC GUI:


1) I think it would be easy and probably useful to add, in your GUI, the following parameters:

--level <string> set codec level, default auto

--profile <string> set codec profile, default auto

H.264: Baseline, Main, High
HEVC : Main
MPEG2: Simple, Main, High


2) The three different codecs that QSVEncC supports right now (H264, H265, MPEG2) and probably VP8 and MJPEG that is going to support in the next versions, don't share the same encoding features.

For example there is no ICQ encoding mode for MPEG2.

You can check the encoding features available, by executing the command --check-features or directly from the GUI by selecting "Check Features" from the arrow (it's not working using latest v2.11 for x64, only for x86 - I have already mentioned that to the developer and he is going to fix it in the next QSVEncC version)

I wonder how difficult would be to adjust the QSVEncC GUI according to the codec selection and change the name of the template to single "Intel H.265/H.264/MPEG2" instead of different templates "Intel H.264" and "Intel H.265"


Missing updates:

MediaInfo is at 0.7.76 version.

[Yups]

Seems the artifacts I get with the Intel HEVC encoder happen only in the first 10 seconds so I can make a codec comparison.


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.





2) The three different codecs that QSVEncC supports right now (H264, H265, MPEG2) and probably VP8 and MJPEG that is going to support in the next versions, don't share the same encoding features.

For example there is no ICQ encoding mode for MPEG2.

You can check the encoding features available, by executing the command --check-features or directly from the GUI by selecting "Check Features" from the arrow (it's not working using latest v2.11 for x64, only for x86 - I have already mentioned that to the developer and he is going to fix it in the next QSVEncC version)

I wonder how difficult would be to adjust the QSVEncC GUI according to the codec selection and change the name of the template to single "Intel H.265/H.264/MPEG2" instead of different templates "Intel H.264" and "Intel H.265"




Lookahead doesn't work either with HEVC, I don't know if this is an Intel or QSVEnc limitation though.

[stax76]

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.

I tried 256 but it didn't help.

Generally my first impression of the Intel H.265 encoder isn't that good, both speed and quality is somehow disappointing. :(

No "QSV --avqsv --output-res -o - -c raw | NVEncC --y4m"?

I'll add it if it's not too much work, regarding the current piping solution, maybe it's better to keep it as option instead to remove entirely.

@NikosD

Thanks for investigating, I'll work on it.

[stax76]

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]

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]

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]

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]

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]

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]

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]

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]

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]

@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]

@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]

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]

@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]

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]

@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]

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]

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]

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]

@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]

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]

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]

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]

QSVEnc 2.12 has been released.

[burfadel]

Mediainfo v0.7.77 released.

[NikosD]

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]

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]

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]

I tried one sample with a few different settings, so far it looks good.

[stax76]

test build I promised:

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

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

[cegy]

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]

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]

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]

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]

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]

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]

@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]

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]

@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]

@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]

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]

It's in the 'Misc' section, I'll move it to the field section. :)

[NikosD]

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]

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]

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]

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]

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]

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]

@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]

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]

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

[Yups]

Latest QSVEncC fixes it. :)


Possibly because he switched to bframes 2 as new default. Because of this change the GUI needs an update.

GUI default says bframes 3
http://fs2.directupload.net/images/150905/yxnb4szj.png

Converted with bframes 2
http://fs1.directupload.net/images/150905/pua59wgl.png


Does anyone know what Ext. Features PerMBRC means?

[Yups]

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


According to the feature table Ext_BRC and MBBRC is supported in HEVC VBR bitrate mode. For some reason it doesn't work, no effect.

PerMBRC seems to be MBBRC by the way, doesn't work though.

[stax76]

Possibly because he switched to bframes 2 as new default. Because of this change the GUI needs an update.

Next build has it fixed.

[NikosD]

I’ve just read an older post regarding the first benchmarks of the new HW decoding mode of QSVEncC.

My older benchmarks:

1) Core i7 4790 – Win 8.1 x64 Pro – iGPU HD 4600@1.5GHz – Drivers 4206
StaxRip x64 (1.3.1.2)/ QSVEncC x64 (v2.00β3)

I used CQP encoding mode using the default value of 24 with Balanced target usage and everything else set to Auto (default)
I didn’t use Audio encoding (Just Mux option or Auto Pass-through)

H.264 – Eclectic-1080p clip – 11Mbps

StaxRip x64 QSV 301 fps


The new results:

2) Core i7 4790 – Win 10 x64 Pro – iGPU HD 4600@1.5GHz – Drivers 4256
StaxRip x64 (1.3.1.2)/ QSVEncC x64 (v2.00β3)

H.264 – Eclectic-1080p clip – 11Mbps

StaxRip x64 QSV 230 fps



3) Core i7 4790 – Win 10 x64 Pro – iGPU HD 4600@1.5GHz – Drivers 4256
StaxRip x64 (1.3.1.6)/ QSVEncC x64 (v2.12)


H.264 – Eclectic-1080p clip – 11Mbps

StaxRip x64 QSV 201 fps (!)


My goodness (!)

The rise of performance using the older drivers and older QSVEncC version is 100 fps -> 50 %.

I gain 35% using older drivers and 15% using older QSVEncC.

Intel has done a disastrous job with drivers but QSVEncC looses some power too.

[JohnLai]

Driver and the program itself?
I was expecting the driver to be the issue....didn't expect the program itself also one of the cause (30fps gone from using new QSVenc? wow...)

*Now that might explains the anomaly of the QSV decode + resizing (vpp) slowdown*

Someone gonna report these issue to Rigaya and Intel........(~.~ I leave the task to you, @NikosD)

[NikosD]

Of course I have already done that :) even from version v2.06 which has the same speed like v2.12

He knows it, but haven't managed to resolve it yet.

A lot of stuff has been added to v.200 onwards and he is continuously adding more things.

[Yups]

ICQ bitrate mode works much better in HEVC mode, faster and much better quality at the same bitrate.

VBR
http://abload.de/img/vbrkikr1.png


ICQ
http://abload.de/img/icqc9ko3.png

[RazorBurn]

Thanks stax for adding KNLMeansCL in StaxRip. Would it be possible to add Chroma Processing in KNLMeansCL for both AVS+ and VS in StaxRip?

Vapoursynth:
y = core.std.ShufflePlanes(clip, planes=[0], colorfamily=vs.GRAY).knlm.KNLMeansCL(device_type="GPU")
u = core.std.ShufflePlanes(clip, planes=[1], colorfamily=vs.GRAY).knlm.KNLMeansCL(device_type="GPU")
v = core.std.ShufflePlanes(clip, planes=[2], colorfamily=vs.GRAY).knlm.KNLMeansCL(device_type="GPU")
clip = core.std.ShufflePlanes([y, u, v], planes=[0, 0, 0], colorfamily=vs.YUV)

AVS+
Y=KNLMeansCL(device_type="GPU")
U=UToY8().KNLMeansCL(device_type="GPU")
V=VToY8().KNLMeansCL(device_type="GPU")
YToUV (U, V, Y)

Im mostly encoded Surveillance Videos with a cheap USB Webcam, the night time videos has a lot of Chroma noise..

[stax76]

Thanks stax for adding KNLMeansCL in StaxRip. Would it be possible to add Chroma Processing in KNLMeansCL for both AVS+ and VS in StaxRip?

Vapoursynth:
y = core.std.ShufflePlanes(clip, planes=[0], colorfamily=vs.GRAY).knlm.KNLMeansCL(device_type="GPU")
u = core.std.ShufflePlanes(clip, planes=[1], colorfamily=vs.GRAY).knlm.KNLMeansCL(device_type="GPU")
v = core.std.ShufflePlanes(clip, planes=[2], colorfamily=vs.GRAY).knlm.KNLMeansCL(device_type="GPU")
clip = core.std.ShufflePlanes([y, u, v], planes=[0, 0, 0], colorfamily=vs.YUV)

AVS+
Y=KNLMeansCL(device_type="GPU")
U=UToY8().KNLMeansCL(device_type="GPU")
V=VToY8().KNLMeansCL(device_type="GPU")
YToUV (U, V, Y)

Im mostly encoded Surveillance Videos with a cheap USB Webcam, the night time videos has a lot of Chroma noise..

I'm not sure if the current system is good for adding too much code, currently all filters are loaded on startup and all settings are stored in one settings file. Deserializing the settings file takes half of the startup time and everything is always loaded in memory. There is also the problem whenever I reset the filter profiles, customizations are lost. Before adding much filter code I should probably first think about if I can find a better design being more efficient in regard of startup time and memory consumption and with better usability not resetting customizations all the time. In the next release various new plugins will be added so the filter profiles must be reset again.

[cegy]

stax76 is there a minor bug with preview as if the user clicks on crop the video is smaller (which is normal/good) than the whole screen for the input video of say 1920x1080 yet... for preview its full screen (as in the whole screen is covered) even if the video res is set at a smaller res say 1280x720 etc.. ?
where i'm sure when you click on preview it shows you what the output should be filters/video res wise :o

p.s the filename_preview.avs even shows the resizing aswell i.e LanczosResize(1280, 720) but it doesn't make any differences

[RazorBurn]

I'm not sure if the current system is good for adding too much code, currently all filters are loaded on startup and all settings are stored in one settings file. Deserializing the settings file takes half of the startup time and everything is always loaded in memory. There is also the problem whenever I reset the filter profiles, customizations are lost. Before adding much filter code I should probably first think about if I can find a better design being more efficient in regard of startup time and memory consumption and with better usability not resetting customizations all the time. In the next release various new plugins will be added so the filter profiles must be reset again.

Im not rushing you on anything, thanks BTW..

Also a few milliseconds or seconds added to startup time is not a problem for me.. A lot of people using Premiere is Pro or Photoshop are already used to long startup times..

[ShamisOMally]

Staxrip 1.3.1.6 refuses to mux MKV's for me, I had to go back to 1.3.1.5

[JohnLai]

Of course I have already done that :) even from version v2.06 which has the same speed like v2.12

He knows it, but haven't managed to resolve it yet.

A lot of stuff has been added to v.200 onwards and he is continuously adding more things.

I see, have you told rigaya about the QSVenc '--avqsv -c raw' extreme slowdown when piping it to NVencc?

Using lavfilter DSS QSV decoder results in 200fps, but using '--avqsv' in conjunction with '-c raw' only result in 60-90fps.
*1080P H264 to HEVC without resizing.

I dont believe the copy-back penalty is that severe.

Staxrip beta has the option to use QSVEncc as decoder at Nvidia H.265 --> Encoder Options--->Advanced.

[NikosD]

I don't use nvencc, I don't have a recent Nvidia card, I can't reproduce all those.

You could reach him in his email explaining all these.

It's been a while since his last update.
Maybe he is interested in his new version to improve it.

[dejong12]

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.
I still have this problem, even after two Windows reinstalls (using Win 10). This also happens with .mkv so I think it'll happen with every container. I've deleted the settings file in ProgramData, but that didn't help. Making matters worse, StaxRip (using 09-09-2015 one) now crashes when it's done with DGIndexNV, but it's not leaving a crash file. So I can't use DGIndexNV. StaxRip also crashes when I try to manually open the .dgi in StaxRip. I've included the .dgi here (https://www.dropbox.com/s/d90meumneamcnly/Zwarte_Tulp-2130_20150906-15-10800000-1441567800.dgi?dl=0).

[stax76]

I still have this problem, even after two Windows reinstalls (using Win 10). This also happens with .mkv so I think it'll happen with every container. I've deleted the settings file in ProgramData, but that didn't help. Making matters worse, StaxRip (using 09-09-2015 one) now crashes when it's done with DGIndexNV, but it's not leaving a crash file. So I can't use DGIndexNV. StaxRip also crashes when I try to manually open the .dgi in StaxRip. I've included the .dgi here (https://www.dropbox.com/s/d90meumneamcnly/Zwarte_Tulp-2130_20150906-15-10800000-1441567800.dgi?dl=0).

Is the last write date of your DGDecodeNV.dll 2015-05-10? If not than that's the problem and re-downloading it will help.

[dejong12]

Is the last write date of your DGDecodeNV.dll 2015-05-10? If not than that's the problem and re-downloading it will help.
The date of that dll is 2015-05-10 actually. I redownloaded it before testing it again.

[stax76]

Without log file or error message I can't say much, did it work before on the same hardware, same OS and same graphics driver? Did you try things like test different file types, different source filters, test DGDecNV without any GUI, if it's not GUI related than you can also create a dedicated thread here or at DG's forum. I use DGDecNV myself and know that many StaxRip users are using it too so it's likely a problem with your system.

[dejong12]

Without log file or error message I can't say much, did it work before on the same hardware, same OS and same graphics driver? Did you try things like test different file types, different source filters, test DGDecNV without any GUI, if it's not GUI related than you can also create a dedicated thread here or at DG's forum. I use DGDecNV myself and know that many StaxRip users are using it too so it's likely a problem with your system.
I found out the error is related to nvcuda.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-09-15T23:36:11.000000000Z" />
<EventRecordID>235</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-LBA8HIM</Computer>
<Security />
</System>
- <EventData>
<Data>StaxRip.exe</Data>
<Data>1.3.1.7</Data>
<Data>55f0a322</Data>
<Data>nvcuda.dll</Data>
<Data>8.17.13.5582</Data>
<Data>55dc71ce</Data>
<Data>c0000409</Data>
<Data>000000000029c07c</Data>
<Data>1dc4</Data>
<Data>01d0f00f417ab513</Data>
<Data>D:\StaxRip x64 09-09-2015\StaxRip.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\nvcuda.dll</Data>
<Data>d007d03a-5dcb-4b79-8539-4cfc5141b3e8</Data>
<Data />
<Data />
</EventData>
</Event>

Windows 10 probably does not recognize StaxRip wanting to use the Nvidia graphics card (it worked before in Windos 8.1, gfx is 660M). Any idea what goes wrong?

[Jeroi]

Staxx do you believe to add sometime episode handling for DVD Backup prosess? You currently have bluray but DVD episodes or PGC chapters backup is needed here atleast. DVD Decypter handles PGC's in IFO mode but all episodes are needed to manually separate and then encoded with staxx...

[stax76]

Windows 10 probably does not recognize StaxRip wanting to use the Nvidia graphics card (it worked before in Windos 8.1, gfx is 660M). Any idea what goes wrong?

Sorry I don't have experience with mobile NVIDIA, you could try DG's forum.

Staxx do you believe to add sometime episode handling for DVD Backup prosess? You currently have bluray but DVD episodes or PGC chapters backup is needed here atleast. DVD Decypter handles PGC's in IFO mode but all episodes are needed to manually separate and then encoded with staxx...

Dealing with VOB is even for movies broken since there aren't reliable tools, with x64 the situation is even worse, it's possible but you have to know which tools to use and how to use them and it's a lot manual work.

Aren't episodes typically stored in separate titles? MakeMKV creates a separate file for each title by default but I believe MakeMKV has also a advanced mode that can deal with chapters.

[Jeroi]

I found out that I can do episodes backup with DVD Shrink in reauthor mode. It will store invidual vobs to harddisck from episode titles. How ever then is needed some labour to encode the vobs to smaller size. It would be nice to have all in one open dvd and backup episodes separately to mp4 format. Handbrake is supposed to work but I found out that it works only with some vobs that are in one large vob but if there is 4 separate vobs it will not handle the episodes rigth so I need to use some other app.

[stax76]

If every episode is a title then why not just use MakeMKV? You'll get one MKV file for each title effortless.

[Jeroi]

I report still that 2pass encoding mp4 is broken. It uses for passes werad bitrates up to 23000kbit whic makes huge filesizes...

[stax76]

I report still that 2pass encoding mp4 is broken. It uses for passes werad bitrates up to 23000kbit whic makes huge filesizes...

Which encoder?

For most problems I'll have to see a full log file which can be uploaded to www.pastebin.com, pastebin has a auto expire feature which should always be set to 30 days.

[dejong12]

Sorry I don't have experience with mobile NVIDIA, you could try DG's forum.
I found out the troublemaker. It's the Avisynth version (r1773) you included, which is causing the crashing. Installing the newer r1825 fixes it and I'm able to use StaxRip and DGIndexNV once more.

[videoh]

I found out the troublemaker. It's the Avisynth version (r1773) you included, which is causing the crashing. Installing the newer r1825 fixes it and I'm able to use StaxRip and DGIndexNV once more. Good to know. Thanks for the information, dejong12.

[Groucho2004]

I found out the troublemaker. It's the Avisynth version (r1773) you included, which is causing the crashing.
@stax
Huh? Is this (http://forum.doom9.org/showthread.php?p=1736650#post1736650) the one you included? Seriously? Have a look at the very next post in that thread and the one after that.

[dejong12]

Good to know. Thanks for the information, dejong12.
I found the cause by using my pc with Windows 10 which I know for sure works. I reinstalled Windows a few days ago and I was using the latest StaxRip version (09-09-2015) which has AS+ r1773 included. When I tried to index a file, DGIndexNV gave me an error about not supporting MPEG1, which was weird because the video was similar to the file I sent you a few weeks ago. I tried to index it with just DGIndexNV and that worked, but when I tried to import the resulting .dgi into StaxRip, StaxRip crashed. That was when I noticed I had installed the older r1773 version. So I tried r1825 and lo and behold, everything worked again.

[JohnLai]

Staxrip 1.3.1.6 refuses to mux MKV's for me, I had to go back to 1.3.1.5

Bump for this muxing bug.

[@stax76]

When I select the audio to 'Just Mux', the muxing stage will fail.
Using StaxRip_x64_2015-09-09.

[Jeroi]

H264 aac audio mp4 2pass encoding sets the weard bitrates on it's own. I cannot change bitrate even manually --bitrate 900 option to command the prosess to calculate 1pass and second pass in 900 bitrate.

Could you add to encoder options when 2pass selected the target bitrate box?

[stax76]

@all

Please don't forget posting the log file, I wrote it now also to my signature:

For StaxRip support please always post the log file to www.pastebin.com and enable auto expire after 30 days.

Bump for this muxing bug.

I had tested this too without having problems, please post the log file.

@stax
Huh? Is this (http://forum.doom9.org/showthread.php?p=1736650#post1736650) the one you included? Seriously? Have a look at the very next post in that thread and the one after that.

I used rev 1773 in a test release, on my sample clips DGDecNV didn't produce errors. Can you recommend a particular build?

H264 aac audio mp4 2pass encoding sets the weard bitrates on it's own. I cannot change bitrate even manually --bitrate 900 option to command the prosess to calculate 1pass and second pass in 900 bitrate.

Could you add to encoder options when 2pass selected the target bitrate box?

Looks OK here, there is a new option at:

main menu > Options > Misc > Use fixed bitrate

make sure this is zero so the value in the main dialog is used, also make sure you have no --bitrate entered as custom command line switch. I entered 941 in the main dialog and it was passed to x264 correctly and the x264 output was correct two.

Another factor is after audio encoding a video bitrate recalculation is happening adjusting the video bitrate to the bitrate of the audio output, I tested this also and it's still working. Without log file and more detailed description I can't tell much more.


------------------------------------------------------------
x264
------------------------------------------------------------

"D:\Projekte\GitHub\staxrip\bin\Apps\x264\x264.exe" --preset veryfast --pass 1 --bitrate 941 --stats "D:\Temp\Encoding\test temp files\test.stats" --output NUL "D:\Temp\Encoding\test temp files\test.avs"

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 Main, level 4.0
x264 [info]: frame I:16 Avg QP:28.35 size: 62235
x264 [info]: frame P:1429 Avg QP:34.42 size: 4251
x264 [info]: frame B:942 Avg QP:33.95 size: 576
x264 [info]: consecutive B-frames: 45.6% 3.7% 4.8% 45.9%
x264 [info]: mb I I16..4: 69.9% 0.0% 30.1%
x264 [info]: mb P I16..4: 10.5% 0.0% 0.0% P16..4: 11.6% 0.0% 0.0% 0.0% 0.0% skip:77.9%
x264 [info]: mb B I16..4: 0.4% 0.0% 0.0% B16..8: 1.8% 0.0% 0.0% direct: 0.7% skip:97.2% L0:43.5% L1:55.5% BI: 1.0%
x264 [info]: final ratefactor: 33.04
x264 [info]: coded y,uvDC,uvAC intra: 5.2% 27.5% 4.1% inter: 0.4% 1.9% 0.0%
x264 [info]: i16 v,h,dc,p: 36% 31% 23% 10%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 16% 22% 22% 8% 8% 5% 8% 4% 6%
x264 [info]: i8c dc,h,v,p: 70% 13% 12% 5%
x264 [info]: Weighted P-Frames: Y:0.6% UV:0.2%
x264 [info]: kb/s:764.69
encoded 2387 frames, 157.06 fps, 764.69 kb/s

Start: 16:30:07
End: 16:30:22
Duration: 00:00:15


------------------------------------------------------------
x264 Second Pass
------------------------------------------------------------

"D:\Projekte\GitHub\staxrip\bin\Apps\x264\x264.exe" --preset veryfast --pass 2 --bitrate 941 --stats "D:\Temp\Encoding\test temp files\test.stats" --output "D:\Temp\Encoding\test temp files\test_out.h264" "D:\Temp\Encoding\test temp files\test.avs"

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 High, level 4.0
x264 [info]: frame I:16 Avg QP:28.51 size: 51309
x264 [info]: frame P:1429 Avg QP:32.49 size: 5476
x264 [info]: frame B:942 Avg QP:35.70 size: 749
x264 [info]: consecutive B-frames: 45.6% 3.7% 4.8% 45.9%
x264 [info]: mb I I16..4: 18.5% 74.1% 7.4%
x264 [info]: mb P I16..4: 4.7% 5.8% 0.0% P16..4: 12.4% 2.4% 0.5% 0.0% 0.0% skip:74.3%
x264 [info]: mb B I16..4: 0.2% 0.2% 0.0% B16..8: 2.2% 0.3% 0.0% direct: 0.6% skip:96.4% L0:43.5% L1:54.3% BI: 2.2%
x264 [info]: 8x8 transform intra:56.8% inter:59.9%
x264 [info]: coded y,uvDC,uvAC intra: 19.1% 30.4% 4.1% inter: 0.5% 2.4% 0.0%
x264 [info]: i16 v,h,dc,p: 37% 32% 21% 9%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 13% 18% 54% 2% 3% 2% 3% 2% 3%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 15% 21% 17% 9% 11% 7% 9% 5% 7%
x264 [info]: i8c dc,h,v,p: 66% 15% 14% 5%
x264 [info]: Weighted P-Frames: Y:0.6% UV:0.2%
x264 [info]: kb/s:939.37
encoded 2387 frames, 274.08 fps, 939.37 kb/s

[JohnLai]

[@stax76]


Error Muxing using mkvmerge

Muxing using mkvmerge failed with error code 3

mkvmerge v8.3.0 ('Over the Horizon') 64bit
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.



StaxRip.ErrorAbortException: Muxing using mkvmerge failed with error code 3

mkvmerge v8.3.0 ('Over the Horizon') 64bit
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.


at StaxRip.Proc.Start() in D:\Projekte\GitHub\staxrip\General\Proc.vb:line 235
at StaxRip.MkvMuxer.Mux() in D:\Projekte\GitHub\staxrip\General\Muxer.vb:line 512
at StaxRip.MainForm.Encode() in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:line 2289
at StaxRip.MainForm.RunJobRecursive() in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:line 3583

[stax76]

@JohnLai

StaxRip raises a exception because exit code 3 is not mentioned in the mkvmerge documentation:

https://www.bunkus.org/videotools/mkvtoolnix/doc/mkvmerge.html#mkvmerge.exit_codes

I need always a full log file so I can see all parameters giving me hints to reproduce it.

Any other build, the best would be r1576 which is pretty stable. r1773 was pulled from Git and user Elegant hacked around in the code a bit because he thought he could solve the problem.

I can't use r1576 because I have features where ffmpeg use AviSynth+ and ffmpeg is not compatible with r1576, ffmpeg work only with more recent AviSynth+ builds.

[JohnLai]

@JohnLai

StaxRip raises a exception because exit code 3 is not mentioned in the mkvmerge documentation:

https://www.bunkus.org/videotools/mkvtoolnix/doc/mkvmerge.html#mkvmerge.exit_codes

I need always a full log file so I can see all parameters giving me hints to reproduce it.

Full log? I only saw one text file inside the folder created by staxrip. That one?

EDIT: Check your PM inbox.

[stax76]

Full log? I only saw one text file inside the folder created by staxrip. That one?

If there isn't a better log file then please post MediaInfo and a screenshot of the main dialog showing the used options.

[JohnLai]

If there isn't a better log file then please post MediaInfo and a screenshot of the main dialog showing the used options.

The log I pm-ed to you wasn't sufficient?

[Groucho2004]

I can't use r1576 because I have features where ffmpeg use AviSynth+ and ffmpeg is not compatible with r1576, ffmpeg work only with more recent AviSynth+ builds.
Right, I keep forgetting that. I guess you're stuck with r1825 for the time being. Maybe one of the AVS+ devs (like qyot27) will have a look and fix the slowdown issue.

[stax76]

The log I pm-ed to you wasn't sufficient?

It was my error, I deleted everything but 3 executables from the mkvmerge dir in order to save download and disk space, turns out the data dir is needed for your type of source.

[JohnLai]

It was my error, I deleted everything but 3 executables from the mkvmerge dir in order to save download and disk space, turns out the data dir is needed for your type of source.

I will say thanks in advance for fixing the muxing issue in your upcoming staxrip build. ^.^

Now then, my next stuff is to inform Rigaya on the weird avqsv decode slowdown this weekend.

[stax76]

Right, I keep forgetting that. I guess you're stuck with r1825 for the time being. Maybe one of the AVS+ devs (like qyot27) will have a look and fix the slowdown issue.

I wonder if raising money could help AviSynth+ development?

[ShamisOMally]

I wonder if raising money could help AviSynth+ development?

Could you at least update the 1.3.1.6 package so we can use it?

I've been using 1.3.1.5 and just moved over Nvenc/x264 files manually because it works

*EDIT* Unless I'm missing something, you said its just missing a few of the mkv merge files right? Any way to import them?

[stax76]

You can try a build from today:

http://www.mediafire.com/download/61vlca92h51kltw/StaxRip_x64_2015.09.19.7z

[stax76]

test build for AviSynth+ r1825 x64, VapourSynth R28 test4 x64, Python 3.5 x64, DGDecodeNV x64 for VapourSynth.

many people reported problems caused by using wrong app versions so exact versions are now validated and enforced and download links to the exact versions are included, it'll reduce problems and makes the setup easier.

http://www.mediafire.com/download/loyu003b1ppa22y/StaxRip_x64_2015-09-21.7z

[burfadel]

test build for AviSynth+ r1825 x64, VapourSynth R28 test4 x64, Python 3.5 x64, DGDecodeNV x64 for VapourSynth.

many people reported problems caused by using wrong app versions so exact versions are now validated and enforced and download links to the exact versions are included, it'll reduce problems and makes the setup easier.

http://www.mediafire.com/download/loyu003b1ppa22y/StaxRip_x64_2015-09-21.7z

QAAC has been updated to v2.53, you have v2.52.

Also, the Apple Application support files have been updated. Most of the files have the same file version (except objc.dll which is now 1.528.0.129, the version with the 21 Sep Staxrip is 1.528.0.126).

Some of the other files, despite having the same version, have also been updated (May 2015 vs March 2015):

Not identical:
CoreAudioToolbox.dll
CoreFoundation.dll
icudt49.dll
libicuin.dll
libicuuc.dll

No difference:
asl.dll
libdispatch.dll

[stax76]

@burfadel

Thanks, I'll update it.

[burfadel]

@burfadel

Thanks, I'll update it.

QAAC has been updated now to v2.55 :).

edit: As has other files (Stax knows of this)

[JohnLai]

Good news for AMD purists.
Rigaya finally adds VCEenc command line version
http://rigaya34589.blog135.fc2.com/blog-entry-679.html

AMD APU and AMD CPU + AMD GPU will finally get hardware based encoding?

Summoning our beloved @stax76 to implement staxrip gui.

Note:StaxRip_x64_2015-09-21 = everytime when I drag and drop a mkv file into staxrip, it keep poping up a menu asking me to install avisynth 1825 even though I already have it installed. I even check the avisynth.dll version at system32 folder and yes, it is 1825.

[NikosD]

Excellent news.

It also supports B frames, but the quality is poor according to Rigaya.

I would definitely like to see the encoding speed on a 1080p H.264 clip using a fast VCE engine like Tonga, Carrizo or Fiji AMD card.

[dvd_maniac]

I am having an issue where i input a video and the initial resize is screwed up and does not enforce the Resize slider width limit I set. It starts with the actual size of the video instead.
I have to manually move the resize slider back and forth for it to correct itself. This is not a huge problem except that I cannot use batch mode and most of my encoding used to be done automatically through batch files and scheduled tasks.
I have tried to just let it encode but the resize limit did not get enforced.

[stax76]

Good news for AMD purists.
Rigaya finally adds VCEenc command line version
http://rigaya34589.blog135.fc2.com/blog-entry-679.html

AMD APU and AMD CPU + AMD GPU will finally get hardware based encoding?

Summoning our beloved @stax76 to implement staxrip gui.

Adding new tools is always fun. ;)

Note:StaxRip_x64_2015-09-21 = everytime when I drag and drop a mkv file into staxrip, it keep poping up a menu asking me to install avisynth 1825 even though I already have it installed. I even check the avisynth.dll version at system32 folder and yes, it is 1825.

What's the last write date of your DLL? The dates are kept in a file called version.txt in the tools dir, there is no need to modify this file, you can just update it with F12, I'll improve the status descriptions telling about F12.

@dvd_maniac

In order to reproduce it I'll need more info.

[JohnLai]

Adding new tools is always fun. ;)



What's the last write date of your DLL? The dates are kept in a file called version.txt in the tools dir, there is no need to modify this file, you can just update it with F12, I'll improve the status descriptions telling about F12.

@dvd_maniac

In order to reproduce it I'll need more info.

Date Modified of avisynth.dll = 24 Sep 2015

Turn out I need to press F12 and remove the "X64" only. Hmm......

[dvd_maniac]

@Stax76:
I open up Staxrip and goto Options and place the resize width limit to 768. Then I input a 1280x720 video into the program and the resize shows 1280x716 with a DAR/SAR of 1.787
At this point the slider is all the way to the right. I have to move it left then all the way right again and the resize goes to the proper resolution setting of 768x432

I never had a problem like this until I went to 1.2.2.2_beta.
I installed this on 3 different PC's and I am having the same issue.
I just installed 1.3.1.6_beta thinking that it might fix the issue but no luck.

[stax76]

Date Modified of avisynth.dll = 24 Sep 2015

Turn out I need to press F12 and remove the "X64" only. Hmm......

When you run the installer bundled with StaxRip you should get 2015-03-23 as last write date. Any idea what could have changed it? Maybe you used a tool for AviSynth switching?

I open up Staxrip and goto Options and place the resize width limit to 768. Then I input a 1280x720 video into the program and the resize shows 1280x716 with a DAR/SAR of 1.787
At this point the slider is all the way to the right. I have to move it left then all the way right again and the resize goes to the proper resolution setting of 768x432

I never had a problem like this until I went to 1.2.2.2_beta.
I installed this on 3 different PC's and I am having the same issue.
I just installed 1.3.1.6_beta thinking that it might fix the issue but no luck.

As far as I can see it behaves as it should, if you want to resize then you have to check/enable a resize filter. :)

[dvd_maniac]

The resize filter 'IS' checked by default and the Options --> Image --> resize slider width is set to =768.

[dvd_maniac]

Nevermind. I think I figured it out...

I set the Auto resize image size in my template to 331776 and now my videos are properly resizing to 768x432 by default...

[dvd_maniac]

I'm trying to use 1.3.1.6 beta in a command line batch script. With this new version I am getting a pop-up asking me what audio and subtitles to demux. Is there a way to set it to demux everything by default so that I can bypass this pop-up?
All of what I am encoding will only have 1 audio and only sometimes have subtitles anyways.

[dejong12]

I'm trying to use 1.3.1.6 beta in a command line batch script. With this new version I am getting a pop-up asking me what audio and subtitles to demux. Is there a way to set it to demux everything by default so that I can bypass this pop-up?
All of what I am encoding will only have 1 audio and only sometimes have subtitles anyways.
This is an option I would like to have too. Maybe you could also make it that this pop-up does not appear when you only have 1 audio and (if available) 1 subtitle. When you have more, it would pop-up (when enabling the option).

[burfadel]

I've noticed you've removed some features from the x265 settings configuration. I've got some animation that I want to apply x265 deblock settings to, and I can't! There is no deblock setting configuration, and the custom command line option is also missing. Out of the two I would prefer at least the ability for the custom command line to be added back in (it was removed since the last main version).

Why remove it from x265 and leave it for x264?

[stax76]

I'm trying to use 1.3.1.6 beta in a command line batch script. With this new version I am getting a pop-up asking me what audio and subtitles to demux. Is there a way to set it to demux everything by default so that I can bypass this pop-up?

I'll hide it in batch mode and demux all.

I've noticed you've removed some features from the x265 settings configuration. I've got some animation that I want to apply x265 deblock settings to, and I can't! There is no deblock setting configuration, and the custom command line option is also missing. Out of the two I would prefer at least the ability for the custom command line to be added back in (it was removed since the last main version).

Here it's fine!

http://oi57.tinypic.com/sgiq8j.jpg

[burfadel]

Here it's fine!

Found the issue... I'm running Windows 10 Insider Preview (build 10547), and they must be tweaking fonts and dialogue boxes etc. The settings are there, it's just off the end of the list! Just found you can still select the missing categories by using the down cursor :sly:

http://oi61.tinypic.com/s3ex01.jpg

[stax76]

Maybe I can do something, any idea when the final ships?

edit:

also don't forget the search feature at the bottom

[burfadel]

Maybe I can do something, any idea when the final ships?

edit:

also don't forget the search feature at the bottom

It will probably change again before the final. I believe TH2 was meant to be shipped in October, but I believe it may have been pushed back to November.

[stax76]

It will probably change again before the final. I believe TH2 was meant to be shipped in October, but I believe it may have been pushed back to November.

I set the item height based on the font height like so:

Tree.ItemHeight = FontHeight * 2

Maybe they changed something, it doesn't look right however. As far as I know I've tested everything with different DPI settings, to be sure, what DPI settings are you using? Mine is 144 (150% zoom).

[stax76]

Here is a build with VCEEncC support for AMD H.264 encoding, I could not test it so I hope it works.

The build also fixes the issue with dialogs showing in command line mode.

http://www.mediafire.com/download/si8hl09q6hzdda5/StaxRip_x64_2015-09-28.7z

[NikosD]

Now you could add "...and AMD GPU encoding" in the title of this thread :)

[NikosD]

Here is a build with VCEEncC support for AMD H.264 encoding, I could not test it so I hope it works.

http://www.mediafire.com/download/si8hl09q6hzdda5/StaxRip_x64_2015-09-28.7z

I think a setting for Quality/Speed using the command switch

-u,--quality <string> set quality preset
balanced(default), fast, slow

would be useful in basic menu, like Intel's H.264/H.265 GUI.

[stax76]

I wanted to add it but forgot the part that makes it visible. :)

[burfadel]

I set the item height based on the font height like so:

Tree.ItemHeight = FontHeight * 2

Maybe they changed something, it doesn't look right however. As far as I know I've tested everything with different DPI settings, to be sure, what DPI settings are you using? Mine is 144 (150% zoom).

I had a look again and it's showing fine now. It may be an anomaly with the build leading up to TH2 rather than a feature. I'm just about to download the 28 September build so I'll see how that goes!

[rayman3003]

Balanced H265 options for StaxRip
===========================
I use H265 codec in StaxRip for converting videos bcuz it has a good compression. The options that Im using, r the default options. Sometimes they gives me good results but sometimes not.

http://img.ctrlv.in/img/15/09/25/5605bdd70b19b.jpgImage hosted for free at CtrlV.in (http://ctrlv.in/641660)

So I wanna ask users here (that has been already using H265 in StaxRip) to share us whats the best options for H265 in StaxRip that gives a balanced output result. By "Balanced" I mean an output video that has a low size with a quality as close as to the source.

Thanks:

The Options:
==================
Mode:
Level:
MV Precision:
Constant QP I:
Constant QP P:
Constant QP B:
Maximum Bitrate:
GOP Lenght:
B Frames:
Reference Frames:

[burfadel]

By using hardware encoding you typical forego quality for speed. It's because some things are better done on fewer cores that have more power, because they're more effective to process in larger sections. More cores (which you effectively have when GPU processing) is more effective for parts that can be broken down into sections without impeding on quality.

Well, that's a basic idea of it anyway. Not really worded quite right! There's also the issue of transferring the data back and forth between the CPU and GPU. It would be interesting to know the power used vs quality vs speed vs file size of using x265 on a modern CPU using decent settings and using a hardware encoder.

A hardware encoder is still a good concept though. This is especially true with HSA etc (which will become more utilised in the future no doubt). Basically with HSA, you can use the best option for the processing of the encoding between the CPU and GPU without loss of quality (supposedly). Of course, software would have to be cleverly written to make the best use of this.

[NikosD]

The above post is misleading.

It is referred to years before 2011, before QuickSync and the other specific ASICs built for HW encoding.

The above post is referred to general purpose GPUs which up to year 2011 could be used for HW encoding among other things.

HW encoding in late 2015 has nothing to do with all of the above.

[stax76]

@rayman3003

For the NVIDIA H.265 encoder there is hardly something you can tweak, lowering the QP values will increase the bitrate. You'll get better results with x264 and x265, for common use cases like 720p/1080p resolution, 3-10 Mbps bitrate and encoding time within 8 hours, x265 is highly controversial, personally I don't see any advantage for common use cases. x265 it's said to be good for 4K and slow settings which results in days of encoding time instead of hours. There are many different opinions of course, you can compare videos with the video comparison tool located at: Main Menu / Tools / Advanced / Video Comparison

[stax76]

I've now uploaded a new official beta release to github:

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

https://github.com/stax76/staxrip/releases

[rayman3003]

Thank u all for your answers But I need th numbers for those options. It seems nobody here use h265. :rolleyes:

@stax76
I will try video comparison as soon as possible.

I have a nvidia 950 gtx gpu (with 768 cuda cores) that can convert videos very fast using nvenc hardware acceleration. But just like I said, It doesn't always give me good results with the default options (for different videos). Sometimes good results, sometimes bad quality and sometimes big size. (all with the default settings)!

Most of the videos that I want to transcode, have resolution less than (1280x720).

[dejong12]

Videoh, I don't know what changed, but all my h264 1080i recordings in the .mkv container work correctly now with DGDecNV. No dropped frames at the start anymore! :D I have the latest 2050 'installed'.

[videoh]

That's good to hear. Was this a problem you posted here or at my site?

[dejong12]

That's good to hear. Was this a problem you posted here or at my site?
Here, we had a whole discussion at around page 20.

[videoh]

I see, thank you.

[Trench]

A couple observations for StaxRip in general, which remain true in StaxRip_x64_1.3.1.7_beta:


- When I use the "Edit" dialog on the audio encoding, modifying the "Gain:" spinner control doesn't change the command line. I can set whatever gain in the UI, but log confirms the command line ultimately runs without with "+/-XXdb" addition. Manually adding +/-XXdb to the command line using the UI works as expected.

I'm seeing this with codec set to "ACC" and encoder "Automatic", which in my observation always ends up using EAC3TO. This behavior has always been there, even back to the x86 version, but it seems so straight-forward that I don't think I'm simply misunderstanding an intentional behavior here.


- I've been having the issue of MP4Box writing GPAC temp files to the user temp directory rather than the temp area specified in StaxRip, same as the issue you already knew of here https://www.doom9.org/showthread.php?p=1713268#post1713268.

My issue was actually that these GPAC temp files were being abandoned and never deleted, same as the issue you were already aware of and should be fixed per https://github.com/gpac/gpac/issues/61.

What I wanted to mention though is that although I can see via Microsoft's Process Monitor that the TEMP variable has been overridden to the StaxRip-specified temp area, the TMP variable is still set to the user temp directory.

And Process Monitor is confirming that MP4Box.exe is still writing the GPAC temp file to the user temp directory, not the StaxRip-specific area set in the TEMP environment variable.

Process Monitor also reveals that StaxRip_x64_1.3.1.7_beta didn't specify "-tmp" on the MP4Box.exe command line, not withstanding that historically it wasn't being honored anyway.

Maybe it's worth doing both; use -tmp just so MP4Box at least has the opportunity to honor it, and also override the TMP environment variable in addition to TEMP to try and cover more cases where they don't honor it.


- Starting with the x64 version and tool set, the default for x264.exe seems to be to use all processor cores (thread per core), which is great. What I'm usually doing though is having a queue of one or more jobs already running in the background, and I'm in a different instance of StaxRip in the foreground creating and adding new jobs to that background queue.

What didn't happen in x86 but happens now in x64 is that trying to run something like "Compressibility Check" takes FOREVER in this foreground instance, because both the foreground and background instances of x264.exe are trying to run a thread per core, and the resulting contention is greater than the sum of the running time of each job individually.

So the suggestion is whether there can be a way to run "Compressibility Check" with a different thread priority than will be normally assigned to x264.exe when its run for actual conversion. StaxRip lets me assign Idle versus Normal priority, but it's apparently used for everything equally.

Effectively I want to "pause" the background job (which is what I do manually now as a workaround), but with everything returning to normal automatically as soon as the "Compressibility Check" is complete / as soon as cores are available, without me having to remember to come back and resume the background job list.

Or some other smarter solution to the same situation.

[stax76]

@Trench

Welcome and thanks for the detailed feedback.

Gain was only applied for qaac and ffmpeg, next build will apply it for eac3to too.

Regarding the temp dir next build will set both variables TEMP and TMP.

Regarding comp check I've set the comp check priority to normal now, implementing pausing/resuming other instances is too much work for a rarely used feature.

[jones1913]

@stax

VCEEnc fails with 'Unknow Options: "--input"'.

Options must be named: '--input-file' and '--output-file'.

And Check VCE support option in encoder dialog show an empty dialog box (maybe read wrong output stream?).

However vceenc itself works on my 270x, here are some numbers:

Source: Full HD clip 50 Mbps AVC, decoded with lsmashsource

preset fast, cqp 28: encoded 2460 frames, 84.37 fps, 21680.21 kbps, 211.93 MB
preset balanced, cqp 28: encoded 2460 frames, 72.43 fps, 21138.62 kbps, 206.63 MB
preset slow, cqp 28: encoded 2460 frames, 43.28 fps, 20783.30 kbps, 203.16 MB


Excellent news.

It also supports B frames, but the quality is poor according to Rigaya.

I would definitely like to see the encoding speed on a 1080p H.264 clip using a fast VCE engine like Tonga, Carrizo or Fiji AMD card.
I would say all hardware encoders need a lot more bitrate to achieve the same quality than x264.
But my hardware is only VCE 1.0, so no B-frame support.

[NikosD]

I would say all hardware encoders need a lot more bitrate to achieve the same quality than x264.
But my hardware is only VCE 1.0, so no B-frame support.

Not all.
QuickSync encoding is close enough to x264 using Haswell or better and ICQ encoding mode - at least for my needs.

And the efficiency is a lot better than x264.

Regarding VCE 1.0, it is very slow and poor in quality options.

Thanks for sharing your results.

[JohnLai]

Quality aside, VCE support still very useful for AMD APU though.

[NikosD]

Of course.
And latest VCE 3.x is very fast and with better quality.

[NikosD]

QSVencC v2.16 is out, adding VC-1 HW decode and increasing -c raw speed for uses like the ones asked for by JohnLai.

[JohnLai]

QSVencC v2.16 is out, adding VC-1 HW decode and increasing -c raw speed for uses like the ones asked for by JohnLai.

All hail Rigaya for solving the -c raw. :thanks:

Thanks for informing about the 2.16, NikosD.

Will test it later.


EDIT:
QSVenc 2.16 test;

QSVENC --avqsv 1080P H264 to 1080P HEVC NVENCC = encoding fps increased from 84fps to 190fps.

QSVENC --avqsv --output-res 1280x720 resizing an 1080P H264 to 720P HEVC NVENCC = encoding fps increased from 128fps to 350fps.

In both cases, CPU usage slightly high while averaging at 26-30% as viewed at Task Manager (Core I5 3570K OC-ed 4.2Ghz)

EDIT V2:
Hmmm, I just started to batch convert 20 of h264 encoded video 1080 to HEVC 720 (nvencc). Apparently, Rigaya QSVenc --avqsv decode mode isn't quite error resilient in hardware decoding some non-standard h264 video, it crashed immediately after 20-23% on QSVenc portion of decode of my video.

Decoding using LAVfilter QSV = no problem. A bit with little blocky green bits on certain portion of the final hevc encode.


EDIT V3:

Stax~~~~, using staxrip --avqsv + nvencc resulted in weird gui progress report.

http://imgur.com/a/lrqWT


EDIT V4:
Funny stuff;
Final encode result size are different depending on decoder.
LAV QSV = 2gb
QSVENCC = 2.9gb
h264 to hevc 1080.


EDIT V5:
Stax, is it possible to modify the staxrip behavior to stop transcoding process in case of QSVEncc decode error and warn user?
Because when --avqsv is used for decoding non-standard or faulty bits of video and qsvencc crashes with error message about "error in pipeline" (can trigger this similar behavior by pressing CTRL + C when using qsvencc in windows command prompt), staxrip continues to mux the incomplete encoded files.

QSVEnc 2.16 (x64), based on Intel(R) Media SDK Encoding Sample 6,0,0,98947
OS Windows 10 (x64)
CPU Info Intel Core i5-3570K @ 3.40GHz [TB: 4.30GHz] (4C/4T) <IvyBridge>
GPU Info Failed to get GPU Info.
Media SDK QuickSyncVideo (hardware encoder), 2nd GPU, API v1.11
Async Depth 4 frames
Buffer Memory system, 1 input buffer, 9 work buffer
Input Info avcodec video: H.264/AVC, 1920x1008, 24/1 fps
Output 1920x1008p 1:1 24.000fps (24/1fps)
NVEnc 1.10 (x64), using NVENC API v5.0
OS Version Unknown (x64)
CPU Intel Core i5-3570K @ 3.40GHz [TB: 4.30GHz] (4C/4T)
GPU GeForce GTX 970 (13 EU) @ 1253 MHz (356.04)
Input Buffers CUDA, 16 frames
Input Info y4m (yv12) -> nv12 [AVX], 1920x1008, 1199999/50000 fps
Output Info H.265/HEVC main
1920x1008p 1:1 24.000fps (1199999/50000fps)
Rate Control CQP
CQP I:20 P:28 B:30
GOP length 240 frames
B frames 0 frames
Ref frames 5 frames
MV Quality Q-pel
device operation failure.
Error in encoding pipeline. : device operation failure.
error at encode thread.
encoded 121891 frames, 212.21 fps, 557383.68 kbps, 337461.90 MB
encode time 0:09:34 / CPU Usage: 10.30
frame type IDR 121891
frame type I 121891, total size 337461.90 MB
QSVEncC.exe finished with error!
encoded 121891 frames, 212.51 fps, 1399.66 kbps, 847.41 MB
encode time 0:09:34 / CPU Usage: 12.38%
frame type IDR 508
frame type I 508, avgQP 20.00, total size 29.38 MB
frame type P 121383, avgQP 28.00, total size 818.03 MB

Note: As shown at second screenshot imgur mini album link, when the "%" goes missing, the decode + encode process WILL FAIL FOR CERTAIN and results in the error log above after few minutes. Staxrip will continue to mux the incomplete video.

[reeboot]

Hello stax76

I use windows 10 13 64B Vegas, Frame server with Debug mode.
StaxRip 32bits 1.2.2.2 works perfectly.

But if I use the new 64-bit versions, it asks me to install Avisynth + I do and then does it work well on film 4k existing 25P; excellent software!

Except that when I open the AVI file waiting with open vegas (debug mode) he said:

"Failed to open source
The return value scrip'ts Was not a video (is the indefinifed value) "

I tried it on 3 different machines same problem
http://www.repaire.net/forums/discussions/h265-et-encodage-materiel-4k-avec-staxrip.271447/page-3#post-1970223152

[NikosD]

Something is wrong with the muxing of multiple subs.

Using this sample https://www.sendspace.com/file/bx4xwz, I can only re-mux the first sub.

If I select "all" I still get the first subtitle, if I select number 2 subtitle I get nothing in the final mkv.

Demux looks good, it recognizes all subtitles.

[Fantasy]

Hello,
I want to use StaxRip with Intel GPU Encoding.
I have windows 10 64 bit and Intel Skylake HD530.
But I got error message, both with Intel H.264 and Intel H.265:

http://fs5.directupload.net/images/151014/nndjrsil.png

Can you look in to it and solve this error please?
Thank you!

[LoRd_MuldeR]

DWORD(-1073741819) == 0xC0000005 (https://msdn.microsoft.com/en-us/library/cc704588.aspx)

It means that the "intel encoder" has crashed with Access Violation exception. This is a rather unspecific error, indicating that the process tried to access memory that it doesn't have access to.

[Groucho2004]

DWORD(-1073741819) == 0xC0000005 (https://msdn.microsoft.com/en-us/library/cc704588.aspx)

It means that the "intel encoder" has crashed with Access Violation exception. This is a rather unspecific error, indicating that the process tried to access memory that it doesn't have access to.
Why do people throw these cryptic error messages? There's a nice Win32 API function called FormatMessage() which does all the hard work of explaining the error code.

Something like this:
string SysErrorMessage()
{
DWORD dwLastError = GetLastError();
char *szMsg;

if (dwLastError == ERROR_SUCCESS)
return "";

FormatMessage(FORMAT_MESSAGE_ALLOCATE_BUFFER | FORMAT_MESSAGE_FROM_SYSTEM,
NULL,
dwLastError,
MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT),
(LPTSTR)&szMsg,
0,
NULL);

string sRet(szMsg);
return sRet;
}

[LoRd_MuldeR]

...probably because there is no universally valid way to interpret the exit code of a process? (except, maybe, for the convention that a non-zero exit code usually indicates failure)

[Groucho2004]

...probably because there is no universally valid way to interpret the exit code of a process? (except, maybe, for the convention that a non-zero exit code usually indicates failure)
Fair enough but the exit code could at least be checked against the range of NT Status error codes.

[myksto]

When I try to load a file it always ask me to install Avisnith+.
I install it but Staxrip keeps telling me I have to install it.
I used version 1.3.15 with no problem: how can I fix it?
Mi OS is Windows 10.

Thanks a lot.

[stax76]

@myksto

You can edit the version with F12, the latest build has a better explanation:

Install AviSynth+ r1825. Press F12 to edit the version.

If you see the message than StaxRip thinks you are using a wrong version but F12 allows you to use it anyway.

Here is the latest build:

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

Why do people throw these cryptic error messages? There's a nice Win32 API function called FormatMessage() which does all the hard work of explaining the error code.

I tried to code it, unfortunately without success so far. :(

http://pastebin.com/789qdpSz

FormatMessage fails with: Die angegebene Image-Datei enthält keinen Ressourcenabschnitt

@Fantasy

What CPU is it and what's the driver version? In the Intel Encoding Options dialog there is a menu to execute QSVEncC diagnostic switches.

Something is wrong with the muxing of multiple subs.

Using this sample https://www.sendspace.com/file/bx4xwz, I can only re-mux the first sub.

If I select "all" I still get the first subtitle, if I select number 2 subtitle I get nothing in the final mkv.

Demux looks good, it recognizes all subtitles.

Here it worked.

http://pastebin.com/Fe1ZkJc5

@reeboot

I'm not familiar with Vegas and Debugmode FrameServer, does it use a virtual file system?

[Fantasy]

Hello,
I have formated my PC and install windows new and it works now, I don't know why exactly.
But I think because I didn't intall some kind of Microsoft Visual C++ 20xx Redistributable.
And Thank You, I feel like I am dreaming, 4K HEVC 27 fps at standard settings.

[ShamisOMally]

I noticed when encoding VP9 WebM's, Staxrip is not paying attention to entered video bitrate, its only paying attention to the Size setting (The left box, not the right)

This makes it impossible to tune encoding size when making WebM's

[reeboot]

Stax
Yes Frame debug server installed in vegas fashion waits an exported AVI file
This file is denied by any 64-bit StaxRip.

This is unfortunate because StaxRip 32bits allowed to encode videos directly from the editing software.
Thanks for your answer.

[stax76]

Hello,
I have formated my PC and install windows new and it works now, I don't know why exactly.
But I think because I didn't intall some kind of Microsoft Visual C++ 20xx Redistributable.
And Thank You, I feel like I am dreaming, 4K HEVC 27 fps at standard settings.

I've added now Visual C++ 2015 Redistributable Packages as absolute requirement, if it's not installed StaxRip will tell about it and show a download button.

I noticed when encoding VP9 WebM's, Staxrip is not paying attention to entered video bitrate, its only paying attention to the Size setting (The left box, not the right)

Seem to work fine, I would need more details to further examine it.

Stax
Yes Frame debug server installed in vegas fashion waits an exported AVI file
This file is denied by any 64-bit StaxRip.

This is unfortunate because StaxRip 32bits allowed to encode videos directly from the editing software.
Thanks for your answer.

StaxRip uses the avifile VFW API to open avs and vpy like VirtualDub so you could try to open your virtual avi file with VirtualDub, it should work with both VirtualDub x86 and VirtualDub x64. Using virtual file systems it should be possible to mix x86 with x64 or to mix AviSynth with VapourSynth, both AviSynth and VapourSynth can output to a virtual file systems and AviSynth, VapourSynth and StaxRip can open such virtual files.

[Groucho2004]

I tried to code it, unfortunately without success so far. :(

http://pastebin.com/789qdpSz

FormatMessage fails with: Die angegebene Image-Datei enthält keinen Ressourcenabschnitt
No idea. Last I worked on some Basic code was 1994 and that was vastly different to VB code nowadays, therefore => Ich verstehe nur Bahnhof.

[LoRd_MuldeR]

Fair enough but the exit code could at least be checked against the range of NT Status error codes.

You mean the range that goes from 0x00000000 to 0xC03A0019? ;)
https://msdn.microsoft.com/en-us/library/cc704588.aspx

What you actually can do is: Interpret the return value as a DWORD and compare it against a few specific NTSTATUS codes that typically indicate abnormal program termination.

If you got a match, then you probably (though not necessarily) detected a crash and got an NTSTATUS code from the system. Otherwise it's probably (though not necessarily) a "normal" exit code return by the application.

It's not a "perfect" solution, but AFAIK the Win32 API doesn't provide a better method. I'm not aware of an API to check whether the process terminated "normally" or not. So this should solution be working well enough.

At least that's what I'm doing...


I tried to code it, unfortunately without success so far. :(

http://pastebin.com/789qdpSz

FormatMessage fails with: Die angegebene Image-Datei enthält keinen Ressourcenabschnitt

Try removing the FORMAT_MESSAGE_FROM_HMODULE flag and set the module handle to NULL.

For most system messages you don't need to provide the module. And NTDLL.DLL probably doesn't even support this (as the error messages indicates).

You would have to explicitly specify the module for messages from WININET.DLL, for example.

[Groucho2004]

You mean the range that goes from 0x00000000 to 0xC03A0019? ;)
https://msdn.microsoft.com/en-us/library/cc704588.aspx

What you actually can do is: Interpret the return value as a DWORD and compare it against a few specific NTSTATUS codes that typically indicate abnormal program termination.

If you got a match, then you probably (though not necessarily) detected a crash and got an NTSTATUS code from the system. Otherwise it's probably (though not necessarily) a "normal" exit code return by the application.

It's not a "perfect" solution, but AFAIK the Win32 API doesn't provide a better method. I'm not aware of an API to check whether the process terminated "normally" or not. So this should solution be working well enough.
Yes, pretty much along these lines.

[stax76]

No idea. Last I worked on some Basic code was 1994 and that was vastly different to VB code nowadays, therefore => Ich verstehe nur Bahnhof.

I've also tried your C++ example with NTSTATUS 0xC0000005 but it didn't work either.

What you actually can do is: Interpret the return value as a DWORD and compare it against a few specific NTSTATUS codes that typically indicate abnormal program termination.

So what are common codes then?

Try removing the FORMAT_MESSAGE_FROM_HMODULE flag and set the module handle to NULL.

For most system messages you don't need to provide the module. And NTDLL.DLL probably doesn't even support this (as the error messages indicates).

You would have to explicitly specify the module for messages from WININET.DLL, for example.

Using the module is supposed to work according MS:

https://support.microsoft.com/en-us/kb/259693

I tried with and without module in VB.NET and C++, nothing worked.

[NikosD]

Here it worked.

http://pastebin.com/Fe1ZkJc5



I can clearly see in your log file that mkvmerge is indeed muxing all three subs.

BUT you used DGIndexNV for indexing.

Can you please try with the default settings of StaxRip, without using DG* tools ?

I always assume using StaxRip without extra (commercial) added apps.

[LoRd_MuldeR]

Using the module is supposed to work according MS:
https://support.microsoft.com/en-us/kb/259693

I tried with and without module in VB.NET and C++, nothing worked.

I never used VB.NET. The last time I used BASIC was probably on my old C64. Anyway, here is the C# code, which should be easy to adapt:
http://pastebin.com/VV24PUaR

[stax76]

I never used VB.NET. The last time I used BASIC was probably on my old C64. Anyway, here is the C# code, which should be easy to adapt:
http://pastebin.com/VV24PUaR

Great help, thanks. I'm not sure but it looks like my bug was the string marshaling, usually the marshaller is smart about System.String and System.Text.StringBuilder, I don't know why it's not working in this case.

edit:

It wasn't the automatic string marshalling but the definition of the second param IntPtr lpSource which I had defined using ref.

<DllImport("Kernel32.dll", SetLastError:=True, CharSet:=CharSet.Unicode)>
Function FormatMessageW(dwFlags As Integer,
ByRef lpSource As IntPtr,
dwMessageId As Integer,
dwLanguageId As Integer,
ByRef lpBuffer As String,
nSize As Integer,
ByRef Arguments As IntPtr) As Integer
End Function

The error message I had makes sense then of course.

Die angegebene Image-Datei enthält keinen Ressourcenabschnitt

[stax76]

@NikosD

With FFVideoSource it's also working, I also tried demuxing to SRT and using MKV directly as subtitle source and both worked.

[RazorBurn]

@myksto

Install AviSynth+ r1825. Press F12 to edit the version.

If you see the message than StaxRip thinks you are using a wrong version but F12 allows you to use it anyway.

Here is the latest build:

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


May i know what are the changes in the 10-16-2015 build of StaxRip?

[dejong12]

May i know what are the changes in the 10-16-2015 build of StaxRip?
https://github.com/stax76/staxrip/wiki/Changelog

[stax76]

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

It's not in sync, I edit the page after every code change but don't upload a new test build after every code change, not the best solution I know, I might find something better.

[turok]

Thanks for fixing autoload issue Stax76! forgot I had an account here...

does the vorbis encoder used by staxrip roll with vanilla or aotuv version? I use opus currently but I am curious...

[reeboot]

StaxRip uses the avifile VFW API to open avs and vpy like VirtualDub so you could try to open your virtual avi file with VirtualDub, it should work with both VirtualDub x86 and VirtualDub x64. Using virtual file systems it should be possible to mix x86 with x64 or to mix AviSynth with VapourSynth, both AviSynth and VapourSynth can output to a virtual file systems and AviSynth, VapourSynth and StaxRip can open such virtual files.

Sorry I do not understand probably my English is bad ...:helpful:

[stax76]

Thanks for fixing autoload issue Stax76! forgot I had an account here...

does the vorbis encoder used by staxrip roll with vanilla or aotuv version? I use opus currently but I am curious...

It's using ffmpeg so probably no aotuv.

Sorry I do not understand probably my English is bad

Can VirtualDub x64 load the file?

[NikosD]

@NikosD

With FFVideoSource it's also working, I also tried demuxing to SRT and using MKV directly as subtitle source and both worked.
Then, is my system possessed ?

Spooky...

Is there anyone else who could try to just remux the clip with default settings and all subs included ?

Just to be sure it is me...

[reeboot]

Can VirtualDub x64 load the file?
Not stax virtualdub 64 does not open this fil
15071e
Thanks for your help :thanks:

[stax76]

Not stax virtualdub 64 does not open this fil
15071e
Thanks for your help :thanks:

You can also try VirtualDub x86, maybe it's not possible to mix x86 and x64 using the virtual file of your frame server tool.

I believe with AviSynth's and VapourSynth's virtual file system mixing x86 with x64 is no problem.

It can take hours until attachments get approved, you might want to edit your post using a image/file hoster or cloud drive.

@NikosD

It's probably a different setting or action, with a log file there would be a chance to find something...

[g0th1ckn1ght]

I currently have video and audio set to Just Mux (file size is not an issue for me) but for some reason the profile is set to Advanced@L3.

Is there a way to change that please without having to set the codec to x264.

Thank you.

Edit:

It seems to be setting it to Level 3 during the intial import of the Bluray title. Is there a way to extract the main video at a higher level?

EDIT 2

Please ignore the above post. I worked it out :(

[NikosD]

@NikosD

It's probably a different setting or action, with a log file there would be a chance to find something...

OK, the procedure is simple.

I just select the file to open and I press "All" subtitles in the dialog window, along with the audio file of course.

Then, I choose "Just mux" for video and audio and automatic source.
Even if I select an audio or video encoding (like Intel H.264 or x264) there is no difference.

The result after finishing the process is this:
http://pastebin.com/74Et2MAG

[huhn]

is there a way to use lossless nvidia AVC encoding in your program?

[reeboot]

You can also try VirtualDub x86, maybe it's not possible to mix x86 and x64 using the virtual file of your frame server tool.

I believe with AviSynth's and VapourSynth's virtual file system mixing x86 with x64 is no problem.

It can take hours until attachments get approved, you might want to edit your post using a image/file hoster or cloud drive.


Vapoursynth not work either
I think I will use the 32-bit versions

[stax76]

@NikosD

Please post a screenshot of the muxing tab in the container options dialog.

is there a way to use lossless nvidia AVC encoding in your program?

I don't know if NVEncC or the underlying NVIDIA API supports it, if you want I can give you the Email address of the NVEncC author rigaya or I can ask for you.

[myksto]

@myksto

You can edit the version with F12, the latest build has a better explanation:

Install AviSynth+ r1825. Press F12 to edit the version.

If you see the message than StaxRip thinks you are using a wrong version but F12 allows you to use it anyway.

Here is the latest build:

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

Hi Stax and thanks for reply.
I followed your hint and it did the trick
I would like to ask another question as I'd like to import my encoded files (encoded with Staxrip) into Adobe Encore CS6 (for menù, ecc.) but Encore always tells me I have to re-encode them beacause thay're not blu-ray compatible. Of course i used the flag blu-ray compat in Starip and followed dozen of guides around the web but yet I did not succed in encoding a file and Encore wants to encode them everytime.
What settings should I use to have a totally blu-ray compliant file that Encore won't to re-encode it anymore?
Thank a lot.

[huhn]

I don't know if NVEncC or the underlying NVIDIA API supports it, if you want I can give you the Email address of the NVEncC author rigaya or I can ask for you.

the feature check says this:

"Lossless 1"

and adding --lossless doesn't result in an error. my plan was just to see how fast it is and if it is a lot better than lagarith or codecs like this so it could be used for recording nothing important for your program i guess.

[NikosD]

@NikosD
Please post a screenshot of the muxing tab in the container options dialog.


Mystery solved.
It didn't last long.

By choosing all subtitles in the demux dialogue window, I thought that automatically means that all subtitles will be muxed too.

Because you have selected by default the English subs in the demuxing dialogue, which is translated to default muxing of English subs.

So, if someone chooses to demux all subs, wouldn't that mean that he wants to mux all the demuxed subs ?

Obviously this is not the case for StaxRip, you have to explicitly select all subtitles in the container configuration muxing tab too.

I think that you could change that behavior to automatically select all subtitles to muxing options too, because most people would select all subtitles in demuxing options, mostly if they would like to mux them too.

Thanks anyway for solving my case.

[luigizaninoni]

There's something wrong in Compressibility check.

I'm encoding a clip with x264, preset veryfast, crf19. The encoding is fine.

However, if I try the Compressibility check, it is done at crf18 no matter what crf you put in the GUi: you can put 19,20,21 whatever, the compressibility check is always done at crf18

[stax76]

So, if someone chooses to demux all subs, wouldn't that mean that he wants to mux all the demuxed subs ?

Obviously this is not the case for StaxRip, you have to explicitly select all subtitles in the container configuration muxing tab too.

I think that you could change that behavior to automatically select all subtitles to muxing options too, because most people would select all subtitles in demuxing options, mostly if they would like to mux them too.

often people demux everything or everything of particular languages, IIRC Fight Club for instance has like ten different German subtitles, often people mux only certain subtitles, in most cases it necessary to review and adjust the subtitle settings so I think the current behavior is fine.

the feature check says this:

"Lossless 1"

and adding --lossless doesn't result in an error. my plan was just to see how fast it is and if it is a lot better than lagarith or codecs like this so it could be used for recording nothing important for your program i guess.

there is however no lossless feature documented, if you want to know exactly you can contact the author, he was always very helpful when I contacted him, his mail address can be found on his blog.

http://rigaya34589.blog135.fc2.com

rigaya34589 [ at ] live . jp

However, if I try the Compressibility check, it is done at crf18 no matter what crf you put in the GUi: you can put 19,20,21 whatever, the compressibility check is always done at crf18

there are two different crf settings

for encoding on the first tab called Basic
for comp check on the last tab called StaxRip

[huhn]

there is however no lossless feature documented, if you want to know exactly you can contact the author, he was always very helpful when I contacted him, his mail address can be found on his blog.

http://rigaya34589.blog135.fc2.com

rigaya34589 [ at ] live . jp

it's even on the wiki:
https://en.wikipedia.org/wiki/Nvidia_NVENC

Introduced with the first-generation Maxwell architecture, second generation NVENC adds support for HiP444 profile (YUV4:4:4, predictive lossless encoding),

i guess i just ask him.

[JohnLai]

it's even on the wiki:
https://en.wikipedia.org/wiki/Nvidia_NVENC
i guess i just ask him.

Meanwhile......help me in telling rigaya about QSVenc decode + vpp resize + NVenc HEVC encode overflow issue?

When --avqsv is used to decode a long duration video (1 hour 30 minutes to 3 hours), somewhere around halfway or so, not sure which portion crashes (QSVENC -c raw or Nvencc, probably qsvenc), when the error occurs, I notice all four cores cpu usage suddenly jumped to 100% for few seconds (normal operation only two cores averaging 30%- 40%) before the qsv decode + nvenc encode crashed and CPU usage dropped to 0%.

I guess something is overflowing, not sure what.

[huhn]

i have no clue what you are talking about and i don't really care for low quality NVENC HEVC i wouldn't be shocked if xvid is a better encoder...

[brunosso]

Hi stax! Congrats for the app! I use MeGUI for years, and i want to switch to StaxRip, because its a very x64 release!

I have a problem, with template!
In Megui i have many profiles, for my usually encoding needs. I use a profile, load a video, and encode.
In Staxrip i make a template, based on a modified x264 profiles, but when i load a video, many setting go wrong!
In detail, i use 2pass encode with 900k bitrate fixed, or 1500k fixed also. When i load the video, with the template i saved before, the bitrate go to 1700, even i saved the template with 900k.

How can i fix this? Do i apply bitrate settings for every video loaded in the template?

[stax76]

Hi stax! Congrats for the app! I use MeGUI for years, and i want to switch to StaxRip, because its a very x64 release!

I have a problem, with template!
In Megui i have many profiles, for my usually encoding needs. I use a profile, load a video, and encode.
In Staxrip i make a template, based on a modified x264 profiles, but when i load a video, many setting go wrong!
In detail, i use 2pass encode with 900k bitrate fixed, or 1500k fixed also. When i load the video, with the template i saved before, the bitrate go to 1700, even i saved the template with 900k.

How can i fix this? Do i apply bitrate settings for every video loaded in the template?

Hi! StaxRip uses fixed size instead of fixed bitrate by default, for fixed bitrate there is a option: Options > Misc > Use fixed bitrate

[JohnLai]

it's even on the wiki:
https://en.wikipedia.org/wiki/Nvidia_NVENC



i guess i just ask him.

Well....rigaya just added it....

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

[luigizaninoni]

I have another issue:
If I encode a clip with different source filters, but with the same encoding parameters, I obtain files with (about) the same size; which is what I expected, actually.

However, if I do compressibility check with different source filters, I obtain widely different file sizes and bitrates:

For the same clip I obtain with compressibility check the following results:
DSS: bitrate 587 kb/sec
FFMS: bitrate 459 kb/sec
Lwlibav: bitrate 794 kb/sec
DgSourceIm: bitrate 791 kb/sec

The differences are so wild that I think there must be something wrong (or maybe I am missing something)

The log of the four compressibility checks:


------------------------------------------------------------
Environment
------------------------------------------------------------

StaxRip x64 : 1.3.1.7
OS : Windows 8.1 Pro
Language : Italian (Italy)
CPU : Intel(R) Core(TM) i7-4770S CPU @ 3.10GHz
GPU : Intel(R) HD Graphics 4600

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

C:\Users\admin\Desktop\a.ts

General
ID : 1 (0x1)
Complete name : C:\Users\admin\Desktop\a.ts
Format : MPEG-TS
File size : 2.77 GiB
Duration : 2h 9mn
Overall bit rate mode : Variable
Overall bit rate : 3 055 Kbps

Video
ID : 8002 (0x1F42)
Menu ID : 5 (0x5)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : M=3, N=12
Format settings, picture structure : Frame
Codec ID : 2
Duration : 2h 9mn
Bit rate mode : Variable
Bit rate : 2 645 Kbps
Maximum bit rate : 10 000 Kbps
Width : 544 pixels
Height : 576 pixels
Display aspect ratio : 16:9
Active Format Description : Letterbox 16:9 image
Frame rate : 25.000 fps
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) : 0.338
Time code of first frame : 00:00:00:00
Time code source : Group of pictures header
GOP, Open/Closed : Open
GOP, Open/Closed of first frame : Closed
Stream size : 2.40 GiB (87%)

Audio #1
ID : 8003 (0x1F43)
Menu ID : 5 (0x5)
Format : MPEG Audio
Format version : Version 1
Format profile : Layer 2
Codec ID : 3
Duration : 2h 9mn
Bit rate mode : Constant
Bit rate : 128 Kbps
Channel(s) : 2 channels
Sampling rate : 48.0 KHz
Compression mode : Lossy
Delay relative to video : 9ms
Stream size : 119 MiB (4%)
Language : Italian

Audio #2
ID : 8030 (0x1F5E)
Menu ID : 5 (0x5)
Format : MPEG Audio
Format version : Version 1
Format profile : Layer 2
Codec ID : 3
Duration : 2h 9mn
Bit rate mode : Constant
Bit rate : 128 Kbps
Channel(s) : 2 channels
Sampling rate : 48.0 KHz
Compression mode : Lossy
Delay relative to video : 21ms
Stream size : 119 MiB (4%)
Language : English

SelectRangeEvery(280,14)


------------------------------------------------------------
Compressibility Check
------------------------------------------------------------

"C:\Users\admin\Desktop\Stax64\Apps\x264\x264.exe" --preset veryfast --tune film --crf 19 --sar 255:131 --output "E:\Temp\a temp files\a_CompCheck.h264" "E:\Temp\a temp files\a_CompCheck.avs"

avs [info]: 544x576p 255:131 @ 25/1 fps (cfr)
x264 [info]: using SAR=255/131
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
x264 [info]: profile High, level 3.0
x264 [info]: frame I:188 Avg QP:11.96 size: 32371
x264 [info]: frame P:3784 Avg QP:17.01 size: 5046
x264 [info]: frame B:5758 Avg QP:16.09 size: 584
x264 [info]: consecutive B-frames: 17.2% 9.2% 7.7% 65.9%
x264 [info]: mb I I16..4: 24.9% 27.9% 47.1%
x264 [info]: mb P I16..4: 4.3% 10.9% 2.3% P16..4: 16.0% 6.6% 4.0% 0.0% 0.0% skip:55.8%
x264 [info]: mb B I16..4: 0.5% 0.4% 0.0% B16..8: 6.0% 1.6% 0.2% direct: 3.3% skip:87.9% L0:45.7% L1:36.8% BI:17.5%
x264 [info]: 8x8 transform intra:54.3% inter:60.8%
x264 [info]: coded y,uvDC,uvAC intra: 64.9% 57.2% 21.8% inter: 4.7% 7.1% 0.3%
x264 [info]: i16 v,h,dc,p: 61% 19% 16% 4%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 42% 16% 30% 2% 1% 3% 1% 3% 2%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 41% 16% 10% 4% 5% 8% 4% 7% 4%
x264 [info]: i8c dc,h,v,p: 46% 17% 32% 5%
x264 [info]: Weighted P-Frames: Y:0.3% UV:0.1%
x264 [info]: kb/s:586.71
encoded 9730 frames, 191.36 fps, 586.71 kb/s

Start: 23.40.16
End: 23.41.09
Duration: 00:00:52

Quality: 131 %
Compressibility: 0,075

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

"C:\Users\admin\Desktop\Stax64\Apps\Plugins\both\ffms2\ffmsindex.exe" "C:\Users\admin\Desktop\a.ts" "E:\Temp\a temp files\a.ffindex"

Writing index... done.

Start: 23.41.28
End: 23.41.34
Duration: 00:00:06

SelectRangeEvery(280,14)


------------------------------------------------------------
Compressibility Check
------------------------------------------------------------

"C:\Users\admin\Desktop\Stax64\Apps\x264\x264.exe" --preset veryfast --tune film --crf 19 --sar 255:131 --output "E:\Temp\a temp files\a_CompCheck.h264" "E:\Temp\a temp files\a_CompCheck.avs"

avs [info]: 544x576p 255:131 @ 25/1 fps (cfr)
x264 [info]: using SAR=255/131
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
x264 [info]: profile High, level 3.0
x264 [info]: frame I:186 Avg QP:11.55 size: 33906
x264 [info]: frame P:3456 Avg QP:15.76 size: 4192
x264 [info]: frame B:6088 Avg QP:14.45 size: 248
x264 [info]: consecutive B-frames: 14.7% 4.4% 3.4% 77.5%
x264 [info]: mb I I16..4: 24.7% 26.5% 48.8%
x264 [info]: mb P I16..4: 2.8% 8.6% 2.5% P16..4: 10.3% 3.9% 2.6% 0.0% 0.0% skip:69.3%
x264 [info]: mb B I16..4: 0.2% 0.2% 0.0% B16..8: 2.5% 0.6% 0.1% direct: 1.6% skip:94.9% L0:51.7% L1:32.4% BI:15.9%
x264 [info]: 8x8 transform intra:51.9% inter:61.2%
x264 [info]: coded y,uvDC,uvAC intra: 70.7% 61.0% 29.0% inter: 2.4% 4.2% 0.2%
x264 [info]: i16 v,h,dc,p: 63% 17% 16% 3%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 44% 16% 29% 2% 1% 2% 1% 3% 2%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 41% 16% 10% 4% 5% 8% 4% 8% 4%
x264 [info]: i8c dc,h,v,p: 45% 18% 32% 5%
x264 [info]: Weighted P-Frames: Y:0.3% UV:0.1%
x264 [info]: kb/s:458.50
encoded 9730 frames, 325.69 fps, 458.50 kb/s

Start: 23.41.37
End: 23.42.07
Duration: 00:00:30

Quality: 168 %
Compressibility: 0,059

------------------------------------------------------------
Index LWLibav
------------------------------------------------------------

"C:\Users\admin\Desktop\Stax64\Apps\ffmpeg\ffmpeg.exe" -i "E:\Temp\a temp files\a.avs"

ffmpeg version N-76089-ge9299df Copyright (c) 2000-2015 the FFmpeg developers
built with gcc 5.2.0 (GCC)
configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libdcadec --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-lzma --enable-decklink --enable-zlib
libavutil 55. 4.100 / 55. 4.100
libavcodec 57. 7.100 / 57. 7.100
libavformat 57. 8.100 / 57. 8.100
libavdevice 57. 0.100 / 57. 0.100
libavfilter 6. 11.100 / 6. 11.100
libswscale 4. 0.100 / 4. 0.100
libswresample 2. 0.100 / 2. 0.100
libpostproc 54. 0.100 / 54. 0.100
Input #0, avisynth, from 'E:\Temp\a temp files\a.avs':
Duration: 02:09:42.48, start: 0.000000, bitrate: N/A
Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 544x576, 25 fps, 25 tbr, 25 tbn, 25 tbc
At least one output file must be specified

Start: 23.42.26
End: 23.42.27
Duration: 00:00:01

SelectRangeEvery(280,14)


------------------------------------------------------------
Compressibility Check
------------------------------------------------------------

"C:\Users\admin\Desktop\Stax64\Apps\x264\x264.exe" --preset veryfast --tune film --crf 19 --sar 255:131 --output "E:\Temp\a temp files\a_CompCheck.h264" "E:\Temp\a temp files\a_CompCheck.avs"

avs [info]: 544x576p 255:131 @ 25/1 fps (cfr)
x264 [info]: using SAR=255/131
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
x264 [info]: profile High, level 3.0
x264 [info]: frame I:199 Avg QP:14.14 size: 27049
x264 [info]: frame P:4387 Avg QP:17.97 size: 5842
x264 [info]: frame B:5144 Avg QP:19.33 size: 1479
x264 [info]: consecutive B-frames: 20.8% 20.9% 15.5% 42.8%
x264 [info]: mb I I16..4: 27.7% 27.8% 44.5%
x264 [info]: mb P I16..4: 6.5% 13.2% 2.0% P16..4: 21.6% 10.0% 5.8% 0.0% 0.0% skip:41.0%
x264 [info]: mb B I16..4: 1.1% 1.2% 0.0% B16..8: 13.2% 4.5% 0.5% direct: 8.1% skip:71.4% L0:36.2% L1:43.8% BI:20.0%
x264 [info]: 8x8 transform intra:54.8% inter:58.9%
x264 [info]: coded y,uvDC,uvAC intra: 57.0% 53.4% 14.7% inter: 9.2% 13.0% 0.3%
x264 [info]: i16 v,h,dc,p: 62% 19% 14% 4%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 43% 15% 29% 2% 2% 3% 2% 3% 2%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 41% 16% 10% 4% 5% 8% 4% 8% 4%
x264 [info]: i8c dc,h,v,p: 49% 17% 30% 4%
x264 [info]: Weighted P-Frames: Y:0.7% UV:0.1%
x264 [info]: kb/s:793.77
encoded 9730 frames, 173.02 fps, 793.77 kb/s

Start: 23.42.48
End: 23.43.49
Duration: 00:01:01

Quality: 97 %
Compressibility: 0,101

------------------------------------------------------------
DGIndexIM
------------------------------------------------------------

"C:\Users\admin\Desktop\Video\Staxrip\Applications\DGDecodeIM\x64\DGIndexIM.exe" -i "C:\Users\admin\Desktop\a.ts" -o "E:\Temp\a temp files\a.dgim" -h

Project

Start: 23.44.08
End: 23.44.41
Duration: 00:00:33

SelectRangeEvery(280,14)


------------------------------------------------------------
Compressibility Check
------------------------------------------------------------

"C:\Users\admin\Desktop\Stax64\Apps\x264\x264.exe" --preset veryfast --tune film --crf 19 --sar 255:131 --output "E:\Temp\a temp files\a_CompCheck.h264" "E:\Temp\a temp files\a_CompCheck.avs"

avs [info]: 544x576p 255:131 @ 25/1 fps (cfr)
x264 [info]: using SAR=255/131
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
x264 [info]: profile High, level 3.0
x264 [info]: frame I:199 Avg QP:14.08 size: 27081
x264 [info]: frame P:4385 Avg QP:18.37 size: 5820
x264 [info]: frame B:5146 Avg QP:19.86 size: 1469
x264 [info]: consecutive B-frames: 20.8% 20.8% 15.7% 42.7%
x264 [info]: mb I I16..4: 27.6% 27.9% 44.5%
x264 [info]: mb P I16..4: 6.5% 13.2% 2.0% P16..4: 21.5% 10.0% 5.8% 0.0% 0.0% skip:41.0%
x264 [info]: mb B I16..4: 1.1% 1.2% 0.0% B16..8: 13.2% 4.5% 0.5% direct: 8.1% skip:71.4% L0:36.4% L1:43.6% BI:20.0%
x264 [info]: 8x8 transform intra:54.7% inter:59.0%
x264 [info]: coded y,uvDC,uvAC intra: 57.0% 53.3% 14.6% inter: 9.2% 12.9% 0.3%
x264 [info]: i16 v,h,dc,p: 62% 19% 14% 4%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 43% 15% 29% 2% 2% 3% 2% 3% 2%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 41% 16% 10% 4% 5% 8% 4% 8% 4%
x264 [info]: i8c dc,h,v,p: 49% 17% 30% 4%
x264 [info]: Weighted P-Frames: Y:0.7% UV:0.2%
x264 [info]: kb/s:790.69
encoded 9730 frames, 100.70 fps, 790.69 kb/s

Start: 23.45.34
End: 23.47.11
Duration: 00:01:37

Quality: 97 %
Compressibility: 0,101

[dejong12]

How can I crop a video but resize to a certain size? For example, I have a 1920x1080 video and I want to resize it to 1280x720, but I need to crop 8 from the top (because there's a black bar there). Now when it's done with converting, the log file says that mkvmerge sets the display dimensions to 1290/720. When I play this file in full screen, I can see the black bar I just cropped out, but now at the top and and at the bottom of the video. How can I set StaxRip to stretch the video without getting any black bars? I didn't have this behaviour with earlier versions of StaxRip, I think 1.1.8. Is there some setting I need to change?

[stax76]

@luigizaninoni

Wasn't ProjectX enabled? I believe in 1.3.1.7 it should be enabled by default.

@dejong12

go to Options > Image > Aspect Ratio, you might have a cup of coffee before doing so. ;)

[Magik Mark]

Stax can you help me with this. I use handbrake and I do not know how to convert the ff configuration to staxrip.

Video:
1. Nvidia H265 mkv
2. Avg Bitrate 900
3. 2 pass encoding
4. aq_mode=1: aq_strength=2.00: qcomp=0.8: psy_rdoq=14.00
5. Option for 10 bit processing

Audio
1. AAC
2. Bitrate 192
3. 6 Channels

Can I make a template or Preset with this? I think using my GTX 960 as the encoder is a lot faster

[NikosD]

@Stax76

Hello Frank.

I have many MKV files with 2 audio streams (1 dts - hd and 1 ac-3) that I want to remux with 3 audio steams (1 dts - hd, 1 dts-hd core and 1 ac3)

So, actually I want to keep everything as is (video stream (H. 264), audio (dts-hd, ac3) and just add one more audio steam from dts-hd, which is core Dts.

Is there a way to remux 3 audio streams with StaxRip from 2 original source audio streams, keeping everything else the same ?

I don't see how could I add 3 audio streams to StaxRip's GUI.

[Schattenspieler]

If you just want to remux the files, then why would you want to use staxrip and not mkvtools instead?

[NikosD]

Do mkvtools support dts-hd to dts core conversion ?

[sneaker_ger]

Yes, check "reduce to core" in the track options. If you want to keep both versions you have to load the input file twice.

[NikosD]

It sounds fast and I think I can do a batch process using Mkvmerge GUI because I have about 7 of them.

Or I can extract the dts core and add it to the original mkv, like tebasuna51 told me.

Thanks.

[huhn]

Stax can you help me with this. I use handbrake and I do not know how to convert the ff configuration to staxrip.

Video:
1. Nvidia H265 mkv
2. Avg Bitrate 900
3. 2 pass encoding
4. aq_mode=1: aq_strength=2.00: qcomp=0.8: psy_rdoq=14.00
5. Option for 10 bit processing

Audio
1. AAC
2. Bitrate 192
3. 6 Channels

Can I make a template or Preset with this? I think using my GTX 960 as the encoder is a lot faster

NVenc HEVC doesn't support 2 pass encoding and it doesn't support aq_mode it doesn't even support B frames.

it's just a bad encoder NVenc AVC should be better at everything NVenc HEVC does. and NVenc AVC doesn't stand a chance vs x264.

vapoursynth can do 10 bit processing but i don't see any needed processing in your example (for example resizing). i don't know if this can be done with a preset too.

[Yups]

On Maxwell and newest NVAPI AVC encoding works pretty fast. No chance fo x264 in this regards. HEVC is unfinished stuff. Intel doesn't even support HEVC encoding officially for Skylake, I guess this will hapen in API 1.17 and a new Media SDK release.

[Magik Mark]

NVenc HEVC doesn't support 2 pass encoding and it doesn't support aq_mode it doesn't even support B frames.

it's just a bad encoder NVenc AVC should be better at everything NVenc HEVC does. and NVenc AVC doesn't stand a chance vs x264.

vapoursynth can do 10 bit processing but i don't see any needed processing in your example (for example resizing). i don't know if this can be done with a preset too.

Hi!

Can anybody share the best setting using NVenc HEVC? So far the quality from the original is almost the same. Except the compression is not that great compared to CPU.

[huhn]

it's hard to compress without b frames. not a lot you can do about. NVenc AVC is simply better.

[luigizaninoni]

@luigizaninoni

Wasn't ProjectX enabled? I believe in 1.3.1.7 it should be enabled by default.



Yes, enabling Projectx solves the problem, although you can't use DSS2 anymore.

There's still a difference in bitrate between LWLibav, ffms and DGDecIm, but it's much more reasonable

[Magik Mark]

it's hard to compress without b frames. not a lot you can do about. NVenc AVC is simply better.

Is this a hardware limitation or it can be corrected by a software update?

[huhn]

Is this a hardware limitation or it can be corrected by a software update?

they simply didn't finish it. and hardware encoder where never know for good quality. they are good for time critical application like nvidia shield, live streaming and steam streaming PC games to other PCs in the network and things like that.

maxwell HEVC is kind of useless. maybe pascal will support b frames...

[stax76]

@NikosD

Adding more then 2 audio streams could take many days work, I hope one day it will happen but surely not anytime soon.

@luigizaninoni

I'm not sure why DSS/DSS2 cannot load the m2v file, a workaround could be to remux to mkv, it probably can be added manually to the demuxing options in order to automate it.

[NikosD]

No problem.

I covered my needs using two apps (a GUI of eac3to from tebasuna51 and Mkvmerge GUI) in batch processing mode and two steps process, that was a matter of a few minutes to set up.

[impei]

Any chance of including VP8 encoding? It's still pretty commonly used for web based video.

[JohnLai]

Hi! StaxRip uses fixed size instead of fixed bitrate by default, for fixed bitrate there is a option: Options > Misc > Use fixed bitrate

Summoning [@stax76], rigaya just added new NvencC functionality.
Those are "Adaptive Quantization" and "Two Pass VBR".
http://rigaya34589.blog135.fc2.com/blog-entry-702.html
Hoping stax76 can update staxrip gui ASAP........


<s>--vbr-2pass (Rigaya typed wrong, it is not --vbr2, but --vbr-2pass)</s> Well......his/her 1.13v2 Nvencc64 changed it back to --vbr2
--aq

[Magik Mark]

Does anybody know what the "Level" is for in Nvidia x265 encoding? Encoder options -> Basic. What does it do? Why do we even have B frames option when actually this is not supported. Every time it encodes this is set to 0 anyway

I think the 2 pass vbr will even improve the quality of the encodes. I hope staxrip is updated soon. Can't wait to test it

[JohnLai]

Does anybody know what the "Level" is for in Nvidia x265 encoding? Encoder options -> Basic. What does it do? Why do we even have B frames option when actually this is not supported. Every time it encodes this is set to 0 anyway

I think the 2 pass vbr will even improve the quality of the encodes. I hope staxrip is updated soon. Can't wait to test it

Level?
-.- Well......In this case, level is set for warning you if there are some parameters that violated the level.
https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding_tiers_and_levels
Let say if you set reference frame to 14 on 1920x1080 video, but you want your video to be Level 4.1 compliant, the moment you set the level 4.1, the encoder will warn you the parameter reference number isn't level 4.1 compliant because the maximum reference frame for L4.1 is 6 (Most likely it will be 5 due to other parameter factors)

Cause in the future.....updated nvenc black box chip will support B frames. Might as well leaving the option there.....

Next....the VBR 2 pass isn't exactly the multipass encoding you normally find on x264,xvid and x265 sofware. Nvenc VBR 2 Pass is actually single frame two pass (the first pass analysis without lookahead on single frame)

Example;
x264 two pass = run first pass with lookahead from beginning until end of video, then starts actual bitrate allocation encoding based on data from first pass.

Nvenc VBR 2 Pass = run first pass on SINGLE frame without lookahead, then immediately starts bitrate allocation encoding. (Mostly aimed for reducing banding)


So, the most important addition is actually 'adaptive quantization'.

[Magik Mark]

Level?
-.- Well......In this case, level is set for warning you if there are some parameters that violated the level.
https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding_tiers_and_levels
Let say if you set reference frame to 14 on 1920x1080 video, but you want your video to be Level 4.1 compliant, the moment you set the level 4.1, the encoder will warn you the parameter reference number isn't level 4.1 compliant because the maximum reference frame for L4.1 is 6 (Most likely it will be 5 due to other parameter factors)

Cause in the future.....updated nvenc black box chip will support B frames. Might as well leaving the option there.....

Next....the VBR 2 pass isn't exactly the multipass encoding you normally find on x264,xvid and x265 sofware. Nvenc VBR 2 Pass is actually single frame two pass (the first pass analysis without lookahead on single frame)

Example;
x264 two pass = run first pass with lookahead from beginning until end of video, then starts actual bitrate allocation encoding based on data from first pass.

Nvenc VBR 2 Pass = run first pass on SINGLE frame without lookahead, then immediately starts bitrate allocation encoding. (Mostly aimed for reducing banding)


So, the most important addition is actually 'adaptive quantization'.

Thanks for the reply.

Can you elaborate nvenc black box. Is this a hardware or software?
What is adaptive quantization? Is this different from VBR CQP or CBR?
Can you also recommend a good level?
Can you also recommend which is better? VBR CQP or CBR. Emphasizing quality

[JohnLai]

Thanks for the reply.

1. Can you elaborate nvenc black box. Is this a hardware or software?
2. What is adaptive quantization? Is this different from VBR CQP or CBR?
3. Can you also recommend a good level?
4. Can you also recommend which is better? VBR CQP or CBR. Emphasizing quality

1 : It is both hardware (predominantly hardware) and software if you take a look on Nvenc SDK code provided at nvidia website. https://developer.nvidia.com/nvidia-video-codec-sdk

2 : Adaptive Quantization, if we follow x264 definition.......it should follow something like this https://forums.animesuki.com/showthread.php?p=1500517#post1500517
But, the name "adaptive" quantization means it isn't suppose to work in CQP mode ("constant" quantization point), but who knows how nvidia designs and programs its nvenc. I am not even sure if AQ works in CQP for nvenc. In theory, Adaptive Quantization option supposely works for VBR, VBR 2 Pass and CBR only.

From NVENC 4.0 SDK, Adaptive quantization = This is a SW feature that defines which quantization parameters to be used and changed within a row. The regular NVENC rate control is row-based. This feature helps in situations where there is a change in textures within a row.

Meanwhile, NVENC 4.0 and 5.0 SDK manual states "2-pass rate control modes help the encoder to gather statistics of the frame to be encoded before actually encoding it in the second pass, thereby resulting in optimal bit-utilization within the frame and consequently, higher encoding quality."

3 : If we take a look on industry standard, the level used by Blu-ray and maximum supported level by media player, tv decoder & etc is Level 4.1, might as well as follow it.

4 : Quality? Stick with CQP. Nvenc has issue encoding black and dark background no matter what parameters and hardware. Nothing can be done.


EDIT: I will teach you how to use DXVA decode acceleration in conjunction with NVenc encode later. (Hardware decode and hardware encode, if you have need for speed)

[Magik Mark]

Yes, Pls Teach me the best way to encode using Nvidia. Thanks a lot!

[JohnLai]

Yes, Pls Teach me the best way to encode using Nvidia. Thanks a lot!

Asus X99 Sabertooth - i7 5820 - Asus Strix GTX 960 4G - DDR4 16GB Predator - Pioneer KRP 600M (isf calibrated) - Windows 10 x64 - Kodi with DSplayer - Lav - MadVR - XYsubtitle

Transcode means the media must be decoded before it can be encoded to smaller size video or other video format.

I assume these are your system information.
Now, let start with the bad news;
1 : Core I7-5820 has no IGPU, thus depriving you from using IGPU for hardware decoding and pre/post processing purposes (Intel QuickSync / QSV is the fastest hardware decoder/encoder available for codec it can support, faster than AMD and Nvidia)

Hmm, better elaborate the marketing name;

Intel decoder = QuickSync Decoder (QSV Decoder to avoid confusion)
AMD decoder = Unified Video Decoder (UVD)
Nvidia decoder = PureVideo

Intel encoder = QuickSync Encoder (QSV Encoder)
AMD encoder = Video Coding Engine (VCE)
Nvidia encoder = Nvidia Encoder (NVENC)

2: If you often resize video, let say from 1080p to 720p or 480p, you are forced to use CPU based resizer.

Your system;
Decode(GTX 960)---->(post processing) CPU based resizer (I7-5820K)---->Encode(GTX 960).

If you have Intel QSV though ;
Decode (QSV Decode) --> (Pre processing) Intel VPP resize, yes, this is part of QSV hardware based resizer --> Encode (GTX 960)

CPU based resizing = slowing down the transcode a lot....
Too bad you don't have IGPU.
I was planning to teach you how to use Intel QSV to speed up decoding and resizing. Well, not much you can do now......we shall stick with PureVideo decode and NVENC encode.


3: Let begin ;

First picture = http://imgur.com/u3NZyyo
Second picture = http://imgur.com/12ijxKI

Generally, in your case;

"%app:ffmpeg%" -hwaccel dxva2 -i "%script_file%" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | "%app:NVEncC%" --sar %target_sar% --codec h265 --y4m --cqp 20:23:25 --cu-min 8 --cu-max 32 --aq --ref 5 --level 4.1 --bframes 0 --input - --output "%encoder_out_file%"

Free free to use different rate control method, such as --cqp 20:23:25 to --VBR2 4500 (Note, nvenc VBR 2 pass encode is really slow, gtx 970 = 150fps for encoding HEVC 1080P)
--aq stands for adaptive quantization
--cu-min and --cu-max is self explanatory.
--ref (you know it)
--bframe (no bframe support for nvenc hevc/h265, maximum 3 for h264)

Note:
We are lucky because stax76's ffmpeg has dxva2 support compiled........generally, the other ffmpeg you find around the internet doesn't enable -hwaccel functionality at all.
In case if you wanna try the adaptive quantization and vbr2pass, you need to download and extract NVEnc 1.13v2 from http://rigaya34589.blog135.fc2.com/blog-entry-702.html to replace NVEncC and NVEncC64 at Staxrip\Apps\NVEncC folder.

[Magik Mark]

Asus X99 Sabertooth - i7 5820 - Asus Strix GTX 960 4G - DDR4 16GB Predator - Pioneer KRP 600M (isf calibrated) - Windows 10 x64 - Kodi with DSplayer - Lav - MadVR - XYsubtitle

Transcode means the media must be decoded before it can be encoded to smaller size video or other video format.

I assume these are your system information.
Now, let start with the bad news;
1 : Core I7-5820 has no IGPU, thus depriving you from using IGPU for hardware decoding and pre/post processing purposes (Intel QuickSync / QSV is the fastest hardware decoder/encoder available for codec it can support, faster than AMD and Nvidia)

Hmm, better elaborate the marketing name;

Intel decoder = QuickSync Decoder (QSV Decoder to avoid confusion)
AMD decoder = Unified Video Decoder (UVD)
Nvidia decoder = PureVideo

Intel encoder = QuickSync Encoder (QSV Encoder)
AMD encoder = Video Coding Engine (VCE)
Nvidia encoder = Nvidia Encoder (NVENC)

2: If you often resize video, let say from 1080p to 720p or 480p, you are forced to use CPU based resizer.

Your system;
Decode(GTX 960)---->(post processing) CPU based resizer (I7-5820K)---->Encode(GTX 960).

If you have Intel QSV though ;
Decode (QSV Decode) --> (Pre processing) Intel VPP resize, yes, this is part of QSV hardware based resizer --> Encode (GTX 960)

CPU based resizing = slowing down the transcode a lot....
Too bad you don't have IGPU.
I was planning to teach you how to use Intel QSV to speed up decoding and resizing. Well, not much you can do now......we shall stick with PureVideo decode and NVENC encode.


3: Let begin ;

First picture = http://imgur.com/u3NZyyo
Second picture = http://imgur.com/12ijxKI

Generally, in your case;

"%app:ffmpeg%" -hwaccel dxva2 -i "%script_file%" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | "%app:NVEncC%" --sar %target_sar% --codec h265 --y4m --cqp 20:23:25 --cu-min 8 --cu-max 32 --aq --ref 5 --level 4.1 --bframes 0 --input - --output "%encoder_out_file%"

Free free to use different rate control method, such as --cqp 20:23:25 to --VBR2 4500 (Note, nvenc VBR 2 pass encode is really slow, gtx 970 = 150fps for encoding HEVC 1080P)
--aq stands for adaptive quantization
--cu-min and --cu-max is self explanatory.
--ref (you know it)
--bframe (no bframe support for nvenc hevc/h265, maximum 3 for h264)

Note:
We are lucky because stax76's ffmpeg has dxva2 support compiled........generally, the other ffmpeg you find around the internet doesn't enable -hwaccel functionality at all.
In case if you wanna try the adaptive quantization and vbr2pass, you need to download and extract NVEnc 1.13v2 from http://rigaya34589.blog135.fc2.com/blog-entry-702.html to replace NVEncC and NVEncC64 at Staxrip\Apps\NVEncC folder.

Thanks. This is very informative. What I do most of the time is try to tranascode x264 to x265 in order to decrease the file size. I would like to have a quality similar or better from the original but smallest possible file size using nvidia. CPU transcoding is taking so much time and it it taking a toll on my CPU. That's why I want to maximize the potential of GPU transcoding. I work with 1080p & 720p videos predominantly

You are very helpful. Thanks a lot!

[Magik Mark]

CQP has good quality. But the file size is not significantly reduced.

VBR2 4500 is unsuccessfull. I get this error:

Error Encoding video command line encoder: Command Line | NVIDIA H.265

Encoding video command line encoder: Command Line | NVIDIA H.265 failed with error code 1

C:\Users\Magik Mark\Desktop\StaxRip>"C:\Users\Magik Mark\Desktop\StaxRip\Apps\ffmpeg\ffmpeg.exe" -hwaccel dxva2 -i "C:\Users\Magik Mark\Desktop\Bones S11E01 temp files\Bones S11E01.avs" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | "C:\Users\Magik Mark\Desktop\StaxRip\Apps\NVEncC\NVEncC64.exe" --sar 1:1 --codec h265 --y4m --VBR2 4500 --cu-min 8 --cu-max 32 --aq --ref 5 --level 4.1 --bframes 0 --input - --output "C:\Users\Magik Mark\Desktop\Bones S11E01 temp files\Bones S11E01_out.h265"
Unknown Option : 4500av_interleaved_write_frame(): Invalid argument



StaxRip.ErrorAbortException: Encoding video command line encoder: Command Line | NVIDIA H.265 failed with error code 1

C:\Users\Magik Mark\Desktop\StaxRip>"C:\Users\Magik Mark\Desktop\StaxRip\Apps\ffmpeg\ffmpeg.exe" -hwaccel dxva2 -i "C:\Users\Magik Mark\Desktop\Bones S11E01 temp files\Bones S11E01.avs" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | "C:\Users\Magik Mark\Desktop\StaxRip\Apps\NVEncC\NVEncC64.exe" --sar 1:1 --codec h265 --y4m --VBR2 4500 --cu-min 8 --cu-max 32 --aq --ref 5 --level 4.1 --bframes 0 --input - --output "C:\Users\Magik Mark\Desktop\Bones S11E01 temp files\Bones S11E01_out.h265"
Unknown Option : 4500av_interleaved_write_frame(): Invalid argument


at StaxRip.Proc.Start() in D:\Projekte\GitHub\staxrip\General\Proc.vb:line 233
at StaxRip.BatchEncoder.Encode() in D:\Projekte\GitHub\staxrip\General\VideoEncoder.vb:line 430

[JohnLai]

CQP has good quality. But the file size is not significantly reduced.

VBR2 4500 is unsuccessfull. I get this error:

Error Encoding video command line encoder: Command Line | NVIDIA H.265

Encoding video command line encoder: Command Line | NVIDIA H.265 failed with error code 1

C:\Users\Magik Mark\Desktop\StaxRip>"C:\Users\Magik Mark\Desktop\StaxRip\Apps\ffmpeg\ffmpeg.exe" -hwaccel dxva2 -i "C:\Users\Magik Mark\Desktop\Bones S11E01 temp files\Bones S11E01.avs" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | "C:\Users\Magik Mark\Desktop\StaxRip\Apps\NVEncC\NVEncC64.exe" --sar 1:1 --codec h265 --y4m --VBR2 4500 --cu-min 8 --cu-max 32 --aq --ref 5 --level 4.1 --bframes 0 --input - --output "C:\Users\Magik Mark\Desktop\Bones S11E01 temp files\Bones S11E01_out.h265"
Unknown Option : 4500av_interleaved_write_frame(): Invalid argument

Strange. Let begin the troubleshooting;

1 : Did you update to latest NVEnc_1.13v2? You are supposed to replace the NVEncC64.exe inside Staxrip\Apps\NVEncC folder.

2 : Make sure your nvidia driver is up to date.

3 : https://github.com/stax76/staxrip/releases Are you using StaxRip_x64_1.3.1.7_beta? Cause I think older ffmpeg included by stax76 doesn't have dxva2 acceleration. Note: Not all video format can be hardware decoded, in this case, it will automatically fall back to software decoding.

4 : Some recommendation on video bitrate in case you plan to use nvenc VBR2Pass + AQ for 23 - 30fps video.

1080p = 4500
720p = 2500
480p = 1000
360p = 750
240p = 400

[Magik Mark]

Found this in rigaya's blog:

"2015.11.08 6:27 NVEncC x64 executable file is not up-to-date version, - Fixed vbr2 of did not work. x86 Edition is no problem. "

Rough translation of google. The way i understand it, x64 version is not working well

[JohnLai]

Found this in rigaya's blog:

"2015.11.08 6:27 NVEncC x64 executable file is not up-to-date version, - Fixed vbr2 of did not work. x86 Edition is no problem. "

Rough translation of google. The way i understand it, x64 version is not working well


Duh.....he said he fixed it, that why he released V2.
-.- You better update staxrip nvencc.

[Magik Mark]

Duh.....he said he fixed it, that why he released V2.
-.- You better update staxrip nvencc.

How do I do this?

[JohnLai]

How do I do this?

Are you serious?
http://i.imgur.com/WF5Okqa.png

[Magik Mark]

Thank you very much JohnLai for your patience and understanding. I'm really new to this. Continue on giving us advise. Thanks A Lot!

[Yups]

http://www.station-drivers.com/index.php?option=com_remository&Itemid=352&func=fileinfo&id=1901&lang=en


Media SDK 1.17 has been released with this driver. No documentation or changelog available yet. Intel says soon, whatever it means.

[NikosD]

@Stax76

Hello.

Is it possible to add Unicode support to StaxRip ?

I mean in filenames and path.

I have no idea how difficult/painful is this.

[NikosD]

Hi.

Just a few more questions...

1) 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)

I think, that "File Batch" mode follows your current project user preferences regarding video (video encoder profile, selected container) and audio (audio encoder profile)

But what about subs ?
Shouldn't be included by default ?
How can I select what to include in "File Batch" mode ?

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

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

I don't know if indexing is used for anything else besides video processing.

[Yups]

http://www.station-drivers.com/index.php?option=com_remository&Itemid=352&func=fileinfo&id=1901&lang=en


Media SDK 1.17 has been released with this driver. No documentation or changelog available yet. Intel says soon, whatever it means.


New documentation has been released for API 1.17.

https://software.intel.com/sites/default/files/mediasdk_release_notes.pdf
https://software.intel.com/sites/default/files/managed/47/49/mediasdk-man.pdf

[NikosD]

The release notes are for API v1.16, but the reference manual is for v1.17.

Stax76 and StaxRip has nothing to do with this, because he doesn't write code for MediaSDK.

The developer of QSVEncC which is based on MediaSDK is rigaya, you could send him an email.

Here in Doom9 there is no thread for MediaSDK.

A few years ago, the thread of QSV decoder (a decoder based on MediaSDK) by egur (Eric Gur) - an Intel employee - was very active, but now he doesn't seem interested in development any more.

[Yups]

Release notes should be for 1.17 because there wasn't Skylake support in 1.16, now it is. And there are specific 1.17 notes. Rigaya told this might be interesting for QSVEncC.

[NikosD]

API v1.17 added for the first time rotation of 90,180 and 270 degrees.

I've already asked rigaya for implementing it.

Hope he adds it and Stax76 too in StaxRip's GUI.

[NikosD]

QSVEncC v2.22 is out adding support of API v1.17 using latest unofficial drivers v4312.

It adds vpp-rotation <angle>.

[stax76]

I'll catch up on missed posts in the next days. :)

Regarding test builds I made a separate wiki page, changes not yet uploaded will be stated in the future.

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

[dejong12]

I'll catch up on missed posts in the next days. :)

Regarding test builds I made a separate wiki page, changes not yet uploaded will be stated in the future.

https://github.com/stax76/staxrip/wiki/Development-Changelog
Thanks! NVEncC 1.13 is out by the way. :)

[JohnLai]

Indeed.....VBR2pass and adaptive quantization option gui for staxrip?

[stax76]

Indeed.....VBR2pass and adaptive quantization option gui for staxrip?

please let me know if it works

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

[JohnLai]

please let me know if it works

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

Will test it later.

Stax76, I got few questions.....

1)Why is your ffmpeg version has dxva decode support, but lack of ffmpeg QSV Decode + VPP? Oh,plus NVENC support as well?

2)On 9 November 2015 or so....nvidia include GPU Resize and GPU Zero-copy for ffmpeg. https://developer.nvidia.com/ffmpeg . Scroll down the site and click the green "Download" to get nvidia pdf reference.

Reason = rigaya qsv decode + vpp resize often crash for my win10 hd4000 intel igpu. I wonder if ffmpeg is more error resilience at it?

*I actually need hardware based resizer......T_T...Although your ffmpeg has DXVA support (it actually faster in decoding than DSS2 LAVfilter copyback), the cpu based resizing really take a hit on transcoding fps.

*One ffmpeg to rule them all?

[stax76]

@JohnLai

sounds promising, I'll investigate it.

[Magik Mark]

@JohnLai

vbr2 is awesome! Good Quality & small file size. It can encode in 10 minutes for a typical 1 hour tv show

[NikosD]

1)Why is your ffmpeg version has dxva decode support, but lack of ffmpeg QSV Decode + VPP? Oh,plus NVENC support as well?

Reason = rigaya qsv decode + vpp resize often crash for my win10 hd4000 intel igpu. I wonder if ffmpeg is more error resilience at it?

...Although your ffmpeg has DXVA support (it actually faster in decoding than DSS2 LAVfilter copyback), the cpu based resizing really take a hit on transcoding fps.


I remember checking FFMpeg a while ago and for Intel, it had all HW features supported - decoding, encoding and VPP.

BUT IIRC, encoding and VPP were loosely supported, meaning very low API version support, capable for SandyBridge.

SandyBridge can support up to API v1.4 only (I think), so all the advanced rate controls and VPP functions shouldn't be supported by FFMPEG QSV encoding and VPP.

Do you know if the latest version of FFMPEG QSV has changed that ?
Is it updated ?

Now, regarding FFMpeg QSV decoding haven't seen or tested yet.

Have you done any tests regarding speed and video stream compatibility of FFMPEG QSV decoding compared to DXVA LAV and MediaSDK QSVEncC by Rigaya ?

Would be interesting to know...

P.S

I forgot to say that your problems with qsvencc decode + vpp could probably occur due to your Ivybridge setup.
I don't think Haswell or better have such problems.

What is the latest API version support of Ivy ?

[JohnLai]

@JohnLai

sounds promising, I'll investigate it.

Thanks for your hardwork. ^.^b
Oh ya, the VBR2 and AQ GUI option works without issue.

@JohnLai

vbr2 is awesome! Good Quality & small file size. It can encode in 10 minutes for a typical 1 hour tv show

Remember to use adaptive quantization too.

I remember checking FFMpeg a while ago and for Intel, it had all HW features supported - decoding, encoding and VPP.

BUT IIRC, encoding and VPP were loosely supported, meaning very low API version support, capable for SandyBridge.

SandyBridge can support up to API v1.4 only (I think), so all the advanced rate controls and VPP functions shouldn't be supported by FFMPEG QSV encoding and VPP.

Do you know if the latest version of FFMPEG QSV has changed that ?
Is it updated ?

Now, regarding FFMpeg QSV decoding haven't seen or tested yet.

Have you done any tests regarding speed and video stream compatibility of FFMPEG QSV decoding compared to DXVA LAV and MediaSDK QSVEncC by Rigaya ?

Would be interesting to know...

P.S

I forgot to say that your problems with qsvencc decode + vpp could probably occur due to your Ivybridge setup.
I don't think Haswell or better have such problems.

What is the latest API version support of Ivy ?

Even without VPP usage, rigaya QSVencC decode still crash for my system.
From rigaya qsvencc, the API version 1.11 is reported for HD4000.


FFMPEG QSV 2.8 supposes to change that......but so far....I cant find any ffmpeg cli that has full QSV decode + vpp + encode around the internet. Compiling one is too troublesome. Headache.
There is one ffmpeg with qsv_h264 decoder. ffmpeg-20150610-git-913685f-win64-static from zeronoa. The problem, it doesnt work. You will encounter exactly error as mentioned here http://ffmpeg.org/pipermail/ffmpeg-devel/2015-August/176843.html
Based on the mailing list, seems like the latest ffmpeg fixed it, but there isnt anyone compiling and making it available online.


EDIT: -.-......I just found one binary.....https://github.com/illuspas/ffmpeg-hw-win32 .........click 'Download Zip'.....

Extract out anywhere..... Benchmark time? Start command prompt.......

ffmpeg -vcodec h264_qsv -i test_track1_und.h264 -f null -

Should work? GPUZ report the HD4000 has utilization of 70 - 76% for bitrate 3072Kbps 1080p test file.

The log:

ffmpeg version 2.8 Copyright (c) 2000-2015 the FFmpeg developers
built with gcc 5.2.0 (GCC)
configuration: --prefix=/home/aliang/Library/mingw --cross-prefix=i686-w64-mingw32- --cc='ccache i686-w64-mingw32-gcc' --enable-cross-compile --target-os=mingw32 --arch=i686 --enable-small --disable-doc --disable-debug --enable-nvenc --enable-libmfx --enable-libfdk-aac --enable-libspeex --enable-libx264 --enable-libx265 --enable-libopenh264 --enable-libopus --enable-libmp3lame --enable-nonfree --enable-gpl
libavutil 54. 31.100 / 54. 31.100
libavcodec 56. 60.100 / 56. 60.100
libavformat 56. 40.101 / 56. 40.101
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 40.101 / 5. 40.101
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.101 / 1. 2.101
libpostproc 53. 3.100 / 53. 3.100
Input #0, h264, from 'test_track1_und.h264':
Duration: N/A, bitrate: N/A
Stream #0:0: Video: h264, nv12, 1920x1080, 12.50 fps, 25 tbr, 1200k tbn, 25 tbc
Output #0, null, to 'pipe:':
Metadata:
encoder : Lavf56.40.101
Stream #0:0: Video: rawvideo (NV12 / 0x3231564E), nv12, 1920x1080, q=2-31, 200 kb/s, 25 fps, 25 tbn, 25 tbc
Metadata:
encoder : Lavc56.60.100 rawvideo
Stream mapping:
Stream #0:0 -> #0:0 (h264 (h264_qsv) -> rawvideo (native))
Press [q] to stop, [?] for help
[h264_qsv @ 027bebe0] A decode call did not consume any data=N/A
Last message repeated 10 times
frame=34410 fps=179 q=-0.0 Lsize=N/A time=00:45:53.12 bitrate=N/A
video:2151kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown


Note:someone is adding qsv vpp as ffmpeg -vf support to ffmpeg on 12 Nov 16:46 2015......
http://search.gmane.org/?author=Sven+Dueking&sort=date
*deleted*

Hmm...just noticed ffmpeg -benchmark argument, might as well as testing using the command below;

ffmpeg -an -benchmark -vcodec h264_qsv -i test.mkv -f null -


Update:
-.- Darn it.....seem like ffmpeg QSV above is really slow in decoding. When I use "ffmpeg -an -benchmark -hwaccel dxva2 -i test.mkv -f null -" in order to benchmark the same video using my discrete gpu gtx 970....i got this result :

Input stream #0:0 frame changed from size:1920x1080 fmt:yuv420p to size:1920x1080 fmt:nv12
[null @ 04707300] Encoder did not produce proper pts, making some up.
frame=34410 fps=402 q=-0.0 Lsize=N/A time=00:23:55.31 bitrate=N/A
video:2151kB audio:247256kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
bench: utime=32.672s
bench: maxrss=236900kB

179fps ffmpeg QSV decoder vs 402fps ffmpeg DXVA2 gtx 970 decoder.
I guess this ffmpeg slow qsv decode is the same issue encountered by rigaya not too long ago. Before any conclusion is done......NikosD~~, can you post your ffmpeg QSV decode fps here?

ffmpeg -vcodec h264_qsv -i test.mkv -an -vcodec h264_qsv -q 20 test.h264
frame= 4795 fps=130 q=-0.0 Lsize= 141545kB time=00:03:19.78 bitrate=5804.0kbits/s

Hmm.....i wonder if one must use "-hwaccel qsv" instead of using h264_qsv decoder?
From ffmpeg documentation;
-hwaccel[:stream_specifier] hwaccel (input,per-stream)
Use hardware acceleration to decode the matching stream(s). The allowed values of hwaccel are:
qsv
Use the Intel QuickSync Video acceleration for video transcoding.
Unlike most other values, this option does not enable accelerated decoding (that is used automatically whenever a qsv decoder is selected), but accelerated transcoding, without copying the frames into the system memory.
For it to work, both the decoder and the encoder must support QSV acceleration and no filters must be used.

-.- too bad when i run "ffmpeg -hwaccels" to list out any hardware acceleration, only "dxva2" is shown.

Update2: On the bright side of the news....
http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2015-October/181843.html
Thu Oct 22 17:56:10 CEST 2015

He said 2.5 times faster? Maybe like 179fps X 2.5 = 358fps? (This figure seems to be realistic)
Oh well...let see how ffmpeg developers re-design session control and internal allocation.......(copy pasted)

[NikosD]

179fps ffmpeg QSV decoder vs 402fps ffmpeg DXVA2 gtx 970 decoder.
I guess this ffmpeg slow qsv decode is the same issue encountered by rigaya not too long ago. Before any conclusion is done......NikosD~~, can you post your ffmpeg QSV decode fps here?

ffmpeg -vcodec h264_qsv -i test.mkv -an -vcodec h264_qsv -q 20 test.h264
frame= 4795 fps=130 q=-0.0 Lsize= 141545kB time=00:03:19.78 bitrate=5804.0kbits/s

Hmm.....i wonder if one must use "-hwaccel qsv" instead of using h264_qsv decoder?
From ffmpeg documentation;
-hwaccel[:stream_specifier] hwaccel (input,per-stream)
Use hardware acceleration to decode the matching stream(s). The allowed values of hwaccel are:
qsv
Use the Intel QuickSync Video acceleration for video transcoding.
Unlike most other values, this option does not enable accelerated decoding (that is used automatically whenever a qsv decoder is selected), but accelerated transcoding, without copying the frames into the system memory.
For it to work, both the decoder and the encoder must support QSV acceleration and no filters must be used.

-.- too bad when i run "ffmpeg -hwaccels" to list out any hardware acceleration, only "dxva2" is shown.


Maybe I could try that version , although I have to say that I'm very pleased of QSVEncC by Rigaya in terms of both speed and features (+stream compatibility)

It uses ffmpeg for demuxing and muxing only and the transcoding (decoding/encoding) is processed by MediaSDK code of Rigaya and not ffmpeg's.

He has added mpeg2/vc1/hevc HW decoding and mpeg2 HW encoding that ffmpeg qsv doesn't support (I think)

Also, rigaya has implemented his transcoding pipeline without using system memory (memory copy) and that is the reason that is very fast with very low CPU utilisation.


Update2: On the bright side of the news....
http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2015-October/181843.html
Thu Oct 22 17:56:10 CEST 2015

He said 2.5 times faster? Maybe like 179fps X 2.5 = 358fps? (This figure seems to be realistic)
Oh well...let see how ffmpeg developers re-design session control and internal allocation.......(copy pasted)

Hendrik Leppkes is nevcairiel, here in Doom9 the developer of LAV filters.
You could ask him directly here without using ffmpeg forum.

[NikosD]

According to rigaya his app has a lot of differences with ffmpeg version.
I asked him and this is his reply:

ffmpeg and QSVEncC is rather different program, although it uses libavformat for demuxing and muxing.

ffmpeg does not have many encoding options for QSV which is there in QSVEncC.
They only have options below API 1.10, and they don’t have options for bluray, and many other options.

ffmpeg don’t have ability to check QSV features on runtime like QSVEncC has.

Frame rate detection algorithm is completely different, I don’t know which is better.

Also, it does not have vpp feature or full GPU transcoding currently.
But I think ffmpeg will have it soon, because I’ve heard that libav has that feature now.

Currently ffmpeg cannot decode HEVC in QSV.

On the other hand, when using QSV in ffmpeg, you can use many features which ffmpeg has,
such as various audio & video filters which are not there in QSVEncC.


I also said to him to open a thread here in doom9, supporting all his apps for hardware transcoding using AMD/Intel/Nvidia GPUs, in order to help us users and to help him too.

I think it's a good idea.

[JohnLai]

Maybe I could try that version , although I have to say that I'm very pleased of QSVEncC by Rigaya in terms of both speed and features (+stream compatibility)

He has added mpeg2/vc1/hevc HW decoding and mpeg2 HW encoding that ffmpeg qsv doesn't support (I think)

Also, rigaya has implemented his transcoding pipeline without using system memory (memory copy) and that is the reason that is very fast with very low CPU utilisation.

Hendrik Leppkes is nevcairiel, here in Doom9 the developer of LAV filters.
You could ask him directly here without using ffmpeg forum.

Oh? I never know that H.L. is nevcairiel......Maybe I will ask him later.

Latest ffmpeg from github supports qsv hardware decode; (using ffmpeg -decoders>decoder.txt to list out)

V....D h264_qsv H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (Intel Quick Sync Video acceleration) (codec h264)
V....D hevc_qsv HEVC (Intel Quick Sync Video acceleration) (codec hevc)
V....D mpeg2_qsv MPEG-2 video (Intel Quick Sync Video acceleration) (codec mpeg2video)
V..... vc1_qsv VC-1 video (Intel Quick Sync Video acceleration) (codec vc1)


Meanwhile, the ffmpeg hardware based encoders support ; (using ffmpeg -encoders>encoders.txt to list out)

V..... h264_qsv H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (Intel Quick Sync Video acceleration) (codec h264)
V..... hevc_qsv HEVC (Intel Quick Sync Video acceleration) (codec hevc)
V..... mpeg2_qsv MPEG-2 video (Intel Quick Sync Video acceleration) (codec mpeg2video)

V..... nvenc NVIDIA NVENC h264 encoder (codec h264)
V..... nvenc_h264 NVIDIA NVENC h264 encoder (codec h264)
V..... nvenc_hevc NVIDIA NVENC hevc encoder (codec hevc)

Impressively, ffmpeg latest git even has nvenc hevc encode support. I dont understand what is the difference between "nvenc" and "nvenc_h264", should be the same?


According to rigaya his app has a lot of differences with ffmpeg version.
I asked him and this is his reply:


I also said to him to open a thread here in doom9, supporting all his apps for hardware transcoding using AMD/Intel/Nvidia GPUs, in order to help us users and to help him too.

I think it's a good idea.

True, ffmpeg still doesnt support QSV VPP yet......I am hopeful it can be added to official ffmpeg trunk, same with nvidia zero copy and gpu resize.

-.-.....the only thing missing....where is AMD VCE?

*Took me some time to compile full actual working ffmpeg using ffmpeg-windows-build-helpers.
*Will benchmark later. Right now, I just make sure everything works......

[NikosD]

*Took me some time to compile full actual working ffmpeg using ffmpeg-windows-build-helpers.
*Will benchmark later. Right now, I just make sure everything works......

Thank you for the link of the compiled version of full ffmpeg.exe.


ffmpeg -an -benchmark -vcodec h264_qsv -i test.mkv -f null -

Update:
-.- Darn it.....seem like ffmpeg QSV above is really slow in decoding. When I use "ffmpeg -an -benchmark -hwaccel dxva2 -i test.mkv -f null -" in order to benchmark the same video using my discrete gpu gtx 970....i got this result :

179fps ffmpeg QSV decoder vs 402fps ffmpeg DXVA2 gtx 970 decoder.
I guess this ffmpeg slow qsv decode is the same issue encountered by rigaya not too long ago. Before any conclusion is done......NikosD~~, can you post your ffmpeg QSV decode fps here?


Using your command line:
ffmpeg -an -benchmark -vcodec h264_qsv -i test.mkv -f null -

...it is clear to me, that the h264_qsv acceleration is using a copy-back mode for decoding and I also get slow results, with very low GPU clock and a CPU usage that demonstrates a copy-back method.

ffmpeg h264_qsv is faster than Eric's Gur Intel QSV decoder (which also uses copy-back mode) but slower than LAV DXVA copy-back.

I think that -hwaccel dxva2 could use a dxva2 native mode, but unfortunately it gives me the following error with my iGPU and falls back to software mode:

[h264 @ 000001ae43867f00] Hardware accelerated decoding with frame threading is not supported.

I'm afraid we are using a wrong thread for all these, because they have nothing or little to do with StaxRip.

Make another thread regarding ffmpeg HW acceleration (decoding/encoding) to go on there...

[JohnLai]

Thank you for the link of the compiled version of full ffmpeg.exe.

Using your command line:
ffmpeg -an -benchmark -vcodec h264_qsv -i test.mkv -f null -

...it is clear to me, that the h264_qsv acceleration is using a copy-back mode for decoding and I also get slow results, with very low GPU clock and a CPU usage that demonstrates a copy-back method.

ffmpeg h264_qsv is faster than Eric's Gur Intel QSV decoder (which also uses copy-back mode) but slower than LAV DXVA copy-back.

I think that -hwaccel dxva2 could use a dxva2 native mode, but unfortunately it gives me the following error with my iGPU and falls back to software mode:

[h264 @ 000001ae43867f00] Hardware accelerated decoding with frame threading is not supported.

I'm afraid we are using a wrong thread for all these, because they have nothing or little to do with StaxRip.

Make another thread regarding ffmpeg HW acceleration (decoding/encoding) to go on there...

Yeah, maybe I should create a new thread, btw, something isn't right with the build I compile.

When either -vcodec h264_qsv or -hwaccel qsv is used, seem like it doesnt make use of the IGPU at all. Darn it.....the compile seems to be successful without any issue....I wonder what went wrong. The h264_qsv also fall back to software.

*Hope stax76 can compile one that actually work without any issue.

[NikosD]

For me h264_qsv works fine, but hevc_qsv doesn't seem to work.

[JohnLai]

For me h264_qsv works fine, but hevc_qsv doesn't seem to work.

It isn't working for my discrete gpu + headless igpu setup, all my 4 cores jumped to max utilization with 0% utilization on HD4000.

As for "Hardware accelerated decoding with frame threading is not supported." solution, you must specify;

ffmpeg -threads 1 -benchmark -hwaccel dxva2 -i test.mkv -an -sn -f null -

But...ffmpeg nvenc_hevc sure leaves a lot to be desired. Nothing much to control except specifying preset, level and tier.

ffmpeg -threads 1 -hwaccel dxva2 -i test.mkv -an -sn -preset slow -tier high -level 4.1 -vcodec nvenc_hevc output.mkv

I was playing around with ffmpeg nvenc_hevc and using the best possible option I can find from https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/nvenc.c , the end encoded video quality is downright abysmal. Full of visible blocking artifacts. Preset 'slow' has two pass enabled judging from the nvenc.c code and it should be the best preset ;

slow, medium, fast, hq, hp, bd, ll, llhp, llhq, lossless, losslesshp and default

Lack of user configurable option? How to select rate control mode? Where to specify CQP value? MinQP and MaxQP? How to specify b-frame value for H264 and number of reference frame?

I prefer rigaya NVencC encoder in this case. His encoder has more functions and produce way better video quality than ffmpeg right now.

I am hoping for the h264_qsv decoder to be working so that stax76 can include it once ffmpeg developers got the VPP resize working as ffmpeg video filter. >.> But, h264_qsv decoder doesn't seem to work in my case. Back to zero again T_T

[NikosD]

As for "Hardware accelerated decoding with frame threading is not supported." solution, you must specify;

ffmpeg -threads 1 -benchmark -hwaccel dxva2 -i test.mkv -an -sn -f null -



No, it doesn't work for me. No HW acceleration, it falls back to SW.

[JohnLai]

No, it doesn't work for me. No HW acceleration, it falls back to SW.

Strange, it works on mine though (GTX970). Oh well, I surrender.....I shall leave the hard work figuring it out to stax76.....:cool:

[Magik Mark]

Asus X99 Sabertooth - i7 5820 - Asus Strix GTX 960 4G - DDR4 16GB Predator - Pioneer KRP 600M (isf calibrated) - Windows 10 x64 - Kodi with DSplayer - Lav - MadVR - XYsubtitle


Your system;
Decode(GTX 960)---->(post processing) CPU based resizer (I7-5820K)---->Encode(GTX 960).


Generally, in your case;

"%app:ffmpeg%" -hwaccel dxva2 -i "%script_file%" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | "%app:NVEncC%" --sar %target_sar% --codec h265 --y4m --cqp 20:23:25 --cu-min 8 --cu-max 32 --aq --ref 5 --level 4.1 --bframes 0 --input - --output "%encoder_out_file%"

Free free to use different rate control method, such as --cqp 20:23:25 to --VBR2 4500 (Note, nvenc VBR 2 pass encode is really slow, gtx 970 = 150fps for encoding HEVC 1080P)

John, --y4m does not work with vbr2. Needed to remove that

Are there any other settings, parameters, filters that we can use to enhance the image and improve quality using vbr2?

[JohnLai]

John, --y4m does not work with vbr2. Needed to remove that

Are there any other settings, parameters, filters that we can use to enhance the image and improve quality using vbr2?

@Magik Mark,
Download stax76 test build from here.
https://drive.google.com/folderview?id=0B-gPKiJYuKuIRGUxckdyQU5DUkE&usp=sharing

Staxrip test build H265 Nvidia preset has the vbr2 and AQ option now.
To replace the ffmpeg dxva2, go Filters--->Source, right click and select FFVideoSource. Much more easier.

As bearer of bad news, there is nothing more we can do to enhance and improve the quality using nvenc vbr2......





@NikosD,
I can confirm the -threads 1 with -hwaccel dxva2 doesn't work on my Core I3-4330 with only IGPU HD4600 being connected to display. It falls back to software decode as you mentioned. Noteworthy, the h264_qsv decode + encode with -hwaccel qsv actually works with great speed. (GPUZ report 85-93% utilization with -hwaccel qsv enabled for complete QSV transcode)

However, on my gaming system with GTX970 (connected to display) with I5-3570K igpu HD4000(headless), h264_qsv totally fall back to software decode. But the -threads 1 -hwaccel dxva2 works for the GTX970.

Sigh.....oh well, rigaya did mention he might implement all in one fully accelerated nvencc transcode (decode + nvenc resize + zero copy + nvenc). I hope he can successfully implement it.

Although I do think future upcoming FFMPEG video filter for QSV VPP has better quality than Nvidia ffmpeg resize filter sample patch.

From ffmpeg patch note;
QSV VPP resize = VPP uses a separable 8-tap poly-phase scaling filter with adaptive filter ringing suppression.

Nvidia Nvenc resize = From the patch code, I only saw Subsample_Bilinear ? =.=""

[NikosD]

@NikosD,
Noteworthy, the h264_qsv decode + encode with -hwaccel qsv actually works with great speed. (GPUZ report 85-93% utilization with -hwaccel qsv enabled for complete QSV transcode)


Yes, -hwaccel qsv is exactly that.
Full speed transcoding without copy-back but without using any VPP filters.

When ffmpeg implements VPP, they have to keep using GPU memory only without copying to system ram, in order to be fast.


Although I do think future upcoming FFMPEG video filter for QSV VPP has better quality than Nvidia ffmpeg resize filter sample patch.

From ffmpeg patch note;
QSV VPP resize = VPP uses a separable 8-tap poly-phase scaling filter with adaptive filter ringing suppression.

Nvidia Nvenc resize = From the patch code, I only saw Subsample_Bilinear ? =.=""

It is true that even since SandyBridge at 2011, Intel had better HW implemented algorithms for everything regarding VPP (resizing, deinterlacing, scaling etc)

[Magik Mark]

@Magik Mark,
Download stax76 test build from here.
https://drive.google.com/folderview?id=0B-gPKiJYuKuIRGUxckdyQU5DUkE&usp=sharing

Staxrip test build H265 Nvidia preset has the vbr2 and AQ option now.
To replace the ffmpeg dxva2, go Filters--->Source, right click and select FFVideoSource. Much more easier.

As bearer of bad news, there is nothing more we can do to enhance and improve the quality using nvenc vbr2......

Can any other graphics card do better in x265 encoding with video enhancements, filters or processing? Something similar to CPU based encoding? How about SLI based encoding? Is this even possible with results similar to CPU?

[JohnLai]

Can any other graphics card do better in x265 encoding with video enhancements, filters or processing? Something similar to CPU based encoding? How about SLI based encoding? Is this even possible with results similar to CPU?

-.- I think you are confused about something.

HEVC/H.265 is a video compression standard.
x265 = software to encode HEVC compliant video.

As for your question, the ONLY alternative in which there might be better in hardware HEVC encoding with all those video processing done in hardware style (deinterlacing,sharpening, high quality resizing, color conversion, bla bla bla bla.......) is Intel Quicksync available only for Skylake microarchitecture. Yet......no hardware can ever beat software based encoding in term of quality.

SLI based encoding? Nvenc SDK only designed for single gpu so far.

[deekey777]

I cannot use AMD VCE:
Error Encoding using VCEEncC

Encoding using VCEEncC failed with error code 1

Unknow Options: "--input"



StaxRip.ErrorAbortException: Encoding using VCEEncC failed with error code 1

Unknow Options: "--input"


bei StaxRip.Proc.Start() in D:\Projekte\GitHub\staxrip\General\Proc.vb:Zeile 233.
bei StaxRip.AMDEncoder.Encode(String args) in D:\Projekte\GitHub\staxrip\General\VideoEncoder.vb:Zeile 1643.
bei StaxRip.AMDEncoder.Encode() in D:\Projekte\GitHub\staxrip\General\VideoEncoder.vb:Zeile 1633.
bei StaxRip.MainForm.Encode() in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:Zeile 2292.
bei StaxRip.MainForm.RunJobRecursive() in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:Zeile 3587.

Here is the Log:
------------------------------------------------------------
Encoding using VCEEncC
------------------------------------------------------------

"C:\Users\Denis x64\Downloads\StaxRip_x64_1.3.1.7_beta\Apps\VCEEncC\VCEEncC64.exe" --quality slow --cqp 22:24:27 --input "E:\Videos\HDTV-1080p-H264_007-Casino-Royale_AC3 temp files\HDTV-1080p-H264_007-Casino-Royale_AC3_new.avs" --output "E:\Videos\HDTV-1080p-H264_007-Casino-Royale_AC3 temp files\HDTV-1080p-H264_007-Casino-Royale_AC3_new_out.h264"

Unknow Options: "--input"

------------------------------------------------------------
Error Encoding using VCEEncC
------------------------------------------------------------

Encoding using VCEEncC failed with error code 1

Unknow Options: "--input"


Start: 13:21:09
End: 13:21:09
Duration: 00:00:00

PC: Windows 10 Pro x64 1511, R7 260X with the Crimson driver.

Here is a build with VCEEncC support for AMD H.264 encoding, I could not test it so I hope it works.

The build also fixes the issue with dialogs showing in command line mode.

http://www.mediafire.com/download/si8hl09q6hzdda5/StaxRip_x64_2015-09-28.7z
Oh, missed this posting. Give me 10 minutes.

Doesn't work.

[Magik Mark]

-.- I think you are confused about something.

HEVC/H.265 is a video compression standard.
x265 = software to encode HEVC compliant video.

As for your question, the ONLY alternative in which there might be better in hardware HEVC encoding with all those video processing done in hardware style (deinterlacing,sharpening, high quality resizing, color conversion, bla bla bla bla.......) is Intel Quicksync available only for Skylake microarchitecture. Yet......no hardware can ever beat software based encoding in term of quality.

SLI based encoding? Nvenc SDK only designed for single gpu so far.

As always, Thanks a lot for the info!

[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

[cegy]

stax, would it also be possible to support a custom number when using crf if the user wants to say use another number that isn't in the list ? than being locked to 18 - 26

[VelleX]

You can enter any value you want. Just click on "Options" and then go to "Basic"

[cegy]

You can enter any value you want. Just click on "Options" and then go to "Basic"

silly me :scared: i didn't even look there but thank you for pointing that you maybe a balloon tip to suggest that user can put a custom valve via this way might be handy then incase they do over look it

[Magik Mark]

Stax a new milestone in x265 has been released. Maybe its time to update. Thanks for the great work!

[NikosD]

Hello Frank.

It's been exactly two months since your last update of StaxRip (03/12/2015)

A lot of new versions of apps have been released that you include in your StaxRip release and a few bugs have been mentioned, too.

Your project seems a little bit abandoned.

Is everything OK ?

Are you still interested in this project ?

Thanks!

[JohnLai]

I am starting to worry about Stax76.........

Question for stax76, why does staxrip (currently using StaxRip_x64_2015-12-03) use ffmpeg as decoder when x265 preset is being used? I selected DSS2 as 'Source Filter' with lavfilter (copy back dxva) set as preferred directshow. So by right, Lavfilter should be used as the decoder instead of ffmpeg?

[burfadel]

FFmpeg is used to pipe the Avisynth output to x265 etc.

[JohnLai]

FFmpeg is used to pipe the Avisynth output to x265 etc.

Only piping? I don't think so....because normally, gpu-z should reports gpu usage (since the source can be dxva accelerated).

Hmm....if only there is a way to add -hwaccel dxva2 to ffmpeg when x265 preset is being used....

[stax76]

Hi everybody,

the last weeks I could only spent little time for StaxRip, I should have more time in 3-5 weeks and try to catch up then.

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

[luigizaninoni]

Welcome back !

[luigizaninoni]

The following vapoursynth plugins could be updated:
- fmtconv (latest release is v17)
- havsfunc v21
- knlmeans 7.3.0
- mvtools v10
- nnedi3 v.8
- vlsmashsource r859

Vapoursynth is now at release 31, and could be updated as well

Moreover, using Vapoursynth 29 and above, staxrip preview is broken (and "View in external player" too). Maybe because VS now uses zimg instead of SWscale

[Blowis]

Hi everybody,

the last weeks I could only spent little time for StaxRip, I should have more time in 3-5 weeks and try to catch up then.

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

Hi,
Thank you for the work you made. I love this software. I looked forward to the update.
You forgot or not have time to make qaac and MediaInfo update.
thank you again

[burfadel]

The psy-rd setting in Staxrip shows the default as being 0.30. The default psy-rd changed recently and is now 2.00 (yes, 2.00 up from 0.30).

[cegy]

The psy-rd setting in Staxrip shows the default as being 0.30. The default psy-rd changed recently and is now 2.00 (yes, 2.00 up from 0.30).

the default value that i know was also 1.00 for psy-rd and still is at least on the presets on medium or better :confused:

[burfadel]

the default value that i know was also 1.00 for psy-rd and still is at least on the presets on medium or better :confused:

The default in the latest x265 is 2.0 :).

[cegy]

The default in the latest x265 is 2.0 :).

you didn't say if it was x264 or x265 heheh :p

[burfadel]

Yes, I should have mentioned that!

[Atlantis]

Question. After you start encoding a job, it is impossible to add another job before the encoding is finished, right?

[specise_8472]

I have using this for a few years now and find it good. Just one question, why when using Nvidia GPU does it still take ~ hr to convert a 6gig file?
I know that a commercial product uses Nvidia GPU, and can convert same file with same output filesize and quality in less than 5 minutes.
I may have the wrong end of the stick here, and my painted on eyes may have missed an obvious setting. Willing to be educated on correct settings. :confused:

[JohnLai]

I have using this for a few years now and find it good. Just one question, why when using Nvidia GPU does it still take ~ hr to convert a 6gig file?
I know that a commercial product uses Nvidia GPU, and can convert same file with same output filesize and quality in less than 5 minutes.
I may have the wrong end of the stick here, and my painted on eyes may have missed an obvious setting. Willing to be educated on correct settings. :confused:

Are you sure you select "Nvidia H.264" or "Nvidia H.265" instead of "x264"?

[luigizaninoni]

Question. After you start encoding a job, it is impossible to add another job before the encoding is finished, right?

It's totally possible. You just open another instance of Staxrip, create the new job, click next, then instead of clicking "start" click "close". Close the new instance. The new job you created has been queued to the old job (you can check with tools - jobs if you wish)

[Atlantis]

Thank you.

Something strange just happened. I encoded a 4K video with x265 CRF 23. With slow preset it took 1 fps and resulted in the size of 801 MB.

With the same settings but preset medium I got 5 fps and the resulted size of 767 MB!

So with preset medium, not only it's 5 times faster, the resulted file is smaller in size! How is this possible and why would I want
to use the slow preset!

[specise_8472]

Are you sure you select "Nvidia H.264" or "Nvidia H.265" instead of "x264"?

Yes, I am sure I have correct settings. I know because a while ago I had to upgrade Video Card (980 TI) to get this feature. Old card (780 TI) did not work.

[JohnLai]

Yes, I am sure I have correct settings. I know because a while ago I had to upgrade Video Card (980 TI) to get this feature. Old card (780 TI) did not work.

Hmm....

Are you using nvenc VBR2 mode?
What is the video resolution of encoded file?
What is the video resolution of original file?
What is the video format of original file?
What is your current CPU?

Reason = Video need to be decoded first before it can be piped to nvenc. Are the video being hardware accelerated or simply using CPU to decode? (CPU decode = can be very slow depending on resolution and video codec)

What is the cpu usage when nvenc starts to encode?

If you are encoding 4K video = data from nvidia suggested 60fps for fully hardware accelerated decode and encode.

[Sivar]

Hi everybody,

the last weeks I could only spent little time for StaxRip, I should have more time in 3-5 weeks and try to catch up then.

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

I posted a Github request regarding the language of the donation page. I've donated to help your great work before and wanted to again, but I can't read German. Many items on the donation site are images so cannot be translated by software (not that I'd want to trust translation software for a financial transaction).
If you'll let me know what buttons to use, I'll send a donation.
Additionally, I offered long ago to help develop StaxRip, but never did. I am familiar with VB.NET. I am sure I could figure it out, but learning a new language (even one in the familiar .NET framework) is challenging given my time constraints.
Please accept my apology and know that I will participate in the future if I learn the language.

[Atlantis]

How to force subtitles in MKV? I click on the Container Options and I see the subtitle with all the columns, the problem is, I can not click on the Forced cell. Nothing happens when I click on it. The same for all the other cells except name which you can edit.

[TalasNetrag]

Is there a way to make StaxRipx64 work with Avisynth 32bit? I have plugins that dont have a 64bit Version, so I'm stuck with the old StaxRipx86.

[Magik Mark]

The psy-rd setting in Staxrip shows the default as being 0.30. The default psy-rd changed recently and is now 2.00 (yes, 2.00 up from 0.30).

Is this the only variable changed in x265? Are there anything else?

Thanks a lot!

[burfadel]

I believe that's the only change in parameters that was missed. The new x265 options recently seem to be all added to the Staxrip update. It looks like there may be another option, --recursion-skip in the near future to x265. If the patch gets approved (it's on the development patch list) then it will need to be added to the options.

[stax76]

Hello everybody, I've uploaded some updates and plan to do much more work shortly.

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

[stax76]

Is there a way to make StaxRipx64 work with Avisynth 32bit? I have plugins that dont have a 64bit Version, so I'm stuck with the old StaxRipx86.

It could be done with a technique called Inter-process communication but I don't have plans working on it.

How to force subtitles in MKV? I click on the Container Options and I see the subtitle with all the columns, the problem is, I can not click on the Forced cell. Nothing happens when I click on it. The same for all the other cells except name which you can edit.

What subtitle format is it?

@Sivar

I posted a fixed donation link in the github issue. VB.NET is a bit different then C# but since both are on the same platform many things are the same just with different syntax. Most of the time the code repository is up to date so anybody can send small or larger pull requests.

So with preset medium, not only it's 5 times faster, the resulted file is smaller in size! How is this possible and why would I want
to use the slow preset!

Slower presets produce better quality at a given file size, the file size will vary between presets because the presets use lots of different settings.

[Magik Mark]

Stax

Why is it the qtfiles64 folder is not included in the test build?

[stax76]

Stax

Why is it the qtfiles64 folder is not included in the test build?

It's a bit large, about 10 MB compressed, I always have to be careful not to include too large files to keep the download size under control. The default eac3to/Nero -quality=0.35 should not be worse than qaac with equivalent bitrate I believe.

[stax76]

Moreover, using Vapoursynth 29 and above, staxrip preview is broken (and "View in external player" too). Maybe because VS now uses zimg instead of SWscale

It happens only with l-smash and NVIDIA I think and a solution is far away.

[TalasNetrag]

It could be done with a technique called Inter-process communication but I don't have plans working on it.


For now I managed to build a x86 version for myself and replaced the included plugins with their 32bit versions.

Suspending a running x265 encoding doesnt work.

[luigizaninoni]

It happens only with l-smash and NVIDIA I think and a solution is far away.

It happens also with l-smash and Intel; I haven't tried with ffms though, it might work, will try as soon as I get home

[stax76]

It happens also with l-smash and Intel; I haven't tried with ffms though, it might work, will try as soon as I get home

ffms works here

Suspending a running x265 encoding doesnt work.

I've created a ticket for it: https://github.com/stax76/staxrip/issues/34

[luigizaninoni]

ffms works here


Here neither "preview" nor "play with external player" work; both ffms and lwlibavsource do not work

Intel HD4600, ffms2 v. 2.22 RC x64, fmtconv r17 x64, vslmashsource r859 x64, vapoursynth r31

Everything worked fine until vapoursynth r28 inclusive

[stax76]

Suspending a running x265 encoding doesnt work.

I've coded a new implementation for suspend, resume and abort.

Here neither "preview" nor "play with external player" work; both ffms and lwlibavsource do not work

Intel HD4600, ffms2 v. 2.22 RC x64, fmtconv r17 x64, vslmashsource r859 x64, vapoursynth r31

Everything worked fine until vapoursynth r28 inclusive

I hope the next build works, here it works at least for HD sources now.

[stax76]

I've uploaded a new build because of the vlsmashsource issue, it's best used with a new VS test build, StaxRip will ask for VS r31 but allows to use any version by pressing F12

https://github.com/stax76/staxrip/wiki/test-build

vapoursynth-r32-test1.exe (https://dl.dropboxusercontent.com/u/73468194/vapoursynth-r32-test1.exe)

[luigizaninoni]

I've uploaded a new build because of the vlsmashsource issue, it's best used with a new VS test build, StaxRip will ask for VS r31 but allows to use any version by pressing F12

https://github.com/stax76/staxrip/wiki/test-build

vapoursynth-r32-test1.exe (https://dl.dropboxusercontent.com/u/73468194/vapoursynth-r32-test1.exe)

New build works fine on both Intel and Nvidia, thanks a lot.

You might want to fix a couple of issues, though:
- you have to manually load mvsfunc.py when doing qtgmc, given that it doesn't autoload
- parameter wref is unknown in Knlmeans, so you have to manually remove each reference to wref in havsfunc.py

[luigizaninoni]

Also, preview and external player work, but crop doesn't, it gives Resize error: field based video not supported

[cegy]

@stax76 great work with the updates as you know i do like the older 1.1.8 with how it flows etc... however there's one thing that doesn't seem to be "respected" is when you load your on audio it seems to force from the "default" language the user sets i.e english to undetermined which isn't nice at all (this happens every time)being blank would of been nicer or using the default set language i did point this out a few times first here http://forum.doom9.org/showpost.php?p=1748123&postcount=755 and then again here http://forum.doom9.org/showpost.php?p=1748669&postcount=770 maybe add an option where the user can set there default language which doesn't change like it does in 1.1.8 ?

[stax76]

you have to manually load mvsfunc.py when doing qtgmc, given that it doesn't autoload

Turned out there are lot's of dependencies so I had to rewrite it with recursion and a bit OOP, it'll work in the next build.

parameter wref is unknown in Knlmeans, so you have to manually remove each reference to wref in havsfunc.py

so it's a bug in havsfunc?

Also, preview and external player work, but crop doesn't, it gives Resize error: field based video not supported

please post media info of the source and the source filter

@cegy

please post media info of the audio source

[cegy]

Turned out there are lot's of dependencies so I had to rewrite it with recursion and a bit OOP, it'll work in the next build.



so it's a bug in havsfunc?



please post media info of the source and the source filter

@cegy

please post media info of the audio source

the audio file doesn't matter as it seems its trying to read the language from the input file or something? also my point is that if the language is already set to say english why does it change it when 1.1.8 doesn't (this is the point i'm making)
anyways here's a gif to show you what i mean since the last one did help you greatly :)

http://gfycat.com/ScientificGleamingElectriceel

you'll see what it is i'm trying to show keep in mind it was a quick video to show the issue

[stax76]

the audio file doesn't matter as it seems its trying to read the language from the input file or something? also my point is that if the language is already set to say english why does it change it when 1.1.8 doesn't (this is the point i'm making)
anyways here's a gif to show you what i mean since the last one did help you greatly :)

http://gfycat.com/ScientificGleamingElectriceel

you'll see what it is i'm trying to show keep in mind it was a quick video to show the issue

The gif is great, I opened a ticket for it.

https://github.com/stax76/staxrip/issues/35

[stax76]

I uploaded finally a new build to github since the last was somehow old.

https://github.com/stax76/staxrip/releases

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

[Magik Mark]

Thanks for the update. Is it possible to have ICC build? Encoding is faster in intel based CPUs

[RieGo]

nice to see you back stax!
i really like your gui.
have you thought about adding vapour synth portable (i think this exists, right?) and maybe an updating mechanism similar to megui?
just wondering...
anyways keep up the good work :)

[stax76]

Thanks for the update. Is it possible to have ICC build? Encoding is faster in intel based CPUs

It's not a special interest of mine, is there a particular software of what you would prefer an Intel build and are benchmarks available?

have you thought about adding vapour synth portable (i think this exists, right?) and maybe an updating mechanism similar to megui?
just wondering...
anyways keep up the good work :)

I'm happy with the current distribution, I'm the developer and maintainer so I'm looking different at things than users. Suggestions are very important so if you see particular advantages in particular things it's always important to post about it.

[dandyclubs]

today i install StaxRip_x64_1.3.2.0
python-3.5.1-amd64-webinstall
vapoursynth-r31

L-SMASH-Works-r875-20160202-64bit is not work.. StaxRip crash..

i change vslsmashsource.dll in L-SMASH-Works-r859-20160108-64bit.7z

fine work.

[stax76]

i use vslsmashsource.dll in L-SMASH-Works-r859-20160108-64bit.7z

fine work..

but L-SMASH-Works-r875-20160202-64bit is not work..

Hello, does it generally not work or has a problem only with a particular source file or source file type?

[dandyclubs]

Hello, does it generally not work or has a problem only with a particular source file or source file type?

eac3to blu-ray to mkv

General
Unique ID : 209022388361333221829617356128763458446 (0x9D403F67E82874FDFBF49EA9A6CF338E)
Complete name : K:\WORK\99\99.mkv
Format : Matroska
Format version : Version 1
File size : 19.2 GiB
Duration : 2h 0mn
Overall bit rate mode : Constant
Overall bit rate : 22.9 Mbps
Encoded date : UTC 2016-02-29 21:37:22
Writing application : eac3to
Writing library : Haali DirectShow Matroska Muxer 1.13.138.14
ErrorDetectionType : Per level 1
CRC_Error_Pos : 231

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Muxing mode : Container profile=@0.0
Codec ID : V_MPEG4/ISO/AVC
Duration : 2h 0mn
Bit rate mode : Constant
Bit rate : 23.0 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 30.000 fps
Original frame rate : 29.970 (30000/1001) fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan type, store method : Separated fields
Scan order : Top Field First
Bits/(Pixel*Frame) : 0.370
Stream size : 18.9 GiB (98%)
Default : No
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

[dandyclubs]

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

K:\WORK\99\99.h264

General
Complete name : K:\WORK\99\99.h264
Format : AVC
Format/Info : Advanced Video Codec
File size : 19.2 GiB
Overall bit rate mode : Constant

Video
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Bit rate mode : Constant
Bit rate : 23.0 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 29.970 (30000/1001) fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan type, store method : Separated fields
Scan order : Top Field First
Bits/(Pixel*Frame) : 0.370
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709


------------------------------------------------------------
Index LWLibav
------------------------------------------------------------

"C:\Program Files (x86)\VapourSynth\core64\vspipe.exe" "K:\WORK\99\99.vpy" NUL -i


------------------------------------------------------------
Error Index LWLibav
------------------------------------------------------------

Index LWLibav failed with exit code: -1073741819 (0xC0000005)

The exit code might be a system error code: 0xp에 있는 명령이 0xp의 메모리를 참조했습니다. 메모리는 s될 수 없습니다.



Start: 오후 10:35:46
End: 오후 10:35:46
Duration: 00:00:00


------------------------------------------------------------
Exception
------------------------------------------------------------

StaxRip.ErrorAbortException: Index LWLibav failed with exit code: -1073741819 (0xC0000005)

The exit code might be a system error code: 0xp에 있는 명령이 0xp의 메모리를 참조했습니다. 메모리는 s될 수 없습니다.



위치: StaxRip.Proc.Start() 파일 D:\Projekte\GitHub\staxrip\General\Proc.vb:줄 235
위치: StaxRip.MainForm.Indexing() 파일 D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:줄 3064
위치: StaxRip.MainForm.Demux() 파일 D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:줄 3021
위치: StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean isNotEncoding) 파일 D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:줄 1838

[stax76]

@dandyclubs

Here it works with a similar source, full log:

http://pastebin.com/efU7ShE0

Interesting could be this:

The exit code might be a system error code: 0xp에 있는 명령이 0xp의 메모리를 참조했습니다. 메모리는 s될 수 없습니다.

I don't know about the foreign characters, can you send me the original log file as email attachment? My mail address is in StaxRip's main menu.

@cegy

For regular audio files the old behavior is restored.

[stax76]

@dandyclubs

Maybe you can cut 100 mb with mkvtoolnix gui and upload it to media fire or google drive. If it fails here too I'll forward it to the l-smash author.

[dandyclubs]

Sorry

log file was overwrited

[dandyclubs]

@dandyclubs

Maybe you can cut 100 mb with mkvtoolnix gui and upload it to media fire or google drive. If it fails here too I'll forward it to the l-smash author.


check email

have crash only blu-ray to mkv file by eac3to

[Groucho2004]

The exit code might be a system error code: 0xp에 있는 명령이 0xp의 메모리를 참조했습니다. 메모리는 s될 수 없습니다.

I don't know about the foreign characters
It's Korean and refers to this NTSTATUS code:
0xC0000005
STATUS_ACCESS_VIOLATION
The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

[luigizaninoni]

so it's a bug in havsfunc?

Sorry, there was an older Knlmeanscl.dll in autoload folder, I removed it and there is no need to edit havsfunc.py. Wref parameter is recognised.

Crop is fine in 1.3.2.0. Thank you very much

[stax76]

@dandyclubs

nice clip ;), I've created a ticket and let you know when VFR-maniac replies.

[cegy]

@dandyclubs

Here it works with a similar source, full log:

http://pastebin.com/efU7ShE0

Interesting could be this:

The exit code might be a system error code: 0xp에 있는 명령이 0xp의 메모리를 참조했습니다. 메모리는 s될 수 없습니다.

I don't know about the foreign characters, can you send me the original log file as email attachment? My mail address is in StaxRip's main menu.

@cegy

For regular audio files the old behavior is restored.

that's great news @stax76 i guess i need to wait for the next test build then ?

[stax76]

that's great news @stax76 i guess i need to wait for the next test build then ?

yes but probably won't be long

[cegy]

also another bug for you to sort out, its the video comparison it seems if the filter is set to something other than manual ? it will fail i only notice this myself since i like to use dgsource myself

http://gfycat.com/BrokenHoarseFruitbat

would it also be possible to show what the crop values are set to via mouse over event or something since the "preview" tab is missing

[stax76]

The source filter used for the video comparison is hardcoded to ffms2 I think so it don't matter what source filter is in the main dialog, choosing DGSource triggered a bug however, it'll be fixed.

The crop values mouse over issue I don't understand yet, you mean in the video comparison?

[cegy]

The source filter used for the video comparison is hardcoded to ffms2 I think so it don't matter what source filter is in the main dialog, choosing DGSource triggered a bug however, it'll be fixed.

The crop values mouse over issue I don't understand yet, you mean in the video comparison?

nah as in if the user was to make the crop in there video (the video there going to encode) how can they get a preview of what values that was used ?

as in 1.1.8 you had the preview tab when you double click on crop
https://i.imgur.com/EFjMyQG.png

[stax76]

You can find the crop values:

in the crop dialog in the status bar

in the options dialog under Image | Crop

double click filters to show Scripting Editor > show context menu > Script Preview

[cegy]

You can find the crop values:

in the crop dialog in the status bar

in the options dialog under Image | Crop

double click filters to show Scripting Editor > show context menu > Script Preview

oh i would of never known that due to being hided so well away wouldn't a button make it easier for the user to find it ? (far left side from ok and cancel maybe ?)
better yet if you want to keep it clean but to the point how about ? (not sure of the name click able title?)
https://i.imgur.com/q5ehwmG.png

[Magik Mark]

Stax,

Are the settings for the default template been updated. For instance, in x265 the default psy rd was changed from 0.3 to 2

[stax76]

My code is fairly up-to-date, I'm using a diff checker tool to catch changes. I did not reset the profiles and templates though, if you want to reset there is a reset feature for both profiles and templates.

[Magik Mark]

My code is fairly up-to-date, I'm using a diff checker tool to catch changes. I did not reset the profiles and templates though, if you want to reset there is a reset feature for both profiles and templates.

Tried doing that. the psy rd remain 0.3 so I have to manually change it

stax, I'm trying to use "RemoveGrainHD" in lieu of "RemoveGrain" for HD sources. Is this possible?

Thanks

[stax76]

have you seen main menu > tools > directories > plugins ?

[Magik Mark]

I'm getting script error - "There is no function named RemovegrainHD

This is what I did. I copied the Removegrainhd.dll to the avisynth plugin folder then I added Removegrainhd in the filter profile.

Did I missed something?

Thanjks

[stax76]

Are you aware that StaxRip x64 supports only AviSynth+ x64 and AviSynth+ x64 supports only x64 plugins?

http://avisynth.nl/index.php/AviSynth%2B#AviSynth.2B_x64_plugins

[stax76]

some fixes and a feature requested since years

### Download

https://drive.google.com/folderview?id=0B-gPKiJYuKuIRGUxckdyQU5DUkE&usp=sharing

http://1drv.ms/1OqPDOe

### New Features

- support for 3 or more audio tracks added to the muxing dialog
- code preview added to filters menu and script preview renamed to code preview in script editor

### Fixed Bugs

- fixed window freeze in eac3to dialog happening when eac3to fails on the input.
- fixed showing filter selection dialog even if the source is vpy or avs
- fixed StaxRip trying to auto correct the script even if the source is avs
- fixed StaxRip recalculating the video bitrate even when the fixed bitrate option is used
- avi muxer supports two audio tracks now
- in some cases the two audio output file paths were identical
- moving subtitles up and down wasn't working correctly
- the new mp4box update should fix a bug many people reported

### Tweaks

- better error handling when the source is vpy or avs
- when loading an audio file without language info the language of the audio profile/stream stays instead of being changed to undetermined

### Updated Tools

- mp4box 0.6.0
- QSVEncC 2.37

[TalasNetrag]

Is it possible to give the infotext in the preview a black border? Sometimes it's hard to see anything.
http://www.mediafire.com/convkey/3ea0/1ki12j1ut8gs6154g.jpg (http://www.mediafire.com/view/1ki12j1ut8gs615/Infotext.PNG)

Minor inconsistency: When opening a file normaly StaxRip asks to select a source filter and if any of the audio track should be demuxed.
When opening a file with the "open with" dialog (rightclick->open with->StaxRip) StaxRip chooses the source filter and demuxes all audio tracks.

[stax76]

Is it possible to give the infotext in the preview a black border? Sometimes it's hard to see anything.

yes, good idea!

Minor inconsistency: When opening a file normaly StaxRip asks to select a source filter and if any of the audio track should be demuxed.
When opening a file with the "open with" dialog (rightclick->open with->StaxRip) StaxRip chooses the source filter and demuxes all audio tracks.

It's by design that if you use the StaxRip CLI then no dialogs are shown because CLI is often used by batch files, I could make a CLI switch to control this but I'm not sure if showing dialogs should be default in CLI mode.

[stax76]

mp4box was broke because I had compiled in in debug mode...
The info in the preview looks better and is readable regardless of the current background
added a command line switch -show-dialogs:bool and project option 'Show all dialogs when invoked from CLI', by default dialogs are not shown when StaxRip receives CLI arguments


https://github.com/stax76/staxrip/wiki/test-build

[RieGo]

found a little bug:
trying to open a file containing the ' character with vapoursynth results in an error. didn't try avisynth.

[stax76]

If I remember right then Python and JavaScript allow strings defined with both ' and " and since VB.NET uses " I used ' to define all the Python code, if I change it to " then it will be fine I hope.

[RieGo]

If I remember right then Python and JavaScript allow strings defined with both ' and " and since VB.NET uses " I used ' to define all the Python code, if I change it to " then it will be fine I hope.

yeah, that's what i thought about as well. hopefully it works :)

[stax76]

QSVEncC64.exe --la-depth 30 --la-icq 20

No matter which value I use for --la-icq using QSVEncC64 the resulting file is always 41.2 Mbps according to MediaInfo, am I doing something wrong here?

[NikosD]

Try without --la-depth parameter, haven't tested recently though

I always use net --icq.

[Yups]

mp4box was broke because I had compiled in in debug mode...
The info in the preview looks better and is readable regardless of the current background
added a command line switch -show-dialogs:bool and project option 'Show all dialogs when invoked from CLI', by default dialogs are not shown when StaxRip receives CLI arguments


https://github.com/stax76/staxrip/wiki/test-build



This version doesn't work anymore with videos without audio stream.


http://abload.de/img/ffmpegx7si7.png

[stax76]

This version doesn't work anymore with videos without audio stream.


http://abload.de/img/ffmpegx7si7.png

It will be fixed in the next build.

[Q-the-STORM]

I need some help encoding a 4:2:2 10bit v210 avi to 4:2:0 10bit x264 and 4:2:0 8bit x264....
I'm using x64 1.3.2.0 and have avisynth+ and LAV Filters installed...

DSS2 is giving this error:
DSS2: Can't open "E:\File.avi"

Connect filters (Src_Out + VS_In): (80040217) No combination of intermediate filters could be found to make the connection.

(E:\File temp files\File_Source.avs, line 2)


ffvideosource after indexing:
System exception - Access Violation
(E:\File temp files\File_Source.avs, line 2)

avisource:
AVISource couldn't locate a decompressor for fourcc v210

(E:\File temp files\File_Source.avs, line 1)

DirectShowSource:
DirectShowSource couldn't open file E:\File.avi:
Cannot play back the video stream: no suitable decompressor could be found.

(E:\File temp files\File_Source.avs, line 1)

the other ones result in crashing staxrip...

I have no problems watching the clip with MPC-HC + LAV...

[Dust Signs]

Switching from StaxRip to StaxRip x64, I find the support of AviSynth+ and VapourSynth really confusing. I tried to reproduce what I did with StaxRip previously - processing a video with MDegrain with multiple threads (previously using AviSynth MT) for parallelization - but was not able to do so.
I downloaded the release from a few days ago and installed (its shipped version of) AviSynth+. I noticed that mvtools were not available for it, so I uninstalled AviSynth+ and installed VapourSynth instead. In this configuration, when opening a video, StaxRip x64 complains that AviSynth+ is not installed. This does not make sense to me - I thought that VapourSynth is an AviSynth "replacement" just like AviSynth+, not something that builds on the latter.
Anyways, I proceeded to install AviSynth+ again. With both (AviSynth+ and VapourSynth) installed, I could open video files again, but I was not able to use MDegrain2 - the new syntax of VapourSynth and the available noise-filtering templates confused me. Calls like Prefetch(4) still work, but they do not seem to be VapourSynth syntax. I doubted that VapourSynth was even invoked in any operation that I did.
Honestly, I am lost at this point. There seems to be no proper documentation regarding how and when to use AviSynth+ or VapourSynth in StaxRip x64 - whether they can/should/must be combined or whether they can be used without one another. How can a plugin like mvtools that is only available for VapourSynth be used from within StaxRip? Would anyone be so kind as to shed some light onto this?

Thank you very much
Dust Signs

[stax76]

@Q-the-STORM

I wasn't able to open such a file with AviSynth and can't tell you if it can be done. It has worked with ffms2 under VapourSynth and x265 > Basic > Depth: 10 bit

@Dust Signs

I'm sorry you had a bad experience, when you open a file the filter selection should show where you can choose ffms2 for VapourSynth, if VapourSynth and Python aren't installed StaxRip should show the apps dialog which has download links for VapourSynth and Python.

[LexSfX]

You have "DTS" listed twice in the original post's "output codecs".

[stax76]

You have "DTS" listed twice in the original post's "output codecs".

?????

[LexSfX]

Output Codecs: XVID, H.264, H.265, VP9, MP3, AC3, AAC, VORBIS, DTS, FLAC, OPUS, DTS


This is all I meant. See? It just looks a bit confusing.

[stax76]

This is all I meant. See? It just looks a bit confusing.

yes sorry, I'll update it using this:

http://feralhosting.github.io/

[Dust Signs]

I'm sorry you had a bad experience, when you open a file the filter selection should show where you can choose ffms2 for VapourSynth, if VapourSynth and Python aren't installed StaxRip should show the apps dialog which has download links for VapourSynth and Python.

I downloaded StaxRip x64 again, chose a new settings folder, installed Python and VapourSynth and tried to open a file. StaxRip complains that AviSynth+ is not installed and does not allow me to proceed.
I tried to set different source filters in Tools\Settings\Source Filters manually, but the problem prevails. Even though StaxRip x64 reports the installation status of both, Python and VapourSynth to be OK, StaxRip x64 prompts me to install AviSynth+.

Best regards
Dust Signs

[stax76]

I downloaded StaxRip x64 again, chose a new settings folder, installed Python and VapourSynth and tried to open a file. StaxRip complains that AviSynth+ is not installed and does not allow me to proceed.
I tried to set different source filters in Tools\Settings\Source Filters manually, but the problem prevails. Even though StaxRip x64 reports the installation status of both, Python and VapourSynth to be OK, StaxRip x64 prompts me to install AviSynth+.

You can find some info here:

https://github.com/stax76/staxrip/wiki/Test-Build

http://forum.doom9.org/showthread.php?p=1759453#post1759453

[Dust Signs]

I'm having the same problem with the test build. StaxRip x64 still complains about AviSynth+ not being installed when opening any video file.
EDIT: I just saw that the last section of the "Test Build" page refers to changes that you have made locally; does this mean that the next test build will work with VapourSynth (i.e. without AviSynth+)?

Best regards
Dust Signs

[stax76]

It's because before you open a source your script is AviSynth, you can change it to VapourSynth with context menu before you open the source, in the next build it won't matter.

[Dust Signs]

It's because before you open a source your script is AviSynth, you can change it to VapourSynth with context menu before you open the source, in the next build it won't matter.

EDIT: I found it. Wow, that one is really well hidden. Would it be possible to make it more visible or is the next build making this context menu completely obsolete?

Best regards
Dust Signs

[stax76]

Filters > menu > Filter Setup

but due to a critical bug I'm uploading a new build shortly anyway

[stax76]

The new support for more then two audio tracks had a bad bug so I've uploaded a new build:

https://github.com/stax76/staxrip/wiki/Test-Build

[Pengaban]

Hi,

I tried to use StaxRip with NVENC to encode some .ts Files but I always get the following error:


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

Encoding using NVEncC failed with error code 1

No GPU found suitable for NVEnc Encoding.





The used Nvidia GPU in this system is a GT630 v2. This is a GK208 Keppler Chip(double checked this with GPU-Z) which I thought should be able to use the first gen NVENC.

Sys: Win7 64bit (SP1), Nvidia driver 320.49

Maybe I have to use a newer Nvidia GPU driver? Any ideas on that?

Thanks!

[NikosD]

The Nvidia GT630 v2 is a Kepler card and NVEncC should work for you.

Your driver is ancient...

Install the latest and it will do the job.

[JohnLai]

Maybe he choose NVIDIA H.265 preset instead of Nvidia H.264 preset.
Remember, Nvidia Kepler only supports NVENC H264 encoding.
HEVC encoding is only supported on Maxwell V2 (Too bad for Maxwell V1).

[Dust Signs]

The new support for more then two audio tracks had a bad bug so I've uploaded a new build:

https://github.com/stax76/staxrip/wiki/Test-Build

Nice, thank you. Is there any automatic cropping available yet when using VapourSynth?

Best regards
Dust Signs

[Pengaban]

Thanks!

For the driver version I was incorrect it's actually a newer 347.52 from 2015 installed on that sys.

For the GPU error I suspect that maybe the GPU memory type is the cause for the error?
This GT 630 has only cheap DDR3 with 14.4GB/s bandwith(according to GPU-Z). I will try another GK208 GPU laying around a "GT 640" with GDDR5 memory on the system and 40.1GB/s bandwith. Maybe that will do the trick.

Buying a new second gen maxwell eg. GTX950 for about 150,- € only for transcoding isn't worth it for me. Pascal is around the corner. Hopefully there will be some low end Pascal GPUs for NVENC usage.


I double checked that I use "NVIDIA H.264" at encoder settings. I'm using StaxRip v1.3.1.7 and I read this article for a first orientation and setup:
http://www.techspot.com/article/1131-hevc-h256-enconding-playback/page5.html

[NikosD]

Thanks!

For the driver version I was incorrect it's actually a newer 347.52 from 2015 installed on that sys.

For the GPU error I suspect that maybe the GPU memory type is the cause for the error?


Still, too old driver.

I suggest you to download and install latest driver for your system.

GPU memory type and performance has nothing to do with such compatibility errors.

[NikosD]

Tried latest StaxRip x64 test-build

1)I have asked this previously.

For the file below in "Single file" mode I can mux subtitles.
In "file batch" mode, I can't.

Sample:
http://www.filedropper.com/00063

Bug or limitation ?


2) More than 2 audio streams muxing looks good.


3) VCEEnc has a newer version 1.03v2 here:

https://onedrive.live.com/?id=6BDD4375AC8933C6%21516&cid=6BDD4375AC8933C6


4) I think going to Help -> Support forum should point here and not in videohelp.com forum :)

[luigizaninoni]

Is it possible to use x265.exe (for example 8-bit or 10-bit) instead of the multilibrary x265_ml.exe ?

I'm asking this because there are several builds available on the web, updated daily, based of various compilers, while as far as I know x265_ml.exe is only available in Ligh's builds, which are updated less frequently and built with a single compiler.

So using single libraries might be, occasionally, more flexible.

[burfadel]

--psy-rd in Staxrip is only adjustable down from the default value of 2.00. The value in x265 can be up to 5.00.

[NikosD]

Has anyone succeeded in using HW encoding (QSV, NVEnc, VCEEnc) on a laptop with GPU switching technology ?

Like Nvidia Optimus or AMD Enduro.

[Havokdan]

Has anyone succeeded in using HW encoding (QSV, NVEnc, VCEEnc) on a laptop with GPU switching technology ?

Like Nvidia Optimus or AMD Enduro.

Me with Nividia Optimus (Intel 4000 and GTX 675MX) in Clevo P151.

[NikosD]

How ?
Can you describe it a little ?

Which program worked ?

QSVEncC, NVEncC or both ?

[Havokdan]

Both worked, used the H264 version. I've never used these encoders before, I was surprised by their speed. Just to make sure I'm not mistaking, you refer to these encoders that I highlighted in the image below?

https://i.imgur.com/KLjPCC3.png

As were the ones I used.

* I can understand a little English, but to talk I use google translator, so if something sounds incomprehensible, i am sorry.

[stax76]

--psy-rd in Staxrip is only adjustable down from the default value of 2.00. The value in x265 can be up to 5.00.

Will be fixed in the next build.

Is it possible to use x265.exe (for example 8-bit or 10-bit) instead of the multilibrary x265_ml.exe ?

It should work if you use x265_ml.exe as name and don't use incompatible switches. StaxRip will notice that it has a unknown build date but you can change the date and version with F12.


For the file below in "Single file" mode I can mux subtitles.
In "file batch" mode, I can't.

Bug or limitation ?


it's a limitation, please create issue/ticket for it

I think going to Help -> Support forum should point here and not in videohelp.com forum

I'll show both and add some other things to the help menu.

Is there any automatic cropping available yet when using VapourSynth?

unfortunately no, please create issue/ticket for it

[NikosD]

@Stax76

It seems that you have some interesting options for decoder using NVEncC, like ffmpeg DXVA2 and QuickSync.

Is it possible to add those to VCEEncC too ?

[Pengaban]

Hi guys,

just wanted to give a quick feedback on the NVENC error. My educated guess was right about the GPU RAM Type. I just swapped the GT630(DDR3) with the GT640(GDDR5) without changing anything on the software side and it worked like a charm with the 347.52 driver. Remember the GPU cores are the same on the two cards both GK208. Maybe this is something worth to mention anywhere in the documentation?

Done some quick&dirty test on a FullHD.ts(variable bitrate ~9MBit/s) file recorded from SAT TV. I got ~33 fps with NVENC H.264(Mode:CQP standard) compared to 3,x fps with x264 on the same old system(Athlon64 x2 DualCore 2GHz). OK x264 at "medium" settings managed to get a 50% smaller file compared to the original .ts as NVENC only managed a ~20% reduction. But I think room to improve on that.

Looking forward to Nvidia Pascal and some lowend GPUs with enhanced NVENC support.

[NikosD]

My educated guess was right about the GPU RAM Type. I just swapped the GT630(DDR3) with the GT640(GDDR5) without changing anything on the software side and it worked like a charm with the 347.52 driver.


That is really strange.

Are you 100% sure your GT630 is not a Fermi card ?


Done some quick&dirty test on a FullHD.ts(variable bitrate ~9MBit/s) file recorded from SAT TV. I got ~33 fps with NVENC(Mode:CQP standard) compared to 3,x fps with x264 on the same old system(Athlon64 x2 DualCore 2GHz).


That is really slow!

Did you try to choose as decoder the CUVID decoder of latest StaxRip versions ?

It should be a lot faster than your CPU (SW) decoder.

[Pengaban]

That is really strange.

Are you 100% sure your GT630 is not a Fermi card ?

.

I'm pretty sure, I checked it with GPU-Z(still got both screenshots on my tablet). As far as I know GPU-Z only reads out the BIOS information so there might be small chance for disinformation here. I never changed the BIOS on those cards myself. But on the other hand I remember exactly when I bought this very GT630 / 640 GPUs because at that time I wanted a power efficient replacement for some stone aged onboard GPUs. I got information about a newer generation of low end GPUs from NV at that time that used small & efficient mobile Chips(GK208).
So finally the power draw of the whole system was about equal with the GT630 in place compared to the old onboard GPU.


....
That is really slow!

Did you try to choose as decoder the CUVID decoder of latest StaxRip versions ?

It should be a lot faster than your CPU (SW) decoder.

Ok I will have a look on that, so there might already be a much faster encoding in place also for the older first gen. NVENC H.264 cards?

Is this "CUVID" an new ecoding "Mode" from the NCENC encoder?

[NikosD]

Ok I will have a look on that, so there might already be a much faster encoding in place also for the older first gen. NVENC H.264 cards?

Is this "CUVID" an new ecoding "Mode" from the NCENC encoder?

No.
CUVID has nothing to do with encoding.

CUVID is a fast HW decoder in order to accelerate the transcoding process (decoding+encoding)

Because you decode the clip with your very slow CPU which is slowing down the whole process and your NVENC (HW) encoder, which is faster than your CPU.

[Pengaban]

No.
CUVID has nothing to do with encoding.

CUVID is a fast HW decoder in order to accelerate the transcoding process (decoding+encoding)

Because you decode the clip with your very slow CPU which is slowing down the whole process and your NVENC (HW) encoder, which is faster than your CPU.

Is that decoding switch at the advanced tab of the NVENC encoder, I think I tried that yesterday and it got me an error that it didn't found QuickSync on my sys. Obviously cause its a stone aged AMD athlon 64 and no newer Intel CPU with QuickSync support.

[NikosD]

Yes, that switch.
You have to select the NVEnc cuvid decoder.

Tell us your results on the same clip and settings.

[Pengaban]

I tried "NVEnc cuvid" decoder with StaxRip x64 : 1.3.1.7(testbuild -> StaxRip_x64_2016-02-07_test.7z) and got that error.

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

Encoding using NVEncC failed with exit code: -1073741819 (0xC0000005)

The exit code might be a system error code....



Maybe a newer Geforce driver needed?


Edit: The same error code with AviSynth/VapourSynth used as decoder instead of "NVEncC cuvid".

[NikosD]

Your StaxRip test build is not the latest, find the link from the first page of this thread.

I have told you at least 2 times to upgrade your driver, but you preferred to upgrade your HW in order to avoid updating your SW!

That's a very rare behavior and sorry I can't help you more than this.

I can't do the update for you.

[luigizaninoni]

It should work if you use x265_ml.exe as name and don't use incompatible switches. StaxRip will notice that it has a unknown build date but you can change the date and version with F12.


Works fine, thanks

[Magik Mark]

Stax

Is it possible to incorporate audio channels greater than 6?

[stax76]

Is it possible to incorporate audio channels greater than 6?

It depends on if there are tools which support it.

It seems that you have some interesting options for decoder using NVEncC, like ffmpeg DXVA2 and QuickSync.

Is it possible to add those to VCEEncC too ?

I hope it's just a little bit copy and paste, next build allows m2ts files as subtitle source file for mkv muxing.

[NikosD]

I hope it's just a little bit copy and paste



Then you could put the ffmpeg DXVA2 option to QSVEncC too.

It would be interesting to test the performance and the compatibility of the different decoders on Intel hardware.


Next build allows m2ts files as subtitle source file for mkv muxing.

Thanks, I'll try it.

[NikosD]

Two suggestions for the first page of this thread:

The phrase "AMD/Intel/NVIDIA GPU encoding" could be rephrased as "AMD/Intel/NVIDIA HW encoding" because GPUs do so little or nothing these days for the encoding, so HW encoding is more accurate, I think.

The phrase "Intel Quick Sync H.264 encoding" should be "Intel Quick Sync H.264/H.265 encoding" because you have already added H.265 GUI for QSVEncC.

[Yups]

Two suggestions for the first page of this thread:

The phrase "AMD/Intel/NVIDIA GPU encoding" could be rephrased as "AMD/Intel/NVIDIA HW encoding" because GPUs do so little or nothing these days for the encoding, so HW encoding is more accurate, I think.



On Intel its GPU is a big factor for encoding, in quality and performance as well.

[NikosD]

Yes, but even on Intel there is a mode for Skylake to completely isolate GPU from encoding.

For Nvidia and AMD, GPU has zero impact on both performance and quality.

[Yups]

Yes, but even on Intel there is a mode for Skylake to completely isolate GPU from encoding.



This mode doesn't make sense because the quality is very poor and performance can be slower as well. The GPU has a big impact for the quality of Intels Hybrid encoding. It's just a power saving mode which is useless for most people.

[NikosD]

OK...But StaxRip is an app that leverages HW encoding for all brands AMD/Nvidia/Intel.

And HW encoding includes even GPU without explicitly referring to it.

It's a more accurate term in my opinion.

[legend]

Using 1st time I got this message

http://s24.postimg.org/fyuzcgvn9/staxrip.png

My log File

http://pastebin.com/g4yvcZWN


How can I solve this problem.

[stax76]

@legend

Looks like AviSynth+ x64 isn't working, to verify this you can try to open the avs file generated by StaxRip with VirtualDub x64.

I see this error very often, any idea what could have damaged the setup?

[Lupissimo]

After downloading Staxrip 64 ( or 32bit ) I just copied the downloaded files to C:\ . After creating a link to desktop I started the program and assinged the default directory. When trying to drop a file to encode into Staxrip, this is no longer possible.
Could someone please post the correct "installation" procedure ( any security settings, administrator rights etc.).

[stax76]

After downloading Staxrip 64 ( or 32bit ) I just copied the downloaded files to C:\ . After creating a link to desktop I started the program and assinged the default directory. When trying to drop a file to encode into Staxrip, this is no longer possible.
Could someone please post the correct "installation" procedure ( any security settings, administrator rights etc.).

better use a folder with full write access, there are like +100 exe and dll files included, who knows if all of them work correctly in a folder without full write access.

[stax76]

new test build (1.3.3.1 - 2016-03-14) with lot's of changes...

Download

https://drive.google.com/folderview?id=0B-gPKiJYuKuIRGUxckdyQU5DUkE&usp=sharing

http://1drv.ms/1OqPDOe

New Features


support for 3 or more audio tracks added to the muxing dialog
code preview added to filters menu and script preview renamed to code preview in script editor
added a command line switch -show-dialogs:bool and project option 'Show all dialogs when invoked from CLI', by default dialogs are not shown when StaxRip receives CLI arguments
yadifmod2 plugin for AviSynth added
TComb AviSynth plugin added
auto crop plugin replaced with new internal routine supporting both AviSynth and VapourSynth
better subtitle support for m2ts container
decoding options added for AMD encoder
larger x265 custom command line TextBox
x265 new switch added --rc-grain
the encoding options dialogs for x265, AMD, Intel and NVIDIA have now an option to display the full command line


Fixed Bugs


fixed window freeze in eac3to dialog happening when eac3to fails on the input.
fixed showing filter selection dialog even if the source is vpy or avs
fixed StaxRip trying to auto correct the script even if the source is avs
fixed StaxRip recalculating the video bitrate even when the fixed bitrate option is used
avi muxer supports two audio tracks now
in some cases the two audio output file paths were identical
moving subtitles up and down wasn't working correctly
the new mp4box update should fix a bug many people reported
fixed editing dates in apps dialog not working with Persian calendar
fixed crash using ' character in file paths using VapourSynth
fixed inaccurate right and bottom magnifiers in crop dialog
removed one x265 switch that was accidentally added twice :-)


Tweaks


better error handling when the source is vpy or avs
when loading an audio file without language info the language of the audio profile/stream stays instead of being changed to undetermined
improved changelog
cutting with VapourSynth is now possible without AviSynth being installed (the audio cutting code was using AviSynth)
The info in the preview looks better and is readable regardless of the current background
source filter preferences in the settings dialog under Source Filter to configure which source filter should be used for a given file in case the source filter in the project is called Automatic is now also available for VapourSynth, with this VapourSynth support in StaxRip should be on par with AviSynth support making both scripting engines first class citizens
x265 tune grain defaults updated
improved bitrate calculation
The media info dialog shows the file size now also in mega byte instead of giga byte only
removed ffmpeg writing long build info to the log file


Updated Tools


mp4box 0.6.0
QSVEncC 2.37
x264 2665
AVSMeter 2.1.6
fmtconv 18
ffmpeg 2016-03-10
x265 1.9+88

[JohnLai]

If I am not mistaken, in order to use ffmpeg DXVA, one must adds -threads 1 in front of -input;

ffmpeg -hwaccel dxva2 -threads 1 -i INPUT

No idea when this -threads 1 was implemented......every compiled ffmpeg after december 2015 seems to require it.
Stax~~~~, did you add -threads 1 accordingly?

[stax76]

the dialog has a feature to show and copy the command line, as example a generated command line looks like this:

D:\Projekte\GitHub\staxrip\bin\Apps\ffmpeg\ffmpeg.exe -threads 1 -hwaccel dxva2 -i D:\Temp\Video\Clips\twk.mkv -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | D:\Projekte\GitHub\staxrip\bin\Apps\QSVEncC\QSVEncC64.exe --cqp 24:26:27 --input-file D:\Temp\Video\Clips\twk.mkv --output-file D:\Temp\Video\Clips\twk_temp\twk_new_out.h264

what the latest build also does it encloses quotes in paths only if necessary

it encodes a while but then shows an error:

av_interleaved_write_frame(): Broken pipe
Error writing trailer of pipe:: Broken pipe

[NikosD]

Haven't tested yet your new build, but you could try latest QSVEncC v2.39 which has fixed many stability issues.

[NikosD]

added a command line switch -show-dialogs:bool and project option 'Show all dialogs when invoked from CLI', by default dialogs are not shown when StaxRip receives CLI arguments


Tried it with QSVEncC but I didn't see any new dialog showing up.

Can you give an example of a dialog hidden so far ?

Also, why not put it by default to show all dialogues ?


better subtitle support for m2ts container


Fixed for my m2ts files - Thanks!


decoding options added for AMD encoder


...and Intel encoder too


the encoding options dialogs for x265, AMD, Intel and NVIDIA have now an option to display the full command line


You have also added a "Search" field in Intel encoders GUI for easily find some switches in the GUI.



it encodes a while but then shows an error:

av_interleaved_write_frame(): Broken pipe
Error writing trailer of pipe:: Broken pipe



That error is visible even with latest QSVEncC v2.39, I've sent an email to rigaya


NEW BUG:


When QSVEncC decoder is selected in Intel encoders GUI, the "Execute Command Line" no longer works due to incomplete command sent (missing QSVEncC path)


QUESTIONS:


1) What is the "iv" subtitle language abbreviation automatically added in Options -> Subtitles -> Auto load subtitles ?

2) Have you put by default the --avqsv switch to QSVEncC app when using NVEncC and VCEEncC decoders ?

Because it doesn't show up when "Show command line" is pressed, but from the transcoding process it is clear that --avqsv is used (very low CPU usage) even in my system which has no Nvidia/ AMD card.


SUGGESTIONS:


1) VCEEncC as a decoder can't be used by Intel encoder or even AMD encoder because VCEEncC has no HW decoder implemented.
AMD has no API for decoding yet.

You could remove them from decoder option of Intel H.264/H.265 and AMD H.264 encoders GUI without harm.


2) In Tools -> Apps -> QSVEncC description you could add H.265 and MPEG2 encoding


3) You could add Intel MPEG2 encoding in first page description of this thread, too.


4) The "search" field in Intel encoders GUI is useful and I suggest to highlight the options selected in red color.

Grey is not easily distinguished from black.

Also, -profile and -level switches seem to not be highlighted when selected.

The -scenechange switch is not highlighted and missing completely from the GUI.


5) The "MPEG2" encoding GUI for Intel encoder is missing from the templates.

Also, the encoding mode "ICQ" is not valid for MPEG2 encoding.

I have asked rigaya to send me the list of valid encoding modes for Intel MPEG2 encoding and put them in help.txt, too.

BTW, there is a very useful command in latest QSVEncC versions called --fallback-rc

When an encoding option is selected that is not supported by the platform (like ICQ for MPEG2 or LA-ICQ for H.264 on older CPUs like Sandybridge/ Ivybridge) then the app instead of stopping, it automatically falls back to a compatible encoding mode.

I tried it for ICQ in MPEG2 GUI and it works. It falls back to CQP.

Maybe you could add it somewhere as an option probably enabled by default.


6) In Tools -> Launch, I think it would be useful to automatically add as an argument the source file already loaded for mkvinfo GUI

[NikosD]

Regarding the error using ffmpeg dxva2, rigaya replied that it's not his app message.

So, it should be ffmpeg's.

Now, about MPEG2 encoding modes, we can run --check-features in order to see which encoding are available.

[TalasNetrag]

When opening the muxing dialog for the audiotracks, the window has the wrong size when the audio tab was already selected.

http://www.mediafire.com/download/7f5sw0b76pi2sgw/StaxrRip_resize_issue.mp4

[stax76]

When opening the muxing dialog for the audiotracks, the window has the wrong size when the audio tab was already selected.

http://www.mediafire.com/download/7f5sw0b76pi2sgw/StaxrRip_resize_issue.mp4

I don't see it due to different DPI scaling, please try the build I've just uploaded.

added a command line switch -show-dialogs:bool and project option 'Show all dialogs when invoked from CLI', by default dialogs are not shown when StaxRip receives CLI arguments

Tried it with QSVEncC but I didn't see any new dialog showing up.

At the moment it affects the demuxing and filter selection dialog I believe, those should be hidden by default when StaxRip is started with CLI parameters.

Also, why not put it by default to show all dialogues ?

I'm not sure what is more important.

You have also added a "Search" field in Intel encoders GUI for easily find some switches in the GUI.

I think it was hidden in case < 20 switches (it's the same dialog for all more recent encoders)

When QSVEncC decoder is selected in Intel encoders GUI, the "Execute Command Line" no longer works due to incomplete command sent (missing QSVEncC path)

fixed

1) What is the "iv" subtitle language abbreviation automatically added in Options -> Subtitles -> Auto load subtitles ?

it's in the help ;) (right click label to show tooltip as message (task) dialog or press F1)

I use the languages defined in the .NET framework added with some mapping, iv is .NET's invariant culture for which I mapped 'und' as three letter code.

Have you put by default the --avqsv switch to QSVEncC app when using NVEncC and VCEEncC decoders ?

Because it doesn't show up when "Show command line" is pressed, but from the transcoding process it is clear that --avqsv is used (very low CPU usage) even in my system which has no Nvidia/ AMD card.

When it's not shown than it's not used for encoding because it's the same routine, maybe it's not needed and HW decoding is used automatically, in this case I will remove it.

1) VCEEncC as a decoder can't be used by Intel encoder or even AMD encoder because VCEEncC has no HW decoder implemented.
AMD has no API for decoding yet.

You could remove them from decoder option of Intel H.264/H.265 and AMD H.264 encoders GUI without harm.

removed

2) In Tools -> Apps -> QSVEncC description you could add H.265 and MPEG2 encoding

added

3) You could add Intel MPEG2 encoding in first page description of this thread, too.

I added it to the local md (markdown) file so with the next source code commit it will show on github, as for the first page it's based on the markdown file but only updated from time to time using a markdown to bbcode converter.

4) The "search" field in Intel encoders GUI is useful and I suggest to highlight the options selected in red color.

It uses the color of your windows os customization, here it's green atm, this color is used in StaxRip often

Also, -profile and -level switches seem to not be highlighted when selected.

I've fixed it but controls currently hidden are still in the list, it would be some work to change, maybe not worth it, I've added a message for this case: 'Option is hidden by other option.'

The -scenechange switch is not highlighted and missing completely from the GUI.

it's only visible for avs/vs decoder

5) The "MPEG2" encoding GUI for Intel encoder is missing from the templates.

It's maybe not important enough to add a profile but users can make their own profile.

Also, the encoding mode "ICQ" is not valid for MPEG2 encoding.

fixed

BTW, there is a very useful command in latest QSVEncC versions called --fallback-rc

When an encoding option is selected that is not supported by the platform (like ICQ for MPEG2 or LA-ICQ for H.264 on older CPUs like Sandybridge/ Ivybridge) then the app instead of stopping, it automatically falls back to a compatible encoding mode.

I tried it for ICQ in MPEG2 GUI and it works. It falls back to CQP.

Maybe you could add it somewhere as an option probably enabled by default.

but then users might not notice incompatible settings, it would also clutter the command line, the GUI already hides incompatible options.

6) In Tools -> Launch, I think it would be useful to automatically add as an argument the source file already loaded for mkvinfo GUI

added

Now, about MPEG2 encoding modes, we can run --check-features in order to see which encoding are available.

I've updated it now for all three codecs.

New build is online.

[JohnLai]

Regarding the error using ffmpeg dxva2, rigaya replied that it's not his app message.

So, it should be ffmpeg's.

Now, about MPEG2 encoding modes, we can run --check-features in order to see which encoding are available.

T_T.....nobody read my post on ffmpeg dxva requiring "-threads 1" after december 2015?

[NikosD]

I think you didn't read Stax76's reply :)

He has already said that the app uses the -thread 1 switch as you can see above in his reply, which I can confirm too.

[TalasNetrag]

I don't see it due to different DPI scaling, please try the build I've just uploaded.
The new build works fine.

[NikosD]

I downloaded your latest beta from the same link.

Here they are my comments:


I've fixed it but controls currently hidden are still in the list, it would be some work to change, maybe not worth it, I've added a message for this case: 'Option is hidden by other option.'


The issue here is that -profile and -level are always available for all three codecs and for all four decoders (avisynth, qsv, nvencc and ffmpeg dxva2), because decoders have nothing to do with profiles and levels.

Somehow the app thinks that only for avisynth those switches should be available, which is not true.



but then users might not notice incompatible settings, it would also clutter the command line, the GUI already hides incompatible options.



OK, it seems that you did the job and GUI truly hides the incompatible options, but it doesn't work for all cases.

For example, if you own a SandyBridge or IvyBridge the H.264 GUI options are the same like Haswell, but in reality they are less than Haswell or newer CPU.

How are you going to hide dynamically the GUI options based on CPU/ GPU architecture ?
It's not possible, you have to use MediaSDK programming.

Also, don't be afraid of users not noticing incompatible settings because the CLI message of QSVEncC is in yellow and warns clearly the user that the encoding mode he selected is not compatible and that it has to fall back to another one, mentioning that too.

You have to test it for yourself in order to understand the message better, but I can assure you it is clear.



6) In Tools -> Launch, I think it would be useful to automatically add as an argument the source file already loaded for mkvinfo GUI

added


For me it tries to open the app but it crashes immediately.


Quote:
av_interleaved_write_frame(): Broken pipe
Error writing trailer of pipe:: Broken pipe


Do you have any idea how that could be fixed ?


SUGGESTION:

The decoders should have the same names for all HW GUIs.

NVEncC decoder -> NVEncC CUVID

QSVEncC decoder -> QSVEncC QSV

[NikosD]

One last think I forgot:

QSVEncC has a newer version than the one included, v2.39

[stax76]

The issue here is that -profile and -level are always available for all three codecs and for all four decoders (avisynth, qsv, nvencc and ffmpeg dxva2), because decoders have nothing to do with profiles and levels.

Somehow the app thinks that only for avisynth those switches should be available, which is not true.

There was a bug, I rewrote half of the list/search code, should be perfect or close now!


OK, it seems that you did the job and GUI truly hides the incompatible options, but it doesn't work for all cases.

For example, if you own a SandyBridge or IvyBridge the H.264 GUI options are the same like Haswell, but in reality they are less than Haswell or newer CPU.

How are you going to hide dynamically the GUI options based on CPU/ GPU architecture ?
It's not possible, you have to use MediaSDK programming.

Also, don't be afraid of users not noticing incompatible settings because the CLI message of QSVEncC is in yellow and warns clearly the user that the encoding mode he selected is not compatible and that it has to fall back to another one, mentioning that too.

You have to test it for yourself in order to understand the message better, but I can assure you it is clear.


you are right, I've added it and enabled it by default

For me it tries to open the app but it crashes immediately.

what crashes and how?


av_interleaved_write_frame(): Broken pipe
Error writing trailer of pipe:: Broken pipe
Do you have any idea how that could be fixed ?


it comes from ffmpeg, the code is on github so it's easy to search in the code:

https://github.com/FFmpeg/FFmpeg/search?utf8=%E2%9C%93&q=av_interleaved_write_frame

you could try to contact the ffmpeg people, maybe wait until I add hw decoding support for x264 and x265 encoding

The decoders should have the same names for all HW GUIs.

changed to:

NVEncC (NVIDIA CUVID)
QSVEncC (Intel Quick Sync)
ffmpeg (DXVA2)

QSVEncC has a newer version than the one included, v2.39

done

new build is online, I think for today it's enough. :)

[NikosD]

Excellent release!


what crashes and how?


When I select a .mkv file as source and then go to Tools -> Launch -> mkvinfo GUI then StaxRip tries to open mkvinfo GUI but closes instantly, it crashes.

The same procedure with no source selected or other container selected (like .m2ts or .mp4) it opens mkvinfo GUI without problem.

So, the bug has something to do with the .mkv file as argument in mkvinfo GUI app.



it comes from ffmpeg, the code is on github so it's easy to search in the code:

https://github.com/FFmpeg/FFmpeg/search?utf8=%E2%9C%93&q=av_interleaved_write_frame

you could try to contact the ffmpeg people



I wish I could debug that code, but I can't.

My question is this:

Is it a problem for Intel encoder only or Nvidia/ AMD has the same problem too, using ffmpeg dxva2 as a decoder ?



maybe wait until I add hw decoding support for x264 and x265 encoding



That could be interesting, but putting a very fast HW decoder to pipe the output to a very slow SW encoder like x264 or even worse x265, I'm not sure it will be that effective.

Probably only "ultrafast" setting of those SW encoders could benefit from a HW decoder.

Unless you mean H.264 & H.265 HW encoders.



changed to:

NVEncC (NVIDIA CUVID)
QSVEncC (Intel Quick Sync)
ffmpeg (DXVA2)



According to Intel, Quick Sync is one word QuickSync :p


new build is online, I think for today it's enough. :)

It's more than enough!
Thanks again!

[stax76]

When I select a .mkv file as source and then go to Tools -> Launch -> mkvinfo GUI then StaxRip tries to open mkvinfo GUI but closes instantly, it crashes.

fixed

Is it a problem for Intel encoder only or Nvidia/ AMD has the same problem too, using ffmpeg dxva2 as a decoder ?

command line was wrong :o, fixed

According to Intel, Quick Sync is one word QuickSync

most google hits are two words

[NikosD]

fixed



command line was wrong :o, fixed



Have you uploaded the new test build ? :)

[stax76]

it's online now

[dejong12]

it's online now
You're on a roll today Stax, it's really nice to see you active.

[stax76]

It's many little only improvements but it's the little things that make a difference so it's important when Nikos or other people point it out.

I've sent a message to rigaya suggesting to support y4m output for all encoders.

[NikosD]

Hello.

I've done a few tests this morning regarding Intel HW H.264 encoding and the results are not so good.

So, on my system Win 10 x64 - Core i7-4790 - iGPU HD 4600@1.5GHz - Drivers v.4380, I find out these:


1) The main disappointment is the instability of Intel's HW encoder, probably due to drivers on Haswell and Windows 10

For almost all clips I tried, it starts very good with a performance of more than 200+ fps for 1080p to 1080p H.264 transcoding, but it has sudden drops of GPU load and performance to even less than half of it, around 80fps (!) and the average speed is about 120fps - very slow.

I remember the times that I had a steady 300+ fps for the same conversion.

I have discussed the same issue here and with rigaya, he told me that there were some MediaSDK releases that dropped performance a lot introducing new API versions, but it seems more of a problem of the driver, the GPU architecture and the OS version.

So, I wonder how Skylake performs on typical 1080p to 1080p H.264 conversion on yours platform and I mean the Skylake owners.


2) The ffmpeg (DXVA2) decoder is using a copy-back mode from GPU to system memory and the performance is worst than DSS2/LAV QSV and DSS2/LAV DXVA-Copy-back

So the performance of the decoders goes like this:

QSVEncC (Quick Sync) > LAV DXVA copy-back > LAV QSV > ffmpeg (DXVA2)

So, I would suggest to rename ffmpeg (DXVA2) to ffmpeg (DXVA2-CB) in case anyone wonders why is it so slow.

One more detail is that using ffmpeg (DXVA2) decoder, QSVEncC doesn't show the progress in percentage as with all the other decoders. Strange.

3) Frank, after the release of FFMpeg 2.8 last year supporting officially QSV transcoding (HW decoding + HW encoding), Intel has started supporting that implementation a lot.

We have spent a lot of time (YOU a LOT more) to build, test, debug GUIs for HW encoding based on rigaya's CLI HW encoders, but if I were you, I would investigate the ffmpeg QSV and NVENC implementations for HW transcoding on Intel and Nvidia HW, not only decoding.

[stax76]

@Nikos

It runs around ~200fps, my driver is probably outdated though.

I'll take a look at ffmpeg QSV/NVENC, there is an ffmpeg encoder which I can expand, it's a while back it was added so needs some modernization but it's based on the same new framework all recent encoders are based on.


------------------------------------------------------------
Encoding using QSVEncC
------------------------------------------------------------

D:\Projekte\GitHub\staxrip\bin\Apps\QSVEncC\QSVEncC64.exe --fallback-rc
--icq 25 -i D:\Temp\test.mkv -o D:\Temp\test_temp\test_new_out.h264

QSVEncC (x64) 2.39 (r951) by rigaya, Mar 13 2016 10:24:15 (VC 1900/Win/avx2)
OS Windows 10 (x64)
CPU Info Intel Core i5-6600K @ 3.50GHz [TB: 3.80GHz] (4C/4T) <Skylake>
GPU Info Intel HD Graphics 530 (24EU) 1150MHz (20.19.15.4331)
Media SDK QuickSyncVideo (hardware encoder) PG, 2nd GPU, API v1.17
Async Depth 6 frames
Buffer Memory d3d11, 1 input buffer, 18 work buffer
Input Info avcodec video: H.264/AVC, 1920x1080, 25/1 fps
Output H.264/AVC High @ Level 4
1920x1080p 1:1 25.000fps (25/1fps)
Target usage 4 - balanced
Encode Mode ICQ (Intelligent Const. Quality)
ICQ Quality 25
QP Limit min: none, max: none
Trellis Auto
Ref frames 3 frames
Bframes 3 frames, B-pyramid: on
Max GOP Length 250 frames
Scene Change off
Ext. Features PerMBRC
encoded 146824 frames, 203.56 fps, 1789.47 kbps, 1252.83 MB
encode time 0:12:01, CPULoad: 11.48
frame type IDR 588
frame type I 588, total size 36.25 MB
frame type P 37000, total size 733.73 MB
frame type B 109236, total size 482.85 MB

[NikosD]

My performance starts even better than that, but can't keep up and stalls for few moments completely unpredictably with all decoders I have tried -SW avs, LAV SW/HW, ffmpeg (DXVA2) or QSVEncC (Quick Sync)

If you have time, try various clips and see if that kind of performance ~200 fps is consistent across various clips for all transcoding time.

The older ffmpeg based encoders are useless.
They are based on SandyBridge and have very few options.

Last ffmpeg 3.0 is the minimum for anything based on ffmpeg.

What you could easily add right now, I think, is the ffmpeg (Quick Sync) decoder which has added HEVC decoding besides the other HW accelerated codecs of ffmpeg (DXVA2) and probably better performance than ffmpeg (DXVA2)

[stax76]

All three sources I tried give around 200 fps.

[JohnLai]

Note:
FFMPEG DXVA2 has problem with Intel IGPU (tested using haswell i3-4330 hd4600). If one has ONLY Intel IGPU alone, he must use ffmpeg QSV decoder instead of DXVA2, other conditions being the igpu must be active and primary display.

ffmpeg DXVA2 works well with dedicated NVIDIA and AMD gpus.

[NikosD]

As I wrote before, my instability problems happen with ALL decoders, even SW.

It would be useful if Frank could add in the GUI the ffmpeg Quick Sync decoder, though :)

BTW, rigaya replied that when the input comes from piping like ffmpeg dxva2, then QSVEncC can't display the percentage of progress.

P.S1

Maybe Intel want us all to buy Skylake, who knows ;)

P.S2

Haswell 4770K with Win 8.1 x64 and 4332 drivers - no dGPU - has no such issues.

The problem is probably v4380 drivers and/or Win 10

[stax76]

Has anybody a qsv and nvenc enabled ffmpeg build?

[NikosD]

The ffmpeg build included with StaxRip has qsv enabled.

You can check it by running -hwaccels and -codecs.

There a few *_qsv codecs available.

[NikosD]

Has anybody a qsv and nvenc enabled ffmpeg build?
Here is an interesting thread that looks like it was opened yesterday just for you !

http://forum.doom9.org/showthread.php?t=173304

[stax76]

it seems but I cannot get it working


-----------------------------------------------------------
_________ __ __________.__
/ _____// |______ ___ __\______ \__|_____
\_____ \\ __\__ \ \ \/ /| _/ \____ \
/ \| | / __ \_> < | | \ | |_> >
/_______ /|__| (____ /__/\_ \|____|_ /__| __/
\/ \/ \/ \/ |__|

------------------------------------------------------------
Environment
------------------------------------------------------------

StaxRip x64 : 1.3.3.1
OS : Windows 10 Pro
Language : German (Germany)
CPU : Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
GPU : NVIDIA GeForce GTX 960, Intel(R) HD Graphics 530

------------------------------------------------------------
Encoding H.264 Intel Quick Sync using ffmpeg
------------------------------------------------------------

D:\Projekte\GitHub\staxrip\bin\Apps\ffmpeg\ffmpeg.exe -threads 1
-hwaccel dxva2 -i D:\Video\Samples\Misc\eli.mp4 -c:v h264_qsv
-q:v 25 -y -hide_banner D:\Video\Samples\Misc\eli_temp\eli_out.mkv

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'D:\Video\Samples\Misc\eli.mp4':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: isommp42
creation_time : 2015-05-20 08:55:10
Duration: 00:00:43.42, start: 0.000000, bitrate: 2367 kb/s
Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p,
1280x720 [SAR 1:1 DAR 16:9], 2173 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 59.94 tbc (default)
Metadata:
handler_name : VideoHandler
Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 192 kb/s (default)
Metadata:
creation_time : 2015-05-20 08:55:10
handler_name : IsoMedia File Produced by Google, 5-11-2011
[h264_qsv @ 0000018b333038c0] More than one of: { constant qscale, lookahead, VCM } requested,
only one of them can be used at a time.
Output #0, matroska, to 'D:\Video\Samples\Misc\eli_temp\eli_out.mkv':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: isommp42
Stream #0:0(und): Video: h264, none, q=2-31, 128 kb/s, SAR 1:1 DAR 0:0, 29.97 fps (default)
Metadata:
handler_name : VideoHandler
encoder : Lavc57.28.100 h264_qsv
Stream #0:1(eng): Audio: vorbis, 0 channels, 128 kb/s (default)
Metadata:
creation_time : 2015-05-20 08:55:10
handler_name : IsoMedia File Produced by Google, 5-11-2011
encoder : Lavc57.28.100 libvorbis
Stream mapping:
Stream #0:0 -> #0:0 (h264 (native) -> h264 (h264_qsv))
Stream #0:1 -> #0:1 (aac (native) -> vorbis (libvorbis))
Error while opening encoder for output stream #0:0 - maybe incorrect parameters
such as bit_rate, rate, width or height

------------------------------------------------------------
Error Encoding H.264 Intel Quick Sync using ffmpeg
------------------------------------------------------------

Encoding H.264 Intel Quick Sync using ffmpeg 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.

[NikosD]

I'm not 100% certain, but I think you don't need -hwaccels dxva2, try -hwaccels qsv or nothing and you have to use -vcodec h264_qsv and try without specifying encoding mode at all.

[stax76]

I think it's a config issue

https://www.ffmpeg.org/ffmpeg-all.html#QSV-encoders

edit:

this encodes now:

D:\Projekte\GitHub\staxrip\bin\Apps\ffmpeg\ffmpeg.exe -threads 1 -hwaccel dxva2 -i D:\Video\Samples\Misc\eli.mp4 -c:v h264_qsv -b:v 1000k -an -y -hide_banner D:\Video\Samples\Misc\eli_temp\eli_out.mkv

edit2:

about 20 fps faster then QSVEncC

[NikosD]

I've just read in ffmpeg Zeranoe forum a comment from him


Re: Intel QSV Codecs
PostTue Mar 01, 2016 5:16 am

Intel QSV is now included in the daily builds, and Windows XP support has been dropped.


So, it seems that from March 1st the daily builds include QSV.

Probably ffmpeg NVENC is not so mature yet to include it.

[stax76]

I almost gave up until I found out some has to type: ffmpeg -h full

then 8000 lines print including this:


h264_qsv encoder AVOptions:
-async_depth <int> E..V.... Maximum processing parallelism (from 0 to INT_MAX) (default 4)
-avbr_accuracy <int> E..V.... Accuracy of the AVBR ratecontrol (from 0 to INT_MAX) (default 0)
-avbr_convergence <int> E..V.... Convergence of the AVBR ratecontrol (from 0 to INT_MAX) (default 0)
-preset <int> E..V.... (from 1 to 7) (default medium)
veryfast E..V....
faster E..V....
fast E..V....
medium E..V....
slow E..V....
slower E..V....
veryslow E..V....
-vcm <int> E..V.... Use the video conferencing mode ratecontrol (from 0 to 1) (default 0)
-rdo <int> E..V.... Enable rate distortion optimization (from -1 to 1) (default -1)
-max_frame_size <int> E..V.... Maximum encoded frame size in bytes (from -1 to 65535) (default -1)
-max_slice_size <int> E..V.... Maximum encoded slice size in bytes (from -1 to 65535) (default -1)
-bitrate_limit <int> E..V.... Toggle bitrate limitations (from -1 to 1) (default -1)
-mbbrc <int> E..V.... MB level bitrate control (from -1 to 1) (default -1)
-extbrc <int> E..V.... Extended bitrate control (from -1 to 1) (default -1)
-adaptive_i <int> E..V.... Adaptive I-frame placement (from -1 to 1) (default -1)
-adaptive_b <int> E..V.... Adaptive B-frame placement (from -1 to 1) (default -1)
-b_strategy <int> E..V.... Strategy to choose between I/P/B-frames (from -1 to 1) (default -1)
-cavlc <int> E..V.... Enable CAVLC (from 0 to 1) (default 0)
-idr_interval <int> E..V.... Distance (in I-frames) between IDR frames (from 0 to INT_MAX) (default 0)
-pic_timing_sei <int> E..V.... Insert picture timing SEI with pic_struct_syntax element (from 0 to 1) (default 1)
-single_sei_nal_unit <int> E..V.... Put all the SEI messages into one NALU (from -1 to 1) (default -1)
-max_dec_frame_buffering <int> E..V.... Maximum number of frames buffered in the DPB (from 0 to 65535) (default 0)
-look_ahead <int> E..V.... Use VBR algorithm with look ahead (from 0 to 1) (default 1)
-look_ahead_depth <int> E..V.... Depth of look ahead in number frames (from 0 to 100) (default 0)
-look_ahead_downsampling <int> E..V.... (from 0 to 2) (default unknown)
unknown E..V....
off E..V....
2x E..V....
-int_ref_type <int> E..V.... Intra refresh type (from -1 to 65535) (default -1)
none E..V....
vertical E..V....
-int_ref_cycle_size <int> E..V.... Number of frames in the intra refresh cycle (from -1 to 65535) (default -1)
-int_ref_qp_delta <int> E..V.... QP difference for the refresh MBs (from -32768 to 32767) (default -32768)
-recovery_point_sei <int> E..V.... Insert recovery point SEI messages (from -1 to 1) (default -1)
-trellis <flags> E..V.... Trellis quantization (default 0)
off E..V....
I E..V....
P E..V....
B E..V....
-profile <int> E..V.... (from 0 to INT_MAX) (default unknown)
unknown E..V....
baseline E..V....
main E..V....
high E..V....
-a53cc <int> E..V.... Use A53 Closed Captions (if available) (from 0 to 1) (default 0)

hevc_qsv encoder AVOptions:
-async_depth <int> E..V.... Maximum processing parallelism (from 0 to INT_MAX) (default 4)
-avbr_accuracy <int> E..V.... Accuracy of the AVBR ratecontrol (from 0 to INT_MAX) (default 0)
-avbr_convergence <int> E..V.... Convergence of the AVBR ratecontrol (from 0 to INT_MAX) (default 0)
-preset <int> E..V.... (from 1 to 7) (default medium)
veryfast E..V....
faster E..V....
fast E..V....
medium E..V....
slow E..V....
slower E..V....
veryslow E..V....
-vcm <int> E..V.... Use the video conferencing mode ratecontrol (from 0 to 1) (default 0)
-rdo <int> E..V.... Enable rate distortion optimization (from -1 to 1) (default -1)
-max_frame_size <int> E..V.... Maximum encoded frame size in bytes (from -1 to 65535) (default -1)
-max_slice_size <int> E..V.... Maximum encoded slice size in bytes (from -1 to 65535) (default -1)
-bitrate_limit <int> E..V.... Toggle bitrate limitations (from -1 to 1) (default -1)
-mbbrc <int> E..V.... MB level bitrate control (from -1 to 1) (default -1)
-extbrc <int> E..V.... Extended bitrate control (from -1 to 1) (default -1)
-adaptive_i <int> E..V.... Adaptive I-frame placement (from -1 to 1) (default -1)
-adaptive_b <int> E..V.... Adaptive B-frame placement (from -1 to 1) (default -1)
-b_strategy <int> E..V.... Strategy to choose between I/P/B-frames (from -1 to 1) (default -1)
-cavlc <int> E..V.... Enable CAVLC (from 0 to 1) (default 0)
-load_plugin <int> E..V.... A user plugin to load in an internal session (from 0 to 2) (default hevc_sw)
none E..V....
hevc_sw E..V....
hevc_hw E..V....
-load_plugins <string> E..V.... A :-separate list of hexadecimal plugin UIDs to load in an internal session (default "")
-profile <int> E..V.... (from 0 to INT_MAX) (default unknown)
unknown E..V....
main E..V....
main10 E..V....
mainsp E..V....

[NikosD]

From what I have tested and what I have read so far:

If you don't use the -hwaccel switch, then SW decoding is used.

In order to have HW accelerated decoding you have to use -hwaccel which takes two arguments: dxva2 or qsv

You can find the hwaccels available by running ffmpeg -hwaccels. You have to include the last "s" (plural)

By using -hwaccel dxva2, you can get HW decoding for H.264, MPEG2, VC-1/WMV3 but no H.265.

By using -hwaccel qsv, you can get HW decoding for H.265, H.264, MPEG2, VC-1/WMV3

The problem is that in the help file, the term "h264_qsv" and every "*_qsv" item, is used to describe decoding and encoding.

qsv decoding is used only in -hwaccel switch, writing just -hwaccel qsv and the app knows what codec to HW accelerate, just like -hwaccel dxva2.

So, do you see any performance difference by using -hwaccel dxva2 vs - hwaccel qsv ?

[stax76]

-hwaccel qsv -threads 1 : 108 fps
-hwaccel qsv : 240 fps

-hwaccel dxva2 -threads 1 : 220 fps
-hwaccel dxva2 : warning

problem is ffmpeg freezes all the time by printing:

Press [q] to stop, [?] for help

and doing nothing otherwise, after installing the new beta driver and rebooting it started to work again but not for long

[NikosD]

-hwaccel qsv -threads 1 : 108 fps
-hwaccel qsv : 240 fps

-hwaccel dxva2 -threads 1 : 220 fps
-hwaccel dxva2 : warning


Thanks.


problem is ffmpeg freezes all the time by printing:

Press [q] to stop, [?] for help

and doing nothing otherwise



I have exactly the same problem and thought it was my system again (Haswell - Win 10 - v4380)


Edit:
Try SW decoding without -hwaccel switch

[stax76]

SW decoding and QSVEncC works, looks like somebody has to visit ffmpeg bug tracker :)

[NikosD]

You mean ffmpeg SW decoding + ffmpeg gsv encoding works ?

[stax76]

ffmpeg qsv decoding does not work

[NikosD]

If you omit -hwaccel switch, then ffmpeg SW decoding is used.

[stax76]

ffmpeg SW decoding works

[nevcairiel]

The -hwaccel qsv switch is special, its not meant to use qsv decoding, you need to manually tell it to do that.
Using something like "ffmpeg -hwaccel qsv -c:v h264_qsv -i file.mp4 -c:v h264_qsv out.mkv" would use qsv decoding, qsv encoding, with no copying back to system memory (thats what the -hwaccel qsv does). Note that this mode is somewhat unstable because qsv sucks.

[NikosD]

OK. .But if the implementation of -hwaccel qsv doesn't use copy - back like ffmpeg dxva2, then CPU usage should be lower.

My tests show a CPU usage close to a copy - back mechanism and not to native mode.

Some copy - back to memory should be happening, but I'll test it again - when it's not freezing - to be sure.

QSV transcoding (decoding+encoding) doesn't suck and the proof is the native QSV transcoding of QSVEncC with lowest CPU usage and fast performance.

Latest MediaSDK and drivers seem to need some more work on Win 10 and Haswell.

[JohnLai]

-hwaccel qsv = this one was mentioned by ffmpeg contributor to be 'zero copy' mode. No idea why this mode has higher cpu usage than command below;

The command below is 'copy-back' mode;
ffmpeg -vcodec h264_qsv -i "INPUT.mkv" -vcodec h264_qsv -b:v 1000k "OUTPUT.mkv"

Then again, one could COMBINE;
ffmpeg -hwaccel qsv -vcodec h264_qsv -i "INPUT.mkv" -vcodec h264_qsv -b:v 1000k "OUTPUT.mkv"
to get even lower cpu usage.


Note: Remember, Intel IGPU has to be the primary. NO dedicated GPU.

EDIT: I just realize nevcairiel had mentioned it....darn, I just make a fool outta myself.

Fine, next lesson;

Note: To get ffmpeg help, use "ffmpeg -h encoders=nvenc" . To get list of encoder, use "ffmpeg -encoders"


FFMPEG WITH NVRESIZE (g3862200 64bit only, one that compiled with a script from RDP few months ago);
https://www.solidfiles.com/v/zyxWGRgGx53Yn
(Install ublock/adblock and noscript, don't click the wrong 'download')

Command;
ffmpeg -threads 1 -hwaccel dxva2 -i "INPUT.mkv" -pix_fmt nv12 -filter_complex nvresize=1:s=1280x720:readback=0 -vcodec nvenc_hevc -tier high -level 4.1 -preset slow -async 1 -maxrate 10M -bufsize:v 10M -bf 0 -refs 9 -g 240 -i_qfactor 0.71 -b_qfactor 1.25 -qmin 1 -qmax 25 -enableaq true -2pass true -an -sn "OUTPUT.mkv"

Explanation (some copy-pasted from nvidia documentation);
Option available for "s" : hd1080\|hd720\|hd480\|wvga\|cif or one could use 1280x720 (resolution) directly.
Option available for "g" : GOP basic formula "A" seconds x "B" fps = GOP length, in example above, i put 8seconds x 30fps=240, maybe?

Nvresize filter has a -readback parameter, if it's set as 0, resized
result won't be copied back to CPU, mostly in case it's connected to an
NVENC encoder。 If it's set as 1, resized result will still be copied
back to AVFrame so that it could be compatible with other components.

Advanced usage for multiple video resizing at once;
ffmpeg -y -i INPUT -filter_complex
nvresize=5:s=hd1080|hd720|hd480|wvga|cif:readback=0[out0][out1][out2][out3][out4]
-map [out0] -an -vcodec nvenc -b:v 6M -bufsize 6M -maxrate 6.8M -bf 2 out0nv.mp4
-map [out1] -an -vcodec nvenc -b:v 3M -bufsize 3M -maxrate 3.4M -bf 2 out1nv.mp4
-map [out2] -an -vcodec nvenc -b:v 2M -bufsize 2M -maxrate 2.1M -bf 2 out2nv.mp4
-map [out3] -an -vcodec nvenc -b:v 1M -bufsize 1M -maxrate 1.1M -bf 2 out3nv.mp4
-map [out4] -an -vcodec nvenc -b:v 0.5M -bufsize 0.5M -maxrate 0.5M -bf 2 out4nv.mp4
Note: "- y" means overwrite existing files without confirmation.

Example:
ffmpeg -y -i $1 $2 $3 -filter_complex \nvresize=5:s=hd1080\|hd720\|hd480\|wvga\|cif:readback=0[out0][out1][out2][out3][out4]\ -map [out0] -an -vcodec nvenc_h264 -preset slow -profile:v main -async 1 -b:v 200M -bufsize 200M -maxrate 200M -refs 1 -bf 2 $1_1080p.mp4 \ -map [out1] -an -vcodec nvenc_h264 -preset slow -profile:v main -async 1 -b:v 100M -bufsize 100M -maxrate 100M -refs 1 -bf 2 $1_720p.mp4 \ -map [out2] -an -vcodec nvenc_h264 -preset slow -profile:v main -async 1 -b:v 50M -bufsize 50M -maxrate 50M -refs 1 -bf 2 $1_480p.mp4 \ -map [out3] -an -vcodec nvenc_h264 -preset slow -profile:v main
-async 1 -b:v 25M -bufsize 25M -maxrate 25M -refs 1 -bf 2 $1_wvga.mp4 \ -map [out4] -an -vcodec nvenc_h264 -preset slow -profile:v main -async 1 -b:v 10M -bufsize 10M -maxrate 10M -refs 1 -bf 2 $1_cif.mp4

[NikosD]

I did some further tests regarding the stability of the QSVEncC and unfortunately it seems that it is StaxRip's fault.

Running the command via CLI directly without using StaxRip's GUI, i get a stable performance of ~250fps (!)

The exact same clip, with the exact same options drops the performance from 250fps to 99fps (!) using StaxRip.

In all cases I used QSVEncC HW decoding, the switch --avqsv.

So, the only parameter different is the demux/mux of the two apps and maybe some hidden (?) or non-hidden switches.

I can't think of something else, but definitely QSVEncC as a standalone app has no problem at all (!!) on my system.

[NikosD]

Hello Frank.

I used latest QSVEncC v2.40 with a custom switch suggested by rigaya in order to find out what is going on.

So, I put in "Custom Switches:" field these switches --input-thread 1 --output-thread 1 --perf-monitor --log log.txt running at the same time the GPU-Z app in the background and I sent rigaya the log.txt and the .csv file produced in the temp directory of StaxRip.

He replied that he can see QSVEncC waiting doing nothing for a while and start running again in a period of about 5 sec.

Weird behavior which is the cause of my sudden drops of GPU load and performance.

I don't know how could I help more in order to find out the cause of the problem.

[stax76]

Are you sure there is a difference between windows shell and StaxRip? I get around 200 fps in and outside of StaxRip, when I wake up from Standby though it's only 70 fps again in and outside of StaxRip the same.

[Havokdan]

Wow, I manually changed the version of QuickSync to version 2.40, the encodes who were in the average speed of 70/90 fps was for over 400 fps.

[Pulp Catalyst]

bug in StaxRip x64 1.3.2.0 pre-release

Python exception: knlm.KNLMeansCL: a must be greater then or equel to 1!

this happens with temporal light/medium/strong profile

[NikosD]

Are you sure there is a difference between windows shell and StaxRip? I get around 200 fps in and outside of StaxRip, when I wake up from Standby though it's only 70 fps again in and outside of StaxRip the same.
Yes. I did the tests a few times.

The problem is there, even when I run "Execute command" from inside StaxRip running QSVEncC.

Only when I run QSVEncC from pure Shell environment I get stable performance.

[stax76]

Did you try to reboot? It has helped here.

[Magik Mark]

bug in StaxRip x64 1.3.2.0 pre-release



this happens with temporal light/medium/strong profile


Are you using nvidia gtx 900 series Gpu?


Sent from my iPhone using Tapatalk

[NikosD]

Did you try to reboot? It has helped here.
If it was for me, I always shut down and restart my PC.

I don't leave it open for no reason.

[Pulp Catalyst]

i'm using gtx 760, i changed to another profile, i'm now using the temporal + spacial one instead, as it's only "dvd" material, the speed is ok, the GPU can decode fast enough to keep the pipe fed to x265.

[stax76]

If it was for me, I always shut down and restart my PC.

I don't leave it open for no reason.

My PC boots ridiculous slow, like a minute and there is nothing left I could try to make it faster. I shut it down every night but at daytime I often just put it in energy saving mode.

I made some more test with same results as before, I never saw a fps difference between running in StaxRip or the command shell. Normally I get about 220 fps but when I but the PC shortly to energy saving mode it drops to pitiful 70 fps until I either reboot or shortly deactivate the device in the device manager. My specs are:

Windows 10 Pro - 10586.164
i5-6600K - Skylake - 20.19.15.4404 - GPU set to always on in Bios, no need for fake monitor
GTX 960 - Maxwell 2 - 10.18.13.6451
GA-Z170X-UD3 - F6

[burfadel]

Just a reminder Yadifmod2 has been updated :)

[NikosD]

I made some more test with same results as before, I never saw a fps difference between running in StaxRip or the command shell.


OK...Here we are.

Rigaya managed to reproduce my issue with his Haswell Win 8.1 Pro system and he found out a workaround.

In order to reproduce the issue with your systems, you have to transcode a clip with high bitrate output, more than 20 Mbps.

Probably you must have a large bitrate input source clip and use the default -cqp or -icq encoding modes with low values for cqp and icq, in order to output large bitrates.

My sample is a source clip with 53Mbps and the output is 25Mbps using default -cqp value of QSVEncC.

The workaround is to add a custom switch --output-buf with values 4 or 8 or 16.

With that switch --output-buf 16 my average speed is ~235 fps.

The default value of --output-buf is 64 and it drops my performance to ~95 fps (!)

That switch defines the internal buffer size in MBytes for output and its purpose is not to mix up disk input & output in fine grain for further performance.

According to rigaya, output buffer size and Staxrip should have no interaction to each other.

As a workaround he will probably put a lower than 64 value to that switch in the next QSVEncC release, BUT Frank I think you could probably send an email to rigaya to find the cause of the issue and fix it, if possible.

I don't know if Skylake has the same issue, using large bitrate (> 20 Mbps) output.

I have to write once more, that using the CLI version of QSVEncC outside of StaxRip, I have no problem at all using the default values, but the CLI version of QSVEncC inside StaxRip, drops the transcoding speed more than 60% for high bitrate outputs.

[NikosD]

According to rigaya, Skylake has a drop in performance around 10% when the encoding exceeds 20Mbps and QSVEncC is used inside StaxRip.

That reminds me the increase in performance of ffmpeg qsv encoding that Frank noticed, when using ffmpeg CLI app outside StaxRip, compared to QSVEncC inside StaxRip.

Frank, it would be useful to try ffmpeg qsv encoding inside StaxRip, if you are interested in implementing that GUI, or try QSVEncC inside/ outside StaxRip with large bitrate output.

[stax76]

@Nikos

I'm still not able to reproduce it, please mail a full StaxRip log file and one log from the command shell (Ctrl+A and Enter), if possible tell me where to download the source video.

[NikosD]

Frank, I have sent you an email with everything you asked.

Now, for everyone wanted to test my source sample you can download it from here:
http://www.filedropper.com/megascansjungle

[jsquare]

Been using and testing Quick Sync with Staxrip (QSVEncC) these past few days, QS encodes are very flat and kills a lot of detail unlike x264 that can be fine tuned, but the speed of QS is 4 times faster than x264 on my rig. I tried to solve this issue with one of the custom switches: The --vpp-detail-enhance <int> option, but it gives the same results no matter the value of the strength, tried from 1 to 100.
Anyone knows the values or range for this variable?

[stax76]

@Nikos

with your sample and settings I get this numbers:

StaxRip: 244-245 fps
Shell: 244-245 fps
--output-buf 16: 252 fps

I see a drop to 86 fps after wake up from power saving mode. Looks like a problem of the Intel driver.

If a programmer has a problem like yours chances to find the reason are already not good but if it happens not on his machine and only on one machine chances are near zero.

You can try to change the process priority in the settings and change your target drive because --output-buf might affect disk IO. I can add support for --output-buf of course.

I have done some work on the ffmpeg GUI and will do some more but due to the freezes it's not really useful, I hope most issues can be fixed some time.

[JohnLai]

Been using and testing Quick Sync with Staxrip (QSVEncC) these past few days, QS encodes are very flat and kills a lot of detail unlike x264 that can be fine tuned, but the speed of QS is 4 times faster than x264 on my rig. I tried to solve this issue with one of the custom switches: The --vpp-detail-enhance <int> option, but it gives the same results no matter the value of the strength, tried from 1 to 100.
Anyone knows the values or range for this variable?

{Detail Enhancement}: is the process of enhancing the edge contrast to improve its sharpness. VPP uses an adaptive detail enhancement algorithm to increase the edge sharpness.

Value of 0-100 (inclusive) indicates the level of details to be enhanced. Default value is 0 (disabled).

Sorry to break the party, but that option is not what you need.
There is not much you can do with QSV about finer detail retainment. Maybe LA-ICQ mode, higher value for la-depth scenechange, trellis for all, --quality sets to best, --b-pyramid on,--weightp, --weightb, --la-quality sets to slow .....etc?

[NikosD]

@Nikos

with your sample and settings I get this numbers:

StaxRip: 244-245 fps
Shell: 244-245 fps
--output-buf 16: 252 fps

I see a drop to 86 fps after wake up from power saving mode. Looks like a problem of the Intel driver.

If a programmer has a problem like yours chances to find the reason are already not good but if it happens not on his machine and only on one machine chances are near zero.

You can try to change the process priority in the settings and change your target drive because --output-buf might affect disk IO. I can add support for --output-buf of course.



Rigaya released QSVEncC v2.41 with a default --output-buf 8, so no worries of using QSVEncC inside or outside StaxRip.

It's only that we really didn't find out the reason of dropping performance on Haswell so much inside StaxRip.



I have done some work on the ffmpeg GUI and will do some more but due to the freezes it's not really useful, I hope most issues can be fixed some time.


Nice.
It's a work on development from ffmpeg team, so maybe sometime they will reach the stability of QSVEncC.

You could also add the ffmpeg QSV option as a decoder in all three HW encoding GUIs of rigaya's encoders inside StaxRip (Intel, Nvidia, AMD) without changing the encoder.

It could be better/ more compatible than ffmpeg DXVA2 for Intel.


Been using and testing Quick Sync with Staxrip (QSVEncC) these past few days, QS encodes are very flat and kills a lot of detail unlike x264 that can be fine tuned, but the speed of QS is 4 times faster than x264 on my rig. I tried to solve this issue with one of the custom switches: The --vpp-detail-enhance option, but it gives the same results no matter the value of the strength, tried from 1 to 100.
Anyone knows the values or range for this variable?


QSVEncC is based on a mixed/hybrid fixed function/GPU encoder with a lot more flexibility and options than NVEncC (Nvidia) or VCEEncC (AMD), but still is no match for a SW encoder like x264 in terms of encoding options.

The main advantages of every HW encoder is the speed, low power and efficiency.

The main drawbacks are quality, size and flexibility.

Try --icq encoding mode with lower values and maybe the lookahead switches.

Read the help file, it has a lot of options and if some of them don't work, email directly to the developer (rigaya) pointing out the issue.

He usually fixes bugs in the next release.