StaxRip

[dom61]

I found the command to compare the second file.
Also with the space bar you can switch from one image to the other.



It would be very helpful to include an indexing indicator when loading the file, so as not to incur the misinterpretation of crashes.

[CarlOtto]

Version 2.39.3 is released.
https://github.com/staxrip/staxrip/releases/tag/v2.39.3

[CarlOtto]

Version 2.41.0 is released.
https://github.com/staxrip/staxrip/releases/tag/v2.41.0

[dom61]

Good morning.
When I import the file with ProRes HQ422 codec to do x265 encoding StaRip crashes with the following message.



I don't understand what it refers to in order to solve this problem.
Any ideas?
Thank you

[Nu©leus]

v2.41.6 is released.

https://github.com/staxrip/staxrip/releases/tag/v2.41.6

Changelog: v2.41.6 (2024-07-03)

• UI: Fix "--normalize" and "--gain" are used for qaac at the same time when Pipe is used (#1410)
• Internal: Fix crash on demuxing command without loaded project
• Internal: Fix rare crash when closing Processing window right before closing StaxRip (#1414)
• Internal: Raise event "Before Job Adding" also when adding a batch job (#1407)
• Internal: Improve valid Dolby Vision metadata recognition for extraction (#1409)
• NVEncC: Add new "--vpp-fft3d" parameter
• NVEncC: Add new value "ngx-vsr" for "--vpp-resize" parameter
• x264: Add "--aq-bias-strength" parameter (#1412)
• Update tools
• MediaInfo v24.06
• NVEncC v7.57
• QSVEncC v7.67
• vvencFFapp v1.12.0 r236-d57c73d

[dom61]

Release 2.42 Dendraspis released this (2024-09-05)
https://github.com/staxrip/staxrip/releases/tag/v2.42.0

Note
Among many, many changes you can find listed below, it's time for a "little" game changer. After an incredible amount of hours of back and forth the number of audio tracks is optional now, with a default number of six. ���� Because of so many different factors the Main window does currently not change its size automatically when you change the number of audio tracks. Therefore the Main window is sizable now (within some limits) which offers some other benefits. In this context the whole audio file and stream insertion and recognition was also altered, which leads to a better, but maybe different, handling than you were used to.
The optional number of audio tracks was very challenging to integrate into the existing environment, but I am very sure, that it works wonderful finally. Nevertheless I am also sure that I could not have tested all workflow cases and exceptions. So please pay attention and report any issue.
The Auto Crop process has also been improved and extended a lot, so there are some new parameters to define what you want to consider to be cropped. The default values should be fine for almost all cases, but feel free to tweak them for your needs. ��
For everything else check the Changelog below.
Many thanks to everybody, who helped testing during the development stages as well as @Patman86 for his binaries. Special thanks to the few supporters for their support and kind words!

Important
It is highly recommended to start with new/fresh settings, especially because of the change in audio handling! You can avoid unwanted side effects by not using or copying your old settings over.


Update 2.42.1 Dendraspis released this (2024-09-08)
https://github.com/staxrip/staxrip/releases/tag/v2.42.1

Changelog:
UI: Fix Demuxing Subtitles for ffmpeg (#1466)
UI: Fix not saving log files (#1467)
UI: Fix no time display on Crop window (#1470)
UI: Disable Window Dark Mode when system colors are used (#1470)
UI: Fix Demux handling for subtitles (#1471)
NVEncC: Fix incompatible output file type for AV1 encodes
QSVEncC: Fix incompatible output file type for AV1 encodes
VCEEncC: Fix incompatible output file type for AV1 encodes

[LigH.de]

Thanks a lot for your great efforts.

Yesterday I used it just to try which CLI you use to handle x265's input. I missed the new audio part, so my first test ended without any audio stream. Then I noticed the area. I discovered easily how to use it, added another audio stream, restarted the job ... and it asked me whether I want it to re-encode or re-use the already present video stream. Smart job!

[Bibo64]

Sorry guys, I'm looking for a forum to discuss recent problems with V2.42.1.
I use staxrip since the very early days and always found a way for me to manage problems which occur with a new version.
But now I'm stuck...
I convert 720p50 content to 480p25 that fails because staxrip counts the frames encoded and realizes a mismatch (of course...!).

The second is a failure with deinterlacing. I use ffmpeg to impose the delogo filter and so I do all the work within an ffmpeg filter graph that fails completely.
Can you tell me a forum, where I can discuss my problem(s)?

Tanks in advance.

[lojelo5]

https://forum.doom9.org/showthread.php?t=172068

[Bibo64]

Thanks, lojelo5,

I posted my request for help with doom9, but it seems there's nobody to answer.
Maybe my question was to difficult?
Or the forum is dead at the moment?

[Stupido]

v2.44.0 released by Dendraspis (2024-12-20)
https://github.com/staxrip/staxrip/releases/tag/v2.44.0

Important
I highly recommend starting with new settings and templates as VapourSynth and many encoder related parameters have changed and might break your configurations that have to be renewed. Otherwise check your profiles and templates, fix them if necessary and don't forget to save them again. 😉

Note
Special thanks to all supporters, especially the few Patreon members, who have been instrumental in making this version available! ❤️

This is the last release for 2024!
Thank you for using StaxRip, for reporting issues, for requesting features as well as for supporting StaxRip and keeping it alive. ❤️
Merry Christmas and a happy new year! See you in 2025.... 🎆✨
And just in case any of your friends or family still needs a gift for you: 🎄🎅 😉

Changelog:

• Audio: Add "Center/Speech Optimized Stereo" option
• Audio: Demux audio even if all tracks are set to "No Audio" (#1529)
• Audio: Fix broken audio file addition of demuxed files under some circumstances
• Audio: Fix Normalize (#1484)
• Audio: Improve Normalize
• Macro: Fix %encoder_codec% is not shown on Macro List
• MP4Box: Add custom switches for video tracks (#1532)
• MP4Box: Add "Better Seeking" general preset (#1535)
• NVEncC: Add new value "libplacebo" for "--vpp-resize" parameter
• NVEncC: Adjust default values for "--vpp-ngx-truehdr" parameter
• NVEncC: Always show "--vbr-quality" parameter in VBR mode
• NVEncC: Remove parameters "--level", "--profile" and "--tier" for AV1 codec (#1534)
• Rav1e: Fix 2-pass execution (#1531)
• Rav1e: Fix bitrate not being synced with main window
• Rav1e: Reorganize options
• SvtAv1EncApp: Set default value for "--chroma-qm-min" to 8
• SvtAv1EncApp: Adjust default value for "--hierarchical-levels" (#1546)
• SvtAv1EncApp: Add value "2" to "--fast-decode" parameter
• SvtAv1EncApp: Add "--noise-norm-strength" parameter
• SvtAv1EncApp: Add "--kf-tf-strength" parameter
• SvtAv1EncApp: Rename "Logical Processors" to "Level Of Parallelism"
• x265: Fix overwriting of set up VBV values when loading a source file (#1539)
• x265: Adjust new default values for Medium Preset
• x265: Fix default value for "--limit-tu" for VerySlow Preset
• x265: Remove deprecated parameters (#1544)
• Update tools
  • aomenc v3.11.0-145-gc1bcb109d4-x64-msvc1942
  • DoVi_Tool v2.1.3
  • FFmpeg v7.2-dev-N-118074-x64-gcc14.2.0
  • HDR10Plus_Tool v1.6.1
  • MediaInfo v24.12
  • MKVToolNix v88.0
  • MP4Box v2.5-DEV-rev964-ga3c626300-x64-msvc1942
  • NVEncC v7.77
  • Python v3.12.7
  • qaac v2.83
  • QSVEncC v7.75
  • rav1e v0.7.0 (p20241015)-x64-msvc1942
  • Subtitle Edit v4.0.8
  • SvtAv1EncApp v2.3.0-1+12-7ae833c2-.Mod-by-Patman.-x64-msvc1942 [SVT-AV1-PSY]
  • VapourSynth R70
  • VCEEncC v8.24
  • vvencFFapp v1.13.0 r295-0c2c21e
  • x264 v0.164.3198+7-bf259fa-.Mod-by-Patman.-x64-gcc14.2.0
  • x265 v4.1+54+9-0c07fe364-.Mod-by-Patman.-x64-avx2-msvc1942
  • Update AviSynth+ plugins
  • DePan v2.7.46
  • DePanEstimate v2.7.46
  • MVTools2 v2.7.46
  • Update Dual plugins
  • BestSource R8
  • Update VapourSynth plugins
  • AVISource R1

Tip
If you want to keep StaxRip alive, support its development, get early access to new releases or just say thanks, please consider visiting:
Static Badge Static Badge Static Badge

[Stupido]

v2.44.1 released by Dendraspis (2025-01-01)
https://github.com/staxrip/staxrip/releases/tag/v2.44.1


Note
Special thanks to all supporters, especially the few Patreon members, who have been instrumental in making this version available for you! ❤️

🎆 Happy New Year 🥂 🍾
You have the opportunity to be part of something special. Last year on New Year's Day I have released v2.31.0, so with this release we are starting a new tradition. All you have to do is to download the new release, extract and start it - copying the old Settings folder over is optional. Then you're part of that magical moment. 🥳

TL;DR: Have fun 😅


Tip
If you want to keep StaxRip alive, support its development, get early access to new releases or just say thanks, please consider visiting:
Static Badge Static Badge Static Badge


Changelog:

• General: Fix Haali Splitter package
• General: Fix Package status check
• General: Disable Dolby Vision metadata extraction for non-HEVC files (#1553)
• General: Add "Convert bit depth to 10-bit" option
• Adds a filter to change the bit depth to 10-bit if the source file has a different bit depth
• Audio: Fix Normalize with Channel change for Opus (#1569)
• Audio: Fix hidden errors while cutting audio with mkvmerge (#1525)
• Audio: Override Track Name if specified in template (#1487)
• UI: Change source and target length format to HH:mm:ss
• UI: Fix crash and/or missing text when using Thumbnailer
• UI: Fix missing Assistant warning for no audio
• UI: Make Audio editing window taller
• MP4Box: Fix default tag for audio tracks and subtitles (#1530)
• NVEncC: Add "--vpp-libplacebo-deband" parameter
• NVEncC: Add "--vpp-libplacebo-tonemapping" parameter
• QSVEncC: Add new value "libplacebo" for "--vpp-resize" parameter
• SvtAv1EncApp: Add "--ss" parameter (#1556)
• SvtAv1EncApp: Fix "--lp" parameter (#1556)
• SvtAv1EncApp: Fix "--pin" parameter (#1556)
• SvtAv1EncApp: Add value "2" to "--enable-tf" parameter
• SvtAv1EncApp: Add "--psy-rd" parameter
• SvtAv1EncApp: Apply new default value of "1" to "--sharpness" parameter
• Update tools
  • ffmpeg v7.1-dev-N-116758-x64-gcc14.2.0
  • MKVToolNix v89.0
  • Python v3.12.8
  • Subtitle Edit v4.0.10
  • SvtAv1EncApp v2.3.0-A-0+15-5ea471e2-.Mod-by-Patman.-x64-msvc1942 [SVT-AV1-PSY]
  • vvencFFapp v1.13.0 r298-81a3b6c

Important
If you're an SvtAv1EncApp user, please check your settings as the new version brought some new (default) values.
You also have to pay attention to a current bug in SVT-AV1-PSY, which causes SvtAv1EncApp to crash on (s)lower presets in case the source (and target) file is 8-bit.

[ChillyWonka]

I think I've googled sufficiently to say it doesn't exist, but doesn't hurt to ask: Is there any existing way I could convince existing StaxRip releases to add the "-no-check" parameter to any MP4Box command line it needs to generate when demuxing?

I've encountered more than one MP4 container which ends up throwing error, specifically about "not enough bytes in box colr: 6 left, reading 7":

StaxRip.ErrorAbortException: MP4Box 2.5-DEV-rev1021-g49a598895-x64-msvc1942

[isom] not enough bytes in box colr: 6 left, reading 7 (file H:\repos\gpac\src\isomedia\iff.c, line 226) - try specifying -no-check (might crash)
[iso file] Read Box "colr" (start 10855184763) failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "avc1" (start 10855184623) failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "stsd" (start 10855184607) failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "stbl" (start 10855184599) failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "minf" (start 10855184535) failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "mdia" (start 10855184450) failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "trak" (start 10855184314) failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "moov" (start 10855184198) failed (Invalid IsoMedia File) - skipping

Which stops any further processing. In my particular instances, the MP4 files play fine as-is, and even the demux generates valid exports of all the track types when I manually figure out the needed MP4Box commands and then add "-no-check". I'm about to do it for a second time, so I just wanted to ask whether StaxRip might already have a way to add this without me manually doing the work to demux the MP4.

If it's not already there, does this seem worthy of me making a bug in the tracker, or is there a better place for "enhancement requests." Clearly for any MP4 I'm in control of generating, I would instead want to solve why the generated MP4 isn't valid. But for users of StaxRip receiving an MP4 which they can't otherwise "fix", perhaps having the "use -no-check" option would save them some grief and let StaxRip help them potentially get past the issue.

Oh, the idea didn't come to mind until writing this: Can I get StaxRip to reveal all the demux command lines it intends to generate for the current file? Because that's really "the issue"; because StaxRip processing aborts on the first demux command line that fails, I can't just "look at the StaxRip log" to see all the command lines needed and add -no-check to them to run them manually myself. Only the first failed command line is in the log. StaxRip is willing to show me the command lines for the encodings it intends to perform, but if it will preview me the demux command lines, I've missed it.

[Stupido]

You can add a custom demuxer in the settings, but could be difficult. Otherwise make a feature request.

[EmmePi]

Does anyone know of any video filters and/or settings to use to correct videos that saturate the color towards red?
Thanks

[LigH.de]

Knowing the reason for wrong chrominance is the most important first step to a solution...

You mention a reddish tint, so my guess is that it might be a wrong colorimetry (Rec. 601 vs. 709); but seeing your material may be useful to estimate if that reason is probable at all.

The Avisynth filter "ColorYUV" has a lot of functions to change colors, especially the U (Cb) and V (Cr) balance. But which and how much is hard to guess without knowning your video.

[EmmePi]

Knowing the reason for wrong chrominance is the most important first step to a solution...

You mention a reddish tint, so my guess is that it might be a wrong colorimetry (Rec. 601 vs. 709); but seeing your material may be useful to estimate if that reason is probable at all.

The Avisynth filter "ColorYUV" has a lot of functions to change colors, especially the U (Cb) and V (Cr) balance. But which and how much is hard to guess without knowning your video.

Especially in the darker scenes you can see the shift towards red, however the whole video has an unnatural color saturation.
If you tell me where I find the Avisynth "ColorYUV" filter and those settings, I'll do some tests to see if it improves.

[LigH.de]

It is a core filter.

AviSynth+ ReadTheDocs: ColorYUV

But you can find more interesting details about RGB/YUV conversion and colorimetry (also the ColorMatrix plugin) here:

AviSynth+ ReadTheDocs: Colorimetry

[EmmePi]

I found this, is it the right one?
Thanks for your patience and help...
[Attachment 84997 - Click to enlarge]

[EmmePi]

If I wanted I could try to increase the brightness... trying it in playback with KMPlayer it is definitely better and the red color fades,
But also this, in Staxrip how do I set the output with a higher brightness level?

[LigH.de]

I found this, is it the right one?

You may not win by relying on automatic methods, it may require manual parameters, editing the generated script in a text editor.

Regarding "brightness": You may not even mean brightness, maybe rather gamma instead. I can't recommend you anything without having your material.

[EmmePi]

I found this, is it the right one?

You may not win by relying on automatic methods, it may require manual parameters, editing the generated script in a text editor.

Regarding "brightness": You may not even mean brightness, maybe rather gamma instead. I can't recommend you anything without having your material.

I solved it from here:


[Attachment 85067 - Click to enlarge]

[EmmePi]

Now instead a million dollar (virtual) question:
I should convert several films that I have on DVD to .mkv, trying to improve their quality, perhaps upscaling to 1080p
I have never found how to upload them to Staxrip, it seems to me that it does not digest .vob files
Is there some procedure and particular settings to do this?

[Stupido]

AFAIK you must open or drag&drop the video files all together.
VTS_*_1.vob, VTS_*_2.vob, ...

PS: virtual means Bitcoin?

[LigH.de]

Decades of experience of converting DVD Video content ignored and forgotten... It all starts with reading the main movie PGC out of the VOB files sequence, using the information stored in the IFO files along with them. That's the job of a good DVD ripper. The video converter comes second.

One of the best DVD rippers in this generation is makeMKV. It can read the main movie PGC to a whole linear MKV file, perfect as input for converters like StaxRip.

[rondobeats]

Hello everyone, I have some problem when encoding DV/HDR content. Source file has Dolby Vision & HDR10+ and I want to keep that while encoding to lower bitrate using NVEnnC (hardware encoder). Extraction of both Dolby RPU and HDR10Plus metadata went without any issue but my final file appeared to be grey-ish and not displaying HDR10+ colors correctly. I played both, source and output, files on my phone which supports HDR10+ playback and source file has vivid colors while my encoded file looked grey and washed out.

You can see the comparison here: https://slow.pics/c/jcylWa2c?canvas-mode=fit-width

This is the mediainfo for both files:

Source file

General
Unique ID : 18413228603565579808705897170982220522 (0xDDA4242F2B04E83391DD21950D932EA)
Format : Matroska
Format version : Version 4
File size : 18.9 GiB
Duration : 1 h 49 min
Overall bit rate : 24.7 Mb/s
Frame rate : 23.976 FPS
Encoded date : 2025-06-18 23:14:06 UTC
Writing application : mkvmerge v91.0 ('Signs') 64-bit
Writing library : libebml v1.4.5 + libmatroska v1.7.1

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@High
HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 49 min
Bit rate : 23.9 Mb/s
Width : 3 840 pixels
Height : 1 606 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 23.976 FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.162
Stream size : 18.4 GiB (97%)
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : BT.2020
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 956 cd/m2
Maximum Frame-Average Light Level : 381 cd/m2

Audio
ID : 2
Format : E-AC-3 JOC
Format/Info : Enhanced AC-3 with Joint Object Coding
Commercial name : Dolby Digital Plus with Dolby Atmos
Codec ID : A_EAC3
Duration : 1 h 49 min
Bit rate mode : Constant
Bit rate : 768 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 603 MiB (3%)
Language : English
Service kind : Complete Main
Default : Yes
Forced : No
Complexity index : 16
Number of dynamic objects : 15
Bed channel count : 1 channel
Bed channel configuration : LFE

Encoded file

General
Unique ID : 6089208462259403397101721693313322347 (0x494BD27FE6ED020EDE1B7F1F2D84D6B)
Format : Matroska
Format version : Version 4
File size : 6.60 GiB
Duration : 1 h 49 min
Overall bit rate : 8 608 kb/s
Frame rate : 23.976 FPS
Encoded date : 2025-07-03 20:29:09 UTC
Writing application : mkvmerge v93.0 ('Goblu') 64-bit
Writing library : libebml v1.4.5 + libmatroska v1.7.1

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 49 min
Bit rate : 7 838 kb/s
Width : 3 840 pixels
Height : 1 606 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.053
Stream size : 6.01 GiB (91%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : BT.2020
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 956 cd/m2
Maximum Frame-Average Light Level : 381 cd/m2

Audio
ID : 2
Format : E-AC-3 JOC
Format/Info : Enhanced AC-3 with Joint Object Coding
Commercial name : Dolby Digital Plus with Dolby Atmos
Codec ID : A_EAC3
Duration : 1 h 49 min
Bit rate mode : Constant
Bit rate : 768 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 603 MiB (9%)
Language : English
Service kind : Complete Main
Default : Yes
Forced : No
Complexity index : 16
Number of dynamic objects : 15
Bed channel count : 1 channel
Bed channel configuration : LFE

Here are my NVEnnC settings that were used for encoding

--qvbr 20 --codec h265 --preset p7 --output-depth 10 --profile main10 --multipass 2pass-full --vbv-bufsize 16500 --max-bitrate 8250 --lookahead 32 --master-display "G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,1 6450)L(10000000,1)" --dhdr10-info FOLDER_TEMP\HDR10PlusMetadata.json --dolby-vision-profile 8.1 --dolby-vision-rpu FOLDER_TEMP\HDRDVmetadata.rpu --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --atc-sei undef --max-cll "956,381" --chromaloc 2 --aud --repeat-headers

*FOLDER_TEMP - this is the temp folder that StaxRip creates during indexing stage. I always double check these setting and they always correspond to the source file.

I really don't know what issue is, what can I do (if anything) to fix it or what should I do in the future when encoding to prevent this from happening and correct colors to be displayed.

If I am missing any important information please ask me and I'll provide it. Thank you all in advance!

[Spunkmeyer]

Format profile : Main 10@L5@High vs Format profile : Main 10@L5@Main in the encoded file is one difference I can see straight off.

Whether that is enough to cause the problem I don't know.

[priest31]

hi everyone! from 2.46.3 staxrip gui didn't start at all. what might be a reason? win11 64
thanx