StaxRip

[Revan654]

Thanks Revan654 for the updates




+1 for that

there must be a way, theres only two master display line possible.


i dont know if its possible but maybe something like this:

-When mediainfo Mastering display color primaries say Display P3 then tell staxrip to set
G(13250,34500)B(7500,3000)R(34000,16000)WP(15634,16450)

-When mediainfo Mastering display color primaries say Bt2020 then tell staxrip to set
G(13250,34500)B(7500,3000)R(35000,16000)WP(15634,16450)

Display Luminance data are still reported by the newer mediainfo.




*Also, could it be possible to add some kind of CRF estimator/ calculator like Bd-Rebuilder ?

The Master-Display should be set to monitor it was graded on. It will usually be within BT.2020 Range. P3 is not considered a proper HDR colorspace by many. Even Youtube refuses to enable HDR if you upload P3. just a small warning about that.

I've never used BD-Rebuilder not sure what that looks like or how it works.

I could add checking line and it would have to pass both sets to be enabled.

If Mediainfo returns BT.2020 = Pass, Now Check Luma if passed send BT.2020 Master-display data to codec.

The results would auto load adding BT.2020 Master-Display data to text box in the codec settings. of course this would only work with BT.2020 space anyone who tries to use P3 will will not pass the check.

Right now it tries to reads the full Master-Display line, Which is completely missing. So it fails everytime. I have no idea why mediainfo removed it. I tried to get them to add it back but never got reply back or it got buried in the massive thread about HDR.

[Revan654]

Revan,

I did take the --check-- features option with qsvencc 1.06.exe and there were a lot of options available for my processor
Also other software works wher i can choose f.i la -icq (xmedia recode) but has other flaws...

Staxrip did'nt update qsvenc anymore after 2.75 and last 5-6 months i guess (not for sure) and therefore the gui of intel h265 (qsvenc) does not contain the options now available
It is really outdated and should be upgraded with the latest options to choose from....H265 is the next move in encoding and would really improve...it is as important as the nvencc...most computers have now the availability of hardware encoding with lightning fast encode time and quality

QSVENCc settings and switches have been updated, It's one of first things I updated in the core settings. Documentation does not match the source code. If I add X switch from the Documentation it does not work when you enable the flag.

I would add the colorspace switches for 2020 and see if it runs. So far no one can get the newer version to run with BT.2020.

Some changes and updates to the switches some many not be visible to the outside. Many of the hardware encoders are still missing many import flags. It still comes down to Software vs Hardware encoder debate which I'm not going to touch.

I do tests outside of staxrip first to see if it runs, if it fails I know it's not in the source code yet or was cut. Allot of this is out of my hand and have no control over it.

Adding new switches and such is easy enough for me. Maybe list what switches you want added and I'll look into it.

[mparade]

Create a profile for HDR is the easiest way, The only thing that doesn't autoload in the VUI is the Master-Display data. Due to mediainfo and that data changes from monitor to monitor.

Thanks, but I think without Master-display data in the output
there will be a risk for my HDR TV not to dispay the video correctly. Don't you recommend to replace the new medianfo with the old one?

[Revan654]

Thanks, but I think without Master-display data in the output
there will be a risk for my HDR TV not to dispay the video correctly. Don't you recommend to replace the new medianfo with the old one?

Never said you shouldn't include it, Just saying it doesn't auto-load.

The old one gave bad data readouts when it came to HDR10.

[mparade]

Never said you shouldn't include it, Just saying it doesn't auto-load.

The old one gave bad data readouts when it came to HDR10.

