View Full Version : StaxRip 2.0 Support Thread
Atlantis
29th September 2019, 20:27
So, this happened after a 3 day encode! Any idea what is this?
FormatException (2.0.4.0)
Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
at System.Text.StringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ParamsArray args)
at System.String.FormatHelper(IFormatProvider provider, String format, ParamsArray args)
at System.String.Format(String format, Object arg0, Object arg1)
at StaxRip.Audio.CutMkvmerge(AudioProfile ap) in D:\Projekte\VB\staxrip\General\Audio.vb:line 467
at StaxRip.Audio.Cut(AudioProfile ap) in D:\Projekte\VB\staxrip\General\Audio.vb:line 188
at StaxRip.Audio.Process(AudioProfile ap) in D:\Projekte\VB\staxrip\General\Audio.vb:line 46
at StaxRip.GlobalClass._Closure$__._Lambda$__31-0() in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 105
at System.Threading.Tasks.Parallel.<>c__DisplayClass4_0.<Invoke>b__0()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at StaxRip.GlobalClass.ProcessJob(String jobPath) in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 138
at StaxRip.GlobalClass.ProcessJobs() in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 37
And I also get 3 files that I never got before, don't know why. I'm not trimming anything.
mov.English_cut_mm.avi
mov.English ID0_cut_sub.mkv
mov.English ID0_cut_.srt
stax76
29th September 2019, 21:14
For most issues I need a full log file. This looks like an issue that is fixed in the last Beta build. It should absolutely only happen when you used the cut feature in the preview and if your source had audio or subtitle tracks that have titles, these titles are written to the filenames (new feature recently added) enclosed in curly braces and that curly braces caused an exception in a crappy legacy .NET format function.
Atlantis
29th September 2019, 22:21
OK Thanks. Yes this happens when it is encoding the audio and the extracted audio track has a name like this
movie ID2 English {5.1 DTS-HD-MA (AAAAAAAAAAAAA)}.dtshd
Thank god the video encoded without error. It took me 3 days! I'm keeping backups of the video in case!
When I encode the audio track separately with Execute, it works. Only fails when I use the full encode mode.
I did use the cut in the preview but then I unchecked the Trim part. It's ok I will fix this project myself untill the next release comes out.
stax76
29th September 2019, 22:27
Unchecking trim in the script is not sufficient because it's also saved somewhere else, you have to delete it in the preview.
Atlantis
30th September 2019, 01:03
I've updated my builds and add two versions of x265. The one from git (x265-3.2...) and the modifided version (x265_custom_...) with custom progress bar like MeteorRain uses. THX for code @ MeteorRain
What are those? Can we see screenshots?
Natty
30th September 2019, 01:15
I've updated my builds and add two versions of x265. The one from git (x265-3.2...) and the modifided version (x265_custom_...) with custom progress bar like MeteorRain uses. THX for code @ MeteorRain
perfect. no one else is currently updating x265 builds that fast. thank you.
JKyle
30th September 2019, 06:02
perfect. no one else is currently updating x265 builds that fast. thank you.
Agreed. I'm really happy to see that it's hard to catch up.
Good job, @Patman.
:thanks:
chipxtreme
30th September 2019, 15:06
I've just downloaded 2.0.4.6 beta and went to encode a file and now the file size box under the target section is not there when I select x265 10bit profile?
Patman
30th September 2019, 15:50
What are those? Can we see screenshots?
Just cosmetic
Screen Comparison (http://www.framecompare.com/screenshotcomparison/DWLWLNNX)
Patman
30th September 2019, 15:54
I've just downloaded 2.0.4.6 beta and went to encode a file and now the file size box under the target section is not there when I select x265 10bit profile?
What mode have you select under x265 options? Filesize is only shown for bitrate and the two/ three pass modes.
chipxtreme
30th September 2019, 16:02
What mode have you select under x265 options? Filesize is only shown for bitrate and the two/ three pass modes.
I use Nvidia x265, I cloned the main x265 profile and added settings from a guide I found on net.
The options are --vbrhq 0 --codec h265 --preset quality --level 4.1 --output-depth 10 --vpp-edgelevel --vpp-deband --lookahead 32 --vbr-quality 0 --aq
Patman
30th September 2019, 16:56
I use Nvidia x265, I cloned the main x265 profile and added settings from a guide I found on net.
The options are --vbrhq 0 --codec h265 --preset quality --level 4.1 --output-depth 10 --vpp-edgelevel --vpp-deband --lookahead 32 --vbr-quality 0 --aq
Stax made some changes in 2.0.4.6 beta. To see the filesize and the bitrate you need to set --vbr-quality to -1 under rate control.
chipxtreme
30th September 2019, 17:13
Stax made some changes in 2.0.4.6 beta. To see the filesize and the bitrate you need to set --vbr-quality to -1 under rate control.
Thanks that works :D
Salem874
30th September 2019, 22:00
I've found StaxRip after trying to find a way to rip HDR content to a smaller size, but KEEPING the HDR metadata.
I currently use Handbrake due to the excellent quality of it's exports, plus it's super easy to use (but still flexible), but as we know it's not yet fully HDR/10-bit compatible.
However, i'm extremely confused as to how to re-encode/rip HDR content using StaxRip. Are there any guides/tutorials out there?
jlw_4049
30th September 2019, 22:16
I've found StaxRip after trying to find a way to rip HDR content to a smaller size, but KEEPING the HDR metadata.
I currently use Handbrake due to the excellent quality of it's exports, plus it's super easy to use (but still flexible), but as we know it's not yet fully HDR/10-bit compatible.
However, i'm extremely confused as to how to re-encode/rip HDR content using StaxRip. Are there any guides/tutorials out there?I could show you my work flow for 4k. Also best to learn to use stuff other then Handbrake. So you can control settings better. (1080p and less)
Sent from my SM-G965U1 using Tapatalk
-QfG-
1st October 2019, 19:33
However, i'm extremely confused as to how to re-encode/rip HDR content using StaxRip. Are there any guides/tutorials out there?
HDR10 Rip:
1st check the Metadata from your source movie with mediaInfo. Example:
colour_range : Limited
colour_primaries : BT.2020
transfer_characteristics : PQ
matrix_coefficients : BT.2020 non-constant
MasteringDisplay_ColorPrimaries : Display P3
MasteringDisplay_Luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
MaxCLL : 1000 cd/m2
MaxFALL : 400 cd/m2
now, u must set the metadata in your bitstream. the easiest way is, to use the "Custom" section in x265 Encoder settings. The sample above:
--hdr --output-depth 10 --hdr-opt --max-cll "1000,400" --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)"
*Examples for Luminance:
MasteringDisplay_Luminance : min: 0.0001 cd/m2, max: 1000 cd/m2 = L(10000000,1)
MasteringDisplay_Luminance : min: 0.0005 cd/m2, max: 1000 cd/m2 = L(10000000,5)
MasteringDisplay_Luminance : min: 0.0010 cd/m2, max: 1000 cd/m2 = L(10000000,10)
MasteringDisplay_Luminance : min: 0.0100 cd/m2, max: 1000 cd/m2 = L(10000000,100)
Thats all for HDR10.
HDR10+
You must extract the HDR10+ Metadata from the complete HEVC bitstream and save into a JSON File.
You can find a parsing tool for HDR10+ Metadata here:
https://github.com/quietvoid/hdr10plus_parser
Activate HDR10+ Metadata in the "Custom" section, too.
Example:
--dhdr10-opt --dhdr10-info "C:\Path\to\JSON.json"
Thats all.
jlw_4049
1st October 2019, 20:33
HDR10 Rip:
1st check the Metadata from your source movie with mediaInfo. Example:
now, u must set the metadata in your bitstream. the easiest way is, to use the "Custom" section in x265 Encoder settings. The sample above:
*Examples for Luminance:
MasteringDisplay_Luminance : min: 0.0001 cd/m2, max: 1000 cd/m2 = L(10000000,1)
MasteringDisplay_Luminance : min: 0.0005 cd/m2, max: 1000 cd/m2 = L(10000000,5)
MasteringDisplay_Luminance : min: 0.0010 cd/m2, max: 1000 cd/m2 = L(10000000,10)
MasteringDisplay_Luminance : min: 0.0100 cd/m2, max: 1000 cd/m2 = L(10000000,100)
Thats all for HDR10.
HDR10+
You must extract the HDR10+ Metadata from the complete HEVC bitstream and save into a JSON File.
You can find a parsing tool for HDR10+ Metadata here:
https://github.com/quietvoid/hdr10plus_parser
Activate HDR10+ Metadata in the "Custom" section, too.
Example:
Thats all.StaxRip does this all automatically for you if uses correctly.
Sent from my SM-G965U1 using Tapatalk
-QfG-
1st October 2019, 20:52
I don't know, i'm setting all HDR Metadata manually since i encoded HDR content.
Salem874
1st October 2019, 21:14
I could show you my work flow for 4k. Also best to learn to use stuff other then Handbrake. So you can control settings better. (1080p and less)
Sent from my SM-G965U1 using Tapatalk
That would be a great help. Any help would be appreciated.
I understand Handbrake may not be the best tool, but having to learn/memorise all the various command line parameters used by many other tools is not actually very user friendly. That's what handbrake makes easy. :)
jlw_4049
1st October 2019, 21:29
I don't know, i'm setting all HDR Metadata manually since i encoded HDR content.You're obviously pretty adept when it comes to encoding. I'd like to learn all the manual commands as well but thankfully staxrip does the heavy lifting for me.
Sent from my SM-G965U1 using Tapatalk
aegisofrime
2nd October 2019, 15:55
Hello,
I'm getting the following error with certain content, especially wmv files:
vapoursynth.Error: Analyse: failed to retrieve first frame from super clip. Error message: Resize error: Resize error 3074: no path between colorspaces (2/2/2 => 1/2/2). May need to specify additional colorspace parameters.
I noticed that this error is caused by the following line, which appears to be auto-added by StaxRip:
clip = clip.resize.Bicubic(matrix_s = '709', format = vs.YUV420P8)
The strange thing is, the script as a whole works perfectly fine without the above line, so why is it being auto-added and how do I stop StaxRip from auto-adding it?
NikosD
2nd October 2019, 17:23
It's a quality mode and I missed setting the main window to quality mode view, 2.0.4.6 Beta is available. Hello Frank.
It seems that NVEncC GUI is missing two useful switches: (or I just couldn't find them)
--aq-strength <int> set aq strength (weak 1 - 15 strong) default: 0 = auto
which is used along with --aq
and
--bref-mode <string> set B frame reference mode
- disabled (default)
- each
- middle
Also, I suggest for the GUI to rename these switches at the Rate Control tab:
Adaptive Quantization to Adaptive Quantization (Spatial)
and
AQ Temporal to Adaptive Quantization (Temporal)
to be more descriptive and accurate.
Thanks!
stax76
2nd October 2019, 21:10
@aegisofrime
When the source is loaded staxrip checks with mediainfo if chroma subsampling is 4:2:0, if not it adds a function to convert it to 4:2:0, this function is faulty for a reason I don't understand. I'm not sure if it's a great idea to automatically insert this function, feedback is welcome, it would not be difficult to add an option so it can be user disabled. Because it's only inserted after the source is loaded you can remove it in the script editor afterwards.
@NikosD
--aq-strength is only visible for h264, does it work with h265?
--bref-mode was marked as ignore for unknown reasons (staxrip analyzes --fullhelp to discover new/changed/removed switches), next build will support it.
Adaptive Quantization to Adaptive Quantization (Spatial)
AQ Temporal to Adaptive Quantization (Temporal)
Available in the next build.
NikosD
2nd October 2019, 21:50
@NikosD
--aq-strength is only visible for h264, does it work with h265?
--bref-mode was marked as ignore for unknown reasons (staxrip analyzes --fullhelp to discover new/changed/removed switches), next build will support it.
Available in the next build.Thanks.
Both AQ modes work with Turing encoders using both H.264 and H.265.
--aq is spatial and is used along with --aq-strength for both H.264/H.265 for all (almost) nVidia cards
--aq-temporal is temporal obviously and it works for all (almost) nVidia cards using H.264.
But Turing encoders can use it for H.265 too.
A more advanced way to figure out what it works for a specific card in order to offer it to the GUI, could be to run --check-features in real-time in background and read the appropriate fields e.g AQ Temporal in order to decide if you can provide it or not to the GUI/ user.
Atlantis
4th October 2019, 00:04
Question. What CRF do you use for your 4K HDR encodes?
With a little detail and noise in the picture, the encoding size could become huge with even CRF 23.
What are your limits for video bitrate? I have an arbitrary limit that my 4K encodes should not go higher than 15 Mbit/s for video.
Atlantis
4th October 2019, 00:10
Feature Request: in the demux window, you get buttons to select None for Audio and Subtitle but you do not have buttons for the Attachments. It's better to have the same buttons that you have for Audio and Subtitle also for attachments.
ZeroCool22
4th October 2019, 01:29
What does --bref-mode?
jlw_4049
4th October 2019, 04:44
Question. What CRF do you use for your 4K HDR encodes?
With a little detail and noise in the picture, the encoding size could become huge with even CRF 23.
What are your limits for video bitrate? I have an arbitrary limit that my 4K encodes should not go higher than 15 Mbit/s for video.Varies widely from video to video. I do multiple tests to get the CRF I want for my final encode. Takes me about 10 minutes per video to test for b frames and then test for the proper CRF setting.
Also I shoot for 16 MB's.
Sent from my SM-G965U1 using Tapatalk
Patman
4th October 2019, 06:34
What does --bref-mode?
Look here (https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#--bref-mode-string)
JKyle
4th October 2019, 07:19
2.0.4.8 Beta:
Since my MPC-HC is installed with K-Lite Codec Pack and its exe name is weirdly renamed as mpc-hc64_nvo.exe by K-Lite, I forced StaxRip to find this exe file on the Apps > Manage > MPC-HC menu.
No problem up to here.
But when I try to launch MPC-HC, StaxRip reports the following error message and fails to do it.
https://i.imgur.com/cwOHTcP.jpg
I guess it's because StaxRip tries to launch the app by calling the regular mpc-hc64.exe, not the filename altered by K-Lite.
Can you fix this issue please?
ZeroCool22
4th October 2019, 09:09
Look here (https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#--bref-mode-string)
Thank you, i'm really new to Staxrip, this will help a lot, thx.
ZeroCool22
4th October 2019, 09:10
I've found StaxRip after trying to find a way to rip HDR content to a smaller size, but KEEPING the HDR metadata.
I currently use Handbrake due to the excellent quality of it's exports, plus it's super easy to use (but still flexible), but as we know it's not yet fully HDR/10-bit compatible.
However, i'm extremely confused as to how to re-encode/rip HDR content using StaxRip. Are there any guides/tutorials out there?
But Handbrake doesn't let you encode with H265/NVEnc at 10 Bits, only with x265 and with this last one, you can't make use of the power of the GPU.
ZeroCool22
4th October 2019, 09:24
It's possible for StaxRip to encode with H265 at 12 Bits and if yes how do it, what parameter should i use?
Thx in advance?
NikosD
4th October 2019, 09:24
Available in the next build. Just downloaded your latest 2.0.4.8 version.
A few comments:
1) AQ Strength should be available only when someone selects Adaptive Quantization (Spatial).
From what I have read, it can't be used as a standalone option or using Adaptive Quantization (Temporal)
2) A small bug regarding "Constant Quality Mode"
Constant Quality Mode can be used only with VBRHQ like this:
"--vbrhq 0 --vbr-quality <float>"
In StaxRip when you select that option, you added the --vbr-quality 0 parameter.
You should add --vbrhq 0 instead and should be available with VBRHQ only.
3) The following HW resize options of --vpp-resize
nn nearest neighbor
npp_linear linear interpolation by NPP library
cubic 4x4 cubic interpolation
super So called "super sampling" by NPP library
lanczos Lanczos interpolation
need the nppi64_10.dll which uses the NPP library and supports x64 version only.
To use those algorithms, you need to download nppi64_10.dll separately and place it in the same folder as NVEncC64.exe.
Thanks!
ZeroCool22
4th October 2019, 10:01
Just downloaded your latest 2.0.4.8 version.
A few comments:
1) AQ Strength should be available only when someone selects Adaptive Quantization (Spatial).
From what I have read, it can't be used as a standalone option or using Adaptive Quantization (Temporal)
2) A small bug regarding "Constant Quality Mode"
Constant Quality Mode can be used only with VBRHQ like this:
"--vbrhq 0 --vbr-quality <float>"
In StaxRip when you select that option, you added the --vbr-quality 0 parameter.
You should add --vbrhq 0 instead and should be available with VBRHQ only.
3) The following HW resize options of --vpp-resize
nn nearest neighbor
npp_linear linear interpolation by NPP library
cubic 4x4 cubic interpolation
super So called "super sampling" by NPP library
lanczos Lanczos interpolation
need the nppi64_10.dll which uses the NPP library and supports x64 version only.
To use those algorithms, you need to download nppi64_10.dll separately and place it in the same folder as NVEncC64.exe.
Thanks!
--vbrhq 0 High value will give you better quality or it's always better to leave it at 0?
And also
adaptive quantization (spatial)
adaptive quantization (temporal)
Is always better to have it checked on?
Constant Quality Mode just block the other two, so it have no sense to active one of the other two if we use CQM?
Sorry for make a lot of question but i really want to know what i'm doing and if i'm doing it the correct way.
Atlantis
4th October 2019, 11:35
Varies widely from video to video. I do multiple tests to get the CRF I want for my final encode. Takes me about 10 minutes per video to test for b frames and then test for the proper CRF setting.
Also I shoot for 16 MB's.
How do you test to see which CRF to use?
And you meant 16Mbit/s not MB, right?
stax76
4th October 2019, 14:40
Since my MPC-HC is installed with K-Lite Codec Pack and its exe name is weirdly renamed as mpc-hc64_nvo.exe by K-Lite, I forced StaxRip to find this exe file on the Apps > Manage > MPC-HC menu.
No problem up to here.
But when I try to launch MPC-HC, StaxRip reports the following error message and fails to do it.
Will be fixed in the next build.
Constant Quality Mode can be used only with VBRHQ like this:
"--vbrhq 0 --vbr-quality <float>"
In StaxRip when you select that option, you added the --vbr-quality 0 parameter.
You should add --vbrhq 0 instead and should be available with VBRHQ only.
Please re-check, if you check 'Constant Quality Mode' then you should see --vbrhq 0
3) The following HW resize options of --vpp-resize
nn nearest neighbor
npp_linear linear interpolation by NPP library
cubic 4x4 cubic interpolation
super So called "super sampling" by NPP library
lanczos Lanczos interpolation
need the nppi64_10.dll which uses the NPP library and supports x64 version only.
To use those algorithms, you need to download nppi64_10.dll separately and place it in the same folder as NVEncC64.exe.
How large is the file and where can it be downloaded?
Taurus
4th October 2019, 15:16
How large is the file and where can it be downloaded?
Look here at rigayas google drive website:https://drive.google.com/drive/folders/0BzA4dIFteM2dS1ZUT1FjTnF3Q0E
Or for the somewhat older npp64_80.dll: https://drive.google.com/drive/folders/0BzA4dIFteM2dT0lnQ2tRTF9Zcnc
JKyle
4th October 2019, 15:42
Please re-check, if you check 'Constant Quality Mode' then you should see --vbrhq 0
Stax is right on this.
https://i.imgur.com/fIWjoYc.gif
stax76
4th October 2019, 15:43
Look here at rigayas google drive website:https://drive.google.com/drive/folde...1ZUT1FjTnF3Q0E
Or for the somewhat older npp64_80.dll: https://drive.google.com/drive/folde...0lnQ2tRTF9Zcnc
Thanks, I think it's too large to include by default.
Patman
4th October 2019, 18:34
Thanks, I think it's too large to include by default.
If someone want to use this option you can add a link to download the nppi64_10.dll.
NikosD
4th October 2019, 19:08
Please re-check, if you check 'Constant Quality Mode' then you should see --vbrhq 0 Stax is right on this.
Yes of course, you are both right!
I had VBR Quality at the default value of 0 which doesn't appear in the command line box and when I selected Constant Quality Mode, I saw only that it's just added at the end as --vbr-quality 0, but at the same time --vbrhq value changes to --vbrhq 0 as JKyle posted.
The parameter --vbrhq 0 becomes bold when you select 'Constant Quality Mode' and it's easier to see it, when there is a value to --vbr-quality and not leave it to the default 0.
Still, that mode 'Constant Quality Mode' shouldn't be shown when --vbr is selected but only for --vbrhq, I think.
Patman
4th October 2019, 19:19
The parameter --vbrhq 0 becomes bold when you select 'Constant Quality Mode' and it's easier to see it, when there is a value to --vbr-quality and not leave it to the default 0.
Still, that mode 'Constant Quality Mode' shouldn't be shown when --vbr is selected but only for --vbrhq, I think.
Hello NikosD,
I have done some tests with the option and it also works for --vbr.
With --vbr-quality 0 you got the best quality ;). Some requirements should be brought as a user, if you want to use certain options. Otherwise, the people here like to help ;) :D
NikosD
4th October 2019, 20:51
I have done some tests with the option and it also works for --vbr. Ok, but VBR (1 pass encoding) is a lot different than VBRHQ (2 pass encoding)
How did you test that is actually working ?
VBRHQ 0 is by itself self explanatory and I think in rigaya's help "Constant Quality" is also described as a VBRHQ only option.
I'm all ears to you because it's the first time that I go deeper to NVENC (till know I was just playing games :) )
NikosD
5th October 2019, 13:47
@stax76
Hello Frank.
Everything is working fine using StaxRip v2.0.4.9.
You are truly firing on all cylinders these days!
Clever addition of --vbr 0 --vbr-quality using VBR and 'Constant Quality' but I'm afraid is not going to work!
Haven't found it anywhere documented and I think 'Constant Quality' needs HQ (2-pass) encoding as a requirement.
Thanks!
Patman
5th October 2019, 14:32
@stax76
Hello Frank.
Everything is working fine using StaxRip v2.0.4.9.
You are truly firing on all cylinders these days!
Clever addition of --vbr 0 --vbr-quality using VBR and 'Constant Quality' but I'm afraid is not going to work!
Haven't found it anywhere documented and I think 'Constant Quality' needs HQ (2-pass) encoding as a requirement.
Thanks!
Hi NikosD,
due to a few tests with NVEnc (see link (https://github.com/staxrip/staxrip/issues/62#issuecomment-536600384)), the option was added. The --vbr-quality 0 option behaves identically with --vbr 0 and --vbrhq 0. I have seen that the option is exclusive to --vbrhq, but it works with --vbr as well.
NikosD
5th October 2019, 14:49
Hi NikosD,
due to a few tests with NVEnc (see link (https://github.com/staxrip/staxrip/issues/62#issuecomment-536600384)), the option was added. The --vbr-quality 0 option behaves identically with --vbr 0 and --vbrhq 0. I have seen that the option is exclusive to --vbrhq, but it works with --vbr as well. OK...I see your comparison.txt file and it seems that --vbr 0 --vbr-quality is something that NVEncC understands.
But I'm not sure I could say the difference, even if you upload the encodings and this is the reason that probably I'm not going to try and test it myself.
If rigaya replies to the email of Frank, I suggest to follow his reply.
In his documentation, he doesn't refer to VBR as capable of Constant Quality mode, so after this email exchange between Frank and rigaya, maybe he should add it to his documentation, if it actually works.
Thanks for testing!
Tadanobu
5th October 2019, 16:30
Hello,
First of all, thank you very much for this great encoder. I had been using MeGUI for many years but I'm now switching to Staxrip. There are two very useful functions in MeGUI that I can't find in Staxrip. Could you please tell me if there is something similar ?
The first one is the input file in the file indexer in MeGUI that lets you choose an ifo file. When you select an ifo file as a source, it shows you the list of the videos in the DVD structure. With staxrip, I'm using DGIndex, which is fine. But that little ifo hack is sometimes very convenient and can save time.
The second one is the analysis tool in the AVS Script Creator from MeGUI. The analysis tool automatically suggests a deinterlacing function. I know I can manually add Yadif, QTGMC or whatever in the AVS Filters box. But when the source needs a more complex script, I'm sometimes clueless and the MeGUI analysis tools is very helpful.
Last question : I know the SVT encoders are still experimental (HEVC, VP9 and AV1), but are you planning to integrate them ? Using ffmpeg in command line is not that bad, but having a good GUI is always nice.
Thank you.
Natty
5th October 2019, 19:15
analysis tool isn't available. i miss that feature of MegUI
stax76
6th October 2019, 17:29
The first one is the input file in the file indexer in MeGUI that lets you choose an ifo file. When you select an ifo file as a source, it shows you the list of the videos in the DVD structure. With staxrip, I'm using DGIndex, which is fine. But that little ifo hack is sometimes very convenient and can save time.
If you don't have NTSC than it's easier to rip with makemkv. What should also work is choosing merge files and then select the vob files you want to open, it should then run dgindex on the selected files.
Last question : I know the SVT encoders are still experimental (HEVC, VP9 and AV1), but are you planning to integrate them ? Using ffmpeg in command line is not that bad, but having a good GUI is always nice.
It depends on how many people make a feature request for it on the issue tracker, post +1 and write a few words to the following issue:
https://github.com/staxrip/staxrip/issues/61
staxrip has support for a generic command line encoder, the xvid encoder is based on that so you can clone, rename and edit the xvid encoder to get your SVT encoder.
The second one is the analysis tool in the AVS Script Creator from MeGUI.
Even though it's a popular request, it's not planed to be supported.
NikosD
7th October 2019, 16:27
I asked Rigaya if he is going to update NVEncC to SDK v9.1 using multiple reference frames for Turing and he informed that he released NVEncC v4.51 with exactly that support.
Download link:
https://github.com/rigaya/NVEnc/releases/download/4.51/NVEncC_4.51_x64.7z
From nVidia's docs:
Multiple reference frames
Turing NVENC adds support for choosing the matching macroblock/CTB from multiple reference frames, which results to improvement to encoded quality.
The numbers of reference frames are decided inside NVIDIA’s display driver.
The current SDK exposes control to the client for specifying the number of reference frames which will override the values set inside NVIDIA’s display driver.
mcjordan
8th October 2019, 18:34
Frank, please add, if possible --multiref-l0, --multiref-l1 in NVEnc settings as choise.
Rigaya has released a new NVEnc 4.5.2
Short changelog:
Change command line options for multiple refs from NVEnc 4.51, to be able to set them individually. (--multiref-l0, --multiref-l1)
Add multiref-** options to help.
Revert binaries for x64 buillt in appveyor back to VS2017, as VS2019 sometimes runs into error when installing CUDA.
stax76
9th October 2019, 04:13
Frank, please add, if possible --multiref-l0, --multiref-l1 in NVEnc settings as choise.
Rigaya has released a new NVEnc 4.5.2
Short changelog:
Change command line options for multiple refs from NVEnc 4.51, to be able to set them individually. (--multiref-l0, --multiref-l1)
Add multiref-** options to help.
Revert binaries for x64 buillt in appveyor back to VS2017, as VS2019 sometimes runs into error when installing CUDA.
It will be supported in the next build.
mcjordan
9th October 2019, 19:26
Frank - set of integer value for --multiref-l0, --multiref-l1 (max 7) is missing...
stax76
9th October 2019, 19:45
And defaults are 0 ?
https://github.com/staxrip/staxrip/blob/master/Encoding/NVEnc.vb#L444
mcjordan
9th October 2019, 19:54
Hmm... Not sure, but yes. Sample which suggest Rigaya is 5/4, I use 7/6 (L0/L1). At --ref value 8. Logically - yes - 0 is the starting point.
mcjordan
9th October 2019, 20:16
I just compiled it and did a small encoding test. Works excellent. Thank you, Frank!
mcjordan
9th October 2019, 20:24
New ffms2 (https://ln2.sync.com/dl/917b6fe60/d9e5tyaq-qwmnwnbq-ks2xwnur-j9bbdfcz) from StvG:
- ffmpeg n4.3_a746359;
- dav1d 0.4.0 (seeking accurate with threads=1 and still ~50% faster than aom).
expanseFan
10th October 2019, 09:07
Hello, although I've been using StaxRip for quite some time, I have some questions regarding encoding a DVD but also questions in general about StaxRip that have been bugging me for quite some time, I hope you could help me! :)
1) how should I open VIDEO_TS folder in StaxRip? Is merge files correct?
2) Which filter should I use to deinterlace? Is yadifmod2 adequate?
3) Is QTGMC superior even in super fast or ultra fast presets? Does SelectEven(),to keep original framerate, reduce deinterlace quality? When should I use QTGMC with repair?
3) Is there an alternative to QTGMC that offers better quality than yadif but is faster than QTGMC?
4) When encoding audio in AAC should I keep normalize checked? What does it do? Also, which encoder is better for AAC, ffmpeg or eac3to? Why isn't it possible to specify bitrate in AAC but I have to use quality slider?
5) In the x264 or x265 options, besides tweaking the basic options(preset,mode,etc.), is it okay leaving the other options(rate control, analysis, slice decisions tabs) at their defaults? Are these options automatically set based on the video source?
Sorry for so many questions, I'd like to learn more about StaxRip, it's such a great tool, I find it more useful and significantly faster than Handbrake! :D
stax76
10th October 2019, 09:27
That are many questions for one post. :-)
how should I open VIDEO_TS folder in StaxRip? Is merge files correct?
Yes, for PAL DVDs using MakeMKV has some advantages.
expanseFan
10th October 2019, 09:41
That are many questions for one post. :-)
Yes, for PAL DVDs using MakeMKV has some advantages.
I'll try that, thanks, never heard of MKV before. I suppose it converts the entire VIDEO_TS folder into one MKV file (losslessly)?
Indeed, too many questions, I hope you can answer as many as you can, WHENEVER you have the time of course! (they are at a descending order of importance to me).
Also, I'd like to congratulate you for the great work you're doing with StaxRip, it's an exceptional tool for encoding my videos. Although, I'm a newbie, I prefer StaxRip over Handbrake due to its better performance, ability to trim video(with preview) and the fact that it has many filters available with VapourSynth and AviSynth. :thanks:
P.S. I like that you frequently update StaxRip to latest x264, x265, NVENC, ffmpeg, etc. :) Don't want to rush you, but are you planning to release a new stable soon? Couldn't find your beta builds, are they stable enough for encoding without errors?
TomSmith
10th October 2019, 15:06
Hi,
I used StaxRip for some time with my Intel/Nvidia Setup.
As I changed my hardware to AMD Ryzen3000/Navi10 I noticed that VCEEnc seems to be outdated. Is it that Rigaya stopped development by the end of 2018? I do hope that this is not the case...
If it really is, is there another Enc that should be used with AMD CPU/GPU?
Thank you very much,
Tom
NikosD
10th October 2019, 16:49
As I changed my hardware to AMD Ryzen3000/Navi10 I noticed that VCEEnc seems to be outdated.
Is it that Rigaya stopped development by the end of 2018? I do hope that this is not the case...
Rigaya is like Frank (stax76)
He never stops development.
Unfortunately AMD stopped development of its SDK called AMF.
Take a look at GitHub of AMD AMF and I think you will conclude the same think.
I don't think you will find a better encoder, try ffmpeg with built-in AMD encoder to see if there is something more to add to VCEEnc.
TomSmith
11th October 2019, 17:18
Rigaya is like Frank (stax76)
He never stops development.
Unfortunately AMD stopped development of its SDK called AMF.
Take a look at GitHub of AMD AMF and I think you will conclude the same think.
I don't think you will find a better encoder, try ffmpeg with built-in AMD encoder to see if there is something more to add to VCEEnc.
:thanks:
Atlantis
12th October 2019, 00:52
If we have 2 instances of Staxrip, is it possible to have 2 Job Lists?
At the moment we have only one Job List. I think it is important to be able to tell which instance should get which job.
Sometimes you have long encodes that you want in one instance and other short encodes that you want in a second instance.
stax76
12th October 2019, 01:43
If we have 2 instances of Staxrip, is it possible to have 2 Job Lists?
No, it's always shared.
Atlantis
12th October 2019, 01:58
Makes sense to be able to separate them if it's easy to do.
jlw_4049
12th October 2019, 02:17
Makes sense to be able to separate them if it's easy to do.I think temporary workers similar to MeGui would work instead of two seperate UIs.
Sent from my SM-G965U1 using Tapatalk
Atlantis
12th October 2019, 02:33
I finally switched to VapourSynth to do my encodes and just found out that there is no FFT3DFilter in VS menus. I can see that it exists in the plugin directory of VS.
I used it in Avisynth alot and found it very useful.
Atlantis
14th October 2019, 00:33
I am using MCTemporalDenoise in VapourSynth and I get this message
Script exceeded memory limit. Consider raising cache size.
The encoding still continues and finishes. Do I have to do something? Is something wrong?
stax76
14th October 2019, 01:30
http://forum.doom9.net/showthread.php?p=1874625#post1874625
Atlantis
14th October 2019, 01:53
Thanks.
core.max_cache_size =xxxx
But I have no idea what I should put in xxxx and is it necessary? I prefer not to add things and not to complicate. It already encodes, does it mean that it is encoding incorrectly?
stax76
14th October 2019, 02:18
It's documented here:
http://www.vapoursynth.com/doc/pythonreference.html#Core.max_cache_size
If search don't help you can ask in the VapourSynth thread, I'm not really an expert in VS because I'm retired from encoding...
imhh11
14th October 2019, 04:18
Thanks.
core.max_cache_size =xxxx
But I have no idea what I should put in xxxx and is it necessary? I prefer not to add things and not to complicate. It already encodes, does it mean that it is encoding incorrectly?
I use core.max_cache_size = 8192 for my fmtc script and the warning is gone
Atlantis
14th October 2019, 04:27
Thanks
I'm asking this question in here because it concerns the entire pipeline which staxrip uses. It's about MCTemporalDenoise.
I'm using MCTemporalDenoise to process some HDR 10bit video. I look at MCTemporalDenoise script and it's dated 2010, 9 years ago.
Safe to say that there was no HDR back then. I just want to be sure that if I use MCTemporalDenoise inside staxrip and feed it a 10bit clip,
it will not get converted to 8bit or a lower color space inside the pipeline, right? Is it HDR 10bit compatible?
ZeroCool22
14th October 2019, 13:31
Question:
In VBRHQ
If we have checked "Constant Quality Mode" we must deactivate the other options or can have AQ checked too?
https://i.ibb.co/0V3kxht/Screenshot-6.png
Patman
14th October 2019, 20:21
Question:
In VBRHQ
If we have checked "Constant Quality Mode" we must deactivate the other options or can have AQ checked too?
https://i.ibb.co/0V3kxht/Screenshot-6.png
Hi Zero,
default setting for --aq is off (look here (https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#--aq)) but the AQ-option can also be enabled.
Natty
15th October 2019, 01:59
I'm using MCTemporalDenoise to process some HDR 10bit video. I look at MCTemporalDenoise script and it's dated 2010, 9 years ago.
Safe to say that there was no HDR back then. Is it HDR 10bit compatible?
avisynth+ or HBD weren't introduced at that time afaik. you might need to look at some another denoiser
expanseFan
15th October 2019, 18:49
Hello, I have a problem about deinterlacing with VapourSynth in StaxRip. I want to use QTGMC without doubling the framerate. In order to do that, in Avisynth I simply add SelectEven() below QTGMC. In VapourSynth, how do I do that? I tried several combinations(SelectEven(), clip = havsfunc.SelectEven(), clip = havsfunc.SelectEven(clip)) but nothing works. How can I use it? Is there an alternative to QTGMC but one that's better quality from yadifmod?
stax76
15th October 2019, 18:55
I think you want SelectEvery.
http://www.vapoursynth.com/doc/functions/selectevery.html
Natty
16th October 2019, 00:12
@Natty
I would need a full log file.
here (https://privatebin.net/?a682c5c8dc45f653#8ybd7bpLvqCtGXGpuTPGFiRYYYwS7LHrU8CvuDop6LZR)
i used all decoding methods, and in all of them "normalization" option was set. i prefer "pipe" but i think it doesnt normalize. or maybe audio was normalized by ffmpeg and not qaac?
:thanks:
ZeroCool22
16th October 2019, 04:15
Hi Zero,
default setting for --aq is off (look here (https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#--aq)) but the AQ-option can also be enabled.
Thx you!
Exaris
17th October 2019, 21:21
Do we have an approximate date for the next stable release? I've seen a lot of useful commits from 2.0.4.0 but I would like to avoid beta build as I modify each release adding scripts/plugins/encoders before use which would make weekly upgrades time consuming.
Bahamuth
17th October 2019, 21:47
Why is it a must to have Avisynth+ installed when the programm tells me, it can run with Avisynth+ or Vapoursynth? Vapoursynth is installed, all pathes are correct in the settings, Python is installed, everything is freaking there.
But whenever I want to open a video source, it wants to force me to install Avisynth+. Why? I wasted an hour now to check all settings 10 times in all dialog windows I could find in Staxrip 2. All I could find in this thread was "you have to create a template"
Nowhere in the template I can tell "Use Vapoursynth". This really should be pointed out much better how to even use Vapoursynth. I'm close to uninstall Python and Vapoursynth again because I don't need it when the program can't use it.
Btw. same with "Included Two versions of exe file, One targets 4.7.2 framework and other targets the newer 4.8 framework." Yes. I started Staxrip.exe out of the 4.8 folder and got a ton of error messages, because he couldn't find the Apps folder, because it was not in the same folder like staxrip.exe, which I couldn't read anywhere.
stax76
17th October 2019, 22:54
@Bahamuth
That would be a bug, I will examine it if you create a ticket on the tracker. In your startup template I assume that your filter setup is vapoursynth and not avisynth?
stax76
18th October 2019, 00:30
Do we have an approximate date for the next stable release? I've seen a lot of useful commits from 2.0.4.0 but I would like to avoid beta build as I modify each release adding scripts/plugins/encoders before use which would make weekly upgrades time consuming.
Since people start to ask for it and I didn't work on new features that would likely be buggy in the beginning, I should probably make a new release. Maybe it makes sense to wait for a new VapourSynth release.
About modifications, isn't everything covered by the settings, we didn't do any breaking changes or resets for a long time.
Exaris
18th October 2019, 04:20
When I change builds I have to move my custom scripts and plugins into the new install's directory and point the settings to them. I also have customized encoder profiles I need to reconfigure each time.
Also, unrelated but is there a way to use an image batch as an input? Like FILENAME[000-999].FILETYPE Ex. Animation000.jpg,Animation001.jpg...Animation999.jpg
At the moment I am losslessly muxing the images into an mkv before importing into StaxRip with "ffmpeg -framerate FPS -i FILENAME%03d.jpg -codec copy output.mkv", is there a way to do this without running through external ffmpeg first?
stax76
18th October 2019, 08:45
You could put your scripts inside staxrip's settings directory or somewhere else outside of the install/startup directory. It should be possible to keep profiles when updating to a new version.
Regarding image input, I don't remember if there is already a mechanism, there is probably a way, it might need a powershell script. Create a ticket if you like.
Patman
18th October 2019, 08:55
Another option to insert images in video files, the Attachments tab in container options:
https://i.imgur.com/WqnGXbX.png
Atlantis
18th October 2019, 16:41
FFT3DFilter has a newer version than what is in the Staxrip package.
If possible please update.
FFT3DFilter v2.6
https://github.com/pinterf/fft3dfilter/releases
Mixer73
19th October 2019, 00:19
EDIT: Fixed with current beta.
Natty
19th October 2019, 01:46
Another option to insert images in video files, the Attachments tab in container options:
https://i.imgur.com/WqnGXbX.png
your latest x265 3.2.8 is actually 3.2.6. :p
TomSmith
19th October 2019, 06:14
While trying out my new System (Ryzen 3700X, RT5700) I'm fighting with this error using x265
x265 [info]: HEVC encoder version 3.2+5-gfbe9fef31
x265 [info]: build info [Windows][GCC 9.2.0][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [info]: Main 10 profile, Level-5 (Main tier)
x265 [info]: Thread pool created using 16 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 4 / wpp(26 rows)
x265 [warning]: NAL HRD parameters require VBV parameters, ignored
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 3
x265 [info]: Keyframe min / max / scenecut / bias: 23 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 3 / off / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-15.0 / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 early-skip rskip signhide tmvp b-intra
x265 [info]: tools: strong-intra-smoothing lslices=8 deblock sao
Error: fwrite() call failed when writing frame: 4909, plane: 0, errno: 32
Output 4928 frames in 701.24 seconds (7.03 fps)
Can someone translate this for me, please? Is it the encoder or do I have trouble with RAM etc.?
Kind regards,
Tom
Patman
19th October 2019, 06:55
your latest x265 3.2.8 is actually 3.2.6. :pThank you for the info. I'm going to fix it tonight. I don't know how that happened [emoji849]
Gesendet von meinem HMA-L09 mit Tapatalk
Patman
19th October 2019, 07:14
While trying out my new System (Ryzen 3700X, RT5700) I'm fighting with this error using x265
Can someone translate this for me, please? Is it the encoder or do I have trouble with RAM etc.?
Kind regards,
Tom
Hi Tom,
a full log is required to help you with your problem.
Gesendet von meinem HMA-L09 mit Tapatalk
TomSmith
19th October 2019, 10:40
Hi Tom,
a full log is required to help you with your problem.
Gesendet von meinem HMA-L09 mit Tapatalk
This is the log:
-------------------------- System Environment --------------------------
StaxRip : 2.0.4.10
Windows : Windows 10 Pro 1903
Language : German (Germany)
CPU : AMD Ryzen 7 3700X 8-Core Processor
GPU : AMD Radeon RX 5700
Resolution : 1920 x 1080
DPI : 96
------------------------ MediaInfo Source File ------------------------
E:\smile\smile.m2ts
General
ID : 0 (0x0)
Complete name : E:\smile\smile.m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 39.6 GiB
Duration : 2 h 35 min
Overall bit rate mode : Variable
Overall bit rate : 46.5 Mb/s
Maximum Overall bit rate : 109 Mb/s
Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile A compatible
Codec ID : 36
Duration : 2 h 35 min
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 285 cd/m2
Maximum Frame-Average Light Level : 63 cd/m2
Audio #1
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : DTS XLL
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Muxing mode : Stream extension
Codec ID : 130
Duration : 2 h 35 min
Bit rate mode : Variable
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossless
Language : English
Audio #2
ID : 4353 (0x1101)
Menu ID : 1 (0x1)
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : 130
Duration : 2 h 35 min
Bit rate mode : Constant
Bit rate : 768 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 670 MiB (2%)
Language : German
Text
ID : 4768 (0x12A0)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144
Language : German
-------------------- Process M2TS file using eac3to --------------------
"C:\Program Files (x86)\StaxRip2-x64\Apps\Audio\eac3to\eac3to.exe" E:\smile\smile.m2ts -progressnumbers
M2TS, 1 video track, 2 audio tracks, 1 subtitle track, 2:35:28, 11.988p
1: h265/HEVC, 2160p24 /1.001 (16:9), 10 bits
2: DTS Master Audio, English, 2.0 channels, 24 bits, 48kHz
(core: DTS, 2.0 channels, 1509kbps, 48kHz)
3: DTS, German, 5.1 channels, 768kbps, 48kHz
4: Subtitle (PGS), German
--------------------- Demux M2TS using eac3to 3.34 ---------------------
"C:\Program Files (x86)\StaxRip2-x64\Apps\Audio\eac3to\eac3to.exe" E:\smile\smile.m2ts 2: "T:\temp\StaxRip\smile_temp\smile ID2 English.dts" -core 3: "T:\temp\StaxRip\smile_temp\smile ID3 German.dts" 4: "T:\temp\StaxRip\smile_temp\smile ID4 German.sup" -progressnumbers
M2TS, 1 video track, 2 audio tracks, 1 subtitle track, 2:35:28, 11.988p
1: h265/HEVC, 2160p24 /1.001 (16:9), 10 bits
2: DTS Master Audio, English, 2.0 channels, 24 bits, 48kHz
(core: DTS, 2.0 channels, 1509kbps, 48kHz)
3: DTS, German, 5.1 channels, 768kbps, 48kHz
4: Subtitle (PGS), German
s04 Extracting subtitle track number 4...
a02 Extracting audio track number 2...
a02 Extracting DTS core...
a03 Extracting audio track number 3...
a02 Creating file "T:\temp\StaxRip\smile_temp\smile ID2 English.dts"...
a03 Creating file "T:\temp\StaxRip\smile_temp\smile ID3 German.dts"...
s04 Creating file "T:\temp\StaxRip\smile_temp\smile ID4 German.sup"...
a02 Audio overlaps for 46ms at playtime 0:00:36.
a02 Audio overlaps for 93ms at playtime 1:56:27.
a02 Audio overlaps for 47ms at playtime 1:58:29.
a03 Audio overlaps for 46ms at playtime 0:00:36.
a03 Audio overlaps for 93ms at playtime 1:56:27.
a03 Audio overlaps for 47ms at playtime 1:58:29.
a02 Starting 2nd pass...
a02 Realizing DTS gaps...
a02 Creating file "T:\temp\StaxRip\smile_temp\smile ID2 English.dts"...
a03 Starting 2nd pass...
a03 Realizing DTS gaps...
a03 Creating file "T:\temp\StaxRip\smile_temp\smile ID3 German.dts"...
Video track 1 contains 175419 frames.
Subtitle track 4 contains 1242 captions.
eac3to processing took 2 minutes, 3 seconds.
Done.
Start: 08:52:29
End: 08:54:34
Duration: 00:02:05
-------------------------- VapourSynth Script --------------------------
import os, sys
import vapoursynth as vs
core = vs.get_core()
sys.path.append(r'C:\Program Files (x86)\StaxRip2-x64\Apps\Plugins\VS\Scripts')
core.std.LoadPlugin(r"C:\Program Files (x86)\StaxRip2-x64\Apps\Plugins\both\L-SMASH-Works\LSMASHSource.dll")
clip = core.lsmas.LWLibavSource(r"E:\smile\smile.m2ts")
clip = core.std.Crop(clip, 0, 0, 276, 276)
clip.set_output()
-------------------------- Script Properties --------------------------
Source Frame Count : 175440
Source Frame Rate : 23.976024
Source Duration : 02:35:28.4900000
Target Frame Count : 175440
Target Frame Rate : 23.976024
Target Duration : 02:35:28.4900000
----------------------- MediaInfo Audio Source 1 -----------------------
General
Complete name : T:\temp\StaxRip\smile_temp\smile ID3 German.dts
Format : DTS
Format/Info : Digital Theater Systems
File size : 670 MiB
Duration : 2 h 35 min
Overall bit rate mode : Constant
Overall bit rate : 768 kb/s
Audio
Format : DTS
Format/Info : Digital Theater Systems
Duration : 2 h 35 min
Bit rate mode : Constant
Bit rate : 768 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 670 MiB (100%)
----------------------- MediaInfo Audio Source 2 -----------------------
General
Complete name : T:\temp\StaxRip\smile_temp\smile ID2 English.dts
Format : DTS
Format/Info : Digital Theater Systems
File size : 1.29 GiB
Duration : 2 h 35 min
Overall bit rate mode : Constant
Overall bit rate : 1 509 kb/s
Audio
Format : DTS
Format/Info : Digital Theater Systems
Duration : 2 h 35 min
Bit rate mode : Constant
Bit rate : 1 509 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 1.29 GiB (100%)
------- Error Video encoding using x265 3.2+5-gfbe9fef31 Patman -------
Video encoding using x265 3.2+5-gfbe9fef31 Patman failed with exit code: -1073741819 (0xC0000005)
The exit code might be a system error code: Die Anweisung in 0xp verwies auf Arbeitsspeicher bei 0xp. Der Vorgang s konnte im Arbeitsspeicher nicht durchgeführt werden.
---------- Video encoding using x265 3.2+5-gfbe9fef31 Patman ----------
"C:\Program Files\VapourSynth\core\vspipe.exe" "T:\temp\StaxRip\smile_temp\smile-x265-nogpu.vpy" - --y4m | "C:\Program Files (x86)\StaxRip2-x64\Apps\Encoders\x265\x265.exe" --crf 15 --output-depth 10 --aq-mode 3 --me umh --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "285,63" --hdr --repeat-headers --hrd --aud --frames 175440 --y4m --output "T:\temp\StaxRip\smile_temp\smile-x265-nogpu_out.hevc" -
y4m [info]: 3840x1608 fps 24000/1001 i420p10 unknown frame count
raw [info]: output file: T:\temp\StaxRip\smile_temp\smile-x265-nogpu_out.hevc
x265 [info]: HEVC encoder version 3.2+5-gfbe9fef31
x265 [info]: build info [Windows][GCC 9.2.0][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [info]: Main 10 profile, Level-5 (Main tier)
x265 [info]: Thread pool created using 16 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 4 / wpp(26 rows)
x265 [warning]: NAL HRD parameters require VBV parameters, ignored
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : umh / 57 / 2 / 3
x265 [info]: Keyframe min / max / scenecut / bias: 23 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 3 / off / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 3 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-15.0 / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 early-skip rskip signhide tmvp b-intra
x265 [info]: tools: strong-intra-smoothing lslices=8 deblock sao
Error: fwrite() call failed when writing frame: 8019, plane: 0, errno: 32
Output 8036 frames in 1600.10 seconds (5.02 fps)
---------- Video encoding using x265 3.2+5-gfbe9fef31 Patman ----------
"C:\Program Files\VapourSynth\core\vspipe.exe" "T:\temp\StaxRip\smile_temp\smile-x265-nogpu.vpy" - --y4m | "C:\Program Files (x86)\StaxRip2-x64\Apps\Encoders\x265\x265.exe" --crf 15 --output-depth 10 --aq-mode 3 --me umh --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "285,63" --hdr --repeat-headers --hrd --aud --frames 175440 --y4m --output "T:\temp\StaxRip\smile_temp\smile-x265-nogpu_out.hevc" -
y4m [info]: 3840x1608 fps 24000/1001 i420p10 unknown frame count
raw [info]: output file: T:\temp\StaxRip\smile_temp\smile-x265-nogpu_out.hevc
x265 [info]: HEVC encoder version 3.2+5-gfbe9fef31
x265 [info]: build info [Windows][GCC 9.2.0][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [info]: Main 10 profile, Level-5 (Main tier)
x265 [info]: Thread pool created using 16 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 4 / wpp(26 rows)
x265 [warning]: NAL HRD parameters require VBV parameters, ignored
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : umh / 57 / 2 / 3
x265 [info]: Keyframe min / max / scenecut / bias: 23 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 3 / off / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 3 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-15.0 / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 early-skip rskip signhide tmvp b-intra
x265 [info]: tools: strong-intra-smoothing lslices=8 deblock sao
Error: fwrite() call failed when writing frame: 8019, plane: 0, errno: 32
Output 8036 frames in 1600.10 seconds (5.02 fps)
Start: 10:49:22
End: 11:16:02
Duration: 00:26:40
Interesting... there is this
------- Error Video encoding using x265 3.2+5-gfbe9fef31 Patman -------
Video encoding using x265 3.2+5-gfbe9fef31 Patman failed with exit code: -1073741819 (0xC0000005)
The exit code might be a system error code: Die Anweisung in 0xp verwies auf Arbeitsspeicher bei 0xp. Der Vorgang s konnte im Arbeitsspeicher nicht durchgeführt werden.
I do hope it gives the needed informations. I'm thankful for every hint!!
Patman
19th October 2019, 22:06
This is the log:
Interesting... there is this
------- Error Video encoding using x265 3.2+5-gfbe9fef31 Patman -------
Video encoding using x265 3.2+5-gfbe9fef31 Patman failed with exit code: -1073741819 (0xC0000005)
The exit code might be a system error code: Die Anweisung in 0xp verwies auf Arbeitsspeicher bei 0xp. Der Vorgang s konnte im Arbeitsspeicher nicht durchgeführt werden.
I do hope it gives the needed informations. I'm thankful for every hint!!
Hi Tom,
i've done an encode with nearly the same setting as yours.
"C:\Program Files (x86)\VapourSynth\core\vspipe.exe" E:\x264\test\00009_temp\00009.vpy - --y4m | F:\VideoProgz\Staxripx64\Apps\Encoders\x265\x265.exe --crf 15 --output-depth 10 --aq-mode 3 --me umh --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "285,63" --hdr --repeat-headers --hrd --aud --frames 175440 --y4m --output E:\x264\test\00009_temp\00009_out.hevc -
y4m [info]: 1920x1080 fps 24000/1001 i420p8 unknown frame count
raw [info]: output file: E:\x264\test\00009_temp\00009_out.hevc
x265 [info]: HEVC encoder version 3.2+8-7fc1f6ef2b96
x265 [info]: build info [Windows][GCC 9.2.0][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [info]: Main 10 profile, Level-4 (Main tier)
x265 [info]: Thread pool created using 8 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 3 / wpp(17 rows)
x265 [warning]: NAL HRD parameters require VBV parameters, ignored
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : umh / 57 / 2 / 3
x265 [info]: Keyframe min / max / scenecut / bias: 23 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 3 / off / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 3 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-15.0 / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 early-skip rskip signhide tmvp b-intra
x265 [info]: tools: strong-intra-smoothing lslices=6 deblock sao
Output 2184 frames in 289.56 seconds (7.54 fps)
x265 [info]: frame I: 53, Avg QP:11.73 kb/s: 45306.42
x265 [info]: frame P: 693, Avg QP:13.39 kb/s: 19557.51
x265 [info]: frame B: 1438, Avg QP:17.73 kb/s: 4051.85
x265 [info]: Weighted P-Frames: Y:15.7% UV:10.7%
x265 [info]: consecutive B-frames: 24.0% 13.7% 18.1% 34.0% 10.2%
encoded 2184 frames in 290.35s (7.52 fps), 9973.06 kb/s, Avg QP:16.21
Start: 21:33:23
End: 21:38:14
Duration: 00:04:50
As indexer i've used ffms, because L-Smash causes me some problems. I'm already looking for a solution. Try to reinstall Python (https://www.python.org/ftp/python/3.7.5/python-3.7.5-amd64-webinstall.exe) and Vapoursynth (https://github.com/vapoursynth/vapoursynth/releases/download/R48-RC1/VapourSynth64-R48-RC1.exe) and then try again.
Patman
19th October 2019, 22:06
your latest x265 3.2.8 is actually 3.2.6. :p
Updated :D
stax76
19th October 2019, 22:33
@TomSmith
In error in the middle of an encoding could be a hardware issue, an issue with the source or with the source filter, that are the most likely causes, I've not seen this happening before.
I googled for "fwrite() call failed when writing frame" and found that other staxrip had this error using VapourSynth before but I did not really understand what was the cause, can be found here:
https://forum.videohelp.com/threads/392480-Easy-way-to-encode-vpy-scripts
Patman
19th October 2019, 22:35
FFT3DFilter has a newer version than what is in the Staxrip package.
If possible please update.
FFT3DFilter v2.6
https://github.com/pinterf/fft3dfilter/releases
This version is included in the latest beta of staxrip.
TomSmith
20th October 2019, 04:43
Hi Tom,
i've done an encode with nearly the same setting as yours.
As indexer i've used ffms, because L-Smash causes me some problems. I'm already looking for a solution. Try to reinstall Python (https://www.python.org/ftp/python/3.7.5/python-3.7.5-amd64-webinstall.exe) and Vapoursynth (https://github.com/vapoursynth/vapoursynth/releases/download/R48-RC1/VapourSynth64-R48-RC1.exe) and then try again.
@TomSmith
In error in the middle of an encoding could be a hardware issue, an issue with the source or with the source filter, that are the most likely causes, I've not seen this happening before.
I googled for "fwrite() call failed when writing frame" and found that other staxrip had this error using VapourSynth before but I did not really understand what was the cause, can be found here:
https://forum.videohelp.com/threads/392480-Easy-way-to-encode-vpy-scripts
Hi,
I installed Python and Vapoursynth (R48-RC1) again and will try it again asap (using ffms2).
I tested my RAM using memtest86 also but no errors. RAM seems to be OK. It is also listed in the compatibility-list of the motherboard.
Thank you for your help!
Bahamuth
20th October 2019, 18:02
@Bahamuth
That would be a bug, I will examine it if you create a ticket on the tracker. In your startup template I assume that your filter setup is vapoursynth and not avisynth?
I'm honest, it might have been my error. I never used VapourSynth before so I didn't even knew, there is this "Filter Setup" setting if you right click on the filters.
In my defense, I didn't find "filter setup" at the Docs from https://staxrip2.readthedocs.io/en/latest/index.html when searching for it after reading your post.
Bahamuth
20th October 2019, 20:01
Is it normal that vspipe.exe uses 45% CPU usage?
edit: it did so on a DVD movie (with deinterlace). on a progressive BluRay movie vspipe.exe stays low it seems
sneaker_ger
20th October 2019, 20:57
The vspipe CPU usage includes the VapourSynth filter usage. So with complex filters vspipe usage will be high.
Natty
21st October 2019, 01:51
Updated :D
works fine. :thanks: update custom ver too sometimes if you find it useful and have some free time. there are a few useful ones which others implement. eg keeping rc=crf in beginning of encoding settings.
TomSmith
21st October 2019, 16:35
Hi,
I installed Python and Vapoursynth (R48-RC1) again and will try it again asap (using ffms2).
I tested my RAM using memtest86 also but no errors. RAM seems to be OK. It is also listed in the compatibility-list of the motherboard.
Thank you for your help!
I 'reinstalled' Staxrip as well to have a clean version and changed the indexer.
It is the same error:
------- Error Video encoding using x265 3.2+5-gfbe9fef31 Patman -------
Video encoding using x265 3.2+5-gfbe9fef31 Patman failed with exit code: -1073741819 (0xC0000005)
The exit code might be a system error code: Die Anweisung in 0xp verwies auf Arbeitsspeicher bei 0xp. Der Vorgang s konnte im Arbeitsspeicher nicht durchgeführt werden.
---------- Video encoding using x265 3.2+5-gfbe9fef31 Patman ----------
"C:\Program Files (x86)\StaxRip-x64-2\Apps\Support\avs2pipemod\avs2pipemod64.exe" -y4mp T:\temp\StaxRip\smile2_temp\smile2.avs | "C:\Program Files (x86)\StaxRip-x64-2\Apps\Encoders\x265\x265.exe" --crf 13 --output-depth 10 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --hdr --repeat-headers --hrd --aud --frames 197674 --y4m --output T:\temp\StaxRip\smile2_temp\smile2_out.hevc -
avs2pipemod[info]: writing 197674 frames of 24000/1001 fps, 3840x1608,
sar 0:0, YUV-420-planar-10bit progressive video.
y4m [info]: 3840x1608 fps 24000/1001 i420p10 unknown frame count
raw [info]: output file: T:\temp\StaxRip\smile2_temp\smile2_out.hevc
x265 [info]: HEVC encoder version 3.2+5-gfbe9fef31
x265 [info]: build info [Windows][GCC 9.2.0][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [info]: Main 10 profile, Level-5 (Main tier)
x265 [info]: Thread pool created using 16 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 4 / wpp(26 rows)
x265 [warning]: NAL HRD parameters require VBV parameters, ignored
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 3
x265 [info]: Keyframe min / max / scenecut / bias: 23 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 3 / off / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-13.0 / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 early-skip rskip signhide tmvp b-intra
x265 [info]: tools: strong-intra-smoothing lslices=8 deblock sao
avs2pipemod[info]: finished, wrote 30524 frames [15%].
avs2pipemod[info]: total elapsed time is 4999.736 sec.
avs2pipemod[error]: only wrote 30524 of 197674 frames.
---------- Video encoding using x265 3.2+5-gfbe9fef31 Patman ----------
"C:\Program Files (x86)\StaxRip-x64-2\Apps\Support\avs2pipemod\avs2pipemod64.exe" -y4mp T:\temp\StaxRip\smile2_temp\smile2.avs | "C:\Program Files (x86)\StaxRip-x64-2\Apps\Encoders\x265\x265.exe" --crf 13 --output-depth 10 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --hdr --repeat-headers --hrd --aud --frames 197674 --y4m --output T:\temp\StaxRip\smile2_temp\smile2_out.hevc -
avs2pipemod[info]: writing 197674 frames of 24000/1001 fps, 3840x1608,
sar 0:0, YUV-420-planar-10bit progressive video.
y4m [info]: 3840x1608 fps 24000/1001 i420p10 unknown frame count
raw [info]: output file: T:\temp\StaxRip\smile2_temp\smile2_out.hevc
x265 [info]: HEVC encoder version 3.2+5-gfbe9fef31
x265 [info]: build info [Windows][GCC 9.2.0][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [info]: Main 10 profile, Level-5 (Main tier)
x265 [info]: Thread pool created using 16 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 4 / wpp(26 rows)
x265 [warning]: NAL HRD parameters require VBV parameters, ignored
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 3
x265 [info]: Keyframe min / max / scenecut / bias: 23 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 3 / off / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-13.0 / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 early-skip rskip signhide tmvp b-intra
x265 [info]: tools: strong-intra-smoothing lslices=8 deblock sao
avs2pipemod[info]: finished, wrote 30524 frames [15%].
avs2pipemod[info]: total elapsed time is 4999.736 sec.
avs2pipemod[error]: only wrote 30524 of 197674 frames.
Atlantis
21st October 2019, 16:59
AviSynth+ 3.4.0 is released.
https://github.com/AviSynth/AviSynthPlus/releases
stax76
21st October 2019, 19:01
------- Error Video encoding using x265 3.2+5-gfbe9fef31 Patman -------
Video encoding using x265 3.2+5-gfbe9fef31 Patman failed with exit code: -1073741819 (0xC0000005)
The exit code might be a system error code: Die Anweisung in 0xp verwies auf Arbeitsspeicher bei 0xp. Der Vorgang s konnte im Arbeitsspeicher nicht durchgeführt werden.
Maybe try an alternative way to narrow the cause, in staxrip there are always at least two ways:
AviSynth
VapourSynth
x264
x265
ffms2
l-smash
avs2pipemod
ffmpeg
etc.
AviSynth+ 3.4.0 is released.
https://github.com/AviSynth/AviSynthPlus/releases
I've bookmarked it, thanks.
Patman
21st October 2019, 19:21
I 'reinstalled' Staxrip as well to have a clean version and changed the indexer.
It is the same error:
------- Error Video encoding using x265 3.2+5-gfbe9fef31 Patman -------
Video encoding using x265 3.2+5-gfbe9fef31 Patman failed with exit code: -1073741819 (0xC0000005)
The exit code might be a system error code: Die Anweisung in 0xp verwies auf Arbeitsspeicher bei 0xp. Der Vorgang s konnte im Arbeitsspeicher nicht durchgeführt werden.
Hi Tom,
can you pls share a sample of your file with me? Send me pm and I will test your file with your settings.
Gesendet von meinem HMA-L09 mit Tapatalk
Patman
21st October 2019, 19:29
works fine. :thanks: update custom ver too sometimes if you find it useful and have some free time. there are a few useful ones which others implement. eg keeping rc=crf in beginning of encoding settings.I'm also updating the custom version of x265. I will look at further adjustments and, if useful, integrate them.
Gesendet von meinem HMA-L09 mit Tapatalk
Exaris
22nd October 2019, 02:18
What are the differences between the included x265 and the Stable Branch VS2019 AVX2 releases from http://msystem.waw.pl/x265/ ?
Patman
22nd October 2019, 16:48
What are the differences between the included x265 and the Stable Branch VS2019 AVX2 releases from http://msystem.waw.pl/x265/ ?The included x265 is compiled with gcc 9.2.0 and not with visual studio. An other difference is that the included x265 is packed with upx, what results in smaller filesize. And the included version based on master branch, not on stable branch.
stable branch:
x265 [info]: HEVC encoder version 3.2+5-a3a088a7262f
x265 [info]: build info [Windows][MSVC 1923][64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
master branch:
x265 [info]: HEVC encoder version 3.2+5-gfbe9fef31
x265 [info]: build info [Windows][GCC 9.2.0][64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
TomSmith
22nd October 2019, 18:45
Maybe try an alternative way to narrow the cause, in staxrip there are always at least two ways:
AviSynth
VapourSynth
x264
x265
ffms2
l-smash
avs2pipemod
ffmpeg
etc.
I've bookmarked it, thanks.
I've used x264 and x265, avisynth and vapoursynth etc. it's always the same error... Sometimes x264 avisynth is successful but I woult like to use x265...
stax76
22nd October 2019, 18:56
I've used x264 and x265, avisynth and vapoursynth etc. it's always the same error... Sometimes x264 avisynth is successful but I woult like to use x265...
Maybe try another source file and another source filter, by default staxrip uses the filter FFVideoSource which belongs to the ffms2 plugin, except for MP4 where LSMASHVideoSource is the default, that belongs to the l-smash plugin. You can try LWLibavVideoSource as alternative to FFVideoSource. There are multiple ways to do this, for instance before you open a source file, right-click the source filter and then select the filter you want, after that you can open the source file. If that works better you might want to make this filter the default, in that case just ask how to do this. If it's reproducible with a certain file then please upload that file.
videoh
23rd October 2019, 13:56
I've used x264 and x265, avisynth and vapoursynth etc. it's always the same error... Sometimes x264 avisynth is successful but I woult like to use x265... Definitely sounds like a hardware issue, especially if it happens with other source filters as well. Have you looked into that?
IbrahimKh
24th October 2019, 13:40
Hi, any idea how do I can convert this type of video (VBR) into CBR?
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 22 min 35 s
Width : 1 424 pixels
Height : 1 080 pixels
Display aspect ratio : 4:3
Frame rate mode : Variable
Original frame rate : 23.976 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
I indexed the video but the result was like this (using ffmsindex)
https://i.postimg.cc/Ssq2btY2/screenshot-210.png (https://postimages.org/)
what filter I should use to get proper output?
Patman
24th October 2019, 16:09
Hi, any idea how do I can convert this type of video (VBR) into CBR?
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 22 min 35 s
Width : 1 424 pixels
Height : 1 080 pixels
Display aspect ratio : 4:3
Frame rate mode : Variable
Original frame rate : 23.976 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
I indexed the video but the result was like this (using ffmsindex)
https://i.postimg.cc/Ssq2btY2/screenshot-210.png (https://postimages.org/)
what filter I should use to get proper output?
Test this (http://forum.doom9.org/showthread.php?p=1886890) ffms2 version. If result is still same, right-click into filter-window and add -> FrameRate -> AssumeFPS -> AssumeFPS and select FrameRate 24000/1001.
TomSmith
25th October 2019, 15:16
Hi Tom,
can you pls share a sample of your file with me? Send me pm and I will test your file with your settings.
Gesendet von meinem HMA-L09 mit Tapatalk
Maybe try another source file and another source filter, by default staxrip uses the filter FFVideoSource which belongs to the ffms2 plugin, except for MP4 where LSMASHVideoSource is the default, that belongs to the l-smash plugin. You can try LWLibavVideoSource as alternative to FFVideoSource. There are multiple ways to do this, for instance before you open a source file, right-click the source filter and then select the filter you want, after that you can open the source file. If that works better you might want to make this filter the default, in that case just ask how to do this. If it's reproducible with a certain file then please upload that file.
Hi Patman!
Hi stax76!
I've done some testing and I get this error with different files and encoders - even at different frames with the same file/encoder.
As I'm the only one with this problem at the moment, I guess it is the x570 Chipset driver or motherboard bios that needs some improvement. Waiting for the next version to test it again. The RAM is good (memtest86 - no errors).
Thank you very much for your help!
Tom
Patman
25th October 2019, 21:13
Hi Patman!
Hi stax76!
I've done some testing and I get this error with different files and encoders - even at different frames with the same file/encoder.
As I'm the only one with this problem at the moment, I guess it is the x570 Chipset driver or motherboard bios that needs some improvement. Waiting for the next version to test it again. The RAM is good (memtest86 - no errors).
Thank you very much for your help!
TomHi Tom,
I plan to update my system (cpu: ryzen7 3800x, gigabyte x570 elite, g.skill trident z 32gb for AMD) which mainboard you use?
Gesendet von meinem HMA-L09 mit Tapatalk
Exaris
26th October 2019, 06:42
From there being no commits since October 16th I assume the next stable build is being prepared, is this correct?
TomSmith
26th October 2019, 09:53
Hi Tom,
I plan to update my system (cpu: ryzen7 3800x, gigabyte x570 elite, g.skill trident z 32gb for AMD) which mainboard you use?
Gesendet von meinem HMA-L09 mit Tapatalk
I use an Asus ROG STRIX X570 F-Gaming at the moment. My RAM is g.skill trident z neo 16GB.
I started with an Aorus x470 at first but after updating the firmware (Ryzen 3000 support was missing) and setting up Win10 all of a sudden the mainboard showed an error '7' which wasn't mentioned in the manual. I decided to go for a 'cheap' x570 board that fill my needs and ended up with this Asus.
Patman
26th October 2019, 11:46
I use an Asus ROG STRIX X570 F-Gaming at the moment. My RAM is g.skill trident z neo 16GB.
I started with an Aorus x470 at first but after updating the firmware (Ryzen 3000 support was missing) and setting up Win10 all of a sudden the mainboard showed an error '7' which wasn't mentioned in the manual. I decided to go for a 'cheap' x570 board that fill my needs and ended up with this Asus.Thanks for the info. After updating my system, i'll give you a feedback.
Gesendet von meinem HMA-L09 mit Tapatalk
Atlantis
27th October 2019, 00:06
Question, where are the Profiles saved? In Settings.dat, in Templates...?
Patman
27th October 2019, 12:42
Question, where are the Profiles saved? In Settings.dat, in Templates...?
Profiles are saved in the folder templates.
Atlantis
27th October 2019, 13:25
Profiles are saved in the folder templates.
This does not seem to be true. I see only templates in that folder and when I open any old template, my new commands in Profiles still show up.
Profiles are under AVS Filters and you can add extra stuff. It starts with
[Source]
Automatic = # can be configured at: Tools > Settings > Source Filters
AviSource = AviSource("%source_file%", Audio = False)
DGSource = DGSource("%source_file%")
DGSourceIM = DGSourceIM("%source_file%")
.................
Patman
27th October 2019, 15:17
This does not seem to be true. I see only templates in that folder and when I open any old template, my new commands in Profiles still show up.
Profiles are under AVS Filters and you can add extra stuff. It starts with
[Source]
Automatic = # can be configured at: Tools > Settings > Source Filters
AviSource = AviSource("%source_file%", Audio = False)
DGSource = DGSource("%source_file%")
DGSourceIM = DGSourceIM("%source_file%")
.................
Ah ok,
you mean filter profiles, these are stored in settings.dat. I thought you mean encoder profiles.
chipxtreme
31st October 2019, 18:54
NVEnc 4.53 is out
JKyle
1st November 2019, 00:27
VapourSynth R48 is released today.
chipxtreme
2nd November 2019, 11:30
NVEnc 4.54 is out
Forteen88
2nd November 2019, 13:38
I used StaxRip-x64-2.0.4.0-stable, and even though I set SAR 1:1 (for Blu-ray source), the encode still said "sar=0" in MediaInfo, it should be set to "sar=1".
-QfG-
2nd November 2019, 14:20
I used StaxRip-x64-2.0.4.0-stable, and even though I set SAR 1:1 (for Blu-ray source), the encode still said "sar=0" in MediaInfo, it should be set to "sar=1".
Using u the Custom Line?
Forteen88
2nd November 2019, 14:38
Using u the Custom Line?Nope, but I still think that when a user sets SAR 1:1 in the StaxRip-GUI, it should be set to that in the encode. StaxRip doesn't even change the encode-line to --sar 1 when I switch setting in the GUI from SAR 0 to SAR 1:1.
I might as well use x264/x265-launcher if I can't trust StaxRip's GUI and have to put settings in StaxRip's custom-line.
stax76
2nd November 2019, 16:16
I don't see how this is a real problem, 0 probably stands for undefined which should effectively be identical to 1. The concept of undefined/nothing/null/whatever often makes the world more complex than it needs to be, staxrip is here to simplify things.
edit:
to force writing the PAR it's possible to add a custom command:
--sar %target_par_x%:%target_par_y%
This is relative new so might require using the last beta.
stax76
3rd November 2019, 23:28
I've uploaded a new beta build and hope that a stable release can be made soon. Please test it. :thanks:
2.0.5.1 Beta
------------
- update: DGHDRtoSDR 1.13
- update: NVEncC 4.54
- update: VapourSynth R48
- update: x265 3.2+9-971180b100f8 Patman
- new: various UI improvements
- new: the short version of x265 and nvenc switches like -c, -f etc.
were integrated into the search field and command line import
feature, the search feature now first looks for a exact match
- new: x265 switches --dup-threshold, --frame-dup
- new: nvenc switches --multiref-l0, --multiref-l1
- new: StaxRip can use MediaInfo.NET instead of the built-in MediaInfo GUI,
it requires MediaInfo.NET to be installed and started at least once
- fix: FFTW not always asked to be installed when needed
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR
https://github.com/stax76/MediaInfo.NET
jlw_4049
3rd November 2019, 23:46
I've uploaded a new beta build and hope that a stable release can be made soon. Please test it. :thanks:
2.0.5.1 Beta
------------
- update: DGHDRtoSDR 1.13
- update: NVEncC 4.54
- update: VapourSynth R48
- update: x265 3.2+9-971180b100f8 Patman
- new: various UI improvements
- new: the short version of x265 and nvenc switches like -c, -f etc.
were integrated into the search field and command line import
feature, the search feature now first looks for a exact match
- new: x265 switches --dup-threshold, --frame-dup
- new: nvenc switches --multiref-l0, --multiref-l1
- new: StaxRip can use MediaInfo.NET instead of the built-in MediaInfo GUI,
it requires MediaInfo.NET to be installed and started at least once
- fix: FFTW not always asked to be installed when needed
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR
https://github.com/stax76/MediaInfo.NETAwesome I might give it a whirl here tonight.
Sent from my SM-G965U1 using Tapatalk
Bahamuth
5th November 2019, 01:44
hmm when using the default field "QTGMC Medium", the frame rate of each input file is doubled. if I replace it with "QTGMC with Repair" it shows the correct FPS.
Now I wonder if I made a mistake or if I should choose another field for interlaced mpeg streams anyway.
Even stranger is, that when using IVTC, the fps changes from e.g. 25 to 20 (I just replaced the field with various entries to see which ones keep 25fps).
Also interesting, if I preview filter code, it shows me a line with "#clip = core.std.AssumeFPS(clip, None, 25, 1)"
And another thing after I encoded a 25FPS video:
Video: MPEG4 Video (H264) 720x576 (349:192) 50fps 1611kbps [V: h264#video@GPAC0.7.2-DEV-rev1009-g8b9f06546-ab-suite (h264 high L3.1, yuv420p, 720x576, 1611 kb/s)]
But when I play the file, playback speed is normal and all.
stax76
5th November 2019, 01:58
There was a thread about it:
https://forum.doom9.org/showthread.php?t=176960
Z'Hadum
5th November 2019, 14:15
I've uploaded a new beta build and hope that a stable release can be made soon. Please test it. :thanks:
2.0.5.1 Beta
------------
Many Thy for your awesome work.
One small notice:
For HDR Material the "Mastering display luminance" seems not to be set correct:
In the VUI Panel under Master Display it is always set to L(10000000,1) regardless what I can find in Mediainfo.
Can you fix this?
:thanks:
stax76
5th November 2019, 14:37
I just wanted to upload the stable release. :)
Code was written by Revan, I hope he will comment on it, otherwise I can try to understand it, for that a sample, or at least mediainfo would help.
chipxtreme
5th November 2019, 21:45
NVEnc 4.55 is out.
Bahamuth
5th November 2019, 23:22
I'm having a Ryzen 3900x now and I wonder, why x264 more often uses only around 33% of my CPU threads. Is this a good thing or not? I use always the preset slower. Or did I miss some kind of setting for the amount of cores available for the programs run from Staxrip?
Atak_Snajpera
5th November 2019, 23:30
I'm having a Ryzen 3900x now and I wonder, why x264 more often uses only around 33% of my CPU threads. Is this a good thing or not? I use always the preset slower. Or did I miss some kind of setting for the amount of cores available for the programs run from Staxrip?
Show us your script. While encoding run process hacker and show CPU usage for all processes spawned by staxrip.
Bahamuth
5th November 2019, 23:52
I guess you mean the Vapoursynth-Script?
import os
import sys
ScriptPath = 'C:/apps/video/StaxRip2/Apps/Plugins/VS/Scripts'
sys.path.append(os.path.abspath(ScriptPath))
import vapoursynth as vs
core = vs.get_core()
import importlib.machinery
mvsfunc = importlib.machinery.SourceFileLoader('mvsfunc', r"C:\apps\video\StaxRip2\Apps\Plugins\VS\Scripts\mvsfunc.py").load_module()
adjust = importlib.machinery.SourceFileLoader('adjust', r"C:\apps\video\StaxRip2\Apps\Plugins\VS\Scripts\adjust.py").load_module()
havsfunc = importlib.machinery.SourceFileLoader('havsfunc', r"C:\apps\video\StaxRip2\Apps\Plugins\VS\Scripts\havsfunc.py").load_module()
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\Both\FFMS2\ffms2.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\AWarpSharp2\libawarpsharp2.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\CTMF\CTMF.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\DCTFilter\DCTFilter.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\Deblock\Deblock.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\DFTTest\DFTTest.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\EEDI2\EEDI2.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\EEDI3m\EEDI3m.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\FFT3DFilter\fft3dfilter.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\FluxSmooth\libfluxsmooth.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\fmtconv\fmtconv.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\HQDN3D\libhqdn3d.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\both\KNLMeansCL\KNLMeansCL.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\BM3D\BM3D.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\mvtools\libmvtools.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\nnedi3\libnnedi3.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\nnedi3\NNEDI3CL.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\Sangnom\libsangnom.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\scenechange\scenechange.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\SVPFlow\svpflow1_vs64.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\SVPFlow\svpflow2_vs64.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\TTempSmooth\TTempSmooth.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\nnedi3\vsznedi3.dll")
clip = core.ffms2.Source(r"V:\Aufnahmen\Mary und die Blume der Hexen.m2v", cachefile = r"V:\Aufnahmen\Mary und die Blume der Hexen_temp\Mary und die Blume der Hexen.ffindex")
#clip = core.std.AssumeFPS(clip, None, 25, 1)
clip = core.std.Crop(clip, 0, 0, 12, 12)
clip = core.std.SetFieldBased(clip, 2) # 1 = BFF, 2 = TFF
clip = havsfunc.QTGMC(clip, TFF = True, Preset = 'Medium')
clip.set_output()
And I hope you mean something like this for the processes:
https://i.imgur.com/qDoJeRI.png
It varies a bit, for the x264 between 30 and 50%. I understand, that the QTGMC filter will take a few percent, but x264 should use more of the still available CPU then I would have thought.
Running on Windows 10 Pro.
Input is a TV recording (reencoding it for smaller size)
Complete name : V:\Aufnahmen\Mary und die Blume der Hexen.m2v
Format : MPEG Video
Format version : Version 2
File size : 1.77 GiB
Duration : 1 h 33 min
Overall bit rate mode : Variable
Overall bit rate : 2 722 kb/s
Video
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings : CustomMatrix / BVOP
Format, BVOP : Yes
Format, Matrix : Custom
Format, GOP : M=3, N=12
Format, picture st : Frame
Duration : 1 h 33 min
Bit rate mode : Variable
Bit rate : 2 722 kb/s
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 16:9
Frame rate : 25.000 FPS
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.263
Time code of first frame : 00:00:00:00
GOP, Open/Closed : Open
GOP, Open/Closed of first f : Closed
Stream size : 1.77 GiB (100%)
Atak_Snajpera
5th November 2019, 23:58
Two problems. Too low resolution 576p and bottleneck caused by qmtc. In avisynth i use prefetch function to get proper CPU usage. No idea how this is solved in vapoursynth.
Z'Hadum
6th November 2019, 07:01
I just wanted to upload the stable release. :)
Code was written by Revan, I hope he will comment on it, otherwise I can try to understand it, for that a sample, or at least mediainfo would help.
It is really simple, I think:
Mediainfo (Bold the part I mean)
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2
Maximum Content Light Level : 1838 cd/m2
Maximum Frame-Average Light Level : 277 cd/m2
With this Informjation you get on
x265 Options-> VUI-Panel-> Master Display:
G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)
But it should be:
G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50) in this case.
The Luminance isn't set to the value from the file.
:thanks:
stax76
6th November 2019, 11:18
@Z'Hadum
I'll investigate it.
chipxtreme
6th November 2019, 14:13
MKVToolnix 39.0.0 Released.
Bahamuth
6th November 2019, 17:23
Two problems. Too low resolution 576p and bottleneck caused by qmtc. In avisynth i use prefetch function to get proper CPU usage. No idea how this is solved in vapoursynth.
Any other deinterlacer to recommend for interlaced TV recordings and DVD movies? The old StaxRip used TDeint as default, and x264 always had 100% CPU usage when I converted with the i3770 back then.
Atak_Snajpera
6th November 2019, 18:11
Any other deinterlacer to recommend for interlaced TV recordings and DVD movies? The old StaxRip used TDeint as default, and x264 always had 100% CPU usage when I converted with the i3770 back then.
QTGMC is fine but you have to enable multi-threading in vapoursynth. In AviSynth+ MT we have prefetch function. Like I said before I have zero knowledge about vapoursynth.
poisondeathray
6th November 2019, 18:34
multithreading is "automatic" in vapoursynth . You don't have to "guess" the correct prefetch value. It just works
Atak_Snajpera
6th November 2019, 18:48
multithreading is "automatic" in vapoursynth . You don't have to "guess" the correct prefetch value. It just works
No. It does not work. vspipe uses only ~20% of 24 threads in his 3900x. That's 5 cpu threads or 2.5 cpu cores.
https://i.imgur.com/qDoJeRI.png
I also took 720x576@25i source and with QTGMC (preset medium) + x264 (preset medium) on 16 thread CPU I get this with Prefetch(8)...
https://i.postimg.cc/PqgyFqb8/Untitled-2.png
See the difference now?
BTW. Correct prefetch value is just number of physical cores. That's it!
stax76
6th November 2019, 19:16
Thanks to everybody for testing and help with the updates. :thanks:
2.0.5.3 Beta
------------
- update: mkvtoolnix 39
- update: mpv.net 5.4.3
- update: NVEnc 4.55
- fix: few UI issues
- fix: avs MCTemporalDenoise/GradFun2DBmod
- fix: VUI luminance issue
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR
poisondeathray
6th November 2019, 19:26
See the difference now?
I suspect something is not working correctly on his setup, some other bottleneck
You don't have to "enable" multithreading in vapoursynth. It just works (or is supposed to).
With a single filter like QTGMC, avs+ is slightly faster, but once you add more filters, avs+ bogs down in speed . Threading is not as good as vapoursynth. Try it out.
BTW. Correct prefetch value is just number of physical cores. That's it!
Sometimes that's not the "ideal" value . Sometimes n+1 is faster, or n+2 . Sometimes it's virtual cores. It depends on the hardware and particular script, and encoding situation
Atak_Snajpera
6th November 2019, 19:43
Sometimes that's not the "ideal" value . Sometimes n+1 is faster, or n+2 . Sometimes it's virtual cores. It depends on the hardware and particular script, and encoding situation
Trust me. I have done many, many tests (QTGMC,MDegrain,HDR to SDR Tonemapping). Prefetch = cores is optimal. Anything above that causes choking effect in piping process (cpu usage drops significantly and then after a while goes up).
poisondeathray
6th November 2019, 19:50
Trust me. I have done many, many tests (QTGMC,MDegrain,HDR to SDR Tonemapping). Prefetch = cores is optimal. Anything above that causes choking effect in piping process (cpu usage drops significantly and then after a while goes up).
Perhaps on your particular HW setup
I measured actual FPS encoding speed and got different results on many tests. CPU usage was not always indictive of actual encoding speed on some scripts. Sometimes the induced thrashing would cause a lower actual FPS encoding speed, yet high CPU usage
Atak_Snajpera
6th November 2019, 20:09
Perhaps on your particular HW setup
I measured actual FPS encoding speed and got different results on many tests. CPU usage was not always indictive of actual encoding speed on some scripts. Sometimes the induced thrashing would cause a lower actual FPS encoding speed, yet high CPU usage
Tested on my Xeon E5-2690 and on Ryzen 1700. Both act in the same way. Choking effect above core count. Lower value means lower fps.
Patman
6th November 2019, 20:09
Thanks to everybody for testing and help with the updates. :thanks:
2.0.5.3 Beta
------------
- update: mkvtoolnix 39
- update: mpv.net 5.4.3
- update: NVEnc 4.55
- fix: few UI issues
- fix: avs MCTemporalDenoise/GradFun2DBmod
- fix: VUI luminance issue
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR
Thx for update,
VUI luminance works perfect now. Now focus on the implementation of the SVT-AV1 Encoder :D ;)
Patman
6th November 2019, 20:11
@ TomSmith
i've updated my system now and everything works like a charme. No problems with ram or other hardware issues.
@ all
updated some of my builds
poisondeathray
6th November 2019, 20:12
Tested on my Xeon E5-2690 and on Ryzen 1700. Both act in the same way. Choking effect above core count.
You could be right . I tested a long time ago, maybe something has changed .
In general, I found that higher prefetch="x" wasn't always better because of thrashing
But I found that different scripts had different "ideal" prefetch values for actual encoding speed (completion times)
The more filters, the faster the delta with vapoursynth
poisondeathray
6th November 2019, 20:39
You could be right . I tested a long time ago, maybe something has changed .
And nothing has changed, at least here for me
3 runs on a Haswell 4C/8T . Default QTGMC (slower), default libx264 (medium). PF6 was 3-5% faster each time , than PF4 . Only a 5min test clip, but long enough for the encoding speed to settle down
And when I add a bicubicresize(640,480) , PF6 is 8-11% faster than PF4.
I think YMMV, depending on your script , your HW setup.
Atak_Snajpera
6th November 2019, 21:07
BTW. Do you even need prefetch on such small numbers of cores? It would be funny if you got even higher fps without those extra AviSynth threads
Bahamuth
6th November 2019, 21:18
I just stumbled over this:
http://www.chaneru.com/Roku/HLS/X264_Settings.htm#threads
"Default: auto (frame based threads: 1.5 * logical processors, rounded down; slice based threads: 1 * logical processors)"
Could it be, that x264 is limiting itself? Should I tamper with this setting?
poisondeathray
6th November 2019, 21:19
BTW. Do you even need prefetch on such small numbers of cores? It would be funny if you got even higher fps without those extra AviSynth threads
Hahaha funny guy :D
Atak I believe what you're saying is true for your case your HW, and your scripts.
I've never seen a script or situation where "2" was worse speedwise than no prefetch (on a dual core at least, I guess) . It's just a bit of a pain to find the "ideal" prefetch value
Some people look at CPU usage, without measuring speed, it's a big mistake . Sometimes high CPU usage is thrashing, not "faster" processing or encoding
Atak_Snajpera
6th November 2019, 21:22
Some people look at CPU usage, without measuring speed, it's a big mistake
I look at fps reported by AVSMeter...
I just stumbled over this:
http://www.chaneru.com/Roku/HLS/X264...gs.htm#threads
"Default: auto (frame based threads: 1.5 * logical processors, rounded down; slice based threads: 1 * logical processors)"
Could it be, that x264 is limiting itself? Should I tamper with this setting?
vspipe is a problem (Does not send frames for encoder fast enough). For science run the same file in ripbot264 and show screenshot from process hacker just like before.
poisondeathray
6th November 2019, 21:23
I just stumbled over this:
http://www.chaneru.com/Roku/HLS/X264_Settings.htm#threads
"Default: auto (frame based threads: 1.5 * logical processors, rounded down; slice based threads: 1 * logical processors)"
Could it be, that x264 is limiting itself? Should I tamper with this setting?
It should be ok autodetected; You can manually set --threads if you want
Can you switch to avs+ in staxrip ? Worth a try .
Atak is right in that something is bottlenecking in your vpy setup.
poisondeathray
6th November 2019, 21:29
I look at fps reported by AVSMeter...
Useful tool Atak, but synthethic tests do not necessarily reflect actual encoding performance.
If you look at avsmeter, varying prefetc, sometimes a much higher CPU% results in only a marginally higher FPS with lots of threads . That's probably similar to the "choking" you're referring to or "thrashing" I'm referring to. CPU usage% and FPS do not always relate 1:1 . Thrashing could be a bottleneck for CPU encoder.
stax76
6th November 2019, 21:47
Can you switch to avs+ in staxrip ? Worth a try .
By design, you can change any setting at any time (Filters Menu > Filter Setup > AviSynth).
Bahamuth
6th November 2019, 22:11
With the old staxrip and avisynth (the setting I used with my old computer) x264 also does stay at around 40% of CPU usage.
With the Ripbot the encoding speed is around same (~140FPS) when setting preset slower. But CPU usage is again not fully utilized.
Please see image here (don't want to spam the thread) (https://i.imgur.com/ZNEhWPE.png)
Bahamuth
6th November 2019, 22:18
And with AviSynth+ it's not going really better: Image (https://i.imgur.com/C9rJC9m.png).
Contents of the AviSynth script:
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\Both\FFMS2\ffms2.dll")
FFVideoSource("C:\Users\Ezatoka\Desktop\Arpeggio of Blue Steel Ars Nova DC.m2v", colorspace = "YV12", \
cachefile = "C:\Users\Ezatoka\Desktop\Arpeggio of Blue Steel Ars Nova DC_temp\Arpeggio of Blue Steel Ars Nova DC.ffindex")
#AssumeFPS(25)
poisondeathray
6th November 2019, 22:43
Probably what Atak said about too small resolution and QTGMC bottleneck . You can try 2 simultaneous encodes (or try GPU(CUDA) QTGMC variant if that is the bottleneck).
Atak_Snajpera
6th November 2019, 23:03
With the old staxrip and avisynth (the setting I used with my old computer) x264 also does stay at around 40% of CPU usage.
With the Ripbot the encoding speed is around same (~140FPS) when setting preset slower. But CPU usage is again not fully utilized.
Please see image here (don't want to spam the thread) (https://i.imgur.com/ZNEhWPE.png)
Did you activate deinterlacing? CPU usage by ffmpeg is too low.
Z'Hadum
7th November 2019, 08:58
Thank you for your work!
Thanks to everybody for testing and help with the updates. :thanks:
2.0.5.3 Beta
------------
- update: mkvtoolnix 39
- update: mpv.net 5.4.3
- update: NVEnc 4.55
- fix: few UI issues
- fix: avs MCTemporalDenoise/GradFun2DBmod
- fix: VUI luminance issue
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR
Can also confirm that the luminance issue is fixed.
The rest seems also to work for me....
jlw_4049
7th November 2019, 15:01
Ready for that new stable build :)
stax76
7th November 2019, 17:15
The stable release 2.0.6.0 is online. Thanks to Patman and everybody else for posting tool updates, bug reports and suggestions.
Changelog:
https://github.com/staxrip/staxrip/blob/master/changelog.md
Download:
https://github.com/staxrip/staxrip/releases
Atlantis
7th November 2019, 17:24
No change log for 2.0.6.0
Atlantis
7th November 2019, 17:34
AviSynth+ has not been updated?
There is AviSynth+ 3.4.0 (https://github.com/AviSynth/AviSynthPlus/releases)
Atlantis
7th November 2019, 17:38
Thanks for updating FFT3DFilter. I find it to be the fastest and best temporal noise reduction. It's more practical.
stax76
7th November 2019, 17:54
AviSynth+ has not been updated?
There is AviSynth+ 3.4.0 (https://github.com/AviSynth/AviSynthPlus/releases)
The main reason for why it wasn't updated is there is no small enough installer because the only installer available includes vcredist which is more than 20 MB, it's too large to include. I don't know if 3.4.0 is different from 2.7.7.2, it's likely that for staxrip both will work well.
Atlantis
7th November 2019, 18:02
It's only 27.2 MB. I think we can handle it with today's internet speeds even in countries with ADSL only.
For comparison, Firefox installer is 50 MB and VLC is 40 MB.
I don't understand the technical details maybe someone with knowledge should contact the AviSynth+ team and ask for a better installer? We don't need vcredist?
Patman
7th November 2019, 18:03
No change log for 2.0.6.0Here is right changelog (https://github.com/staxrip/staxrip/blob/master/Changelog.md)
Bahamuth
7th November 2019, 19:16
Did you activate deinterlacing? CPU usage by ffmpeg is too low.
Could be I did not. Am not used to RipBot. I downloaded the current version of Staxrip now, but of course it didn't do much for my problem.
I don't think QTGMC is the main problem, because even if I don't deinterlace, I don't get more CPU usage on x264, vspipe just has nearly no usage anymore.
When deinterlacing, vspipe uses between 5 to 30% CPU and x264 takes between 35 and 45%. Even with a ripped DVD video.
I want to add, that before my new computer, on the old one x264 always uses 100% of the CPU (with Avisynth+), no matter if TV recording, DVD or BluRay movie.
Old computer: Windows 7, 16GB RAM, Intel Core i7-3770s
New Computer: Windows 10, 32GB RAM, AMD Ryzen 9 3900X
Atak_Snajpera
7th November 2019, 19:43
Could be I did not. Am not used to RipBot. I downloaded the current version of Staxrip now, but of course it didn't do much for my problem.
I don't think QTGMC is the main problem, because even if I don't deinterlace, I don't get more CPU usage on x264, vspipe just has nearly no usage anymore.
When deinterlacing, vspipe uses between 5 to 30% CPU and x264 takes between 35 and 45%. Even with a ripped DVD video.
I want to add, that before my new computer, on the old one x264 always uses 100% of the CPU (with Avisynth+), no matter if TV recording, DVD or BluRay movie.
Old computer: Windows 7, 16GB RAM, Intel Core i7-3770s
New Computer: Windows 10, 32GB RAM, AMD Ryzen 9 3900X
Simple solution to all your cpu issues... This way I can saturate even two EPYCs 2 64C/128T
https://i.imgsafe.org/5c/5c0a9ddd47.png
Bahamuth
7th November 2019, 20:52
I just took a look at AVSMeter, though I don't understand it's output... plus it was like 10 times faster than encoding.
AVSMeter 2.9.7 (x64), 2012-2019, Groucho2004
AviSynth+ 0.1 (r2772, MT, x86_64) (0.1.0.0)
Number of frames: 32339
Length (hh:mm:ss.ms): 00:21:33.560
Frame width: 716
Frame height: 576
Framerate: 25.000 (25/1)
Colorspace: i420
Frames processed: 32339 (0 - 32338)
FPS (min | max | average): 684.7 | 1487 | 1242
Process memory usage (max): 37 MiB
Thread count: 44
CPU usage (average): 9.7%
Time (elapsed): 00:00:26.046
Atak_Snajpera
7th November 2019, 21:04
I just took a look at AVSMeter, though I don't understand it's output... plus it was like 10 times faster than encoding.
AVSMeter 2.9.7 (x64), 2012-2019, Groucho2004
AviSynth+ 0.1 (r2772, MT, x86_64) (0.1.0.0)
Number of frames: 32339
Length (hh:mm:ss.ms): 00:21:33.560
Frame width: 716
Frame height: 576
Framerate: 25.000 (25/1)
Colorspace: i420
Frames processed: 32339 (0 - 32338)
FPS (min | max | average): 684.7 | 1487 | 1242
Process memory usage (max): 37 MiB
Thread count: 44
CPU usage (average): 9.7%
Time (elapsed): 00:00:26.046
Because x264 can't utilize all those 24 threads with such low resolution. Try with 1080i source and you will see full cpu usage.
Bahamuth
7th November 2019, 23:35
So... basically I can't do anything at all (which I noticed because I tried giving x264 more to do with --threads option, and it did nothing) because the input data is already coming in as fast as it can? I think with that I can live at least. And hey, the less cores are used, the more MHz the cores get (I think).
Edit: I think a last question about delinterlacers. It seems, TDeint and YadifMod2 are each twice as fast as QTGMC. (encoding a 20min video in 4mins compared to 8mins).
How much worse are the first two deinterlacers? I mean only having to use half of the time seems like a good thing, on 576i/p material?
Atlantis
8th November 2019, 00:59
With 2.0.4.0 we used to get the staxrip version written in MKV like this
Writing frontend : StaxRip v2.0.4.0
Where and what should I write in the Containers Options to get that?
Also just for information, x265 doesn't write the CRF value at the beginning of the line in MKV anymore which was easier to check.
Atlantis
8th November 2019, 01:15
Just reporting, I don't know which is correct. Encoding HDR
With v2.0.4.0 we got
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
With v2.0.6.0 we get
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2
Groucho2004
8th November 2019, 01:23
So... basically I can't do anything at all (which I noticed because I tried giving x264 more to do with --threads option, and it did nothing) because the input data is already coming in as fast as it can?
1. Post your complete script that uses QTGMC.
2. Run "AVSMeter64 avsinfo -log" and post the created log file.
Atlantis
8th November 2019, 02:33
Just checked the original file, so
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2
of v2.0.6.0 is correct.
My question is, I did some HDR encodings with 2.0.4.0.
what
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
means? Is it bad, does it show a difference on an HDR TV instead of the correct info
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2?
Atlantis
8th November 2019, 03:18
Found it. You have to add Writing frontend: StaxRip v%version% but not like previously.
Do not add it in Container Options->Options->Tags like before. It doesn't work.
Add it in Container Options->Tags as
Name: Writing frontend
Value: StaxRip v%version%
Bahamuth
8th November 2019, 09:19
Found it. You have to add Writing frontend: StaxRip v%version% but not like previously.
Do not add it in Container Options->Options->Tags like before. It doesn't work.
Add it in Container Options->Tags as
Name: Writing frontend
Value: StaxRip v%version%
Here's an example:
import os, sys
import vapoursynth as vs
core = vs.get_core()
sys.path.append(r'C:\apps\video\StaxRip2\Apps\Plugins\VS\Scripts')
import importlib.machinery
mvsfunc = importlib.machinery.SourceFileLoader('mvsfunc', r"C:\apps\video\StaxRip2\Apps\Plugins\VS\Scripts\mvsfunc.py").load_module()
adjust = importlib.machinery.SourceFileLoader('adjust', r"C:\apps\video\StaxRip2\Apps\Plugins\VS\Scripts\adjust.py").load_module()
havsfunc = importlib.machinery.SourceFileLoader('havsfunc', r"C:\apps\video\StaxRip2\Apps\Plugins\VS\Scripts\havsfunc.py").load_module()
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\Both\FFMS2\ffms2.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\AWarpSharp2\libawarpsharp2.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\CTMF\CTMF.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\DCTFilter\DCTFilter.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\Deblock\Deblock.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\DFTTest\DFTTest.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\EEDI2\EEDI2.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\EEDI3m\EEDI3m.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\FFT3DFilter\fft3dfilter.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\FluxSmooth\libfluxsmooth.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\fmtconv\fmtconv.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\HQDN3D\libhqdn3d.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\both\KNLMeansCL\KNLMeansCL.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\BM3D\BM3D.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\mvtools\libmvtools.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\nnedi3\libnnedi3.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\nnedi3\NNEDI3CL.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\Sangnom\libsangnom.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\scenechange\scenechange.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\SVPFlow\svpflow1_vs64.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\SVPFlow\svpflow2_vs64.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\vs\TTempSmooth\TTempSmooth.dll")
core.std.LoadPlugin(r"C:\apps\video\StaxRip2\Apps\Plugins\VS\nnedi3\vsznedi3.dll")
clip = core.ffms2.Source(r"C:\Users\Ezatoka\Documents\!media\DVD\He-Man and the Masters of the Universe\001. Das verlorene Schwert (Quest For The Sword).mkv", cachefile = r"C:\Users\Ezatoka\Documents\!media\DVD\He-Man and the Masters of the Universe\001. Das verlorene Schwert (Quest For The Sword)_temp\001. Das verlorene Schwert (Quest For The Sword).ffindex")
#clip = core.std.AssumeFPS(clip, None, 25, 1)
clip = core.std.SetFieldBased(clip, 2) # 1 = BFF, 2 = TFF
clip = havsfunc.QTGMC(clip, TFF = True, Preset = 'Medium')
clip.set_output()
and the AVSMeter info:
AVSMeter 2.9.7 (x64), 2012-2019, Groucho2004
VersionString: AviSynth+ 0.1 (r2772, MT, x86_64)
VersionNumber: 2.60
File / Product version: 0.1.0.0 / 0.1.0.0
Interface Version: 6
Multi-threading support: Yes
Avisynth.dll location: C:\Windows\SYSTEM32\avisynth.dll
Avisynth.dll time stamp: 2018-12-20, 11:55:16 (UTC)
PluginDir2_5 (HKLM, x64): C:\apps\video\AviSynth+\plugins64
PluginDir+ (HKLM, x64): C:\apps\video\AviSynth+\plugins64+
[CPP 2.6 Plugins (64 Bit)] [Version, Time stamp]
C:\apps\video\AviSynth+\plugins64+\ConvertStacked.dll [x.x.x.x, 2018-12-20]
C:\apps\video\AviSynth+\plugins64+\DirectShowSource.dll [x.x.x.x, 2018-12-20]
C:\apps\video\AviSynth+\plugins64+\ImageSeq.dll [x.x.x.x, 2018-12-20]
C:\apps\video\AviSynth+\plugins64+\Shibatch.dll [x.x.x.x, 2018-12-20]
C:\apps\video\AviSynth+\plugins64+\TimeStretch.dll [x.x.x.x, 2018-12-20]
C:\apps\video\AviSynth+\plugins64+\VDubFilter.dll [x.x.x.x, 2018-12-20]
[Scripts (AVSI)] [Time stamp]
C:\apps\video\AviSynth+\plugins64+\colors_rgb.avsi [2016-07-05]
[Uncategorized files] [Time stamp]
C:\apps\video\AviSynth+\plugins64+\colors_rgb.txt [2016-07-05]
Groucho2004
8th November 2019, 09:29
@Bahamuth
How do you run a Vapoursynth script with AVSMeter (I don't know anything about VS)?
stax76
8th November 2019, 12:49
@Bahamuth
How do you run a Vapoursynth script with AVSMeter (I don't know anything about VS)?
vfw/avifile api can open avs and vpy and avisource is vfw/avifile based so you can open a vapoursynth vpy script with avisource.
Groucho2004
8th November 2019, 13:19
vfw/avifile api can open avs and vpy and avisource is vfw/avifile based so you can open a vapoursynth vpy script with avisource.OK. In that case I don't know why the CPU usage is so low. It must be a VS setting or the vfw interface because with AVS+ it is certainly possible to multi-thread QTGMC efficiently even with 24 logical cores (or more).
Bahamuth
8th November 2019, 18:05
Sorry, had the wrong folder:
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\AddGrainC\AddGrainC.dll")
Import("C:\apps\video\StaxRip2\Apps\Plugins\avs\AnimeIVTC\AnimeIVTC.avsi")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\Average\Average.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\Decomb\Decomb.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\DFTTest\dfttest.dll")
Import("C:\apps\video\StaxRip2\Apps\Plugins\AVS\Dither\dither.avsi")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\AVS\Dither\dither.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\EEDI2\EEDI2.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\EEDI3\EEDI3.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\FFT3DFilter\fft3dfilter.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\JPSDR\Plugins_JPSDR.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\both\KNLMeansCL\KNLMeansCL.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\masktools2\masktools2.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\modPlus\modPlus.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\MPEG2DecPlus\MPEG2DecPlus.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\mvtools2\mvtools2.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\RgTools\RgTools.dll")
Import("C:\apps\video\StaxRip2\Apps\Plugins\avs\SMDegrain\SMDegrain.avsi")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\AVS\TDeint\TDeint.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\avs\yadifmod2\yadifmod2.dll")
LoadPlugin("C:\apps\video\StaxRip2\Apps\Plugins\Both\FFMS2\ffms2.dll")
Import("C:\apps\video\StaxRip2\Apps\Plugins\avs\QTGMC\QTGMC.avsi")
FFVideoSource("C:\Users\Ezatoka\Documents\!media\DVD\He-Man and the Masters of the Universe\001. Das verlorene Schwert (Quest For The Sword).mkv", colorspace = "YV12", \
cachefile = "C:\Users\Ezatoka\Documents\!media\DVD\He-Man and the Masters of the Universe\001. Das verlorene Schwert (Quest For The Sword)_temp\001. Das verlorene Schwert (Quest For The Sword).ffindex")
#AssumeFPS(25)
Crop(2, 0, -2, -0)
QTGMC(Preset = "Medium")
Bahamuth
8th November 2019, 18:09
OK. In that case I don't know why the CPU usage is so low. It must be a VS setting or the vfw interface because with AVS+ it is certainly possible to multi-thread QTGMC efficiently even with 24 logical cores (or more).
even without any deinterlacer, x264 stays under 50%. It's not just the deinterlacer. I will make a try with a FullHD movie to see, how the CPU usage will be then.
Bahamuth
8th November 2019, 18:33
Yep, FullHD movie makes x264 use 95-99% CPU, without any filters
Patman
8th November 2019, 19:06
Just checked the original file, so
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2
of v2.0.6.0 is correct.
My question is, I did some HDR encodings with 2.0.4.0.
what
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
means? Is it bad, does it show a difference on an HDR TV instead of the correct info
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2?
Hi Atlantis,
maybe that (https://x265.readthedocs.io/en/default/cli.html#cmdoption-master-display) will help you.
...
Also just for information, x265 doesn't write the CRF value at the beginning of the line in MKV anymore which was easier to check.
That feature is an customization of the x265.exe, that's not included in default x265.exe.
Atak_Snajpera
8th November 2019, 19:19
Yep, FullHD movie makes x264 use 95-99% CPU, without any filters
Told you...
Exaris
8th November 2019, 20:06
The included x265 is compiled with GCC right? Could you check the performance difference when compiled with VS 2019? At http://msystem.waw.pl/x265/ I've noticed that VS 2019 AVX2 is faster than GCC 9.2 AVX2. Could you check if the performance difference is worth changing compilers?
TomSmith
9th November 2019, 10:37
@ TomSmith
i've updated my system now and everything works like a charme. No problems with ram or other hardware issues.
@ all
updated some of my builds
Hi Patman!
My board just got an bios update. It seems that my problem was fixed... at least I haven't seen this errors...
Best wishes!
Tom
Bahamuth
9th November 2019, 12:30
Told you...
I'm making things easy then... I'll just spawn two Staxrip instances both having other videos to encode. This should be a workaround for utilising my CPU to the fullest.
Atak_Snajpera
9th November 2019, 13:00
I'm making things easy then... I'll just spawn two Staxrip instances both having other videos to encode. This should be a workaround for utilising my CPU to the fullest.
Some people prefer to build two houses simultaneously and some single house but two times faster...
Bahamuth
9th November 2019, 14:07
Well I'm trying now for many days to make this work. It does not, and I lost these days encoding things I want to encode. So when there is no solution, one has to use a workaround.
stax76
9th November 2019, 15:11
The way I see it is if the tools are too slow then it's not the fault of staxrip. I'm not sure how difficult it would be to add this feature, the processing routine supports multiple processes so it might not be very difficult.
Bahamuth
9th November 2019, 15:16
Could it be, that the icons folder is missing sometimes in the rar file? In the current version it's gone again. And without a proper icon, if you minimize the window to the tray, it's gone. (can use Process Explorer to get the window to front again).
Bahamuth
9th November 2019, 19:11
I can't change any values using the scroll wheel in fields like quality. Intended?
https://i.imgur.com/VRFVgtz.png
stax76
9th November 2019, 20:02
Could it be, that the icons folder is missing sometimes in the rar file? In the current version it's gone again. And without a proper icon, if you minimize the window to the tray, it's gone. (can use Process Explorer to get the window to front again).
I've downloaded it and the icons folder was there, maybe there is still a bug with the tray icon.
I can't change any values using the scroll wheel in fields like quality. Intended?
It should work as long as you hover over the control, I wrote this control but the wheel of the default numeric up down control behaves exactly the same as mine.
Bahamuth
9th November 2019, 23:36
I've downloaded it and the icons folder was there, maybe there is still a bug with the tray icon.
That... I don't understand. I download https://github.com/Revan654/staxrip/releases/download/2.0.2.4/Staxrip.2.0.2.4.x64.rar and when I look into the Apps subfolder, I see this:
https://i.imgur.com/5yN0nxa.png
No Icons subfolder.
It should work as long as you hover over the control, I wrote this control but the wheel of the default numeric up down control behaves exactly the same as mine.
check, so I should just keep my mouse over there
stax76
10th November 2019, 02:42
First post is outdated...
https://github.com/staxrip/staxrip
lasa
10th November 2019, 13:53
which avs source filter should i use for bluray to mkv
jlw_4049
10th November 2019, 14:43
which avs source filter should i use for bluray to mkvFfvidesource
Sent from my SM-G965U1 using Tapatalk
Forteen88
12th November 2019, 18:38
which avs source filter should i use for bluray to mkvI think that LSMASHSource is great for AVC Blu-rays.
lasa
13th November 2019, 10:24
LSMASHSource or Ffvidesource?
jlw_4049
13th November 2019, 12:02
LSMASHSource or Ffvidesource?Both will do what you need to do
Sent from my SM-G965U1 using Tapatalk
stax76
13th November 2019, 14:25
@lasa
There are three popular source plugin for AviSynth and VapourSynth:
ffms2
FFVideoSource
L-Smash-Works
LSMASHVideoSource (*.mp4 file type/extension only, no indexing needed)
LWLibavVideoSource (any video file type/extension)
Both support hardware decoding.
DGDecNV
DGDecode
For dvb it's probably still better than ffms2 and L-Smash-Works.
Patman
16th November 2019, 16:47
Hi all, i've updated my builds. There were problems with ffmpeg if you wanted to encode VP9/AV1. If you want to know the estimated file size when using x265-encoder, download my custom build of x265. Thanks for the info Link (https://github.com/staxrip/staxrip/issues/86)
L-Smash-Works has been updated Link (http://forum.doom9.org/showthread.php?p=1890493#post1890493)
NikosD
16th November 2019, 21:37
@patmam
@stax76
Latest QSVEncC v3.25 is out with minor performance gain and among other things, rigaya removed VC-1 from HW decoding.
According to him, he did everything he could but didn't manage to make it work as it used to.
https://onedrive.live.com/?authkey=%21ABHV5TR4KvNqv9o&id=6BDD4375AC8933C6%21482&cid=6BDD4375AC8933C6
Patman
16th November 2019, 21:54
Hi NikosD,
thanks for the info. I read the changelog on github.
Gesendet von meinem HMA-L09 mit Tapatalk
Forteen88
17th November 2019, 12:28
@patmamIt's Maaaaan! :)
Andy
18th November 2019, 18:41
Thanks for updating FFT3DFilter. I find it to be the fastest and best temporal noise reduction. It's more practical.
Yes, I also started using. It is faster than QTGMC and leaves slight noise like bluray.
I would like to ask which noise filter retains the bit depth of the 10bit source?
I ask because I have been working with Staxrip 2.0.0.0 and 2.0.2.4 for a long time, which had the wrong script template (colorspace = YV12) and so I have all the UHD rips basically 8bit ...
According to this table FFT3DFilter should suit if I understand it well:
http://avisynth.nl/index.php/External_filters#Spatio-Temporal_Denoisers
Atlantis
19th November 2019, 00:15
I'm not 100% sure but I think FFT3DFilter is correctly handling 10bit source. I am currently using FFT3DFilter with 4K HDR sources and all seems correct.
I also use RemoveGrain
https://forum.doom9.org/showthread.php?t=174347
10-16 bits and 32 bit float colorspace support in AVS+
t3nzin
19th November 2019, 08:46
A few updates since 2.0.6.0 and some that didn't make it:
- d2vsource v1.2 (https://github.com/dwbuiten/d2vsource/releases/tag/v1.2)
- AVSMeter v2.9.7 (http://www.iol.ie/~schubert/gas/gas.html) & (https://forum.doom9.org/showthread.php?p=1889697#post1889697)
- BDSup2Sub++ v1.0.3 (https://github.com/amichaeltm/BDSup2SubPlusPlus/releases)
- chapterEditor v1.19 (https://forum.doom9.org/showthread.php?p=1884972#post1884972)
- AviSynth+ v3.4.0 (https://github.com/AviSynth/AviSynthPlus/releases/tag/v3.4.0)
- Python 3.7.5 (https://www.python.org/downloads/release/python-375/)
- MKVToolNix v40.0.0 (https://forum.doom9.org/showthread.php?p=1889963#post1889963)
- SubtitleEdit v3.5.11 (https://github.com/SubtitleEdit/subtitleedit/releases/tag/3.5.11)
- rav1e v0.1.0 (https://github.com/xiph/rav1e/releases/tag/0.1.0)
- QSVEnc v3.25 (https://github.com/rigaya/QSVEnc/releases/tag/3.25)
- x265-stable v3.2.1+1 (http://msystem.waw.pl/x265/)
- x265-default v3.2+15 (http://msystem.waw.pl/x265/) & (https://www.mediafire.com/folder/vkt2ckzjvt0qf/StaxRip_Tools)
- x264 r2988 (https://code.videolan.org/videolan/x264/commits/master) & (https://www.mediafire.com/folder/vkt2ckzjvt0qf/StaxRip_Tools)
- MP4Box v0.8.0-rev107 (https://www.mediafire.com/folder/vkt2ckzjvt0qf/StaxRip_Tools)
- FFmpeg Nightly (https://ffmpeg.zeranoe.com/builds/) & (https://www.mediafire.com/folder/vkt2ckzjvt0qf/StaxRip_Tools)
- L-SMASH-Works 2019-11-16 (http://forum.doom9.org/showthread.php?p=1890493#post1890493)
stax76
19th November 2019, 14:02
@t3nzin
That is very helpful, thank you. I might start to code something difficult so it might take some time until updating continues.
t3nzin
20th November 2019, 01:47
@stax76 I can send you a PR or file an issue on the github repo if you like, also have a personal Stax change to reimplement the batch system from pre-2.0.
AMED
20th November 2019, 18:43
Hi Stax76,
There is an issue with v2.0.6.0 and the parentheses that are being used. staxrip is using ' for the file path for the vapoursynth source filter which is give an invalid syntax error in python when the file name contains a '.
This occurs with FFMS2 and LWLibavSource.
Python exception: invalid syntax (Batman- The Animated Series - S01E06 - It's Never Too Late_source.vpy, line 6)
Traceback (most recent call last):
File "src\cython\vapoursynth.pyx", line 1943, in vapoursynth.vpy_evaluateScript
File "C:\TMP\Batman- The Animated Series - S01E06 - It's Never Too Late_temp\Batman- The Animated Series - S01E06 - It's Never Too Late_source.vpy", line 6
clip = core.lsmas.LWLibavSource(r'Z:\Bluray\Queue\10\Batman- The Animated Series\Season 1\Batman- The Animated Series - S01E06 - It's Never Too Late.mkv', cachefile=r'C:\TMP\Batman- The Animated Series - S01E06 - It's Never Too Late_temp\Batman- The Animated Series - S01E06 - It's Never Too Late.lwi')
^
SyntaxError: invalid syntax
import os, sys
import vapoursynth as vs
core = vs.get_core()
sys.path.append(r'Z:\Bluray\Staxrip\Apps\Plugins\VS\Scripts')
import importlib.machinery
resamplehq = importlib.machinery.SourceFileLoader('resamplehq', r"Z:\Bluray\Staxrip\Apps\Plugins\VS\Scripts\resamplehq.py").load_module()
mvsfunc = importlib.machinery.SourceFileLoader('mvsfunc', r"Z:\Bluray\Staxrip\Apps\Plugins\VS\Scripts\mvsfunc.py").load_module()
adjust = importlib.machinery.SourceFileLoader('adjust', r"Z:\Bluray\Staxrip\Apps\Plugins\VS\Scripts\adjust.py").load_module()
havsfunc = importlib.machinery.SourceFileLoader('havsfunc', r"Z:\Bluray\Staxrip\Apps\Plugins\VS\Scripts\havsfunc.py").load_module()
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\fmtconv\fmtconv.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\AWarpSharp2\libawarpsharp2.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\CTMF\CTMF.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\VS\DCTFilter\DCTFilter.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\VS\Deblock\Deblock.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\DFTTest\DFTTest.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\EEDI2\EEDI2.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\EEDI3m\EEDI3m.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\FFT3DFilter\fft3dfilter.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\FluxSmooth\libfluxsmooth.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\HQDN3D\libhqdn3d.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\both\KNLMeansCL\KNLMeansCL.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\BM3D\BM3D.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\mvtools\libmvtools.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\VS\nnedi3\libnnedi3.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\VS\nnedi3\NNEDI3CL.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\Sangnom\libsangnom.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\scenechange\scenechange.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\VS\SVPFlow\svpflow1_vs64.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\VS\SVPFlow\svpflow2_vs64.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\vs\TTempSmooth\TTempSmooth.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\VS\nnedi3\vsznedi3.dll")
core.std.LoadPlugin(r"Z:\Bluray\Staxrip\Apps\Plugins\both\L-SMASH-Works\LSMASHSource.dll")
clip = core.lsmas.LWLibavSource(r'Z:\Bluray\Queue\10\Batman- The Animated Series\Season 1\Batman- The Animated Series - S01E06 - It's Never Too Late.mkv', cachefile=r'C:\TMP\Batman- The Animated Series - S01E06 - It's Never Too Late_temp\Batman- The Animated Series - S01E06 - It's Never Too Late.lwi')
#clip = core.std.AssumeFPS(clip, None, 25, 1)
clip = core.fmtc.bitdepth(clip, bits=16)
clip = core.std.Crop(clip, 0, 0, 0, 0)
clip = resamplehq.resamplehq(clip, 960, 540, kernel='Spline36')
clip = havsfunc.SMDegrain(clip, tr=4, RefineMotion=True, thSAD=500)
clip.set_output()
mcjordan
20th November 2019, 20:40
x265 3.2+15 -> New options:
Add options "--scenecut-aware-qp", "--scenecut-window" and "--max-qp-delta" to
enable boundary aware frame quantization, to set window size (optional) and to
set offset (optional).
Andy
21st November 2019, 15:33
I'm not 100% sure but I think FFT3DFilter is correctly handling 10bit source. I am currently using FFT3DFilter with 4K HDR sources and all seems correct.
I also use RemoveGrain
https://forum.doom9.org/showthread.php?t=174347
10-16 bits and 32 bit float colorspace support in AVS+
Thank you, I thought so.
But I'm not sure about RemoveGrain, the table shows only coloformat YV12 and YUY2.
(sorry for bad english, not my native language, I use google translator)
Patman
21st November 2019, 17:10
Hi Stax76,
There is an issue with v2.0.6.0 and the parentheses that are being used. staxrip is using ' for the file path for the vapoursynth source filter which is give an invalid syntax error in python when the file name contains a '.
This occurs with FFMS2 and LWLibavSource.
Hi AMED,
i've got these error only with LibavSMASHSource. FFMS2 and LWLibavSource works great.
AMED
21st November 2019, 18:08
Hi AMED,
i've got these error only with LibavSMASHSource. FFMS2 and LWLibavSource works great.When i change the source filter in the Vapoursynth profile i see this
clip = core.avisource.AVISource(r'%source_file%')
clip = core.d2v.Source(r'%source_file%')
clip = core.dgdecodenv.DGSource(r'%source_file%')
clip = core.ffms2.Source(r'%source_file%', cachefile=r'%source_temp_file%.ffindex')
clip = core.lsmas.LibavSMASHSource(r'%source_file%')
clip = core.lsmas.LWLibavSource(r'%source_file%', cachefile=r'%source_temp_file%.lwi')
when it should be
clip = core.avisource.AVISource(r"%source_file%")
clip = core.d2v.Source(r"%source_file%")
clip = core.dgdecodenv.DGSource(r"%source_file%")
clip = core.ffms2.Source(r"%source_file%", cachefile=r"%source_temp_file%.ffindex")
clip = core.lsmas.LibavSMASHSource(r"%source_file%")
clip = core.lsmas.LWLibavSource(r"%source_file%", cachefile=r"%source_temp_file%.lwi")
The workaround is to change the source from automatic to the source filter you want to use and then edit the source filter manually.
Patman
21st November 2019, 18:40
When i change the source filter in the Vapoursynth profile i see this ...
The workaround is to change the source from automatic to the source filter you want to use and then edit the source filter manually.
When i set vapoursynth filters, right-click in filter window and select profiles, these code is shown:
[Source]
Automatic = # can be configured at: Tools > Settings > Source Filters
AVISource = clip = core.avisource.AVISource(r"%source_file%")
d2vsource = clip = core.d2v.Source(r"%source_file%")
DGSource = clip = core.avs.DGSource(r"%source_file%")
ffms2 = clip = core.ffms2.Source(r"%source_file%", cachefile = r"%source_temp_file%.ffindex")
LibavSMASHSource = clip = core.lsmas.LibavSMASHSource(r"%source_file%")
LWLibavSource = clip = core.lsmas.LWLibavSource(r"%source_file%")
Manual = # shows filter selection dialog
Seems to be correct.
stax76
21st November 2019, 18:54
The workaround is to change the source from automatic to the source filter you want to use and then edit the source filter manually.
If you edit the filter profiles you have to change it only once.
Andy
21st November 2019, 19:10
I'm trying to shrink and convert uhd movie to fhd sdr 10bit while maintaining bit depth according to dghdrtosdr and it seems to work. :thanks:
https://www.2i.cz/images/2019/11/21/Beze-jmena.th.jpg (https://www.2i.cz/i/3ZeTO)
AMED
21st November 2019, 21:24
I've deleted the settings folder and reopened Staxrip, chose a new setting folder. Said no to the daily update message then clicked on avs filters > filter setup > vapoursynth. right clicked source and selected Source > ffms.
clip = core.ffms2.Source(r'%source_file%', cachefile=r'%source_temp_file%.ffindex')
#clip = core.std.AssumeFPS(clip, None, 25, 1)
I have tested this on 3 computers, server 2012R2 and W10 1909
EDIT: I just found this in package.vb
.VSFiltersFunc = Function() {New VideoFilter("Source", "ffms2", "clip = core.ffms2.Source(r'%source_file%', cachefile=r'%source_temp_file%.ffindex')" + BR + "#clip = core.std.AssumeFPS(clip, None, 25, 1)")}})
https://github.com/staxrip/staxrip/blob/master/General/Package.vb#L486
Which i assume should be changed to this
.VSFiltersFunc = Function() {New VideoFilter("Source", "ffms2", "clip = core.ffms2.Source(r""%source_file%"", cachefile=r""%source_temp_file%.ffindex"")" + BR + "#clip = core.std.AssumeFPS(clip, None, 25, 1)")}})
d2vsource = https://github.com/staxrip/staxrip/blob/master/General/Package.vb#L1602
DGSource = https://github.com/staxrip/staxrip/blob/master/General/Package.vb#L453
LibavSMASHSource = https://github.com/staxrip/staxrip/blob/master/General/Package.vb#L589
LWLibavSource = https://github.com/staxrip/staxrip/blob/master/General/Package.vb#L590
Salem874
21st November 2019, 23:28
I've found StaxRip after trying to find a way to rip HDR content to a smaller size, but KEEPING the HDR metadata.
I currently use Handbrake due to the excellent quality of it's exports, plus it's super easy to use (but still flexible), but as we know it's not yet fully HDR/10-bit compatible.
However, i'm extremely confused as to how to re-encode/rip HDR content using StaxRip. Are there any guides/tutorials out there?
I've finally managed to convert an video file but colour mapping it down to SDR-ready video for non-HDR players/screens.
Now, is there any special I need to select/set in the Plethora of options available within Staxrip (Currently running 2.0.6.0)?
I'm liking Staxrip, and it seems to be very flexible, but what it does need is a good set of tutorials (maybe there are already, but i havent found any)
stax76
21st November 2019, 23:38
@AMED
https://postimg.cc/94xZNGH0
I'll fix it when development continues, this might take some weeks or even months, I want to replace the interface for avisynth and vapoursynth as well as the rendering.
Bahamuth
23rd November 2019, 21:44
I have several video files with the following codec:
Video
ID : 1
ID in the original source medium : 4113 (0x1011)
Format : VC-1
Format profile : Advanced@L2
Codec ID : V_MS/VFW/FOURCC / WVC1
Codec ID/Hint : Microsoft
Duration : 1 min 20 s
Bit rate : 2 216 kb/s
Width : 720 pixels
Height : 480 pixels
Display aspect ratio : 3:2
Original display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Scan order : 2:3 Pulldown
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.267
Stream size : 21.2 MiB (74%)
Language : English
Default : No
Forced : No
Original source medium : Blu-ray
Upon opening them with Staxrip, the automatic crop goes to 358x338 and when I open the crop window, I only get a message on the top saying "Resize error: Resize error 3074: invalid colorspace definition (5/2/6 => 0/2/6). May need to specify additional colorspace parameters"
This comes when I use VapourSynth. When I use AviSynth the crop window works as usual.
So I would guess, this is an error in the crop plugin for VS then? Are the crop plugins this different for VS and AS?
IbrahimKh
24th November 2019, 14:01
I'm trying to shrink and convert uhd movie to fhd sdr 10bit while maintaining bit depth according to dghdrtosdr and it seems to work. :thanks:
https://www.2i.cz/images/2019/11/21/Beze-jmena.th.jpg (https://www.2i.cz/i/3ZeTO)
I've finally managed to convert an video file but colour mapping it down to SDR-ready video for non-HDR players/screens.
Now, is there any special I need to select/set in the Plethora of options available within Staxrip (Currently running 2.0.6.0)?
I'm liking Staxrip, and it seems to be very flexible, but what it does need is a good set of tutorials (maybe there are already, but i havent found any)
Did you both got full CPU usage when converting from HDR to SDR?
I could only get about 20% CPU usage with avisynth and DGHable script. But when DGHable was stripped, I am able to get about 98% CPU usage.
https://i.postimg.cc/sGgYvDZj/screenshot-102.png (http://postimg.cc/sGgYvDZj)
I had to encode 3 videos at once, none of them could get more than 30% CPU with DGHable applied.
Bahamuth
24th November 2019, 21:26
Another problem I hope I can find some insights here.
File properties:
ID : 1
ID in the original source medium : 4113 (0x1011)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 2 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 2 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 min 5 s
Bit rate mode : Variable
Bit rate : 3 838 kb/s
Width : 720 pixels
Height : 480 pixels
Display aspect ratio : 4:3
Original display aspect ratio : 4:3
Frame rate mode : Variable
Frame rate : 59.940 (60000/1001) FPS
Original frame rate : 29.970 (30000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan type, store method : Separated fields
Scan order : Bottom Field First
Bits/(Pixel*Frame) : 0.185
Stream size : 29.8 MiB (95%)
Language : English
Default : No
Forced : No
Original source medium : Blu-ray
No matter which deinterlacing I choose, no matter if I don't set any deinterlacer at all, no matter if I set x264 options to Interlaced, Bottom Field First, the output file ALWAYS plays the video only in half speed. What could cause this? As this example is just an advertisement, I could upload it.
JKyle
25th November 2019, 19:18
NVEnc 4.56 is released today.
- Allow one of the value (either width or height) in --output-res to be negative, which will automatically calculate the width or height to keep the aspect ratio.
- Fix issue that VC-1 hw decode was failing in some input files.
- Update option list of weightp, removing "H.264 only".
- Now warning for HEVC + weightp encoding will be shown on Pascal/Volta Gen GPUs.
- Limit HEVC multirefs to make it complaiant to HEVC spec.
- Add option which adds delay to audio stream. (avaliable for avsw/avhw reader)
Andy
28th November 2019, 21:28
Did you both got full CPU usage when converting from HDR to SDR?
No, in this case specifically only about 50-70% on average, I do not remember much anymore. The main thing I did was gpu (1080Ti).
I haven't used the DGHable script, only DGIndex, Resize to 1080p and DGHDRtoSDR with avisynth (mode = "pq", white = 1800, fulldepth = true).
The value of "white" increases gamma, at 1800 the video is dark, I gave 2300.
Maybe it does not comply with BT.709 standards, but it is good for my eyes and ips monitor. The color corresponds to reality.
http://forum.doom9.net/showthread.php?t=175686
Bahamuth
30th November 2019, 16:52
Hmm my problem with the slow video after encoding does not exist when encoding with Handbrake. Tried now four different deinterlacers, each result is the same. Slow video, normal audio speed.
These separate fields must be terrible...
sgfrisbee
2nd December 2019, 18:12
StaxRip has stopped hardcoding subtitles. I have try versions 2.0 to 2.0.6.0 and they all have stopped hardcoding subtiles.
StaxRip does not error out when encoding video file, it just does
not HC subtitles. It does the same thing with subtitles I use
srt and ass files.
Log file attached.
Thank you for any help on this.
jonrodrigos
3rd December 2019, 18:13
Hello everyone, I have many doubts when using staxrip, I would like to ask if anyone can give me a link or explain through the forum how to configure and use staxrip 2.0.6 for movies in 4k hdr in the best quality using nvenc NVIDIA? I have doubts as to the decoder if it is better to use vapourSynth or AviSynth or even nvenc hardware or software .... etc
i have nvidia asus gtx 1070ti
it's hard to find tutorial on the internet
if anyone can explain me, I will be very grateful.
thank you!
JKyle
5th December 2019, 20:34
NVEnc 4.57 is released today.
- Add HLG->SDR support to vpp-colorspace hdr2sdr.
- Fix typo of a parameter. ( arib-srd-b67 -> arib-std-b67)
- Remove "w" option from vpp-colorspace hdr2sdr=hable, now will be calculated by source_peak / ldr_nits.
- Fix sub-copy not working from NVEnc 4.56.
- Fix trueHD decode error in mkv which has certain pattern of timestamps.
- Fix vpp-afs level= 0 getting unexpexted artifacts.
Here (https://github.com/rigaya/NVEnc/releases/tag/4.57).
writersblock29
8th December 2019, 09:14
StaxRip has stopped hardcoding subtitles. I have try versions 2.0 to 2.0.6.0 and they all have stopped hardcoding subtiles.
Yeah, I ran into this tonight while encoding "Men in Black." After a bit of troubleshooting, I concluded that the problem lays with VSFilterMod, or at the very least it was worth bypassing it. Since I also have Ripbot264 installed on my system, I copied the VSFilter plugin from Ripbot's plugin folder... pasted it into Staxrip's AVS plugins folder... then edited Staxrip's AVS script so that it would point to it. It worked: the subs are burned into the video as expected.
If you try this approach, you can edit the necessary commands from Staxrip's filter editor. After placing VSFilter into your AVS plugins folder, open the editor and you'll see a command like, "TextSubMod (your subtitle file's path and file name.)" In my case, I replaced this text with:
LoadPlugin("C:\Users\write\Documents\StaxRip-x64-2.0.6.0-stable\Apps\Plugins\AVS\VSFilter\VSFilter.dll")
TextSub("F:\Men in Black.srt")
Of course you'll likely have a different file path than mine, but that's the tall and skinny of it. It's clunky, but it works!
Forteen88
9th December 2019, 10:41
...
i have nvidia asus gtx 1070tiYou should've got a newer Nvidia-card for HEVC/H.265 NVEnc-encoding, since the newest graphicscards gives better picture quality for the bitrate (the new ones handles B-frames!),
I mean the cards in the list with "HEVC B Frame support" here,
https://developer.nvidia.com/video-encode-decode-gpu-support-matrix
writersblock29
9th December 2019, 17:57
...I would like to ask if anyone can give me a link or explain through the forum how to configure and use staxrip 2.0.6 for movies in 4k hdr in the best quality using nvenc NVIDIA?
Questions like this tend to be loaded, since quality's subjective. I could post the settings I use, but it'd fall flat on two counts: the first is that I'm using a GTX 1660, which supports the use of b-frames and uses a different architecture than your card. The second is that someone else will inevitably chime in with "Why the heck are you using X setting? You're wasting bits!!!" Because I like my settings, I'll be right. Because he likes HIS settings, he'll be right. That's why this forum frowns on the "What's best?" question.
The most general advice I can offer is to make sure you're using 10-bit instead of 8-bit, use the Main 10 profile in your encoder, and run some tests from there. If you use low CQP values, you'll get better quality which will come at the expense of larger file sizes. If you use high VBR settings, same deal: better quality, bigger file sizes. Only you can determine where your sweet spot is. And once you find it, you'll be just as right as anyone else.
Bahamuth
13th December 2019, 00:49
I found the reason for the wrong encoding of my videos.
ffms2.dll with version 2019-08-30 StvG is producing faulty videos for me. If I use the "old" 2.23.1 (latest version) from the website (https://github.com/FFMS/ffms2/releases), then my video is encoded just fine.
I noticed, that during the x264 encode, the amount of frames was considerably higher than with the ffms2.dll shipped from StaxRip 2.
I uploaded an example. (https://silentstrider.net/example.mkv) No additional filters needed.
Old ffms2.dll shows this info in StaxRip:
https://i.imgur.com/QVCva3s.png
New ffms2.dll shows this info in StaxRip:
https://i.imgur.com/aEeKSGB.png
Notice the FPS of the Source Video.
ircopdd
14th December 2019, 04:36
I found the reason for the wrong encoding of my videos.
ffms2.dll with version 2019-08-30 StvG is producing faulty videos for me. If I use the "old" 2.23.1 (latest version) from the website (https://github.com/FFMS/ffms2/releases), then my video is encoded just fine.
.
right
i use FFVideoSource("%source_file%", cachefile="%source_temp_file%.ffindex", fpsnum=60000, fpsden=1001)
#AssumeFPS(25)
have problem
https://youtu.be/IRaFKzqpF18
use Old ffms2.dll is Works perfectly...
Bahamuth
14th December 2019, 18:43
Now I have to check hundreds of video clips I have encoded since 2.0.4.0 came out, crap...
When converting DVDs and BluRays I don't open the resulting file immediately. Never had a reason to.
Mister XY
14th December 2019, 22:26
Now I have to check hundreds of video clips I have encoded since 2.0.4.0 came out, crap...
When converting DVDs and BluRays I don't open the resulting file immediately. Never had a reason to.
I have write me a small bash script for linux. That script search for mkv files with frames higher than 24 and write it to a log file.
I must start this Script with ./mediainfo.sh "/mnt/md0/Video"
but i have to install the bin mediainfo
#!/bin/bash
FRAusgabe="/root/x265FRinfo.txt" # Output for the logfile
WriAppi="" # mkvmerge or HandBrake or another
miniFR="24" # minimal Frames
Frames() {
if [ -f $FRAusgabe ]
then
rm $FRAusgabe
fi
find "$UF_FOLDER" . -type f -iname "*.mkv" -print0 | while IFS= read -r -d $'\0' linefr; do
if [ `mediainfo --inform= "$linefr" | grep "Writing application" | grep -c "$WriAppi"` -eq 1 ]; then
mediainfver=$(mediainfo --inform="Video;%FrameRate%" "$linefr")
if [ `mediainfo --inform="Video;%FrameRate%" "$linefr" | cut -c 1-2` -ge $miniFR ]; then
echo $linefr FPS:$mediainfver | sed "s|$UF_FOLDER||" >> $FRAusgabe
fi
fi
done
}
case "$1" in
* )
UF_FOLDER="$1"
Frames
;;
esac
stax76
16th December 2019, 14:26
Quick status update on the hardware renderer for the preview and crop dialog, I've reached 2 milestones recently and will hopefully have a first beta within a month.
JKyle
16th December 2019, 17:15
rigaya released NVEnc 4.58 today.
Some bug fixes.
- Fix memory leak in audio processing.
- Fix HEVC level not shown properly on the log.
- Fix issue that encode speed and bitrate were not shown properly by --pref-monitor.
Here (https://github.com/rigaya/NVEnc/releases/tag/4.58).
JKyle
17th December 2019, 20:11
x264 159 r2991 was released yesterday.
Here (https://www.videohelp.com/software/x264-Encoder).
However, the official build distributed by VideoLAN lacks support for ffms and MP4 container as you may know.
I'd like to see if @Patman is interested in building a customized version with that kind of support as he's been doing recently.
(And ffmpeg and others as well.)
Thanks in advance. :)
Patman
17th December 2019, 20:31
x264 159 r2991 was released yesterday.
Here (https://www.videohelp.com/software/x264-Encoder).
However, the official build distributed by VideoLAN lacks support for ffms and MP4 container as you may know.
I'd like to see if @Patman is interested in building a customized version with that kind of support as he's been doing recently.
(And ffmpeg and others as well.)
Thanks in advance. :)Hi JKyle,
I will do, maybe at weekend. My hdd has crashed two weeks ago, so I had no time to build my custom builds.
Gesendet von meinem HMA-L09 mit Tapatalk
JKyle
17th December 2019, 20:38
My hdd has crashed two weeks ago, so I had no time to build my custom builds.
I'm deeply sorry to hear that. :eek:
It explains why your builds have not been updated over the last 3 weeks. Hmm...
Hope the data isn't lost along and you recover quickly. :)
Patman
17th December 2019, 20:40
I'm deeply sorry to hear that. :eek:
It explains why your builds have not been updated over the last 3 weeks. Hmm...
Hope the data isn't lost along and you recover quickly. :)I'm on a good way [emoji16]
Gesendet von meinem HMA-L09 mit Tapatalk
hippo88
18th December 2019, 03:04
Hi,
I used staxrip x64 2.0.6.0 to encode these games but received "unsupported video data" from Samsung (2009) playing from external hd. Please help. Thank you.
writersblock29
21st December 2019, 16:58
StaxRip has stopped hardcoding subtitles.
Okay... I looked into this some more since this doesn't seem to be a wide-spread problem, yet we're both having it. I found a solution that hopefully helps you out, too.
Check to see what your decoder is set to. I was using my Nvidia card before, and I can't tell from your log if you're doing the same. Switch it to AVIsynth+/Vaporsynth. While you're at it, make sure Staxrip sees no problem with your AVIsynth+ installation--and if it does, reinstall it.
Once done with those steps, try rerunning your project and see if that clears things up. On my end, it did: no more directing it to Ripbot's VSFilter or other lasso tricks. It runs just as it always had before. Fingers crossed here, but hopefully it'll dig you out, too.
If it does, please reply so if anyone else out there's having this problem, they'll know to make sure Staxrip is playing nice with AVIsynth+.
lordalibaski
21st December 2019, 23:55
Hi guys
I'm back to converting some old vhs videos again, some of these captures are low in volume is there any option in staxrip to boost the volume a little?
luigizaninoni
22nd December 2019, 07:41
Hi guys
I'm back to converting some old vhs videos again, some of these captures are low in volume is there any option in staxrip to boost the volume a little?
in audio settings of your profile, in custom try adding:
-af dynaudnorm=p=0.94:m=50:s=12
this should normalise your audio fairly well
stax76
22nd December 2019, 15:10
New build:
2.0.6.1 Beta
------------
new: the preview dialog uses now a Direct2D harware accelerated video renderer, it's much faster, especially on 4K screens
fix: the info tool in the code editor was not showing the correct colorspace
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR
I've not yet decided what's next for staxrip, options are:
Website
Documentation
Better usability and diagnostics
SVT-AV1 GUI
Replacing VFW/AVIFile with direct AviSynth/VapourSynth access
Splitting video in parts and encode it in parallel
Better support for opening external avs and vpy files
Improve mpv.net that it can open vpy files
Support Direct2D in Crop and Video Comparison
I've few little other projects as well however. :)
imhh11
22nd December 2019, 19:12
Thank's for the update stax76 (https://forum.doom9.org/member.php?u=13377)
Patman
23rd December 2019, 14:23
Hi all,
i've updated my tools for staxrip "small christmas present".
stax76
23rd December 2019, 15:26
Thanks, Patman. Next built has the crop dialog using hw rendering as well which completes this work so maintenance (tool updates and user feedback) can continue now.
Tadanobu
23rd December 2019, 16:11
I'm using 2.0.3 and video comparison seems buggy. It often happens to me that the tool shows different frames when I change tab. I'm sure the problem does not come from the files. MediaInfo.NET shows same framerate and frames count. Also, when I play the files frames after frames in mpv.NET I can see they are all the same. Is this a known bug that has been fixed already ? (Changelog on github is unavailable).
Another idea for future feature : be able to easily calculate VMAF.
JKyle
23rd December 2019, 17:36
Hi all,
i've updated my tools for staxrip "small christmas present".
Thanks a million, Patman!
BTW, this round of ffmpeg.exe build has a size of 69.67 MiB, and based on that, it seems like you left it uncompressed unlike other binaries.
(But I'm not sure if it's true.)
If it is not compressed, was it intended or did you forget?
:thanks:
Patman
23rd December 2019, 17:53
Thanks a million, Patman!
BTW, this round of ffmpeg.exe build has a size of 69.67 MiB, and based on that, it seems like you left it uncompressed unlike other binaries.
(But I'm not sure if it's true.)
If it is not compressed, was it intended or did you forget?
:thanks:
THX,
forgot to compress. It's fixed.
Patman
23rd December 2019, 18:04
Thanks, Patman. Next built has the crop dialog using hw rendering as well which completes this work so maintenance (tool updates and user feedback) can continue now.
Nice to hear that. Let us continuing the work at the project ;)
JKyle
25th December 2019, 04:33
Well, rigaya is really at hard work even at this time of year.
NVEnc 4.59 is released today.
Here (https://github.com/rigaya/NVEnc/releases/tag/4.59).
- Fix vpp-subburn result getting colorless
Patman
25th December 2019, 21:44
VCEEnc has been updated too, 5.00...
Gesendet von meinem HMA-L09 mit Tapatalk
stax76
26th December 2019, 04:49
2.0.6.2
-------
- new: crop dialog supports harware accelerated video rendering
- fix: info feature in preview dialog is back
- fix: when a second preview was opened the first one had broken rendering
- fix: image was vertically flipped using preview dialog with VapourSynth
- fix: main window DPI scaling issue on 96 DPI, please post a screenshot
if you find something that doesn't look good!
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR
The info feature in the preview dialog misses some important info like color space and bit depth, vfw/avifile cannot access it, maybe it's time to let it go.
Is it worth to extract needed interfaces from DirectN? This would reduce disk space by factor 10, DirectN is 3,6 MB.
RainyDog
27th December 2019, 08:33
Thanks for the new build stax.
Hardware accelerated crop and preview is so much snappier!
A couple of minor bugs I've found are that images exported from the preview window are saved upside down.
Also, the save as PNG is still broken when in preview (with AVS at least, not tried VS). I came across this after Revan took over the reigns but when I reported it he claimed it was my system and not the program so not sure it was even looked into...
Mzvasturbo
27th December 2019, 09:16
Hi i would like some help with staxrip i read StaxRip 2.0 uses 10bit pipline. I use handbrake to rip my bluray remuxes but people say handbrake uses 8bit pipline and converts 10bit to 8bit and back to 10bit. So i made some testing staxrip handbrake comparing images and i saved the logs you can check here https://www.dropbox.com/sh/yabmid1mduiiibm/AAApMWJCziIeyNBMPUI5otsna?dl=0 I would like to check if there is some proper 10bit pipline decoding but i dont know what command to look in the logs can someone please help?
Is my staxrip proper 10bit decode? From the log data does handbrake realy converts 10bit to 8 bit?
stax76
27th December 2019, 14:41
Thanks for the new build stax.
Hardware accelerated crop and preview is so much snappier!
A couple of minor bugs I've found are that images exported from the preview window are saved upside down.
Also, the save as PNG is still broken when in preview (with AVS at least, not tried VS). I came across this after Revan took over the reigns but when I reported it he claimed it was my system and not the program so not sure it was even looked into...
Thanks for the feedback. This feature depends on avisynth or vapoursynth. I'll first replace the vfw/avifile interface with a more direct and powerful interface to avisynth and vapoursynth. StaxRip will then be able to directly query, use and show valuable info like color space and bit depth. I hope I can finish it in 1-2 weeks.
Hi i would like some help with staxrip i read StaxRip 2.0 uses 10bit pipline. I use handbrake to rip my bluray remuxes but people say handbrake uses 8bit pipline and converts 10bit to 8bit and back to 10bit. So i made some testing staxrip handbrake comparing images and i saved the logs you can check here https://www.dropbox.com/sh/yabmid1md...PUI5otsna?dl=0 I would like to check if there is some proper 10bit pipline decoding but i dont know what command to look in the logs can someone please help?
Is my staxrip proper 10bit decode? From the log data does handbrake realy converts 10bit to 8 bit?
In the log file the video encoder section should display if the input avs/vpy script is 10 bit. The log file has a avs/vpy script section which will soon display the output color space and bit depth.
All filters you used can work in 10 bit mode.
LoadPlugin("C:\Users\user\Downloads\StaxRip-x64-2.0.6.0-stable\Apps\Plugins\both\ffms2\ffms2.dll")
FFVideoSource("F:\Ready Player One - 2018\Ready Player One - 2018.mkv", cachefile="F:\Ready Player One - 2018\Ready Player One - 2018_temp\Ready Player One - 2018.ffindex")
#AssumeFPS(25)
Crop(0, 278, -0, -278)
--------- Video encoding using x265 3.2+9-971180b100f8 Patman ---------
C:\Users\user\Downloads\StaxRip-x64-2.0.6.0-stable\Apps\Support\avs2pipemod\avs2pipemod64.exe -y4mp F:\Ready Player One - 2018\Ready Player One - 2018_temp\Ready Player One - 2018_new.avs | C:\Users\user\Downloads\StaxRip-x64-2.0.6.0-stable\Apps\Encoders\x265\x265.exe --crf 20 --level-idc 5.1 --output-depth 10 --master-display "G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(40000000,50)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "725,162" --hdr --repeat-headers --hrd --aud --frames 201341 --y4m --output F:\Ready Player One - 2018\Ready Player One - 2018_temp\Ready Player One - 2018_new_out.hevc -
avs2pipemod[info]: writing 201341 frames of 24000/1001 fps, 3840x1604,
sar 0:0, YUV-420-planar-10bit progressive video.
y4m [info]: 3840x1604 fps 24000/1001 i420p10 unknown frame count
raw [info]: output file: F:\Ready Player One - 2018\Ready Player One - 2018_temp\Ready Player One - 2018_new_out.hevc
x265 [info]: HEVC encoder version 3.2+9-971180b100f8
x265 [info]: build info [Windows][GCC 9.2.0][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
x265 [warning]: Specifying a decoder level with constant rate factor rate-control requires
x265 [warning]: enabling VBV with vbv-bufsize=160000kb vbv-maxrate=160000kbps. VBV outputs are non-deterministic!
x265 [info]: Main 10 profile, Level-5.1 (High tier)
x265 [info]: Thread pool created using 8 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 3 / wpp(26 rows)
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 3
x265 [info]: Keyframe min / max / scenecut / bias: 23 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 3 / off / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-20.0 / 0.60
x265 [info]: VBV/HRD buffer / max-rate / init : 160000 / 160000 / 0.900
x265 [info]: tools: rd=3 psy-rd=2.00 early-skip rskip signhide tmvp b-intra
x265 [info]: tools: strong-intra-smoothing lslices=8 deblock sao
avs2pipemod[info]: finished, wrote 201341 frames [100%].
avs2pipemod[info]: total elapsed time is 93694.253 sec.
x265 [info]: frame I: 1727, Avg QP:19.38 kb/s: 27560.53
x265 [info]: frame P: 57175, Avg QP:20.98 kb/s: 15837.71
x265 [info]: frame B: 142439, Avg QP:24.27 kb/s: 7291.45
x265 [info]: Weighted P-Frames: Y:9.1% UV:6.8%
x265 [info]: consecutive B-frames: 21.9% 9.8% 7.5% 26.1% 34.7%
encoded 201341 frames in 93695.94s (2.15 fps), 9892.20 kb/s, Avg QP:23.29
Mzvasturbo
28th December 2019, 20:00
Ok Thank you. I will be using staxrip from now on it is realy great gui. One question yesterday i rip my alita bluray again and i manage to get hdr10+ with staxrip HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible but the original is HDR format: SMPTE ST 2094 App 4, Version 1, HDR10+ Profile A compatible i dont know why the profile is diferent i used hdr10plus_parser and i used hdr-opt / dhdr10-opt. I dont see any diference so i gues it is ok but if someone knows why profile is changed it is appreciated to know. The other thing is i dont know how to make small samples. I am used to work with handbrake where i just set the time duration of my rip however i want i cant find these settings in staxrip.
VincAlastor
29th December 2019, 10:39
Hello thank you for the update notification.
I have experimented with the SVT-AV1 encoder. Except that the cmd windows in staxrip freezes after 10.000 frames (but the encoding continues), there is a big problem.
I muxed the finished elementary stream in mkv. If I now play it and jump back or forward for more than 5 min, the player (with current LAVfilters) needs a lot of time until the playback continues.
If I download a youtube AV1 video in mp4 container the player doesn't need too much time to skip.
However, mp4box does not want to mux .opus streams, so I cannot really use the mp4 container. Do you have a solution?
ffmpeg -i "%script_file%" -nostdin -f rawvideo -pix_fmt yuv420p - | SvtAv1EncApp.exe -i stdin -fps-num 24000 -fps-denom 1001 -n %source_frames% -w %target_width% -h %target_height% -enc-mode 6 -q 50 -b "%encoder_out_file%"
And are there macros for fps-num/denom in staxrip?
edit:
if i mux youtube AV1 mp4 into mkv, i also can skip fast trough the file. So is there a SVT-AV1 bug?
Yanak
29th December 2019, 18:00
Hello,
Mp4box 0.9.x from the "Filters" Branch used in command line allows the opus and flac input for audio, last builds have some little issues tho.
Have not played much lately with regular version 0.8.x but pretty sure it is possible to add a .opus audio file with it too now ( flac input is only in 0.9.0 for sure ), changes were made around this summer if i recall correctly.
I'm not much into av1 and can't even test svt one but maybe this (and last comment for ffmpeg ) : https://github.com/OpenVisualCloud/SVT-AV1/issues/170#issuecomment-477785525 , there is quite a few discussions about jerky playback there tho.
VincAlastor
29th December 2019, 22:52
Hello,
Mp4box 0.9.x from the "Filters" Branch used in command line allows the opus and flac input for audio, last builds have some little issues tho.
Have not played much lately with regular version 0.8.x but pretty sure it is possible to add a .opus audio file with it too now ( flac input is only in 0.9.0 for sure ), changes were made around this summer if i recall correctly.
I'm not much into av1 and can't even test svt one but maybe this (and last comment for ffmpeg ) : https://github.com/OpenVisualCloud/SVT-AV1/issues/170#issuecomment-477785525 , there is quite a few discussions about jerky playback there tho.
thank you very much. That link was very helpful - the background hints about mp4 too.
ukmark
31st December 2019, 20:08
Apologies if this has been asked before (I have tried searching both here and on the net but can't find an answer).
Question: Does QuickSync HEVC support ICQ with Lookahead??
I'm running a Kaby Lake processor - i5-7200u, with Intel HD 620 graphics.
I believe it is supported in QuickSync H264? If it isn't supported, will Ice Lake support this feature?
I find QuickSync HEVC ICQ very acceptable, but Lookahead would improve it further.
Any info would be very much appreciated.
PS. StaxRip rocks!, best GUI I have ever used (and I have used them all!):)
EDIT: Lookahead is not supported with QSV HEVC - checked via my own testing using ffmpeg and QSV HEVC (the encoder rejects the "look_ahead 1" setting in the ffmpeg script). I can't find any info regarding if it will ever be implemented for QSV HEVC.
Salem874
1st January 2020, 15:26
Is it possibile to rip 3D Bluray discs to a SBS 3D video file (MP4/MKV) using StaxRip?
If so, are there any tutorials out there?
Mzvasturbo
2nd January 2020, 14:30
Sory for asking again but how can i make 30second or 1minute samples with staxrip. Because i realy dont want to encode whole movie and waste 50hours of rip time just to try different settings.
stax76
2nd January 2020, 15:26
Sory for asking again but how can i make 30second or 1minute samples with staxrip. Because i realy dont want to encode whole movie and waste 50hours of rip time just to try different settings.
You would disable audio processing by using 'No Audio' audio profiles and then either cut in the preview or use certain x265 IO encoder switches like:
--seek
--frames
--chunk-start
--chunk-end
Is it possibile to rip 3D Bluray discs to a SBS 3D video file (MP4/MKV) using StaxRip?
It might be possible, I don't think there are tutorials.
Tadanobu
2nd January 2020, 16:23
Sory for asking again but how can i make 30second or 1minute samples with staxrip. Because i realy dont want to encode whole movie and waste 50hours of rip time just to try different settings.
Use an AVS script. Add something like SelectRangeEvery (3000,40,1000)
stax76
2nd January 2020, 16:56
Use an AVS script. Add something like SelectRangeEvery (3000,40,1000)
If he wants to output 30 seconds than he needs Trim.
http://avisynth.nl/index.php/Trim
Tadanobu
2nd January 2020, 18:09
Well it depends of what he needs. Trim is good to have consecutive frames and match a specific length. SelectRangeEvery is good if you want to make a test encode and see how different scenes will be encoded. This is what I personally use when I want to select my options (crf, b-frames and so on).
Yanak
3rd January 2020, 08:53
Hello Stax,
Sorry to bother you but in regards to cropping window, previously in 1.7.0.6 we could do this :
https://streamable.com/dmchx
Going far starting from one side,
now in 2.0.6.2 we are limited and for example cannot go past a certain crop distance from the right border, it is like this now for max cropping :
https://streamable.com/98v5d
I'm not sure if it's a limitation of the new renderer or something wrong on my side yet but the cropping using the crop tool is quite limited now.
--------------------------
- Another thing that comes to my mind as i saw it already reported a few times is about mp4box muxing and mediainfo displaying the streamtype+mp4box build version in the title for the video stream.
I rarely leave those options visible for my encodes as i use the "-for-test" switch in my mp4box custom muxing profiles, this switch removes those specific build infos but also the "Encoded date" & "Tagged date" data from the mp4.
Right now the command line in staxrip adds this for audio stream ' :name=" ' so nothing is displayed for it in mediainfo unless a tittle is added manually,
why not add the same thing for the video stream, and unless some input title is added in the container option just leave it like this ?
Like i said i remove all those data using "-for-test" switch to get a more generic output in my encoding but as i saw a few posts about this searching something else on forum yesterday...
--------------------
Another thing please : could you please allow the .bmp extension for cover picture in the MKV container options please, right now only jpg & png are allowed via the browse files selector ( if needed I'll add this as request to github page, just let me know )
Also MKVtoolnix was released in v42.0.0 yesterday
Thanks a lot :)
stax76
3rd January 2020, 12:04
Hello Yanak, thank you for the feedback. Recently it's difficult for me to follow all requests, if there is something important please use the issue tracker, I'll catch up later. I'm currently working on new staxrip features but not using VB.NET and .NET framework but rather C++ and Win32, this is very interesting but since I don't have much experience in that area it will take few more weeks to finish. After that not only staxrip maintenance will continue but also mpv.net and few other tools.
Yanak
3rd January 2020, 15:14
Hi Stax, thanks for the reply.
Added a few reports on the github, sorry for spamming issues there, there is no hurry, i still have 1.7.0.6 with most tools updated so for things like visual cropping i can use it or something else no worries.
Wondering what you will bring to Staxrip man, as for those coding languages well i can't help you with this sadly, barely manage powershell now, thanks to you who put me into this btw, learned quite a few things with your help on this forum and the old staxrip github :)
( BTW where did the old github for staxrip has gone, deleted or hidden in a private repo now ? Issues section had quite a lot of useful things in it )
Anyways no worries and thanks for all, glad to see you working again on this fantastic tool.
stax76
3rd January 2020, 16:12
I'm replacing the interface to AviSynth and VapourSynth, currently it is accessed via a Windows API called VFW/AVIFile, there are some limitations, so I'm building a replacement accessing AviSynth and VapourSynth more directly via wrapper library.
VapourSynth might be accessible directly from .NET because it has a C interface, I don't think it's possible with AviSynth, so I build a wrapper library exposing basic AviSynth and VapourSynth functionality via common COM+ interface IFrameserver. I've also built a C++/classic Win32 GUI app for learning and testing all this and for fun, source code will be available.
It probably will only bring small improvements to StaxRip, often I do projects just to learn something new and have fun, there are three languages important on Windows: PowerShell, C# and C++.
Another thing I want to investigate is rendering YV12 directly with Direct2D instead of converting it to RGB beforehand.
Sometime later this year or next year I want to improve documentation and possible add chunk encoding support for x265, about SVT-AV1 I'm skeptical, see rant here:
https://github.com/OpenVisualCloud/SVT-AV1/issues/779
BTW where did the old github for staxrip has gone, deleted or hidden in a private repo now ? Issues section had quite a lot of useful things in it
It's gone mostly due to my own git/github incompetence, I'm still a total noob with that struggling every time I do a simple task like creating a repo, sorry for deleting it. I think it was the second most popular VB.NET project with 350 stars.
Atak_Snajpera
3rd January 2020, 16:34
https://github.com/OpenVisualCloud/SVT-AV1/issues/779
I would also add that all new encoders should just clone progress output style from x264/x265.
[85.1%] 9323/10961, 24.96 fps, 993.49 kbps, eta 0:01:08
encoded 1438 frames, 825.96 fps, 993.49 kbps
I really do not understand why they have to invent a wheel each time?
Yanak
3rd January 2020, 16:59
I came across your rant on the link some days ago yeah and it is logical for many, svt-av1 is out of reach for me, needed cpu hardware and what i could read for RAM needs at high resolution too... but it might interest a lot of people since av1 seems to become more common, when i see the speeds i get using rav1e, including last 2.0 version where there is a good speed boost... well my hardware is old and money drains directly into other things, replacement of hardware is not for anytime soon sadly...
I started to put more my hands into coding stuff but mostly lack of time to put into all this or sometimes getting out of the country for 3-4weeks and not even have a pc there, just barely any internet to check news and mails on my phone is breaking all this, right now i profit of the winter to update all my tools first then will start to mess with other little things if time allows it...
For me StaxRip is the best tool for video encoding and other things possible in it with all the macros and liberty you gave us to implement our own things, it's good to see you always improving it, thanks for that.
Sad to know that the repo with all issues is gone, it had a lot of stars indeed and a load of nice tips from you regarding the usage and customization of StaxRip in the issues section, but no worries i am even more a noob with github and probably struggling even more with it, at least they made private repo's possible now so i can try to mess up things there when i have time :p
Btw in previous pages you said you did not know what you will look into next, if you remember you helped me quite a bit to make this in 1.7 or 1.6 maybe, just uploaded it as it might serve some others too :
https://github.com/jalba69/Staxrip_Stuff/tree/master/Create_Chapters
It's probably ugly from a real coder point of view but it works,
added as a new menu entry from the preview window mode, either executing directly the script or "ExecutePowerShellScript" with script content inside it, it allows to easily create chapters from the preview mode,
the chapters file is created in the temp folder and have the name "Custom_Chapters.txt" to not mess with a possible already existing chapter that had been demuxed,
then once done it needs to be selected manually in the container muxing options for mkv or mp4 ( could have a custom muxing profile set but paths for chapters not allow macros there sadly ), but it works and does the job for creating chapters easily in staxrip ^^
If one day you have no more ideas it might be something to look at and implement in a better way as native function in the preview mode... :p
Like i said it's good to see you back into this man.
Tadanobu
3rd January 2020, 18:33
If we're talking about chunk encoding and av1, please, please, do it for libaom. You'll be our hero ! Everybody at av1 Discord will be glad.
SVT AV1 is nice because it's fast. But libaom is way better than rav1e and SVT AV1. Also libaom is already supported by ffmpeg (or you can use aomenc.exe to have more options available).
MrBrownCow
4th January 2020, 09:02
Can anyone help me verify what I might be doing wrong for crop settings? I've tried 2.0.4.0, 2.0.6.0 and now 2.0.6.2 but I seem to be getting the wrong crop. It keeps picking 1032 for height and I think it should be 1040. Do i have my aspect ratio settings wrong or something?
https://imgur.com/a/efkKoJi
Thank you in advance!
VincAlastor
4th January 2020, 12:32
Sometime later this year or next year I want to improve documentation and possible add chunk encoding support for x265, about SVT-AV1 I'm skeptical, see rant here:
i also would please you to prefer libaom for "Splitting video in parts and encode it in parallel"
Thank you.
Yanak
5th January 2020, 20:20
Can anyone help me verify what I might be doing wrong for crop settings? I've tried 2.0.4.0, 2.0.6.0 and now 2.0.6.2 but I seem to be getting the wrong crop. It keeps picking 1032 for height and I think it should be 1040. Do i have my aspect ratio settings wrong or something?
https://imgur.com/a/efkKoJi
Thank you in advance!
Hello,
I'm not sure if i am missing something but in your 2nd screenshot i see it's 24 pixels cropped on top and bottom so 48 pixels total, input is 1080px, so 1080-48 = 1032px, to get 1040px you need to remove 20 px on top and bottom.
If there is an issue with setting 20 pixels i guess the setting "Output mod" in the first screenshot could be switched from 8 to 4 to allow it, just a guess.
frenchfries
6th January 2020, 01:37
Apologies if this has been asked before (I have tried searching both here and on the net but can't find an answer).
Question: Does QuickSync HEVC support ICQ with Lookahead??
I'm running a Kaby Lake processor - i5-7200u, with Intel HD 620 graphics.
I believe it is supported in QuickSync H264? If it isn't supported, will Ice Lake support this feature?
I find QuickSync HEVC ICQ very acceptable, but Lookahead would improve it further.
Any info would be very much appreciated.
PS. StaxRip rocks!, best GUI I have ever used (and I have used them all!):)
EDIT: Lookahead is not supported with QSV HEVC - checked via my own testing using ffmpeg and QSV HEVC (the encoder rejects the "look_ahead 1" setting in the ffmpeg script). I can't find any info regarding if it will ever be implemented for QSV HEVC.
Pretty sure this is in error. I use this all the time with high amounts of reference frames and and b frames to boot. The hardware doesn't seem very affected by the high numbers like X265 is.
My command line is below
--avhw --codec hevc --quality best --profile main10 --la-quality slow --la-window-size 15 --bframes 6 --ref 9 --b-pyramid --icq 17
Forteen88
6th January 2020, 02:42
I don't see how this is a real problem, 0 probably stands for undefined which should effectively be identical to 1. The concept of undefined/nothing/null/whatever often makes the world more complex than it needs to be, staxrip is here to simplify things.
edit:
to force writing the PAR it's possible to add a custom command:
--sar %target_par_x%:%target_par_y%
This is relative new so might require using the last beta.--sar 1:1 doesn't stand for undefined, at least according to this site,
--sar <integer|w:h>
Sample Aspect Ratio, the ratio of width to height of an individual sample (pixel). The user may supply the width and height explicitly or specify an integer from the predefined list of aspect ratios defined in the HEVC specification. Default undefined (not signaled)
1. 1:1 (square)
2. 12:11https://x265.readthedocs.io/en/default/cli.html
ukmark
6th January 2020, 16:11
Pretty sure this is in error. I use this all the time with high amounts of reference frames and and b frames to boot. The hardware doesn't seem very affected by the high numbers like X265 is.
My command line is below
--avhw --codec hevc --quality best --profile main10 --la-quality slow --la-window-size 15 --bframes 6 --ref 9 --b-pyramid --icq 17
Thanks for your reply. I'm referring specifically to the "LA-ICQ" mode that is available for QSV H264 (along with 2 other "LA" modes - "LA" and "LA-HRD" ).
With QSV HEVC there are no such "LA" modes. Wouldn't the encoder just ignore the "la-quality" and "la-window-size" options when using "ICQ" for QSV HEVC?
My best guess is that these settings would be 'activated' when using the "LA" modes for QSV H264 but 'ignored' for QSV HEVC?? I'll try your settings, run a quick test and look in the StaxRip log to see if these 2 "la" settings are mentioned when using QSV H264 and QSV HEVC.
EDIT: Just did a quick test on a very short clip using these 2 "la" settings ("la-quality slow" and "la-window-size 15"). I noticed that when choosing "LA-ICQ" for QSV H264 an extra setting appeared in the "Slice Decision" settings in the StaxRip GUI that is not shown when choosing "ICQ" for QSV HEVC - namely "Lookahead Depth". Also in the StaxRip log for "LA-ICQ" QSV H264 I see the following section where it mentions the "Lookahead" settings for depth and quality (but not window size), but this line is not present when using "ICQ" QSV HEVC. This would lead me to believe that QSV HEVC has not (yet) implemented "lookahead".
From StaxRip QSV encoding log:-
Output H.264/AVC High @ Level 4
1280x720p 1:1 23.976fps (24000/1001fps)
Target usage 1 - best
Encode Mode LA-ICQ (Intelligent Const. Quality with Lookahead)
Lookahead depth 30 frames, quality slow <------- This line does not appear when using QSV HEVC ICQ settings with "la-quality slow" and "la-window-size 15".
I find that QSV HEVC ICQ is very good and just wish the LA-ICQ was implemented for HEVC as it is with H264. It may give that extra bit of quality (at similar bitrates to x265) that would make me switch from CPU software encoding to GPU hardware encoding (I notice the difference between the two mainly in dark scenes). I'm tempted to get a 10th gen Ice Lake laptop as Intel have touted some big improvements for QuickSync - but I'll wait until we get more info as time goes by. I'm hoping in a few more Intel 'generations' that GPU encoding could become the norm (due to competition from Ryzen, NVidia and from consumer demand etc).
frenchfries
8th January 2020, 03:34
Thanks for your reply. I'm referring specifically to the "LA-ICQ" mode that is available for QSV H264 (along with 2 other "LA" modes - "LA" and "LA-HRD" ).
With QSV HEVC there are no such "LA" modes. Wouldn't the encoder just ignore the "la-quality" and "la-window-size" options when using "ICQ" for QSV HEVC?
My best guess is that these settings would be 'activated' when using the "LA" modes for QSV H264 but 'ignored' for QSV HEVC?? I'll try your settings, run a quick test and look in the StaxRip log to see if these 2 "la" settings are mentioned when using QSV H264 and QSV HEVC.
EDIT: Just did a quick test on a very short clip using these 2 "la" settings ("la-quality slow" and "la-window-size 15"). I noticed that when choosing "LA-ICQ" for QSV H264 an extra setting appeared in the "Slice Decision" settings in the StaxRip GUI that is not shown when choosing "ICQ" for QSV HEVC - namely "Lookahead Depth". Also in the StaxRip log for "LA-ICQ" QSV H264 I see the following section where it mentions the "Lookahead" settings for depth and quality (but not window size), but this line is not present when using "ICQ" QSV HEVC. This would lead me to believe that QSV HEVC has not (yet) implemented "lookahead".
From StaxRip QSV encoding log:-
Output H.264/AVC High @ Level 4
1280x720p 1:1 23.976fps (24000/1001fps)
Target usage 1 - best
Encode Mode LA-ICQ (Intelligent Const. Quality with Lookahead)
Lookahead depth 30 frames, quality slow <------- This line does not appear when using QSV HEVC ICQ settings with "la-quality slow" and "la-window-size 15".
I find that QSV HEVC ICQ is very good and just wish the LA-ICQ was implemented for HEVC as it is with H264. It may give that extra bit of quality (at similar bitrates to x265) that would make me switch from CPU software encoding to GPU hardware encoding (I notice the difference between the two mainly in dark scenes). I'm tempted to get a 10th gen Ice Lake laptop as Intel have touted some big improvements for QuickSync - but I'll wait until we get more info as time goes by. I'm hoping in a few more Intel 'generations' that GPU encoding could become the norm (due to competition from Ryzen, NVidia and from consumer demand etc).
Thanks for clarifying. The LA mode for H265 definitely doesn't exist. Disregard all I said about that. I actually knew this but clearly forgot :/
You can see it in a trimmed --check-features i just ran
Codec: HEVC
CBR VBR AVBR QVBR CQP LA LAHRD ICQ LAICQ VCM
RC mode o o x x o x x o x o
10bit depth o o x x o x x o x o
Fixed Func x x x x x x x x x x
Interlace x x x x o x x x x x
VUI info o o x x o x x o x o
Trellis x x x x x x x x x x
Adaptive_I x x x x x x x x x x
Adaptive_B x x x x x x x x x x
WeightP o o x x o x x o x o
WeightB o o x x o x x o x o
FadeDetect x x x x x x x x x x
B_Pyramid o o x x o x x o x o
+ManyBframes o o x x o x x o x o
PyramQPOffset x x x x o x x x x x
MBBRC o o x x x x x o x o
ExtBRC o o x x x x x x x x
Adaptive_LTR x x x x x x x x x x
LA Quality x x x x x x x x x x
QP Min/Max x x x x x x x x x x
IntraRefresh o o x x o x x o x o
No Deblock o o x x o x x o x o
No GPB o o x x o x x o x o
Windowed BRC x x x x x x x x x x
PerMBQP(CQP) o o x x x x x o x o
DirectBiasAdj x x x x x x x x x x
MVCostScaling x x x x x x x x x x
SAO x x x x x x x x x x
Max CTU Size x x x x x x x x x x
TSkip x x x x x x x x x x
That being said, I'm surprised you see it as lower quality output then with X265 as I see the reverse using the settings i previously posted and with X265 with little tuning using a CRF of 18 and slower.
Quicksync seems to finish in around 4 hours or so with a smaller file size and subjectively better quality using stax's video compare tool, than X265 which takes a couple of days.
I only have access to 24 threads at home so maybe more oomph is required but TBH that's too power prohibitive for me.
ukmark
8th January 2020, 11:43
Thanks for clarifying. The LA mode for H265 definitely doesn't exist. Disregard all I said about that. I actually knew this but clearly forgot :/
You can see it in a trimmed --check-features i just ran
Codec: HEVC
CBR VBR AVBR QVBR CQP LA LAHRD ICQ LAICQ VCM
RC mode o o x x o x x o x o
10bit depth o o x x o x x o x o
Fixed Func x x x x x x x x x x
Interlace x x x x o x x x x x
VUI info o o x x o x x o x o
Trellis x x x x x x x x x x
Adaptive_I x x x x x x x x x x
Adaptive_B x x x x x x x x x x
WeightP o o x x o x x o x o
WeightB o o x x o x x o x o
FadeDetect x x x x x x x x x x
B_Pyramid o o x x o x x o x o
+ManyBframes o o x x o x x o x o
PyramQPOffset x x x x o x x x x x
MBBRC o o x x x x x o x o
ExtBRC o o x x x x x x x x
Adaptive_LTR x x x x x x x x x x
LA Quality x x x x x x x x x x
QP Min/Max x x x x x x x x x x
IntraRefresh o o x x o x x o x o
No Deblock o o x x o x x o x o
No GPB o o x x o x x o x o
Windowed BRC x x x x x x x x x x
PerMBQP(CQP) o o x x x x x o x o
DirectBiasAdj x x x x x x x x x x
MVCostScaling x x x x x x x x x x
SAO x x x x x x x x x x
Max CTU Size x x x x x x x x x x
TSkip x x x x x x x x x x
That being said, I'm surprised you see it as lower quality output then with X265 as I see the reverse using the settings i previously posted and with X265 with little tuning using a CRF of 18 and slower.
Quicksync seems to finish in around 4 hours or so with a smaller file size and subjectively better quality using stax's video compare tool, than X265 which takes a couple of days.
I only have access to 24 threads at home so maybe more oomph is required but TBH that's too power prohibitive for me.
Thanks. I just tried your settings. For x265 I usually have 720p 10bit HEVC, CRF 24 and AQ-Mode 3, preset Medium as the extra settings - this gives me very good quality. Maybe with an ICQ of 17 vs x265 CRF 18, the bit rates are increased enough to the point where QSV is at least as good as x265 - I just find that CRF24 for x265 gives me very good quality and was hoping that ICQ 24 would do the same at similar bit rates - and it does in all but darker scenes.
I did try comparing an encode with your settings using ICQ 24 (= CRF 24??) and although the QSV was very good, it did lose some definition in the darker muddier scenes. In the brighter scenes it was as good as x265 and encoded about 6x faster. I'm checking the output using my laptop and getting very close to the screen - I would think that normal viewing on a TV would probably not show a difference - but I'm picky about dark scenes:scared:
I might try lowering the ICQ to see where the dark scenes match the quality of x265 and then see what the final bit rates are. I don't mind QSV being larger file size but I don't want it to be double the size of x265. I probably only encode about 3 times per week, so speed is not that important to me - but I am seeing that QSV is getting close to x265 at my CRF of 24.
frenchfries
11th January 2020, 02:43
Thanks. I just tried your settings. For x265 I usually have 720p 10bit HEVC, CRF 24 and AQ-Mode 3, preset Medium as the extra settings - this gives me very good quality. Maybe with an ICQ of 17 vs x265 CRF 18, the bit rates are increased enough to the point where QSV is at least as good as x265 - I just find that CRF24 for x265 gives me very good quality and was hoping that ICQ 24 would do the same at similar bit rates - and it does in all but darker scenes.
I did try comparing an encode with your settings using ICQ 24 (= CRF 24??) and although the QSV was very good, it did lose some definition in the darker muddier scenes. In the brighter scenes it was as good as x265 and encoded about 6x faster. I'm checking the output using my laptop and getting very close to the screen - I would think that normal viewing on a TV would probably not show a difference - but I'm picky about dark scenes:scared:
I might try lowering the ICQ to see where the dark scenes match the quality of x265 and then see what the final bit rates are. I don't mind QSV being larger file size but I don't want it to be double the size of x265. I probably only encode about 3 times per week, so speed is not that important to me - but I am seeing that QSV is getting close to x265 at my CRF of 24.
Try messing with the amount of ref frames and b frames. That's where the smaller file sizes come into it. I've tested considerably higher amounts of both before with only a small performance decrease but diminishing returns kicks in and it doesn't get much smaller.
What profile in QSV are you using? eg. fastest or best
Interesting that you don't seem happy with dark scenes. That's where i do a lot of my subjective analysis as it's the most obvious to compare but my results are the opposite, at least with the settings I use.
Mzvasturbo
12th January 2020, 14:06
Sory for asking again but how can i make 30second or 1minute samples with staxrip. Because i realy dont want to encode whole movie and waste 50hours of rip time just to try different settings.
It is hard to find a simple tool to trim a 4k hdr remux.
So after trying diferent things i found out mkvtoolnix can do the job.
Now i am playing with hevc adaptive quantization and my movie rips are getting smaller and smaller :)
Yanak
12th January 2020, 17:34
This comes maybe too late but simply use trim in Staxrip :
- Load a video into Staxrip
- Open the preview mode
- Move the slider at the bottom to the start of a test scene you want to encode or cut
- Right click in the preview window to bring the menu then :
- "Cut" > "Begin Selection" ( Home key shortcut)
- Move slider to the end of the scene or navigate using shortcuts and from the Menu > "Cut" > "End selection" ( End key shortcut )
- Close the preview mode, the video is trimmed.
From there launch the encode with your encoder test settings, only this selected section of the video will be done, or you can also cut it into a new video without re-encoding like mkvtoolnix have done for you :
just need to select "MKV" as output container and "Copy/Mux" in the list instead of x264 or x265 encoder,
same for the audio track if you want to keep it use "Copy/Mux" instead of opus or whatever audio codec is set, but as it's a video encoding test probably going with "No Audio " will be better.
Like i said a bit late but might serve :p
chipxtreme
13th January 2020, 20:53
NVEnc 4.60 is out
neo_sapien
13th January 2020, 21:54
I've been getting this error for about a year or so when using the latest StaxRip, most recently when using version 2.0.6.0. Often when I get the error, it's a bummer because it's during 30 hour encodes of film sources, using QTGMC Slower to stabilize the film grain (which can reduce the bitrate needed by up to 75% with some film sources without smoothing out the rest of the details too much), at the cost of reducing my encoding speed to about 3fps on my Ryzen 1700X (with x265 Slow).
Here's the error I'm getting:
------ Error Video encoding using x265 3.2+9-971180b100f8 Patman ------
Video encoding using x265 3.2+9-971180b100f8 Patman failed with exit code: -1073741819 (0xC0000005)
The exit code might be a system error code: The instruction at 0xp referenced memory at 0xp. The memory could not be s.
Help?
More info: The issue pops up at random, it's not really reproducible. If I try to encode it again, I might get no crashes, or it might crash at a different point, there's little chance that it would crash at exactly the same frame (it would be like lightning striking in the same place twice). Here's another bit of error code:
avs2pipemod[info]: finished, wrote 9461 frames [85%].
avs2pipemod[info]: total elapsed time is 1182.232 sec.
avs2pipemod[error]: only wrote 9461 of 11004 frames.
Patman
13th January 2020, 22:12
I've been getting this error for about a year or so when using the latest StaxRip, most recently when using version 2.0.6.0. Often when I get the error, it's a bummer because it's during 30 hour encodes of film sources, using QTGMC Slower to stabilize the film grain (which can reduce the bitrate needed by up to 75% with some film sources without smoothing out the rest of the details too much), at the cost of reducing my encoding speed to about 3fps on my Ryzen 1700X (with x265 Slow).
Here's the error I'm getting:
------ Error Video encoding using x265 3.2+9-971180b100f8 Patman ------
Video encoding using x265 3.2+9-971180b100f8 Patman failed with exit code: -1073741819 (0xC0000005)
The exit code might be a system error code: The instruction at 0xp referenced memory at 0xp. The memory could not be s.
Help?
Hi neo_sapien,
an error like your's was posted here (http://forum.doom9.org/showthread.php?p=1887946#post1887946). A bios update of the mainboard fixed that issue for Tom.
neo_sapien
13th January 2020, 22:48
Hi neo_sapien,
an error like your's was posted here (http://forum.doom9.org/showthread.php?p=1887946#post1887946). A bios update of the mainboard fixed that issue for Tom.
I tried a BIOS update a while back. I also tried doing an extensive memtest86 check on my memory (I think it was 24 hours or more). When I upgraded to StaxRip 2.0.6.0 it stopped for a while, and I thought the issue was resolved, and then recently it came back.
Patman
13th January 2020, 23:20
I tried a BIOS update a while back. I also tried doing an extensive memtest86 check on my memory (I think it was 24 hours or more). When I upgraded to StaxRip 2.0.6.0 it stopped for a while, and I thought the issue was resolved, and then recently it came back.
The error code returns a hardware failure or hardware problem.
Maybe it helps if you test it with staxrip 2.0.6.2 or updated x265 from my sig. Reinstall vcredist (https://github.com/abbodi1406/vcredist/releases/latest)...
MrBrownCow
14th January 2020, 21:34
The error code returns a hardware failure or hardware problem.
Maybe it helps if you test it with staxrip 2.0.6.2 or updated x265 from my sig. Reinstall vcredist (https://github.com/abbodi1406/vcredist/releases/latest)...
@@Patman I'm sure you have said before but can you verify what the difference is between the x265 and x265 custom builds you have please? Not sure which one to use for win 10 64bit and 2.0.6.2 staxrip.
Patman
14th January 2020, 23:20
@@Patman I'm sure you have said before but can you verify what the difference is between the x265 and x265 custom builds you have please? Not sure which one to use for win 10 64bit and 2.0.6.2 staxrip.
Hi MrBrownCow,
look here
http://forum.doom9.org/showthread.php?p=1886119#post1886119
http://forum.doom9.org/showthread.php?p=1886190#post1886190
better feedback during encoding progress...
ukmark
15th January 2020, 23:17
Try messing with the amount of ref frames and b frames. That's where the smaller file sizes come into it. I've tested considerably higher amounts of both before with only a small performance decrease but diminishing returns kicks in and it doesn't get much smaller.
What profile in QSV are you using? eg. fastest or best
Interesting that you don't seem happy with dark scenes. That's where i do a lot of my subjective analysis as it's the most obvious to compare but my results are the opposite, at least with the settings I use.
Hi again. I have messed with b and ref frames and from very quick testing I upped both ref and b frames to 16 (although QSV encoder sets a max of 15 for ref frames during the encode). With these values so high I was able to lower the ICQ to 22 and get about the same file size as CRF 24 with x265 (10bit HEVC for both). I always use the "best" quality setting for QSV HEVC.
Encode times did not increase a lot - still about 5x faster than x265 software encoding.
I have just ordered a new Intel i7-1065G7 laptop so I will be testing again when that comes. I'm sure encode times will improve substantially from my current i5-7200u PC. However, I'm much more interested to see if visual quality has improved.
The comparison tool in StaxRip is a great aid, as I believe you recommended it. When comparing side by side the x265 with the QSV encodes, I see VERY slightly more detail in some scenes on the x265 encode - but this is not global - only on some scenes - and the difference is only noticeable on these freeze frames in the comparison tool - and unnoticeable during normal playback on my laptop.
So, all in all, when the new PC comes I will be defaulting to QSV HEVC - the settings are 10 bit, quality best, b-frames and ref frames 16 and icq 22
Maybe with the new version 7 of QS that has been introduced with 10th gen Ice Lake laptops, there will be that extra bit of quality. I plan on testing that.
Not sure if StaxRip has to be modified if there are any new settings available with version 7 of QS - time will tell.
frenchfries
16th January 2020, 11:44
Hi again. I have messed with b and ref frames and from very quick testing I upped both ref and b frames to 16 (although QSV encoder sets a max of 15 for ref frames during the encode). With these values so high I was able to lower the ICQ to 22 and get about the same file size as CRF 24 with x265 (10bit HEVC for both). I always use the "best" quality setting for QSV HEVC.
Encode times did not increase a lot - still about 5x faster than x265 software encoding.
I have just ordered a new Intel i7-1065G7 laptop so I will be testing again when that comes. I'm sure encode times will improve substantially from my current i5-7200u PC. However, I'm much more interested to see if visual quality has improved.
The comparison tool in StaxRip is a great aid, as I believe you recommended it. When comparing side by side the x265 with the QSV encodes, I see VERY slightly more detail in some scenes on the x265 encode - but this is not global - only on some scenes - and the difference is only noticeable on these freeze frames in the comparison tool - and unnoticeable during normal playback on my laptop.
So, all in all, when the new PC comes I will be defaulting to QSV HEVC - the settings are 10 bit, quality best, b-frames and ref frames 16 and icq 22
Maybe with the new version 7 of QS that has been introduced with 10th gen Ice Lake laptops, there will be that extra bit of quality. I plan on testing that.
Not sure if StaxRip has to be modified if there are any new settings available with version 7 of QS - time will tell.
I'm glad the ref and b frames worked out for you.
I am extremely interested in your results with your forthcoming ice lake system as I was looking to do some tests with some hardware from work as well when it becomes available.
Please post your findings regarding absolute performance as well as any potential quality increases, although the latter is obviously likely to be anecdotal.
Intel has publicly stated that there is an ~2x performance increase for Ice Lake as well as 422 and 444 support, which probably is of no use to most people. However, the new hardware HDR tone mapping may appeal to some, particularly when used in conjunction with real time transcodes such as with plex or emby.
I am unaware of any quality changes as i think the doubling of EUs and duplicated decoders as well as an EU cache bump is what brings the performance gain.
EDIT - There may actually be some changes as Ice Lake has support for HEVC using only the media engines without using the shaders i.e. low power mode which does not exist in Kaby, coffee, comet etc.
Tiger Lake though is a different beast, as I believe it will double again i.e. ~4x speed of Kaby Lake but is supposed to have new HEVC units and wait for it, AV1 encode support. My concern is that the new HEVC hardware may make for a step back in quality. I suppose we'll see towards the end of the year supposedly, although I really expecting a launch early 2021.
The biggest news for me would be the release of the LP versions of Xe as I hope they simply copy the media units or even duplicate them again for extra performance as I would love to transcode directly on my server rather than having to do it on my laptop.
chipxtreme
17th January 2020, 11:34
NVEnc 4.61 is out
Taurus
17th January 2020, 14:57
@all:
If someone is doing a manual update:
NVEnc 4.61 & NVEnc 4.60 are throwing an exception on my machine.
4.59 and former are doing nice.
Just to be warned.....
No time for troubleshooting at the moment.
This is on Win7 64bit (what else?)
neo_sapien
18th January 2020, 06:52
The error code returns a hardware failure or hardware problem.
Maybe it helps if you test it with staxrip 2.0.6.2 or updated x265 from my sig. Reinstall vcredist (https://github.com/abbodi1406/vcredist/releases/latest)...
I tried Staxrip 2.0.6.2 and reinstalling vcredist but still get the same error, so I'm trying a workaround; splitting the encode into segments using Preview and Cut Points. If I'm encoding content that has 200,000 frames, then I might do it like this without audio or chapters or subtitles:
Job 1: frame 1 to 35,000
Job 2: frame 35,001 to 70,000
Job 3: frame 70,001 to 105,000
Job 4: frame 105,001 to 140,000
Job 5: frame 140,001 to 175,000
Job 6: frame 175,001 to 200,000
Then append parts 1 through 6 in MKVToolNix GUI and add audio, chapters and subtitles to make the content whole again. This way if I get an error in a 25 hour encode when I'm 80% in, I haven't lost 20 hours of CPU time with nothing to show for it.
Is this a reasonable way to go about it? I was worried that this might result in async audio.
chipxtreme
19th January 2020, 01:01
@all:
If someone is doing a manual update:
NVEnc 4.61 & NVEnc 4.60 are throwing an exception on my machine.
4.59 and former are doing nice.
Just to be warned.....
No time for troubleshooting at the moment.
This is on Win7 64bit (what else?)
4.61 works fine for me, Win 10 64 bit, Ryzen 3900X and 1070 GPU.
ukmark
19th January 2020, 16:02
I'm glad the ref and b frames worked out for you.
I am extremely interested in your results with your forthcoming ice lake system as I was looking to do some tests with some hardware from work as well when it becomes available.
Please post your findings regarding absolute performance as well as any potential quality increases, although the latter is obviously likely to be anecdotal.
Intel has publicly stated that there is an ~2x performance increase for Ice Lake as well as 422 and 444 support, which probably is of no use to most people. However, the new hardware HDR tone mapping may appeal to some, particularly when used in conjunction with real time transcodes such as with plex or emby.
I am unaware of any quality changes as i think the doubling of EUs and duplicated decoders as well as an EU cache bump is what brings the performance gain.
EDIT - There may actually be some changes as Ice Lake has support for HEVC using only the media engines without using the shaders i.e. low power mode which does not exist in Kaby, coffee, comet etc.
Tiger Lake though is a different beast, as I believe it will double again i.e. ~4x speed of Kaby Lake but is supposed to have new HEVC units and wait for it, AV1 encode support. My concern is that the new HEVC hardware may make for a step back in quality. I suppose we'll see towards the end of the year supposedly, although I really expecting a launch early 2021.
The biggest news for me would be the release of the LP versions of Xe as I hope they simply copy the media units or even duplicate them again for extra performance as I would love to transcode directly on my server rather than having to do it on my laptop.
Received the i7 10th gen laptop. Brief testing - very strange results with QSV HW encoding. The graphics driver version really makes a huge difference and has been flaky. The Lenovo driver (non-DCH) and the latest Intel driver (DCH) give different results. It seems that the drivers will have to be improved over the next few months. I had one occasion (doing a test on 2 mins of video) where the output was noticeably different between the first and second test - same input file, same driver, same settings etc - I can't figure that one out, but I swear nothing changed - apart from the output quality getting better. The speed increase is about 70% for HW encoding. The API version used by QSV is now 1.30, on KL it was 1.27 and there are some extra features auto plugged into the encode settings - tskip is new setting, sao is now set to "all" (was "none" on KL), CTU is now 64 (was 32 on KL).
Another observation is that ICQ 22 on Kaby Lake seems the same as ICQ 19 on Ice Lake(!) with the current Ice Lake driver. I used the same input file with the same settings and encoded a QSV HEVC video on Ice Lake with the exact same settings as Kaby Lake (ICQ 22 and all the extra settings identical), and the file was 35% smaller(!). At first I thought maybe quality had somehow been magically maintained with a 35% smaller file - but no, the quality was noticeably inferior on Ice Lake. To get the same video bit rate, I had to lower the ICQ value from 22 to 19 on Ice Lake (flaky drivers again??)
For SW encoding I'm getting about triple the speed (pleased with that) - and the quality is identical to Kaby Lake (which it should be as the graphics driver is not used in SW encoding AFAIK).
I think once the drivers get improved, then QSV HW encoding looks promising. I'm seeing some excellent quality (at times), but as I say, the graphics drivers seem flaky right now.
Patman
19th January 2020, 19:07
I tried Staxrip 2.0.6.2 and reinstalling vcredist but still get the same error, so I'm trying a workaround; splitting the encode into segments using Preview and Cut Points. If I'm encoding content that has 200,000 frames, then I might do it like this without audio or chapters or subtitles:
Job 1: frame 1 to 35,000
Job 2: frame 35,001 to 70,000
Job 3: frame 70,001 to 105,000
Job 4: frame 105,001 to 140,000
Job 5: frame 140,001 to 175,000
Job 6: frame 175,001 to 200,000
Then append parts 1 through 6 in MKVToolNix GUI and add audio, chapters and subtitles to make the content whole again. This way if I get an error in a 25 hour encode when I'm 80% in, I haven't lost 20 hours of CPU time with nothing to show for it.
Is this a reasonable way to go about it? I was worried that this might result in async audio.
Change your x265.exe with a version from here (http://msystem.waw.pl/x265/) and test again.
neo_sapien
20th January 2020, 09:21
Change your x265.exe with a version from here (http://msystem.waw.pl/x265/) and test again.
I tried using 3.2.1+3-b4b2eca VS 2019 AVX2 from the stable branch. I encountered this error. (I'm trying to modify the below text to keep from breaking the tables too bad)
--------- Error Video encoding using x265 3.2.1+3-b4b2ecac21f6 ---------
Video encoding using x265 3.2.1+3-b4b2ecac21f6 failed with exit code: -1073741674 (0xC0000096)
The exit code might be a system error code: {EXCEPTION}
Privileged instruction.
------------ Video encoding using x265 3.2.1+3-b4b2ecac21f6 ------------
C:\StaxRip-x64-2.0.6.2-beta\Apps\Support\avs2pipemod\avs2pipemod64.exe -y4mp "video_input.avs"
| C:\StaxRip-x64-2.0.6.2-beta\Apps\Encoders\x265\x265.exe --crf 20 --preset slow --level-idc 4.1
--output-depth 10 --csv-log-level 1 --ssim --psnr --frames 200000 --y4m --output "video_output.hevc" -
avs2pipemod[info]: writing 200000 frames of 24000/1001 fps, 1904x792,
sar 0:0, YUV-420-planar-8bit progressive video.
y4m [info]: 1904x792 fps 24000/1001 i420p8 unknown frame count
raw [info]: output file: video_output.hevc
x265 [info]: HEVC encoder version 3.2.1+3-b4b2ecac21f6
x265 [info]: build info [Windows][MSVC 1924][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [warning]: --psnr used with psy on: results will be invalid!
x265 [warning]: --tune psnr should be used if attempting to benchmark psnr!
x265 [warning]: Specifying a decoder level with constant rate factor rate-control requires
x265 [warning]: enabling VBV with vbv-bufsize=50000kb vbv-maxrate=50000kbps. VBV outputs are non-deterministic!
x265 [info]: Main 10 profile, Level-4.1 (High tier)
x265 [info]: Thread pool created using 16 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 4 / wpp(13 rows)
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : star / 57 / 3 / 3
x265 [info]: Keyframe min / max / scenecut / bias: 23 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 25 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 4 / on / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-20.0 / 0.60
x265 [info]: VBV/HRD buffer / max-rate / init : 50000 / 50000 / 0.900
x265 [info]: tools: rect limit-modes rd=4 psy-rd=2.00 rdoq=2 psy-rdoq=1.00
x265 [info]: tools: rskip signhide tmvp strong-intra-smoothing lslices=4
x265 [info]: tools: deblock sao
avs2pipemod[info]: finished, wrote 24000 frames [12%].
avs2pipemod[info]: total elapsed time is 12446.648 sec.
avs2pipemod[error]: only wrote 24000 of 200000 frames.
Patman
20th January 2020, 18:15
I tried using 3.2.1+3-b4b2eca VS 2019 AVX2 from the stable branch. I encountered this error. (I'm trying to modify the below text to keep from breaking the tables too bad)
Maybe a problem of avs2pipemod... go to x265 options, other and set piping tool to none... test again... really strange
LazyNcoder
20th January 2020, 22:27
Hello guys,
I hope you can help me here.
What I'm trying to do is, to create a blank video in length of the %Video_Delay% and add it to the start of the encode.
I mean, if the source video has 5000 ms delay, I create this 5000 ms delay as blank black video.
I'm using Vapoursynth. What I already have is this:
clip2 = core.ffms2.Source(r"%source_file%", cachefile = r"%source_temp_file%.ffindex")
clip1 = core.std.BlankClip(clip2,length=%Video_Delay%)
clip = clip1+clip2
I know it has huge problems. So, What should I do here?
I also need to change the delay which is in ms to needed FPS here.
ukmark
21st January 2020, 15:55
Received the i7 10th gen laptop. Brief testing - very strange results with QSV HW encoding. The graphics driver version really makes a huge difference and has been flaky. The Lenovo driver (non-DCH) and the latest Intel driver (DCH) give different results. It seems that the drivers will have to be improved over the next few months. I had one occasion (doing a test on 2 mins of video) where the output was noticeably different between the first and second test - same input file, same driver, same settings etc - I can't figure that one out, but I swear nothing changed - apart from the output quality getting better. The speed increase is about 70% for HW encoding. The API version used by QSV is now 1.30, on KL it was 1.27 and there are some extra features auto plugged into the encode settings - tskip is new setting, sao is now set to "all" (was "none" on KL), CTU is now 64 (was 32 on KL).
Another observation is that ICQ 22 on Kaby Lake seems the same as ICQ 19 on Ice Lake(!) with the current Ice Lake driver. I used the same input file with the same settings and encoded a QSV HEVC video on Ice Lake with the exact same settings as Kaby Lake (ICQ 22 and all the extra settings identical), and the file was 35% smaller(!). At first I thought maybe quality had somehow been magically maintained with a 35% smaller file - but no, the quality was noticeably inferior on Ice Lake. To get the same video bit rate, I had to lower the ICQ value from 22 to 19 on Ice Lake (flaky drivers again??)
For SW encoding I'm getting about triple the speed (pleased with that) - and the quality is identical to Kaby Lake (which it should be as the graphics driver is not used in SW encoding AFAIK).
I think once the drivers get improved, then QSV HW encoding looks promising. I'm seeing some excellent quality (at times), but as I say, the graphics drivers seem flaky right now.
Longer testing - encoded over 2 hr action movie with my x265 CRF24 settings (720p 10bit HEVC) using SW. Then used latest Lenovo graphics driver (25.x version) and tried with QSV HEVC and set ICQ to 18. This resulted in very similar file size/bitrate between x265 and QSV.
Quality is excellent with QSV (I used the StaxRip "video comparison" tool). I haven't checked every frame :D, but I did check the usual suspects (dark scenes, fast moving action) and the QSV held up very well. Being very picky, there were some really very minor differences in the dark scenes, but I was impressed with QSV. During normal playback of these scenes I could not see any differences.
Settings for x265 (medium preset, CRF 24, 10bit HEVC, aq mode 3), rest of settings at default.
Settings for QSV (best quality, ICQ 18, 10bit HEVC, bframes 8, ref frames 5, mbbrc on (per macro block rate control), rest of settings at default.
In my previous post, I noted some discrepancies between the ICQ levels for KL and IL, but I was messing around so much with different driver versions and other things that those initial quick tests should probably be ignored. Thus I ended up doing a fresh install of the manufacturer's Win10 image for the above test.
It does appear that QSV compression has improved with IL. On KL, I was getting approx ICQ of 21 or 22 equivalent to x265 CRF24 (bit rate equivalents), whereas now on IL, I get the same bitrate with ICQ 18 or 19. The IL QSV encodes at ICQ 18/19 are better than my KL encodes at ICQ 21/22 yet achieving equivalent bit rates.
I hope to do a few more movies this way (or at least sections of more movies) and will post if I find anything of note.
UPDATE: Checked more dark scenes and QSV still lags a little behind x265 in the really poorly defined dark scenes, where details are not clear even in the original source. The differences on a per frame basis are noticeable but not terrible. Normal playback does not usually expose these differences (to my eyes). I guess for those archive quality videos that you are going to keep forever, then x265 is still the way to go, but IMHO the gap is small between QSV and x265 and seems to be getting smaller with each generation of processor. I'll revisit this if/when new graphics drivers are released (I'm sticking to OEM drivers as trying the latest from Intel made the output worse.)
neo_sapien
22nd January 2020, 07:49
Maybe a problem of avs2pipemod... go to x265 options, other and set piping tool to none... test again... really strange
When I set the piping tool to none, I get this error:
x265 [error]: yuv: width, height, and FPS must be specified
So in addition to setting the piping tool to none, I also go to Input/Output and set the Frame Rate field to 24000/1001, for 23.976fps. And then I go down to Custom, and input in the Custom field "--input-res 1904x792" which is the resolution of my content after cropping. I then start encoding, and my resulting encode gets up to 2KB and then stops (pretty much immediately).
x264 seems to be working fine without crashing, so I'm doing a workaround - I'm encoding the heavy duty filters that really slow down your encode into x264 qp0 (lossless), then taking that lossless x264 pre-filtered file and running it through x265 using the medium preset and without any additional filters. So instead of spending 25-30 hours running x265, I'm spending 20 hours to build a lossless x264 file, and then spending another 5 hours or so to encode it to x265. This way, if my x265 encode crashes, I only lose up to 5 hours of work, not up to 25-30 hours of work.
JKyle
27th January 2020, 20:21
@Patman
Hi. In your builds archive, I see a modified version of x264 named x264-159-r2991M-1771b55.
Can you please explain what makes it different from the regular version x264-159-r2991-1771b55?
Thanks :)
Patman
28th January 2020, 07:41
@Patman
Hi. In your builds archive, I see a modified version of x264 named x264-159-r2991M-1771b55.
Can you please explain what makes it different from the regular version x264-159-r2991-1771b55?
Thanks :)
Hi JKyle,
Some time ago the code for the progress feedback was changed. Original code is if( last_ts )
bitrate = (double) i_file * 8 / ( (double) last_ts * 1000 * param->i_timebase_num / param->i_timebase_den );
else
bitrate = (double) i_file * 8 / ( (double) 1000 * param->i_fps_den / param->i_fps_num );
if( i_frame_total )
{
int eta = i_elapsed * (i_frame_total - i_frame) / ((int64_t)i_frame * 1000000);
sprintf( buf, "x264 [%.1f%%] %d/%d frames, %.2f fps, %.2f kb/s, eta %d:%02d:%02d",
100. * i_frame / i_frame_total, i_frame, i_frame_total, fps, bitrate,
eta/3600, (eta/60)%60, eta%60 );
}
else
sprintf( buf, "x264 %d frames: %.2f fps, %.2f kb/s", i_frame, fps, bitrate );
fprintf( stderr, "%s \r", buf+5 );
x264_cli_set_console_title( buf );
fflush( stderr ); // needed in windows
return i_time;
my changes are
if( last_ts )
bitrate = (double) i_file * 8 / ( (double) last_ts * 1000 * param->i_timebase_num / param->i_timebase_den );
else
bitrate = (double) i_file * 8 / ( (double) 1000 * param->i_fps_den / param->i_fps_num );
if( i_frame_total )
{
int eta, eta_hh, eta_mm, eta_ss, fps_prec, bitrate_prec, file_prec, estsz_prec;
double percentage, estsz, file_num, estsz_num;
char *file_unit, *estsz_unit;
fps_prec = fps > 999.5 ? 0 : fps > 99.5 ? 1 : fps > 9.95 ? 2 : 3;
bitrate_prec = bitrate > 9999.5 ? 0 : bitrate > 999.5 ? 1 : 2;
file_prec = i_file < 1048576000 ? 2 : i_file < 10485760000 ? 1 : 0;
file_num = i_file < 1048576 ? (double) i_file / 1024. : (double) i_file / 1048576.;
file_unit = i_file < 1048576 ? "K":"M";
if( i_frame_total )
{
eta = i_elapsed * (i_frame_total - i_frame) / ((int64_t)i_frame * 1000000);
percentage = 100. * i_frame / i_frame_total;
eta_hh = eta / 3600;
eta_mm = ( eta / 60 ) % 60;
eta_ss = eta % 60;
estsz = (double) i_file * i_frame_total / (i_frame * 1024.);
estsz_prec = estsz < 1024000 ? 2 : estsz < 10240000 ? 1 : 0;
estsz_num = estsz < 1024 ? estsz : estsz / 1024;
estsz_unit = estsz < 1024 ? "K" : "M";
sprintf( buf, "x264 [%.1f%%] %d/%d frames, %.*f fps, %.*f kb/s, %.*f %sB, eta %d:%02d:%02d, est.size %.*f %sB",
percentage, i_frame, i_frame_total, fps_prec, fps, bitrate_prec, bitrate,
file_prec, file_num, file_unit,
eta_hh, eta_mm, eta_ss,
estsz_prec, estsz_num, estsz_unit );
}
else
sprintf( buf, "x264 %d frames: %.*f fps, %.*f kb/s, %.*f %sB",
i_frame, fps_prec, fps, bitrate_prec, bitrate,
file_prec, file_num, file_unit );
estimated size reappears
At the moment, i do some tests in compiling x265 with msvc2019 and a filesize of 7 MB. Stay excited :)
Short question: Does anyone use the -bStylish option of my x265 build? Or is it enough for you to see the estimated size?
JKyle
28th January 2020, 08:26
At the moment i do some tests in compiling x265 with msvc2019 and an filesize of 7 MB. Stay excited :)
Thanks for the info.
And... Wow! That's good news.
I'm pretty much looking forward to it. :)
Spunkmeyer
29th January 2020, 00:30
@all:
If someone is doing a manual update:
NVEnc 4.61 & NVEnc 4.60 are throwing an exception on my machine.
4.59 and former are doing nice.
Just to be warned.....
No time for troubleshooting at the moment.
This is on Win7 64bit (what else?)
Win 10 64 bit and it throws the exception out at the very end of encoding. All is not lost though as I been able to manually mux the video and audio back from the temp files.
Definitely Nvenc is the problem, as I have tried it in other ways as well.
craigpro
1st February 2020, 07:36
Hi all, hoping someone can help me please.
I'm using Staxrip 2.0.6.0 stable and I've noticed that subtitles are not being copied exactly from the source MKV.
eg: looking at the source file
Text #1
ID : 4
Format : ASS
Codec ID : S_TEXT/ASS
Codec ID/Info : Advanced Sub Station Alpha
Duration : 23 min 27 s
Bit rate : 15.2 kb/s
Count of elements : 10888
Compression mode : Lossless
Stream size : 2.55 MiB (0%)
Title : Signs [kdfss / FFF]
Language : English
Default : Yes
Forced : No
Text #2
ID : 5
Format : ASS
Codec ID : S_TEXT/ASS
Codec ID/Info : Advanced Sub Station Alpha
Duration : 23 min 38 s
Bit rate : 15.3 kb/s
Count of elements : 11334
Compression mode : Lossless
Stream size : 2.58 MiB (0%)
Title : Subtitles [kdfss / FFF]
Language : Japanese
Default : No
Forced : No
looking at the output file:
Text #1
ID : 4
Format : ASS
Codec ID : S_TEXT/ASS
Codec ID/Info : Advanced Sub Station Alpha
Duration : 23 min 27 s
Bit rate : 15.2 kb/s
Count of elements : 10888
Compression mode : Lossless
Stream size : 2.55 MiB (1%)
Title : English
Language : English
Default : No
Forced : No
Text #2
ID : 5
Format : ASS
Codec ID : S_TEXT/ASS
Codec ID/Info : Advanced Sub Station Alpha
Duration : 23 min 38 s
Bit rate : 15.3 kb/s
Count of elements : 11334
Compression mode : Lossless
Stream size : 2.58 MiB (1%)
Title : Japanese
Language : Japanese
Default : No
Forced : No
MPC-HT will not display any subtitle text from the output file when subtitles for stream 1 are enabled. If I select stream 2 on the output file then the ENGLISH subtitles are displayed (not the Japanese).
my Subtitle settings in Staxrip are set to:
Preferred Languages: all
Track Name: %language_english%
Demux Subtitles: All
Default Subtitle: None
convert sup - disabled
Add hardcoded - disabled
I believe those settings are default as I haven't messed with them that I can remember.
What should the settings be to directly copy the existing subtitles from the source file be please? Thank you.
Spunkmeyer
1st February 2020, 15:23
@all:
If someone is doing a manual update:
NVEnc 4.61 & NVEnc 4.60 are throwing an exception on my machine.
4.59 and former are doing nice.
Just to be warned.....
No time for troubleshooting at the moment.
This is on Win7 64bit (what else?)
Seems to be fixed now with Nvenc 4.62.
@craigpro the only thing I can see is that subtitle 1 is set as default in the original file and not so in the output.
ukmark
1st February 2020, 22:05
Preferred Languages: all
Track Name: %language_english%
Demux Subtitles: All
Default Subtitle: None
convert sup - disabled
Add hardcoded - disabled
I believe those settings are default as I haven't messed with them that I can remember.
What should the settings be to directly copy the existing subtitles from the source file be please? Thank you.
Could you try setting Default Subtitle: None to 'eng'?
JoyBell
4th February 2020, 00:43
How to add new AVISynth Filters to StaxRip?
I have spent several hours reading around and I have to admit that I simply am stumped on how to add a new AVISynth script/filter to Stax. I know how to make new filters in Stax in Profiles I have a few dozen customized filters I use all the time under MyName grouping.
I am trying to add AviSynthShader v1.6.5 into Stax so that I can try using many of the GPU shader real time filters that keep coming out that look interesting.
https://github.com/mysteryx93/AviSynthShader/releases/tag/v1.6.5 (AviSynthShader v1.6.5)
I put the .dll and autoload file in the /plugins64+ folder and then I am lost.
I am more lost on how to import the HLSL shaders after.
https://github.com/bloc97/Anime4K (Anime4K)
The new Nvidia sharpen I would like to try and is available as well as Anime4K filters, both of which are real time and of great interest.
That being said (as every other ask gets bogged down on what HLSL shaders I use as an example) the main thing I am asking is using AviSynthShader for all those interesting HLSL filters
Pulp Catalyst
8th February 2020, 10:54
Hello,
anyway of staxrip having the option to automatically remuxing the subtitles files back into the final job, so it doesn't have to be remuxed by manual methods.
what i want is the original subtitles string to just be remuxed in the final MKV, as most if not all of my players/streamers can handle native subtitles files now (dvd and bluray pgs).
thanks,
i'm doing a huge job of many dvd's (episodic tv shows and my wife is italian, so keeping the english subtitle files is a great help for her understanding).
ukmark
9th February 2020, 22:51
Just thought I'd pass this along.
During testing of StaxRip in conjunction with Intel QSV 10bit HEVC, I accidentally found a way of drastically reducing CPU usage when encoding the video, and not lose any encoding speed. I had already changed in the encoder settings, the "Decoder" (under the "Basic" section), from "Avisynth/VapourSynth" to "QSVEnc Hardware", and that did reduce the CPU usage a little, but not by much. CPU usage was still around 30-35% with no other activity occurring on the laptop.
However, by chance, I changed a setting "Async Depth" - this is under the "Performance" section. I changed the value from the default 0 (this appears to set the value at runtime to some random number - often 6 - in my case), to a value of 1. Now my CPU usage ranges between 4-7%!!!
Hard to believe the difference. I have done this a few times now just to confirm what I'm seeing. The bottom of the laptop is barely lukewarm. Makes a change from 100% CPU usage with SW encoding.
There's not much info out there I could find about Async Depth, but just thought I'd pass this finding on.
UPDATE: Just had one file that was encoding at half-speed. I increased the async depth to 2 from 1 and it is now encoding at full speed. CPU usage is still between 4-7%.
UPDATE 2: After some quick testing re "async depth", this is what I found on my laptop. It appears that setting this value explicity from 2 to 5 keeps the CPU usage between 4-7%. Also fps encoding speed is identical (so far) regardless of which value you choose between 2 to 5. Setting the value to 1 can cause speed to drop about 50% (but not always).
Setting the "async depth" to 0 (default), caused the CPU usage to increase to approx. 35%. There was no fps encoding speed increase. The "async depth" 'chosen' by QSVEnC (or the Media SDK API??) for this video was 6. All of this stuff is new to me, but it would appear a safe bet to set "async depth" to 3 or 4 and leave it there. That's what I plan on doing and if anything changes I'll let you know.
Good to know that you can get very low CPU usage with QSV and not lose any speed.
I am using ICQ setting (1=best & quality=21), HEVC 10bit, output 720p, and using latest version of QSVEnC (v3.30) and Media SDK API version of 1.30. Laptop is i7-1065g7/12gb ram and 4 cores/8 threads running Win 10 v1909.
UPDATE 3: I find that setting "1=best" is required to keep the CPU usage in that 4-7% range, setting it to "balanced" or "fast" sends it back up to 25% or higher (no idea why that is). That's fine by me as I always use that setting. I'm still getting around 90-100 fps, and as I have alluded to in a previous post, I'm finding video quality to be very good with the settings I am using.
That excellent "video comparison" tool works really well, and I am seeing very little or no difference between the QSV encode and ones done with SW encoding using the "medium" preset with CRF 24, x265 720p 10bit HEVC, (also set aq-mode to 3 and aq-strength between 0.7 and 1). I have compared about five movies so far and every comparison is extremely close between HW and SW encoding. Also, bitrates are reasonably close between HW and SW and I have had 2 movies so far where the HW bitrate was lower than the SW with equivalent (or very similar) quality. These were Captain Marvel and Avengers Infinity War. QSV seems to do a really good job with the modern digital format movies, where the image is very clean and has very little or no grain.
Considering the speed difference between HW and SW (about 3 to 4 times faster with HW), the drastically reduced CPU usage (less than 10% vs 100% with SW encoding) and the very acceptable quality of current HW encodes I am getting, then this will be default from now on. I'll only revert to SW encoding if the quality is poor for a HW encode.
Th3RadMan
10th February 2020, 00:49
I'm brand new to Staxrip, so when I took a look at the options list and got hit with... where do I start
First I'll start with my goal, transcode 4k blu rays to H.265 for space storage with as little video degradation as possible. Of course saying 'as little degradation' will make some people say then just don't transcode, however, other than the loss of HDR, when I was using handbrake, I managed to get extremely good quality with H.265 file sizes. You couldn't tell which video looked worse with my settings. That was comparing using a sdr monitor, so the color looked the same. But now that I have seen the light of a 10 bit pipeline, I want to take advantage.
So my question is this, what needs to be adjusted in the huge list of options to get the best quality to size videos. I'm not afraid of having 2 systems run 24/7 as I'm used to having 24-34hr transcode times per 4k movie on HB.
So far I have changed the preset to slow and mode to quality, with a value of 18. For video I don't know what else needs to be touch. Additionally for audio, I don't want anything to be transcoded, just pass through. Do I just set it to Copy/Mux the audio I want? I swear somewhere I read you want all or non under 'Demux Audio'... but I'm not sure.
NikosD
14th February 2020, 18:20
Major VCEEncC v5.02 update for AMD cards.
-Only Win10 is supported.
-Updated the version of AMF to 1.4.14-> 1.4.16.
Requires AMD Radeon Software Adrenalin Edition 20.2.1 or later.
-Added an option for pre-anaysis added in AMF 1.4.16.
(Valid only in VBR mode, VCEEncC only)
(--pa, --pa-sc, --pa-ss, --pa-activity-type, --pa-caq-strength, --pa-initqpsc,- -pa-fskip-maxqp)
-Added the option to calculate ssim / psnr. (--ssim /-psnr)
...and more.
https://onedrive.live.com/?authkey=%21AKqSYx46r4NYcP8&cid=6BDD4375AC8933C6&id=6BDD4375AC8933C6%217173&parId=6BDD4375AC8933C6%21516&o=OneUp
Taurus
14th February 2020, 20:19
Rigaya released NVEncC 4.64 a few days ago.
And for what it's worth:
QSVEnc 3.30 is available.
ukmark
15th February 2020, 23:35
Came across something I've never used before on my new shiny i7-1065g7 laptop - "fixed function encoding" setting in StaxRip.
Thought I'd give it a try and....!!!
Tried h264 encoding with the best (slowest) preset, output to 720p, ICQ method, and used QSVEnc decoding. Encoding speeds reached ..... over 500fps!!
The resulting file is of very good video quality and file sizes are not excessive.
Can't find much on the web regarding what settings are changeable (if any), when using fixed function encoding (I assume the term "fixed function" is self-explanatory). I can see that it ignores the number of b-frames selected and sets this to 0 in the encode log.
Looks like you choose the decoder, preset, profile, level, encoding method and quality setting, and output resolution. With h264 if I change the ICQ setting from say 24 to 26, the resulting file size is reduced as you would expect. However, with h265, changing the ICQ level has no effect on the file size produced.
Does this seem like an Intel bug with h265 ICQ on fixed function encoding, or is it a QSVEnc bug (rigaya) or even something in StaxRip??
BTW, speed on h265 10bit is 350fps using same settings as for h264 and video is very good quality. File sizes are approx 30-50% smaller than h264.
Any feedback welcome - also if anybody can shed more light on fixed function encoding and what settings are available.
I've also asked the question on rigaya's QSVEnc github.
Ta!
UPDATE: If encode method is VBR or QVBR-q, then changing the quality (or bitrate for VBR) does affect output file size for h265 when "fixed-func" is activated. Just does not currently work for ICQ and h265. I did find some notes on rigaya's github that "fixed-func" gave a lower quality output when activated. TBH, on Ice Lake, quality looks very good to me. I know that Intel touted improved QuickSync performance on Ice Lake - maybe this is why the quality has improved for fixed-function encoding? (I don't have anything to compare it with - but to my eyes, quality is very comparable to SW encoding).
I've uploaded 4 images from the "video comparison" tool showing 2 versions of "Star Trek Into Darkness". First version is 10bit HEVC SW encoded with CRF 24, x265, medium preset (encode used 100% CPU and achieved around 25-30fps). Second version is 10bit HEVC HW encoded with ICQ fixed-function (unknown quality setting due to issue above, used 25% CPU @ 350fps!). There is a tiny bit more detail on the face of Spock and Khan. However, watching the footage, you'd be very hard pressed to see any differences. Fixed-function file size is 20% bigger (bit rate ~1200kbps vs ~1000kbps on x265). I also encoded fixed-function to h264 8bit with ICQ setting. The file size is 40% larger than the h265 fixed-function version (bit rate ~1700kbps). Quality on this is also very good and encode achieved over 500fps. I've uploaded the freeze frame of Khan from h264 fixed-function encode also.
It would be difficult to go back to SW encoding. I can accept a very tiny drop in quality (and 20% larger files), in return for vastly improved encoding speed and much reduced CPU usage.
MrBrownCow
19th February 2020, 01:39
I can't figure out why my encodes with AAC audio keep getting an error. AC3 works fine but AAC does not. I think it has something to do with "CoreAudioToolbox 7.10.9.0" but I've followed the instructions for extracting the dll files from the itunes downloader with the make portable script and moved those dll files into the same folder as the qaac64.exe file yet i still get an error.
qaac 2.68, CoreAudioToolbox 7.10.9.0
ERROR: Not available input file format
Anyone having success using qaac and AAC audio?
Taurus
19th February 2020, 20:04
I can't figure out why my encodes with AAC audio keep getting an error. AC3 works fine but AAC does not. I think it has something to do with "CoreAudioToolbox 7.10.9.0" but I've followed the instructions for extracting the dll files from the itunes downloader with the make portable script and moved those dll files into the same folder as the qaac64.exe file yet i still get an error.
Folder:
staxrip\audio\qaac\QTfiles64
Thats where the quicktime files should normally be inserted.
qaac64.exe and corresponding files in the root of the quaac folder.
And make sure the path is set right in the staxrip gui:
Apps/Manage/Qaac
Set the path to the qaac folder and verify your quaac64.exe is recognized.
It's really simple.
staxrip will throw an error in case you made something wrong...
JKyle
19th February 2020, 21:13
Short question: Does anyone use the -bStylish option of my x265 build? Or is it enough for you to see the estimated size?
I do. And I do appreciate your builds.
BTW, x265 3.3 was released two days ago and I think it's time we updated the binary builds.
Sorry about nagging you, but do you have any plan to update your binary builds?
:thanks:
imhh11
19th February 2020, 23:51
I do. And I do appreciate your builds.
BTW, x265 3.3 was released two days ago and I think it's time we updated the binary builds.
Sorry about nagging you, but do you have any plan to update your binary builds?
:thanks:
+1
waiting for your custom build with the estimated size. I've been using the Wolfberry google drive links just for that but it looks like he/she stopped doing new builds.
thank you
Patman
20th February 2020, 07:31
I do. And I do appreciate your builds.
BTW, x265 3.3 was released two days ago and I think it's time we updated the binary builds.
Sorry about nagging you, but do you have any plan to update your binary builds?
:thanks:
I'm going to update my builds tonight.
imhh11
20th February 2020, 16:42
Awesome, keep it up. thank you
Taurus
20th February 2020, 20:41
@Patman:
Just out of curiousity:
What is the difference between your builds and the others?
Sorry if this has been answered somewhere along the way :D.
Patman
20th February 2020, 21:04
@Patman:
Just out of curiousity:
What is the difference between your builds and the others?
Sorry if this has been answered somewhere along the way :D.
Hi Taurus,
there are different things ...
First, the size of the files, they are all packed. FFMPEG is a bit better adapted to Staxrip in my build and not overloaded with additional libraries. x264 and x265 are adapted in such a way that the final file size is estimated in Staxrip. The timeliness of the builds is another point. If you are intrested, try my builds :D
JKyle
20th February 2020, 22:14
@Patman:
Thanks for the timely update of your builds.
BTW, when I try to download xvid_encraw, I get the following error message:
Well, looks like we can’t go any further
The file you requested has been blocked for a violation of our Terms of Service. Still have questions, or think we've made a mistake? Please contact support for further assistance.
Any idea?
:thanks:
Taurus
20th February 2020, 22:30
@Patman::thanks:
I surely will try some of your StaxRip tools.
Thanks for the updates on many of them!
Patman
20th February 2020, 22:33
@Patman:
Thanks for the timely update of your builds.
BTW, when I try to download xvid_encraw, I get the following error message:
Any idea?
:thanks:
I just tested the download and everything works fine for me.
EDIT:
filename was the reason... xvid isn't allowed... :P
Taurus
20th February 2020, 22:50
xvid_encraw download throws the error JKyle mentioned.
Maybe try with a proxy server :cool:
JKyle
20th February 2020, 23:03
xvid_encraw download throws the error JKyle mentioned.
Maybe try with a proxy server :cool:
It's funny but the problem is gone after @Patman changed the file name from xvid to x_v_i_d. :rolleyes:
Magik Mark
21st February 2020, 01:08
PatMan,
Among your x265 builds (3 of them), which one is best suited for intel i9 Processors? May I ask for performance differences?
Thanks a lot!
Taurus
22nd February 2020, 16:40
It's funny but the problem is gone after @Patman changed the file name from xvid to x_v_i_d. :rolleyes:
Thank you!
Will have a look:D.
imhh11
22nd February 2020, 17:14
@Patman thanks a lot for the new builds.
Any chance for your custom build with estimated size on GCC as well? It's always slightly faster than MSVC with my i9.
https://extraimage.net/images/2020/02/22/1313b44ace928032940f749bc0989a72.png
Patman
22nd February 2020, 17:31
@Patman thanks a lot for the new builds.
Any chance for your custom build with estimated size on GCC as well? It's always slightly faster than MSVC with my i9.
Hi imhh11,
I'm just testing the compilation with clang instead of gcc. If there is no big difference, I will compile the custom build in gcc. Stay tuned...
Gesendet von meinem HMA-L09 mit Tapatalk
imhh11
22nd February 2020, 18:42
Thank you!
Patman
23rd February 2020, 02:48
Thank you!
Done...
x265M-3.3+2-...-gcc is online.
lifta19
23rd February 2020, 12:36
Hi, Patman. Please build stable version of x265.
Patman
23rd February 2020, 19:55
x265 builds
I added a stable version of x265 (3.3+1) that was compiled with GCC 9.2.0 and MSVC 1924 (VS2019). Short explanation to my builds:
x265-3.3+1 - Stable Build
x265-3.3+2 - Default Branch / Master Branch
x265M-3.3+2 - Default Branch / Master Branch with customization to display estimated file size
I recompiled all MSVC version because i optimizied the compile code. In my case, the MSVC version is almost 1.5 seconds faster with a small video file.
GCC 9.2.0
avs2pipemod[info]: writing 4115 frames of 24000/1001 fps, 720x304,
sar 0:0, YUV-420-planar-8bit progressive video.
y4m [info]: 720x304 fps 24000/1001 i420p8 unknown frame count
raw [info]: output file: G:\Movie\x264\test\testfile_temp\testfile_new_out.hevc
x265 [info]: HEVC encoder version 3.3+2-gbe2d82093
x265 [info]: build info [Windows][GCC 9.2.0][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [info]: Main 10 profile, Level-2.1 (Main tier)
x265 [info]: Thread pool created using 16 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 4 / wpp(5 rows)
x265 [warning]: Source height < 720p; disabling lookahead-slices
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 3
x265 [info]: Keyframe min / max / scenecut / bias : 23 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 3 / off / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-20.0 / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 early-skip rskip mode=1 signhide tmvp
x265 [info]: tools: b-intra strong-intra-smoothing deblock sao
avs2pipemod[info]: finished, wrote 4115 frames [100%].
avs2pipemod[info]: total elapsed time is 45.134 sec.
x265 [info]: frame I: 153, Avg QP:18.30 kb/s: 3471.00
x265 [info]: frame P: 1226, Avg QP:21.36 kb/s: 1335.03
x265 [info]: frame B: 2736, Avg QP:26.01 kb/s: 433.49
x265 [info]: Weighted P-Frames: Y:2.9% UV:2.3%
x265 [info]: consecutive B-frames: 29.7% 8.7% 16.5% 23.8% 21.3%
encoded 4115 frames in 44.84s (91.78 fps), 815.03 kb/s, Avg QP:24.34
Start: 02:37:22
End: 02:38:07
Duration: 00:00:45
MSVC
avs2pipemod[info]: writing 4115 frames of 24000/1001 fps, 720x304,
sar 0:0, YUV-420-planar-8bit progressive video.
y4m [info]: 720x304 fps 24000/1001 i420p8 unknown frame count
raw [info]: output file: G:\Movie\x264\test\testfile_temp\testfile_new_out.hevc
x265 [info]: HEVC encoder version 3.3+2-gbe2d82093
x265 [info]: build info [Windows][MSVC 1924][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [info]: Main 10 profile, Level-2.1 (Main tier)
x265 [info]: Thread pool created using 16 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 4 / wpp(5 rows)
x265 [warning]: Source height < 720p; disabling lookahead-slices
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 3
x265 [info]: Keyframe min / max / scenecut / bias : 23 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 3 / off / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-20.0 / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 early-skip rskip mode=1 signhide tmvp
x265 [info]: tools: b-intra strong-intra-smoothing deblock sao
avs2pipemod[info]: finished, wrote 4115 frames [100%].
avs2pipemod[info]: total elapsed time is 43.694 sec.
x265 [info]: frame I: 153, Avg QP:18.30 kb/s: 3471.00
x265 [info]: frame P: 1226, Avg QP:21.36 kb/s: 1335.03
x265 [info]: frame B: 2736, Avg QP:26.01 kb/s: 433.49
x265 [info]: Weighted P-Frames: Y:2.9% UV:2.3%
x265 [info]: consecutive B-frames: 29.7% 8.7% 16.5% 23.8% 21.3%
encoded 4115 frames in 43.43s (94.74 fps), 815.03 kb/s, Avg QP:24.34
Start: 18:57:42
End: 18:58:26
Duration: 00:00:44
Pls test and give feedback...
imhh11
23rd February 2020, 21:31
thanks but the GCC builds don't work on my end. it says it's missing libgcc_s_seh-1.dll
imhh11
23rd February 2020, 22:27
same error
Mzvasturbo
24th February 2020, 12:51
Hi is it possible to rip with 2computers at the same time. I have a pc with i7 and other pc with i5 cpu both conected in my home network i rip 4k hdr movies using x265 cpu only. Now my i7 struggles even at medium preset so if there is a way my i5 pc could help it would be great. O and i found some nice settings for 4k hdr compression i get very nice rezults and small files if anyone is interested write me in private.
stax76
24th February 2020, 15:38
Hi is it possible to rip with 2computers at the same time. I have a pc with i7 and other pc with i5 cpu both conected in my home network i rip 4k hdr movies using x265 cpu only. Now my i7 struggles even at medium preset so if there is a way my i5 pc could help it would be great. O and i found some nice settings for 4k hdr compression i get very nice rezults and small files if anyone is interested write me in private.
Not with StaxRip but with RipBot264.
Mzvasturbo
24th February 2020, 16:23
And finally i figure out x265 settings i like. Staxrip with encoding server is the future :)
chipxtreme
25th February 2020, 02:19
And finally i figure out x265 settings i like. Staxrip with encoding server is the future :)
What were your settings?
Natty
26th February 2020, 09:30
Short explanation to my builds:
x265-3.3+2 - Default Branch / Master Branch
x265M-3.3+2 - Default Branch / Master Branch with customization to display estimated file size
:thanks: :)
mikraphne
26th February 2020, 20:39
I've been doing 4K encodes perfectly fine for awhile, and was wondering about HDR10+. I know how to use the HDR10plus parser tool to generate a JSON from a raw HEVC file, but how do I insert this file into Staxrip to have it embedded within the .mkv?
MrBrownCow
26th February 2020, 22:43
I added a stable version of x265 (3.3+1) that was compiled with GCC 9.2.0 and MSVC 1924 (VS2019). Short explanation to my builds:
x265-3.3+1 - Stable Build
x265-3.3+2 - Default Branch / Master Branch
x265M-3.3+2 - Default Branch / Master Branch with customization to display estimated file size
Pls test and give feedback...
the GCC version was consistently about 4% faster vs the MSVC on my ryzen 3900X testing with a few short files.
Thank you!
imhh11
26th February 2020, 23:21
I've been doing 4K encodes perfectly fine for awhile, and was wondering about HDR10+. I know how to use the HDR10plus parser tool to generate a JSON from a raw HEVC file, but how do I insert this file into Staxrip to have it embedded within the .mkv?
here:
https://extraimage.net/images/2020/02/26/3cee6fa9a4978bf88d051f8d4c033272.png
you will want to add --dhdr10-opt too
stax76
27th February 2020, 08:01
--chromaloc --vpp-sub --vpp-sub-charset --vpp-sub-shaping --videoformat --colormatrix --colorprim --transfer --fullrange
Were all these switches removed from qsvenc or is the documentation incomplete?
Patman
27th February 2020, 20:48
--chromaloc --vpp-sub --vpp-sub-charset --vpp-sub-shaping --videoformat --colormatrix --colorprim --transfer --fullrange
Were all these switches removed from qsvenc or is the documentation incomplete?
Only vpp-sub (--vpp-sub --vpp-sub-charset --vpp-sub-shaping) switches were removed. All other switchen can be found here (https://github.com/rigaya/QSVEnc/blob/master/QSVEncC_Options.en.md)
Patman
27th February 2020, 20:49
the GCC version was consistently about 4% faster vs the MSVC on my ryzen 3900X testing with a few short files.
Thank you!
Thanks for your feedback!
Mzvasturbo
27th February 2020, 22:37
What were your settings?
Try it on average 4k hdr bluray source.
preset medium
--crf 17 --level-idc 5.1 --output-depth 10 --rdoq-level 2 --aq-mode 4 --aq-motion --max-merge 3 --ref 4 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(x,x)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "x,x" --hdr --hdr-opt --repeat-headers --hrd --aud --deblock -1:-1 --no-sao
If you can go slow preset it is like this.
--crf 17 --preset slow --level-idc 5.1 --output-depth 10 --aq-mode 4 --aq-motion --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(x,x)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "x,x" --hdr --hdr-opt --repeat-headers --hrd --aud --deblock -1:-1 --no-sao
It gives me very good rezults and small files.
For heavy grainy movies like midway 2019 filesize with above settings is very big almost the same as tune grain. So in movies like that it is better to use tune grain if you want quality. Or some other settings mybe some grain remove filter to get better compression and smaller file.
stax76
27th February 2020, 23:13
Only vpp-sub (--vpp-sub --vpp-sub-charset --vpp-sub-shaping) switches were removed. All other switchen can be found here (https://github.com/rigaya/QSVEnc/blob/master/QSVEncC_Options.en.md)
Thanks, I'll update it later. Which GCC version did you use to build x265?
@all
I was working on this VFW interface replacement, it worked out well I think and I've tested all I could think of, I hope the new build is fine as well as the updated tools. In the next weeks I don't plan to work on anything larger, so I should have time for staxrip and mpv.net maintenance. Sorry for things not addressed yet, I have to catch up. I hope there are some useful improvements, have fun.
### 2.0.7.1 Beta
- new: icons added in encoder dialog menus
- new: option dialog is shown in case a tool has multiple help
resources, x265 for instance has a local help file containing
the console help and it has a comprehensive online help.
L-Smash-Works for instance has separate help pages
for AviSynth and for VapourSynth
- new: medium quality for x264 was changed from crf 20 to 22
- new: medium quality for x265 was changed from crf 20 to 18
- new: %dpi% macro added, returnes the DPI value of the main dialog screen
- new: High DPI aware Info() AviSynth filter profile added to misc section
- new: the VFW interface used to access AviSynth and VapourSynth
was replaced with a new library
- new: a dozen new x265 switches
- new: nvenc switches --colorrange, --psnr, --ssim
- new: search matches in the video encoder config dialog
stay now permanently highlighted with bold font
- new: the search feature in the video encoder config dialog now
also searches in option values, for instance searching
for 'medium' will find and highlight the 'preset' switch
- new: in the video encoder config dialogs the context menu of the
command line preview has a new menu item to search
for the switch or string at the caret or cursor
- new: Opus format enabled for MP4Box muxer, this was requested
but did not work in my test
- new: bmp format for cover art can be used in muxer dialog
- update: nvenc 4.65
- update: qsvenc 3.31
- update: vceenc 5.02
- update: x265 3.3+2-gbe2d82093 GCC Patman
- update: ffmpeg N-96788 GCC 9.2.0 Patman
- update: mkvtoolnix 43
- update: MP4Box 0.8.0-rev178-g44c48d630 Patman
- fix: x265 three pass encoding (untested)
- fix: zoom in/out was flipped in preview dialog
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/u/s!ArwKS_ZUR01g0kH4d4eT_6a3GaKe?e=qbOfGS
Patman
28th February 2020, 07:35
Thanks, I'll update it later. Which GCC version did you use to build x265?
I use GCC 9.2.0 to build x265.
JKyle
28th February 2020, 08:49
@stax76:
Thanks for the update.
But even with 2.0.7.1 Beta, the following things related to x265 options don't seem to have been fixed.
1) refine-ctu-distortion is named incorrectly
https://i.imgur.com/duAUvXX.jpg
2) High Tier doesn't work
https://i.imgur.com/qESW4Sx.jpg
3) Options with the 'no-' switch do not show up the help file when right-clicked
https://i.imgur.com/JhzaAHM.jpg
:thanks:
Patman
28th February 2020, 12:52
@stax76:
2) High Tier doesn't work
This switch only had an effect when a level is set. I can't see in the commandline, that you set a level.
JKyle
28th February 2020, 14:47
This switch only had an effect when a level is set. I can't see in the commandline, that you set a level.
Oops, my bad! :eek:
Yes, you’re right, as it’s obviously explained in the help. :p
:thanks:
shodan5000
28th February 2020, 21:42
When trying to open a source file with the newest beta I only get a message stating:
System.DllNotFoundException: Unable to load DLL 'FrameServer': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Any ideas on how to fix this issue?
Spunkmeyer
28th February 2020, 22:25
When trying to open a source file with the newest beta I only get a message stating:
System.DllNotFoundException: Unable to load DLL 'FrameServer': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Any ideas on how to fix this issue?
Me too, path in error details is pointing to drive D:/Projekte
Suppose I could just install it there as a temp fix but still ;-)
JKyle
28th February 2020, 22:37
When trying to open a source file with the newest beta I only get a message stating:
System.DllNotFoundException: Unable to load DLL 'FrameServer': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Any ideas on how to fix this issue?
Same problem here.
DllNotFoundException (2.0.7.1)
Unable to load DLL 'FrameServer': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
System.DllNotFoundException: Unable to load DLL 'FrameServer': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at StaxRip.FrameServer.CreateAviSynthServer()
at StaxRip.FrameServer..ctor(String path) in D:\Projekte\VB\staxrip\General\FrameServer.vb:line 12
at StaxRip.VideoScript.Synchronize(Boolean convertToRGB, Boolean comparePath, Boolean flipVertical) in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 246
at StaxRip.VideoScript.GetInfo() in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 437
at StaxRip.VideoScript.GetFramerate() in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 432
at StaxRip.MainForm.ModifyFilters() in D:\Projekte\VB\staxrip\Forms\MainForm.vb:line 2263
at StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean isEncoding) in D:\Projekte\VB\staxrip\Forms\MainForm.vb:line 1981
chipxtreme
29th February 2020, 02:15
Same for me
Patman
29th February 2020, 02:25
FrameServer-Error
Copy the FrameServer.dll from zip or folder to C:/Windows/System32. I think Stax will fix that soon :)
EDIT: doesn't help... :(
JKyle
29th February 2020, 03:25
Copy the FrameServer.dll from zip or folder to C:/Windows/System32.
This doesn't seem to fix the problem.
There already existed another version of the file, but I replaced it with the one included in the StaxRip zip file. However, the problem still exists.
:(
Patman
29th February 2020, 03:28
This doesn't seem to fix the problem.
There already existed another version of the file, but I replaced it with the one included in the StaxRip zip file. However, the problem still exists.
:(
Hmmm... i have no problem with the new version of Staxrip...
Mister XY
29th February 2020, 05:21
I have also the same FramServer error
JKyle
29th February 2020, 06:07
Just out of curiosity...
If FrameServer.dll plays such a crucial role in the new Beta version, why don't you put it in the Apps => Manage => Runtimes menu and let users to customize its path?
Sorry if it's against your development philosophy.
Taurus
29th February 2020, 11:25
Same for me
Same here...
Magik Mark
29th February 2020, 12:27
Same here. Refuses to be copied in the system32 directory
stax76
29th February 2020, 13:48
Sorry, I'm not super C++ competent, I've not used it often and not in recent years.
I use Windows 10 and in Visual Studio 2019 I used Platform Toolset 'Visual Studio 2019 (v142)', it's the newest and I hope it works when following x64 runtime is installed:
https://support.microsoft.com/en-au/help/2977003/the-latest-supported-visual-c-downloads
If it doesn't work then it might be the same issue I have with my other C++ library:
https://github.com/stax76/OpenWithPlusPlus/issues/5
The C++ DLL exports C functions, in .NET C functions are called using a technique named pinvoke, which means the .NET runtime loads FrameServer.dll, there is another unrelated FrameServer.dll in system32 (maybe a Windows component), this should not be a problem because the startup directory has a higher priority than the system32 directory.
Patman
29th February 2020, 14:44
Maybe this will help with the frameserver. dll error
http://batcmd.com/windows/10/services/frameserver/
That service only exists on win10.
Spunkmeyer
29th February 2020, 15:40
System.DllNotFoundException: Unable to load DLL 'FrameServer': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at StaxRip.FrameServer.CreateVapourSynthServer()
at StaxRip.FrameServer..ctor(String path) in D:\Projekte\VB\staxrip\General\FrameServer.vb:line 14
at StaxRip.VideoScript.Synchronize(Boolean convertToRGB, Boolean comparePath, Boolean flipVertical) in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 246
at StaxRip.VideoScript.GetInfo() in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 437
at StaxRip.VideoScript.GetFrameCount() in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 461
at StaxRip.GlobalClass.IsValidSource(Boolean warn) in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 684
at StaxRip.MainForm.AviSynthListView_ScriptChanged() in D:\Projekte\VB\staxrip\Forms\MainForm.vb:line 5196
at StaxRip.FiltersListView.OnChanged() in D:\Projekte\VB\staxrip\Controls\FiltersListView.vb:line 269
at StaxRip.FiltersListView._Lambda$__14-0(VideoScript script) in D:\Projekte\VB\staxrip\Controls\FiltersListView.vb:line 29
at StaxRip.VideoScript.RaiseChanged() in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 21
at StaxRip.VideoScript.SetFilter(Int32 index, VideoFilter filter) in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 91
at StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean isEncoding) in D:\Projekte\VB\staxrip\Forms\MainForm.vb:line 2064
Tried all the above hints and Visual Studio, 3.5 gig download etc, happens with both AVS and Vapour.
Oh and Nvenc has been updated again :-)
Magik Mark
29th February 2020, 15:50
Yup. Problem still persisting
stax76
29th February 2020, 17:06
I searched for DllNotFoundException which led to a StackOverflow thread were somebody said:
I ran into this problem and solved with the following:
There's a dependency on msvcr90.dll if you compile under /MD. Try compiling the code with /MT instead.
Project properties > C/C++ > Code Generation > Runtime Library: /MT
I check this setting and it's:
Multi-threaded Debug DLL (/MDd)
I think the problem is I released a debug build, I do it all the time with .NET code and wasn't aware that it can't be done with native code.
Sorry everybody, I'll upload a new build soon.
ukmark
29th February 2020, 17:18
Sorry everybody, I'll upload a new build soon.
Absolutely no need to apologize.
I know we are all very grateful for your efforts.:thanks:
stax76
29th February 2020, 19:27
I hope it's fine now.
2.0.7.2 Beta
------------
- new: showing MediaInfo for the source file works now even if
the source file is an d2v/dgi index file
- new: improved detection to find out if all video encoder
command line switches have a GUI implementation,
(there is still a lot work to do)
- fix: use FrameServer.dll release build instead of debug build
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/u/s!ArwKS_ZUR01g0kH4d4eT_6a3GaKe?e=qbOfGS
Patman
29th February 2020, 20:06
I hope it's fine now.
2.0.7.2 Beta
------------
- new: showing MediaInfo for the source file works now even if
the source file is an d2v/dgi index file
- new: improved detection to find out if all video encoder
command line switches have a GUI implementation,
(there is still a lot work to do)
- fix: use FrameServer.dll release build instead of debug build
The new version with release compiling settings works great!!! :thanks:
Magik Mark
1st March 2020, 00:06
Thanks Stax! It' s awesome!
stax76
1st March 2020, 09:57
Thanks for the feedback everybody. :thanks:
@JKyle
Next build addresses the x265 issues and has also some related improvements.
NikosD
1st March 2020, 12:20
New versions for all HW encoders:
NVenc v4.67
QSVenc v3.32
VCEenc v5.03
Mainly bug fixes and a new noise reduction filter for NVenc (--vpp-smooth)
I think you can just add them inside StaxRip folders.
Taurus
1st March 2020, 17:40
For three hours I have tried to get QTGMC in a working condition :devil:
Dfttest.dll provided by StaxRip was throwing an illegal instruction message.
Searched my harddisk & internet for a 64bit version of this file.
Exchanging various mutants of the dll did not work well.
And yes, the corresponding fftw.dll is in the search path.
Lately I found a mod (dfttest_1943mod_190410) and bingo:
QTGMC & dfttest denoiser are working reliable and fast.
This is on an old PC Intel Core2 Quad CPU Q6600 with just
MMX, SSE, SSE2, SSE3, SSSE3, Intel 64 instructions.
I know over at the older StaxRip help thread someone had the same struggle:https://forum.doom9.org/showthread.php?p=1901957#post1901957http://
Here is where I've got this mod from:https://github.com/299792458m/dfttest_mod/releases
Hope this helps someone..
Cheers
stax76
1st March 2020, 19:23
Thanks for pointing it out, I think it was reported at least twice. Included in the next build.
Taurus
1st March 2020, 19:44
Thanks for pointing it out, I think it was reported at least twice. Included in the next build.
Thank you:thanks:
stax76
2nd March 2020, 04:39
I had few posts bookmarked, bug reports, tool links and other things and addressed it now, thanks for the help. I might pause coding a while and after that much likely work on other tools with other languages. At some time trying to write documentation would make sense I guess. I hope it's working. I'll be back.
### 2.0.7.3 Beta
- fix: x265 issues with --refine-ctu-distortion and --high-tier
- fix: certain avs and vpy files failed to load before, hopefully all external
scripts can now be opened
- fix: opening source files that contain single quotes caused a VapourSynth
script error, the fix will however only work when people reset their
filter profiles
- fix: the local context help of x264 did often not work
- update: nvenc 4.66
- update: L-Smash-Work 20200207 HolyWu
- update: VSFilterMod R5.2.1
- update: BDSup2Sub++ 1.0.3
- update: qsvenc 3.31
- update: JPSDR 3.2.0
- update: d2vsource 1.2
- update: AVSMeter 2.9.8
- update: chapterEditor 1.21
- update: Subtitle Edit 3.5.13
- update: rav1e 0.3.0
- update: x264 2991-1771b55 Patman
- new: improved possibility to show AviSynth and VapourSynth script
information with a new dialog and new pixel format parameter
- new: the right click context help in the x264 and x265 dialog can now
alternativly open the online help with ctrl or shift + right click
to navigate directly to the online help of the right-clicked switch
- new: the F1 help in the video encoder dialogs was greatly improved
- new: in the nvenc dialog custom switches do overwrite regular switches
- new: Bwdif plugin for VapourSynth (similar to yadif)
- new: filters can be removed from the filter list view in the main dialog
using the delete key
- new: qsvenc --colorrange --dhdr10-info --key-on-chapter --sub-source
- new: x264 --avcintra-flavor --index --input-fmt --muxer --quiet
--verbose --video-filter
- new: the short version command line switches (like -t) are now supported
in the x264 dialog
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/u/s!ArwKS_ZUR01g0kH4d4eT_6a3GaKe?e=qbOfGS
Havokdan
2nd March 2020, 12:29
Just a question, does this beta version no longer support avisynth +? And I saw that it comes without the installer in the folder where it was before.
stax76
2nd March 2020, 12:49
It requires AviSynth+ x64 3.4.0, the official installer is too large to include and I don't see a need to make a custom installer (I had a INNO script in the past but lost it), it should be no problem for users to download and install it, if the user opens a video file and AviSynth+ is not installed the Apps dialog will show up presenting a download button, pressing this will shell execute the URL of the executable triggering the browser to automatically download it. The app management, verification and help system work with these URLs:
.WebURL = "https://github.com/AviSynth/AviSynthPlus",
.HelpURL = "http://avisynth.nl",
.DownloadURL = "https://github.com/AviSynth/AviSynthPlus/releases/download/v3.4.0/AviSynthPlus_3.4.0_20191020.exe",
Maybe there should also be a readme file, better documentation is planned for this or next year.
I hope it's clear now. :)
Patman
2nd March 2020, 13:47
I'm planning to recompile Avisynth+ without VCRedist. You will find it in "My Builds" soon.
stax76
2nd March 2020, 14:07
Nice, I can include it then. Theoretically it could be used portable as well, it's probably fairly simple, needed would only be a small change in app management and verification and when tools are started the path env variable of the process must be updated with folder of avisynth so the OS finds it when the tool calls LoadLibrary. Same for vapoursynth except that it's a larger package due to python. I'm not really seeing a benefit in the portable way though.
Havokdan
2nd March 2020, 14:20
Thanks for the answer.
DavidRyan
2nd March 2020, 15:48
Just wanted to say thanks for all the work on Staxrip, have been using it a lot over the last few years.
Thought I'd also mention a few little quirks I've noticed (Win10/Staxrip v2.0.6.0) in case someone else hasn't reported them before:
- Been using the cutting feature recently to encode parts of a few source files, muxing sometimes fails when the new segment doesn't contain a chapter, reporting an xml file error. Can get around this by manually muxing the pieces with mkvtoolnix.
- With the window of avisynth scripts it seems like audio functionality is excluded, guessing because of the way audio is handled elsewhere in the interface instead? Eg if using AssumeFPS(true) the audio also won't be adjusted as expected. Or if using 'cutting' one can't just change the frames listed there to do the next piece as audio cutting won't be adjusted too, one needs to go back to the preview window to change it.
- v2.0.6.0 no longer includes the "writing frontend: staxrip vx.x" tag as before, not sure if intended.
These are minor issues one can work around, but thought it worth a mention. Thanks again for all the hard work.
lasa
2nd March 2020, 18:24
I get the error: System.OverflowException: Die arithmetische Operation hat einen Überlauf verursacht.
bei StaxRip.MainForm.ModifyFilters() in D:\Projekte\VB\staxrip\Forms\MainForm.vb:Zeile 2273.
bei StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean isEncoding) in D:\Projekte\VB\staxrip\Forms\MainForm.vb:Zeile 1986.
stax76
2nd March 2020, 19:41
- Been using the cutting feature recently to encode parts of a few source files, muxing sometimes fails when the new segment doesn't contain a chapter, reporting an xml file error. Can get around this by manually muxing the pieces with mkvtoolnix.
Fixed in the next build.
- With the window of avisynth scripts it seems like audio functionality is excluded, guessing because of the way audio is handled elsewhere in the interface instead? Eg if using AssumeFPS(true) the audio also won't be adjusted as expected. Or if using 'cutting' one can't just change the frames listed
StaxRip does hardly if any audio processing with AviSynth, source filters probably most often do not process audio by default. StaxRip however gives relative much control over AviSynth, almost full control like you write code by hand, you can edit the code and you can config StaxRip so that it uses script code you want, by default. Cutting audio and changing frame rate should work because StaxRip adds the Trim filters at the end of the script. You can find out if a script has audio with the Info() function, if you add this function to your script than the preview will show info parameters, if the font is too small then you can use the new Info filter profile which is High DPI aware, at 288DPI something like Info(size=50) will work, the new profile uses the new %dpi% macro so it works everywhere. If it's not in the filter profiles menu then you can find it in the defaults tab of the filter profiles editor, we improve the filter profiles often but never reset it to avoid people lose their customization. If you modify your script that it has audio than for instance you can use the avisynth script file as audio source file. I generally never had much interest in scripting and audio, megui and maybe other GUIs use more off avisynths audio capabilities.
v2.0.6.0 no longer includes the "writing frontend: staxrip vx.x" tag as before, not sure if intended.
It was not re-added after most of the related code was rewritten, you can add it in the Tags tab of the muxer dialog, save a project template and muxer profiles to make the setting persist, the macro you need is %version%. Selur forces it, I don't care.
I get the error: System.OverflowException: Die arithmetische Operation hat einen Überlauf verursacht.
bei StaxRip.MainForm.ModifyFilters() in D:\Projekte\VB\staxrip\Forms\MainForm.vb:Zeile 2273.
bei StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean isEncoding) in D:\Projekte\VB\staxrip\Forms\MainForm.vb:Zeile 1986.
I can try to reproduce it if it's not obvious looking at the code, does it happen only at special conditions? If so which conditions?
DavidRyan
2nd March 2020, 20:08
Great, will look into that, appreciate the response.
stax76
2nd March 2020, 21:14
@Iasa
I'm not sure exactly which line, there is a GetFrameRate method that probably returns NaN (not a number) instead of a proper frame rate, I can fix this line, it's not doing anything important put not getting a proper frame rate might cause other issues so it would be best if you can tell me how to reproduce it. I tried to set FirstOriginalSourceFile to null but it cause an null ref exception somewhere else instead of a overflow exception.
Dim miFPS = MediaInfo.GetFrameRate(p.FirstOriginalSourceFile)
Dim avsFPS = p.SourceScript.GetFramerate
If (CInt(miFPS) * 2) = CInt(avsFPS) Then
Dim src = p.Script.GetFilter("Source")
src.Script = src.Script + BR + "SelectEven().AssumeFPS(" & miFPS.ToInvariantString + ")"
p.SourceScript.Synchronize()
End If
Atlantis
3rd March 2020, 04:25
Try it on average 4k hdr bluray source.
preset medium
--crf 17 --level-idc 5.1 --output-depth 10 --rdoq-level 2 --aq-mode 4 --aq-motion --max-merge 3 --ref 4 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(x,x)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "x,x" --hdr --hdr-opt --repeat-headers --hrd --aud --deblock -1:-1 --no-sao
If you can go slow preset it is like this.
--crf 17 --preset slow --level-idc 5.1 --output-depth 10 --aq-mode 4 --aq-motion --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(x,x)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "x,x" --hdr --hdr-opt --repeat-headers --hrd --aud --deblock -1:-1 --no-sao
It gives me very good rezults and small files.
For heavy grainy movies like midway 2019 filesize with above settings is very big almost the same as tune grain. So in movies like that it is better to use tune grain if you want quality. Or some other settings mybe some grain remove filter to get better compression and smaller file.
wow, crf 17 is huge. What sizes, what bitrate do you get with crf17?
Atlantis
3rd March 2020, 04:31
AviSynth+ 3.5.0 released. (https://github.com/AviSynth/AviSynthPlus/releases)
AviSynth+ 3.5.0 (https://github.com/AviSynth/AviSynthPlus/releases)
AviSynthPlus_3.5.0_20200302.exe
7.94 MB
AviSynthPlus_3.5.0_20200302_vcredist.exe
26.9 MB
@qyot27 qyot27 released this 1 hour ago
New:
New: Native Linux, macOS, and BSD support.
New function:
bool IsVersionOrGreater(int majorVersion, int minorVersion [,int bugfixVersion]) function
Returns true if the current version is equal or greater than the required one in the parameters.
The function is checking the current version against the given parameters (similar to a Windows API function)
e.g. IsVersionOrGreater(3, 4) or IsVersionOrGreater(3, 5, 8)
New: "Expr" helpers:
Constants "yrange_min", "yrange_half", "yrange_max"
Unlike the luma/chroma plane adaptive "range_min", "range_half", "range_max" these constants always report the luma (Y) values
new parameter: bool clamp_float_UV (default false)
this parameter affects clamping of chroma planes: chroma is clamped between 0..1.0 instead of -0.5..0.5s
"clamp_float" is not ignored (and set to true) when parameter "scale_inputs" auto-scales 32 bit float type pixels
New "yscalef" and "yscaleb" keywords similar to "scalef" and "scaleb" but scaling is forced to use rules for Y (non-UV) planes
new allowed value "floatUV" for scale_inputs.
In short: chroma pre-shift by 0.5 for 32 bit float pixels
Affects the chroma plane expressions of 32 bit float formats.
Shifts the input up by 0.5 before processing it in the expression, thus values from -0.5..0.5 (zero centered) range are converted to the 0..1 (0.5 centered) one.
Since the expression result internally has 0..1.0 range, this then is shifted back to the original -0.5..0.5 range. (since 2.2.20)
Note: predefined constants such as cmin, cmax, range_min, range_max and range_half will be shifted as well, e.g. the expression will see range_half = 0.5
These modifications are similar to Masktools2 2.2.20+
New: AddBorders, LetterBox: new color_yuv parameter like in BlankClip
Atlantis
3rd March 2020, 04:49
Now they have 2 exe of AviSynth+ 3.5.0. You can include the verison without vcredist. It is only 7.94 MB.
Patman
3rd March 2020, 08:36
Now they have 2 exe of AviSynth+ 3.5.0. You can include the verison without vcredist. It is only 7.94 MB.
Thank you for the info so AviSynth+ doesn't have to be recompiled. :thanks:
stax76
3rd March 2020, 13:00
That's a welcome improvement, people can probably accept that the package grows 8 MB, there is still room for improvement though as it combines 32 and 64 bit.
People need to understand that vapoursynth does things very often much better than avisynth. The vapoursynth author has implemented my request to provide separate downloads for 32 and 64 bit and his setup script can download VC redist which reduces server costs and is more user-friendly for people that don't know what VC redist is.
shodan5000
3rd March 2020, 16:49
I'm experiencing some issues with cropping. The crop window is showing a distorted image when viewing. My crop input does not seem to be sticking during encoding. These issues are not present in the 2.0.6.2 beta. Also, is there a way to have the auto crop feature automatically run for each new video in a batch process?
stax76
3rd March 2020, 18:54
@Patman
@Atlantis
The new AviSynth version and setup is included in the next build, I've tested if StaxRip actually asks to install the new version, verified that the installation process is working properly and made some fonts size and layout improvements in the app manage dialog.
I'm experiencing some issues with cropping. The crop window is showing a distorted image when viewing. Also, my crop input does not seem to be sticking during encoding. These issues are not present in the 2.0.6.2 beta.
Please elaborate, crop filter is checked in the filter list?
Post a full log file at pastebin.com
Patman
3rd March 2020, 19:25
@Patman
@Atlantis
The new AviSynth version and setup is included in the next build, I've tested if StaxRip actually asks to install the new version, verified that the installation process is working properly and made some fonts size and layout improvements in the app manage dialog.
Great, good job! :thumbs:
EDIT:
@stax76: It would be great if you could fix the error with input formats like VP9, AV1 or VC-1. You have a run ;)
Issue #98 (https://github.com/staxrip/staxrip/issues/98#issue-542815033); Issue #87 (https://github.com/staxrip/staxrip/issues/87#issue-522454557)
Atlantis
4th March 2020, 00:31
Thanks.
People need to understand that vapoursynth does things very often much better than avisynth. The vapoursynth author has implemented my request to provide separate downloads for 32 and 64 bit and his setup script can download VC redist which reduces server costs and is more user-friendly for people that don't know what VC redist is.
I switched to vapoursynth and used it for 2 weeks but again switched back to avisynth. Don't know if I did the right thing. If I'm not mistaking there shouldn't be an encoding speed difference and avisynth seemed to be easier to follow and use its filters to me.
RainyDog
4th March 2020, 09:12
I'm experiencing some issues with cropping. The crop window is showing a distorted image when viewing. My crop input does not seem to be sticking during encoding. These issues are not present in the 2.0.6.2 beta. Also, is there a way to have the auto crop feature automatically run for each new video in a batch process?
I've come across the distorted image during preview mode after cropping too.
It's only happened once though, and that was on a film with vertical black bars that required left and right sides cropping. Not seen the issue when cropping top and bottom pixels yet.
So maybe it could be isolated to left/right cropping?
shodan5000
4th March 2020, 14:35
I've come across the distorted image during preview mode after cropping too.
It's only happened once though, and that was on a film with vertical black bars that required left and right sides cropping. Not seen the issue when cropping top and bottom pixels yet.
So maybe it could be isolated to left/right cropping?
Same here. Only noticed on videos with vertical black bars.
stax76
4th March 2020, 16:01
Does it look like this:
https://github.com/staxrip/staxrip/issues/120
What I found out so far is that it happens only when the width is not mod 16 and only with avisynth, not with vapoursynth and only in staxrip, looks fine when rendered by mpv or mpc.
jlw_4049
4th March 2020, 16:41
@stax76 it seems like when I'm testing a file on latest 2.0.6.0 after I do a test encode with (selectrangeevery) it takes 10 minutes to MUX a 150 mb file where as 2.0.4.0 did it near instantly. Crop also seems slower on 2.0.6.0 as well. Going to test in a second and report back.
EDIT: Crop is definitely faster on 2.0.4.0
EDIT: Muxing is pretty slow on both of these versions. I'll do more tests with older versions to see if I'm mistaken and it's always been like this.
stax76
4th March 2020, 17:01
I though ConvertToRGB32 and COMPATBGR32 give the same data but the pitch is only the same with mod 16.
stax76
4th March 2020, 17:19
@stax76 it seems like when I'm testing a file on latest 2.0.6.0 after I do a test encode with (selectrangeevery) it takes 10 minutes to MUX a 150 mb file where as 2.0.4.0 did it near instantly. Crop also seems slower on 2.0.6.0 as well. Going to test in a second and report back.
EDIT: Crop is definitely faster on 2.0.4.0
EDIT: Muxing is pretty slow on both of these versions. I'll do more tests with older versions to see if I'm mistaken and it's always been like this.
I don't remember what happened when and focus on the last beta 2.0.7.3, slow auto crop is probably mostly caused by slow frame server seeking, nothing has changed in staxrip, only newer frame server source plugins. I can try ffmpeg -vf cropdetect, it's probably much faster, if it works.
Slow muxing is much likely caused by mkvmerge.
stax76
5th March 2020, 01:37
OK, I hope it's getting stable, please test.
### Todo
- documentation
- website
- use ffmpeg for auto crop
- improve default settings
- improve and maintain video encoders
### 2.0.7.4
- fix: bug in crop dialog was fixed
- fix: raw format of VP8/VP9 (IVF) was undefined which
caused a NotImplementedException
- fix: OverflowException of unknown cause
- fix: using txt chapters with mkv muxer caused xml exception
- fix: if the width was not mod 16 the crop and preview
dialog showed a distorted image
- update: AviSynth 3.5.0
- new: the apps dialog can create a CSV file listing all tools
with various properties like Name, Version, Modified date etc.
- new: x265 --rskip switch updated
- new: improved main menu
- new: improved app management dialog
- new: mpv and mpc started in the preview dialog start at the current
time position of the preview instead of the beginning
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/u/s!ArwKS_ZUR01g0kH4d4eT_6a3GaKe?e=qbOfGS
jlw_4049
5th March 2020, 17:11
I don't remember what happened when and focus on the last beta 2.0.7.3, slow auto crop is probably mostly caused by slow frame server seeking, nothing has changed in staxrip, only newer frame server source plugins. I can try ffmpeg -vf cropdetect, it's probably much faster, if it works.
Slow muxing is much likely caused by mkvmerge.
Tested another file on 2.0.6.0 and crop/program was snappy on the other file.
Muxing is still painfully slow.
EDIT: Muxing is quick on the file that is fast on the program. I just don't understand how 1 varies from the other.
stax76
5th March 2020, 19:44
next build:
- new: auto crop feature in crop dialog shows progress in the
form that the navigation slider and picture moves
- new: setting that allows to define how many frames are analysed
for auto crop, default changed from 20 to 10.
I measured how much time it spends to analyze one frame, it was 50 ms for a 4K source, this can be optimized to be 10x times faster but it's not worth the time it would take coding it because 10 frames take only 0,5 seconds, seeking is slow, only thing we could do is asking source filter and frame server devs if there is room for optimization.
Muxing is still painfully slow.
Post command line, media and hardware specs in mkvmerge thread, maybe full log file on pastebin.com, it's not related to staxrip as the only thing it does is executing a command line and wait until it finishes, mkvmerge does the muxing. Don't use 50 subtitle tracks like in that last sample you uploaded. :)
jlw_4049
6th March 2020, 03:55
next build:
- new: auto crop feature in crop dialog shows progress in the
form that the navigation slider and picture moves
- new: setting that allows to define how many frames are analysed
for auto crop, default changed from 20 to 10.
I measured how much time it spends to analyze one frame, it was 50 ms for a 4K source, this can be optimized to be 10x times faster but it's not worth the time it would take coding it because 10 frames take only 0,5 seconds, seeking is slow, only thing we could do is asking source filter and frame server devs if there is room for optimization.
Post command line, media and hardware specs in mkvmerge thread, maybe full log file on pastebin.com, it's not related to staxrip as the only thing it does is executing a command line and wait until it finishes, mkvmerge does the muxing. Don't use 50 subtitle tracks like in that last sample you uploaded. :)
It was for sure the file I was using due to all of the subtitles.
Is there anyway to demux just the video and it be automatically placed into a .mkv file for testing/encoding from?
stax76
6th March 2020, 14:24
I don't know if it's possible to demux directly from BD with free and still maintained software.
colinhunt
6th March 2020, 15:50
I wanted to do some upscaling using SuperRes, any of the three variants, but progress halts immediately to a Script Error, "Cannot load file '<path>/Shader.dll'. Platform returned code 126: The specified module could not be found."
I suspect the module not found is referring to something else than Shader.dll because both it and Shader.avsi are present in the correct directory. I'm running StaxRip x64 2.0.7.4 beta.
Am I missing something here?
stax76
6th March 2020, 16:05
This loads here:
Import("D:\Projekte\VB\staxrip\bin\Apps\Plugins\AVS\NNEDI3\edi_rpow2.avsi")
LoadPlugin("D:\Projekte\VB\staxrip\bin\Apps\Plugins\avs\JPSDR\Plugins_JPSDR.dll")
LoadPlugin("D:\Projekte\VB\staxrip\bin\Apps\Plugins\both\L-SMASH-Works\LSMASHSource.dll")
Import("D:\Projekte\VB\staxrip\bin\Apps\Plugins\AVS\Shader\Shader.avsi")
LoadPlugin("D:\Projekte\VB\staxrip\bin\Apps\Plugins\AVS\Shader\Shader.dll")
LSMASHVideoSource("D:\Samples\aaa.mp4")
SuperXBR(factor=2)
I'm not good in filter diagnostic, it could have something to do with your OS and runtimes, your CPU and your disc drive.
'<path>/Shader.dll'
Right-click filters, choose 'Preview Code', show it.
colinhunt
6th March 2020, 16:38
Right-click filters, choose 'Preview Code', show it.
Import("D:\Videotools\StaxRip-x64-2.0.7.4\Apps\Plugins\AVS\NNEDI3\edi_rpow2.avsi")
LoadPlugin("D:\Videotools\StaxRip-x64-2.0.7.4\Apps\Plugins\avs\JPSDR\Plugins_JPSDR.dll")
LoadPlugin("D:\Videotools\StaxRip-x64-2.0.7.4\Apps\Plugins\avs\Decomb\Decomb.dll")
LoadPlugin("D:\Videotools\StaxRip-x64-2.0.7.4\Apps\Plugins\both\L-SMASH-Works\LSMASHSource.dll")
Import("D:\Videotools\StaxRip-x64-2.0.7.4\Apps\Plugins\AVS\Shader\Shader.avsi")
LoadPlugin("D:\Videotools\StaxRip-x64-2.0.7.4\Apps\Plugins\AVS\Shader\Shader.dll")
LoadPlugin("D:\Videotools\StaxRip-x64-2.0.7.4\Apps\Plugins\AVS\SmoothD2\SmoothD2.dll")
LoadPlugin("D:\Videotools\StaxRip-x64-2.0.7.4\Apps\Plugins\avs\VagueDenoiser\VagueDenoiser.dll")
LWLibavVideoSource("Z:\_ENCODE\LH-HMB\filename.ts", format = "YUV420P8")
#ConvertFromDoubleWidth(bits=10)
#AssumeFPS(25)
Telecide(guide = 1)
Decimate()
VagueDenoiser(threshold=0, method=1, nsteps=6, chromaT=2)
SmoothD2(quant=13, num_shift=3, Matrix=3, Qtype=1, ZW=1, ZWce=1, ZWlmDark=0, ZWlmBright=255, ncpu=4)
SuperXBR(Passes=2, Factor=2)
BTW, thanks for all your hard work over the years, it's very much appreciated!
stax76
6th March 2020, 17:38
I was googling 'Platform returned code 126' and the first post was a doom9 avisynth thread where Ligh said that it might miss a dependency, I checked then shader.dll with Dependency Walker and it listed D3D9.DLL and D3DX9_43.DLL as dependency.
https://www.microsoft.com/en-us/download/details.aspx?id=34429
colinhunt
6th March 2020, 18:01
Check if you have these DLLs in C:\Windows\System32, if not google for DirectX 9.
It was the missing D3DX9_43.dll that threw a wrench in the works. Copied the dll over from my old Win7 installation, and StaxRip is now churning away happily with SuperResXBR enabled. Thank you!
stax76
6th March 2020, 18:55
You're welcome. Next build includes a check for it.
JKyle
7th March 2020, 09:21
While remuxing an AAC audio stream via stream copy with a re-encoded HEVC video stream to an mp4 file, I found this weird behavior of StaxRip (2.0.7.4 Beta): it demuxes the HE-AAC audio stream (via MP4Box) to an mka format while demuxing the AAC-LC audio stream to an m4a format (as expected).
This produces a false warning that remuxing the original AAC(HE-AAC) audio stream via stream copy to an mp4 format is not appropriate, which is inappropriate itself.
https://i.imgur.com/JDMGm3E.jpg
On the other hand, this warning does not appear in the case of an AAC-LC audio stream, as a matter of course.
https://i.imgur.com/rGg8eX7.jpg
Well, is there any reason why an HE-AAC stream is demuxed to an mka format?
Thanks in advance.
stax76
7th March 2020, 09:54
2.0.7.5 Beta
------------
- fix: when the cut feature was used and afterwards the preview was
opened from the code editor then the cut settings got damaged
- fix: when AviSynthShader was used StaxRip did not show
a warning in case DirectX 9 is not installed
- fix: HE-AAC as demuxed as mka
- new: setting that allows to define how many frames
are used for auto cropping
- new: some default settings were changed
- new: the buttons in the preview dialog look much better now, also flicker
was eleminated and the button and trackbar size was increased,
standard buttons were used, I don't know how it looks on Win 7...
- new: the csv file content in the apps dialog was improved
- new: auto crop feature in crop dialog finally shows progress
- new: the avisynth and vapoursynth code editor has a new
'Advanced > Advanced Info' feature, it offers the following info:
avs2pipemod info, avsmeter info, avsmeter benchmark and vspipe info
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/u/s!ArwKS_ZUR01g0kH4d4eT_6a3GaKe?e=qbOfGS
Spunkmeyer
7th March 2020, 23:46
Hi Stax, I'm still getting the same exitcode crash referencing D:Projekte etc when trying to use Vapoursynth at the end of demuxing.
Using Avisynth as filters is working ok.
stax76
8th March 2020, 00:04
Hi Stax, I'm still getting the same exitcode crash referencing D:Projekte etc when trying to use Vapoursynth at the end of demuxing.
Using Avisynth as filters is working ok.
Please post either a link to the error message or post the error message.
Spunkmeyer
8th March 2020, 00:34
StaxRip.ErrorAbortException: Index LWLibav failed with exit code: -1073741515 (0xC0000135)
C:\Users\gouck\AppData\Local\Programs\VapourSynth\core\vspipe.exe "D:\****1080p_temp\ ****1080p_new.vpy" NUL -i
at StaxRip.Proc.Start() in D:\Projekte\VB\staxrip\General\Proc.vb:line 342
at StaxRip.MainForm.Indexing() in D:\Projekte\VB\staxrip\Forms\MainForm.vb:line 3193
at StaxRip.VideoScript.Synchronize(Boolean convertToRGB, Boolean comparePath, Boolean flipVertical) in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 237
at StaxRip.VideoScript.GetInfo() in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 444
at StaxRip.VideoScript.GetFrameCount() in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 458
at StaxRip.GlobalClass.IsValidSource(Boolean warn) in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 701
at StaxRip.MainForm.AviSynthListView_ScriptChanged() in D:\Projekte\VB\staxrip\Forms\MainForm.vb:line 5223
at StaxRip.FiltersListView.OnChanged() in D:\Projekte\VB\staxrip\Controls\FiltersListView.vb:line 271
at StaxRip.FiltersListView._Lambda$__14-0(VideoScript script) in D:\Projekte\VB\staxrip\Controls\FiltersListView.vb:line 30
at StaxRip.VideoScript.RaiseChanged() in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 22
at StaxRip.VideoScript.SetFilter(Int32 index, VideoFilter filter) in D:\Projekte\VB\staxrip\General\VideoScript.vb:line 92
at StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean isEncoding) in D:\Projekte\VB\staxrip\Forms\MainForm.vb:line 2069
stax76
8th March 2020, 01:10
Apparently my diagnostic code failed on multiple levels, 0xC0000135 should be STATUS_DLL_NOT_FOUND, try this:
Main Menu > Apps > Manage > type 'visual' in search field and install some VC++ Redist x64, also please post the generated vpy vapoursynth script, so I can fix the requirement detection as well as the exit code analysis.
edit:
Is there a _staxrip.log file?
Mister XY
8th March 2020, 12:36
In version 2.0.7.5 the chapters are not set automatically. You have to search and select the xml file via Container Options -> Options -> Chapters for each film. If you do not do this, the line in Chapters remains empty.
Patman
8th March 2020, 13:37
In version 2.0.7.5 the chapters are not set automatically. You have to search and select the xml file via Container Options -> Options -> Chapters for each film. If you do not do this, the line in Chapters remains empty.On github is an issue (https://github.com/staxrip/staxrip/issues/124) opened for this case. Look there, I uploaded a fix in the comments.
Taurus
8th March 2020, 16:34
On github is an issue (https://github.com/staxrip/staxrip/issues/124) opened for this case. Look there, I uploaded a fix in the comments.
Thank you, working as expected:thanks:
stax76
8th March 2020, 17:39
I hope it's getting more stable because I really want to get that 2.0.8.0 stable release out, please help to test.
2.0.7.6
-------
- fix: format compatibility was improved with an automated test
- fix: in the preview dialog the start position for mpc
and mpv was incorrect when cut ranges were active
- fix: chapter file not being picked up
- fix: in the filter setup profiles dialog a exception could
happen and loading a filter setup from the menu could fail
- fix: the filter parameter menu in the code editor was adding
parameters even if they were already existing with different casing
- fix: cutting could cause an error where staxrip generates
a chapter file without containing a ChapterAtom
- new: the logic to create and edit cut sections in the preview
dialog is now smarter and more flexible
- new: the assistant tells in case of a script error that the
full error can be shown by clicking the preview button
- new: MiniDeen avs filter added
- new: Advanced Info in the code editor was moved to the top level menu
and AviSynth Info() can be shown directly from the Advanced Info
without adding Info() to the script, staxrip generates the script
with perfect font size and shows it with mpv (paused, no osc, no osd)
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/u/s!ArwKS_ZUR01g0kH4d4eT_6a3GaKe?e=qbOfGS
NikosD
8th March 2020, 18:33
For your next version ALL rigaya's HW transcoders have new versions:
NVenc v4.68
QSVenc v3.33
VCEenc v5.04
stax76
8th March 2020, 19:44
@NikosD
I've updated it locally.
Spunkmeyer
8th March 2020, 20:18
I'm not even getting a chance to run a script when choosing VS as filters, it just bombs after demuxing as above.
JKyle
8th March 2020, 20:22
And Subtitle Edit was updated to 3.5.14 yesterday:
https://github.com/SubtitleEdit/subtitleedit/releases/tag/3.5.14
BTW, I noticed a sub-folder name change in the StaxRip\Apps\Plugins folder: Both ⇒ Dual
Well, just for you guys who just overwrite the whole folders/files. :)
Patman
8th March 2020, 20:47
For your next version ALL rigaya's HW transcoders have new versions:
NVenc v4.68
QSVenc v3.33
VCEenc v5.04
With the update of these three apps, a new option was added for each: --input-option
Another option has been added for QSVEnc: --vpp-colorspace
stax76
8th March 2020, 20:55
@Spunkmeyer
Look for a file that ends with _staxrip.log
@JKyle
I've updated it.
FreaQ
8th March 2020, 20:58
Hi,
I tried 2.0.7.6 and it's not usable.
I open a new video file with source "automatic". Demuxing is working, but then the program fails and I get the error message, that AviSynth+ was not found even so I installed 3.5 prior.
------------------------- Error opening source -------------------------
AviSynth+ installation cannot be found
LoadPlugin("D:\_Programme\_Portable\StaxRip-x64-2.0.7.6-beta\Apps\Plugins\both\ffms2\ffms2.dll")
FFVideoSource("D:\Video\Der Film_temp\Der Film.mkv", colorspace = "YV12", \
cachefile = "D:\Video\Der Film_temp\Kim Possible - Der Film.ffindex")
But what is even more painful is, that my version of 2.0.6.0 is also not working anymore.
I use both versions as portable installations with the settings folder in each portable folder. I reverted AviSynth+ to the previous version but 2.0.6.0 keeps on failing.
------------------------- Error opening source -------------------------
FFVideoSource: The index does not match the source file
(D:\Video\Billy the Kid_temp\Billy the Kid_source.avs, line 3)
LoadPlugin("D:\_Programme\_Portable\StaxRip-x64-2.0.6.0-stable\Apps\Plugins\both\ffms2\ffms2.dll")
FFVideoSource("D:\Video\Billy the Kid_temp\Billy the Kid.mkv", colorspace = "YV12", \
cachefile = "D:\Video\Billy the Kid_temp\Billy the Kid.ffindex")
Edit: 1.7.0.6 still works flawlessly.
stax76
8th March 2020, 21:12
With the update of these three apps, a new option was added for each: --input-option
Another option has been added for QSVEnc: --vpp-colorspace
I've already added it locally, don't anybody worry that a switch will be missed, it's not gonna happen. :)
https://github.com/staxrip/staxrip/blob/master/General/Test.vb
https://github.com/staxrip/staxrip/blob/master/Encoding/QSVEnc.vb#L116
stax76
8th March 2020, 21:21
@FreaQ
Post one screenshot of the AviSynth page in the apps dialog and one screenshot of your Windows Uninstall dialog showing your AviSynth+ 3.5 x64 installation.
FreaQ
8th March 2020, 21:28
https://abload.de/img/avisynth1sekuf.jpg
https://abload.de/img/avisynth252jql.jpg
stax76
8th March 2020, 21:32
In the apps dialog there is a runtime section where you can find 'Visual C++ 2015-2019', is that installed?
FreaQ
8th March 2020, 21:34
Yes. Status is OK.
Patman
8th March 2020, 21:55
@FreaQ have you updated the name of your folder that contains the AviSynth and Vapoursynth plug-ins? New name is dual, not both for staxrip 2.0.7.6 beta...
FreaQ
8th March 2020, 22:00
Where should I update it?
The path is: D:\_Programme\_Portable\StaxRip-x64-2.0.7.6-beta\Apps\Plugins\Dual
So I think I am fine here.
stax76
8th March 2020, 22:11
Is there any other tool that can open an avs script? You could create a version or colorbars script and then try to open with mpv or mpc, everything x64 of course.
stax76
8th March 2020, 22:21
It might be a dependency missing, as far as I know avs has only vc 2019 as dependency that is not part of all windows versions. You could try FileMon to find out which lib fails to load.
FreaQ
8th March 2020, 22:31
Is there any other tool that can open an avs script? You could create a version or colorbars script and then try to open with mpv or mpc, everything x64 of course.
I tried a version script.
It did not work with AviSynth 3.5.
But when I reverted to back to 0.1 R2772 it played fine in MPC-HC and VirtualDub.
stax76
8th March 2020, 22:37
Try reinstalling AviSynth 3.5 x64, for the case that AviSynth isn't working in general you have better chances somebody can help when you create a new thread. I don't see a reason why StaxRip should not work with on older AviSynth version.
https://github.com/pinterf/AviSynthPlus/releases
And you can also try VapourSynth, does almost exactly the same.
stax76
8th March 2020, 22:50
Could also help, all in one vc redist package:
https://github.com/abbodi1406/vcredist
FreaQ
8th March 2020, 22:51
You were right about dependencies.
Even so VC 2015-2019 was installed, I installed the latest versions (14.24.28127.4) for x86 and x64 which fixed the problem.
Thank you for your support, even the fault way my configuration.
JKyle
8th March 2020, 23:31
MKVToolNix 44.0.0 is released today.
https://www.videohelp.com/software/MKVToolNix
:)
stax76
8th March 2020, 23:50
MKVToolNix 44.0.0 is released today.
https://www.videohelp.com/software/MKVToolNix
:)
I've updated it.
@FreaQ
I notice now that the error handling needs improvement, it was calling the function LoadLibrary("AviSynth.dll") and it returned null which means error, staxrip reported this but it's not good enough because the OS can also provide a meaningful error message on request (by calling the GetLastError function), I'll fix it.
fredlkrue
9th March 2020, 18:39
You were right about dependencies.
Even so VC 2015-2019 was installed, I installed the latest versions (14.24.28127.4) for x86 and x64 which fixed the problem.
Thank you for your support, even the fault way my configuration.
Thank you, that fixes the issue I had with Windows 7.
stax76
9th March 2020, 19:03
@FreaQ
I further investigated the issue and the outcome was sadly that Windows only reports that a module failed to load but it's really not telling the name of the module, Windows only reports:
126 / hex 0x7e
ERROR_MOD_NOT_FOUND (winerror.h)
The specified module could not be found.
There are however system tools that can monitor the system and tell the name of the module, people in programming forums are saying that FileMon or Process Explorer can be used to get this information.
edit:
Even so VC 2015-2019 was installed, I installed the latest versions (14.24.28127.4) for x86 and x64 which fixed the problem.
I'll add a check that verifies a recent version is installed.
Natty
9th March 2020, 22:42
i would like to request 2 features, only if it's easy to implement.
1) compressibility test in CRF mode. currently it shows that option only in 2pass mode. please give some option to CRF which can estimate final bitrate with a small test.
2) batch only audio encoding. currently we need to drag-drop audio 1 by 1 in audio tab and right click - execute. not very useful for encoding 10-20 audios at once.
:thanks:
stax76
9th March 2020, 23:41
I cannot make promises, in particular not for the near future but I can tell you that I often bookmark posts that contain issues or request.
JKyle
11th March 2020, 06:18
Just out of curiosity:
Is there any way that I can change the UI font?
The default font is somewhat too wide, so sometimes the status bar message (such as estimated file size, etc.) is cropped.
I'd like to change the font to another fixed width font that's not too wide. :)
(FYI, I know about the UI Scale Factor option in Tools > Settings, but I don't want to re-scale my current UI.)
TomSmith
11th March 2020, 13:19
Just want to let you know that bitdefender is showing rav1e.exe being infected with ' Trojan.GenericKD.42833991' (2.0.7.6 beta).
Does anybody know anything about that? Is it serious?
stax76
11th March 2020, 15:39
Just out of curiosity:
Is there any way that I can change the UI font?
The default font is somewhat too wide, so sometimes the status bar message (such as estimated file size, etc.) is cropped.
I'd like to change the font to another fixed width font that's not too wide. :)
(FYI, I know about the UI Scale Factor option in Tools > Settings, but I don't want to re-scale my current UI.)
There ain't, next build increases the processing dialog width from 45 to 46, I hope that this fixes it
Just want to let you know that bitdefender is showing rav1e.exe being infected with ' Trojan.GenericKD.42833991' (2.0.7.6 beta).
Does anybody know anything about that? Is it serious?
Please try some online test on this file.
@all
The verification code needed some enhancement in order to enforce an up to date version of VC++ 2019, the code was a bit messy, so I had to rewrite much of it, I've tested it as good as possible so hope it's fine. The apps dialog got some improvements too.
Please everybody help to test so the stable version can be released as soon as possible, so I can take a longer break from staxrip, there has been much progress made since the last stable release.
### 2.0.7.7 Beta
- new: the apps management, verification and diagnostic has been improved
- fix: usage of too old VC++ 2019 runtime is now prevented
- update: qsvenc 3.33
- update: nvenc 4.68
- update: vceenc 5.04
- update: MiniDeen r6
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/u/s!ArwKS_ZUR01g0kH4d4eT_6a3GaKe?e=qbOfGS
JKyle
11th March 2020, 18:48
There ain't, next build increases the processing dialog width from 45 to 46, I hope that this fixes it.
I see. Thanks for the reply.
BTW, I think you forgot to mention that mkvtoolnix has been updated to 44.0.0 in 2.0.7.7 Beta.
-------------------------
And here's my questions:
1) Can't I change the default player in StaxRip from mpv.net to the Windows default player or something else?
I admit that mpv.net is a very powerful player, but sometimes I miss more convenient functions from other players. :(
2) In Preview, the Tools > External Player menu launches mpv.net (StaxRip default player) but doesn't seem to automatically open the video file in it.
https://i.imgur.com/zJqYpWW.gif
:thanks:
stax76
11th March 2020, 19:52
Can't I change the default player in StaxRip from mpv.net to the Windows default player or something else?
I admit that mpv.net is a very powerful player, but sometimes I miss more convenient functions from other players.
Which features do you miss in mpv.net? In the code editor and in the preview there is mpv and mpc support, you have to reset or config the preview menu, you don't see it in the menu because it was added after your settings were created. The old function uses internally the new function, I just tried it and it worked, maybe you use a vapoursynth script, the current libmpv build from shinchiro doesn't have vapoursynth enabled, I will have to create my own libmpv build which I will do when mpv.net development continues, very soon.
JKyle
11th March 2020, 21:21
Which features do you miss in mpv.net?
AFAIK, there's no way I can zoom in/out a video to a specific level like 50%, 100%, 150%, etc. or arbitrarily in mpv.net.
I'm not talking about 'fit to screen' or 'pan & scan'. I just want to zoom in/out a video based on its original resolution, not on the screen size.
(Fix me if I'm wrong.)
And mpv.net autofits a video based on its setting, but I'd like to view a video in its original resolution when it starts playing.
Besides, I can't seek a video based on the subtitle lines in mpv.net. By contrast, in PotPlayer (my default player), I can press Home or End button to seek to the previous/next subtitle line. I miss this function a lot.
In the code editor and in the preview there is mpv and mpc support, you have to reset or config the preview menu, you don't see it in the menu because it was added after your settings were created.
Thanks for the advice. (Sorry about my ignorance.)
Per your advice, I reset the Preview menus along with the overall menus (Tools > Edit Menu > Reset Everything).
Now the right click menu in Preview seems up to date:
https://i.imgur.com/J7MD9nG.jpg
However, the problem of not loading the avs script in mpv.net still exists. (I tried both 5.4.3.0 and 5.4.4.0 of mpv.net.)
On the other hand, 'Play with MPC' launches MPC-BE and plays the avs script very well.
But with VS, neither works (as you pointed out, maybe.)
What am I missing? :(
JKyle
11th March 2020, 21:45
However, the problem of not loading the avs script in mpv.net still exists. (I tried both 5.4.3.0 and 5.4.4.0 of mpv.net.)
On the other hand, 'Play with MPC' launches MPC-BE and plays the avs script very well.
Well, I finally figured out what was the problem: non-English/European-language filename.
The filename was in Korean, and the temp path automatically includes this Korean letter in it. This seems to prevent mpv.net from opening the avs script in the temp folder.
At this point, I raise this question: why can't mpv.net play an avs script in a non-English/European-language path whereas MPC-BE can?
I guess this is a bug in mpv.net and please fix this in the next version.
:thanks:
stax76
12th March 2020, 03:55
@JKyle
I've bookmarked the post on mpv.net.
Unfortunately I cannot reproduce the text encoding bug, generally avisynth does not support Unicode, because of that staxrip will show an error instead of loading the file, ANSII works here. I'm German, and we have three characters called Umlaute (ä ö ü), I've tried a file with the name of my favorite animal Eisbär (Polar bear) and mpv.net loads Eisbär_play.avs fine, please try if mpv opens an avs file with Korean characters:
mpv.exe "좋은 하루.avs"
Please also try to open the original mkv/mp4 file with mpv.net.
I hope it's not my bug because I would have to change my regional setting (risky?) or I would have to set up a VM.
Please show your system settings.
Desktop> Get-Culture
LCID Name DisplayName
---- ---- -----------
1031 de-DE German (Germany)
Desktop> Get-WinSystemLocale
LCID Name DisplayName
---- ---- -----------
1033 en-US English (United States)
Desktop> [Text.Encoding]::Default
IsSingleByte : True
BodyName : iso-8859-1
EncodingName : Western European (Windows)
HeaderName : Windows-1252
WebName : Windows-1252
WindowsCodePage : 1252
IsBrowserDisplay : True
IsBrowserSave : True
IsMailNewsDisplay : True
IsMailNewsSave : True
EncoderFallback : System.Text.InternalEncoderBestFitFallback
DecoderFallback : System.Text.InternalDecoderBestFitFallback
IsReadOnly : True
CodePage : 1252
JKyle
12th March 2020, 05:07
Please try if mpv opens an avs file with Korean characters.
Please also try to open the original mkv/mp4 file with mpv.net.
The thing is, if an avs file is named in English and placed in a path that doesn't include any Korean letters, mpv.net opens the file very well, which is quite natural.
(And video files, of course.)
Even if some of the letters in the path are in Korean, mpv.net successfully plays a video file in that path regardless of whether the filename is in English or Korean (via right click).
However, as for avs files, if any of the folder names in the path or the filename is in Korean, mpv.net fails to load (via right click) the avs file.
On the other hand, MPC-BE and MPC-HC successfully open the same avs file in the same path (via right click).
Here's the code of the avs file that causes the problem in mpv.net:
LoadPlugin("D:\Utilities\StaxRip\Apps\Plugins\Dual\L-SMASH-Works\LSMASHSource.dll")
LSMASHVideoSource("D:\Work\temp\테스트 영상.mp4")
#AssumeFPS(25)
Trim(1847, 6347)
The text in the avs file is encoded in ANSI.
Its name is "테스트 영상_new.avs" (Korean letters in the filename) and it is located in this path (Korean letters in the path):
D:\Work\temp\테스트 영상_temp\
("테스트 영상" means "test video" in Korean.)
Even if I move this avs file to the same folder where the video file("테스트 영상.mp4") is located("D:\Work\temp")(no Korean letters in the path), mpv.net still fails to open it.
But if I change the filename to "Test Video.avs" (no Korean letters in the filename along with no Korean letters in the path), mpv.net now successfully opens the avs file even if there's Korean letters in the avs file itself.
Please show your system settings.
Here it is:
PS D:\Work> Get-Culture
LCID Name DisplayName
---- ---- -----------
1033 en-US English (United States)
PS D:\Work> Get-WinSystemLocale
LCID Name DisplayName
---- ---- -----------
1042 ko-KR Korean (Korea)
PS D:\Work> [Text.Encoding]::Default
BodyName : ks_c_5601-1987
EncodingName : Korean
HeaderName : ks_c_5601-1987
WebName : ks_c_5601-1987
WindowsCodePage : 949
IsBrowserDisplay : True
IsBrowserSave : True
IsMailNewsDisplay : True
IsMailNewsSave : True
IsSingleByte : False
EncoderFallback : System.Text.InternalEncoderBestFitFallback
DecoderFallback : System.Text.InternalDecoderBestFitFallback
IsReadOnly : True
CodePage : 949
:thanks:
stax76
12th March 2020, 14:18
Please run this:
Desktop> Get-Culture; Get-UICulture; Get-WinSystemLocale; Get-WinDefaultInputMethodOverride; [Text.Encoding]::Default | select EncodingName,CodePage
LCID Name DisplayName
---- ---- -----------
1033 en-US English (United States)
1033 en-US English (United States)
1042 ko-KR Korean (Korea)
InputMethodTip : 0407:00000407
Description : German (Germany) - German
EncodingName : Korean
CodePage : 949
I can reproduce that mpv.net can't open the avs file with this culture settings but not any other player can open it either! Not mpv, not mpc-be, not mpc-hc, if mpv cannot open it than I can only file a bug report. Please try mpv, drag the Korean avs file on the mpv UI or use powershell, if you are not familiar with it, you can use absolute paths like so:
& 'absolute path to mpv.exe' 'absolute path to avs file'
Or use the crappy old cmd interpreter like so:
"absolute path to mpv.exe" "absolute path to avs file"
Not sure what the problem could be, we'll see, staxrip and virtualdub2 can open the Korean avs file, for mpc the reason why it works for you and not for me could be usage of different filters, in the mpc-be context menu choose 'Copy filters list to clipboard' while the Korean avs file is successfully loaded, show the list. A screenshot collection would help to replicate your environment exactly, right now it looks like a bug in mpv but it reports ffmpeg/demuxer as error source, I've tried ffmpeg -i and that works.
In mpc-be I get this filters for avs:
MPC-BE 1.5.4.4969
Filters currently loaded:
- Default DirectSound Device
- Enhanced Video Renderer (custom presenter)
- Audio Switcher
- LAV Video Decoder
- MPC Audio Decoder
- LAV Splitter Source
- MPC MP4/MOV Source
This is the error I get from mpv:
https://i.postimg.cc/7ZGmS3Sz/Untitled.png
I open files with mpc-be using Open with++ but I also tried with drag and drop, neither works.
JKyle
12th March 2020, 19:32
@Stax
I get the following results. Almost the same as yours except that my MPC-HC and MPC-BE can open a Korean named avs file in a Korean named path.
I'm attaching my test result.
[Environment Variables in PowerShell]
PS D:\Work\tmp> Get-Culture; Get-UICulture; Get-WinSystemLocale; Get-WinDefaultInputMethodOverride; [Text.Encoding]::Default | select EncodingName,CodePage
LCID Name DisplayName
---- ---- -----------
1033 en-US English (United States)
1033 en-US English (United States)
1042 ko-KR Korean (Korea)
InputMethodTip : 0412:{A028AE76-01B1-46C2-99C4-ACD9858AE02F}{B5FE1F02-D5F2-4445-9C03-C568F23C99A1}
Description : Korean (Korea) - Microsoft IME
EncodingName : Korean
CodePage : 949
[AVS file path\name]
D:\Work\tmp\테스트 영상_temp\테스트 영상_new_play.avs
[AVS file content: encoded in ANSI]
LoadPlugin("D:\Utilities\StaxRip\Apps\Plugins\Dual\L-SMASH-Works\LSMASHSource.dll")
LSMASHVideoSource("D:\Work\tmp\테스트 영상.mp4")
#AssumeFPS(25)
[Run mpv in Powershell: mpv-x86_64-20200308-git-28ea1ed, Portable]
PS D:\Work\tmp> & 'D:\Utilities\mpv\mpv.exe' 'D:\Work\tmp\테스트 영상_temp\테스트 영상_new_play.avs'
PS D:\Work\tmp>
=> returns to prompt without any response
So I registered mpv in the user PATH environment variable and moved the cwd to the Korean named folder.
I ran mpv in Powershell again this time with a different command line.
PS D:\Work\tmp\테스트 영상_temp> mpv '.\테스트 영상_new_play.avs'
[ffmpeg/demuxer] avisynth: Import: couldn't open "D:\Work\tmp\��Ʈ ����_temp\??? ??_new_play"
[lavf] avformat_open_input() failed
[ffmpeg/demuxer] avisynth: Import: couldn't open "D:\Work\tmp\��Ʈ ����_temp\??? ??_new_play"
[lavf] avformat_open_input() failed
Failed to recognize file format.
Same result as yours. I suspect both mpv and avisynth are responsible for failing to parsing the path/name.
Or maybe PowerShell cannot transfer the path\filename in the correct text encoding that ffmpeg can recognize (UTF-8 or whatever).
Just in case, I changed the codepage of PowerShell to 65001(UTF-8) but I get the same error.
I tried mpv.net(5.4.4.0, Portable) instead, but I get the same results. (No wonder... :()
This time I open the same Korean named avs file (in the Korean named path) successfully in both MPC-HC(installed) and MPC-BE(portable).
Here's the filter info:
[MPC-HC (Nightly, 64-bit, 1.9.1.34 (a771140f7)), Installed]
Filters currently loaded:
- madVR
- AVI/WAV File Source
[MPC-BE (64-bit, 1.5.4 (build 4969)), Portable]
MPC-BE 1.5.4.4969
Filters currently loaded:
- MPC Video Renderer (external)
- AVI/WAV File Source
Well, I know AviSynth+ doesn't support UTF-8 encoded avs files, but I didn't know it doesn't support non-English filenames either. :(
Or is it a bug embedded in mpv?
And my impression with PowerShell (or Windows) is that the codepage inconsistency (UTF-8 vs localized ANSI) makes a lot of problems.
With the default localized ANSI, PowerShell can't parse unicode(UTF-8) error messages from FFmpeg correctly.
When I change the codepage to UTF-8(65001), this time PowerShell doesn't allow me to type in Korean letters. :(
Anyway, thanks a lot for your precious time and concern.
I hope we can find a fix for this problem.
:thanks:
JKyle
12th March 2020, 20:43
@Stax
For your reference, I screen-recorded my test: right-click to open a Korean named avs file in a Korean named folder.
https://youtu.be/PzMYhZYDBqs
As you can see, all my players except mpv.net/mpv can open this avs file.
(Since madVR cannot be recorded in my screen recording app, I skipped it, but MPC-HC with madVR certainly opens the file.)
Spunkmeyer
12th March 2020, 20:47
I have managed to resolve the VS errors I was getting, seems it didn't like the beta versions of VS or Python.
Keep up the good work Stax.
stax76
12th March 2020, 21:05
@JKyle
Looks like a bug in mpv, I've just reported it here:
https://github.com/mpv-player/mpv/issues/7522
For mpc we simply have different settings resulting in different source filters used.
Thank you for the tests and detailed info!
JKyle
12th March 2020, 22:36
Looks like a bug in mpv, I've just reported it here:
https://github.com/mpv-player/mpv/issues/7522
Thanks a million. But your issue was closed by one of the mpv maintainers, wm4.
Well, it looks obvious that mpv developers are not interested in making mpv play avs/vs files correctly.
So for this reason plus others, I'd like to ask you if you could add an option in StaxRip to change the default player (source or target right-click > play) to some other players or add PotPlayer in the Apps menu.
(The default binary path to PotPlayer 64bit is C:\Program Files\DAUM\PotPlayer\PotPlayerMini64.exe)
Yes, it is my personal desire, and if you think it is too much, you can just ignore it. :)
:thanks:
stax76
12th March 2020, 23:36
Thanks a million. But your issue was closed by one of the mpv maintainers, wm4.
Well, it looks obvious that mpv developers are not interested in making mpv play avs/vs files correctly.
I think he is the lead dev and from the same country as me but likely uses Linux as primary OS like most mpv devs so it's understandable that he has little interest in this issue. There are some Windows devs for instance Rossy, maybe I can fix it if nobody else does.
So for this reason plus others, I'd like to ask you if you could add an option in StaxRip to change the default player (source or target right-click > play) to some other players or add PotPlayer in the Apps menu.
I've only limited amount of respect for mpc and hardly any for potplayer as it's not open source but uses open source code and adware. So far I think staxrip passes time position, aspect ratio, subtitles and audio tracks via command line to mpv and next builds will also pass color info, almost nothing of this can be achieved with any other player, they hardly ever helped me with anything, they can't even play my files, only mpv can play my 4K 50 fps HDR files with my low end GT 1030card.
https://mpv.io/manual/master/#video-filters-%3Ccolormatrix%3E
JKyle
13th March 2020, 01:51
Maybe I can fix it if nobody else does.
I'd appreciate it if you do so.
I've only limited amount of respect for mpc and hardly any for potplayer as it's not open source but uses open source code and adware. ...only mpv can play my 4K 50 fps HDR files with my low end GT 1030card.
I see. Thanks, and keep it up! :)
stax76
13th March 2020, 15:39
@JKyle
It's not solved but there is a very interesting workaround, changing the default code page of the OS to UTF-8, this will enable full Unicode support for AviSynth, it's working and hopefully does not break other things, I've enabled it and hope for the best.
https://forum.doom9.org/showthread.php?p=1903639#post1903639
JKyle
13th March 2020, 22:10
It's not solved but there is a very interesting workaround, changing the default code page of the OS to UTF-8, this will enable full Unicode support for AviSynth, it's working and hopefully does not break other things, I've enabled it and hope for the best.
https://forum.doom9.org/showthread.php?p=1903639#post1903639
You mean this, right?
https://i.imgur.com/fa2MpaP.jpg
Yes, you're right. This setting enables non-single-byte language named avs files to be played in mpv/mpv.net. I'm really happy to see that. I appreciate your advice.
However, there's one catch: Korean input via Korean IME does not work well in some 32-bit (maybe?) apps. XYplorer, my favorite file management app, is a typical example. I know this is a bug in those apps, so I'm gonna report to the developers about this.
Meanwhile, I'll be sticking to your solution. Thanks again. :)
stax76
14th March 2020, 02:21
A new stable release 2.0.8.0 is now available.
It features fast rendering in the preview and crop dialog and many small detail improvements.
Thanks to Patman and everybody else for helping with updates and builds, testing and reporting issues.
I'll be working a little on mpv.net and some other project next and hope being able to write documentation for staxrip sometime this or next year.
Changelog:
https://github.com/staxrip/staxrip/blob/master/Changelog.md
Download:
https://github.com/staxrip/staxrip/releases
craigpro
14th March 2020, 05:52
Thank you stax76!
Atlantis
14th March 2020, 05:54
Thank you for the new version.
I tested and 2.0.8.0 is slightly faster than 2.0.6.0 when encoding using x265.
DavidRyan
14th March 2020, 11:27
Thanks for all your work on the new version.
JKyle
14th March 2020, 13:35
@stax76
Many thanks for your hard work and precious output. :)
:thanks:
imhh11
14th March 2020, 17:16
thanks for the update stax
DMagic1
14th March 2020, 18:39
Im sorry if this is covered somewhere but I havent seen it. Is there a way for Staxrip to pull the chapters from the mkv file your reencoding automatically? I usually have to create the chapter.xml file manually, then load it from the same mkv I just loaded into Staxrip.
SaboraPie
14th March 2020, 19:33
Very very thaks for the new update!!!!!
-QfG-
14th March 2020, 20:31
I have problems with 2.0.8.0. I updated today from 2.0.6.0. The problems are with DNxHR HQX YUV422 input files. So StaxRip says, that ConverttoYV12 can only handle 8-Bit Video types. This is correct. But i have no line in my StaxRip Editor Window with "ConvertoYV12()". The line 4 in my AVS Script have really "ConverttoYV12()" inside, but why?
If i delete this line in the AVS Script and do the same the second time, this line will be automatically created. I must roll back to 2.0.6.0, no chance with the newest version.
AVS Script:
LoadPlugin("E:\VIDEOTOOLS\AVIS riPPen\StaxRip-x64-2.0.8.0-stable\Apps\Plugins\Dual\L-SMASH-Works\LSMASHSource.dll")
LSMASHVideoSource("E:\Video\Silent Hill\Untitled.mov", format="YUV422P10")
ConvertToYUV420()
ConvertToYV12()
Crop(0, 0, -0, -0)
Addborders(0, 0, 0, 0)
With v2.0.6.0 the same template works fine! Here 2 pictures what i mean, if i add my Intermediate into the source row.
https://s19.directupload.net/images/200314/5jbbx433.png
https://s19.directupload.net/images/200314/seo2r8e2.png
AMED
14th March 2020, 21:03
@-QfG-
Is Tools > Settings > Video | Add filter to convert Chroma subsampling to 4:2:0 enabled? try turning that off.
I think it's always wise to rebuild your profiles when you change stable builds. I've seen some really wacky stuff happen.
@DMagic1,
I've never had any problems with Chapters but i mainly use file batch mode for my encoding runs.
-QfG-
14th March 2020, 22:04
@-QfG-
Is Tools > Settings > Video | Add filter to convert Chroma subsampling to 4:2:0 enabled? try turning that off.
Thanks mate, this is the solution. :thanks:
@Stax I would change "ConverttoYV12()" with "ConvertToYUV420()", so this option works with 10bit videos, too.
Patman
14th March 2020, 22:45
thank you stax,
if I find time, I will try to fix issues and upload corresponding fixes ;)
SD70ACEJM
14th March 2020, 23:24
I am having an issue with StaxRip not loading the frameserver.dll. Where exactly am I supposed to put the dll at? Currently it's in the same folder as the program itself.
Edit
Then it erases my script and does this. It wipes it out, makes a new one and changes MPEG2Source to Import.
LoadPlugin("C:\Users\sd70a\Downloads\StaxRip-x64-2.0.8.0-stable\Apps\Plugins\AVS\yadifmod2\yadifmod2.dll")
Import("C:\1111Ripped DVDs\Jayce and the Wheeled Warriors 02. The Vase of Xiang_temp\Jayce and the Wheeled Warriors 02. The Vase of Xiang.avs")
Patman
14th March 2020, 23:38
I am having an issue with StaxRip not loading the frameserver.dll. Where exactly am I supposed to put the dll at? Currently it's in the same folder as the program itself.
Edit
Then it erases my script and does this. It wipes it out, makes a new one and changes MPEG2Source to Import.
LoadPlugin("C:\Users\sd70a\Downloads\StaxRip-x64-2.0.8.0-stable\Apps\Plugins\AVS\yadifmod2\yadifmod2.dll")
Import("C:\1111Ripped DVDs\Jayce and the Wheeled Warriors 02. The Vase of Xiang_temp\Jayce and the Wheeled Warriors 02. The Vase of Xiang.avs")
Hi SD70ACEJM,
frameserver.dll in program folder is right. Have you installed latest VCRedist (https://github.com/abbodi1406/vcredist/releases/latest)?
SD70ACEJM
14th March 2020, 23:46
Hi SD70ACEJM,
frameserver.dll in program folder is right. Have you installed latest VCRedist (https://github.com/abbodi1406/vcredist/releases/latest)?
I'm going through the process now. It took a bit to install, now I am installing the 2019 version. When I went in to the Manage, all of my runtimes said OK, before I downloaded the link you provided. I'll check back in a few with an update. Thanks for the help!
jlw_4049
15th March 2020, 05:15
Thanks for the updates. Will encode a 4K HDR film tonight with it!
SD70ACEJM
15th March 2020, 13:06
No luck. Everytime I enter my script into StaxRip it crashes and wipes my script clean. It leaves me with an avs of import(and my location). I can load the same script in VirtualdubMod2 and it works ok.
DenFox
15th March 2020, 14:43
Hello guys, I have 2.0.6.0 installed and I wanted to update to the latest 2.0.8.0.
I tried Tools->Advanced->Check for Update but nothing happens, how can I update Staxrip?
I have some settings saved in the 2.0.6.0, I just can't download and use 2.0.8.0 because in this way I will lose it.
ukmark
15th March 2020, 15:10
Im sorry if this is covered somewhere but I havent seen it. Is there a way for Staxrip to pull the chapters from the mkv file your reencoding automatically? I usually have to create the chapter.xml file manually, then load it from the same mkv I just loaded into Staxrip.
Tools > Settings > PreProcessing > then edit "mkvextract" entry and ensure "Chapters Demuxing" is selected.
stax76
15th March 2020, 17:08
@JKyle
Changing my codepage to UTF8 has caused a very small issue in the stable release, the crop dialog showed the Plus–minus sign ∓ which has the code point 177, with UTF8 it shows an error symbol. What I did to prevent something like this to happen in the future is to improve the release script, it scans now all source code files and returns an error if anything non ASCII is found, overall two non ASCII characters were in the original code, and they could be replaced easily. I've found a suspicious line in the ffmpeg source but cannot report it without analyzing it with a debugger, working with non Visual Studio code is very difficult for me, I soon have to learn it because I need a custom libmpv build so mpv.net can open vapoursynth scripts. I hope qyot27 does something regarding the ffmpeg issue.
@Stax I would change "ConverttoYV12()" with "ConvertToYUV420()", so this option works with 10bit videos, too.
I want to work on mpv.net and Open with++ but have bookmarked the post to examine it later.
I am having an issue with StaxRip not loading the frameserver.dll. Where exactly am I supposed to put the dll at? Currently it's in the same folder as the program itself.
With which version does this happen? A recent improvement is supposed to prevent exactly this problem. If that happens with the last build than it won't be easy to find the reason. Before StaxRip uses the DLL it is supposed to verify and enforce the presence of a recent VC++ 2019 runtime, without having installed that the DLL should not be loaded and if the runtime is installed the DLL should be found and loaded, the DLL is located in the startup directory and that directory has the highest priority when the OS looks for DLLs.
Then it erases my script and does this. It wipes it out, makes a new one and changes MPEG2Source to Import.
When you open any kind of source staxrip typically creates a _temp folder besides the source file and saves its scripts and temp files in this folder, maybe there is some logic somewhere that prevents creating and using the _temp folder but uses the folder of the original source, I tried to find such a logic in the code without success, you would have to tell me how to reproduce this behavior.
Hello guys, I have 2.0.6.0 installed and I wanted to update to the latest 2.0.8.0.
I tried Tools->Advanced->Check for Update but nothing happens, how can I update Staxrip?
I have some settings saved in the 2.0.6.0, I just can't download and use 2.0.8.0 because in this way I will lose it.
There are probably issues with the auto update feature, I've bookmarked the post and examine it sometime later.
stax76
15th March 2020, 17:45
OK, I think I found the issue with the external avs file, it happened with relative paths like this:
LSMASHVideoSource("aaa.mp4")
### 2.0.8.12 Beta without apps
- fix: external avs/vpy scripts that use relative instead of
absolute paths failed to load
### 2.0.8.11 Beta without apps
- new: Version is shown in main dialog title bar
- fix: event command issue
- fix: layout and usability issue in audio dialog (Patman)
https://staxrip.readthedocs.io/intro.html#download
cyanfire
15th March 2020, 19:37
I am having issues using QTGMC using 2.0.8.0 when i enable it staxrip crashes, any help on fixing this?
stax76
15th March 2020, 19:41
Maybe study and post in following threads:
https://github.com/staxrip/staxrip/issues/125
https://forum.doom9.org/showthread.php?t=174544
cyanfire
15th March 2020, 19:58
Maybe study and post in following threads:
https://github.com/staxrip/staxrip/issues/125
https://forum.doom9.org/showthread.php?t=174544
I needed AVX version of plugins_JSPDR.dll, working now! Thankyou for pointing me to the first thread
stax76
15th March 2020, 20:05
Which one did you use?
Release_Intel_W7_Core2_AVX
Release_W7_AVX
edit:
The included one was Release_W7_AVX2, I'll replace it with Release_W7_AVX.
JKyle
15th March 2020, 20:31
Changing my codepage to UTF8 has caused a very small issue in the stable release, the crop dialog showed the Plus–minus sign ∓ which has the code point 177, with UTF8 it shows an error symbol. What I did to prevent something like this to happen in the future is to improve the release script, it scans now all source code files and returns an error if anything non ASCII is found, overall two non ASCII characters were in the original code, and they could be replaced easily. I've found a suspicious line in the ffmpeg source but cannot report it without analyzing it with a debugger, working with non Visual Studio code is very difficult for me, I soon have to learn it because I need a custom libmpv build so mpv.net can open vapoursynth scripts. I hope qyot27 does something regarding the ffmpeg issue.
Thanks a lot. :)
### 2.0.8.12 Beta without apps
- fix: external avs/vpy scripts that use relative instead of
absolute paths failed to load
### 2.0.8.11 Beta without apps
- new: Version is shown in main dialog title bar
- fix: event command issue
- fix: layout and usability issue in audio dialog (Patman)
I've found 2.0.8.12 Beta has one critical issue and one minor issue.
1) Critical Issue
The FrameServer.dll shipped with it (148 KiB, 2.0.8.12 Beta was downloaded from DropBox) causes this FrameServer.dll error, which looks familiar.
https://forum.doom9.org/showthread.php?p=1902400#post1902400
So I replaced it with the one shipped with 2.0.8.0 stable (32 KiB), and now the error is gone.
2) Minor Issue
The main window doesn't remember its last position. Every time I start up StaxRip, it appears at a location not intended by me. :(
stax76
15th March 2020, 21:05
The FrameServer.dll shipped with it (148 KiB, 2.0.8.12 Beta was downloaded from DropBox) causes this FrameServer.dll error, which looks familiar.
Previously I switched between debug and release manually but since it was very cumbersome to do that I integrated building into the release script while porting the script from VB.NET to PowerShell yesterday, probably something is wrong with the new script, the code is so simple that I didn't expect that something could go wrong, calls the build tool with Release config and checks the exit code afterwards.
& $msBuild ($PSScriptRoot + '\StaxRip.sln') /p:Configuration=Release /p:Platform=x64
if ($LastExitCode)
{
throw $LastExitCode
}
The main window doesn't remember its last position. Every time I start up StaxRip, it appears at a location not intended by me.
I'll investigate it.
cyanfire
15th March 2020, 21:49
Which one did you use?
Release_Intel_W7_Core2_AVX
Release_W7_AVX
edit:
The included one was Release_W7_AVX2, I'll replace it with Release_W7_AVX.
Yeah i used Release_W7_AVX
stax76
15th March 2020, 22:16
Here is another fix including apps this time (new release script makes it easier to upload builds):
### 2.0.9.1 Beta
- new: Check for Updates added to main menu in Help section
- fix: QTGMC did not work on systems without AVX2
- fix: Window position of the main dialog was not remembered
- fix: FrameServer.dll again released as debug build because
of a bug in the new release script
https://github.com/staxrip/staxrip/blob/master/Changelog.md
https://staxrip.readthedocs.io/intro.html#download
DavidRyan
15th March 2020, 22:33
Seeing this change: "The included one was Release_W7_AVX2, I'll replace it with Release_W7_AVX.", I assume for those of us with AVX2-capable processors it will be to our advantage to copy over the AVX2 version of this dll if we update in future? If QTGMC is making use of AVX2 in some way I'm guessing there is a performance advantage to keeping this one, esp given how demanding QTGMC can be.
JKyle
16th March 2020, 00:47
Seeing this change: "The included one was Release_W7_AVX2, I'll replace it with Release_W7_AVX.", I assume for those of us with AVX2-capable processors it will be to our advantage to copy over the AVX2 version of this dll if we update in future? If QTGMC is making use of AVX2 in some way I'm guessing there is a performance advantage to keeping this one, esp given how demanding QTGMC can be.
Like you pointed out, AVX2-enabled CPU users can always overwrite the plugins_JPSDR.dll file in
StaxRip\Apps\Plugins\AVS\JPSDR\
with the up-to-date Release_W7_AVX2 build of JPSDR from its git site (https://github.com/jpsdr/plugins_JPSDR/releases).
Well, I think it's a matter of whether StaxRip maintains universality or gains efficiency that StaxRip ships with an AVX-only version of JPSDR.
And as most of you would agree, this issue is totally up to @stax.
But of course I agree that there needs to be some documentation on this matter - at least on the online manual. :)
Atlantis
16th March 2020, 00:53
Something is missing in 2.0.8.0. that existed before.
In the crop window, you had two zoom squares in the middle on the bottom and top where the crop was. You could easily see how much to crop in zoomed in boxes.
Now it is gone. You see no zoom. This was very important.
MrBrownCow
16th March 2020, 03:10
Does anyone with a 3rd gen Ryzen processor get their CPU fully utilized or is x265 just not good at taking advantage of too many cores...
I'm ok with it, was just curious if there were tweaks or anything that lead to more cores being utilized. Maybe Ryzen master profiles anyone has seen work well for staxrip?
https://i.imgur.com/IqtunAI.png
stax76
16th March 2020, 03:23
In the Apps dialog there is a short description for each tool, it's now updated to show 'Included is the W7 AVX variant'. Users can either replace it or define an external path. Maybe somebody can request a single variant from JPSDR. I don't have much time to do more about it.
In the crop window, you had two zoom squares in the middle on the bottom and top where the crop was. You could easily see how much to crop in zoomed in boxes.
Now it is gone. You see no zoom. This was very important.
The Direct2D API is very different from the API (WinForms/GDI) that was used before, would probably take some time, so I don't plan to put it back, sorry.
JKyle
16th March 2020, 03:40
Does anyone with a 3rd gen Ryzen processor get their CPU fully utilized or is x265 just not good at taking advantage of too many cores...
I'm ok with it, was just curious if there were tweaks or anything that lead to more cores being utilized. Maybe Ryzen master profiles anyone has seen work well for staxrip?
https://i.imgur.com/IqtunAI.png
AFAIK, it depends on the resolution of the input video and thread settings in x265.
Please read this post and others in the thread.
https://forum.doom9.org/showthread.php?p=1827973#post1827973
And if you're interested in utilizing more threads via distributed encoding with x265, you better consider giving a try to RipBot264 (https://www.videohelp.com/software/RipBot264).
ukmark
16th March 2020, 17:30
Looks like you choose the decoder, preset, profile, level, encoding method and quality setting, and output resolution. With h264 if I change the ICQ setting from say 24 to 26, the resulting file size is reduced as you would expect. However, with h265, changing the ICQ level has no effect on the file size produced.
Does this seem like an Intel bug with h265 ICQ on fixed function encoding, or is it a QSVEnc bug (rigaya) or even something in StaxRip??
I've also asked the question on rigaya's QSVEnc github.
This is a bug with Inel Media SDK. I raised issue on github (https://github.com/Intel-Media-SDK/MediaSDK/issues/1977), and they found out that (for some unknown reason so far), the quality used by ICQ fixed-function encoding for 8bit or 10bit HEVC is "hard coded" to 26 and ignores your chosen level.
Another issue I reported (https://github.com/Intel-Media-SDK/MediaSDK/issues/1980) has been passed on to their documentation team I believe. This is to do with using CQP 10bit HEVC encoding.
It appears that the QP range of 1-51 is for 8bit HEVC (have not tested AVC), and for 10bit the QP range is extended from 1-63. I was getting huge file sizes for 10bit HEVC vs 8bit HEVC when using CQP mode. The defaults in StaxRip for CQP are I:24, P:26 and B:27.
FYI I am using I:33, P:33 and B:37 with 9 b-frames for 10bit HEVC CQP mode, and am very happy with the results. I was previously using ICQ, but very occasionally with sudden very high motion scenes, I would get a lot of blockiness during playback (maybe HEVC ICQ with lookahead might help if/when it gets implemented). I found with above settings for CQP, encodes have no blockiness and by using 9 b-frames along with b-pyramid being set on, file sizes are very acceptable (on average between 5-15% higher than CRF 24 with x265 SW encoding, and very similar visual quality). Playback is via Amlogic S905x2 box running CoreELEC OS and is hardware decoded by the box. (I think at one time, some media players couldn't handle a large number of b-frames, but that issue does not exist with S905x2 and CoreELEC.)
DMagic1
17th March 2020, 15:02
I recently updated Staxrip after not updating for a while from 2060 to 2080. I have used a code to add boarders to videos that had none.
AddBorders(0, (1080 - %source_height% )/2, 0, (1080 - %source_height% )/2, color_black)
This worked very well and I had no issues. I'm not sure if it was after to update but now when I process a video it comes out in the same input resolution without the boarders even though the preview looks correct. The "new" avs file has the code and when I test play it the boarders are there.
DMagic1
18th March 2020, 01:07
I recently updated Staxrip after not updating for a while from 2060 to 2080. I have used a code to add boarders to videos that had none.
AddBorders(0, (1080 - %source_height% )/2, 0, (1080 - %source_height% )/2, color_black)
This worked very well and I had no issues. I'm not sure if it was after to update but now when I process a video it comes out in the same input resolution without the boarders even though the preview looks correct. The "new" avs file has the code and when I test play it the boarders are there.
So it seems it was because I had the wrong decoder selected.
taulen
18th March 2020, 10:56
Is it possible to run StaxRip on 2 separate machines while using the same source file from a shared folder ? When trying this staxrip seems to crash because of writing to the same temp /log file ?
The workaround seems to be to duplicate the source file before starting the process, but that seems a bit wasteful and takes time on 5400 rpm drives :P
AMED
18th March 2020, 19:29
Hi Stax76
I'm currently using a single instance of StaxRip on 2 computers via mapped share to process a single job queue . After upgrading to from v2.0.6.0 version to v2.0.8.0 (also tested 2.0.9.12) the file path for the setting changes from the mapped drive to the full UNC path which borks a lot of the plugins from working.
Computer1 has a physical Z drive. Computer2 has Computer1's Z drive mapped as Z drive so the path references will be the same.
E.g. v2.0.6.0 in the registry after clicking browse for custom directory and selecting "Z:\Bluray\StaxRip\Settings"
Computer1 Setting location
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"Z:\\Bluray\\Staxrip\\"="Z:\\Bluray\\StaxRip\\Settings\\"
Computer2 Setting location
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"Z:\\Bluray\\Staxrip\\"="Z:\\Bluray\\StaxRip\\Settings\\"
E.g. v2.0.8.0 (and v2.0.9.12) in the registry after clicking browse for custom directory and selecting "Z:\Bluray\StaxRip\Settings"
Computer1 Setting location
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"Z:\\Bluray\\Staxrip\\"="Z:\\Bluray\\StaxRip\\Settings\\"
Computer2 Setting location in registry
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"\\\\192.168.11.1\\z$\\Bluray\\StaxRip\\"="Z:\\Bluray\\StaxRip\\Settings\\"
If i try and delete that key and manually create it like on Computer1 i just get prompted for the settings directory again when i open StaxRip.
Z'Hadum
19th March 2020, 07:34
Hi Stax76
I'm currently using a single instance of StaxRip on 2 computers via mapped share to process a single job queue . After upgrading to from v2.0.6.0 version to v2.0.8.0 (also tested 2.0.9.12) the file path for the setting changes from the mapped drive to the full UNC path which borks a lot of the plugins from working.
Computer1 has a physical Z drive. Computer2 has Computer1's Z drive mapped as Z drive so the path references will be the same.
E.g. v2.0.6.0 in the registry after clicking browse for custom directory and selecting "Z:\Bluray\StaxRip\Settings"
Computer1 Setting location
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"Z:\\Bluray\\Staxrip\\"="Z:\\Bluray\\StaxRip\\Settings\\"
Computer2 Setting location
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"Z:\\Bluray\\Staxrip\\"="Z:\\Bluray\\StaxRip\\Settings\\"
E.g. v2.0.8.0 (and v2.0.9.12) in the registry after clicking browse for custom directory and selecting "Z:\Bluray\StaxRip\Settings"
Computer1 Setting location
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"Z:\\Bluray\\Staxrip\\"="Z:\\Bluray\\StaxRip\\Settings\\"
Computer2 Setting location in registry
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"\\\\192.168.11.1\\z$\\Bluray\\StaxRip\\"="Z:\\Bluray\\StaxRip\\Settings\\"
If i try and delete that key and manually create it like on Computer1 i just get prompted for the settings directory again when i open StaxRip.
I realized the same: To workaround it, you can choose in the "Settings path dialog" at first startup a custom directory and then choose the path with the mapped drive.
AMED
19th March 2020, 08:22
@Z'Hadum
That's what i have been doing and still uses the UNC path.
https://i.ibb.co/0MQFhzj/Staxrip-UNC.png (https://ibb.co/0MQFhzj)
stax76
19th March 2020, 09:44
There was a bug with UNC paths so a recent beta would be needed:
https://staxrip.readthedocs.io/intro.html#download
Please try:
Main Menu > Options > Paths > Temp Files Folder
AMED
19th March 2020, 17:52
thanks stax76,
I am testing with the latest beta.
https://i.ibb.co/qg3KjkM/Staxrip-2-0-9-12.png (https://ibb.co/qg3KjkM)
My Temp Files folder is "C:\TMP\%source_name%_temp" since i do the processing on each computers C: Drive and then my default target folder is "Z:\Bluray\Conversion".
ENiGMA59
19th March 2020, 19:40
Hi ,
i search add automated lines in staxrip at each encodage , i use line in cmd not automated
line :
C:\>"C:\ffmpeg.exe" -i "C:\Input\input.mkv" -c copy -bsf:v 'filter_units=remove_types=6' "C:\Output\output.mkv"
thanx for reps :)
almanteka
20th March 2020, 09:11
hi! why when i use the single file option to add a video file the StaxRip window is filled with the data from the video and audio and i can make changes to the job before is started? and when is in a batch when i select a job from tools > jobs the window remain empty and i can't change anything before the job is started? the only visible change is the window title!
https://i.imgur.com/tlet04Y.jpg
stax76
20th March 2020, 15:16
In StaxRip you first change the setting and afterwards add files for batch processing which will immediately create batch jobs.
I don't know if these jobs can be modified afterwards and I don't recommend trying it.
ukmark
20th March 2020, 15:55
hi! why when i use the single file option to add a video file the StaxRip window is filled with the data from the video and audio and i can make changes to the job before is started? and when is in a batch when i select a job from tools > jobs the window remain empty and i can't change anything before the job is started? the only visible change is the window title!
With batch jobs, you first set up how you want to process the files and then select your batch. The settings you have in place will be applied to all files in that batch.
You can exclude individual files (untick them when you are presented with the job list). This method assumes that all files in the batch are to be processed exactly the same.
almanteka
20th March 2020, 18:43
thanks for your replies @stax76 and @ukmark! is there is a way to add multiple files as individual jobs without using batch? maybe an script? i'm using the same template for the files, but some files needs cropping, in others the audio files are undetermined and not correctly selected! i know that adding the files one by one fulfill what i'm looking for, but that takes time! thanks in advance for any suggestions!
almanteka
20th March 2020, 21:51
is there is any issue with MediaInfo Folder View? with StaxRip-x64-2.0.8.0-stable it don't populate the media info!
EDIT:
ok, found out the problem is MediaInfo, changed the MediaInfo.dll to v0.7.96 and populates correctly!
stax76
21st March 2020, 13:20
ok, found out the problem is MediaInfo, changed the MediaInfo.dll to v0.7.96 and populates correctly!
This will break things! Maybe I redo it from scratch using PowerShell Out-GridView, try this:
Get-Process | Out-GridView
Data should also be cached because it's painful slow.
bin.n2f
21st March 2020, 16:27
hi
how i can solve this problem
System.ArgumentOutOfRangeException: Value to add was out of range
:thanks:
almanteka
21st March 2020, 17:47
This will break things! Maybe I redo it from scratch using PowerShell Out-GridView, try this:
Get-Process | Out-GridView
Data should also be cached because it's painful slow.
more info on how to proceed using powershell is appreciate it! thanks!
stax76
21st March 2020, 17:49
how i can solve this problem
System.ArgumentOutOfRangeException: Value to add was out of range
Generally if there is a bug in any app you visit the website and look for the support instructions:
https://github.com/staxrip/staxrip#support
In case of staxrip these instructions need some work, there should be log file, please post it to pastebin.com
edit:
I've changed the issue template on the tracker but still needs some work.
https://github.com/staxrip/staxrip/issues/new/choose
more info on how to proceed using powershell is appreciate it! thanks!
You have to wait until the app/script is finished, so far I have only 10 lines, it will be about 500 and I code very slow with PowerShell.
almanteka
21st March 2020, 21:31
You have to wait until the app/script is finished, so far I have only 10 lines, it will be about 500 and I code very slow with PowerShell.
ok, i was thinking that i need to do something for powershell to populate the mediainfo folder list. will wait to test it out! thanks!
stax76
22nd March 2020, 03:09
@almanteka
I've uploaded a fix for the MediaInfo folder view bug.
A small project of mine is Get-MediaInfo (https://github.com/stax76/Get-MediaInfo) which allows requesting single MediaInfo properties via PowerShell. This could be expanded into a full PowerShell MediaInfo solution in the future and be integrated or merged with MediaInfo.NET (https://github.com/stax76/MediaInfo.NET). We'll see but it's nothing that will happen soon because I've still much to learn about PowerShell.
StaxRip 2.1.0.1 Beta (all tools included):
https://github.com/staxrip/staxrip/blob/master/Changelog.md
https://staxrip.readthedocs.io/intro.html#download
almanteka
22nd March 2020, 08:20
@almanteka
I've uploaded a fix for the MediaInfo folder view bug.
A small project of mine is Get-MediaInfo (https://github.com/stax76/Get-MediaInfo) which allows requesting single MediaInfo properties via PowerShell. This could be expanded into a full PowerShell MediaInfo solution in the future and be integrated or merged with MediaInfo.NET (https://github.com/stax76/MediaInfo.NET). We'll see but it's nothing that will happen soon because I've still much to learn about PowerShell.
StaxRip 2.1.0.1 Beta (all tools included):
https://github.com/staxrip/staxrip/blob/master/Changelog.md
https://staxrip.readthedocs.io/intro.html#download
i can confirm that the mediainfo folder view is workin at v2.1.0.1 Beta! thanks!
Mzvasturbo
23rd March 2020, 14:34
StaxRip 2.0.8.0 x265 [warning]: --dhdr10-info disabled. Enable HDR10_PLUS in cmake.
StaxRip 2.0.6.0 works ok with HDR10+.
Patman
23rd March 2020, 16:52
StaxRip 2.0.8.0 x265 [warning]: --dhdr10-info disabled. Enable HDR10_PLUS in cmake.
StaxRip 2.0.6.0 works ok with HDR10+.Hi,
pls download one of the newer versions from my sig "staxrip tools"
almanteka
24th March 2020, 01:01
just a suggestion for future versions of StaxRip: add the total count of jobs in the jobs window, something like the pict below! not the same, but a way to know how many jobs are still pending! thanks!
https://i.imgur.com/SrQQxXJ.jpg
Taurus
24th March 2020, 12:02
@stax76:
There is a new version of dfftest (v1.9.5) from pinterf.
https://forum.doom9.org/showpost.php?p=1904821&postcount=5265
Works reliable on my side.
There is a msvc and a clang version, both in 32bit and 64bit.
And even a msvc_xp version foor the old hardcore users :p
I have only tested the 64bit msvc version.
Hope this helps.
Edit: the clang version seems to be a little bit faster (dont count on me, no numbers...)
Groucho2004
24th March 2020, 12:16
And even a msvc_xp version foor the old hardcore usersDoes one have to be old to use it? For adults only I presume? :p
Taurus
24th March 2020, 15:50
Does one have to be old to use it? For adults only I presume? :p
Nice one :D
Taurus
24th March 2020, 17:15
...and another update.
Pinterf is really busy this time.
There is a dfttest ver_1.9.6.
https://forum.doom9.org/showpost.php?p=1904858&postcount=5268
Works reliable inside StaxRip, tested the clang version this time.
Solo, in qtgmc, smdegrain, etc.
Bye
chipxtreme
25th March 2020, 17:23
NVEnc has been updated to 4.69
JKyle
27th March 2020, 08:19
VapourSynth is also updated to R49.
Mzvasturbo
27th March 2020, 11:45
Hi,
pls download one of the newer versions from my sig "staxrip tools"
Tried the latest beta and tried your staxrip fix HDR10+ not working.
Patman
27th March 2020, 20:31
Tried the latest beta and tried your staxrip fix HDR10+ not working.Do not update staxrip, but the x265.exe! look here (https://www.mediafire.com/folder/vkt2ckzjvt0qf/StaxRip_Tools)
Mzvasturbo
27th March 2020, 21:27
Do not update staxrip, but the x265.exe! look here (https://www.mediafire.com/folder/vkt2ckzjvt0qf/StaxRip_Tools)
Yea thanks i did that i have the latest x265. It works perfect.
Just for knowing other people HDR10+ dont work in never versions.
Patman
27th March 2020, 22:07
Yea thanks i did that i have the latest x265. It works perfect.
Just for knowing other people HDR10+ dont work in never versions.I think the next build will include a newer version of x265 and hdr10+ will work as it should be.
AMED
27th March 2020, 22:09
Hi Stax76
I'm currently using a single instance of StaxRip on 2 computers via mapped share to process a single job queue . After upgrading to from v2.0.6.0 version to v2.0.8.0 (also tested 2.0.9.12) the file path for the setting changes from the mapped drive to the full UNC path which borks a lot of the plugins from working.
Computer1 has a physical Z drive. Computer2 has Computer1's Z drive mapped as Z drive so the path references will be the same.
E.g. v2.0.6.0 in the registry after clicking browse for custom directory and selecting "Z:\Bluray\StaxRip\Settings"
Computer1 Setting location
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"Z:\\Bluray\\Staxrip\\"="Z:\\Bluray\\StaxRip\\Settings\\"
Computer2 Setting location
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"Z:\\Bluray\\Staxrip\\"="Z:\\Bluray\\StaxRip\\Settings\\"
E.g. v2.0.8.0 (and v2.0.9.12) in the registry after clicking browse for custom directory and selecting "Z:\Bluray\StaxRip\Settings"
Computer1 Setting location
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"Z:\\Bluray\\Staxrip\\"="Z:\\Bluray\\StaxRip\\Settings\\"
Computer2 Setting location in registry
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"\\\\192.168.11.1\\z$\\Bluray\\StaxRip\\"="Z:\\Bluray\\StaxRip\\Settings\\"
If i try and delete that key and manually create it like on Computer1 i just get prompted for the settings directory again when i open StaxRip.
Hi stax76,
I've done some more investigations to this bug. there seems to be some change maybe in the environment after StaxRip-x64-2.0.7.1-beta that makes it change to a UNC path.
StaxRip-x64-2.0.6.1-beta = Local path
StaxRip-x64-2.0.7.1-beta = Local path
StaxRip-x64-2.0.8.0-stable = UNC path
StaxRip-x64-2.0.9.1-beta = UNC path
StaxRip-x64-2.1.0.1-beta = UNC path
here is another example using StaxRip-x64-2.1.0.1-beta.
Open staxrip on computer 1 and set the settings path to Z:\Bluray\Staxrip-x64-2.1.0.1-Beta\Settings.
https://i.ibb.co/LpftXhw/Computer-1.png (https://imgbb.com/)
Open staxrip on computer 2 and the program prompts for the full UNC path and not the local path. Using a custom directory doesn't resolve this.
https://i.ibb.co/D9kCpsK/Computer-2.png (https://imgbb.com/)
This is how the registry looks on computer 2 opening each still available beta and stable after v2.0.6.0.
[HKEY_CURRENT_USER\Software\StaxRip\SettingsLocation]
"Z:\\Bluray\\StaxRip-x64-2.0.6.1-beta\\"="Z:\\Bluray\\StaxRip-x64-2.0.6.1-beta\\Settings\\"
"Z:\\Bluray\\StaxRip-x64-2.0.7.1-beta\\"="Z:\\Bluray\\StaxRip-x64-2.0.7.1-beta\\Settings\\"
"\\\\10.11.4.98\\z$\\Bluray\\StaxRip-x64-2.0.9.1-beta\\"="\\10.11.4.98\\z$\\Bluray\\StaxRip-x64-2.0.9.1-beta\\Settings\\"
"\\\\10.11.4.98\\z$\\Bluray\\StaxRip-x64-2.0.8.0-stable\\"="Z:\\Bluray\\StaxRip-x64-2.0.8.0-stable\\"
"\\\\10.11.4.98\\z$\\Bluray\\StaxRip-x64-2.1.0.1-beta\\"="\\\\10.11.4.98\\z$\\Bluray\\StaxRip-x64-2.1.0.1-beta\\Settings\\"
Does Folder.Startup need to be changed to Folder.Startup.FixDir?
jlw_4049
28th March 2020, 01:08
Yea thanks i did that i have the latest x265. It works perfect.
Just for knowing other people HDR10+ dont work in never versions.
I think the next build will include a newer version of x265 and hdr10+ will work as it should be.
How do you know that HDR10+ isn't working? It has worked good for me that I know of.
Upon looking at my logs I don't see a warning about it not working.
Atlantis
28th March 2020, 01:41
Yea thanks i did that i have the latest x265. It works perfect.
Just for knowing other people HDR10+ dont work in never versions.
What not work means? Please explain. You mean you can encode in HDR10+ with staxrip? I did not know that you could.
jlw_4049
28th March 2020, 02:00
What not work means? Please explain. You mean you can encode in HDR10+ with staxrip? I did not know that you could.
Mzvasturbo says hdr encoding wasn't working for him.
I was responding to him saying that it's working fine on mine like it always has.
AMED
28th March 2020, 02:14
i made a small change to the this sub routine
Shared ReadOnly Property Startup() As String
Get
If StartupValue Is Nothing Then
Dim buffer As New StringBuilder(500)
QueryFullProcessImageName(Process.GetCurrentProcess.Handle, 0, buffer, buffer.Capacity)
StartupValue = buffer.ToString.Dir
End If
Return StartupValue
End Get
End Property
To this and it fixes the problem
Shared ReadOnly Property Startup() As String
Get
If StartupValue Is Nothing Then
StartupValue = Application.StartupPath.FixDir
End If
Return StartupValue
End Get
End Property
https://i.ibb.co/HdMqph7/Computer-2-fix.png (https://imgbb.com/)
this is the first time i've ever done something in .net so i'm sure there is a more robust way to fix it.
Atlantis
28th March 2020, 02:16
Yes HDR10 encoding works. I'm also doing it.
But HDR10+ is different. Mzvasturbo was talking about that. I did not know you could do HDR10+ encoding with staxrip.
Atlantis
28th March 2020, 02:22
What is the difference between x265M and x265? I don't know which one to download. Which one is provided with staxrip?
jlw_4049
28th March 2020, 03:19
Yes HDR10 encoding works. I'm also doing it.
But HDR10+ is different. Mzvasturbo was talking about that. I did not know you could do HDR10+ encoding with staxrip.
Oh, I didn't know there was an HDR10+ actually. Guess you learn something new every day.
Atlantis
28th March 2020, 03:43
Yes HDR10+ is like Dolby Vision. from wiki
HDR10+ is a High Dynamic Range (HDR) video technology that adds dynamic metadata to HDR10 source files. HDR10+ signals the dynamic range and scene characteristics on a scene-by-scene or even frame-by-frame basis. The display device then uses the dynamic metadata to apply an appropriate tone map through the process of dynamic tone mapping. Dynamic tone mapping differs from static tone mapping by applying a different tone curve from scene-to-scene rather than use a single tone curve for an entire video.
I know that HDR10+ is so new and special that you don't even do a crop on a 2.35:1 movie. You keep it at 3840 x 2160 with black bars. Because if you crop it, you have to change the dynamic range scene by scene.
So it is a surprise to me. I would like to know what does not work in regards to HDR10+ in staxrip 2.0.8.0. I didn't even know you could do HDR10+ encoding.
jlw_4049
28th March 2020, 04:19
Yes HDR10+ is like Dolby Vision. from wiki
HDR10+ is a High Dynamic Range (HDR) video technology that adds dynamic metadata to HDR10 source files. HDR10+ signals the dynamic range and scene characteristics on a scene-by-scene or even frame-by-frame basis. The display device then uses the dynamic metadata to apply an appropriate tone map through the process of dynamic tone mapping. Dynamic tone mapping differs from static tone mapping by applying a different tone curve from scene-to-scene rather than use a single tone curve for an entire video.
I know that HDR10+ is so new and special that you don't even do a crop on a 2.35:1 movie. You keep it at 3840 x 2160 with black bars. Because if you crop it, you have to change the dynamic range scene by scene.
So it is a surprise to me. I would like to know what does not work in regards to HDR10+ in staxrip 2.0.8.0. I didn't even know you could do HDR10+ encoding.
Does BluRay movies even release with this?
Atlantis
28th March 2020, 04:37
Yes. There are many.
stax76
28th March 2020, 04:45
@AMED
Thanks for finding the reason and a solution, for me it would have been very difficult to find because there is a network involved and I'm not very competent in this area. There was another UNC related bug recently and I found out I can get such a path by using \\localhost\c$\Users\frank\Desktop, your issue appeared more complex and probably I wouldn't have found the reason.
git is like a time based file system, it's possible to browse later versions of a file, the original code here:
https://github.com/staxrip/staxrip/blob/0c263ffff8e26d2166d4eef50d692f95c84682bd/General/General.vb#L32
So it's almost the same as your fix.
I do remember this change and I also remember the reason: on my PC staxrip is located at D:\Projekte\VB\StaxRip, for unknown (and maybe mystical) reason System.Windows.Forms.Application.StartupPath was returning wrong casing, staxrip instead StaxRip, it wasn't causing a bug, I noticed it in the Apps dialog, I don't remember all details but much likely I had tried to investigate it by looking if powershell dir shows something different from Explorer and by looking which Win32 function is used by .NET, I think the outcome was that Win32 already returned the wrong casing and finding the reason seemed very difficult, guys like Raymond Chen know such things (helped me before with a difficult 'Open with++' issue) but the shitty StackOverflow site where I could ask has blocked me, so I just decided to try another Win32 function, didn't expect that this will cause an issue in a network. The problem was only cosmetic but still did bother me enough trying to work around it and potentially such things can trigger bugs. I did revert it now and it probably will remain a mystery for me. :)
Mzvasturbo
28th March 2020, 08:28
Yes. There are many.
There arent so many. There is like 23 movies with HDR10+.
you simply extract daynamic metadata with HDR10+parser to json file with ffmpeg. Then you put it in staxrip.
But never verions of staxrip show this message.
[warning]: --dhdr10-info disabled. Enable HDR10_PLUS in cmake.
Patman
28th March 2020, 09:46
What is the difference between x265M and x265? I don't know which one to download. Which one is provided with staxrip?Have a look here (http://forum.doom9.org/showthread.php?p=1902048). Both versions are provided by staxrip. My new versions have hdr10+ activated.
Atlantis
28th March 2020, 22:12
Mzvasturbo, could you please give a step by step detail how to encode a HDR10+ file?
Atlantis
29th March 2020, 04:21
Ok here is my unscientific speed tests. Same 4K HDR file. The first one is the x265 provided by staxrip 2.0.8.0
x265 3.3+2-gbe2d82093 GCC 9.2.0
2.40 fps
x265 3.3+10-g08d895bb6-gcc9.3.0
2.45 fps
x265 3.3+10-g08d895bb6-msvc-vs2019
2.34 fps
x265 M-3.3+10-g08d895bb6-gcc9.3.0
2.51 fps
x265 M-3.3+10-g08d895bb6-msvc-vs2019
2.30 fps
So gcc seems faster than msvc.
pintcat
29th March 2020, 09:37
Tried the latest StaxRip 2.0.8.0 and it doesn't recognize Visual C++ 2019. Runtimes are installed (both 32 & 64bit) and msvcp140.dll is in place. Still complaining. System is Windows 7 64bit.
Mzvasturbo
29th March 2020, 12:24
Mzvasturbo, could you please give a step by step detail how to encode a HDR10+ file?
If you actualy have a mkv remux of video with HDR10+ metadata you must parse it with
HDR10+ parser https://github.com/quietvoid/hdr10plus_parser/releases
You can do it with ffmpeg https://video.stackexchange.com/questions/20495/how-do-i-set-up-and-use-ffmpeg-in-windows
Command in cmd looks like this
ffmpeg -i "C:\video rip\Test.mkv" -c:v copy -vbsf hevc_mp4toannexb -f hevc - | "C:\hdr10plus_parser\hdr10plus_parser.exe" - -o "C:\video rip\Test.json"
ffmpeg -i "This is your video file path and name" -c:v copy -vbsf hevc_mp4toannexb -f hevc - | "this is your parser .exe location and name" - -o "This is your output file location and name"
Now next step is very simple.
http://shrani.si/f/J/7W/43pblryA/hdr10.jpg
I hope this helps.:) If you did all things correct you could see with https://mediaarea.net/en/MediaInfo something like this HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
stax76
29th March 2020, 12:27
@pintcat
You can try clicking the Version button and if that don't help you can try editing the versions.txt file in the apps folder, either edit the date of visual c or remove that line completely. You can try the same things with the latest beta, the current VC version I have is 14.25.28508.3 from 2020-01-08, it was necessary to block old VC versions because avisynth failed to load using an old version.
stax76
29th March 2020, 14:08
I've uploaded a new beta that addressed recent feedback and tool updates but has also a new feature.
### 2.1.0.2 Beta
- new: the MediaInfo folder view was replaced with a new powershell based
dialog that supports caching for fast startup performance
- fix: install instructions for wrong versions in the Apps dialog were improved
- fix: UNC path issue fix (AMED)
- fix: x265 --hdr-opt renamed to --hdr10-opt
- update: x265 3.3+10-g08d895bb6-gcc9.3.0 Patman
- update: Python 3.8.2
- update: VapourSynth R49
- update: VC++ 2019 14.25.28508.3
https://staxrip.readthedocs.io/intro.html#download
Taurus
29th March 2020, 14:21
@Mzvasturbo
The picture in your post above is not showing....
Atlantis
29th March 2020, 17:14
Question about HDR10+. Is the metadata only that json file you mentioned? I thought it's a second video stream. There are video with a second video stream. What is that?
JKyle
29th March 2020, 17:48
Question about HDR10+. Is the metadata only that json file you mentioned? I thought it's a second video stream. There are video with a second video stream. What is that?
HDR10+ is one of the HDR standards proposed by Samsung and Amazon and maintained by the HDR10+ Alliance. Although it's not as common as HDR10 (another de-facto standard of HDR), it's royalty-free. On the other hand, another HDR standard Dolby Vision charges businesses.
AFAIK, @Mzvasturbo has shown how to extract the SMPTE ST 2094-40 dynamic metadata embedded in an HDR10+ video file.
You can refer to this Wikipedia document (https://en.wikipedia.org/wiki/High-dynamic-range_video) about the detail on HDR and HDR standards. :)
Mzvasturbo
29th March 2020, 17:57
If you actualy have a mkv remux of video with HDR10+ metadata you must parse it with
HDR10+ parser https://github.com/quietvoid/hdr10plus_parser/releases
You can do it with ffmpeg https://video.stackexchange.com/questions/20495/how-do-i-set-up-and-use-ffmpeg-in-windows
Command in cmd looks like this
ffmpeg -i "C:\video rip\Test.mkv" -c:v copy -vbsf hevc_mp4toannexb -f hevc - | "C:\hdr10plus_parser\hdr10plus_parser.exe" - -o "C:\video rip\Test.json"
ffmpeg -i "This is your video file path and name" -c:v copy -vbsf hevc_mp4toannexb -f hevc - | "this is your parser .exe location and name" - -o "This is your output file location and name"
Now next step is very simple.
http://shrani.si/f/J/7W/43pblryA/hdr10.jpg
I hope this helps.:) If you did all things correct you could see with https://mediaarea.net/en/MediaInfo something like this HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
I can see it just fine in any browser ok here is the link
http://shrani.najdi.si/?J/7W/43pblryA/hdr10.jpg
Taurus
29th March 2020, 18:24
I can see it just fine in any browser ok here is the link
http://shrani.najdi.si/?J/7W/43pblryA/hdr10.jpg
Thank you, maybe my security settings blocked the webhoster.
:thanks:
JKyle
29th March 2020, 21:17
■ System Environment
StaxRip : 2.1.0.2
Windows : Windows 10 Home 2004
CPU : Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz
■ Source video
LG: New York HDR (https://4kmedia.org/lg-new-york-hdr-uhd-4k-demo/)
■ Remuxing of the original ts to mkv
ffmpeg -hide_banner -analyzeduration 100M -probesize 50M -i "LG New York HDR UHD 4K Demo.ts" -map 0 -c copy -bsf:a aac_adtstoasc -y "LG New York HDR UHD 4K Demo.mkv"
■ Resize
Spline64Resize (avs): 4K to FHD
■ Video encoding command line (avs2pipe, x265)
D:\Utilities\StaxRip\Apps\Support\avs2pipemod\avs2pipemod64.exe -y4mp "D:\Work\tmp\LG New York HDR UHD 4K Demo_temp\LG New York HDR UHD 4K Demo.avs" | D:\Utilities\StaxRip\Apps\Encoders\x265\x265.exe --crf 27 --output-depth 10 --aq-mode 3 --qg-size 8 --aq-strength 2 --me star --bframes 3 --rc-lookahead 30 --ref 5 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(12000000,500)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --repeat-headers --hrd --aud --psy-rd 3 --frames 1806 --y4m --output "D:\Work\tmp\LG New York HDR UHD 4K Demo_temp\LG New York HDR UHD 4K Demo_out.hevc" -
■ Result (from slowest to fastest)
x265M-3.3+10-g08d895bb6-gcc9.3.0
7.61 fps (237.29s)
x265M-3.3+10-g08d895bb6-msvc-vs2019
7.77 fps (232.41s)
x265M-3.3+10-g08d895bb6-gcc10.0.1
7.97 fps (226.74s)
x265-3.3+10-g08d895bb6-gcc10.0.1
8.02 fps (225.10s)
Patman
29th March 2020, 22:18
■ Result (from slowest to fastest)
x265M-3.3+10-g08d895bb6-gcc9.3.0
7.61 fps (237.29s)
x265M-3.3+10-g08d895bb6-msvc-vs2019
7.77 fps (232.41s)
x265M-3.3+10-g08d895bb6-gcc10.0.1
7.97 fps (226.74s)
x265-3.3+10-g08d895bb6-gcc10.0.1
8.02 fps (225.10s)
THX for testing my builds. I'm very happy with the GCC 10.0.1 builds. Compiling with GCC 10 is a lot faster than compiling with GCC 9. I'll try to compile all my builds with GCC 10 in the future.
JKyle
29th March 2020, 22:28
I'll try to compile all my builds with GCC 10 in the future.
That's pretty good news. :)
:thanks:
creeve4
29th March 2020, 22:38
Hey all! I'm currently using StaxRip 2.0.2.4 Beta and encoding a 4K movie using NVEnc. But for some reason, it will output two files after the encoding is finished. One has the original name that i set, and the other has _HDR10 at the end. Is there an option I'm missing to keep it from doing this? Thanks!
I am also looking for an answer about this. What are the differences between the file with _HDR and the one without?
Atlantis
29th March 2020, 23:11
I also confirm that GCC 10 is a little faster. I'm using x265 3.3+10-g08d895bb6 GCC 10.0.1 Patman. And no M branch. I think the original looks better and cleaner. fps, Bitrate and ETA is enough.
pintcat
30th March 2020, 03:04
You can try clicking the Version button and if that don't help you can try editing the versions.txt file in the apps folder, either edit the date of visual c or remove that line completely. You can try the same things with the latest beta, the current VC version I have is 14.25.28508.3 from 2020-01-08, it was necessary to block old VC versions because avisynth failed to load using an old version.
Thank you, works fine now. Wouldn't it be wise to accept every component version which is above the one mentioned in the versions.txt?
Mertiz88
30th March 2020, 16:17
Hi there,
Sorry if this is not the right thread to ask this question, also I've searched in the forums but didn't find the answer. I'm trying to use Staxrip 2.0.0.1 Beta just to apply a filter on an encoded video. What I did is taking that video and checked the filter box and made both video and audio settings on (copy/mux) but I found out that the filter didn't be applied. Basically, is that possible? If so, what's the right way to do that? thanks.
Joekiwi
30th March 2020, 22:34
Hi I'm a newbie - but I think filters will not work unless you to a video encode . Definitely applies to crop - as I wanted to remove black borders and no can do - so had to do a complete re-encode from source.
I may be wrong -
Anyway you can run filters/scripts / command lines on base programs for avisynth & vapoursynth - I'm not going that far - so Staxrip just for me-( learning curve for payback for my needs too much ) Staxrip is just a nice frontend for a bunch of tools made easy for people like me
AMED
30th March 2020, 22:36
@Mertiz88,
If you permanently want the filter on the video then you'll need to re encode it not copy/mux. are you able to just apply the filter on the software your using for playback?
Joekiwi
30th March 2020, 22:50
Just like to say a big thanks to Patman for all your effort
JKyle
31st March 2020, 06:21
I speed-tested different builds of x264 by Patman in a very similar way to this post (https://forum.doom9.org/showthread.php?p=1905473#post1905473).
The source video is the same UHD HDR video from 4kmedia.org and remuxing to mkv is the same.
The only different part is applying ConvertBits and DGHDRtoSDR in the AviSynth script and x264 encoding.
Here's the detail.
■ System Environment
StaxRip : 2.1.0.2
Windows : Windows 10 Home 2004
CPU : Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz
■ Source Video
LG: New York HDR (https://4kmedia.org/lg-new-york-hdr-uhd-4k-demo/)
■ Remuxing of the original ts to mkv
ffmpeg -hide_banner -analyzeduration 100M -probesize 50M -i "LG New York HDR UHD 4K Demo.ts" -map 0 -c copy -bsf:a aac_adtstoasc -y "LG New York HDR UHD 4K Demo.mkv"
■ AviSynth Script
LG New York HDR UHD 4K Demo.avs
LoadPlugin("D:\Utilities\StaxRip\Apps\Plugins\Dual\DGHDRtoSDR\DGHDRtoSDR.dll")
LoadPlugin("D:\Utilities\StaxRip\Apps\Plugins\Dual\ffms2\ffms2.dll")
FFVideoSource("D:\Work\tmp\LG New York HDR UHD 4K Demo.mkv", cachefile = "D:\Work\tmp\LG New York HDR UHD 4K Demo_temp\LG New York HDR UHD 4K Demo.ffindex")
#AssumeFPS(25)
Spline64Resize(1920, 1080)
ConvertBits(16)
DGHDRtoSDR(mode="pq",white=2500)
■ Video encoding command line (avs2pipe, x264)
D:\Utilities\StaxRip\Apps\Support\avs2pipemod\avs2pipemod64.exe -y4mp "D:\Work\tmp\LG New York HDR UHD 4K Demo_temp\LG New York HDR UHD 4K Demo.avs" | D:\Utilities\StaxRip\Apps\Encoders\x264\x264.exe --crf 23 --profile high --aq-mode 3 --me umh --direct auto --merange 24 --b-adapt 2 --colorprim bt709 --colormatrix bt709 --transfer bt709 --aud --deblock -1:-1 --demuxer y4m --frames 1806 --output "D:\Work\tmp\LG New York HDR UHD 4K Demo_temp\LG New York HDR UHD 4K Demo_out.h264" -
■ Result (from slowest to fastest)
x264-159-r2991-1771b55-gcc9.3.0
10.83 fps
x264-159-r2991M-1771b55-gcc9.3.0
12.36 fps
x264-159-r2991-1771b55-gcc10.0.1
12.39 fps
x264-159-r2991M-1771b55-gcc10.0.1
12.48 fps
Mertiz88
31st March 2020, 10:49
@Joekiwi, thanks for your reply, I think I'll ask this question in Avisynth thread.
@AMED, That's my question. I ask if I can apply any filter without doing enocde again.
stax76
31st March 2020, 11:26
are you able to just apply the filter on the software your using for playback?
mpv is the player with the best support for it, it allows:
ffmpeg filters:
https://mpv.io/manual/master/#video-filters
vapoursynth filters:
https://mpv.io/manual/master/#video-filters-vapoursynth
per file configuration:
https://mpv.io/manual/master/#file-specific-configuration-files
mpv.net supports almost all mpv features.
Patman
31st March 2020, 17:00
Just like to say a big thanks to Patman for all your effortYou're welcome. Currently Stax is here the machine and updates StaxRip quite regularly! A big thanks for that!
Lynx_TWO
31st March 2020, 18:06
@Stax and everyone else - So many thanks for this great tool!
Is it possible to implement a feature that would encode a video stream at two different resolutions while only processing once with plugins?
I'd love to the ability to denoise deinterlace, etc. on a 1080p file and then output a stream to 720p and 1080p mp4 file simultaneously with the same CRF settings, audio streams, subtitles, etc. Basically just resizing the processed raw 1080p output to 720p and encode it at the same time it's encoding the 1080p version. Would save a bunch of time and use a multicore system more efficiently I would think, esp. if using x264 :)
:thanks:
Z'Hadum
1st April 2020, 05:50
@Stax and everyone else - So many thanks for this great tool!
Is it possible to implement a feature that would encode a video stream at two different resolutions while only processing once with plugins?
Why do you not simply create two jobs for this? If you start staxrip two times, you get also your parallel processing....
shodan5000
1st April 2020, 16:56
Why is it that Vapoursynth scripts crash anytime time I have a video file with an apostrophe anywhere in the name? Avisynth scripts do not do this.
Patman
1st April 2020, 19:40
How can we set "chromaloc-top = 2" and "chromaloc-bottom = 2", "scenecut-bias = 0.05"
I set it, but look in the info section "chromaloc-top = 1" and "chromaloc-bottom = 1", "scenecut-bias = 0.00"
Help me! Thank you very much! (StaxRip Ver: 2.0.8.0)
I think there is no possibility to set these values. Scenecut-bias used 0.5 steps and chromaloc can general be set without the options bottom or top.
AMED
1st April 2020, 22:28
Why is it that Vapoursynth scripts crash anytime time I have a video file with an apostrophe anywhere in the name? Avisynth scripts do not do this.
What version of StaxRip are you running. I'm pretty sure this was fixed after 2.0.6.0 stable.
for now all you need to do is
open StaxRip, right click in the VS filters section and select profiles.
and change this[Source]
Automatic = # can be configured at: Tools > Settings > Source Filters
AVISource = clip = core.avisource.AVISource(r'%source_file%')
d2vsource = clip = core.d2v.Source(r'%source_file%')
DGSource = clip = core.dgdecodenv.DGSource(r'%source_file%')
ffms2 =
clip = core.ffms2.Source(r'%source_file%', cachefile=r'%source_temp_file%.ffindex')
#clip = core.std.AssumeFPS(clip, None, 25, 1)
LibavSMASHSource =
clip = core.lsmas.LibavSMASHSource(r'%source_file%')
#clip = core.std.AssumeFPS(clip, None, 25, 1)
LWLibavSource =
clip = core.lsmas.LWLibavSource(r'%source_file%', cachefile=r'%source_temp_file%.lwi')
#clip = core.std.AssumeFPS(clip, None, 25, 1)
Manual = # shows filter selection dialog
to this[Source]
Automatic = # can be configured at: Tools > Settings > Source Filters
AVISource = clip = core.avisource.AVISource(r"%source_file%")
d2vsource = clip = core.d2v.Source(r"%source_file%")
DGSource = clip = core.dgdecodenv.DGSource(r"%source_file%")
ffms2 =
clip = core.ffms2.Source(r"%source_file%", cachefile=r"%source_temp_file%.ffindex")
#clip = core.std.AssumeFPS(clip, None, 25, 1)
LibavSMASHSource =
clip = core.lsmas.LibavSMASHSource(r"%source_file%")
#clip = core.std.AssumeFPS(clip, None, 25, 1)
LWLibavSource =
clip = core.lsmas.LWLibavSource(r"%source_file%", cachefile=r"%source_temp_file%.lwi")
#clip = core.std.AssumeFPS(clip, None, 25, 1)
Manual = # shows filter selection dialog
shodan5000
2nd April 2020, 11:26
What version of StaxRip are you running. I'm pretty sure this was fixed after 2.0.6.0 stable.
I'm using version 2.1.0.1 but went ahead and tried your fix. It worked. Thank you very much. Maybe there was some old code that made its way back into that beta version?
JKyle
2nd April 2020, 12:24
Maybe there was some old code that made its way back into that beta version?
That's why you need to reset(restore) the profiles whenever you suspect there's old trash in them. :)
https://i.imgur.com/G7pHOP4m.jpg
https://i.imgur.com/mP1VeLhm.jpg
shodan5000
2nd April 2020, 17:15
That's why you need to reset(restore) the profiles whenever you suspect there's old trash in them. :)
I never knew that. Thanks for the tip.:thanks:
AMED
3rd April 2020, 00:09
I'm using version 2.1.0.1 but went ahead and tried your fix. It worked. Thank you very much. Maybe there was some old code that made its way back into that beta version?Did you use the same settings directory from a previous version of StaxRip when you started using v2.1.0.1?
Atlantis
3rd April 2020, 00:24
AviSynth+ 3.5.1 (https://github.com/AviSynth/AviSynthPlus/releases) released.
JKyle
3rd April 2020, 05:12
@Stax
Just FYI, there's a small typo in the x264 Options window (2.1.0.2 Beta).
https://i.imgur.com/hmOMXsCl.jpg
As you know, HDR(high dynamic range) is not HRD(hypothetical reference decoder), which is equal to VBV(video buffering verifier).
Plz fix this in order to prevent confusion. :)
:thanks:
Zetti
3rd April 2020, 19:12
MediaInfo v20.03 is released.
stax76
4th April 2020, 05:04
2.1.0.3 Beta
------------
- new: check added that blocks source files with too long path or filename. A setting
that allows to change the limit exists and there is also a explanation as tooltip:
In theory Windows supports paths that are longer than 260 characters, in reality
neither Windows, nor the .NET Framework or the used tools have full long path support.
- new: in order to support unicode the command line based encoder used by XviD uses
now cmd.exe directly without creating a batch file. This command line based encoder
is not only useful for XviD but can be used for any command line based encoder
- new: very basic SVT-AV1 encoder support added
- update: MediaInfo 20.03
- update: AviSynth 3.5.1
- update: ffmpeg N-97107-g33c106d411-g72be5d4661+2-gcc9.3.0 Patman
- fix: 2 reported typos
https://staxrip.readthedocs.io/intro.html#download
Patman
4th April 2020, 09:03
thank you very muck! So chromaloc customizations are the default and can't be manually set?
You can change chromaloc under x265 options -> VUI 2 if you want.
Zetti
4th April 2020, 16:38
MKVToolNix v45.0.0 is released.
stax76
4th April 2020, 16:43
MKVToolNix v45.0.0 is released.
Thanks, I've bookmarked your post.
impei
5th April 2020, 00:02
Hi, I'm using Staxrip 2.0.8.0 stable, and I can't crop more than 40% from any given side. Is there a way to fix this? I've looked through the settings and can't find anything. Thanks.
chipxtreme
5th April 2020, 00:51
MKVToolNix 45.0.0 is out.
Latest beta's haven't had NVEnc upgraded either.
JKyle
5th April 2020, 06:54
@Stax
I'd like to report two errors.
1) Opening/Remuxing TS to MKV failure
I opened an issue about this error (https://github.com/staxrip/staxrip/issues/149#issue-589908110) on GitHub, so please take a look.
2) qaac fails to encode some flac files
I ran into this weird error (pop-up message) while encoding a 6 channel flac audio stream in a video file into a stereo aac stream using qaac.
------------------- Audio encoding 1 using qaac 2.68 -------------------
D:\Utilities\StaxRip\Apps\Audio\qaac\qaac64.exe --tvbr 62 --delay -0.001 --normalize "D:\Work\tmp\test_temp\test ID1 -1ms Japanese.flac" -o "D:\Work\tmp\test_temp\test ID1 Japanese_a1.m4a"
qaac 2.68, CoreAudioToolbox 7.10.9.0
test ID1 Japanese_a1.m4a
ERROR: m_module.stream_decoder_seek_absolute(m_decoder.get(), count)
StaxRip.ErrorAbortException: Audio encoding 1 using qaac 2.68 returned error exit code: 2 (0x2)
It's unclear what the exit code means, in case it's a Windows system error then it possibly means:
The system cannot find the file specified
------------------- Audio encoding 1 using qaac 2.68 -------------------
D:\Utilities\StaxRip\Apps\Audio\qaac\qaac64.exe --tvbr 62 --delay -0.001 --normalize "D:\Work\tmp\test_temp\test ID1 -1ms Japanese.flac" -o "D:\Work\tmp\test_temp\test ID1 Japanese_a1.m4a"
qaac 2.68, CoreAudioToolbox 7.10.9.0
test ID1 Japanese_a1.m4a
ERROR: m_module.stream_decoder_seek_absolute(m_decoder.get(), count)
at StaxRip.Proc.Start() in D:\Projekte\VB\staxrip\General\Proc.vb:line 394
at StaxRip.GUIAudioProfile.Encode() in D:\Projekte\VB\staxrip\General\AudioProfile.vb:line 676
at StaxRip.GlobalClass._Closure$__._Lambda$__31-0() in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 101
at System.Threading.Tasks.Parallel.<>c__DisplayClass4_0.<Invoke>b__0()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at StaxRip.GlobalClass.ProcessJob(String jobPath) in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 133
The original video file is here (https://drive.google.com/open?id=17gPylEPxtPlHeQOFqDTm5htUKBXWbpoa) and the log file is here (https://pastebin.com/WiuJ6GPm).
I never had an error when I re-encoded aac streams with 2 channels using qaac even if I set the decoding method to FLAC.
Thanks in advance. :)
sneaker_ger
5th April 2020, 08:33
2) qaac fails to encode some flac files
It's probably because the file was split at some point without re-creating FLAC headers/re-encoding the FLAC part. This was discussed very recently in the MKVToolNix thread (https://forum.doom9.org/showthread.php?p=1905464#post1905464). If you use --delay option of qaac it tries seeking and will fail. (Piping from the mkv using ffmpeg should still work.)
https://gitlab.com/mbunkus/mkvtoolnix/-/wikis/Appending-&-splitting-FLAC-audio-tracks-not-supported
JKyle
5th April 2020, 09:06
Piping from the mkv using ffmpeg should still work.
Thanks for your advice.
You're right. Setting the decoding method to Pipe solved the problem by piping the flac file via ffmpeg.
https://i.imgur.com/8mB6LzYl.jpg
In this setting, qaac encodes the wav file piped via ffmpeg instead of directly dealing with the flac file.
D:\Utilities\StaxRip\Apps\Encoders\ffmpeg\ffmpeg.exe -i "D:\Work\tmp\test_temp\test ID1 -1ms Japanese.flac" -ac 2 -loglevel fatal -hide_banner -f wav - | D:\Utilities\StaxRip\Apps\Audio\qaac\qaac64.exe --tvbr 62 --delay -0.001 --normalize --gain 5.4 - -o "D:\Work\tmp\test_temp\test ID1 Japanese_a1.m4a"
:thanks:
taulen
5th April 2020, 09:08
Why do you not simply create two jobs for this? If you start staxrip two times, you get also your parallel processing....
Are you able to do this ?
Whenever I try to do two encoding instances of the same source file it always crashes both instances. This is when doing 2-pass x264 cpu encoding at least.
craigpro
5th April 2020, 10:22
Hi all,
I downloaded 2.1.0.2 beta as I was having issues with NeroEnc freezing in 2.0.8.0 stable and I noticed this error when encoding a video tonight:
C:\Staxrip\Apps\Encoders\NVEnc\NVEncC64.exe --cqp 18:20:22 --codec h265 --preset quality --level 5.1 --output-depth 10 --qp-init 20 --qp-max 22 --qp-min 18 --aq --aq-temporal --gop-len 240 --lookahead 16 --slices 2 --multiref-l0 4 --multiref-l1 4 --strict-gop --nonrefp --weightp -i D:\Temp\videosource_temp\videosource.avs -o D:\Temp\videosource_temp\videosource_out.h265
--------------------------------------------------------------------------------------------------------------------------------------------
D:\Temp\videosource_temp\videosource_out.h265
--------------------------------------------------------------------------------------------------------------------------------------------
nvenc : Error on nvEncGetEncodePresetConfig: 4 (NVENC this indicates that device passed to the API call is invalid)
multiref(L1) is lowered 4 -> 3 due to HEVC spec.
weighted prediction with B frames unsupported.
NVEncC (x64) 4.68 (r1402) by rigaya, Mar 7 2020 13:54:44 (VC 1916/Win/avx2)
OS Version Windows 10 x64 (18363)
CPU AMD Ryzen 7 3700X 8-Core Processor (8C/16T)
GPU #0: GeForce RTX 2060 (1920 cores, 1710 MHz)[PCIe3x16][445.75]
NVENC / CUDA NVENC API 9.1, CUDA 11.0, schedule mode: auto
Input Buffers CUDA, 32 frames
Input Info Avisynth+ 2.60(yv12)->nv12 [AVX2], 1280x720, 24000/1001 fps
Vpp Filters copyHtoD
cspconv(nv12 -> p010)
Output Info H.265/HEVC main10 @ Level 5.1
1280x720p 1:1 23.976fps (24000/1001fps)
Encoder Preset quality
Rate Control CQP I:18 P:20 B:22
Lookahead on, 16 frames, Adaptive I, B Insert
GOP length 240 frames
B frames 3 frames [ref mode: disabled]
Ref frames 3 frames, MultiRef L0:4 L1:3
AQ on
CU max / min auto / auto
Others mv:auto nonrefp
what does the error mean please?
Should I be using other NVenc settings?
Sorry for my noobidity. Thank you.
EDIT: nvidia driver 445.75
stax76
5th April 2020, 18:34
MKVToolNix v45.0.0 is released.
MKVToolNix 45.0.0 is out.
Latest beta's haven't had NVEnc upgraded either.
Thanks, updated.
Hi, I'm using Staxrip 2.0.8.0 stable, and I can't crop more than 40% from any given side. Is there a way to fix this? I've looked through the settings and can't find anything. Thanks.
I don't want to waste time and add useless code so it would need a request with explanation why it's not sufficient, in the Options dialog there is a crop section where values can be edited.
Opening/Remuxing TS to MKV failure
It's hardly possible to handle everything perfectly by default. In this case you can customize the command line at:
Main Menu > Tools > Settings > Pre Processing > ffmpeg: Re-mux TS to MKV > Edit
Command: powershell.exe
Arguments: -nologo -file "D:\ffmpegTsToMkv.ps1" "%source_file%" "%temp_file%.mkv"
Code:
$muxingMode = Get-MediaInfoValue ($args[0]) -Kind Audio -Parameter MuxingMode
if ($muxingMode -eq 'ADTS')
{
$bsf = '-bsf:a', 'aac_adtstoasc'
}
ffmpeg -hide_banner -analyzeduration 100M -probesize 50M -i $args[0] -map 0 -c copy @bsf -y $args[1]
You need to install Get-MediaInfo and add ffmpeg to the path env var or use the full path or use the build from today, it adds all exe tools to the path env var of the process and adds all macros as env vars.
Are you able to do this ?
Whenever I try to do two encoding instances of the same source file it always crashes both instances. This is when doing 2-pass x264 cpu encoding at least.
You can process it with one instance sequentially or maybe use the Event Command feature where you can run a command line or powershell script.
nvenc : Error on nvEncGetEncodePresetConfig
I can't help with it but you can use the nvenc tracker:
Main Menu > Help > Apps > nvenc > Online > Issues
2.1.0.5 Beta
------------
- new: the global setting 'Add filter to convert chroma subsampling to 4:2:0'
uses now ConvertToYUV420 instead of ConverttoYV12
- new: in custom command line based demuxers and in the ExecuteCommandLine
command the path environment variable of the process has all exe tools
added and all macros are available as environment variables
- new: AviSynth filter profile using ColorYUV function
- update: mkvtoolnix 45.0.0
- update: nvenc 4.69
- update: DFTTest 1.9.5 Clang
- update: L-Smash-Works 2020-03-22 HolyWu
- update: ffms2 89bd1e1 StvG
- fix: the MediaInfo Folder view did not work unless Get-MediaInfo was installed,
now it should work even without being installed, please try and give feedback
https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/u/s!ArwKS_ZUR01g0kH4d4eT_6a3GaKe?e=qbOfGS
Patman
5th April 2020, 19:40
Thanks, updated.
2.1.0.5 Beta
------------
- new: the global setting 'Add filter to convert chroma subsampling to 4:2:0'
uses now ConvertToYUV420 instead of ConverttoYV12
- new: in custom command line based demuxers and in the ExecuteCommandLine
command the path environment variable of the process has all exe tools
added and all macros are available as environment variables
- new: AviSynth filter profile using ColorYUV function
- update: mkvtoolnix 45.0.0
- update: nvenc 4.69
- update: DFTTest 1.9.5 Clang
- update: L-Smash-Works 2020-03-22 HolyWu
- update: ffms2 89bd1e1 StvG
- fix: the MediaInfo Folder view did not work unless Get-MediaInfo was installed,
now it should work even without being installed, please try and give feedback
What are the diffrences between 2.1.04 beta and 2.1.0.5 beta?
Some tools were updated... DFTTest 1.9.6 (https://github.com/pinterf/dfttest/releases/latest), L-Smash-Works 2020-03-28 HolyWu (https://www.mediafire.com/file/1nm7y22qe0si76p/LSMASHSource_20200328.7z/file) (L-Smash-Works 2020-03-22 HolyWu is buggy), Xvid_encraw 1.3.7 (My Builds).
Atlantis
5th April 2020, 23:29
In the log, what does Avg QP mean? If it's higher does it mean the picture quality of the encoded file is better?
JKyle
5th April 2020, 23:47
In the log, what does Avg QP mean? If it's higher does it mean the picture quality of the encoded file is better?
Nope, it's the opposite.
QP = quantization parameter.
JKyle
5th April 2020, 23:48
Some tools were updated... DFTTest 1.9.6 (https://github.com/pinterf/dfttest/releases/latest), L-Smash-Works 2020-03-28 HolyWu (https://www.mediafire.com/file/1nm7y22qe0si76p/LSMASHSource_20200328.7z/file) (L-Smash-Works 2020-03-22 HolyWu is buggy), Xvid_encraw 1.3.7 (My Builds).
Thanks for the info.
And QSVEnc is updated to 4.00.
jlw_4049
6th April 2020, 02:14
Reporting a bug @Stax76
I'm on version 2.0.8.0
https://i.imgur.com/63N61Mi.png
The issue is circled in red.
No matter how many times I create an audio profile with the name that I want it to be. It defaults right back to taking on the track name of what it's encoding from. I have tried creating the profile many different ways and times.
Thanks!
EDIT: Found another bug.
I'm trying to setup some batch encode profiles.
When I setup the profile and set my bitrate here
https://i.imgur.com/4wYNilT.jpg
it will not carry over to the encode if I do multiple files with the same settings (batch)
If i force the command with a custom command it does however work here
https://i.imgur.com/3YRA0kv.png
taulen
6th April 2020, 02:43
You can process it with one instance sequentially or maybe use the Event Command feature where you can run a command line or powershell script.
This is what I do, but with a AMD 3950x it only uses about 50-60% of the CPU, so doing multiple instances REALLY shortens the time. So currently I copy the source file temporarily and run it 2 times that way. But its a bit of a pain tbh :P
What do you mean by the second part of your reply, Im no expert so that went a bit over my head. And thanks for keeping Staxrip alive ! <3
stax76
6th April 2020, 06:41
What are the diffrences between 2.1.04 beta and 2.1.0.5 beta?
There was a bug where Main Menu > Folders showed an error, the underlying function is probably used by other features as well.
Some tools were updated... DFTTest 1.9.6, L-Smash-Works 2020-03-28 HolyWu (L-Smash-Works 2020-03-22 HolyWu is buggy), Xvid_encraw 1.3.7 (My Builds).
I've updated it except xvid for which I've removed the binaries because it's very old, the xvid encoder has still a profile in the video encoder menu and people that try to use it will see the Apps dialog, the download button is linked to your folder so it's easy for people to download.
And QSVEnc is updated to 4.00.
Also updated
No matter how many times I create an audio profile with the name that I want it to be. It defaults right back to taking on the track name of what it's encoding from. I have tried creating the profile many different ways and times.
I've changed it now that it uses the title of the source only when the title in the profile is empty.
This is what I do, but with a AMD 3950x it only uses about 50-60% of the CPU, so doing multiple instances REALLY shortens the time. So currently I copy the source file temporarily and run it 2 times that way. But its a bit of a pain tbh :P
Maybe try chunk encoding with ripbot or mediacoder, staxrip does not have such a feature and I don't have interest at this time. Building an app capable of it might not be terribly difficult for an experienced programmer, maybe a day or two for a prototype, it should be possible to build it as a console app that can be used as drop in replacement with identical CLI as the encoder.
What do you mean by the second part of your reply, Im no expert so that went a bit over my head.
There are some advanced features for power users, unfortunately there is no documentation and I usually only help advanced users with it these days. I have a plan to write documentation, some projects have really awesome documentation, for instance mpv or x265.
https://mpv.io/manual/master
https://x265.readthedocs.io/en/latest/cli.html
taulen
6th April 2020, 11:30
Maybe try chunk encoding with ripbot or mediacoder, staxrip does not have such a feature and I don't have interest at this time. Building an app capable of it might not be terribly difficult for an experienced programmer, maybe a day or two for a prototype, it should be possible to build it as a console app that can be used as drop in replacement with identical CLI as the encoder.
There are some advanced features for power users, unfortunately there is no documentation and I usually only help advanced users with it these days. I have a plan to write documentation, some projects have really awesome documentation, for instance mpv or x265.
https://mpv.io/manual/master
https://x265.readthedocs.io/en/latest/cli.html
No worries, I manage fine using Staxrip, which I have used for a few years by now, and really like. I was just curious if it was a feature that was "hidden away" or something, and I fully understand that you wont take the time to do it. I think I remember seeing you taking a break or "leaving" behind Staxrip at an earlier point, so Im just glad you continue the updating in any way you can and find the time for, thanks ! =)
Atlantis
6th April 2020, 11:40
An interesting observation I have made with encoding x265 4K. Encoding with a lower CRF takes more time. CRF 21 is a little slower than CRF 22 and CRF 20 is significantly slower.
I would have thought that if you wanted a better quality and use less compression, it should be faster to encode but it is the opposite. So, it is interesting on how to decide which CRF to use. Not only it depends on the quality you want, you have to consider how slow the encoding will be. I'm thinking that for me 4K CRF 20 is a no go for me. Too slow.
Lynx_TWO
6th April 2020, 21:32
After some analysis, I've arrived at some great settings when converting full dynamic range audio to something that's usable on a laptop:
Original audio was the first episode of Picard. Original audio specs after converting to Stereo, DPLII below:
True Peak: 0.0dB
Integrated Loudness [LKFS]: -23.6
(this is very quiet)
Max momentary [LKFS]: -8.8
Max Short-term [LKFS]: -12.7
Loudness range [LU]: 22.1 (WAY too dynamic for comfortable listening on any laptop)
After processing with dynamic audio normalization:
True Peak: +2.1dB
(technically this is not the best, but someone would need to integrate the ability to oversample or something to find true peak into dynaudionorm)
Integrated Loudness [LKFS]: -14.3
(very close to Spotify standards)
Max momentary [LKFS]: -4.6
Max Short-term [LKFS]: -6.5
Loudness range [LU]: 12.5 (usable and comfortable dynamic range)
Settings used to reach this result:
Frame Length: 145
Gaus filter win size: 31
Target Peak: 1.00
(when set lower, you'll get stronger peaks and less evenness in volume)
Max gain factor: 60.0
(20, 30, and 40 work well but result in a greater LU range and Integrated Loudness of -15, -14.8, and -14.4 respectively)
Compress factor: 30.0
I suspect there's likely a formula that could be applied for all the settings to reach optimal Integrated Loudness LKFS/LUFS, LU, and Max Momentary and Short-term LKFS/LUFS based on the original if we did enough testing and collected data on different tracks to find correlations...
jlw_4049
7th April 2020, 00:19
An interesting observation I have made with encoding x265 4K. Encoding with a lower CRF takes more time. CRF 21 is a little slower than CRF 22 and CRF 20 is significantly slower.
I would have thought that if you wanted a better quality and use less compression, it should be faster to encode but it is the opposite. So, it is interesting on how to decide which CRF to use. Not only it depends on the quality you want, you have to consider how slow the encoding will be. I'm thinking that for me 4K CRF 20 is a no go for me. Too slow.
With my settings I can encode a movie in about 15 - 19 hours depending on movie length.
Atlantis
7th April 2020, 03:26
What's your settings?
I also get the same hours if I go with CRF 22 and depending on the video and filters I apply. With CRF21 and below it could easily take more than 24+ hours.
JKyle
7th April 2020, 04:08
In 2.1.0.5 beta, Tools > Folders > Templates menu tries to open a wrong folder, TemplatesV2.
https://i.imgur.com/PKzE6qel.jpg
https://i.imgur.com/1o0OSxw.jpg
Of course I can manually fix this by changing the default command line from
"%settings_dir%TemplatesV2"
to
"%settings_dir%Templates"
but I just wanted to point out that the default command line is problematic.
Magik Mark
7th April 2020, 15:25
Any advise on a good upscaler for fullHD to 4k?
Atlantis
7th April 2020, 15:58
Question, in StaxRip Remove Grain Repair is added something like this by default
FFVideoSource(".............
Processed = RemoveGrain()
Repair(Processed)
-------------------------------------------------
In the manual of RgTools it suggests using it in another way. Passing the untouched video like this
Unprocessed = FFVideoSource(".............
Processed = RemoveGrain(Unprocessed)
Repair(Processed, Unprocessed)
-------------------------------------------------
I have tested both scripts and I get 2 different results. The second method noted in the manual gives more details and seems better.
Anyone knows why? In the first method inserted by Staxrip, the unprocessed clip is not passed to Repair() function? Doesn't Repair() get the current clip by default if you don't mention it?
jlw_4049
7th April 2020, 18:42
What's your settings?
I also get the same hours if I go with CRF 22 and depending on the video and filters I apply. With CRF21 and below it could easily take more than 24+ hours.
Keep in mind this is without a video loaded into the program. So all the color flags etc aren't there.
--crf 16 --level-idc 5.1 --output-depth 10 --vbv-bufsize 50000 --vbv-maxrate 60000 --bframes 8 --ref 5 --max-luma 1023 --hdr-opt --no-rect
This is set to a medium preset and my crf I adjust according to the size I want of my file. I test until it hits a bit-rate I like then I stick with that crf. Depending on the film it's as low as 9 all the way up to 19.
My file sizes are usually in the 15 to 20gb size depending on film.
Patman
7th April 2020, 19:17
A request:
I have compiled the new x265.exe 3.3 + 18 (x265_git branch) and always get an error message when using the bit depth 10 bit and 12 bit. If you have the time and desire, please download and test x265.exe 3.3 + 19 (x265_hg branch) (http://msystem.waw.pl/x265/), the error also occurs here. You can report briefly if possible.
Atlantis
7th April 2020, 21:02
Depending on the film it's as low as 9 all the way up to 19.
My file sizes are usually in the 15 to 20gb size depending on film.
Wow, that's huge and it would take me several days to encode just 1 video like that.
What is your processor and memory?
Mine:
CPU : Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
GPU : NVIDIA GeForce GTX 980 Ti
Interestingly staxrip log does not include the memory.
RAM 64GB
JKyle
7th April 2020, 21:34
A request:
I have compiled the new x265.exe 3.3 + 18 (x265_git branch) and always get an error message when using the bit depth 10 bit and 12 bit. If you have the time and desire, please download and test x265.exe 3.3 + 19 (x265_hg branch) (http://msystem.waw.pl/x265/), the error also occurs here. You can report briefly if possible.
This is pretty weird.
I downloaded x265-3.3+19-1d2f556_gcc100-AVX2.7z (http://msystem.waw.pl/x265/x265-3.3+19-1d2f556_gcc100-AVX2.7z), put the files in D:\Work\tmp\ and test-encoded a UHD HDR video (https://4kmedia.org/lg-new-york-hdr-uhd-4k-demo/) via avs2pipe with the following command line:
D:\Utilities\StaxRip\Apps\Support\avs2pipemod\avs2pipemod64.exe -y4mp "D:\Work\tmp\LG New York HDR UHD 4K Demo_temp\LG New York HDR UHD 4K Demo.avs" | D:\Work\tmp\x265-10b.exe --crf 27 --output-depth 10 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(12000000,500)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --frames 500 --y4m --output "D:\Work\tmp\LG New York HDR UHD 4K Demo_temp\LG New York HDR UHD 4K Demo_out.hevc" -
In PowerShell, it fails with this error message:
avs2pipemod[info]: writing 500 frames of 25/1 fps, 1280x720,
sar 0:0, YUV-420-planar-10bit progressive video.
avs2pipemod[info]: finished, wrote 500 frames [100%].
avs2pipemod[info]: total elapsed time is 93.899 sec.
Program 'x265-10b.exe' failed to run: Exception of type 'System.OutOfMemoryException' was thrown.At line:1 char:152
+ ... Demo.avs" | D:\Work\tmp\x265-10b.exe --crf 27 --output-depth 10 --mas ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ D:\Utilities\StaxRip\Apps\Support\avs2pipemod\avs2pipemod64.exe -y4mp ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (:) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
On the other hand, it does not produce any error but encodes the file successfully in the Command Prompt.
I ran the same encode using the x265 build by Patman, which does not produce any error run in StaxRip, but I get the same error in PowerShell as well.
What the heck is going on? :scared:
Well, this is something I wasn't aware of, but at least I can say that x265-3.3+19-1d2f556_gcc100-AVX2.7z is OK (at least the 10-bit version).
JKyle
7th April 2020, 23:18
And I tested the 12-bit version in a similar way, and got the same result.
So, it seems that x265-3.3+19-1d2f556_gcc100-AVX2.7z is OK.
Patman
8th April 2020, 07:39
And I tested the 12-bit version in a similar way, and got the same result.
So, it seems that x265-3.3+19-1d2f556_gcc100-AVX2.7z is OK.Hey JKyle, thanks for your tests. Pls do the same with x265.exe (multilib version), not with x265-8b.exe, x265-10b.exe or x265-12b.exe. The x265.exe includes all bith depth. Thanks
JKyle
8th April 2020, 16:59
Pls do the same with x265.exe (multilib version), not with x265-8b.exe, x265-10b.exe or x265-12b.exe. The x265.exe includes all bith depth.
You were right. x265.exe returns errors with 10-bit and 12-bit encodes.
x265 [info]: HEVC encoder version 3.3+19-1d2f556ffb12
x265 [info]: build info [Windows][GCC 10.0.1][64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [error]: internalBitDepth must match compiled bit depth
x265 [error]: x265_encoder_open() failed for Enc,
aborted at input frame 1, output frame 0
By contrast, your build - x265-3.3+10-g08d895bb6-gcc10.0.1 - chooses the appropriate bit depth in encoding.
x265 [info]: HEVC encoder version 3.3+10-g08d895bb6
x265 [info]: build info [Windows][GCC 10.0.1][64 bit] 12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [info]: Main 12 profile, Level-3.1 (Main tier)
x265 [info]: Thread pool created using 4 threads
...
I guess the main difference lies in adaptively choosing the right bit depth at the time of encoding.
Yours can but the official x265 cannot.
stax76
8th April 2020, 18:39
An interesting observation I have made with encoding x265 4K. Encoding with a lower CRF takes more time. CRF 21 is a little slower than CRF 22 and CRF 20 is significantly slower.
I would have thought that if you wanted a better quality and use less compression, it should be faster to encode but it is the opposite. So, it is interesting on how to decide which CRF to use. Not only it depends on the quality you want, you have to consider how slow the encoding will be. I'm thinking that for me 4K CRF 20 is a no go for me. Too slow.
here is a benchmark:
https://forum.doom9.org/showthread.php?t=180438
In 2.1.0.5 beta, Tools > Folders > Templates menu tries to open a wrong folder, TemplatesV2.
Will be fixed in the next build.
In PowerShell, it fails with this error message:
On the other hand, it does not produce any error but encodes the file successfully in the Command Prompt.
Not every command line that works in cmd works also in ps, at least not without modification, piping to x265 does not work unless you do:
cmd /s /c --% "regular command line between this quotes"
https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_special_characters?view=powershell-5.1
That is similar to what staxrip does, calling cmd /s /c "" with the dotnet Process class with shellex disabled, it uses CreateProcess in Win32.
I think it was quot27 who gave me this clue.
In the next build there are some terminal related improvements:
https://github.com/staxrip/staxrip/blob/master/Changelog.md
Patman
8th April 2020, 19:23
That is similar to what staxrip does, calling cmd /s /c "" with the dotnet Process class with shellex disabled, it uses CreateProcess in Win32.
I think it was quot27 who gave me this clue.
I gave you the tipp too for SVT-AV1 encoder :D
Patman
8th April 2020, 19:31
I guess the main difference lies in adaptively choosing the right bit depth at the time of encoding.
Yours can but the official x265 cannot.
THX for testing JKyle, that's the point. I want to update my x265 builds, but with this known error i won't to build new versions. I hope the x265 devs can help with this problem. Till version x265-3.3+15 everything works fine, but after that version the error ocurrs. The offical build worked also fine till version 3.3+10. I hope other users can confirm this error.
JKyle
8th April 2020, 20:27
Not every command line that works in cmd works also in ps, at least not without modification, piping to x265 does not work unless you do:
cmd /s /c --% "regular command line between this quotes"
https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_special_characters?view=powershell-5.1
Now your tip wakes up my vague memory that PowerShell's piping is different from cmd's piping.
Thank you for the pointer. :)
JKyle
8th April 2020, 20:33
BTW, chapterEditor is updated to 1.22:
https://www.videohelp.com/software/chapterEditor
stax76
8th April 2020, 21:03
I gave you the tipp too for SVT-AV1 encoder :D
Recently yes, and also thanks for the command line example.
BTW, chapterEditor is updated to 1.22:
Thanks, bookmarked.
jlw_4049
9th April 2020, 06:44
Wow, that's huge and it would take me several days to encode just 1 video like that.
What is your processor and memory?
Mine:
CPU : Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
GPU : NVIDIA GeForce GTX 980 Ti
Interestingly staxrip log does not include the memory.
RAM 64GB
My encoding rig is a Ryzen 1700 stock speeds. It does pretty good!
For encoding 4K you pretty much are going to be encoding for ever regardless.
onekmilesbehind
9th April 2020, 19:56
For encoding 4K you pretty much are going to be encoding for ever regardless.
Nailed it. I thought when I built my threadripper rig a couple years back, I'd be sitting pretty. But then I just started enabling higher settings. Even with great CPUs, x265 is intense. At least if you're happy with the end results, it all works out. Well maybe not as much for my electric bill.
Stax thanks for making such a great app. Been using it for a few years now and realized I never stopped by to say thanks. Been a treat to use in my encoding pipeline.
Atlantis
9th April 2020, 20:02
Yes, if you are encoding 4K, it's non stop, it's so slow.
So in the past with x264 1080p, I could encode the entire thing and if I wanted another setting, redo it all over again.
Now it's impossible with 4K x265. You have to do it right on the first try. That's why I do compressibility check before doing the whole thing.
jlw_4049
9th April 2020, 20:07
Yeah doing a 2 pass to hit a more controlled bitrate is impossible. It would be 30 to 35 hours on my encoding rig.
I've gotten it down to where I can hit the bitrate I want with crf but it's not easy.
Sent from my Pixel 3a using Tapatalk
stax76
9th April 2020, 20:41
@onekmilesbehind
Thank you, positive feedback from people is probably the main reason why I still like to improve staxrip, even though I rarely use staxrip myself (ok indirectly...).
Negative feedback (https://github.com/staxrip/staxrip/issues/101) also motivates me, for instance to improve the documentation, I don't have great problems with the technical part, the command line interface page (https://staxrip.readthedocs.io/cli.html) is much better since today, it's auto-generated from staxrip, non-technical things like writing real content will be a challenge, I'm terrible in that, we'll see. :)
Patman
9th April 2020, 21:07
The error with the x265.exe (Multilib) has been fixed. I updated my x265 versions ;) THX to the x265 developers ... Great support and good collaboration :thanks:
JKyle
9th April 2020, 21:25
The error with the x265.exe (Multilib) has been fixed. I updated my x265 versions ;)
Wow! That's pretty good news! :)
BTW, I'm kind'a looking forward to the GCC 10 compiled version of ffmpeg to see how much improvement it will show.
Will it be available?
:thanks:
Patman
9th April 2020, 21:37
Wow! That's pretty good news! :)
BTW, I'm kind'a looking forward to the GCC 10 compiled version of ffmpeg to see how much improvement it will show.
Will it be available?
:thanks:I'm doing my best, but there are still a few problems. Not all of the tools I need the libraries are compatible with gcc 10.
Atlantis
10th April 2020, 00:24
What is this place? The difference?
http://msystem.waw.pl/x265/
I also did some test with 3.3+19 on that link and I got errors. Couldn't encode.
Atlantis
10th April 2020, 00:31
Tried Patman's x265-3.3+18-g8b61ca0ca-gcc10.0.1 it freezes at the end. Does not end. Tried it in a Command Prompt.
JKyle
10th April 2020, 00:55
Tried Patman's x265-3.3+18-g8b61ca0ca-gcc10.0.1 it freezes at the end. Does not end. Tried it in a Command Prompt.
Well, in my testing, all of Patman's builds of x265(3.3+18-g8b61ca0ca) are working OK with different encoding speeds.
craigpro
10th April 2020, 08:04
I keep encountering issues with NeroAACenc stalling (it stalled in 2.0.8.0 stable, worked fine in 2.1.0.2 and is stalling again with 2.1.0.5), don't sometimes it continues and writes out the encoded file, sometimes it aborts completely.
I've never reported a log file before, I hope this is ok? Thank you.
https://pastebin.com/raw/eMy3g4uy
stax76
10th April 2020, 08:26
@craigpro
I'll take a look, meanwhile maybe try the two other aac encoders that are included.
Patman
10th April 2020, 09:39
Tried Patman's x265-3.3+18-g8b61ca0ca-gcc10.0.1 it freezes at the end. Does not end. Tried it in a Command Prompt.Hi Atlantis,
I can't reproduce it with any of my x265 builds. Is there a log or something else?
Atlantis
10th April 2020, 14:40
No worry, I will wait for one of the future versions. I'm in no hurry to change versions, still using x265-3.3+10-g08d895bb6-gcc10.0.1 for my encodes.
Atlantis
10th April 2020, 14:54
Something strange happening, if anyone can help me to understand or how to find the cause
this script
Unprocessed = FFVideoSource("..........
Processed = RemoveGrain(Unprocessed, mode=2)
Repair(Processed, Unprocessed, mode=2)
and this script
Unprocessed = FFVideoSource("...........
RemoveGrain(Unprocessed, mode=2)
give the same results, like the Repair() function in the first script not doing anything.
However this script
FFVideoSource(".....................
Processed = RemoveGrain(mode=2)
Repair(Processed, mode=2)
gives a different result, like Repair is doing something here. Any idea how can I pinpoint why this is happening?
Zetti
11th April 2020, 13:31
x264 r3000 is released.
Atlantis
11th April 2020, 19:15
HD Audio Tracks
DTS-HD tracks have 5.1 core inside. Don't know if it's already possible, it would be great if we could extract and encode those automatically inside staxrip. eac3to -core.
At the moment I have to use eac3to separately to extract the core tracks. It would be great to have an option in the demux dialog to demux the core only and not the entire track.
JKyle
11th April 2020, 23:18
@Patman
Thanks for the builds update.
But it seems that ffmpeg-N-97277-ged617c85c7-g7b0c22768e-gcc9.3.0.7z is buggy. No response from execution.
Can you look into this please?
:thanks:
Patman
11th April 2020, 23:56
@Patman
Thanks for the builds update.
But it seems that ffmpeg-N-97277-ged617c85c7-g7b0c22768e-gcc9.3.0.7z is buggy. No response from execution.
Can you look into this please?
:thanks:
Thank you for the information. I'm going back to the old version. Many tools have been updated these days, I'll take a look at them.
EDIT: New version is online
JKyle
12th April 2020, 04:40
EDIT: New version is online
Oh, ffmpeg-N-97302-gde2bd64474-g0ece80559a-gcc9.3.0.7z looks good.
:thanks:
mcjordan
12th April 2020, 12:52
Frank, I've a strange issue with DGDecNV (r206 from 2020-04-10; legal).
When trying to encode an sample file, StaxRip 2.1.0.6 after the demux phase shows a message:
"A new guard page for the stack cannot be created." (obviously when DGIndexNV trying to start indexing)
and it closes on its own. I'm on Windows 10 LTSC (1809) and Nvidia 445.78 driver.
I can't figure out where this result comes from.
Help me if possible. I will be very grateful.
Another test with LSMASHVideoSource (LSMASHSource_20200328 - latest from HolyWu) give me this result:
"LSMASHVideoSource [Fatal]: Failed to read an input file.
(C:\Temp\Passengers - Trailer_temp\Passengers - Trailer_new_source.avs, line 2)"
There is content of.avs file:
LoadPlugin("C:\Portables\StaxReborn\Apps\Plugins\Dual\L-SMASH-Works\LSMASHSource.dll")
LSMASHVideoSource("C:\Passengers - Trailer.mkv", format = "YUV420P8")
#ConvertFromDoubleWidth(bits=10)
#AssumeFPS(25)
P.S. Tested also with StaxRip 1.7.0.6 and DGDecNV r206 - they works like a charm.
stax76
12th April 2020, 17:49
'A new guard page for the stack cannot be created' is according to what I found with Google probably a dotnet specific error so it's likely that staxrip is responsible for the error, please search for a log file.
mcjordan
12th April 2020, 18:05
I compiled the source with target .NET 4.72 and things went right.
But it's weird, because it hadn't happened to previous versions before.
(i have installed .Net 4.8). But LSMASHVideoSource error is present there again.
stax76
12th April 2020, 18:36
Please follow this instruction:
https://staxrip.readthedocs.io/support.html
Edit:
The issue templates on the issue tracker were just much improved, and also the support page in the docs a little.
https://staxrip.readthedocs.io/support.html
https://github.com/staxrip/staxrip/issues/new/choose
mcjordan
12th April 2020, 20:30
Stax, thank you again for help and brilliant work! All works good now.
lordalibaski
13th April 2020, 02:03
Hi guys got a bit of a problem which is doing my head in I have tried a few things now and all I want to do is copymux the sound.
I'm using v2.1.0.6
These are the settings I am using
https://i.postimg.cc/5t4s8C0k/testing.png
This is the original captured files properties
Format : MPEG-PS
File size : 2.67 GiB
Duration : 39 min 30 s
Overall bit rate mode : Variable
Overall bit rate : 9 683 kb/s
Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : M=3, N=12
Format settings, picture struc : Frame
Duration : 39 min 30 s
Bit rate mode : Variable
Bit rate : 9 235 kb/s
Maximum bit rate : 9 450 kb/s
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 4:3
Frame rate : 25.000 FPS
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.891
Time code of first frame : 00:00:20:04
Time code source : Group of pictures header
GOP, Open/Closed : Closed
Stream size : 2.55 GiB (95%)
Audio
ID : 189 (0xBD)-128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Format settings, Endianness : Big
Muxing mode : DVD-Video
Duration : 39 min 30 s
Bit rate mode : Constant
Bit rate : 256 kb/s
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Delay relative to video : -224 ms
Stream size : 72.3 MiB (3%)
Service kind : Complete Main
I have tried converting it 3 times and every time I have tried I get no audio. I want it to be the same audio bitrate but every time I set it to copy/mux the end result is no aduio.
This is the converted file properties
Format : Matroska
Format version : Version 4 / Version 2
File size : 800 MiB
Duration : 39 min 30 s
Overall bit rate : 2 830 kb/s
Encoded date : UTC 2020-04-13 00:01:08
Writing application : mkvmerge v45.0.0 ('Heaven in Pennies') 64-bit
Writing library : libebml v1.3.10 + libmatroska v1.5.2
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main@L3@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 39 min 30 s
Bit rate : 2 828 kb/s
Width : 720 pixels
Height : 568 pixels
Display aspect ratio : 1.382
Original display aspect ratio : 1.383
Frame rate mode : Constant
Frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Bits/(Pixel*Frame) : 0.277
Stream size : 799 MiB (100%)
Writing library : x265 3.3+10-g08d895bb6:[Windows][GCC 9.3.0][64 bit] 8bit+10bit+12bit
Encoding settings : cpuid=1049071 / frame-threads=3 / numa-pools=12 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=720x568 /
interlace=0 / total-frames=59256 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-hrd / info /
hash=0 / no-temporal-layers / open-gop / min-keyint=25 / keyint=250 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=20 / lookahead-slices=0 /
scenecut=40 / hist-scenecut=0 / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=3 /
selective-sao=4 / no-early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=14.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=2 / overscan=0 / videoformat=5 / range=0 / colorprim=2 / transfer=2 / colormatrix=2 / chromaloc=0 / display-window=0 / cll=0,0 / min-luma=0 / max-luma=255 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / hist-threshold=0.01 / no-opt-cu-delta-qp / no-aq-motion / no-hdr10 / no-hdr10-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=0 / analysis-save-reuse-level=0 / analysis-load-reuse-level=0 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00 / no-scenecut-aware-qpconformance-window-offsets / right=0 / bottom=0 / decoder-max-rate=0
Default : Yes
Forced : No
Why does it keep muting the audio? I've never had this problem before. If I trim a small segment out of the original file and convert it the sound is there.
stax76
13th April 2020, 03:33
@mcjordan
You're welcome.
@lordalibaski
Apparently staxrip just ignores the audio track because the mkv muxer does not recognize the mpeg (and also not vob) file extension. It should work if you rename the file extension to mpg. I'll add mpeg and vob to the list of recognized file types and I'll check why it did not try to demux the audio track or at least generate an assistant message instead of ignoring it silently.
almanteka
13th April 2020, 03:46
is there is any option to see the jobs window from this:
https://i.imgur.com/7SniT8t.jpg
to this?
https://i.imgur.com/W1dKdwj.jpg
avoiding the paths and showing only the source file and/or the template name & source file? the "12 jobs remaining' was a suggestion a few posts above to know how many active jobs are online. thanks for the great job!!!
stax76
13th April 2020, 04:53
@almanteka
I've bookmarked it for later consideration but unlikely anytime soon.
almanteka
13th April 2020, 05:46
@almanteka
I've bookmarked it for later consideration but unlikely anytime soon.
thanks!
lifta19
13th April 2020, 11:19
Vapoursynth is much more stable than avisynth and fully supports 64-bit Why use avisynth? Encoding speed is always faster.
And the multithread is perfect.
The plug-in is fast indexed by LSMASHSource.dll
StaxRip Best Encoder
stax76
13th April 2020, 13:48
staxrip supports both equally. For me the question is why use DirectShow players. ;)
lordalibaski
13th April 2020, 15:24
@lordalibaski
Apparently staxrip just ignores the audio track because the mkv muxer does not recognize the mpeg (and also not vob) file extension. It should work if you rename the file extension to mpg. I'll add mpeg and vob to the list of recognized file types and I'll check why it did not try to demux the audio track or at least generate an assistant message instead of ignoring it silently.
Thank you stax76
It was just bugging me because it would actually work on a smaller file, If I cut a 2 mins or so segment out of the same file it would demux the audio but not on the full size file. I'm going to rename the files now mate and I will get back to you sometime later and tell you the result.
Many thanks
lordalibaski
Ps edit... @ stax76
Changing the extension worked mate thank you very much.
jlw_4049
13th April 2020, 20:34
is there is any option to see the jobs window from this:
https://i.imgur.com/7SniT8t.jpg
to this?
https://i.imgur.com/W1dKdwj.jpg
avoiding the paths and showing only the source file and/or the template name & source file? the "12 jobs remaining' was a suggestion a few posts above to know how many active jobs are online. thanks for the great job!!!
I would love for this to be implemented. Of course when ever stax wants to do this.
Vapoursynth is much more stable than avisynth and fully supports 64-bit Why use avisynth? Encoding speed is always faster.
And the multithread is perfect.
The plug-in is fast indexed by LSMASHSource.dll
StaxRip Best Encoder
I have never used vapoursynth. I wouldn't even know where to begin. I use minimal avisynth commands so it probably wouldn't be extremely difficult to learn.
L E G E N D
13th April 2020, 20:44
Hi, i would like to complain about a thing that drove me mad for the past week i might need some help as well.
the whole story is that i'm trying to encode an avisynth filtered video script with NVEnc h265 in StaxRip,
i choose NVEnc to accelerate the process, because the avisynth script contains a lot of filters.
normally encoding with x264/x265 costs a lot of time, then eventualy i assume using NVEnc might get the fps higher ^^
so since i'm in x64 env, i installed avisynth+ for both version 64 and 32, and added the plugins to right places,
everything works fine, i get the video preview in AVSPmod just OK.
the problem is when i start to encode the video, the fps is just the same as when i use only cpu to encode,
the gpu does nothing to speed-up the thing. i used MP_PIPELINE to create a process for each filter with max memory set to 1024 Mb,
and still i get: gpu 3% and VE 9% and fps 24 (max). I kept monitoring the process of MP_pipeline and noticed that cpu actes only without the gpu.
my question: is there anything to do to help accelerate the encoding of avisynth scripts with NVEnc h265/h264! or am i missing something??
i'll leave more details down below:
Windows 10 Pro(x64) (Build 18362)
StaxRip v2.0.8.0 Stable
NVEnc v4.68
AVSPmod V2.6.1.1 x64 and x32
MicrosoftVC++ Redistributable 2005->2019 x64 & x32
NVidia Driver v441.08
Encoder settings:
--vbrhq 2048 --codec h265 --preset quality --profile main10 --tier high --level 5.1 --output-depth 10 --aq --bframes 6 --ref 16 --gop-len 600
--lookahead 32 --strict-gop --nonrefp --cu-max 32 --cuda-schedule auto --colormatrix bt709 --colorprim bt709 --transfer bt709
--vpp-edgelevel strength=10,threshold=15,black=5,white=2 --mv-precision full-pel --cabac
Max B frames are 0 frames.
NVEncC (x64) 4.68 (r1402) by rigaya, Mar 7 2020 13:54:44 (VC 1916/Win/avx2)
OS Version Windows 10 x64 (18362)
CPU Intel Core i7-8550U @ 1.80GHz [TB: 2.59GHz] (4C/8T)
GPU #0: GeForce GTX 1050 (640 cores, 1493 MHz)[PCIe3x16][441.08]
NVENC / CUDA NVENC API 9.1, CUDA 10.2, schedule mode: auto
Input Buffers CUDA, 41 frames
Input Info Avisynth+ 2.60(yv12)->nv12 [AVX2], 1280x720, 24000/1001 fps
Vpp Filters copyHtoD
cspconv(nv12 -> yv12(16bit))
edgelevel: strength 10.0, threshold 15.0, black 5.0, white 2.0
cspconv(yv12(16bit) -> p010)
Output Info H.265/HEVC main10 @ Level 5.1
1280x720p 1:1 23.976fps (24000/1001fps)
Encoder Preset quality
Rate Control VBRHQ
Bitrate 2048 kbps (Max: 153600 kbps)
Target Quality auto
Initial QP I:20 P:23 B:25
VBV buf size auto
Lookahead on, 32 frames, Adaptive I, B Insert
GOP length 600 frames
B frames 0 frames [ref mode: disabled]
Ref frames 16 frames
AQ on
CU max / min 32 / auto
VUI matrix:bt709,colorprim:bt709,transfer:bt709
Others mv:full-pel nonrefp
Script i'm trying to encode
MP_Pipeline("""
### platform: win64
FFmpegSource2("C:\Users\LEGEND\Desktop\Filter\File.mkv", width=1280, height=720, resizer="BICUBIC", colorspace="YV12")
### ###
### platform: win32
SetMemoryMax(1024)
LoadPlugin("C:\Program Files (x86)\AviSynth+\plugins\eDeen.dll")
eDeen(r=2, ty=14, tuv=21, ly=7, luv=10, hqc=true)
### prefetch: 32, 16
### ###
### platform: win32
SetMemoryMax(1024)
LoadPlugin("C:\Program Files (x86)\AviSynth+\plugins\Deen.dll")
Deen(mode="a2d", rad=2, thrY=14, thrUV=16, min=0.5)
### prefetch: 32, 16
### ###
### platform: win32
SetMemoryMax(1024)
Sharpen(0.20)
### prefetch: 32, 16
### ###
### platform: win32
SetMemoryMax(1024)
LoadPlugin("C:\Program Files (x86)\AviSynth+\plugins\aWarpSharp2.dll")
aWarpSharp2(depth=20)
### prefetch: 32, 16
### ###
### platform: win32
SetMemoryMax(1024)
LoadPlugin("C:\Program Files (x86)\AviSynth+\plugins\MSharpen.dll")
msharpen(threshold=10, strength=70,mask=false, highq=true)
### prefetch: 32, 16
### ###
### platform: win32
SetMemoryMax(1024)
FastLineDarken(strength=100, luma_cap=191, threshold=4, thinning=24)
### prefetch: 32, 16
### ###
### platform: win32
SetMemoryMax(1024)
Trim(18200, 25900)
### prefetch: 32, 16
### ###
""")
tell me if you need more details. and Thanks in advance.
Lynx_TWO
14th April 2020, 02:13
Title says it all: qaac handles 6.1 audio correctly but automatic settings default to Nero which copies the 7th channel, so that should be changed.
Thanks!
Lynx_TWO
14th April 2020, 02:15
When using loudness normalization (loudnorm) since it oversamples to 192khz to find true peak (still not enough btw, really need 8x or even up to 32x oversampling) the resulting AAC file is at 96khz instead of downsampling back to 48khz. Fix is to set --rate 48000 if loudnorm is used.
Thanks!
PS - it would be really sweet if someone could come up with a multi-pass solution to hit a target range accurately. Loudnorm does a decent job but is still only guessing. Perhaps writing a statistics file on each pass to adjust based on settings would help? Even having 6 passes, it would still complete before the average movie gets encoded :D
Algorithms to measure audio programme loudness and true-peak audio level (includes multichannel measurement algorithm)
https://www.itu.int/dms_pubrec/itu-r/rec/bs/R-REC-BS.1770-4-201510-I!!PDF-E.pdf
Loudness standards table
https://youlean.co/loudness-standards-full-comparison-table/
almanteka
14th April 2020, 02:40
Vapoursynth is much more stable than avisynth and fully supports 64-bit Why use avisynth? Encoding speed is always faster.
And the multithread is perfect.
The plug-in is fast indexed by LSMASHSource.dll
StaxRip Best Encoder
i installed Vapoursynth and the requiring packages just to test it out. it's possible to use it with mkv files converting to x265 using staxrip? what settings i need to use so staxrip use Vapoursynth? thanks in advance for any advice!
almanteka
14th April 2020, 02:44
@stax76
is there is any way to batch import jobs from an older version of staxrip to a newer one? i use the open project option and select the *.srip file at temp folder one at a time, but with hundreds of projects, i need to add all of them in one easy step, is that possible? thanks for your advice!!!
lifta19
14th April 2020, 09:18
i installed Vapoursynth and the requiring packages just to test it out. it's possible to use it with mkv files converting to x265 using staxrip? what settings i need to use so staxrip use Vapoursynth? thanks in advance for any advice!
Install:
Apps\Installers (python, VapourSynth)
Settings:
AVS Filters -> Filter Setup -> Vapoursynth
Settings are the same as avisynth
Lynx_TWO
14th April 2020, 23:25
i installed Vapoursynth and the requiring packages just to test it out. it's possible to use it with mkv files converting to x265 using staxrip? what settings i need to use so staxrip use Vapoursynth? thanks in advance for any advice!
There's a couple things AVISynth does that Vaporsynth doesn't (yet) SuperRes is one
Natty
15th April 2020, 06:56
because avisynth uses lower RAM
craigpro
18th April 2020, 13:54
Rigaya's NVenc 5.0 released
VincAlastor
20th April 2020, 09:53
https://github.com/OpenVisualCloud/SVT-AV1/releases/tag/v0.8.2
Latest SVT-AV1 encoder release brings new command line parameters,which is why Staxrip (2.1.0.8) integration should be revised, please.
I'm using following custom cmd right now:
--preset 6 --keyint 255 --irefresh-type 2 --scm 2
So just -q you can be set in staxrip GUI window.
The default value --irefresh-type 1 results in a problem to seek/skip in video stream. The problem seems to be known, but i can't find a solution. Maybe you know how to merge SVT-AV1 open GOPs with mkvmerge correctly, otherwise maybe you can think about to recommend users to use --irefresh-type 2 and longer GOPs up to 255 (256) in staxrip for now.
kalehrl
21st April 2020, 07:57
Is there something like 'analyse source' in staxrip?
I like this option which is present in MeGUI but I haven't found it in staxrip.
VincAlastor
21st April 2020, 09:18
https://github.com/OpenVisualCloud/SVT-AV1/releases/tag/v0.8.2
Latest SVT-AV1 encoder release brings new command line parameters,which is why Staxrip (2.1.0.8) integration should be revised, please.
I'm using following custom cmd right now:
--preset 6 --keyint 255 --irefresh-type 2 --scm 2
So just -q you can be set in staxrip GUI window.
The default value --irefresh-type 1 results in a problem to seek/skip in video stream. The problem seems to be known, but i can't find a solution. Maybe you know how to merge SVT-AV1 open GOPs with mkvmerge correctly, otherwise maybe you can think about to recommend users to use --irefresh-type 2 and longer GOPs up to 255 (256) in staxrip for now.
I tested Staxrip 2.1.0.9 test build. Integration of the modified SVT AV1 parameters works. --irefresh-type 1 is still not decoded correctly. So I assume that you haven't found a solution to the problem yet either.
Thanks for good and very fast implementation.
almanteka
21st April 2020, 20:18
where i can download the latest beta releases for StaxRip? since 2.1.0.1 i can't locate any download of the beta releases, only know about them in the changelog.md file. right now is at 2.1.0.9 and https://staxrip.readthedocs.io/intro.html#download send me to an page doesn't exist error! TIA!
Patman
21st April 2020, 20:28
Look here (http://forum.doom9.org/showthread.php?p=1908497)
Atlantis
21st April 2020, 21:38
Question why do we have the msvc version of x265? What is it good for?
Patman
21st April 2020, 21:48
Question why do we have the msvc version of x265? What is it good for?It was requested by some users and is not difficult to create. Compared to gcc8, it did better, but since gcc9 and above, this advantage has been gone.
almanteka
22nd April 2020, 00:55
Look here (http://forum.doom9.org/showthread.php?p=1908497)
thanks!!!!
Mister XY
22nd April 2020, 06:12
Since Version 2.1.0.8 DGIndex is missing in package. But it is needet for mpeg2, vob etc.
stax76
22nd April 2020, 06:55
In v2.1.0.9 DGIndex is disabled by default, it can be enabled in the settings dialog.
The author had requested to remove it from the distribution.
Mister XY
22nd April 2020, 15:51
Is there any alternate for this "vob mpg DGIndex" problem?
Patman
22nd April 2020, 17:09
You can still use DGIndex, you just have to activate it in the settings. DGIndex should just not be distributed with the package. And if you don't have DGIndex ready, you can download it.
DavidRyan
22nd April 2020, 17:36
Is there any way to change the 'FLAC' audio encoding profile to use a FLAC binary instead of ffmpeg? Have a recently compiled FLAC binary I wanted to use but despite trying a few things I can't seem to make it available as an option so would appreciate any advice - guessing I'm missing something obvious.
manolito
22nd April 2020, 18:54
DGIndex should just not be distributed with the package.
Even the latest Version 1.5.8 of DGIndex/DGDecode is still licensed under the GPL. This means that it can be distributed without the author's permission as long as the GPL requirements are fulfilled. Of course the friendly way is to ask the author for permission, but for GPL software this is not required.
stax76
22nd April 2020, 18:55
Is there any way to change the 'FLAC' audio encoding profile to use a FLAC binary instead of ffmpeg? Have a recently compiled FLAC binary I wanted to use but despite trying a few things I can't seem to make it available as an option so would appreciate any advice - guessing I'm missing something obvious.
I think you can use eac3to as encoder (there is an Encoder option), the libFLAC.dll it uses is from 2019.
There is a generic command line audio encoder where a custom command line can be used.
This generic audio encoder is probably still based on bat files and the general policy is to remove bat files from everywhere, it's probably the last feature where bat is used, there will be a replacement then, possibly using cmd.exe directly without bat file like the generic command line video encoder or more or less all command lines staxrip executes for job processing.
Patman
22nd April 2020, 19:44
Even the latest Version 1.5.8 of DGIndex/DGDecode is still licensed under the GPL. This means that it can be distributed without the author's permission as long as the GPL requirements are fulfilled. Of course the friendly way is to ask the author for permission, but for GPL software this is not required.Yeah, you're right but Stax wrote:
The author had requested to remove it from the distribution.
And you can follow the discuss in the other staxrip thread.
DavidRyan
22nd April 2020, 20:26
Thanks for the advice stax76, will try those.
Mister XY
24th April 2020, 17:45
You can still use DGIndex, you just have to activate it in the settings. DGIndex should just not be distributed with the package. And if you don't have DGIndex ready, you can download it.
That mean, DGIndex is the one and olny alternate for mpg vob etc. is it not in package, but i must download it for staxrip. Staxrip has the app not include, but with a frsh install, it ask me every time for the place from DGindex.
Patman
24th April 2020, 19:02
Yes, DGIndex is supported by staxrip but not distributed.
stax76
24th April 2020, 19:36
@Mister XY
Sometimes I remove a tool because of different reasons, most recently dgindex and xvid, but it's relatively easy to still use these tools:
StaxRip tries to find tools, often it can find the location of a tool.
If it cannot be found staxrip asks for the location.
An external custom path can be defined for all tools and this path is stored in the settings, keep your settings and staxrip will not ask a second time.
There is an excellent tool called voidtools everything which staxrip (and mpv.net) integrates to find things, it's probably a must-have for every power user.
videoh
24th April 2020, 19:49
Even the latest Version 1.5.8 of DGIndex/DGDecode is still licensed under the GPL. This means that it can be distributed without the author's permission as long as the GPL requirements are fulfilled. Of course the friendly way is to ask the author for permission, but for GPL software this is not required. That is correct. It is only the non-GPL tools that are affected. Thank you for clarifying that.
almanteka
25th April 2020, 06:58
an already encoded HEVC video i try to re-encode using x265 always renders a green screen on the re-encoded version. i just re-encode to shrink the file, but i test it out in placebo preset with the same results using avisynth! changed to vapoursynth and the green screen disappear! any ideas? only happens with already HEVC encoded videos.
stax76
25th April 2020, 09:54
You can use pastebin to post the log file.
VincAlastor
26th April 2020, 18:34
https://github.com/OpenVisualCloud/SVT-AV1/releases/tag/v0.8.3
Presets optimization
ACKR
27th April 2020, 04:32
Does staxrip support any deband filter? don't see them in the options
stax76
27th April 2020, 12:22
Does staxrip support any deband filter? don't see them in the options
I guess so but I'm not really a filter expert.
The Apps dialog and the docs are searchable:
https://staxrip.readthedocs.io/generated/tools.html
You can of course use filters that are not included, more or less everything that is possible with avisynth or vapoursynth is supported by staxrip using customizations.
Atlantis
27th April 2020, 19:38
RgTools v0.99 released. (https://github.com/pinterf/RgTools/releases)
Atlantis
28th April 2020, 00:03
RgTools v1.0 released. (https://github.com/pinterf/RgTools/releases)
almanteka
28th April 2020, 21:32
is possible to create an autocrop AVS filter and add it to the filters menu to create a template? i already know how to add filters to the menu, but can't find how to add the AutoCrop function. thanks in advance for your answers!
Atlantis
29th April 2020, 04:43
in AVS Filters, profiles, I add few lines. It stays there for few times when I open staxrip, but for example the next day that I open staxrip, those lines are gone! Any idea why this happens? Very strange.
jlw_4049
2nd May 2020, 04:26
I've tried several times to encode a season. I keep getting the error
"x264 [error]: 2nd pass has more frames than 1st pass (40556 vs 32444)"
Here is the log https://pastebin.com/229NL5Sf
I have tried manually setting the FPS as StaxRip was specifying the wrong FPS. However, that didn't seem to help. Any help would be appreciated!
proper88
2nd May 2020, 05:31
When i try to open a Blu-ray folder i get an empty playlist window.
I am using Beta 2.1.0.9
Does anybody else has this problem ?
Patman
2nd May 2020, 09:51
I've tried several times to encode a season. I keep getting the error
"x264 [error]: 2nd pass has more frames than 1st pass (40556 vs 32444)"
Here is the log https://pastebin.com/229NL5Sf
I have tried manually setting the FPS as StaxRip was specifying the wrong FPS. However, that didn't seem to help. Any help would be appreciated!
Hi jlw_4049,
have you tested 2-pass encoding without loading all plugins and scripts? During porting the informations, something goes wrong. Your source file has a frame rate of 29.97 fps, in your log file i saw ---------------------- Source Script Information ----------------------
Width : 720
Height : 480
Frames : 32444
Time : 22:33.185
Framerate : 23.976023 (24000/1001)
Format : YUV420P8
---------------------- Target Script Information ----------------------
Width : 640
Height : 480
Frames : 40556
Time : 22:33.219
Framerate : 29.970029 (30000/1001)
Format : YUV420P8
The incorrect information was ported from Source Script Information. Please test without plugins and scripts. I think 40556 frames are right.
jlw_4049
2nd May 2020, 17:18
Hi jlw_4049,
have you tested 2-pass encoding without loading all plugins and scripts? During porting the informations, something goes wrong. Your source file has a frame rate of 29.97 fps, in your log file i saw ---------------------- Source Script Information ----------------------
Width : 720
Height : 480
Frames : 32444
Time : 22:33.185
Framerate : 23.976023 (24000/1001)
Format : YUV420P8
---------------------- Target Script Information ----------------------
Width : 640
Height : 480
Frames : 40556
Time : 22:33.219
Framerate : 29.970029 (30000/1001)
Format : YUV420P8
The incorrect information was ported from Source Script Information. Please test without plugins and scripts. I think 40556 frames are right.
The QTGMC filter is actually causing the issues. The default settings when you enable it via StaxRip, one of the filters is causing the issues.
When I use the default full repair setting
(QTGMC(preset="Very Slow", InputType=3, sourceMatch=3, sharpness=0.2, tr2=2, ediThreads=8)
The issue is there with the above code^
If I just edit the code and input (QTGMC(preset="Very Slow") it works perfectly. So, one of the commands, I haven't done much testing, and I probably will just end up using stock settings, is causing the issue.
--------------------------------------
Now on to the framerate. Staxrip in the log is wrong on the target framerate. The framerate of DVD I'm attempting to encode is 23.976 fps (24000/1001), or so mediainfo says.
Obviously I'm new to DVD encoding, so learning everything, so this might be correct anyways.
This is probably irrelevant since it was the QTGMC filter preset causing the issue. Firing up the full encode again with just 'Very Slow' set.
EDIT: just using the default QTGMC command did not work.
------------------------------------------
UPDATE:
The issue only occurs when I do a batch encode based off of a template and manually have the source set to MPEG2. If I leave the source as "Automatic" with all the rest of my settings the same, it works fully so far. It still uses MPEG2source, so I am not sure what the difference is.
Hello i have a question. Staxrip only encodes 2 audio tracks and doesn't encode any other ones. Anyway to ensure it encodes all tracks?
jlw_4049
3rd May 2020, 01:52
Hello i have a question. Staxrip only encodes 2 audio tracks and doesn't encode any other ones. Anyway to ensure it encodes all tracks?
You could encode audio via ffpmeg or something else like that and mux the file together how you want it when you're done.
almanteka
3rd May 2020, 08:16
Hello i have a question. Staxrip only encodes 2 audio tracks and doesn't encode any other ones. Anyway to ensure it encodes all tracks?
you can manually add audio files in the container options > audio tab and select the encode format when adding the audio file. see photo below:
https://i.imgur.com/uUHjK3n.jpg
VirulentPip
3rd May 2020, 12:55
Hey all, I'm intrigued as to why Subs don't seem to hardcode when using NVEnc Hardware to decode and encode and only works when choosing AviSynth to decode?
Patman
3rd May 2020, 18:55
Only ass subs are supported by nvenc to be hardcoded in the file.
VirulentPip
3rd May 2020, 19:52
Ohhh! Awesome thanks :)
Hello i have a couple of more questions:-
1)is there anyway to adjust memory cache for vapoursynth? i have error try increasing cache when only 50% memory is being used
2) when adding plugins using profiles do i separate multiple line code using ; ? where the 1st line is import code for the plugin or script as it is not included in stax
3) https://staxrip.readthedocs.io/generated/tools.html#finedehalo it says here that finedehalo2 is included but i couldn't find it anywhere?
thanks
Arkana
4th May 2020, 02:33
Hello, what I need to do? I see the plugin is already on the folder
https://i.postimg.cc/HnvrF7xY/screenshot-669.png (https://postimages.org/)
i am having another problem and this the worst of them all. whenever i try to use vapoursynth scripts the filters get copied into audio avisynth script as a result the encoder also crashes. why does this happen?.As a result whenever i choose no audio while using vapoursynth then only is the video encoded. any help is appreciated
Edit:
this is the error
D:\StaxRip-x64-2.0.8.0-stable\Apps\Encoders\ffmpeg\ffmpeg.exe -i "G:\test_Audio02.JPN_DecodeFFAudioSource.avs" -y -hide_banner "G:\test_Audio02.JPN_convFFAudioSource.w64"
clip = core.ffms2.Source(r"", cachefile=r"G:\.ffindex")
#clip = core.std.AssumeFPS(clip, None, 25, 1)
AudioDub(last,FFAudioSource("G:\test.dts", cachefile="G:\test_Audio02.JPN.ffindex"))
clip = core.dfttest.DFTTest(clip, sigma=1)
Audiochannels() >= 6 ? Down2(last) : last
function Down2(clip a)
{
a = ConvertAudioToFloat(a)
fl = GetChannel(a, 1)
fr = GetChannel(a, 2)
c = GetChannel(a, 3)
lfe = GetChannel(a, 4)
sl = GetChannel(a, 5)
sr = GetChannel(a, 6)
l_sl = MixAudio(fl, sl, 0.2929, 0.2929)
c_lfe = MixAudio(lfe, c, 0.2071, 0.2071)
r_sr = MixAudio(fr, sr, 0.2929, 0.2929)
l = MixAudio(l_sl, c_lfe, 1.0, 1.0)
r = MixAudio(r_sr, c_lfe, 1.0, 1.0)
return MergeChannels(l, r)
}
[avisynth @ 000001d145ac3240] Script error: expected a , or )
(G:\test_Audio02.JPN_DecodeFFAudioSource.avs, line 3, column 28)
G:\test_Audio02.JPN_DecodeFFAudioSource.avs: Unknown error occurred
edit: this is the avisynth file being generated
LoadPlugin("D:\StaxRip-x64-2.0.8.0-stable\Apps\Plugins\AVS\DFTTest\dfttest.dll")
LoadPlugin("D:\StaxRip-x64-2.0.8.0-stable\Apps\Plugins\Dual\ffms2\ffms2.dll")
LoadPlugin("D:\StaxRip-x64-2.0.8.0-stable\Apps\Plugins\Dual\flash3kyuu_deband\flash3kyuu_deband.dll")
clip = core.ffms2.Source(r"", cachefile=r"G:\.ffindex")
#clip = core.std.AssumeFPS(clip, None, 25, 1)
AudioDub(last,FFAudioSource("G:\test.dts", cachefile="G:\test.ffindex"))
clip = core.dfttest.DFTTest(clip, sigma=1)
clip = core.f3kdb.Deband(clip)
Audiochannels() >= 6 ? Down2(last) : last
function Down2(clip a)
{
a = ConvertAudioToFloat(a)
fl = GetChannel(a, 1)
fr = GetChannel(a, 2)
c = GetChannel(a, 3)
lfe = GetChannel(a, 4)
sl = GetChannel(a, 5)
sr = GetChannel(a, 6)
l_sl = MixAudio(fl, sl, 0.2929, 0.2929)
c_lfe = MixAudio(lfe, c, 0.2071, 0.2071)
r_sr = MixAudio(fr, sr, 0.2929, 0.2929)
l = MixAudio(l_sl, c_lfe, 1.0, 1.0)
r = MixAudio(r_sr, c_lfe, 1.0, 1.0)
return MergeChannels(l, r)
}
the highlighted part shouldnt be there right
whenever i try to encode video only its fine
Patman
4th May 2020, 12:53
Hello, what I need to do? I see the plugin is already on the folder
https://i.postimg.cc/HnvrF7xY/screenshot-669.png (https://postimages.org/)
Rename the folder both to Dual and test again.
Patman
4th May 2020, 12:56
i am having another problem and this the worst of them all. whenever i try to use vapoursynth scripts the filters get copied into audio avisynth script as a result the encoder also crashes. why does this happen?.As a result whenever i choose no audio while using vapoursynth then only is the video encoded. any help is appreciated
Edit:
this is the error
...
whenever i try to encode video only its fine
I commented your problem on Github.
Statick
4th May 2020, 18:43
couple of issues I'm having with Staxrip2.0 :
if I use the default temp folder name and choose to delete temp files, then it gets deleted and that's all good. but if I specify a custom temp folder name then selecting to delete temp files has no effect, the temp folder remains with all the files inside it.
the default temp folder name has issues with very long folder names (this is why I specify a custom temp folder name). if the folder name and the video name are over a certain length, then the default temp folder name can end up too long and Staxrip crashes. it also handles this very poorly as well - the app crashes, it opens a log file in notepad, it opens a browser to show a staxrip support page, it opens the problem folder in windows, as well as popping up multiple dialog boxes. it's quite punishing if this happens when you're on the machine, and suddenly all this stuff pops up at once. it also then stops processing the task queue until the error dialogs are clicked on. it would be good if this error could be handled more gracefully without opening half a dozen new windows, and if the task queue would also continue (so a machine rendering overnight doesn't sit idle for 8 hours). but also it would be good if the default temp folder did not cause this behaviour if the folder and file names involved happen to be too long.
stax76
4th May 2020, 19:05
Maybe try last beta:
https://staxrip.readthedocs.io/introduction.html#beta
jlw_4049
4th May 2020, 19:18
I generally install it in a folder on the root of my SSD. Never have had issues with temp files but file names that are super long I've had issues in the past.
Sent from my Pixel 3a using Tapatalk
stax76
4th May 2020, 19:56
In the beta there is a setting which defines a character limit of 150 characters, if the path is longer it will show:
In theory Windows supports paths that are longer than 260 characters, in reality neither Windows, nor the .NET Framework or the used tools have full long path support. StaxRip has a setting that allows to increase the limit but it's not recommended changing this limit! It will almost certainly not work!
jlw_4049
4th May 2020, 21:03
In the beta there is a setting which defines a character limit of 150 characters, if the path is longer it will show:
In theory Windows supports paths that are longer than 260 characters, in reality neither Windows, nor the .NET Framework or the used tools have full long path support. StaxRip has a setting that allows to increase the limit but it's not recommended changing this limit! It will almost certainly not work!It's something I've gotten used to. It's easier to just rename them. As long as I rename the super long ones I've never had an issue.
Sent from my Pixel 3a using Tapatalk
I commented your problem on Github.
thanks Patman this works. which decoders can you use with vapoursynth?
also few other questions
1)is there anyway to adjust memory cache for vapoursynth? i have error try increasing cache when only 50% memory is being used
2) when adding plugins using profiles do i separate multiple line code using ; ? where the 1st line is import code for the plugin or script as it is not included in stax
3) https://staxrip.readthedocs.io/gener...tml#finedehalo it says here that finedehalo2 is included but i couldn't find it anywhere?
Patman
4th May 2020, 23:03
thanks Patman this works. which decoders can you use with vapoursynth?
I think ffmpeg, but i have a look at it. Maybe this option is a bit tricky/buggy
1)is there anyway to adjust memory cache for vapoursynth? i have error try increasing cache when only 50% memory is being used
there is an option called std.cache (http://www.vapoursynth.com/doc/functions/cache.html). You can ask in the vapoursynth thread for more informations.
2) when adding plugins using profiles do i separate multiple line code using ; ? where the 1st line is import code for the plugin or script as it is not included in stax
vapoursynth or avisynth usage?
3) https://staxrip.readthedocs.io/gener...tml#finedehalo it says here that finedehalo2 is included but i couldn't find it anywhere?
https://i.imgur.com/WvZz8E6.png
stax76
4th May 2020, 23:08
when adding plugins using profiles do i separate multiple line code using ; ? where the 1st line is import code for the plugin or script as it is not included in stax
There are multi line filter profiles defined at the top of the defaults:
LSMASHVideoSource =
LSMASHVideoSource("%source_file%")
#AssumeFPS(25)
I think ffmpeg, but i have a look at it. Maybe this option is a bit tricky/buggy
there is an option called std.cache (http://www.vapoursynth.com/doc/functions/cache.html). You can ask in the vapoursynth thread for more informations.
vapoursynth or avisynth usage?
https://i.imgur.com/WvZz8E6.png
1) i know how set cache for one vapoursynth script but i wanted to know if there is a way to incorporate it into a profile so its included at top of .vpy scripts generated everytime
2)vapoursynth. To stax76 does that mean to incorporate something like this you just need line
Adaptive grain = import kagefunc as kgf
clip = kgf.adaptive_grain(clip)
and the ; isn't needed?
3)code for finedehalo2 is different but i added it using profiles since its one line only.
Atlantis
7th May 2020, 14:13
I noticed this today. When I batch encode several files. If later I go and open one project of one of those files and change settings and the name of the output, it always encodes to the old name and overwrites the old file [file]_new.
For example if in target I say [file]_new2 it always encodes to [file]_new.
So this happens to projects that were created automatically with Batch Encoding.
chipxtreme
7th May 2020, 14:55
NVEnc 5.01 is out
MKVToolnix 46.0.0 is out
jlw_4049
8th May 2020, 06:45
Wanted to report a bug.
https://i.imgur.com/qa77ORW.png
Sometimes when I'm going through settings the window will get to large to see all the way to the top. There is no way to resize the window or drag it and move it around.
almanteka
11th May 2020, 10:10
any way to change the job % progress bar color from gray? example picture below
https://i.imgur.com/ZgEErR3.jpg
stax76
11th May 2020, 10:38
any way to change the job % progress bar color from gray? example picture below
It was already changed two times because of conflicts with user theme colors, too much risk changing it again.
almanteka
11th May 2020, 16:50
It was already changed two times because of conflicts with user theme colors, too much risk changing it again.
never experience the versions with a colored bar, maybe 'cause i was stocked with v1.6.0.3, the last with the option of "demux and index before creating jobs". still using it with updated apps for creating batch jobs that needs adjustments only and using the latest stable for that adjustments and encoding since i can't find a way to batch demux and index the files before creating the jobs with newer versions. i thought the progress bar color was related with the user theme colors or somewhere in the options to select the color myself. too hard to see when the monitor is at distance or at an angle, and i'm using a 27" monitor! thanks for your reply!
Atlantis
11th May 2020, 18:55
never mind
stax76
11th May 2020, 19:24
Sorry I missed your post, I do my best to maintain staxrip, it's not complete fun because I gave up encoding years ago and lost interest in encoding. A lot of tools updating, not so much programming, not really convinced of the help platform rest/sphinx etc. mpv(.net) is much more exciting and that's what I was working on in recent days. If I don't reply and say that I examined or bookmarked a request then it might get lost, reporting an issue on the tracker is more work but has the advantage that nothing gets lost, the chance to get help from me and also various other staxrip users is higher on the tracker. About your request, I confirm it's a bug and I've bookmarked it, hopefully it's not difficult to fix.
edit:
Actually I had it bookmarked, did just not post that I did so.
edit2:
not easy but fixed
stax76
12th May 2020, 02:05
Wanted to report a bug.
https://i.imgur.com/qa77ORW.png
Sometimes when I'm going through settings the window will get to large to see all the way to the top. There is no way to resize the window or drag it and move it around.
Is there a way to reproduce it?
jlw_4049
12th May 2020, 09:08
Is there a way to reproduce it?Yes I'll provide steps tomorrow when I get on my server.
Short version is it happens when I switch back and forth from 2 pass to quality encoding.
It mainly happens when the command line window has a lot of commands. The top just goes up into the top of the screen and I can't pull it down.
I'll try to explain exact steps tomorrow.
Sent from my Pixel 3a using Tapatalk
tormento
12th May 2020, 18:35
Is there a way to import a AVS script without having it modified by StaxRip?
Sometimes I need it only as a interface for encoder, nothing else.
stax76
12th May 2020, 18:52
Is there a way to import a AVS script without having it modified by StaxRip?
Sometimes I need it only as a interface for encoder, nothing else.
StaxRip should not modify the original file and it should support all scripts without exception, try 2.1.1.2 Beta.
tormento
12th May 2020, 19:16
StaxRip should not modify the original file and it should support all scripts without exception, try 2.1.1.2 Beta.
I just tried, that’s why I am asking you. :)
It creates a sort of import script, loading KNLMeansCL too from local tools dir.
stax76
12th May 2020, 19:24
You mean it added more lines than the import line, like LoadPlugin calls? If so then I can fix it, it's harmless.
tormento
12th May 2020, 19:31
You mean it added more lines than the import line, like LoadPlugin calls? If so then I can fix it, it's harmless.
My script is:SetFilterMTMode("DEFAULT_MT_MODE", 2)
LoadPlugin("D:\eseguibili\media\DGDecNV_x64\DGDecodeNV.dll")
DGSource("E:\in\1_45 Star trek 3 — Alla ricerca di Spock\spock.dgi",ct=128,cb=136,cl=0,cr=0)
SMDegrain (tr=4, thSAD=500, refinemotion=false, n16=true, mode=0, contrasharp=false, PreFilter=4, truemotion=true, plane=4, chroma=true)
Prefetch(6)
I open it with right click and it generates the following in a spock_temp dir inside the original avs script:
spock.avs
LoadPlugin("D:\eseguibili\media\StaxRip_x64\Apps\Plugins\Dual\KNLMeansCL\KNLMeansCL.dll")
Import("D:\eseguibili\media\StaxRip_x64\Apps\Plugins\AVS\SMDegrain\SMDegrain.avsi")
Import("E:\in\1_45 Star trek 3 — Alla ricerca di Spock\spock.avs")
spock_source.avs
LoadPlugin("D:\eseguibili\media\StaxRip_x64\Apps\Plugins\Dual\KNLMeansCL\KNLMeansCL.dll")
Import("D:\eseguibili\media\StaxRip_x64\Apps\Plugins\AVS\SMDegrain\SMDegrain.avsi")
Import("E:\in\1_45 Star trek 3 — Alla ricerca di Spock\spock.avs")
and if I right click preview code, I get
LoadPlugin("D:\eseguibili\media\StaxRip_x64\Apps\Plugins\Dual\KNLMeansCL\KNLMeansCL.dll")
Import("D:\eseguibili\media\StaxRip_x64\Apps\Plugins\AVS\SMDegrain\SMDegrain.avsi")
Import("E:\in\1_45 Star trek 3 — Alla ricerca di Spock\spock.avs")
Bit useless and confusing IMHO, as I want to load my avsi and my plugins (the original KNLMeansCL is not compatible with AviSynth+ 3.0, as example).
I'd like, if possible, to have a way to transparently import a script with no fuss, bell or whistles.
stax76
12th May 2020, 20:00
I've uploaded a hotfix to the onedrive and dropbox folder.
tormento
12th May 2020, 20:29
I've uploaded a hotfix to the onedrive and dropbox folder.
Thanks, will try asap.
Atlantis
13th May 2020, 01:43
Don't know if post #1765 was to me but just to clarify, my never mind post was about my own post. I had posted an incorrect answer to an earlier post, I edited my post to remove it.
I would never expect to receive replies to all my posts. Thank you.
tormento
13th May 2020, 09:23
I've uploaded a hotfix to the onedrive and dropbox folder.
Ok, trying now.
My 2 cents:
Why to import a script instead of using that's ready?
Is there a way to save the encoding preferences instead of having to set every time a new file is opened?
please add switches in x264 config to add --keyint xxx and --opencl
why when you start jobs you can't interact with StaxRip GUI anymore? You perhaps want to add more jobs to be executed later.
stax76
13th May 2020, 11:30
staxrip needs control over the script to implement an integrated workflow, most tools use the avisynth API by using import:
https://github.com/staxrip/staxrip/blob/master/FrameServer/AviSynthServer.cpp#L75
This is also true for megui.
https://staxrip.readthedocs.io/features.html
https://staxrip.readthedocs.io/faq.html#why-don-t-settings-persist
tormento
13th May 2020, 12:47
staxrip needs control over the script
Thanks for answering 1) and 2). I don't understand if you aswered 3) and 4) too.
stax76
13th May 2020, 13:15
please add switches in x264 config to add --keyint xxx and --opencl
At the bottom of the x264 dialog there is search field and drop-down.
The Search dropdown field at the dialog bottom left lists options and can be used to quickly find options, it searches command line switches, labels and dropdowns. Multiple matches can be cycled by pressing enter.
It lists and finds --keyint and --opencl
why when you start jobs you can't interact with StaxRip GUI anymore? You perhaps want to add more jobs to be executed later.
The design isn't perfect, it was always like this and it's too difficult to fix but you can start another instance and add jobs I think, even running instances will see the new jobs I think.
Atlantis
13th May 2020, 17:15
I do this all the time. You can run another instance of staxrip and work on another job. You can either create a new project or open an existing project
tormento
13th May 2020, 17:38
Thanks you both
Natty
14th May 2020, 07:22
i want to load 2 videos at once on and use some frames from video 1 and some from video 2. is it possible to index 2 videos in 1 job?
Khun_Doug
14th May 2020, 15:56
Natty, could you explain what you are trying to do? For instance, are you trying to merge part of video #1 and then append part of video #2, to make just one video? Or do you want specific frames from video #2 interspersed with video #1 as the output video?
Atlantis
14th May 2020, 16:52
You can surely do that in an avs script.
theincognito
14th May 2020, 19:14
The design isn't perfect, it was always like this and it's too difficult to fix but you can start another instance and add jobs I think, even running instances will see the new jobs I think.
Hi. How to encode in EAC3? I tried with eac3to and it ended up outputting a normal ac3.
theincognito
14th May 2020, 19:20
It was requested by some users and is not difficult to create. Compared to gcc8, it did better, but since gcc9 and above, this advantage has been gone.
So you are saying that msvc builds are no longer faster than gcc builds on intel cpus? Also, is there a way we can force the encoder to use avx2? I have seen x265 builds with avx2, avx tags and supposedly, for avx2 pcs, avx2 builds are slightly faster.
almanteka
14th May 2020, 19:35
So you are saying that msvc builds are no longer faster than gcc builds on intel cpus? Also, is there a way we can force the encoder to use avx2? I have seen x265 builds with avx2, avx tags and supposedly, for avx2 pcs, avx2 builds are slightly faster.
maybe --asm avx2? from x265 docs:
"Performance Options
--asm <integer:false:string>, --no-asm
x265 will use all detected CPU SIMD architectures by default. You can disable all assembly by using --no-asm or you can specify a comma separated list of SIMD architectures to use, matching these strings: MMX2, SSE, SSE2, SSE3, SSSE3, SSE4, SSE4.1, SSE4.2, AVX, XOP, FMA4, AVX2, FMA3, AVX512
Some higher architectures imply lower ones being present, this is handled implicitly.
One may also directly supply the CPU capability bitmap as an integer.
Note that by specifying this option you are overriding x265’s CPU detection and it is possible to do this wrong. You can cause encoder crashes by specifying SIMD architectures which are not supported on your CPU.
Default: auto-detected SIMD architectures"
Patman
14th May 2020, 19:57
So you are saying that msvc builds are no longer faster than gcc builds on intel cpus? Also, is there a way we can force the encoder to use avx2? I have seen x265 builds with avx2, avx tags and supposedly, for avx2 pcs, avx2 builds are slightly faster.I can compile versions with gcc and msvc (both with avx and avx2) and you can test them.
theincognito
14th May 2020, 20:09
maybe --asm avx2? from x265 docs:
"Performance Options
--asm <integer:false:string>, --no-asm
x265 will use all detected CPU SIMD architectures by default. You can disable all assembly by using --no-asm or you can specify a comma separated list of SIMD architectures to use, matching these strings: MMX2, SSE, SSE2, SSE3, SSSE3, SSE4, SSE4.1, SSE4.2, AVX, XOP, FMA4, AVX2, FMA3, AVX512
Some higher architectures imply lower ones being present, this is handled implicitly.
One may also directly supply the CPU capability bitmap as an integer.
Note that by specifying this option you are overriding x265’s CPU detection and it is possible to do this wrong. You can cause encoder crashes by specifying SIMD architectures which are not supported on your CPU.
Default: auto-detected SIMD architectures"
Thank you :)
theincognito
14th May 2020, 20:10
I can compile versions with gcc and msvc (both with avx and avx2) and you can test them.
That will be great, if its not too much of a bother for you :)
Arkana
14th May 2020, 23:20
Hi. How to encode in EAC3? I tried with eac3to and it ended up outputting a normal ac3.
you cannot encode it properly using command line. Even if you could the result would be bad as ffmpeg eac3 encoder is very bad.
You need Dolby Media encoder for that
Arkana
14th May 2020, 23:22
Rename the folder both to Dual and test again.
Hi, I got same result still
https://i.postimg.cc/sv6yWr33/screenshot-710.png (http://postimg.cc/sv6yWr33)
proper88
15th May 2020, 04:26
Hi,
is it possible to change/modifier parameters of a saved job ?
thanks,
proper 88
stax76
15th May 2020, 09:26
@Arkana
Code 126 means ERROR_MOD_NOT_FOUND, it should mean DLL could not be found but unfortunately Windows does not tell which DLL, it could be a dependency.
is it possible to change/modifier parameters of a saved job ?
The Jobs dialog has a Load button, this should work for normal jobs, for batch jobs I'm not sure.
Natty
15th May 2020, 15:02
Natty, could you explain what you are trying to do? For instance, are you trying to merge part of video #1 and then append part of video #2, to make just one video? Or do you want specific frames from video #2 interspersed with video #1 as the output video?
only taking some frames from each source. lets say i have 3 sources with 100 frames each. i would like to take 20 frames from source 1, 40 from source 2 and 40 from sources 3 selectively and filter all of them selectively scene by scene and make a hybrid encode of 100 frames.
i can get that to work with my AVS/VS script and there are many other things which can be done but for that to work. i think i would need to index 2 - 3 videos at once. or is it possible without it? :)
Khun_Doug
15th May 2020, 15:22
only taking some frames from each source. lets say i have 3 sources with 100 frames each. i would like to take 20 frames from source 1, 40 from source 2 and 40 from sources 3 selectively and filter all of them selectively scene by scene and make a hybrid encode of 100 frames.
i can get that to work with my AVS/VS script and there are many other things which can be done but for that to work. i think i would need to index 2 - 3 videos at once. or is it possible without it? :)
You almost certainly need to manually write an AVS or VPY script for that. And the really nice thing with manually editing a script is you can apply different filters, different resize, etc.This sounds like an interesting project. I have an AVS script I use to read multiple sources and then I have different methods of viewing the sources. Stack vertical/horizontal, and view differences between them. Manually editing a script can do some really neat things.
jonrodrigos
15th May 2020, 15:48
good morning people,
I'm having problems with staxrip using VapourSynth, since they released the new version r49 I can't use staxrip stable or beta, only previous versions like r48.
now released version VapourSynth r50 and the same error occurs see the printscreen.
when loading the video file it already gives error of VapourSynth did anyone experience the same problem?
NOTE: I have already tried the portable version and the problem continues, if using R48 it works normal, this version of python 3.8 is installed.
thank you
https://imgur.com/u0s41qb
https://imgur.com/u0s41qb
I couldn't post the photo sorry, but I leave the link to the photo.
who can help me thank you.
stax76
15th May 2020, 16:42
@jonrodrigos
Probably your vapoursynth setup does not work, it happens often.
If you use the last staxrip beta 2.1.1.2 you can use the included portable vapoursynth version, to do so there are two ways:
1. Uninstall python and vapoursynth
2. Go into the Apps dialog and define a custom path to the included python and vapoursynth version
almanteka
15th May 2020, 17:27
Hi, I got same result still
https://i.postimg.cc/sv6yWr33/screenshot-710.png (http://postimg.cc/sv6yWr33)
staxrip recognized the location? go to apps > manage > on the left list avisynth > KNLMeansCL > status OK? the same for vapoursynth: apps > manage > on the left list vapoursynth> KNLMeansCL > status OK? if not, then go to path > browse and locate the file manually for avisynth and vapoursynth
StaxRip folder\Apps\Plugins\Dual\KNLMeansCL\KNLMeansCL.dll
jonrodrigos
15th May 2020, 17:40
@jonrodrigos
Probably your vapoursynth setup does not work, it happens often.
If you use the last staxrip beta 2.1.1.2 you can use the included portable vapoursynth version, to do so there are two ways:
1. Uninstall python and vapoursynth
2. Go into the Apps dialog and define a custom path to the included python and vapoursynth version
good afternoon, thanks for the reply but I pointed to the internal folders as requested and the error continues. my current version is the latest beta staxrip 2.1.1.2 if i install the R48 version it works, only at 49 and 50 that happens, I have tried several versions of staxrip with the r49 and 50 versions and it does not work.
any video file when it finishes loading it presents this error.
I already did a virtual pc to test and the same happens.
https://i.postimg.cc/JDtM8mzm/2020-05-15-3.png (https://postimg.cc/JDtM8mzm)
https://i.postimg.cc/PvZyvp54/2020-05-15-1.png (https://postimg.cc/PvZyvp54)
https://i.postimg.cc/bd23BM9t/2020-05-15-2.png (https://postimg.cc/bd23BM9t)
almanteka
15th May 2020, 17:41
I can compile versions with gcc and msvc (both with avx and avx2) and you can test them.
that would be great!!! i like the M version! :eek:
stax76
15th May 2020, 17:52
@jonrodrigos
Maybe it's because you don't have a custom path to the included portable python.
jonrodrigos
15th May 2020, 18:21
@jonrodrigos
Maybe it's because you don't have a custom path to the included portable python.
would it be this? if everything is already pointing to the internal portable
and I had uninstalled the installs
I also did it on a clean windows installation, pointing only to the portable
https://i.postimg.cc/VdwNdKmC/2020-05-15-4.png (https://postimg.cc/VdwNdKmC)
VirulentPip
16th May 2020, 07:01
For a while now I've been using Turing Nvenc my encodes (1080p) I have just got a Ryzen 3900x and was wondering if there's any settings out there I can use that would get me the same quality output but for potentially less bitrate/file sizes?
This is what I use for 1080p Blurays
--vbrhq 4400 --codec h265 --preset quality --profile main10 --level 5.1 --output-depth 10 --max-bitrate 4400 --aq --aq-temporal --bref-mode each --bframes 5 --ref 15 --gop-len 240 --lookahead 32 --output-buf 32 --vpp-unsharp radius=2,weight=0.65,threshold=20 --vpp-edgelevel strength=6.0,threshold=16.0,black=0,white=0
And this for older Blurays with a lot of noise
--vbrhq 4400 --codec h265 --preset quality --profile main10 --level 5.1 --output-depth 10 --max-bitrate 4400 --aq --aq-temporal --bref-mode each --bframes 5 --ref 15 --gop-len 240 --lookahead 32 --output-buf 32 --vpp-knn --vpp-unsharp radius=2,weight=0.65,threshold=20 --vpp-edgelevel strength=6.0,threshold=16.0,black=0,white=0
Should I change over to x265 or continue with Nvenc and is there anything I should change?
If anyone could point me in the right direction that would be great :)
colinhunt
16th May 2020, 19:39
Could someone provide me with some pointers on how to enable FFV1 version 3 encoding (-c:v ffv1 -level 3) in Staxrip, using ffmpeg of course? I can't figure out how to add it to encoding options. Using beta 2.1.1.1, btw. Thanks.
Patman
16th May 2020, 20:02
updated some tools for staxrip...
Patman
16th May 2020, 20:48
Could someone provide me with some pointers on how to enable FFV1 version 3 encoding (-c:v ffv1 -level 3) in Staxrip, using ffmpeg of course? I can't figure out how to add it to encoding options. Using beta 2.1.1.1, btw. Thanks.
Currently this is only possible with the command line.
colinhunt
16th May 2020, 21:39
Currently this is only possible with the command line.
Okay, thanks. No wonder I couldn't figure it out :)
almanteka
17th May 2020, 01:15
updated some tools for staxrip...
whats the difference between an msvc version and gcc? method of compiling? same results? thanks!
Arkana
17th May 2020, 09:34
staxrip recognized the location? go to apps > manage > on the left list avisynth > KNLMeansCL > status OK? the same for vapoursynth: apps > manage > on the left list vapoursynth> KNLMeansCL > status OK? if not, then go to path > browse and locate the file manually for avisynth and vapoursynth
StaxRip folder\Apps\Plugins\Dual\KNLMeansCL\KNLMeansCL.dll
both status are OK
stax76
17th May 2020, 09:49
@Arkana
Which GPU is in use?
colinhunt
17th May 2020, 10:28
Staxrip 2.1.1.1 beta stops processing on an error before writing a single frame when trying to output ProRes. Same job works fine in 2.0.8.0 Stable (edit: after it prompted to install Avisynth). I'll add what little information I can gather of the crash shortly.
Job: deinterlacing and IVTC'ing a music video.
TFM()
TDecimate(cycle=25,cycleR=5)
DeBlock QED (defaults)
VagueDeNoiser (defaults)
Output to ProRes normal profile.
update: Figured out why 2.1.1.1 beta throws in the towel. Avisynth+ was not installed. Odd though, I have done perhaps two dozen jobs on 2.1.1.1 and it never complained about Avisynth missing. I ran 2.0.8.0 the first time on this PC today; it told me to install Avisynth, and once I did that, 2.1.1.1 began outputting ProRes as well.
(Sidetrack: Could someone shed some light on why the CPU load remains at 4% for the job mentioned above? I get 10fps out of StaxRip with that 4%. Would be awesome to get the job done faster; where's the bottleneck?)
Patman
17th May 2020, 10:53
whats the difference between an msvc version and gcc? method of compiling? same results? thanks!MSVC (Microsoft Visual C) and GCC (GNU Compiler Collection) are different compilers. You are right with the statement that the methods of compiling are different. As a result, there are performance differences in the builds.
stax76
17th May 2020, 12:24
@colinhunt
2.1.1.3 is portable, I've not installed avisynth or fftw, tried all your configuration and it worked fine.
Khun_Doug
17th May 2020, 16:00
Staxrip 2.1.1.1 beta stops processing on an error before writing a single frame when trying to output ProRes. Same job works fine in 2.0.8.0 Stable (edit: after it prompted to install Avisynth). I'll add what little information I can gather of the crash shortly.
(Sidetrack: Could someone shed some light on why the CPU load remains at 4% for the job mentioned above? I get 10fps out of StaxRip with that 4%. Would be awesome to get the job done faster; where's the bottleneck?)
A lot of AVISynth filters perform really well when using PreFetch. Look through the menus and for the MT Mode stuff and you should find the option to set the number of threads (that's the prefetch). If you have 8 threads on your CPU, try setting PreFetch to 4, or 6, or even 8. You can really get a remarkable speed bump this way.
One note: I have an AMD 3950X with 16 cores / 32 threads. I found the sweet spot to be between 12 and 16 threads when using X265. Just because you have a lot of threads does not mean you will get a speed bump beyond a certain point.
Atak_Snajpera
17th May 2020, 16:03
If you have 8 threads on your CPU, try setting PreFetch to 4, or 6, or even 8. You can really get a remarkable speed bump this way.
The rule is simple. Always use value equal to number of physical cores not virtual ones. With higher value than number of cores you will notice choking effect. (cpu usage drops constantly)
jlw_4049
17th May 2020, 17:36
@stax76 is there anyway to setup the program to where the video bitrate is tied to (x264/x265) preset instead of the template? Similar to how the CRF value is tied to it?
stax76
17th May 2020, 17:50
@stax76 is there anyway to setup the program to where the video bitrate is tied to (x264/x265) preset instead of the template? Similar to how the CRF value is tied to it?
In the x265 dialog the Custom tab can be used for this, custom switches override GUI switches.
jlw_4049
17th May 2020, 17:53
In the x265 dialog the Custom tab can be used for this, custom switches override GUI switches.
Thank you for this information! :)
@stax76 - I know you are busy with tons of stuff. IDK if you would want to do this, but could you add a way to setup more then just 2 audio tracks. For those rare films/etc where there is 3 or 4 of them?
Also is there anyway you could add a DTS down mix to core option for the audio section? You can do this with ffmpeg via a command like this "-c:v copy -bsf:a dca_core -c:a copy" and I know there is a way to do it with mkv.
Thanks!
stax76
17th May 2020, 19:12
@stax76 - I know you are busy with tons of stuff. IDK if you would want to do this, but could you add a way to setup more then just 2 audio tracks. For those rare films/etc where there is 3 or 4 of them?
If you are not batch processing you can add more audio tracks in the Container Options, it has an audio Tab.
Also is there anyway you could add a DTS down mix to core option for the audio section? You can do this with ffmpeg via a command like this "-c:v copy -bsf:a dca_core -c:a copy" and I know there is a way to do it with mkv.
For that I would need more info, ideally on the issue tracker, mediainfo for the input file, command line and mediainfo for the output file.
jlw_4049
17th May 2020, 19:57
If you are not batch processing you can add more audio tracks in the Container Options, it has an audio Tab.
For that I would need more info, ideally on the issue tracker, mediainfo for the input file, command line and mediainfo for the output file.
Added to tracker as requested with everything you said you would need.
https://github.com/staxrip/staxrip/issues/198
I have found a potential work around that seems to work fine. It's updated in the comment section of the tracker.
44vince44
17th May 2020, 21:28
I saw the workaround, well, if it's working, then this is a real solution, not just a "workaround" (and congrats for that).
You seem to have created a profile with it, so it should be very handy, isn't it ?
jlw_4049
17th May 2020, 22:37
I saw the workaround, well, if it's working, then this is a real solution, not just a "workaround" (and congrats for that).
You seem to have created a profile with it, so it should be very handy, isn't it ?
Yes it works perfectly so far. However, it would be nice to have it implemented into the GUI.
and thanks! :)
Atlantis
18th May 2020, 03:14
This DTS-HDMA / DTS-HD to DTS core was something I mentioned some pages ago. I suggested if it is possible the best place is when the demux window opens.
So the term reduce is not correct, extract is better. MakeMKV or MeGUI can do this. At the very beginning, instead of demuxing DTS-HDMA, would be great to demux only the DTS core.
You do it with eac3to and the option -core.
jlw_4049
18th May 2020, 06:10
This DTS-HDMA / DTS-HD to DTS core was something I mentioned some pages ago. I suggested if it is possible the best place is when the demux window opens.
So the term reduce is not correct, extract is better. MakeMKV or MeGUI can do this. At the very beginning, instead of demuxing DTS-HDMA, would be great to demux only the DTS core.
You do it with eac3to and the option -core.
I knew there was a way to do it with eac3to. I generally try to stay away from using eac3to where I can, since it hasn't had support in many years. I do most of the work that I can with mkvmerge/ffmpeg.
With that said I would like this feature. My work around that I posted earlier does work though.
44vince44
18th May 2020, 09:44
@jlw_4049 this is a great find. The logic of the UI makes it difficult to to create an option to check/uncheck such option in the "Audio Settings" (the standard audio settings window related to an encoder) because as you can see, this "Audio Settings" is for decode>encode operations, where a decoding operation has to take place. So there is no way that the DTS Core extraction option could fit in that window since when extracting DTS core, there is no decoding taking place.
I guess what you found here is the only way it can work.
Maybe @Stax76 can integrate that profile you created in the default profiles, since this operation is very much used !
I have a question: I was wondering why you put wav as file type, shouldn,t it be dts? or it simply doesn't matter because it doesn't affect the script in any way.
44vince44
18th May 2020, 09:47
And you shouldn't say "workaround" ;-)))) because it is not a workaround, it is a REAL solution, created with the regular options in Staxrip. Staxrip is designed to be customizable, so what you did is simply add a new feature.
Please @Stax76 if you are reading this, consider updating the default audio profiles with that new one!! Thanks for both of you!
jlw_4049
18th May 2020, 13:12
@jlw_4049 this is a great find. The logic of the UI makes it difficult to to create an option to check/uncheck such option in the "Audio Settings" (the standard audio settings window related to an encoder) because as you can see, this "Audio Settings" is for decode>encode operations, where a decoding operation has to take place. So there is no way that the DTS Core extraction option could fit in that window since when extracting DTS core, there is no decoding taking place.
I guess what you found here is the only way it can work.
Maybe @Stax76 can integrate that profile you created in the default profiles, since this operation is very much used !
I have a question: I was wondering why you put wav as file type, shouldn,t it be dts? or it simply doesn't matter because it doesn't affect the script in any way.
If you don't put wav the audio "encode" actually will error out. I'll explain further.
Decoding (extracting the core is technically the proper term for this) a dtshd file to a .wav file is correct. As far as I know that's how ffmpeg and mkvmerge does it, they just do it without a two step process, it does the same thing with 1 command. You just never actually see the .wav file being extracted.
(Someone can correct me if I'm wrong)
If you use some older programs to manually do it, it goes to a .wav first then back to the dts core. Maybe if stax76 implements this it'll work in one step.
He can add it in the audio options correctly and he will be able to add it in the demux window when you do a manual work flow. An option like reduce to core similiar to mkvtoolnix would work great. (The audio profile could work both with ffmpeg and eac3to, the later isn't updated ever so i never use it, the demux section could use mkvmerge) it could even be done in the final muxing stage with mkvmerge
Until then my custom profile works perfectly
Stax76 is pretty good at keeping up with this and responding. I wish I knew how to do more then write scripts.
I'm glad it worked out for you Vince!
Sent from my Pixel 3a using Tapatalk
44vince44
18th May 2020, 13:49
@jlw_4049, I am doing tests to confirm several things, trying to tweak, and this whole work revealed missing features in the command line edit window:
Working of course on the ffmpeg solution
1) .dts is a known and valid extension for dts streams that are unpadded, and it should be used here (wav has no meaning unless you are preparing your stream to be burned on an audio DTS CD)
unpadded streams (dts, ac3 etc) are the proper streams used by ffmpeg and all encoders/decoders/muxers. Wav has nothing to do here, except if you intend to burn a cd.
TEST CONFIRMATION : Successful, so you should put dts instead of wav (it didn't crash nor fail)
2) In the command line, you must not have this: -disposition:a default -metadata:s:a language=eng
those have no effect at this stage. you can select the language in the drop down box "language".
currently you can set language with this drop-down, but you can't select if default of forced track. And this is the missing feature (you can try it, use -metadata:s:a language=fre or ara of whatever, you'll see the resulting file will not carry this info. Also -disposition:a default will have no effect, you won't have the default status, check it with mediainfo).
This is the output-file mediainfo audio section:
Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 49 s 56 ms
Bit rate mode : Constant
Bit rate : 1 509 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 8.82 MiB (62%)
Language : English
Default : No
Forced : No
and this is the original before processing
ID : 2
Format : DTS XLL
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Codec ID : A_DTS
Duration : 49 s 56 ms
Bit rate mode : Variable
Channel(s) : 6 channels
Channel(s)_Original : 8 channels
ChannelLayout_Original : C L R LFE Lsr Rsr Lss Rss
Sampling rate : 96.0 kHz
Frame rate : 187.500 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossless
Language : English
Default : Yes
Forced : No
Duration_Source : General_Duration
3) The way you've done it and I've re-done it is already a one step, I don't undertsand what we need more, except that it is should be a default profile, and that the missing features are added for the command line window: missing features are : default and forced statuses.
jlw_4049
18th May 2020, 14:12
@jlw_4049, I am doing tests to confirm several things, trying to tweak, and this whole work revealed missing features in the command line edit window:
Working of course on the ffmpeg solution
1) .dts is a known and valid extension for dts streams that are unpadded, and it should be used here (wav has no meaning unless you are preparing your stream to be burned on an audio DTS CD)
unpadded streams (dts, ac3 etc) are the proper streams used by ffmpeg and all encoders/decoders/muxers. Wav has nothing to do here, except if you intend to burn a cd.
TEST CONFIRMATION : Successful, so you should put dts instead of wav (it didn't crash nor fail)
2) In the command line, you must not have this: -disposition:a default -metadata:s:a language=eng
those have no effect at this stage. you can select the language in the drop down box "language".
currently you can set language with this drop-down, but you can't select if default of forced track. And this is the missing feature (you can try it, use -metadata:s:a language=fre or ara of whatever, you'll see the resulting file will not carry this info. Also -disposition:a default will have no effect, you won't have the default status, check it with mediainfo).
This is the output-file mediainfo audio section:
Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 49 s 56 ms
Bit rate mode : Constant
Bit rate : 1 509 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 8.82 MiB (62%)
Language : English
Default : No
Forced : No
and this is the original before processing
ID : 2
Format : DTS XLL
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Codec ID : A_DTS
Duration : 49 s 56 ms
Bit rate mode : Variable
Channel(s) : 6 channels
Channel(s)_Original : 8 channels
ChannelLayout_Original : C L R LFE Lsr Rsr Lss Rss
Sampling rate : 96.0 kHz
Frame rate : 187.500 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossless
Language : English
Default : Yes
Forced : No
Duration_Source : General_Duration
3) The way you've done it and I've re-done it is already a one step, I don't undertsand what we need more, except that it is should be a default profile, and that the missing features are added for the command line window: missing features are : default and forced statuses.I'll do some more testing when I get back to my computer in a little bit.
However in the meantime try disposition:a:0 default
And
-metadata:s:a:0 language=eng
And tell me if that works.
Sent from my Pixel 3a using Tapatalk
44vince44
18th May 2020, 14:26
I just tried it, it is in my previous post, see by yourself
Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 49 s 56 ms
Bit rate mode : Constant
Bit rate : 1 509 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 8.82 MiB (62%)
Language : English
Default : No
Forced : No
So "disposition:a:0 default " doesn't work as you can see above, and there is no way it can work at this stage because this is metadata for the container. Here we are at a stream level.
and neither -metadata:s:a:0 language=eng will work for the same reason! Language is passed through to muxer from the value you've selected in the Language box.
I made a new bug report so that we can have default and Forced flags selection checkboxes, as it is in all other audio edit settings.
jlw_4049
18th May 2020, 16:15
I just tried it, it is in my previous post, see by yourself
Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 49 s 56 ms
Bit rate mode : Constant
Bit rate : 1 509 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 8.82 MiB (62%)
Language : English
Default : No
Forced : No
So "disposition:a:0 default " doesn't work as you can see above, and there is no way it can work at this stage because this is metadata for the container. Here we are at a stream level.
and neither -metadata:s:a:0 language=eng will work for the same reason! Language is passed through to muxer from the value you've selected in the Language box.
I made a new bug report so that we can have default and Forced flags selection checkboxes, as it is in all other audio edit settings.That makes perfect sense. I didn't think about it that way.
Grab latest BETA here
https://staxrip.readthedocs.io/introduction.html#beta
Sent from my Pixel 3a using Tapatalk
stax76
18th May 2020, 17:11
There is a new beta that addresses some issues (announced in the other staxrip thread (https://forum.doom9.org/showthread.php?t=172068&page=171)).
jlw_4049
18th May 2020, 17:12
There is a new beta that addresses some issues (announced in the other staxrip thread (https://forum.doom9.org/showthread.php?t=172068&page=171)).
wooow! I didn't know there was another staxrip thread haha. So should we take all discussions about staxrip over there then?
stax76
18th May 2020, 17:20
Problem with this thread is, first post don't point to https://github.com/staxrip/staxrip
colinhunt
18th May 2020, 17:23
@colinhunt
2.1.1.3 is portable, I've not installed avisynth or fftw, tried all your configuration and it worked fine.
Okay. Well, here Prores export worked only after I installed Avisynth. I dunno what else to tell you. But it works now, so all's well that ends well, yeah?
jlw_4049
18th May 2020, 17:25
Problem with this thread is, first post don't point to https://github.com/staxrip/staxripI will take my discussion over there from now on. Thanks sir!
Sent from my Pixel 3a using Tapatalk
colinhunt
18th May 2020, 17:47
A lot of AVISynth filters perform really well when using PreFetch. Look through the menus and for the MT Mode stuff and you should find the option to set the number of threads (that's the prefetch). If you have 8 threads on your CPU, try setting PreFetch to 4, or 6, or even 8. You can really get a remarkable speed bump this way.
One note: I have an AMD 3950X with 16 cores / 32 threads. I found the sweet spot to be between 12 and 16 threads when using X265. Just because you have a lot of threads does not mean you will get a speed bump beyond a certain point.
Thanks, I'll look into PreFetch/MT stuff!
44vince44
18th May 2020, 19:37
@Patman, I see you have now separate builds for AVX and AVX2. Didn't the "regular" builds check for available instruction sets on your hardware and use them ?
44vince44
18th May 2020, 19:48
and btw @Patman, I saw also you have compiled ffmpeg with gcc10, that must have been quite some work !!! Thanks !!!
44vince44
18th May 2020, 19:49
wooow! I didn't know there was another staxrip thread haha. So should we take all discussions about staxrip over there then?
Well it's better to discuss things here, and report bugs there...
jlw_4049
18th May 2020, 21:04
I will take my discussion over there from now on. Thanks sir!
Sent from my Pixel 3a using TapatalkI mean this thread is Ravens and the other is the official staxrip thread.
But yes I know what you mean
Sent from my Pixel 3a using Tapatalk
Patman
18th May 2020, 21:52
@Patman, I see you have now separate builds for AVX and AVX2. Didn't the "regular" builds check for available instruction sets on your hardware and use them ?
Hi vince,
the regular builds check for available instructions and use them. It was a request ;)
Arkana
19th May 2020, 00:40
@Arkana
Which GPU is in use?
I'm using Windows server. Seems like no dedicated GPU at all
44vince44
19th May 2020, 07:27
Hi vince,
the regular builds check for available instructions and use them. It was a request ;)
Thanks Patman, so please confirm, if my processor is AVX2, If I use the regular M build GCC11, and the "AVX2" M build GCC11, the performance and result is the same ? Please confirm !
And again thanks for everything.:thanks:
(BTW I'm new here, but the same Vince at github)
JKyle
19th May 2020, 07:35
@Patman
It seems like your build of FFmpeg, ffmpeg-N-97806-g883c48190f-g1ead7ed5bf-gcc10.1.7z has a problem with a text file input that's encoded in UTF-8, CR/LF(Windows).
In order to concatenate two wmv files into one mkv, I made the following txt file named mylist.txt (UTF-8, CR/LF):
file 'test 1.wmv'
file 'test 2.wmv'
Then I ran the following command to join those two wmv files:
(Windows 10 x64 2004)
ffmpeg -hide_banner -f concat -safe 0 -i mylist.txt -c copy -y 'test.mkv'
But your FFmpeg binary yields this error message:
[concat @ 00000147d0463300] Impossible to open 'mtest 1.wmv'
mylist.txt: No such file or directory
On the other hand, Zeranoe's build (4.2.2 static) runs OK.
I can't figure out why there's an unnecessary letter m in the filename in the error message.
My guess is that maybe it's related to the text encoding method your ffmpeg binary employs when it takes the text input file.
Any idea?
stax76
19th May 2020, 08:52
@Patman
JKyle uses CP 949 if I remember right.
I'm using Windows server. Seems like no dedicated GPU at all.
KNLMeansCL uses OpenCL which your system probably don't support due to lack of GPU driver.
Arkana
19th May 2020, 10:00
@Patman
JKyle uses CP 949 if I remember right.
KNLMeansCL uses OpenCL which your system probably don't support due to lack of GPU driver.
any suggestion for denoise filter on windows server?
SaboraPie
19th May 2020, 13:36
Hi!! a bug opening in Video Comparison:
---------------------------- System Environment ----------------------------
StaxRip : 2.1.1.4
Windows : Windows 10 Pro 1809
Language : Spanish (Spain, International Sort)
CPU : Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz
GPU : NVIDIA GeForce GTX 670
Resolution : 1920 x 1200
DPI : 96
-------------------------------- Exception --------------------------------
System.OverflowException: La operación aritmética ha provocado un desbordamiento.
en StaxRip.VideoComparisonForm.VideoTab.Draw() en D:\Projekte\VB\staxrip\Forms\VideoComparisonForm.vb:línea 342
en StaxRip.VideoComparisonForm.VideoTab.OnPaint(PaintEventArgs e) en D:\Projekte\VB\staxrip\Forms\VideoComparisonForm.vb:línea 409
en System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
en System.Windows.Forms.Control.WmPaint(Message& m)
en System.Windows.Forms.Control.WndProc(Message& m)
en System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
44vince44
19th May 2020, 15:39
any suggestion for denoise filter on windows server?
did you try DFTTEST it's one of the most popular denoisers.
Khun_Doug
19th May 2020, 15:49
any suggestion for denoise filter on windows server?
It depends on the type of noise you want to remove. Is this an SD or HD source? Old movie that has been digitized? B&W or color?
Take a look at SMDegrain and mClean.
JKyle
19th May 2020, 16:02
@Patman
JKyle uses CP 949 if I remember right.
Thanks for remembering, but after talking with you about mpv/mpv.net failing to read a non-single-byte language named avs file on a non-UTF8 codepage system, I changed the codepage to UTF8 (https://forum.doom9.org/showpost.php?p=1903673&postcount=1496).
PS D:\Work\temp\test> Get-Culture; Get-UICulture; Get-WinSystemLocale; Get-WinDefaultInputMethodOverride; [Text.Encoding]::Default | select EncodingName,CodePage
LCID Name DisplayName
---- ---- -----------
1033 en-US English (United States)
1033 en-US English (United States)
1042 ko-KR Korean (Korea)
InputMethodTip : 0412:{A028AE76-01B1-46C2-99C4-ACD9858AE02F}{B5FE1F02-D5F2-4445-9C03-C568F23C99A1}
Description : Korean (Korea) - Microsoft IME
EncodingName : Unicode (UTF-8)
CodePage : 65001
:)
Patman
20th May 2020, 15:34
@Patman
...
Any idea?
Please download the new version, an error occurred while compiling :scared:
Arkana
20th May 2020, 15:53
did you try DFTTEST it's one of the most popular denoisers.
thanks, will give it a try
It depends on the type of noise you want to remove. Is this an SD or HD source? Old movie that has been digitized? B&W or color?
Take a look at SMDegrain and mClean.
for video like this
https://images2.imgbox.com/1e/69/3sZtnC03_o.jpg
JKyle
20th May 2020, 17:36
Please download the new version, an error occurred while compiling :scared:
You mean ffmpeg-N-97833-gc94550eb31-gb707abf091-gcc10.1.0.7z, right?
Unfortunately, ffmpeg.exe does not return anything this time.
For example, even the simplest command in the unarchived folder
.\ffmpeg.exe -version
returns nothing.
Patman
20th May 2020, 18:28
You mean ffmpeg-N-97833-gc94550eb31-gb707abf091-gcc10.1.0.7z, right?
Unfortunately, ffmpeg.exe does not return anything this time.
...
returns nothing.
ffmpeg-N-97833-gc94550eb31-gb707abf091-gcc10.1.0.7z is correct, but it's strange that your command gave no feedback... i got following feedback with the downloaded version
C:\Windows\system32>C:\Users\PATRIC~1\AppData\Local\Temp\Rar$DRa1344.14723\ffmpeg.exe -version
ffmpeg version N-97833-gc94550eb31-gb707abf091+3 Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 10.1.0 (Rev2, Built by MSYS2 project)
configuration: --cc='ccache gcc' --cxx='ccache g++' --disable-autodetect --enable-amf --enable-bzlib --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --enable-ffnvcodec --enable-nvdec --enable-cuda-llvm --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libdav1d --enable-libaom --disable-debug --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmfx --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwavpack --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-gpl --enable-avisynth --enable-libxvid --enable-libopenmpt --enable-version3 --enable-libsvthevc --enable-openal --enable-vapoursynth --enable-opencl --enable-opengl --enable-openssl --extra-cflags=-DLIBTWOLAME_STATIC --extra-libs=-lstdc++ --extra-cflags=-DLIBXML_STATIC --extra-libs=-liconv --enable-nonfree
libavutil 56. 46.100 / 56. 46.100
libavcodec 58. 84.100 / 58. 84.100
libavformat 58. 43.100 / 58. 43.100
libavdevice 58. 9.103 / 58. 9.103
libavfilter 7. 81.100 / 7. 81.100
libswscale 5. 6.101 / 5. 6.101
libswresample 3. 6.100 / 3. 6.100
libpostproc 55. 6.100 / 55. 6.100
stax76
20th May 2020, 18:35
Thanks for remembering, but after talking with you about mpv/mpv.net failing to read a non-single-byte language named avs file on a non-UTF8 codepage system, I changed the codepage to UTF8.
I find the topic text encoding difficult but interesting and important. Regarding this avisynth issue I found something (https://www.reddit.com/r/programming/comments/7cfftq/wm4_talks_about_c_locales/) few days ago that is somehow related.
JKyle
20th May 2020, 19:49
ffmpeg-N-97833-gc94550eb31-gb707abf091-gcc10.1.0.7z is correct, but it's strange that your command gave no feedback... i got following feedback with the downloaded version
Well, it's pretty weird.
I re-downloaded the file, but I still get the same result: no return.
Maybe we need someone else's help about this.
Can anyone join us and test it please?
The file is here (http://www.mediafire.com/file/nbg5tz1xhtc353v/ffmpeg-N-97833-gc94550eb31-gb707abf091-gcc10.1.0.7z/file).
44vince44
20th May 2020, 21:30
Well, it's pretty weird.
I re-downloaded the file, but I still get the same result: no return.
Maybe we need someone else's help about this.
Can anyone join us and test it please?
The file is here (http://www.mediafire.com/file/nbg5tz1xhtc353v/ffmpeg-N-97833-gc94550eb31-gb707abf091-gcc10.1.0.7z/file).
Just tested ffmpeg.exe -version, i get the error:
The code execution cannot proceed because libbrotlidec.dll was not found. Reinstalling the program may fix this problem.
JKyle
20th May 2020, 21:47
Just tested ffmpeg.exe -version, i get the error:
The code execution cannot proceed because libbrotlidec.dll was not found. Reinstalling the program may fix this problem.
Well, AFAIK, libbrotlidec.dll is a Brotli compression library included in mingw64 / MSYS2. (Here (https://packages.msys2.org/package/mingw-w64-x86_64-brotli).)
I guess there was something wrong in the course of making ffmpeg static. (Not sure though.)
If I do more guesswork, I think it's related to MSYS2 and GCC 10.1.0.
:thanks:
44vince44
20th May 2020, 21:50
Well, AFAIK, libbrotlidec.dll is a Brotli compression library included in mingw64 / MSYS2. (Here (https://packages.msys2.org/package/mingw-w64-x86_64-brotli).)
I guess there was something wrong in the course of making ffmpeg static. (Not sure though.)
:thanks:
Indeed, there shouldn't be such depencies !
and you're welcome :-)
44vince44
20th May 2020, 21:59
Then, copying libbrotlidec.dll next to ffmeg.exe generates another error: libbrotlicommon.dll is missing.
Copying that one fixes the problem and i get the following output:
C:\Program Files\StaxRip\Apps\Encoders\ffmpeg>ffmpeg -version
ffmpeg version N-97833-gc94550eb31-gb707abf091+3 Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 10.1.0 (Rev2, Built by MSYS2 project)
configuration: --cc='ccache gcc' --cxx='ccache g++' --disable-autodetect --enable-amf --enable-bzlib --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --enable-ffnvcodec --enable-nvdec --enable-cuda-llvm --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libdav1d --enable-libaom --disable-debug --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmfx --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwavpack --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-gpl --enable-avisynth --enable-libxvid --enable-libopenmpt --enable-version3 --enable-libsvthevc --enable-openal --enable-vapoursynth --enable-opencl --enable-opengl --enable-openssl --extra-cflags=-DLIBTWOLAME_STATIC --extra-libs=-lstdc++ --extra-cflags=-DLIBXML_STATIC --extra-libs=-liconv --enable-nonfree
libavutil 56. 46.100 / 56. 46.100
libavcodec 58. 84.100 / 58. 84.100
libavformat 58. 43.100 / 58. 43.100
libavdevice 58. 9.103 / 58. 9.103
libavfilter 7. 81.100 / 7. 81.100
libswscale 5. 6.101 / 5. 6.101
libswresample 3. 6.100 / 3. 6.100
libpostproc 55. 6.100 / 55. 6.100
Atlantis
21st May 2020, 00:10
AviSynth+ 3.6.0 (https://github.com/AviSynth/AviSynthPlus/releases)
hello i have a problem everything else works fine with vapoursynth but when i give files as file batch it crashes so i have to give every single file one after another. is there any fix for this?
stax76
21st May 2020, 11:36
hello i have a problem everything else works fine with vapoursynth but when i give files as file batch it crashes so i have to give every single file one after another. is there any fix for this?
If it's not the last beta then please try the last beta.
mcjordan
21st May 2020, 19:41
Stax, do you plan to update the FrameServer generally to AviSynth headers interface V8 ?
There are a huge list of plugins that which are already in line with it or are in the process of the adapting.
Later I will publish what I have followed so far.
stax76
21st May 2020, 20:39
Stax, do you plan to update the FrameServer generally to AviSynth headers interface V8 ?
There are a huge list of plugins that which are already in line with it or are in the process of the adapting.
Later I will publish what I have followed so far.
I don't know if I should but can ask an avisynth dev.
Has anybody tried AviSynth+ 3.6.0, QTGMC working?
mcjordan
21st May 2020, 20:46
Not yet, but maybe later. I'm terribly tired, I'll continue tomorrow morning. Excuse me, Stax.
stax76
21st May 2020, 20:58
Have a good night.
Patman
22nd May 2020, 09:18
FFMPEG issue
I reinstalled msys2 and compiled ffmpeg again. Now it works without problems. Give it a try.
Patman
22nd May 2020, 09:37
I don't know if I should but can ask an avisynth dev.
Has anybody tried AviSynth+ 3.6.0, QTGMC working?
Have a look here (https://forum.doom9.org/showthread.php?p=1913013#post1913013)
JKyle
22nd May 2020, 11:04
I reinstalled msys2 and compiled ffmpeg again. Now it works without problems. Give it a try.
Super! The text input error is also gone.
:thanks:
mcjordan
22nd May 2020, 19:26
DirectN library have an update - 1.90
Changelog: Updated with Windows SDK 19041
colinhunt
23rd May 2020, 11:58
A bit of a mystery here, would appreciate any advice on how to solve.
StaxRip 2.1.1.4 on two PCs, both AMD Zen CPUs, both with Nvidia GPUs (1080Ti & 2080 Super). Both running same version of Win10, AviSynth+ and other dependencies as far as I can tell.
When I drop a file in StaxRip and try to set MCTemporalDenoise (Avisynth), the 1080Ti one has no problem, but the 2080 Super one says this:
"Cannot load file 'C:/Users/xxxxxx/Desktop/videotools/Stax2114/Apps/Plugins/AVS/FFT3DGPU/FFT3dGPU.dll' Platform returned code 126: the specified module could not be found.
But the .dll is definitely in that directory. I can't figure out why this is happening or how to fix it.
mcjordan
23rd May 2020, 14:08
NVEncC 5.0.2 is out
https://github.com/rigaya/NVEnc/releases/tag/5.02
Khun_Doug
23rd May 2020, 15:45
A bit of a mystery here, would appreciate any advice on how to solve.
StaxRip 2.1.1.4 on two PCs, both AMD Zen CPUs, both with Nvidia GPUs (1080Ti & 2080 Super). Both running same version of Win10, AviSynth+ and other dependencies as far as I can tell.
"Cannot load file 'C:/Users/xxxxxx/Desktop/videotools/Stax2114/Apps/Plugins/AVS/FFT3DGPU/FFT3dGPU.dll' Platform returned code 126: the specified module could not be found.
But the .dll is definitely in that directory. I can't figure out why this is happening or how to fix it.
One thing that you can check is what MS Visual C libraries are installed on each machine. It is possible that there is a dependency and the machine with the 2080 Super doesn't have something installed that the 1080 machine does.
-QfG-
24th May 2020, 02:59
Is there no more DGIndexNV Support in the newest BETA?
Atlantis
24th May 2020, 19:49
Has anybody re-encoded iphone videos? I get this error
-------------------------- System Environment --------------------------
StaxRip : 2.0.8.0
Windows : Windows 10 Pro 1909
Language : English (United States)
CPU : Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
GPU : NVIDIA GeForce GTX 980 Ti
Resolution : 3840 x 2160
DPI : 168
------------------------ MediaInfo Source File ------------------------
Z:\Media\Video\Making\QVPI0471.MP4
General
Complete name : Z:\Media\Video\Making\QVPI0471.MP4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (isom/mp41/mp42)
File size : 92.5 MiB
Duration : 12 s 672 ms
Overall bit rate : 61.2 Mb/s
Encoded date : UTC 2020-05-24 18:09:26
Tagged date : UTC 2020-05-24 18:09:39
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main@L5.1@High
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 12 s 672 ms
Source duration : 12 s 835 ms
Bit rate : 60.6 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 60.000 FPS
Minimum frame rate : 54.545 FPS
Maximum frame rate : 60.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Bits/(Pixel*Frame) : 0.122
Stream size : 91.5 MiB (99%)
Source stream size : 92.4 MiB (100%)
Title : Core Media Video
Encoded date : UTC 2020-05-24 18:09:26
Tagged date : UTC 2020-05-24 18:09:39
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : hvcC
Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 12 s 671 ms
Source duration : 12 s 864 ms
Bit rate mode : Constant
Bit rate : 48.0 kb/s
Nominal bit rate : 64.0 kb/s
Channel(s) : 1 channel
Channel layout : C
Sampling rate : 44.1 kHz
Frame rate : 43.066 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 76.9 KiB (0%)
Source stream size : 78.2 KiB (0%)
Title : Core Media Audio
Encoded date : UTC 2020-05-24 18:09:26
Tagged date : UTC 2020-05-24 18:09:39
--------------------------- AviSynth Script ---------------------------
LoadPlugin("Z:\Data\Portable Apps\Video\StaxRip\Apps\Plugins\Dual\L-SMASH-Works\LSMASHSource.dll")
LSMASHVideoSource("Z:\Media\Video\Making\QVPI0471.MP4")
#AssumeFPS(25)
---------------------- Source Script Information ----------------------
Width : 3840
Height : 2160
Frames : 770
Time : 20:25:05.000
Framerate : 0.0001075 (2/18593)
Format : YUV420P8
---------------------- Target Script Information ----------------------
Width : 3840
Height : 2160
Frames : 770
Time : 20:25:05.000
Framerate : 0.0001075 (2/18593)
Format : YUV420P8
- Error Video encoding using x265 3.3+10-g08d895bb6 GCC 10.0.1 Patman -
Video encoding using x265 3.3+10-g08d895bb6 GCC 10.0.1 Patman failed with exit code: 1 (0x1)
It's unclear what the exit code means, in case it's a Windows system error then it possibly means:
Incorrect function
---- Video encoding using x265 3.3+10-g08d895bb6 GCC 10.0.1 Patman ----
"Z:\Data\Portable Apps\Video\StaxRip\Apps\Support\avs2pipemod\avs2pipemod64.exe" -y4mp "Z:\Media\Video\Making\QVPI0471_temp\QVPI0471 new.avs" | "Z:\Data\Portable Apps\Video\StaxRip\Apps\Encoders\x265\x265.exe" --crf 21 --output-depth 10 --colorprim bt709 --colormatrix bt709 --transfer bt709 --range limited --frames 770 --y4m --output "Z:\Media\Video\Making\QVPI0471_temp\QVPI0471 new_out.hevc" -
[sgpd] box has more bytes than expected: 60
[sgpd] box has more bytes than expected: 2
[sgpd] box has more bytes than expected: 4
avs2pipemod[info]: writing 770 frames of 2/18593 fps, 3840x2160,
sar 0:0, YUV-420-planar-8bit progressive video.
x265 [error]: unable to open input file <->
avs2pipemod[info]: finished, wrote 0 frames [0%].
avs2pipemod[info]: total elapsed time is 0.351 sec.
avs2pipemod[error]: only wrote 0 of 770 frames.
---- Video encoding using x265 3.3+10-g08d895bb6 GCC 10.0.1 Patman ----
"Z:\Data\Portable Apps\Video\StaxRip\Apps\Support\avs2pipemod\avs2pipemod64.exe" -y4mp "Z:\Media\Video\Making\QVPI0471_temp\QVPI0471 new.avs" | "Z:\Data\Portable Apps\Video\StaxRip\Apps\Encoders\x265\x265.exe" --crf 21 --output-depth 10 --colorprim bt709 --colormatrix bt709 --transfer bt709 --range limited --frames 770 --y4m --output "Z:\Media\Video\Making\QVPI0471_temp\QVPI0471 new_out.hevc" -
[sgpd] box has more bytes than expected: 60
[sgpd] box has more bytes than expected: 2
[sgpd] box has more bytes than expected: 4
avs2pipemod[info]: writing 770 frames of 2/18593 fps, 3840x2160,
sar 0:0, YUV-420-planar-8bit progressive video.
x265 [error]: unable to open input file <->
avs2pipemod[info]: finished, wrote 0 frames [0%].
avs2pipemod[info]: total elapsed time is 0.351 sec.
avs2pipemod[error]: only wrote 0 of 770 frames.
Start: 8:41:11 PM
End: 8:41:12 PM
Duration: 00:00:01
Any idea? [sgpd] box has more bytes than expected?
Atlantis
24th May 2020, 19:58
I noticed, it is not indexing the file?
stax76
24th May 2020, 20:16
LSMASHVideoSource only supports .mp4 and it's an index free source filter because the container format allows that.
---------------------- Target Script Information ----------------------
Width : 3840
Height : 2160
Frames : 770
Time : 20:25:05.000
Framerate : 0.0001075 (2/18593)
Format : YUV420P8
videoh
24th May 2020, 20:23
Is there no more DGIndexNV Support in the newest BETA? It's not hard-wired in anymore, which is a reasonable decision. You can still use DGDecNV but you have to jump through a hoop or two. No big deal. It's been addressed here and a search should help you along.
Atlantis
24th May 2020, 20:39
---------------------- Target Script Information ----------------------
Width : 3840
Height : 2160
Frames : 770
Time : 20:25:05.000
Framerate : 0.0001075 (2/18593)
Format : YUV420P8
So what's the problem? What should I do? It's video shot by iPhone 11 Pro. It's detecting the framerate incorrectly it seems.
stax76
24th May 2020, 21:28
It also says:
Frame rate mode : Variable
Frame rate : 60.000 FPS
Minimum frame rate : 54.545 FPS
Maximum frame rate : 60.000 FPS
It's not something I know much or have interest, I hope somebody else can help, maybe ask in the synth section or better in the l-smash support thread.
Atlantis
25th May 2020, 00:17
Yes, it is the LSMASHVideoSource reader. Maybe it is good after all to index!
I put the file in an mkv container and now it encodes without any error.
JKyle
25th May 2020, 00:20
As you know, starting with 2.1.0.8, StaxRip stopped supporting DG Tools natively in the app {per the developer's request (X)}.
<= fix: see this post (https://forum.doom9.org/showthread.php?p=1913599#post1913599).
Four tools are affected by this change: DGIndexNV, DGSource, DGTonemap, and DGHDRtoSDR.
Among them, DGIndexNV and DGSource are packaged as DGDecNV (http://rationalqm.us/dgdecnv/dgdecnv.html), which is a non-free program you need to buy for $15.
In this post, I show how to register DGIndexNV and DGSource using the StaxRip macro %startup_dir% (https://staxrip.readthedocs.io/macros.html) assuming that a purchased/licensed copy of DGDecNV is unzipped to a folder somewhere under the app folder which is denoted by the macro %startup_dir%.
Here, I assume DGDecNV folder is %startup_dir%Apps\Support\DGDecNV.
For this setup, you need to launch a new StaxRip window without any project.
1. DGSource
1) Add DGSource in AVS Filters => Profiles
https://i.imgur.com/3Ie27Sp.jpg
Under the [Source] section, add the following lines:
DGSource =
# Setting is changed since 2.1.0.8 after native DG Tools support is dropped.
LoadPlugin("%startup_dir%Apps\Support\DGDecNV\DGDecodeNV.dll")
DGSource("%source_file%")
https://i.imgur.com/SPclIBU.jpg
2) Add DGSource as a source filter
Go to Tools => Settings, and register DGSource as a source filter for dgi.
https://i.imgur.com/NaHbHuW.jpg
For VapourSynth, switch to VapourSynth and repeat similar steps as follows:
https://i.imgur.com/UzDx8od.jpg
https://i.imgur.com/H1vU3NY.jpg
https://i.imgur.com/0ZBxOaX.jpg
DGSource =
# Setting is changed since 2.1.0.8 after native DG Tools support is dropped.
core.std.LoadPlugin(r"%startup_dir%Apps\Support\DGDecNV\DGDecodeNV.dll")
clip = core.dgdecodenv.DGSource(r"%source_file%")
https://i.imgur.com/mjKm3Dk.jpg
2. DGIndexNV
Under Preprocessing in Settings, register DGIndexNV as a command line demuxer.
https://i.imgur.com/H4L3Maa.jpg
You can create 2 types of demuxers with DGIndexNV depending on the input file types.
[Index, No demux]
https://i.imgur.com/myPXRv5.jpg
Arguments:-i %source_files_comma% -o "%source_temp_file%.dgi" -h
Depending on your situation, you may want to add additional Input File Types.
See this (https://forum.doom9.org/showpost.php?p=1913795&postcount=1914).
[Index & Demux]
https://i.imgur.com/1UZsVPZ.jpg
Arguments:-i %source_files_comma% -o "%source_temp_file%.dgi" -a -h
Make sure to put the command that points to DGIndexNV.exe file directly since DGIndexNV is not registered internally under Apps => Manage.
"%startup_dir%Apps\Support\DGDecNV\DGIndexNV.exe"
videoh
25th May 2020, 00:43
per the developer's request. Sorry but that is false. As I mentioned several times, I asked that instead of bundling my binaries that links be provided. Completely removing the dedicated support was stax76's decision.
Nevertheless, thank you for your guide. It will help a lot of people, I hope. :goodpost:
JKyle
25th May 2020, 01:11
Sorry but that is false. As I mentioned several times, I asked that instead of bundling my binaries that links be provided. Completely removing the dedicated support was stax76's decision.
I see. Sorry about the misunderstanding. I fixed the post accordingly.
BTW, I have a question: Are DGTonemap and DGHDRtoSDR free of charge?
My understanding is that they are free to use, but I want to double check.
I'd like to put a post on setting up those two filters in StaxRip after your confirmation.
:thanks:
videoh
25th May 2020, 01:25
Appreciate that! Yes, they are free for end users to use for their personal purposes. Get them from my website to be sure to have latest versions. I hope they are useful and thank you for your work, JKyle. It will help many.
lordalibaski
25th May 2020, 02:25
Hi guys just encountered a small problem now I have just converted one file perfectly fine it has the exact same audio profiles has this one
Format : MPEG-PS
File size : 8.57 GiB
Duration : 2 h 5 min
Overall bit rate mode : Variable
Overall bit rate : 9 812 kb/s
Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings : CustomMatrix / BVOP
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : M=3, N=12
Format settings, picture struc : Frame
Duration : 2 h 5 min
Bit rate mode : Variable
Bit rate : 9 450 kb/s
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 4:3
Frame rate : 25.000 FPS
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.911
Time code of first frame : 00:00:13:11
Time code source : Group of pictures header
GOP, Open/Closed : Closed
Stream size : 8.17 GiB (95%)
Audio
ID : 189 (0xBD)-128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Muxing mode : DVD-Video
Duration : 2 h 5 min
Bit rate mode : Constant
Bit rate : 256 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : -192 ms
Stream size : 229 MiB (3%)
I used the exact same method of encoding, I need to encode it so it will play on a Apple Mac hence the aac setting.
https://i.postimg.cc/597zVrkR/settings.png
I just tried to convert it but got this error
Error Audio encoding 1 using eac3to 3.34 (2.1.1.5)
Audio encoding 1 using eac3to 3.34 returned error exit code: 1 (0x1)
It's unclear what the exit code means, in case it's a Windows system error then it possibly means:
Incorrect function
-------------------- Audio encoding 1 using eac3to 3.34 --------------------
C:\Users\\Desktop\StaxRip\Apps\Audio\eac3to\eac3to.exe "C:\Users\\Desktop\To Convert
\1988 Technics DMC World DJ Finals_temp\1988 Technics DMC World DJ Finals ID1 -192ms.ac3" "C:\
Users\\Desktop\To Convert\1988 Technics DMC World DJ Finals_temp
\1988 Technics DMC World DJ Finals ID1_a1.m4a" -quality=0.4 -192ms -progressnumbers
The format of the source file could not be detected.
StaxRip.ErrorAbortException: Audio encoding 1 using eac3to 3.34 returned error exit code: 1 (0x1)
It's unclear what the exit code means, in case it's a Windows system error then it possibly means:
Incorrect function
-------------------- Audio encoding 1 using eac3to 3.34 --------------------
C:\Users\\Desktop\StaxRip\Apps\Audio\eac3to\eac3to.exe "C:\Users\\Desktop\
To Convert\1988 Technics DMC World DJ Finals_temp\
1988 Technics DMC World DJ Finals ID1 -192ms.ac3" "C:\Users\\Desktop\
To Convert\1988 Technics DMC World DJ Finals_temp\
1988 Technics DMC World DJ Finals ID1_a1.m4a" -quality=0.4 -192ms -progressnumbers
The format of the source file could not be detected.
at StaxRip.Proc.Start() in D:\Projekte\VB\staxrip\General\Proc.vb:line 367
at StaxRip.GUIAudioProfile.Encode() in D:\Projekte\VB\staxrip\General\AudioProfile.vb:line 698
at StaxRip.GlobalClass._Closure$__._Lambda$__41-0() in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 215
at System.Threading.Tasks.Parallel.<>c__DisplayClass4_0.<Invoke>b__0()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at StaxRip.GlobalClass.ProcessJob(String jobPath) in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 256
Any help is appreciated.
lordalibaski
25th May 2020, 02:50
Think I've got it did the same mistake as last time had to change the extension to mpg and it worked fine.
stax76
25th May 2020, 02:51
Re-open the project under:
File > Recent Projects
In the audio settings you can try:
Encoder > qaac
After that override/replace the AAC audio profile to use qaac, it's probably better and should be made the default AAC encoder.
lordalibaski
25th May 2020, 03:12
Cheers mate will try that on my next conversion see if its any better.
Ps...just a small question regarding the actual bitrate of the audio when setting it to encode to aac it always puts it down to AAC 106 kbps, I have just set the encoder now to use qaac like you said what setting should I be setting it on to get the same bitrate as 256 AC3.
I changed it to qaac CBR 256 is that correct?
JKyle
25th May 2020, 04:40
As we can register DGDecNV in StaxRip (>2.1.0.7) using macros (https://forum.doom9.org/showthread.php?p=1913597#post1913597), we can add DGTonemap & DGHDRtoSDR filters in a similar way as follows.
■ Download & unzip the filter files
Download DGTonemap (http://rationalqm.us/DGTonemap.rar) and DGHDRtoSDR (http://rationalqm.us/hdr/DGHDRtoSDR_1.13.rar) from the developer's site.
Make sure to put x64 versions.
DGTonemap supports AviSynth only while DGHDRtoSDR supports both AviSynth and VapourSynth.
For convenience, I assume you put the filters in somewhere under the StaxRip app folder as follows:
%startup_dir%Apps\Plugins\AVS\DGToneMap\
%startup_dir%Apps\Plugins\Dual\DGHDRtoSDR\
Now open an empty StaxRip window and do the following setting.
■ AviSynth filters
Open and edit AVS profiles:
https://i.imgur.com/3Ie27Sp.jpg
<DGTonemap>
Replace/Add the following item related to DGTonemap under the [Color] section:
https://i.imgur.com/Cqrxkco.jpg
HDRCore | Tone Mapping =
# DGTonemap setting is changed since 2.1.0.8 after native DG Tools support is dropped.
LoadPlugin("%startup_dir%Apps\Plugins\AVS\DGToneMap\DGTonemap.dll")
$select:msg:Select the Map Tone You Wish to Use;DGReinhard|DGReinhard();DGHable|DGHable()$
<DGHDRtoSDR>
Replace/Add the following item related to DGHDRtoSDR under the [Color] section:
https://i.imgur.com/DB5lAuV.jpg
DGHDRtoSDR =
# Setting is changed since 2.1.0.8 after native DG Tools support is dropped.
LoadPlugin("%startup_dir%Apps\Plugins\Dual\DGHDRtoSDR\DGHDRtoSDR.dll")
DGHDRtoSDR(mode="$select:msg:Select transfer function;Perceptual Quantizer|pq;Hybrid Log Gamma|hlg$", white=$enter_text:Enter overall brightness in integer (max 3,000 for PQ, max 10,000 for HLG)$)
■ VapourSynth filters
Change the filters type from AviSynth to VapourSynth by clicking Fiter Setup => VapourSynth:
https://i.imgur.com/UzDx8od.jpg
Open and edit VS profiles:
https://i.imgur.com/H1vU3NY.jpg
<DGHDRtoSDR>
Replace/Add the following item related to DGHDRtoSDR under the [Color] section:
https://i.imgur.com/fNPipCt.jpg
DGHDRtoSDR =
# Setting is changed since 2.1.0.8 after native DG Tools support is dropped.
core.std.LoadPlugin(r"%startup_dir%Apps\Plugins\Dual\DGHDRtoSDR\DGHDRtoSDR.dll")
clip = core.dghdrtosdr.DGHDRtoSDR(clip, mode="$select:msg:Select transfer function;Perceptual Quantizer|pq;Hybrid Log Gamma|hlg$", white=$enter_text:Enter overall brightness in integer (max 3,000 for PQ, max 10,000 for HLG)$)
You can edit the profile code by referring to the StaxRip macros document (https://staxrip.readthedocs.io/macros.html).
44vince44
25th May 2020, 16:16
Thanks JKyle, this was very useful !
JKyle
25th May 2020, 22:40
Thanks JKyle, this was very useful !
You're welcome. :)
BTW, I found a syntax error in DGHDRtoSDR VS filter core.std.LoadPlugin call in my original post.
path=
is obsolete. So I replaced it with
r
I've updated the post, so update your code in your app please.
bananenmann
26th May 2020, 01:10
@JKyle
I'm very sorry, but I think I still need your help :(
I exactcly followed your HowTo for registering DGIndexNV and DGSource, verified everything many times, but I always get an error message, when I want to load a Video-file. Here an Example with an MPEG2-File (this worked with Staxrip 2.1.1.2 (Beta), the last Version supporting DGIndexNV):
Script error: There is no function named 'DGSource'.
(D:\Video-Encode\Evanescence - Sweet Sacrifice_temp\Evanescence - Sweet Sacrifice_source.avs, line 1)
DGSource("D:\Video-Encode\Evanescence - Sweet Sacrifice.mpv")
My StaxRip-Folder is located here: C:\Sonstiges\StaxRip-Beta-x64. I copied the DGDecNV-Folder (including 64-Bit-Versions of DGDecodeNV.dll, DGIndexNV.exe and my Licence file) into that directory: C:\Sonstiges\StaxRip-Beta-x64\Apps\Support\
In both created demuxers, the command points to: "%startup_dir%Apps\Support\DGDecNV\DGIndexNV.exe"
I also tried: "C:\Sonstiges\StaxRip-Beta-x64\Apps\Support\DGDecNV\DGIndexNV.exe"
I filled out the rest of the fields with the informations from your Manual.
I added DGSource as a source filter for dgi (Avisynth AND Vapoursynth) and also edited the AVS and VS-Filter-Profiles as described by copying and pasting all the texts from your code boxes to the places where they belong. Afterwards I exited Staxrip, started it again, but I still get that error Message above mentioned. What did I wrong? (Please don't blame on me, I'm new to Staxrip)...
lordalibaski
26th May 2020, 01:28
@ stax
The qaac works brilliant mate thanks for that much easier to do than to change the extension all the time.
Just a question mate I have asked this before about boosting the volume on certain vhs captures I used this command
-af dynaudnorm=p=0.94:m=70:s=22
It works when I'm doing ac3 audio but it doesn't work with qaac can the audio boost be done when converting to qaac?
thanks
JKyle
26th May 2020, 01:52
Here an Example with an MPEG2-File (this worked with Staxrip 2.1.1.2 (Beta), the last Version supporting DGIndexNV):
Script error: There is no function named 'DGSource'.
(D:\Video-Encode\Evanescence - Sweet Sacrifice_temp\Evanescence - Sweet Sacrifice_source.avs, line 1)
DGSource("D:\Video-Encode\Evanescence - Sweet Sacrifice.mpv")
It seems like you didn't include LoadPlugin in avs profiles.
See if this line is missing in DGSource = before calling DGSource("%source_file%")
LoadPlugin("%startup_dir%Apps\Support\DGDecNV\DGDecodeNV.dll")
bananenmann
26th May 2020, 02:25
I put this into the [Source] - Section of my AVS-Filter-Profile:
DGSource =
# Setting is changed since 2.1.0.8 after native DG Tools support is dropped.
LoadPlugin("%startup_dir%Apps\Support\DGDecNV\DGDecodeNV.dll")
DGSource("%source_file%")
And I put this into the [Source] - Section of my VS-Filter-Profile:
DGSource =
# Setting is changed since 2.1.0.8 after native DG Tools support is dropped.
core.std.LoadPlugin(r"%startup_dir%Apps\Support\DGDecNV\DGDecodeNV.dll")
clip = core.dgdecodenv.DGSource(r"%source_file%")
JKyle
26th May 2020, 02:38
This is part of my edited AVS-Profile:
[Source]
Automatic = # can be configured at: Tools > Settings > Source Filters
AviSource = AviSource("%source_file%", audio=false)
DGSource =
LoadPlugin("%startup_dir%Apps\Support\DGDecNV\DGDecodeNV.dll")
DGSource("%source_file%")
.
.
.
LoadPlugin(...) and DGSource(...) should be indented.
Otherwise, DGSource(...) is recognized as a separate item.
bananenmann
26th May 2020, 03:04
Sorry, I pasted it wrong here... they are indented. See my edited post above (#1899) ... That's exactly how it looks like... but I still get the error message. It seems that the DGDecodeNV.dll still isn't loaded. Silly Question: There is no file called DGSource, right? I just need the files DGDecodeNV.dll, DGIndexNV.exe and my own license.txt in the DGDecNV-Folder, is this correct?
Are you shure there is no typing error in your Manual? It's getting late now, maybe we should sleep over one night.
Thank you for your great effort and help. Good night !!!
;)
Arkana
26th May 2020, 03:27
Hello, which parameter should be keep/changed to encode HDR10+
For HDR10 (not plus) is pretty easy, staxrip loads the HDR metadata automatically
but not for HDR10+
JKyle
26th May 2020, 03:55
Sorry, I pasted it wrong here... they are indented. See my edited post above (#1899) ... That's exactly how it looks like... but I still get the error message. It seems that the DGDecodeNV.dll still isn't loaded. Silly Question: There is no file called DGSource, right? I just need the files DGDecodeNV.dll, DGIndexNV.exe and my own license.txt in the DGDecNV-Folder, is this correct?
Are you shure there is no typing error in your Manual?
I'm pretty sure there's no typo in the code of my guide.
I just copy-and-pasted the working code from my app.
Which version are you using? Mine is the latest one, 2.1.1.5.
BTW, did you put blank lines before and after DGSource = section in the profiles? Please double check.
Just for checking, after you finish composing the avs script, can you click Preview Code and copy and paste the code there?
https://i.imgur.com/T99gcFy.jpg
You can see what avs script codes are generated by your AVS profiles.
Make sure LoadPlugin(...) is properly written in the code.
https://i.imgur.com/FdjbOv0.jpg
If not, you need to reinstall StaxRip and related apps, I guess.
JKyle
26th May 2020, 04:10
Hello, which parameter should be keep/changed to encode HDR10+
For HDR10 (not plus) is pretty easy, staxrip loads the HDR metadata automatically
but not for HDR10+
See this post (https://forum.doom9.org/showpost.php?p=1905420&postcount=1584).
JKyle
26th May 2020, 04:36
Just a question mate I have asked this before about boosting the volume on certain vhs captures I used this command
-af dynaudnorm=p=0.94:m=70:s=22
It works when I'm doing ac3 audio but it doesn't work with qaac can the audio boost be done when converting to qaac?
Open the qaac profile:
https://i.imgur.com/oMvFtwI.jpg
Choose Normalize and click More...:
https://i.imgur.com/5kgi0z1.jpg
You can choose ffmpeg Normalize Method there.
https://i.imgur.com/vLs23v9.jpg
This applies when ffmpeg converts audio files or pipelines them to qaac.
And you can choose parameter settings in the submenu:
https://i.imgur.com/iIuuzom.jpg
BTW, in my experience, volumedetect gives the best result by shifting the volume uniformly.
Other methods sometimes give distortion depending on the source audio.
Arkana
26th May 2020, 06:33
See this post (https://forum.doom9.org/showpost.php?p=1905420&postcount=1584).
thanks a lot
lordalibaski
26th May 2020, 15:56
Excellent tut there JKyle thank you.
Edit
@ JKyle
I have tried that twice now mate and there is no improvement in the sound! will tell you what I did
I did the 1st one like you said and clicked normalize then converted which made no difference in the audio, I did this again by unticking normalize and nothing happened.
Though what I have been doing with other files is this
https://i.postimg.cc/hGG23X2Y/custom.png
When I add the command line into the custom it boost the sound without that command it does nothing. Though I have tried that command when I try to do a qaac conversion and it comes up with that error I put up earlier.
JKyle
26th May 2020, 19:25
I did the 1st one like you said and clicked normalize then converted which made no difference in the audio, I did this again by unticking normalize and nothing happened.
Normalize option in qaac puts --normalize switch in its execution in the shell like this:
qaac64.exe --tvbr 62 --delay -0.001 --normalize
And this works like this in qaac encoding:
...
Scanning maximum peak...
4960208/-1 samples processed in 0:00.328
Peak value: 0.535645
...
If nothing happens, that's something related to your source and qaac encoder. Maybe your source audio already has a peak value that doesn't need to be changed. Then you need to do something other than simply shifting the volume to change the peak value. dynaudnorm can be a useful alternative in this case.
Though I have tried that command when I try to do a qaac conversion and it comes up with that error I put up earlier.
Your AC3 encoder profile makes use of ffmpeg as you can see the command line in the bottom.
And it's a matter of course your custom options don't work directly with qaac since dynaudnorm is an ffmpeg only filter.
If you'd like to make use of your favorite dynaudnorm options, you need to either 1) put them in qaac Advanced Audio Options like I showed in the screenshot, or 2) choose ffmpeg instead of qaac as the AAC encoder.
2) will certainly work, but I'm not sure whether 1) will work seamlessly. Check it out yourself.
You need to examine the log file to see how your settings work.
And if normalization does not work, try to find where the dynaudnorm options are missing, and report to @stax76 about this.
lordalibaski
26th May 2020, 20:25
I can't make my mind up if its doing anything or not lol
This video has very poor audio hence me wanting to boost the sound a bit.
Have a listen to this original capture
https://fromsmash.com/Sx_EM8QFUX-bt
This is a conversion using the settings you said
https://fromsmash.com/l1utbSmE5t-bt
I can hear a slight difference but not much. I did 2 the other week testing some settings and you can tell the difference between no boost and boost, check the 2 videos below.
No Boost
https://www.youtube.com/watch?v=WudQY4TSe54
Boost(though it didn't kick in straight away)
https://www.youtube.com/watch?v=Z5piyj8NhmI
JKyle
26th May 2020, 20:54
Have a listen to this original capture
https://fromsmash.com/Sx_EM8QFUX-bt
This is a conversion using the settings you said
https://fromsmash.com/l1utbSmE5t-bt
I can hear a slight difference but not much.
These two are definitely different. I put those two videos in one folder and ran this command in a Command Prompt window:
for %a in (*.*) do ffmpeg -hide_banner -i "%a" -c:v copy -af "volumedetect" -sn -f null NUL 2>> log.txt
And log.txt is like this (https://pastebin.com/tEkYpNUc).
As you can see there, test.vob has
mean_volume: -24.4 dB
max_volume: -10.4 dB
while testaac.mp4 has
mean_volume: -14.0 dB
max_volume: -0.1 dB
Just looking at those two index values, anyone can see that they are very different.
If you really want to edit the spectrum pattern of the audio, you need to use a dedicated audio editing app such as Audacity or Ocenaudio, not a simple audio filter in ffmpeg.
lordalibaski
26th May 2020, 21:05
Do they sound different to yourself mate? the conversion sounds a little bit slightly louder.
I need to get it a bit more but don't know what settings to use this is my main problem, all the settings I try it fails.
This files a bit bigger than the others its the full video but you will notice the difference right away in sound with the ac3 setting.
https://fromsmash.com/ly2sbhNYpj-bt
I've tried different programs mate but the outcome of the video conversion isn't has good quality as Staxrip no idea what it is but for some reason Staxrip is very good at handling old VHS captures.
JKyle
26th May 2020, 21:10
Do they sound different to yourself mate? the conversion sounds a little bit slightly louder.
I need to get it a bit more but don't know what settings to use this is my main problem, all the settings I try it fails.
Yes, testaac.mp4 sounds louder.
If you want to do more, I guess you need to give up batch processing using the same dynaudnorm settings but resort to audio editing programs.
I've tried different programs mate but the outcome of the video conversion isn't has good quality as Staxrip no idea what it is but for some reason Staxrip is very good at handling old VHS captures.
You can edit the audio separately in Audacity or Ocenaudio, and load it in the audio section in StaxRip.
Then encode video but copy/mux audio.
lordalibaski
26th May 2020, 21:18
Yes, testaac.mp4 sounds louder.
If you want to do more, I guess you need to give up batch processing using the same dynaudnorm settings but resort to audio editing programs.
That's good at least you can tell I think I can't tell the difference anymore because I have listened to it that many times my ears have given up trying to hear anything different lol
If it's better even slightly it will do me it's not every video I have this problem with it's only the odd 1 or 2.
Many thanks for your help mate its been much appreciated, and the help as been bookmarked.
bananenmann
26th May 2020, 23:52
@JKyle
I'm trying to register it to the Beta 2.1.1.5 as well.
I started all over again. Deleted the complete Staxrip-Folder (named-StaxRip-Beta-x64), made a new one, just called "StaxRip", copied everything from the Package inside. Then I again made all your Registering things. I dont know why (because the last Time I exactly did the same things, and I copied and pasted everything of your codes, but this time... it still didn't work :rolleyes:. But this time I got a step further. This time it didn't tell me, that "there is a Script error and that there is no function named 'DGSource'". This Time I got this error Message:
--------------------------- Error opening source ---------------------------
DGSource: Invalid index file!
(D:\Video-Encode\Evanescence - Bring Me To Life_temp\Evanescence - Bring Me To Life_source.avs, line 3)
# Setting is changed since 2.1.0.8 after native DG Tools support is dropped.
LoadPlugin("C:\Sonstiges\StaxRip\Apps\Support\DGDecNV\DGDecodeNV.dll")
DGSource("D:\Video-Encode\Evanescence - Bring Me To Life.m2v")
I verified the "Preview Code" Window and now it was correct:
#Setting is changed since 2.1.0.8 after native DG Tools support is dropped.
LoadPlugin("C:\Sonstiges\StaxRip\Apps\Support\DGDecNV\DGDecodeNV.dll")
DGSource()
But the file wasn't indexed!? First I thought I was getting crazy, because I already registered "dgi" to DGSource in Avisynth and Vapoursynth and I was afraid you maybe were thinking that I'm an Idiot. But then I realized, that those MPEG Files I wanted to open already were demuxed (by me, because I've read, that DGIndexNV sometimes has problems with this.). So my File-Types were "mpv" and "m2v". I added them in the Self-Created-Customized Demuxers and:
IT WORKS!!!
FINALLY !!!
Thanks a lot for your Help, now I can go to sleep without headaches!!!
:thanks:
JKyle
27th May 2020, 00:11
But then I realized, that those MPEG Files I wanted to open already were demuxed (by me, because I've read, that DGIndexNV sometimes has problems with this.). So my File-Types were "mpv" and "m2v". I added them in the Self-Created-Customized Demuxers and:
IT WORKS!!!
FINALLY !!!
So it was about registering additional input file types for DGIndexNV.exe, huh?
Good for you! I'll update my guide about this and link it to your case. :)
JKyle
27th May 2020, 20:21
Since qaac fails to encode (with --delay switch) flac files demuxed by mkvextract (see here (https://forum.doom9.org/showthread.php?p=1906349#post1906349)), I wanted to compose an Event Command which chooses qaac profiles adaptively based on source audio codec after the source file is loaded.
However, I've found that there's no such macro as Source Audio Codec by default. So I had to choose Source File Extension instead and compose it like this:
https://i.imgur.com/bel57M0.jpg
But this method has a catch: it switches qaac profiles regardless of source audio codecs.
I guess I can catch audio codec info by calling Get-MediaInfoValue in Get-MediaInfo as follows:
$audioCodec = Get-MediaInfoValue ($args[0]) -Kind Audio -Parameter "Format/String"
But how can I register this parameter as a macro in StaxRip?
※ I know I can avoid this mess if I set the Decoding Method in qaac profiles to Pipe, but I just wanted to use another method. :)
stax76
27th May 2020, 22:29
@JKyle
I've bookmarked it but can't do much at the moment due to lower back pain.
Having a feature freeze now has the advantage of getting a more solid and relaxed stable release.
JKyle
27th May 2020, 22:36
I've bookmarked it but can't do much at the moment due to lower back pain.
I see. Hope you get up and running asap. :)
:thanks:
stax76
27th May 2020, 22:47
Thanks, it's much better already than yesterday where I spent most of the day in bed due to a sudden lower back pain attack, it's called Hexenschuss (witch shot) in Germany, never had this before and don't want to experience it again anytime soon.
jlw_4049
28th May 2020, 02:32
Thanks, it's much better already than yesterday where I spent most of the day in bed due to a sudden lower back pain attack, it's called Hexenschuss (witch shot) in Germany, never had this before and don't want to experience it again anytime soon.Hope you feel better man!
Sent from my SM-G986U1 using Tapatalk
44vince44
28th May 2020, 03:01
Take much care of yourself Stax, I'm glad you feel better now !!
jlw_4049
29th May 2020, 06:13
@Stax76 wanted to post an update on the FFMPEG demux to core. It does not work correctly, it results in an error dropping from 7.1 to 5.1 core.
Here is a logfile.
https://pastebin.com/C9rXVgzP
https://i.imgur.com/W7HywQ1.png
These are the settings that I used. The source was a 7.1, that FFMPEG command will automatically reduce a DTS 7.1 (of any variant) and a DTS 5.1 (of any variant) to DTS 5.1. If the source is a DTS 2.0 of any kind, it will reduce to core but keep the same channels.
I don't know but the channel/sample rate selection should be greyed out if it's effecting the command. I don't know if it is, however, I tried the command by setting the channel to original and 5.1 and both threw an error.
This is running the command manually
https://pastebin.com/XShARNGX
I think it's due to the fact that StaxRip is outputting to a .wav file. I don't know if that's required at all what so ever.
Either way, let me know if you need any more information. Thanks as usual!
JKyle
29th May 2020, 07:43
@Stax76 wanted to post an update on the FFMPEG demux to core. It does not work correctly, it results in an error dropping from 7.1 to 5.1 core.
Have you tried Command Line & Edit?
https://i.imgur.com/0OezRzO.jpg
https://i.imgur.com/TYnwQGY.jpg
jlw_4049
29th May 2020, 07:49
Have you tried Command Line & Edit?
https://i.imgur.com/0OezRzO.jpg
https://i.imgur.com/TYnwQGY.jpgYes i can make my own with the command line in and outside of StaxRip that works.
However stax added this feature to the GUI. Just wanted to update and let him know its not working as intended.
Sent from my SM-G986U1 using Tapatalk
JKyle
29th May 2020, 08:00
Yes i can make my own with the command line in and outside of StaxRip that works.
However stax added this feature to the GUI. Just wanted to update and let him know its not working as intended.
I see. Thanks for the info. :)
jlw_4049
29th May 2020, 08:09
I see. Thanks for the info. :)I appreciate you trying to help though :)
Sent from my SM-G986U1 using Tapatalk
stax76
29th May 2020, 12:19
Take much care of yourself Stax, I'm glad you feel better now !!
Thx
wanted to post an update on the FFMPEG demux to core. It does not work correctly, it results in an error dropping from 7.1 to 5.1 core.
Using the Decoder option by design forces decoding. I changed it now to disable decoding if the Extract DTS Core option is used, both the function and the UI for decoding is disabled, some other UI options like Channels and Sampling Rate are disabled now too if Extract DTS Core is enabled. The Decoder tooltip shows now: Defines which decoder to use and forces decoding even if not necessary.
44vince44
29th May 2020, 12:26
jlw, the problem is that you set ffmpeg as decoder and encoder.
Simply put AUTOMATIC.
Here:
Codec=DTS
Decoder = Automatic
Encoder= Automatic
Channel, Sample rate = original
Atlantis
29th May 2020, 20:17
I noticed not always an audio track name is passed to staxrip, is this normal? Some times it is passed and some times it is not. For example this is not passed
Audio #1
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 1 h 28 min
Bit rate mode : Constant
Bit rate : 1 509 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 951 MiB (12%)
Title : English Feature Mix
Language : English
Default : Yes
Forced : No
jlw_4049
29th May 2020, 23:13
Using the Decoder option by design forces decoding. I changed it now to disable decoding if the Extract DTS Core option is used, both the function and the UI for decoding is disabled, some other UI options like Channels and Sampling Rate are disabled now too if Extract DTS Core is enabled. The Decoder tooltip shows now: Defines which decoder to use and forces decoding even if not necessary.
Thanks again stax! I'm currently testing out latest BETA now.
Also I took your advice and started learning Python :)
JKyle
31st May 2020, 01:13
I set up an Event Command to play a sound after a job or jobs are finished as follows:
https://i.imgur.com/V8DD16A.jpg
It works well on the first run of a job or jobs on the Jobs list.
But when I modify settings of the same project and re-run it without saving, the sound does not play.
Is it something that can be fixed by choosing some other event, or is there any underlying logic that prevents the sound from playing?
Arkana
31st May 2020, 14:11
If you actualy have a mkv remux of video with HDR10+ metadata you must parse it with
HDR10+ parser https://github.com/quietvoid/hdr10plus_parser/releases
You can do it with ffmpeg https://video.stackexchange.com/questions/20495/how-do-i-set-up-and-use-ffmpeg-in-windows
Command in cmd looks like this
ffmpeg -i "C:\video rip\Test.mkv" -c:v copy -vbsf hevc_mp4toannexb -f hevc - | "C:\hdr10plus_parser\hdr10plus_parser.exe" - -o "C:\video rip\Test.json"
ffmpeg -i "This is your video file path and name" -c:v copy -vbsf hevc_mp4toannexb -f hevc - | "this is your parser .exe location and name" - -o "This is your output file location and name"
Now next step is very simple.
http://shrani.si/f/J/7W/43pblryA/hdr10.jpg
I hope this helps.:) If you did all things correct you could see with https://mediaarea.net/en/MediaInfo something like this HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Hi is this correct?
https://i.postimg.cc/rwffkfK8/screenshot-27.png (https://postimages.org/)
SMPTE 2084? Since there's no SMPTE ST 2094 option
jlw_4049
31st May 2020, 14:54
Hi is this correct?
https://i.postimg.cc/rwffkfK8/screenshot-27.png (https://postimages.org/)
SMPTE 2084? Since there's no SMPTE ST 2094 optionIm pretty sure the parsed info file will override that
Sent from my SM-G986U1 using Tapatalk
JKyle
31st May 2020, 15:06
SMPTE 2084? Since there's no SMPTE ST 2094 option
SMPTE ST 2094 is NOT a transfer function, but the dynamic metadata you put as a json file. Among the 4 popular HDR standards, 3(HDR10, HDR10+, Dolby Vision) use PQ(=SMPTE 2084) as the transfer function and only SL-HDR1 uses HLG(Hybrid Log Gamma, ARIB-STD-B67 in x265).
See this Wiki document about HDR (https://en.wikipedia.org/wiki/High-dynamic-range_video).
Arkana
1st June 2020, 06:59
Im pretty sure the parsed info file will override that
Sent from my SM-G986U1 using Tapatalk
SMPTE ST 2094 is NOT a transfer function, but the dynamic metadata you put as a json file. Among the 4 popular HDR standards, 3(HDR10, HDR10+, Dolby Vision) use PQ(=SMPTE 2084) as the transfer function and only SL-HDR1 uses HLG(Hybrid Log Gamma, ARIB-STD-B67 in x265).
See this Wiki document about HDR (https://en.wikipedia.org/wiki/High-dynamic-range_video).
thanks it works
https://i.postimg.cc/21vnXLhT/screenshot-28.png (http://postimg.cc/21vnXLhT)
jlw_4049
1st June 2020, 07:25
thanks it works
https://i.postimg.cc/21vnXLhT/screenshot-28.png (http://postimg.cc/21vnXLhT)No problem [emoji4]
Sent from my SM-G986U1 using Tapatalk
Disturbance
2nd June 2020, 05:08
Hello, I have a question that I would like some clarification on as I am not the most technical minded. When trimming using the preview menu, when I select the start and end frames for trimming it will shift my end frame selection back a frame instead of using the frame I selected for eg:
Trim(2163, 31171) + Trim(33331, 33688)
Trim(2163, 31170) + Trim(33331, 33687)
So instead of the first line which are the frame selections I make, when I close the window it will change it to the second line where the final frames on both clips are moved backwards 1 frame. Is this a normal behaviour? and if so what is the reason for it as I have no idea. I can however after using the preview window manually change that line to the the frames I originally selected and I have tested in the preview window setting the end frame as 1 frame over and when I close the window it pulls it back by a frame to the frame I initially wanted.
Thanks :)
stax76
2nd June 2020, 15:57
Not including the last frame looks like a bug. :o
Disturbance
2nd June 2020, 23:58
Not including the last frame looks like a bug. :o
Ah ok, was not sure if it was something that I was doing wrong, as staxrip has been doing this for as long as I have been using it along all versions (inc 2.0.8.0). If it is a bug, hopefully it is just an easy fix :)
stax76
3rd June 2020, 01:15
Ah ok, was not sure if it was something that I was doing wrong, as staxrip has been doing this for as long as I have been using it along all versions (inc 2.0.8.0). If it is a bug, hopefully it is just an easy fix
It's doing this since the feature exists, about 16 years I would guess. I've fixed it and tested the fix thoroughly.
44vince44
3rd June 2020, 02:02
Well, it is an old convention used in many video tools, that the video range is [start;end[
meaning that last frame is not included.
It is not a bug, it is intentional.
The reason it was made was the keyframes: when you cut between keyframes (which is the case in programs like Virtualdub), you select a range that starts at a keyframe Kb, and ends at Keyframe Ke.
Then the resulting range is [ Kb ; Ke [ Ke is EXCLUDED.
You can cut video and save it without re-encoding.
I don't know if that still has a meaning.
DavidRyan
6th June 2020, 13:37
I was hoping to use staxrip to encode a bunch of frames I have stored as images in a folder. So I made a simple avisynth input script [ ImageSource("Frames%04d.png", 0001, 1199, 24, pixel_type="RGB24") ] to generate a 24fps clip from the desired range of frames and saved it as input.avs in the folder. When opening this in Staxrip it appears to open correctly and I can preview the video, but if I try an x265 encode it errors out complaining of a missing y4m header.
I can open the same script in virtualdub and export an uncompressed AVI which staxrip can encode without any problems. I could also just encode the frames with ffmpeg. But it would be nice if I could open them directly as a clip in staxrip as I was initially attempting, so if anyone has any ideas on how I could best import this frame range into staxrip without running into the y4m header error later I'd appreciate any suggestions.
stax76
6th June 2020, 18:13
Maybe it has something to do with the color format, if you right-click Filters and choose Info, which color format does it show? Maybe try another piping tool, in the x265 dialog search field at the left bottom enter pipe. Or maybe try VapourSynth (Filters > Filter Setup > VapourSynth), the image source filter of VapourSynth is more convenient.
DavidRyan
7th June 2020, 09:44
Maybe it has something to do with the color format, if you right-click Filters and choose Info, which color format does it show? Maybe try another piping tool, in the x265 dialog search field at the left bottom enter pipe. Or maybe try VapourSynth (Filters > Filter Setup > VapourSynth), the image source filter of VapourSynth is more convenient.
Appreciate the suggestions, if I look at info it just says "Format : 1342177281". I tried other piping tools but didn't have any luck, but I'll look into VapourSynth now, been meaning to familiarise myself with it anyway. Guess some research into y4m is in order too. At least I have a workaround of using virtualdub first.
Thanks for the continued development of staxrip which I use all the time.
stax76
7th June 2020, 10:07
Appreciate the suggestions, if I look at info it just says "Format : 1342177281". I tried other piping tools but didn't have any luck, but I'll look into VapourSynth now, been meaning to familiarise myself with it anyway. Guess some research into y4m is in order too. At least I have a workaround of using virtualdub first.
Thanks for the continued development of staxrip which I use all the time.
Format : 1342177281 could mean that staxrip does not understand this format, and maybe the piping tools or encoders don't understand it either, it could still be a valid format, does the preview work? The preview does a format conversion. Maybe you just need to make a format conversion. There are more ways to show the color format, and they might work better than my relative simple code:
Filters > Edit Code > Right-Click > Advanced Info > Info()
Filters > Edit Code > Right-Click > Advanced Info > avsmeter info
Filters > Edit Code > Right-Click > Advanced Info > avs2pipemod info
44vince44
7th June 2020, 14:08
ImageSource("Frames%04d.png", 0001, 1199, 24, pixel_type="RGB24",
So you have a RGB24 format.
You need to convert it YUV
I would try in staxrip to insert the filter
ConvertToYUV420(matrix="Rec709")
or if your video is strictly less than 720 lines resolution:
ConvertToYUV420(matrix="Rec601")
DavidRyan
8th June 2020, 10:52
Format : 1342177281 could mean that staxrip does not understand this format, and maybe the piping tools or encoders don't understand it either, it could still be a valid format, does the preview work? The preview does a format conversion. Maybe you just need to make a format conversion. There are more ways to show the color format, and they might work better than my relative simple code:
Filters > Edit Code > Right-Click > Advanced Info > Info()
Filters > Edit Code > Right-Click > Advanced Info > avsmeter info
Filters > Edit Code > Right-Click > Advanced Info > avs2pipemod info
ImageSource("Frames%04d.png", 0001, 1199, 24, pixel_type="RGB24",
So you have a RGB24 format.
You need to convert it YUV
I would try in staxrip to insert the filter
ConvertToYUV420(matrix="Rec709")
or if your video is strictly less than 720 lines resolution:
ConvertToYUV420(matrix="Rec601")
Great, that worked perfectly, I just added that line to my input script and now encoding proceeds without errors. What confused me initially was the preview in staxrip was working fine, I guess as stax pointed out that was doing its own conversion. As was virtualdub when I processed it through there first.
Thanks to you both for your time, this is very convenient now. :)
Atlantis
9th June 2020, 12:26
Question, is the x265 in staxrip a compile of this?
https://bitbucket.org/multicoreware/x265/wiki/Home
Patman
9th June 2020, 12:48
Question, is the x265 in staxrip a compile of this?
https://bitbucket.org/multicoreware/x265/wiki/HomeIt's a compile of this (https://bitbucket.org/multicoreware/x265_git/wiki/Home). Same like yours but git not mercurial.
Atlantis
10th June 2020, 02:03
I want to do a batch encode in staxrip. Is it possible in the settings to set a text to be appended to the end of the output files?
Like instead of -new, I want to use another text to be appended.
stax76
10th June 2020, 13:19
You can try:
Options > Paths > Default Target Name
Requires using macros.
And also:
Tools > Advanced > Event Command
Atlantis
10th June 2020, 20:12
Thanks. I will try.
Question for Patman. Using x265, the changing bitrate that is showing during encode, is it the current bitrate or the average bitrate? Using CRF Quality encoding.
Patman
11th June 2020, 19:42
Thanks. I will try.
Question for Patman. Using x265, the changing bitrate that is showing during encode, is it the current bitrate or the average bitrate? Using CRF Quality encoding.
It's the current bitrate.
Atlantis
11th June 2020, 21:40
I'm thinking having the average bitrate is more useful. Do any of your other versions show average bitrate? For example when you have a slow encode that is taking 2-3 days, it's good to know the average final bitrate at the moment. Having the current bitrate is not more useful than average.
44vince44
12th June 2020, 08:27
Atlantis, maybe it useful to have the average bitrate and i don't know what Patman is going to decide, but in all cases the instant (current) bitrate is very important as well and must be kept.
jlw_4049
12th June 2020, 08:28
Yes definitely like seeing the current bitrate
Sent from my SM-G986U1 using Tapatalk
44vince44
12th June 2020, 08:39
the avg bitrate would be easy to get:
avg kbps = current video size x 8 x video_fps / number_of_frames_written
need to adapt MB to KB
Atlantis
12th June 2020, 11:36
Question. Why the current bitrate is important? It means nothing. Actually it is not very useful. Here is an example. You are doing a slow encode. It is saying it is at 11236.99 kb/s. This doesn't help anything at all. You don't know if it is going up much later or if it was much lower. At any point of the encoding, even the last minute, you don't have a useful information.
On the other hand if it was the average bitrate, it is very useful. At any moment you know how the end result will be. The more you get to the end of the encoding, the more the bitrate information is accurate.
So please explain why the current bitrate is important?
44vince44
12th June 2020, 12:01
I understand your concern, but in that case why ALL encoders show current bitrate if it has no meaning.
If Patman removes the current bitrate and replaces it with average bitrate, there will be many people complaining because the current bitrate is expected.
But I am not saying that the average bitrate is useless, this is why I put the formula to show it is easy to calculate.
It's up to Patman to decide.
Now, on the other hand, in Patman's builds: there is a very useful information: the estimated file size.
Zgin
12th June 2020, 12:17
Hey, anyone here were using batch in staxrip? Let's say I have like 26 anime episodes in .mkv with .ass subtitles muxed in it. I want to encode it from .mkv to .mp4 with hardcoded subtitle. Were trying options > subtitles > every option and it just don't hardcode subtitles into .mp4 file. At the moment I have to open 26 stances of staxrip and in everyone manually open episode and then via ctrl + h add subtitle. Please help :)
stax76
12th June 2020, 13:00
Hey, anyone here were using batch in staxrip? Let's say I have like 26 anime episodes in .mkv with .ass subtitles muxed in it. I want to encode it from .mkv to .mp4 with hardcoded subtitle. Were trying options > subtitles > every option and it just don't hardcode subtitles into .mp4 file. At the moment I have to open 26 stances of staxrip and in everyone manually open episode and then via ctrl + h add subtitle. Please help :)
I'm not if this is a well-supported scenario, feel free to create an issue on the tracker (https://github.com/staxrip/staxrip/issues).
DavidRyan
12th June 2020, 13:04
On the other hand if it was the average bitrate, it is very useful. At any moment you know how the end result will be. The more you get to the end of the encoding, the more the bitrate information is accurate.
The estimated size is telling us this though, just in another way. The closer to the end of the encoding the more precise the size information will be, and size is directly correlated to average bitrate of course. To me a combination of current bitrate and estimated average size is two different useful pieces of information. But having said that I always thought it was showing average bitrate, as it doesn't fluctuate much and gradually settles to a range.
Atlantis
12th June 2020, 17:18
Well, the formula doesn't help when I'm in the middle of encoding because I don't have the size when the file has not been written yet to disk. And when the job is finished, I don't need it anymore.
44vince44, I still have not gotten an answer to why current bitrate is important. What do you do with it exactly. What do you learn from current bitrate?
I am using the version that shows only the current bitrate and remaining time.
44vince44
12th June 2020, 19:01
Use builds "M" of Patman: any moment, you have the size written, AND an estimate of the total size.
44vince44
12th June 2020, 20:39
Monitoring the instant (current) fps allows me to check at times if there are peaks of data rate. When I see very high peaks, I can abort encoding and change my encoding strategy by setting a high limit (using VBV-Bufsize and VBV-Maxrate).
This monitoring is possible with instant fps, and it's NOT possible with average fps.
Atlantis
12th June 2020, 21:56
But if your encode takes 7 hours or 2 days, you sit in front of the monitor all that time? For how long do you sit and watch the current bitrate?
Atlantis
12th June 2020, 22:02
Thank you for stable release 2.1.3.0. I just clean installed it and using it.
Thank you for Extract DTS Core feature. As I said before this is more useful and makes more sense at the demux stage and not at the encoding stage.
There are 2 scenarios.
1- You want to keep the core. You demux to DTS Core at demux stage and then use copy/mux.
2- You want to encode the core. Because the core is 5.1 and the HD is 7.1 for example. You want to encode the 5.1 mix. You demux the DTS core at first stage and then at the encoding stage, you can encode it to AAC 5.1 for example.
With eac3to -core you can easily extract it.
44vince44
13th June 2020, 08:19
But if your encode takes 7 hours or 2 days, you sit in front of the monitor all that time? For how long do you sit and watch the current bitrate?
If the film takes 1 day encoding, I do check on it at least once an hour (except sleep time) and I do often rethink how to encode.
But then this is not about me, it is about what Patman decides, and it is about that all encoders display an instant bitrate, since they are variable bitrate and it makes sense to show the variation of the bitrate.
jlw_4049
13th June 2020, 08:23
@stax76
In some of the later updates the ability to drag and drop srt subtitles into the container options window is gone.
Sent from my SM-G986U1 using Tapatalk
44vince44
13th June 2020, 08:28
Thanks Stax for the new release !!!
DavidRyan
13th June 2020, 08:48
Thanks for the hard work on the new release
stax76
13th June 2020, 14:10
In some of the later updates the ability to drag and drop srt subtitles into the container options window is gone.
It was lost in a modernization effort that involved moving code from a custom control that was no longer needed directly into the form. Fixed in the next build.
jlw_4049
13th June 2020, 15:29
It was lost in a modernization effort that involved moving code from a custom control that was no longer needed directly into the form. Fixed in the next build.Thank you again sir :)
Sent from my SM-G986U1 using Tapatalk
DenFox
13th June 2020, 16:40
I updated to 2.1.3.0, but now when I try to add a hardcore subtitle, staxrip crash! Even with the previous version (2.0.6.0)!
What could it be?
stax76
13th June 2020, 17:30
I updated to 2.1.3.0, but now when I try to add a hardcore subtitle, staxrip crash! Even with the previous version (2.0.6.0)!
What could it be?
It's probably caused by a change in avisynth 3.6, there is an issue on the tracker:
https://github.com/staxrip/staxrip/issues/224
There are few possible solutions:
1. install avisynth 3.5, staxrip will not allow an old version to be used because of compatibility changes introduced with avisynth 3.6, but staxrip has a setting to disable version verification, in the settings there is a danger zone setting for it. It should probably only used by power users and not permanently.
2. install avisynth 3.5 and modify the file \Apps\Versions.txt, this file contains all the version information of all the tools. There might be two ways to edit the file, the first is deleting the avisynth line, that's easy and will probably work, if not the line can be modified with the last change date of the DLL and the version name.
3. Use VapourSynth instead of AviSynth.
4. Wait until somebody fixes AviSynth/VSFilterMod.
DenFox
13th June 2020, 19:30
It's probably caused by a change in avisynth 3.6, there is an issue on the tracker:
https://github.com/staxrip/staxrip/issues/224
There are few possible solutions:
1. install avisynth 3.5, staxrip will not allow an old version to be used because of compatibility changes introduced with avisynth 3.6, but staxrip has a setting to disable version verification, in the settings there is a danger zone setting for it. It should probably only used by power users and not permanently.
2. install avisynth 3.5 and modify the file \Apps\Versions.txt, this file contains all the version information of all the tools. There might be two ways to edit the file, the first is deleting the avisynth line, that's easy and will probably work, if not the line can be modified with the last change date of the DLL and the version name.
3. Use VapourSynth instead of AviSynth.
4. Wait until somebody fixes AviSynth/VSFilterMod.
Avisynth 3.6.0 uninstalled, after that I installed Avisynth 3.5.1.
It works!
Thank you so much!
44vince44
14th June 2020, 09:11
Stax, thanks for including me in the contributor's list, that was a nice surprise :-)
mcjordan
14th June 2020, 13:01
NVEnc 5.0.5 is released.
AVSMeter 3.0.1.0 also.
Lynx_TWO
14th June 2020, 16:17
Apologies if I already posted this, but couldn't remember...
Is it possible to get a Frame Sequence / Image Sequence option added for the Source input? Preferably 16-bit TIFF files (.tiff and .tif) but 8 and 16 bit PNG file support would be pretty sweet as well. You'd need to be able to tell Staxrip what frame rate to interpret, and those could be:
8 fps (anime)
12 fps (drawn animation)
15 fps (gif animation)
23.976 fps (NTSC)
24 (film)
25 (PAL)
26 fps (3-strip Cinerama)
29.97 fps Drop Frame (DF timecode)
29.97 fps non-Drop Frame (NDF timecode)
30 fps (TV show)
47.952 fps (2x 23.976)
48 fps (HFR)
50 fps (PAL)
59.94 fps Drop Frame (DF timecode)
59.94 fps non-Drop Frame (NDF timecode)
60 fps (NTSC HD)
120 fps (slow motion output)
240 fps (slow motion output)
With the addition of Topaz Video Enhance Ai and there 16-bit TIFF output being the fastest option, it would be nice not to have to input into Adobe After Effects or similar just to encode a 1.3TB AVI to re-encode it in StaxRip, especially if using to enhance old family footage.
Thanks so much for all you do!
:thanks:
stax76
14th June 2020, 18:56
There is a request issue on the tracker and it's still open, if you add your requirements and technical details then there is a much higher chance that I actually do something about it. With details, I mean sample script and filenames of the first and last file, media info and possible GUI options like the suggested frame rates.
https://github.com/staxrip/staxrip/issues/214
-QfG-
15th June 2020, 20:31
I have a Question. With a 16 core Ryzen 9 3950x, is it recomnend to use 2 chunks, or another tip for boosting the speed during x265 4K encoding?
DavidRyan
15th June 2020, 23:17
I had a couple of strange errors initially after upgrading to 2.1.3.0, such as a popup telling me to open vapoursynth when I went to open a source (don't normally use vapoursynth) and HDR settings appearing by default in a SDR encode I tried. I had installed over the top of my 2.0.8 version, when I cleared the folder and only copied over the new files that came with this version the issues were resolved and everything now works as expected. Thought I'd mention it in case someone else has the same problem, guess there must have been some sort of conflict with the old files this time.
Atlantis
16th June 2020, 04:05
This has been mentioned before. There has been problems putting it on the top of the old. I always clean install a new version. I never keep any old config files. I do all from zero.
Atlantis
16th June 2020, 04:10
StaxRip 2.1.3.0:
In the jobs list we only see the file names of a batch job which I know is new. But we still see the full path for the manual single jobs. They should both look the same.
RainyDog
16th June 2020, 07:10
I had a couple of strange errors initially after upgrading to 2.1.3.0, such as a popup telling me to open vapoursynth when I went to open a source (don't normally use vapoursynth) and HDR settings appearing by default in a SDR encode I tried. I had installed over the top of my 2.0.8 version, when I cleared the folder and only copied over the new files that came with this version the issues were resolved and everything now works as expected. Thought I'd mention it in case someone else has the same problem, guess there must have been some sort of conflict with the old files this time.
I've been having this issue too since I upgraded to 2.1.3.0.
Always just copied new versions over the previous and never had a problem before.
I understand if there's been some substantial code change that requires a fresh install on this occasion. But I have a lot of manually created filter profiles and encoder profiles set-up that I really don't want to lose.
So how do I ensure these are not lost if I do start afresh with version 2.1.3.0... Just keep the Settings folder?
Thanks.
44vince44
16th June 2020, 08:22
Unfortunately the settings folders is the problem! You can't keep it. It's better to do as Atlantis says, clean install, redo all your customization.
However, for your filter profiles, you can copy the whole profiles as text to a text file, then copy it back to your new profiles (erasing the default one), It's a simple text copy/paste operation.
For your encoder profiles or templates, you have to do them again.
Between 2.0.8.0 and 2.1.3.0 there has been major changes. It's probable you wouldn't need to do that again soon.
BTW, remember you can download betas, current betas are more stable that 2.1.3.0 because they are bugfixes.
44vince44
16th June 2020, 08:34
-Qfg- increase chunks in the encoder options and at the same time max number parallel processes in the settings (same value for both), 4 is a good value for your Ryzen.
Also you could try not using chunks but instead, using the pools parameter in the encoder options, using maybe 6.
You could try both on a short sample and monitor the CPU usage to see which is best.
-QfG-
16th June 2020, 18:36
Thank you, i will try some samples.
stax76
16th June 2020, 18:49
In the jobs list we only see the file names of a batch job which I know is new. But we still see the full path for the manual single jobs. They should both look the same.
I can't just remove the path info because some people might miss it, people that use different paths.
Maybe it can be changed using a new setting, feel free to create a tracker ticket.
Recommendations about updates:
Never copy over or install over staxrip (or other apps like mpv.net), uninstall first, delete the old folder.
Absolutely avoid modifying or copy anything inside the startup or apps folder, simply because it would be difficult to update staxrip afterwards. There should not be a need doing this except rare situations like somebody wants to use AviSynth 3.5, here it would be necessary to modify the Versions.txt file (delete AviSynth line). To use custom tools with newer version the Apps dialog has a feature to use custom paths that point outside the startup/apps folder.
StaxRip allows to choose a custom path for its settings folder, this info is stored at:
HKEY_CURRENT_USER\SOFTWARE\StaxRip\SettingsLocation
StaxRip will ask for a settings folder whenever it starts from a new/unknown folder (folder does not match with registry entry).
I design features to use the settings folder for all customizations.
It's not necessary or recommended wiping out old settings after an update, usually settings are compatible, if not I have the possibility to force a reset for individual settings but I do this very rarely, especially for settings that have possibly many customizations like filter profiles.
Sometimes it's necessary or useful to reset certain settings, many dialogs have a reset feature to reset individual settings and there is a central reset feature at:
Tools > Advanced > Reset Setting...
Atlantis
16th June 2020, 21:10
If path is needed then why delete it from the batch job? I'm just saying what I'm seeing. When I have a batch encode and single encodes in the list, they look very different and it doesn't look good. It looks inconsistent.
I rather open a tracker ticket for including extracting the DTS Core in demux stage. If you think it's ok and feasible and you can do it, I will open one about that.
Oh also again in the demux window, you have buttons to select ALL or NONE for Audio and Subtitle, but not for Attachments. We need the same buttons for Attachments.
stax76
16th June 2020, 21:59
If path is needed then why delete it from the batch job? I'm just saying what I'm seeing. When I have a batch encode and single encodes in the list, they look very different and it doesn't look good. It looks inconsistent.
Batch job file paths are located in the settings directory, and they are longer and look more ugly than normal job file paths, it was a request to remove the full path.
There are three options, remove from both, make a setting or leave as is. For me it's fine to leave as is but if people say it could be improved then I consider it.
I rather open a tracker ticket for including extracting the DTS Core in demux stage.
It's supported in the eac3to demuxer, there is a menu preset for it.
For mkvextract somebody has to ask if it's supported, the mkvextract docs only say:
A_DTS
These will be extracted to raw DTS files.
The word core is not mentioned in the docs.
Oh also again in the demux window, you have buttons to select ALL or NONE for Audio and Subtitle, but not for Attachments. We need the same buttons for Attachments.
OK, bookmarked.
jlw_4049
16th June 2020, 22:37
If path is needed then why delete it from the batch job? I'm just saying what I'm seeing. When I have a batch encode and single encodes in the list, they look very different and it doesn't look good. It looks inconsistent.
I rather open a tracker ticket for including extracting the DTS Core in demux stage. If you think it's ok and feasible and you can do it, I will open one about that.
Oh also again in the demux window, you have buttons to select ALL or NONE for Audio and Subtitle, but not for Attachments. We need the same buttons for Attachments.
What benefits do you get from extracting DTS to core during the demuxing stage vs extracting DTS to core via the muxing process?
The former will need to do extra writes to your folder to store the file and then ultimately mux it in the end anyways. Not to mention it'll take longer, as it has to demux that and what ever else you choose, before Indexing, before you are able to crop/make changes and actually do the encode. Doing it in a single process during the muxing process makes more sense in my eyes.
StaxRip already supports this function
https://i.imgur.com/4fQWGme.png
If you simply need to extract the DTS core from a file you can pretty easily do this with FFMPEG. You can even set it up in a .bat script.
something like:
ffmpeg -i examplefilm.mkv -map 0:a:0 -bsf:a dca_core -c:a copy DTSCORE.dts
Or you can setup a .bat script to drag and drop the video file like so.
for %%a in ("*.mkv" "*.mp4") do ffmpeg -i "%%a" ^
-map 0:a:0 ^
-bsf:a dca_core ^
-c:a:0 copy^
"%%~na.dts"
@stax76
I know this is off topic, respond when you have the time, I would have PM'd you but you don't accept PMs.
You told me before you had good resources to learn Python. I have been learning some of it with a little Tkinter. I'm trying to make a basic GUI. I'm still having some trouble understanding some of the syntax and actually getting it into my head, could you please provide the names to the resources you was talking about. Thanks! :)
stax76
17th June 2020, 00:40
I know this is off topic, respond when you have the time, I would have PM'd you but you don't accept PMs.
You told me before you had good resources to learn Python. I have been learning some of it with a little Tkinter. I'm trying to make a basic GUI. I'm still having some trouble understanding some of the syntax and actually getting it into my head, could you please provide the names to the resources you was talking about. Thanks!
I think I had suggested the site realpython.com, it seems to have good free content:
https://realpython.com/learning-paths/python-gui-programming
jlw_4049
18th June 2020, 19:39
I think I had suggested the site realpython.com, it seems to have good free content:
https://realpython.com/learning-paths/python-gui-programming
:thanks:
44vince44
20th June 2020, 13:17
@Stax76:
Many users reporting problems due to Avisynth 3.6.0.
It is unfortunate that the latest stable release 2.1.3.0 includes buggy 3.6.0.
Maybe when 3.6.1 final is released, there should be a new Staxrip stable version ?
hevron
20th June 2020, 13:44
Stax76, Thanks a lot. :thanks::thanks::thanks:
Ver. 2.1.3.1 beta works great, I only added NVEnc 5.05.
It’s not clear what with NVEnc 5.06?
44vince44
20th June 2020, 20:39
Avisynth 3.6.1 final is released !
Atlantis
22nd June 2020, 01:31
AviSynth+ 3.6.1 is released (https://github.com/AviSynth/AviSynthPlus/releases/tag/v3.6.1) .................... with proper link.
44vince44
22nd June 2020, 22:46
Thank you Stax76 for latest beta 2.1.3.4.
It is working very well, and portable avisynth seems perfect now!
Thanks again!
hevron
23rd June 2020, 15:27
There is DTS-HD Master Audio / 5.1 / 48 kHz / 3846 kbps / 24-bit and you need to keep DTS Core: 5.1 / 48 kHz / 1509 kbps / 24-bit.
But staxrip lowers bit depth to 16-bit. It can be fixed?
tsMuxerGUI 2.6.16 Nightly holds 24-bit capacity.
Thanks.
jlw_4049
23rd June 2020, 15:36
There is DTS-HD Master Audio / 5.1 / 48 kHz / 3846 kbps / 24-bit and you need to keep DTS Core: 5.1 / 48 kHz / 1509 kbps / 24-bit.
But staxrip lowers bit depth to 16-bit. It can be fixed?
tsMuxerGUI 2.6.16 Nightly holds 24-bit capacity.
Thanks."DTS cores don't have any inherent bitdepth (same for many other lossy format, e.g. AC3, AAC). You can ignore what MediaInfo tells you about it after core extraction. Only the lossless DTS-HD Master Audio "has" a bitdepth in any meaningful way."
This was a post by sneaker some time ago.
Sent from my SM-G986U1 using Tapatalk
hevron
23rd June 2020, 16:00
"DTS cores don't have any inherent bitdepth (same for many other lossy format, e.g. AC3, AAC). You can ignore what MediaInfo tells you about it after core extraction. Only the lossless DTS-HD Master Audio "has" a bitdepth in any meaningful way."
:thanks:
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.