StaxRip

[stax76]

When having external subtitles, if we add the language at the end like *.English.srt staxrip recognizes the language when loading. Is there a way to also indicate to staxrip that it is a forced track? Something like *.English.Forced.srt?

In the old build only _forced, new build also .forced. (case-insensitive)

There is something I need your help with x264 encoding.

Perhaps I am now a bit spoiled with x265 HBD support and I tried to have the same thing in x264.

I tried to use the x264 (8 bit) --input-depth 16 parameter (unfortunately no --dither found) but what I got is

avs [info]: AviSynth+ 3.7.0 (r3382, 3.7, x86_64)
avs [info]: avisynth 16bit hack enabled
avs [info]: 960x800 0:0 @ 24/1 fps (cfr)

instead of dealing with the original 1080p source.

Is there a way to let x264 properly manage a HDB source?

--input-depth is documented as:

--input-depth <integer> Specify input bit depth for raw input

But I don't know if it means raw pipe, raw file or both, you can try in the x264 Options dialog:

Input/Output > Pipe

It has a couple of options, or maybe create a dedicated thread or ask on the issue tracker:

https://github.com/Patman86/x264-Mod-by-Patman/issues

https://github.com/DJATOM/x264-aMod/issues

https://github.com/staxrip/staxrip/issues


2.1.8.5 Beta (2021-03-09)