Thanks, so there is no any workaround yet. : (

[Revan654]

Thanks, so there is no any workaround yet. : (

No, Since it tries to read the data from mediainfo, since the data isn't there so it fails everytime.

I could add default values for BT.2020 and other HDR colorspaces. However if it's off by one number it will fail.

I can't use the encoding settings since it can be completely missing from the metadata (Studios remove this data). I have a habit of removing it as well.

I would contact mediainfo and ask them to add the coordinate system for colorspace(HDR). If there enough interest, they will add it. I did ask them to add it but dev just stopped replying to the post.

I would run the file through mkvinfo and see if it's even output the coordinates. Sometimes that data isn't even in the core metadata but found elsewhere this is specially noticeable with studio releases.

I will do some testing to see what can be done but for now I would just create a codec profile and use that until mediainfo adds the feature.

Media Info:

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

Mediainfo(Even when I inject custom coordinate by other software, It remains unchanged):

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

MKVInfo(How it should be showing up):

https://i.imgur.com/81l2jSAl.jpg

[mparade]

Maybe the answer is that most of/all the displays will not need those values at all to display the content correctly:

"… Metadata Usage
• Some TVs ignore metadata and don’t use it when present entirely (even when they state support for ST.2086) • Some TVs ignore metadata when present and assume own values for MaxCLL/MaxFALL/Mastering Display Peak Luminance (i.e. 1000nits) • Some TVs prioritise MaxCLL over Mastering Display Peak Luminance (i.e. ignore Mastering Display Peak value) • Some TVs prioritise Mastering Display Peak Luminance (i.e. ignore MaxCLL) • Some TVs use the higher of the two values of MaxCLL / Mastering Display Peak Luminance • Some TVs use MaxCLL only if lower than Mastering Display Peak Luminance. • Some TVs assume Metadata MUST be followed at all times and respond accordingly • Some TVs undertake processing of video frames to determine own values for MaxCLL, MaxFALL on a continual basis • Some TVs use combinations of above strategies “Metadata MAY be used by the display Then again it MAY NOT”


What about making use of the info resulting from MKVInfo instead of the ones from Mediainfo and calculate from them the ones that can be feeded into x265 command line?

[SKPN]

Hey everyone,

I apologize if this has been asked before; I did a search of this thread, but didn't see anything for what I'm trying to do.

Is there any way to auto-generate chapters in a video to line up with where a video is cut? Basically, I have a 35 minute video. I cut out 4 separate sections, leaving me with a 21 minute video. I'd like to add chapters to line up with each individual section from cut to cut. Is this something that can be done via Staxrip?

[gonca]

MediaInfo 17.10 still shows the coordinate system.
It was after this version that it was changed

[dvd_maniac]

I'm having an issue trying to encode a video file.
Can someone explain what the issue is and/or offer a resolution?


Error Demux audio using MP4Box 0.7.2-DEV-rev79 (1.7.0.0)
Demux audio using MP4Box 0.7.2-DEV-rev79 failed with exit code: 1 (0x1)
The exit code might be a system error code: STATUS_WAIT_1
The exit code might be a system error code: Incorrect function.

--------------- Demux audio using MP4Box 0.7.2-DEV-rev79 ---------------

C:\StaxRip\Apps\MP4Box\MP4Box.exe -single 2 -out "T:\PlayOn\Stargate SG-1\Season 1\Stargate SG-1 -..._temp\Stargate SG-1 - s01e01 - Children of the Gods, Part 1 ID1.m4a" "T:\PlayOn\Stargate SG-1\Season 1\Stargate SG-1 - s01e01 - Children of the Gods, Part 1.mp4"

[iso file] Read Box "tx3g" failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "stsd" failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "stbl" failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "minf" failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "mdia" failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "trak" failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "moov" failed (Invalid IsoMedia File) - skipping
Error opening file T:\PlayOn\Stargate SG-1\Season 1\Stargate SG-1 - s01e01 - Children of the Gods, Part 1.mp4: Invalid IsoMedia File

StaxRip.ErrorAbortException: Demux audio using MP4Box 0.7.2-DEV-rev79 failed with exit code: 1 (0x1)

The exit code might be a system error code: STATUS_WAIT_1

The exit code might be a system error code: Incorrect function.

--------------- Demux audio using MP4Box 0.7.2-DEV-rev79 ---------------

C:\StaxRip\Apps\MP4Box\MP4Box.exe -single 2 -out "T:\PlayOn\Stargate SG-1\Season 1\Stargate SG-1 -..._temp\Stargate SG-1 - s01e01 - Children of the Gods, Part 1 ID1.m4a" "T:\PlayOn\Stargate SG-1\Season 1\Stargate SG-1 - s01e01 - Children of the Gods, Part 1.mp4"

[iso file] Read Box "tx3g" failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "stsd" failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "stbl" failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "minf" failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "mdia" failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "trak" failed (Invalid IsoMedia File) - skipping
[iso file] Read Box "moov" failed (Invalid IsoMedia File) - skipping
Error opening file T:\PlayOn\Stargate SG-1\Season 1\Stargate SG-1 - s01e01 - Children of the Gods, Part 1.mp4: Invalid IsoMedia File

at StaxRip.Proc.Start() in D:\Projekte\VS\VB\StaxRip\General\Proc.vb:line 338
at StaxRip.MP4BoxDemuxer.Demux(String sourcefile, AudioStream stream, AudioProfile ap, Project proj) in D:\Projekte\VS\VB\StaxRip\General\Demux.vb:line 601
at StaxRip.MP4BoxDemuxer.Run(Project proj) in D:\Projekte\VS\VB\StaxRip\General\Demux.vb:line 471
at StaxRip.MainForm.Demux() in D:\Projekte\VS\VB\StaxRip\Forms\MainForm.vb:line 3119
at StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean isEncoding) in D:\Projekte\VS\VB\StaxRip\Forms\MainForm.vb:line 1962

[DaMacFunkin]

Hi where do we download the latest developed versions? Are these still on the front page are are they somewhere else now the project has forked?

Thank you.

[Yanak]

Hello, last "stable" release is here 1.7.0.0 :
https://github.com/stax76/staxrip/releases

Latest "test" version released by Stax76 is here 1.7.0.6 :
https://github.com/stax76/staxrip/blob/master/changelog.md

1.7.0.6 have no issues for me and is my main version.

@dvd_maniac :
hard to say what this error is, seems like MP4box have troubles , try to do a manual demuxing using FFMPEG :
Go to Tools > Advanced > Demux,
pick your video file and select an output folder, press OK, in the next dialog select FFmpeg as demuxer to see if it can extract audio and video tracks.

If it works then you just need to import audio and video tracks separately in your project.

PS : sometimes Staxrip have issues with input files and paths being too long, renaming the input video for a shorter name does the trick, not sure if it's the problem encountered here tho.

[Zetti]

#DaMacFunkin

Revan654 have created a fork.

GitHub Page:
https://github.com/Revan654/staxrip/

GitHub Release Page:
https://github.com/Revan654/staxrip/releases

[dvd_maniac]

@Yanak

Manual Demuxing works.
Going to be time consuming rather than simple batch mode since I have about 130 of these files to do... :(
But at least I can now do it...

Thanks.

[Yanak]

Do all your MP4 files fail when trying to be demuxed by MP4Box ? I mean did you done a few more tests on some other of those 130 files and all resulted in the same type of error ?

Maybe you should try to replace MP4Box.exe by a more recent version, maybe you have an old one and it have some issues, hard to say but it won't be the first time it happens.

Edit : this is the one i use, self compiled not long ago, MP4Box version 0.7.2-DEV-rev563-g3096514bb-master : https://www99.zippyshare.com/v/L1YIQVvP/file.html
Try to replace it by the version you have inside staxrip, located here "\StaxRip\Apps\MP4Box" to see if it makes any difference.

Also did you tried to rename the mp4 file for something with a much shorter name like "video.mp4", just for testing purpose.


If still wrong you can try this if you use staxrip in automatic mode :

- Go to Settings > Preprocessing
- Select the MP4Box line and click the edit button, remove the mp4 extension from the " mp4 m4v mov" list
- Then go to the "FFmpeg: Demux", edit button, and this time you add mp4 there, list will look like this "avi flv mp4"

After this in automatic mode all .mp4 files should be directly demuxed by ffmpeg instead of MP4box that gives the error.

This is for the automatic mode, you can also select manual mode as source (and save it as startup template too), there you will be prompted when opening a file and you will just have a single click to do on FFmpeg in the list.

Any of those 2 will be way easier and quicker than demuxing and importing all tracks manually.

@Zetti,

thanks for the info, i think i will have to take a look at this version, i had started to modify the sources too to add a few custom stuff and things i was missing but i'm not a coder so it takes time, too much time, lot of trial and errors :p , this will probably be easier ( and take a bit before importing all my changes and settings made in the program itself ) Thx.

[Yups]

Adding new switches and such is easy enough for me. Maybe list what switches you want added and I'll look into it.


There is no B-Pyramid Off option in the GUI. I can enable it, a unchecked checkbox means it is auto by the driver. I have to use the --no-b-pyramid command.

And you should update QSVEnc to 3.06 because with 3.05 I get some errors.

[dvd_maniac]

@Yanak
I tried renaming and placing file in a root drive folder (T:\test\test.mp4) and got the same issue.
I tried a dozen of the files and got the same error as well...
All the files were ripped the same way from the same streaming service so I expected the issue to be with all files.
I did however manage to figure out how to use a different demuxer and it is chugging away at the 130 videos nicely.
The only real problem now is that it is tipping me over the edge to build a new PC equipped with a nice threadripper.
5820K 6-core @4.4Ghz is nice but this is still going to take days to encode X265 @720p with decent quality settings...

[Yanak]

All good then :)
did you tried to upgrade the MP4Box.exe, either by the one i linked or any other one available on the net, to see if a newer version cause less issues with your videos ?

As for the upgrade i feel you, I'm still on a 3770k... But pockets broken for a proper upgrade so I'll have to wait and hope for better days...

[dvd_maniac]

I did not try to upgrade and I'm fine with the current fix.
I'll switch back to mp4box as soon as I am done with these videos.
About 90 videos still left... :(

Another question I had that someone can hopefully answer:
On previous versions of StaxRip, the encoded video created a temp folder that was not shared by other encoded video and the folder name was the complete name of the video file without the extension.
I do a lot of automated stuff through batch files using the filename as a variable and I used to be able to check the temp folders for subtitles, save them off and then delete them using this variable but now I can't. The temp folder is only a truncated version of the filename now.
Is there a way to go back to using the full filename as the temp folder name?

[Yanak]

No worries, i think it is something that was fixed in MP4box 3 or so months ago with some files being .mp4's but having some .mov tags inside them causing MP4box to loose it's mind and crash, was just by curiosity :p

For the question :
With an empty project ( Staxrip started, no videos added ) :

Go to Options > Paths

in the last field "Temp Files Folder" click the little arrow on the right side, select "Source File Directory" , it will add this in the field:
%source_dir%%source_name%_temp

Then you need to save this as template, it's part of the project options, not the general options, if you don't save it as part of the template settings it won't stick with the next video/project you will add in Staxrip.

Go to: Project > Save as Template
either override existing one, in your case i think it is "Automatic Workflow" that will be already filled, or create a new one and set it as startup template ticking the little box in the popup dialog.


But one thing to keep in mind when using this :

if the result path is too long, i think it's a problem happening when there is more 256 or 260 characters in the ending path, you will see errors reported by tools not able to access the files, keep in mind that the path will be like "path-to-the-input-video/name-of-the-inputvideo_temp/" and can be very very long when files are located in a lot of sub-folders and to make it worse the videos often have very long names...

Myself i use the videos full name for the temp folders but inside a static "Temp" folder at the root of one of my drives to reduce the length of the paths and limit the risks of errors due to long paths, this way i can already shorten it a bit, my temp folder path is :
H:\TEMP\%source_name%_temp\

https://i.imgur.com/mIoZSUb.png

All my staxrip temp folders will be "NameOfTheInputVideo_temp" and all will always be located inside the "H:\TEMP" main folder instead of being inside the source video folder ( i prefer it this way , easier than looking in the videos folders )

And even like this with videos having a very long name i manage to have errors when adding a video to the project, It's rare but happens sometimes, for those i have to rename them for a shorter name to fix it, but i know it and when Staxrip throws me and error directly when input a video file having a long name i know i have to rename it :p

[dvd_maniac]

I think the lengths will be fine in my case as I drop my automated encodes directly to D:\Videos\Encode
I never used to have an issue with crashes due to path lengths before so I should be fine.
Thank You very much... :)

After spending so much time automating my process and then having to do manual work again was getting tedious...

[Yanak]

My encoded files go the root of another drive but this ain't the problem, in my case using H:\TEMP\ for all videos temp folders the limit of characters a video input name can have is around 114, ( i don't recall exactly but it's more or less 114 ), without the file extension just the tittle itself, 114_Characters_long_tittle.mp4 for example, because in the end the paths will be :

"H:\TEMP\114_Characters_long_tittle_temp\114_Characters_long_tittle_new_source.avs" for the avs script of Staxrip,

path length should be around 256 characters in this example, ( and funny enough the entire above line is 114 characters long, to put this in perspective ) :p


if my video name was longer it will end up in errors and I'll have to rename it for something a bit shorter to make it work :p

Anyways, glad to have helped a bit and to see this sorted :)