When a video encoder default value was changed, a compatibility issue with old settings was happening, this is finally fixed, but could only be achieved by resetting all video encoder options (stax76)
Fix issue with ffmpeg AAC encoding (stax76)
Encoder dialogs allow using 1:1 for --sar (stax76)
Introduce Output Highlighting in processing dialog (Dendraspis)
Introduce Command Line Highlighting in command line preview (Dendraspis)
Add more theme colors (Dendraspis)
Fix Menu Item Path not being stored (Dendraspis)
Package Name/Version is not displayed when unknown versions are accepted (Dendraspis)
Customized progress text adjusted for new x264 Patman builds (Dendraspis)
x265 --selective-sao default set to 0 (Dendraspis)
x265 --qpmin, --qpmax and --qpstep boundaries set (Dendraspis)
x265 ---psy-rd moved from Other to Analysis (Dendraspis)
x264 --progress-header disabled for Patman build (Dendraspis)
Customized progress text fix for new Patman build (Dendraspis)
Fix resize values are not refreshed after changing them (Dendraspis)
Adjustments to match the SI prefix according to IEC (Base 10) (Dendraspis)
Set minimum bitrate of 32kbps for (E)AC3 (Dendraspis, 44vince44)
Fix ffmpeg DD+ encoding issue with high bitrates by adding 0.1 to bitrate (Dendraspis)
Add vertical scrollbars to Code Editor code-boxes (Dendraspis)
Code Editor does not join Source, Crop, Resize and Rotation filters automatically (Dendraspis)
Code Editor can join (in-)active filters only [Don't forget to reset "Edit Menu" in Code Editor!] (Dendraspis)
Code Editor joined filters have the filter name "Misc" (Dendraspis)
Custom checkboxes for better theme experience (Dendraspis)
Readme.md refreshed (Dendraspis, stax76)
Error exit codes are interpreted using Err.exe (stax76)
arib-srd-b67 changed to arib-std-b67 in NVEnc, QSVEnc, and VCEEnc (JKyle)
Detect forced subtitles by filename _forced and .forced. (case-insensitive) (stax76)
The crop dialog allows to define the color used for cropping via menu (stax76)
StaxRip passes theme colors to MediaInfo.NET via CLI (stax76)
SMDegrain 3.1.2.111s
mkvtoolnix 55 (mkvextract Unicode fix)
MP4Box 1.1.0 DEV rev542 gcc10.2.0 Patman (AAC 7.1 fix)
rav1e 0.5.0-alpha gcc10.2.0 Patman
DGMPGDec 2.0.0.5 (large file handling fix)
aomenc 2.0.2-1350-msvc1928 Patman
x265 3.5_RC1+2+29-gcc10.2.0 Patman Mod
x264 0.161.3048+25-gcc10.2.0 Patman Mod
ffmpeg N-101392-gcc10.2.0 Patman
MediaInfo.NET 6.9.0.0 (gets theme colors from StaxRip via CLI)
Err 10.0.17763.1


Thanks for testing :thanks:

[44vince44]

Thanks for the beta !

[tormento]

It has a couple of options, or maybe create a dedicated thread or ask on the issue tracker
Thanks for your answer.

I have found this old thread (https://forum.doom9.org/showthread.php?p=1778327) where it seems that a possible solution has been posted but I don't know if it's still valid.

[jlw_4049]

Thanks for BETA ill try it out later today

Sent from my SM-G986U1 using Tapatalk

[kalehrl]

Is there a way to cut a video at I frames only?
I need this for mkv cutting without video and audio encoding.
Sometimes the cuts are a few frames off because cut marks are not at I frames.

[stax76]

Thanks for BETA ill try it out later today

You're welcome, have a look at the new crop color feature, I think it was you suggesting it.

Is there a way to cut a video at I frames only?
I need this for mkv cutting without video and audio encoding.
Sometimes the cuts are a few frames off because cut marks are not at I frames.

The preview has nothing built in to know where an I-frame is, it could maybe be displayed by avs/vs.

@all

I'm thinking and preparing about staxrip retirement since a longer time, but this doesn't change much right now except I won't post in this thread any longer but only on GitHub, where Dendraspis has now also admin rights, 44Vince44 and JKyle (hope you are fine) are still here.

[44vince44]

A well deserved retirement, although we know we'll still be hearing from you !

[jlw_4049]

You're welcome, have a look at the new crop color feature, I think it was you suggesting it.



The preview has nothing built in to know where an I-frame is, it could maybe be displayed by avs/vs.

@all

I'm thinking and preparing about staxrip retirement since a longer time, but this doesn't change much right now except I won't post in this thread any longer but only on GitHub, where Dendraspis has now also admin rights, 44Vince44 and JKyle (hope you are fine) are still here.You've really put in some work. I think we'll be seeing you around [emoji57]

Sent from my SM-G986U1 using Tapatalk

[Lada1]

In the version 2.0.6.0 there was that option to set the output file size I do not see it anymore in 2.1.8.0 version

https://forum.grassvalley.com/filedata/fetch?id=562466&d=1615374705

[Atlantis]

You can't retire! Staxrip is the only usable software to encode video. I remember the days of MeGUI. It was not easy and nice!

[stax76]

It's currently in very good shape with 5 active contributors, absolutely no need to worry.

[Arkana]

Hello, I get this error message whenever I try to denoise my video

https://i.postimg.cc/Q9kCbV0G/screenshot-1320.png (http://postimg.cc/Q9kCbV0G)

The KNLmeansCL is present and staxrip has administrator previliges
Any idea why and how to fix it?

--
edit: it might that my GPU not supporting it, I'm running windows server it doesn't have dedicated GPU. Is there any way to 'move' the work to CPU instead?

[44vince44]

@Arkana Can you show the script please, and tell us what staxrip version you are using...

@Lada1 the output file size appears when you select a mode that allows it in the encoder: bitrate, 2pass, 3pass.
If you select Quantizer and Quality modes, then the output file size is not available because these two modes don't work by anticipating file size.

[tormento]

2.1.8.5 Beta (2021-03-09)
I really love the colored log, thanks!

1) I have a issue I can't find solution: I want the container to stop muxing sub tracks when finished encoding. I have looked into options and preferences and can't find how. On sigle job, I just manually remove them but, on batch, I can't find how. I need help!

2) When I add batch jobs, I'd like to have the capability the single generated ones. I have tried to load one from Jobs panel but it gives me "Project not found" error.

[44vince44]

@tormento

1) you can set in the OPTIONS > Subtitles set Demux Subtitles to NONE

2) this is by design in staxrip, the jobs added in batch mode cannot be opened. But if they have been started, you can load the *.srip file generated in the temp folder so you can edit it.

[tormento]

1) you can set in the OPTIONS > Subtitles set Demux Subtitles to NONE
Tried but it strangely doesn't work in batch mode.

[44vince44]

i'll try it again, it used to work...

you're right, it's a bug, i'll report it!

[44vince44]

It appears to be a known issue (checked with @Dendraspis) , but it has a workaround, that I suggest you use while @Dendraspis sees if it can be fixed soon.
Workaround: remove all from the box "Preferred languages", leave it empty.

[stax76]

i'll try it again, it used to work...

you're right, it's a bug, i'll report it!

It's a feature! Audio and subtitle demuxing isn't needed in staxrip, staxrip/mkvmerge can take the streams directly from the source file. It can be disabled here:

Options > Subtitle > Preferred Languages

It's maybe not very user-friendly, maybe the docs can be improved.

[44vince44]

Ok so not a bug, so it means:

- preferred languages : are the languages that will be included in the final file AUTOMATICALLY
- demux subtitles: tell staxrip if you want to demux subtitles, it is independent from what will be in the final file, and which is not necessary (some people could need the demuxed stream for other processing)

then can "preferred languages" be named in a more understandable way?

[stax76]

It's hopefully possible to improve the usability for this, but possibly not easy, so nothing I can do at the moment because I want to take care of mpv.net, maybe Dendraspis has interest. It's documented here:

https://github.com/staxrip/staxrip/wiki/Usage#demuxing

[tormento]

It's a feature!
Well, I tried and I really can't sort out how to configure it properly.

P.S: Is there a way to modify the font in the "Processing..." window?

[stax76]

> Well, I tried and I really can't sort out how to configure it properly.

You want to disable subtitles altogether and have tried to clear the 'Preferred Subtitles' Option?

I'm having a good idea how to improve the usability, it's probably not much work, so I might upload a hotfix tonight.

> P.S: Is there a way to modify the font in the "Processing..." window?

No, you can request it on the tracker, Dendraspis decides then, he has recently built the highlighting.

[stax76]

@tormento

There is a new hotfix online addressing the issue.

[44vince44]

the hotfix works fine, I've just tested it. Thank you @Stax76. The purpose of those settings is now VERY CLEAR !

However, @Tormento, I was able to have it work BEFORE the hotfix, simply by removing everything from the "preferred languages" box, it worked too.

[tormento]

There is a new hotfix online addressing the issue.
Thanks!

[JKyle]

@stax76,

The most recent hotfix StaxRip.exe seems to have a broken Code Preview window.
The UI scale factor doesn't work, there's no scroll bar, and a Close button is not present on that window.

[tormento]

The StaxRip bitdepth gauge works well when feeding on video source but when feeding on a AVS script, it always presumes that it's 8 bit.

Is it possible for StaxRip to sample some input frames and find the correct bit depth?

[stax76]

The most recent hotfix StaxRip.exe seems to have a broken Code Preview window.
The UI scale factor doesn't work, there's no scroll bar, and a Close button is not present on that window.

Can you please try the last hotfix, UI scale works for me, this dialog is used for the code preview and for the console context help in the encoder dialogs, it has the following features:


Remembers the windows size
Has no close button but can be closed with escape key
Supports vertical and horizontal scrollbars, they are only visible if the text is larger than the window (auto hide mode)
Word wrap is disabled

The StaxRip bitdepth gauge works well when feeding on video source but when feeding on a AVS script, it always presumes that it's 8 bit.

Is it possible for StaxRip to sample some input frames and find the correct bit depth?

You mean what the source section in the main dialog displays? These parameters are a mixture of parameters retrieved by MediaInfo, but also read directly from the script (only the source section is analyzed), if the source file is an avs/vpy file then staxrip might look into the script to make a guess of the original video file source location and read parameters from there via MediaInfo. So yes, there could be an issue, in that case I hope somebody can report it on the tracker and analyze it how it behaves and how it can be improved.

[tormento]

So yes, there could be an issue, in that case I hope somebody can report it on the tracker and analyze it how it behaves and how it can be improved.
Ok, thanks. I hoped AVS+ could report the frame bitdepth with some query function.