[Revan654]

snip

I would try a different demuxing program for pre-process. It seems like Mp4Box isn't getting along with your video file.

[Yups]

There is an GUI issue in Staxrip with the CQP bitrate mode for Quicksync with main10 profile. Staxrip goes up to CQP 51. The problem is that for main10 Intel allows up to CQP 63. Staxrip GUI doesn't allow higher than 51.

[paauw]

Can anyone explain why i have to demux and index before i encode x264 to HEVC ?

Can i skip one step ?

Why is de mkvextract so much faster than the dgindexnv or dgindexIM ?

I have i5 6400, MSI GTX960 and Intel HD530...

the encoding is fast with hardware accelaration but not the index/remux with dgindexnv/im

[NikosD]

Those have already been added. The new version has introduced some issues as well. Mainly with QSVEnc, The documentation is either faulty or code is buggy. It's having problems processing certain colorspace.New versions for QSVEnc v3.07 and NVEnc v4.08

QSVEnc:

- Fixed --audio-file not working properly.
· Added missing options for --colorprim and --transfer etc.
· Improved --input-analyze effect.
- Improvement that - vpp - deinterlace does not work on raw output.

NVEnc:

Fixed --audio-file not working properly.
· Improved --input-analyze effect.
· Improved stability when specifying SAR.

[frenchfries]

New versions for QSVEnc v3.07 and NVEnc v4.08

QSVEnc:

- Fixed --audio-file not working properly.
· Added missing options for --colorprim and --transfer etc.
· Improved --input-analyze effect.
- Improvement that - vpp - deinterlace does not work on raw output.

NVEnc:

Fixed --audio-file not working properly.
· Improved --input-analyze effect.
· Improved stability when specifying SAR.

Hey

First, I just wanted to say that I've been using Staxrip since the beginning so I'm glad someone took it on after Stax76 left.

Awesomely, the new version of QSVEnc seems to add the missing pieces for full HDR support.

Command line is annoying though, so can you add the missing bits to the GUI? Specifically, Max CLL and FALL, min/max luma, updated color matrixes, display primaries? Might be something I've forgotten.

As I'm sure you're aware the updated switches are detailed in an empty run of QSVEnc.exe but see below for an excerpt


--colormatrix <string> undef, auto, bt709, smpte170m, bt470bg
smpte240m, YCgCo, fcc, GBR, bt2020nc
bt2020c
default: undef
--colorprim <string> undef, auto, bt709, smpte170m, bt470m
bt470bg, smpte240m, film, bt2020
default: undef
--transfer <string> undef, auto, bt709, smpte170m, bt470m
bt470bg, smpte240m, linear, log100, log316
iec61966-2-4, bt1361e, iec61966-2-1
bt2020-10, bt2020-12, smpte2084, smpte428
arib-srd-b67
default: undef
--aud insert aud nal unit to ouput stream.
--pic-struct insert pic-timing SEI with pic_struct.
--chromaloc <int> set chroma location flag [ 0 ... 5 ]
default: 0 = unspecified
--fullrange set stream as fullrange yuv
--max-cll <int>,<int> set MaxCLL and MaxFall in nits. e.g. "1000,300"
--master-display <string> set Mastering display data.
e.g. "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)"