[stax76]

@tormento

I think the current behavior is fine, most of the values shown in the source section come directly from the video source file and not from the script. To get script info right-click the filters and click 'Info'.

In the next build:

Main dialog and code editor show script info with F2 key and advanced script info with Ctrl+F2, requires menus to be reset manually

[JKyle]

Can you please try the last hotfix, UI scale works for me, this dialog is used for the code preview and for the console context help in the encoder dialogs, it has the following features:


Remembers the windows size
Has no close button but can be closed with escape key
Supports vertical and horizontal scrollbars, they are only visible if the text is larger than the window (auto hide mode)
Word wrap is disabled


The original Code Preview window of 2.1.8.5:

https://i.imgur.com/jkn8t3a.jpg

The hotfix (StaxRip.exe uploaded in your beta archive about 2 hours ago) Code Preview window:

https://i.imgur.com/xM0OekS.jpg


Remembers the windows size ⇒ OK
Has no close button but can be closed with escape key ⇒ OK
Supports vertical and horizontal scrollbars, they are only visible if the text is larger than the window (auto hide mode) ⇒ OK
Word wrap is disabled ⇒ OK


But the font does not seem to be fixed-width.
Maybe this is why I feel the UI scale factor is not respected.

---

ADDED:

After looking into the hotfix more closely, I've learned that you've changed the font from Consolas to Segoe UI for the same window element.

https://i.imgur.com/AuV3TZS.jpg

It has pros (more tidy, etc.) and cons (smaller than before, etc.), but I think it's a matter of getting used to.
Not bad.

[stax76]

I've uploaded a hotfix with new setting to choose the font used by code and console features. Available fonts to choose from are Consolas, Courier New and if installed Cascadia Code (installed by Windows Terminal).

[JKyle]

Very cool.
:thanks:

[JKyle]

Is there a way to cut a video at I frames only?
I need this for mkv cutting without video and audio encoding.
Sometimes the cuts are a few frames off because cut marks are not at I frames.

You can make a frame number list of I frames and refer to it.

Suppose the input video is INPUT.mkv and you want to make a text file named OUTPUT.txt that contains only the frame number list of I frames.


[Windows CMD]


Step 1

Use ffprobe, findstr with /n switch to produce TEMP.txt that has a list of I frame numbers in this format:

1:frames.frame.0.pict_type="I"
229:frames.frame.228.pict_type="I"
361:frames.frame.360.pict_type="I"
481:frames.frame.480.pict_type="I"
517:frames.frame.516.pict_type="I"
565:frames.frame.564.pict_type="I"
...


The command line is as follows:

ffprobe -loglevel error -select_streams v:0 -show_entries frame=pict_type -of flat INPUT.mkv | findstr /n I > TEMP.txt

Here, ffprobe should be in the user's PATH environment variable. Otherwise, you need to write down the full path to ffprobe.exe instead.


Step 2

In order to remove the unnecessary part other than the actual frame numbers in each line, use for loop with /f switch as follows:

(for /f "tokens=3 delims=." %a in (TEMP.txt) do @echo %a) > OUTPUT.txt

So the final OUTPUT.txt file looks like this:

0
228
360
480
516
564
...



Steps 1 & 2 combined

Just wrap each command line with a pair of parentheses and combine them with &&.

(ffprobe -loglevel error -select_streams v:0 -show_entries frame=pict_type -of flat INPUT.mkv | findstr /n I > TEMP.txt) && ((for /f "tokens=3 delims=." %a in (TEMP.txt) do @echo %a) > OUTPUT.txt)

It looks a little scary, but it works. :D


[Bash]

If you can use Bash shell (in Linux or WSL), then things get much simpler. You just need to use ffprobe, grep with -n switch, cut with -d and -f, and then redirect the output to OUTPUT.txt as follows:

ffprobe -loglevel error -select_streams v:0 -show_entries frame=pict_type -of flat INPUT.mkv | grep -n I | cut -d '.' -f 3 > OUTPUT.txt