Thanks again for taking this one on.

[Zetti]

FFmpeg v4.0.1 is released.

[Zetti]

MKVToolNix v25.0.0 is released.

[mparade]

No, Since it tries to read the data from mediainfo, since the data isn't there so it fails everytime…...

The resulted dgi file contains all the HDR info required by the encoder. If StaxRip read out the infos from this file, that would be great! Right now, one should manually read out and insert them.

[NikosD]

New QSVEnc v3.08

In order to pass options to the audio encoder.
Example: - audio - codec aac: aac_coder = twoloop

so that profiles can be specified during speech encoding. (- audio-profile)

· Added option to specify tier of HEVC. (- tier)

· Slightly reduced memory usage at high bit rate.

· Improved to be incomplete frame rate in case of variable frame rate and so on.

· Improved synchronization when audio starts first.



New NVEnc v4.09

Now --audio-codec can have option to audio encoders.
Example: --audio-codec aac:aac_coder=twoloop

Slightly reduce memory usage, especially encoding with high bitrate.

Add option to add padding to videos. (--vpp-pad)

Improve frame rate detection.

Improve avsync, especially when video has delay.

Add option to specify audio profile, but most of the time it is unnecessary. ( --audio-profile )

[thomy21]

@Revan654

Please also update the x264 to the latest version with the next update: 2901

Thanks and great for developing Stax.

[lansing]

I was trying out this program but couldn't even successfully load a vapoursynth script. It always returns the error "core is not defined". I searched and found the same complain (https://github.com/stax76/staxrip/issues/51) 2 years ago on the project page. I guess it hasn't been fix for 2 years.

I investigated myself and found that every time I load a vpy script, it will auto create a temp folder and duplicated my script to a temp vpy script with some lines added on the top and the program will run that temp script instead. And that's where the problem came from. From the added lines, there's a few calls to core.std but on top of those calls there is no declaration of the vs object or the core...that's why the "core is not defined" error. This is just so silly.

[stax76]

Hi everybody,

it's time for me to leave staxrip, shall the gods decide about it's future, I'm out, PEACE!

[NikosD]

Hope everything is fine for you Frank regarding StaxRip and in general.

Many, many thanks for your time and effort, fixing bugs, replying posts and fulfilling requests.

You were acting as a good paradigm of a developer for the rest to follow.

Have fun whatever you do!

[Yanak]

Hi Stax,

Sad to hear that, still had a tiny hope you will come back to it one of those days.

Thanks a lot for this fantastic tool, thanks for all the help and support you provided, thanks for answering my too numerous questions or requests, thanks for all the things you made me learn while messing with Staxrip, like powershell scripting that i use more often now.

Staxrip is a great tool with a lot of customizations possible, it's really not common nowadays to see such program versatility and open possibilities for the end user to customize it to it's needs or even add some stuff to it while not being it's primary usage, this tool is really outstanding for that.

A big thank you for all Stax, wish you the best for whatever you will do in the future.

[mcjordan]

Frank, I feel deep regret that you leave us. But I fully understand you.
As time goes on, I have less and less time to deal with my favorite things.
You will remain in my heart with your responsiveness and altruism.
Thank you for everything you did for us!

[dev84]

Thank You Frank for years of hard work, i wish You all the best.
You can be sure that Your software will be used for many years to come.

[Lynx_TWO]

So sorry to see you go Stax! Any chance you'll be working with the new dBpoweramp Video Converter? You'd bring a lot of experience to the table with them :)

:thanks:

[Digga]

it's time for me to leave staxrip, shall the gods decide about it's future, I'm out, PEACE!I'd like to thank you for the work you put in this project, I have been a longtime user... your work is and was very much appreciated!
IMHO, the GUI is very nice and suits my needs as an educated user (though no pro) in most ways, so thanks again!

Please also update the x264 to the latest version with the next update: 2901you can easily and without fear of breaking something replace the x264 codec manually by yourself. I've done this a few times already to be up to date with newer encoder versions.
to do so, just replace the executeable located in 'path-to-StaxRip\Apps\x264'. you have to rename your new version to 'x264.exe' or 'x264-10bit.exe', depending on which version you are using (if you don't know which one, replace both, though you prolly are using the more common 'normal' 8-bit version then).
also, make sure to download and use the 64-bit version of x264, unless you are still using an older version of StaxRip with 32-bit support.
there are many places to get a newer version of x264, e.g. here:
http://download.videolan.org/pub/videolan/x264/binaries/win64/

for cosmetic reasons, you also may want to edit the version textfile located in 'path-to-StaxRip\Apps' scroll down untill you see 'x264' there on the left and edit the version number on the right to '0.155.2901 8-Bit'. otherwise, the encoding window will still display the older version number IIRC.

[Zetti]

FFmpeg v4.0.2 is released.

[Yanak]

@Digga : you can edit the version directly from Staxrip ,
go to tools > apps > manage
on the top left in the search field enter x264, select/highlight it on the list of results,
then on top of this window see "version", click on it, enter new version in the little popup and done.

Same for easily locating one .exe or plugin, just need to click on "Explore" at the top after selecting it on the list ;)

[Khun_Doug]

Enjoy your retirement Frank. It's one of the best jobs I ever had. Unlike me, I hope your retirement does not bring on a sense of boredom.

Revan654, are you still on the list? If so, do you plan to move forward, beyond the 1.8.2.0 release?

[NikosD]

I would try a different demuxing program for pre-process. It seems like Mp4Box isn't getting along with your video file.

Hello.

Your last post here is three weeks ago.

Is everything OK with StaxRip support ?

Are you going to keep on developing on this project ?

You seemed very determined in the beginning and full of energy.

I hope everything is fine.

[NikosD]

New NVEncC v4.10

Now progress info shown by NVEncC will consider --trim option.

Avoid freeze with some environments which has OpenCL API causing crush.

[Lynx_TWO]