[tormento]

I've uploaded a hotfix with new setting to choose the font used by code and console features. Available fonts to choose from are Consolas, Courier New and if installed Cascadia Code (installed by Windows Terminal).
/me happy and please leave freedom to choose any fixed width font. I am addicted to Fira Code, for example :)

[stax76]

@tormento

There is a new hotfix online where you can enter the font name in a text box.

Making it a menu to choose from is difficult.

[tormento]

There is a new hotfix online where you can enter the font name in a text box.
I really appreciate it.

[tormento]

Making it a menu to choose from is difficult.
https://i.lensdump.com/i/Iq8FLM.md.png (https://lensdump.com/i/Iq8FLM)

Is it normal to have all those dropdown colors with all the possible themes?

[JKyle]

Yes, it's normal.
Darkness first, feature colors next.

[JKyle]

x265 version 3.5 is now official (https://bitbucket.org/multicoreware/x265_git/commits/).


Version 3.5
===========

Release date - 16th March, 2021.

New feature
-----------
1. Real-time VBV for ABR (Average BitRate) encodes in –pass 2 using `--vbv-live-multi-pass`: Improves VBV compliance with no significant impact on coding efficiency.

Enhancements to existing features
---------------------------------
1. Improved hist-based scene cut algorithm: Reduces false positives by leveraging motion and scene transition info.
2. Support for RADL pictures at IDR scene cuts: Improves coding efficiency with no significant impact on performance.
3. Bidirectional scene cut aware Frame Quantizer Selection: Saves bits than forward masking with no noticeable perceptual quality difference.

API changes
-----------
1. Additions to x265_param structure to support the newly added features and encoder enhancements.
2. New x265_param options `--min-vbv-fullness` and `--max-vbv-fullness` to control min and max VBV fullness.

Bug fixes
---------
1. Incorrect VBV lookahead in `--analysis-load` + `--scale-factor`.
2. Encoder hang when VBV is used with slices.
3. QP spikes in the row-level VBV rate-control when WPP enabled.
4. Encoder crash in `--abr-ladder`.

Hope @DJATOM, @Patman, and @msg7086 start working on their mod versions soon. :)

---

ADDED:

And @DJATOM just released his mod version here (https://github.com/DJATOM/x265-aMod/releases/tag/3.5%2B20). :eek:

[rtyall]

@44vince44
Running the test now with "Avs2pipemod instead of None". I can tell already that its going to finish with the slower 13minutes due to how it starts out. 2.1.7.0 starts out encoding my test file at around 20fps and settles down to around 11fps. When I do the encode with 2.1.3.7 it starts out around 32fps and settles down to around 18fps. Will update once it finishes in about 10 minutes.



When I over wrote things in the 2.1.3.7 folder I did verify in the tools section that the version numbers were updated and it was using the newer tools from 2.1.7.0. x265 and AviSynth 3.6.2 test 6. I cannot use the older AviSynth 3.6.1 or 3.6.0 with the newer staxrip 2.1.7.0 because it gives and error. I think staxtrip 2.1.7.0 requires AviSynth 3.6.2 somewhere so the best test I can do is to add the new tools to the old app.


2.1.3.7 w new apps from 2.1.7.0 (x265, Avisynth 3.6.2 test 6, ffms2, ffmpeg) and FFVideo source filter = Duration: 08:19
2.1.3.7 w new apps from 2.1.7.0 (x265, Avisynth 3.6.2 test 6, ffms2, ffmpeg) and LWLibavVideoSource source filter = Duration: 08:23
2.1.7.0 with LWLibavVideoSource = Duration: 13:10
2.1.7.0 with Automatic (FFVideo) = Duration: 13:01
2.1.7.0 with Automatic (FFVideo) and Avs2pipemod pipe = Duration: 13:01

Something in version 2.1.4.8 and above seem to run much slower on my system for some reason. Happy to keep trying things or post logs if you want. Thanks for the ideas so far.


I know this is an old post, but after upgrading from an old version (2.1.3.0 to 2.1.8.0), I noticed my x265 encodes were taking double the amount of time.
I was using a preset I'd made and opened that before adding a video, after a bunch of trial and error I''d found some of the x265 defaults had changed and these were causing the speed discrepency.

In 2.1.3.0 Rskip is undefined by default, when it runs it defaults to rskip mode=1, in 2.1.8.0 it has rskip defaulting to 0.
Also in 2.1.3.0 although badapt was set to full, this ran with setting 0 according to the logs, whereas in 2.1.8.0 it's set to full and runs badapt=2.


I ran a few tests with each setting enabled/disabled and confirmed in the logs that these were the only differences:

2.1.3.0 - 24 seconds
2.1.8.0 - 68 seconds
2.1.8.0 (- rskip=0 + Badapt=2) - 32 seconds
2.1.8.0 (+ rskip=0 - Badapt=2) - 51 seconds
2.1.8.0 (- rskip=0 - Badapt=2) - 23 seconds


Hope this makes sense, as I don't really understand it myself :D

[44vince44]

@rtyall, we made an entry in our wiki because this is a recurring question.
Read this:
https://github.com/staxrip/staxrip/wiki/x265-apparent-performance-drop-FIX

The x265 build included in 2.1.3.0 is very different from the one in 2.1.8.0.
And the options defaults have changed.

I recommend for you to always delete all the settings, set them from scratch, do your templates from scratch when you get a new version that has too many changes.
By doing that, you ensure that you are using the correct defaults.

[rtyall]

@rtyall, we made an entry in our wiki because this is a recurring question.
Read this:
https://github.com/staxrip/staxrip/wiki/x265-apparent-performance-drop-FIX

The x265 build included in 2.1.3.0 is very different from the one in 2.1.8.0.
And the options defaults have changed.

I recommend for you to always delete all the settings, set them from scratch, do your templates from scratch when you get a new version that has too many changes.
By doing that, you ensure that you are using the correct defaults.

Thanks for that, I searched earlier but didn't come across that post, I was searching for "slow" and "speed" rather than performance, so probably my fault there.

When I next update I'll remember to recreate the templates, thanks :)

[JKyle]

This is a follow-up of this post (https://forum.doom9.org/showthread.php?p=1938227#post1938227) about generating the I-frame list of a video file.

For the same INPUT.mkv file, the PowerShell version is as follows:

$filename = "INPUT.mkv"; ffprobe -loglevel error -select_streams v:0 -show_entries frame=pict_type -of flat $filename | Select-String "I" -CaseSensitive | ForEach-Object { Write-Output ($_.LineNumber-1) } | Out-File -FilePath $filename" I-frame list.txt" -Encoding ascii

The I-frame list text file 'INPUT.mkv I-frame list.txt' is automatically generated based on the input file name.

I was interested in putting this script in the Scripts folder, but have run into a couple hurdles.

I put a Discussion post on GitHub (https://github.com/staxrip/staxrip/discussions/603), so plz participate if you're interested. :)

[fredlkrue]

Using latest beta, either using x264 or HEVC encoder when I set a target file size the output is way off. Older versions didn't have that issue.

[JKyle]

The SI(decimal) prefixes are set to be the default starting with 2.1.8.5. In order to use the old customary binary(IEC) prefixes, you need to set it deliberately on `Tools` > `Settings` > `User Interface` > `Use binary prefix (MiB) instead of decimal prefix (MB) for sizes`.

Adjustments to match the SI prefix (Base 10) for sizes instead of IEC prefixes (Base 2)

That said, there was a bug in calculating bitrates(unit: kbps), and it is fixed recently and the next version will be correct with that. See here (https://github.com/staxrip/staxrip/issues/597).

[fredlkrue]

The SI(decimal) prefixes are set to be the default starting with 2.1.8.5. In order to use the old customary binary(IEC) prefixes, you need to set it deliberately on `Tools` > `Settings` > `User Interface` > `Use binary prefix (MiB) instead of decimal prefix (MB) for sizes`.



That said, there was a bug in calculating bitrates(unit: kbps), and it is fixed recently and the next version will be correct with that. See here (https://github.com/staxrip/staxrip/issues/597).

Thanks for the information.

[44vince44]

New BETA Release : Staxrip v2.1.9.0. Unlike previous betas, this one has been released on Github's release page.

Download link here (https://github.com/staxrip/staxrip/releases/tag/2.1.9.0).

WARNING:

- Might break settings from previous version, so starting with new settings is recommended
- Might break templates and jobs from previous version
- If not starting with new settings, some changes in menu won't be applied (requires manual setting reset or global settings reset in order to make these new items appear, or simply new settings)

Changelog since 2.1.8.5:

Since v2.1.8.5 StaxRip uses the SI prefix for sizes (Base 10: 1 MB = 1000 KB)
Now it is possible to switch (back) to IEC prefix (Base 2: 1 MiB = 1024 KiB) in the settings
Please note, that the target size menu must be resetted or adjusted by hand after a change! (@Dendraspis, @44vince44)
Set "Dark | Blue" as default theme (@Dendraspis)
CheckBox appearance optimized (@Dendraspis)
CodeEditor does not join "Cutting" filter (@Dendraspis)
Block size for Compressibility Check can be set in seconds (@Dendraspis, #547)
The x264 command line preview shows all passes (@Dendraspis, #496)
The aomenc command line preview shows all passes (@Dendraspis, #496)
Extended option descrption for 'Temp Files Folder' if Auto-Deletion is enabled (@Dendraspis, #542)
Progress Reformatting is a global option like Output Highlighting (@Dendraspis)
Improved usability for subtitle options (@stax76, #577)
Show target size label including size unit (@Dendraspis, @VEGAX265, #580)
Theme "Default" is renamed to "System Colors" (@Dendraspis)
Priority for current selected process can be set via menu on Processing window (@Dendraspis)
Multiple theme related adjustments (@Dendraspis, @stax76)
New shortcuts for Output Highlighting and Progress Reformatting on Processing window (@Dendraspis)
New shortcuts for existing actions on Jobs window (@stax76)
Fix x265 --tskip default value for Placebo preset (@tkozybski, @Dendraspis, #600)
Fix x265 Slower preset default values (@tkozybski)
Fix x265 params --atc-sei and --pic-struct wrong parameter type (@Dendraspis, #593)
x264 default CRF value set while setting initial value to 20 (@Dendraspis, #594)
x264 fix UltraFast preset value sync (@Dendraspis, #594)
Fix NVEnc VBR Quality value localization (@Dendraspis, #604)
Fix NVEnc VBR Quality applies even it's disabled (@Dendraspis, #605)
Removal of Menu Styles (@Dendraspis, #589)
In quality mode main dialog shows count and type of active subtitles (@stax76)
Main dialog and code editor show script info with F2 key and
advanced script info with Ctrl+F2, requires menus to be reset manually (@stax76)
New setting to customize the code and console font (@stax76)
Video encoder context console help was fixed and improved (@stax76, #595)
Fix audio bitrate calculation for calculation of video bitrate (@Dendraspis, @44vince44, #608)
When toggling size prefix target size/bitrate are refreshed (@Dendraspis)
AddGrainC v1.8.3.0
AnimeIVTC v2.34 2020-12-19 mod
AVSMeter v3.0.8.0
chapterEditor v1.27
CropResize 2021-02-01
MediaInfo.NET v7.0.0.0
MP4Box v1.1.0 DEV rev589 gcc10.2.0 Patman
MTN Thumbnailer v3.4
SangNom2 v0.6.0
xy-VSFilter v3.2.0.804

[JKyle]

I believe an extra note is due with this beta release.


Starting in this beta version, @Dendraspis can also administer build releases (not to mention @stax76).


The version naming scheme has changed to a new one compatible with semantic versioning. Delimited by a period(.), the first two groups of numbers represent the stable version, the third group represents the beta, and the last group represents the dev version. See here (https://github.com/staxrip/staxrip/discussions/579#discussioncomment-489371) for more detail.


:)