Staxrip Updates (https://1drv.ms/u/s!Aoz5nDzevbl1k98RYy9KBrUT6rUvSw)

UPDATE 07/28/2018 - MP4Box, added required dlls to folder

7zip file, all you have to do is drag and drop the contents into your Staxrip folder and replace original files. The settings texts are there as well so you shouldn't need to manually update the settings in Staxrip.

Disclaimer: none of these have been tested so your mileage may vary with compatibility. :)

List of updates in this package:


APPS

AviSynth+ 2798 (you'll need to run and install this)
ffmpeg 20180726
FFTW 3.3.8
MediaInfo 0.18.05
mkvextract 25.0.0
mkvmerge 25.0.0
MP4Box 0.7.2-DEV-rev625
QSCEnc 3.08
NVEnc 4.10
ProjectX 0.91.0.10
qaac 2.67
x264 2901
x264 10-Bit 2851
x265 2.8+47


PLUGINS (avs)

masktools2 2.2.17
mClean 3.2
modPlus 2017-10-17
mvtools2 2.7.31
QTGMC 3.358s
RgTools 0.97
SMDegrain 3.1.2.100s
TIVTC 1.0.11


PLUGINS (both)

KNLMeansCL 1.1.1
VSFilterMod 11-12-2017


PLUGINS (vs)

d2vsource 1.1
mvtools 20
nnedi3 11
vcmod r24+ (2017)


RUNTIMES (you'll need to install these)

VapourSynth R44
Python 3.7

[Magik Mark]

Can somebody help decipher this:

Error Video encoding using x265 2.8+56 (1.7.0.6)

Video encoding using x265 2.8+56 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.


------------------- Video encoding using x265 2.8+56 -------------------

avs2pipemod[info]: writing 61619 frames of 24000/1001 fps, 1920x1080,
sar 0:0, YUV-420-planar-8bit progressive video.
y4m [info]: 1920x1080 fps 24000/1001 i420p8 unknown frame count
raw [info]: output file: NUL
x265 [info]: HEVC encoder version 2.8+56-613074c6714f
x265 [info]: build info [Windows][MSVC 1914][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 28 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 4 / wpp(17 rows)
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 2
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 / on / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 3 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : ABR-1500 kbps / 0.60
x265 [info]: tools: rd=3 ssim-rd rskip signhide tmvp strong-intra-smoothing
x265 [info]: tools: lslices=6 deblock sao stats-write
avs2pipemod[info]: finished, wrote 36 frames [0%].
avs2pipemod[info]: total elapsed time is 5.167 sec.
avs2pipemod[error]: only wrote 36 of 61619 frames.

at StaxRip.Proc.Start() in D:\Projekte\VS\VB\StaxRip\General\Proc.vb:line 338
at StaxRip.x265Enc.Encode(String passName, String commandLine, ProcessPriorityClass priority) in D:\Projekte\VS\VB\StaxRip\Encoding\x265Enc.vb:line 65
at StaxRip.x265Enc.Encode() in D:\Projekte\VS\VB\StaxRip\Encoding\x265Enc.vb:line 42
at StaxRip.GlobalClass.ProcessVideo() in D:\Projekte\VS\VB\StaxRip\General\GlobalClass.vb:line 225
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\VS\VB\StaxRip\General\GlobalClass.vb:line 137

[Khun_Doug]

Would you provide some additional information. For instance, please specify the filters and their order. Are you able to successfully preview the video? Are you using VapourSynth or AVS?

FYI, I recently had trouble with almost every encode that used SMDegrain. I wasn't able to determine the exact source. There were newer versions of AviAynth+ and masktool2. Updating both of those resolved the error and I can encode again. If you are using AVS please see if you have latest AviAynth+. Also check the revision(s) of your filters.

[NikosD]

Staxrip Updates (https://1drv.ms/u/s!Aoz5nDzevbl1k98RYy9KBrUT6rUvSw)


Adding latest versions of the tools/apps used by StaxRip is one thing, but adding the added functionality of those latest versions is another e.g new switches to QSVEnc & NVEnc GUI.

Haven't used latest StaxRip yet, I would like to know which case we are talking about with latest update.

[mironicus]

Hello,

I tried to encode a video with Staxrip using NVEnc on my laptop that uses Intel HD 630/NVidia GTX 1070 optimus. It does not work because I always get an error message. Also Intel hardware encoding (Intel H264/H265) is not working. Is there a problem that the computer uses two GPUs at the same time?

On my desktop with a single GTX 1050Ti it works.