StaxRip

[Atlantis]

I just tried video-compare. It's strange, I don't see the full picture. It's zoomed in.

[Atlantis]

So for the first time I played with HDR to SDR encoding and did a little test and I'm impressed how easy it is and how good the results look like. Used Staxrip Wiki. Thank you.

What gives better looks from these 3? I'm not much into tweaking too much. The shorter and easier the better.

1- DGReinhard()
2- DGHable()
3- DGHDRtoSDR(mode="pq", white=50)

For the short test I did, DGReinhard looks better.

[JKyle]

I just tried video-compare. It's strange, I don't see the full picture. It's zoomed in.

Maybe it's bug in video-compare itself.

So for the first time I played with HDR to SDR encoding and did a little test and I'm impressed how easy it is and how good the results look like. Used Staxrip Wiki. Thank you.

What gives better looks from these 3? I'm not much into tweaking too much. The shorter and easier the better.

1- DGReinhard()
2- DGHable()
3- DGHDRtoSDR(mode="pq", white=50)

For the short test I did, DGReinhard looks better.

@manolito did some test on 3(DGHDRtoSDR) to get a better result. See here (https://forum.doom9.org/showthread.php?p=1943079#post1943079).

For DGTonemap(1 & 2), someone can refer to its manual and do some testing. (I haven't and am not willing to, though.) :rolleyes:

[StormMeows]

Hey guys, is there a good rule of thumb for cropping when encoding blu-rays to x264 8-bit? I manually cropped a 1080p blu-ray to 1920x1036, but it is in Red and the SAR value is highlighted in red at 1.853281. If I use the Auto Crop in Stax Rip it wants to cut more than just the black bars and make it 1920x1032. I don't want to encode this movie at the wrong crop value, nor do I want to crop part of the actual movie. Please let me know what the best way/rule of thumb would be with cropping.

Thank you guys!

[JKyle]

Hey guys, is there a good rule of thumb for cropping when encoding blu-rays to x264 8-bit? I manually cropped a 1080p blu-ray to 1920x1036, but it is in Red and the SAR value is highlighted in red at 1.853281. If I use the Auto Crop in Stax Rip it wants to cut more than just the black bars and make it 1920x1032.

Adjust the Output Mod (multiples of a specific number) value in Options > Image > Output Mod.
Crop is auto-corrected based on this output mod value if Options > Image > Crop > Auto correct crop values is turned on.
Assistant warns on aspect ratio error based on the cropped pixel values if Options > Assistant > Warn on aspect ratio error is turned on.

Since you choose to encode in x264, mod 2 (= even numbers) will be usually enough except you employ filters that require specific mods or resize drastically so the resulting pixel size becomes not encodable (=odd) in x264.

StaxRip is a highly customizable app. You can do some testing with various option settings.
Plus, if you have a question on a specific option item, right click on it and a short help dialog will pop up in most cases.

[StormMeows]

Adjust the Output Mod (multiples of a specific number) value in Options > Image > Output Mod.
Crop is auto-corrected based on this output mod value if Options > Image > Crop > Auto correct crop values is turned on.
Assistant warns on aspect ratio error based on the cropped pixel values if Options > Assistant > Warn on aspect ratio error is turned on.

Since you choose to encode in x264, mod 2 (= even numbers) will be usually enough except you employ filters that require specific mods or resize drastically so the resulting pixel size becomes not encodable (=odd) in x264.

StaxRip is a highly customizable app. You can do some testing with various option settings.
Plus, if you have a question on a specific option item, right click on it and a short help dialog will pop up in most cases.
Thank you so much! This is what I was looking to do (mod2), but didn't see it under settings. Really appreciate the thorough response!

[Atlantis]

To be safe crop at mod 8. The default value in staxrip is already 8. Even mod 4 is not safe.

[StormMeows]

To be safe crop at mod 8. The default value in staxrip is already 8. Even mod 4 is not safe.

Hey thank you for this. So it is always better to crop evenly on each side and then if it still has 1 thin black line on each side, that's okay (undercrop by 1x on each side)? I have already ran into several cases where Staxrip wants to actually crop a small part of the video.(over crop)

Also, how can I ensure this setting saves the next time I enter Staxrip? It seems like every time I exit out of Staxrip, it won't save some of my settings.

Another cool thing that I have found out about Staxrip is that you can encode VC-1 Blu-rays. When I was researching, for some reason it was saying that I couldn't encode the blu-ray if it was VC-1, maybe things have changed (outdated info)?

Thanks for any guidance.

[Atlantis]

Having 1 or 2 black lines on the edge is not a good idea. The encoder gives an artifact on the encoded video edge. You need a little more. For example some movies crop to 1920 x 804, although I can crop them to 1920 x 808, I don't do that and I crop them to 1920 x 816.

If you don't crop by mod 8 you could have hardware player problems. For example some amlogic devices if you give them a mod 4 video, they will repeat the last 4 lines to make it mod 8 and it gives a very bad visible visual artifact at the bottom.

[StormMeows]

Having 1 or 2 black lines on the edge is not a good idea. The encoder gives an artifact on the encoded video edge. You need a little more. For example some movies crop to 1920 x 804, although I can crop them to 1920 x 808, I don't do that and I crop them to 1920 x 816.

If you don't crop by mod 8 you could have hardware player problems. For example some amlogic devices if you give them a mod 4 video, they will repeat the last 4 lines to make it mod 8 and it gives a very bad visible visual artifact at the bottom.

Thank you, I will overcrop instead of leave black lines and use mod8. I really appreciate the advice 🙏

[Atlantis]

I personally undercrop. There is nothing wrong with having a little black bars. I would die if I overcrop. The thought that I'm throwing away part of the image is unthinkable to me! :)

[StormMeows]

I personally undercrop. There is nothing wrong with having a little black bars. I would die if I overcrop. The thought that I'm throwing away part of the image is unthinkable to me! :)

Sorry, I think i misunderstood you then. So it's okay to leave bigger black bars, but not thin black lines (like 1px)? You're saying that leaving 2 thin lines will cause artifacts but a bit bigger black lines won't? Thanks

[Atlantis]

Yes that is what I am saying. Your original Bluray is 1920 x 1080 with huge black bars already for some movies. There is no problem.

I have discovered that 1 or 2 black lines is too little and gives subtle artifact in the encode. Do your own test. Maybe you will not notice it and it is ok for you.

For example, encode a movie that crops at 804 both at 808 crop and 816 crop and check if you see the difference.

[StormMeows]

Yes that is what I am saying. Your original Bluray is 1920 x 1080 with huge black bars already for some movies. There is no problem.

I have discovered that 1 or 2 black lines is too little and gives subtle artifact in the encode. Do your own test. Maybe you will not notice it and it is ok for you.

For example, encode a movie that crops at 804 both at 808 crop and 816 crop and check if you see the difference.

I understand what you're saying now. Sorry about that. You leave bigger black bars so there is no artifacts. So if it crops to 804, do 816 instead to have the bars bigger kind of similar to blurays with huge black bars.

[Atlantis]

Exactly. Very simple.
1- Crop to mod 8.
2- Avoid 1-2 lines of black bars.

[StormMeows]

Exactly. Very simple.
1- Crop to mod 8.
2- Avoid 1-2 lines of black bars.

Hey, it almost seems like Mod2 might be best, which in most cases it will just over crop the top and bottom by 1 pixel. I don't think 1 pixel is going to make that big of a difference on top and bottom. This is the guidelines that a lot of encoders use from what I have seen. It seems to be the standard to overcrop by 1pixel versus under crop.

Since we are on Staxrip topic, I have been loving this program. Just to verify, for x264 8-bit encodes, there is no way for me to tell Staxrip to use 100% of my CPU? It typically ranges between 70-80% with occasional spikes of up to 91%. I just want to make sure since locking it at 100% would be even faster of encodes.

Also, how do I save settings like the Mod2 setting. Each time I exit Staxrip, it switches back to 8. Thank you guys!

[Atlantis]

If your player can handle mod2 then good for you. As I already explained not all hardware players can. My 3 Amlogic CoreELEC players can handle only mod 8.

[JKyle]

Since we are on Staxrip topic, I have been loving this program. Just to verify, for x264 8-bit encodes, there is no way for me to tell Staxrip to use 100% of my CPU? It typically ranges between 70-80% with occasional spikes of up to 91%. I just want to make sure since locking it at 100% would be even faster of encodes.

Currently only x265 and AOMEnc are capable of chunk encoding in StaxRip. AFAIK, chunk encoding was not enabled for x264 since there was not much demand.

If you want to see chunk encoding in x264, you need to submit a feature request in the Issue Tracker on GitHub (https://github.com/staxrip/staxrip/issues). And of course, whether it will be adopted or not depends on our main developer Dendraspis's mind. :D

If you can't wait to use x264 chunk encoding, you may want to use other software that has such feature like RipBot264 or Av1an.

Also, how do I save settings like the Mod2 setting. Each time I exit Staxrip, it switches back to 8.

You need to save the option in a template not in a particular project.

Start StaxRip, don't open any source file, change Options, and click on File > Save Project As Template.... Use that specific template (File > Project Templates...) to use the saved options afterwards.

For more info about templates in StaxRip, read the corresponding section (https://github.com/staxrip/staxrip/wiki/Usage#templates) on the GitHub wiki.

It's strongly recommended that users take time to read the basic StaxRip usage guide (https://github.com/staxrip/staxrip/wiki/Usage) on the wiki. And you may be able to find answers to many of your questions on the wiki as well. Please read/search the wiki guides first before asking questions.

[guest]

If you can't wait to use x264 chunk encoding, you may want to use other software that has such feature like RipBot264 or Av1an.

Hi J,

I think I might have mentioned this before, but if you and whoever else could get their knowledge on the same wave length, and introduced a chunk encoding function like RipBot, you would by far, have the best encoding app EVER !!!!

It clearly can be done successfully, so you've just got to figure out how Atak did it, so many years ago.....:p

[Atlantis]

Man, there is always something new you have to learn! Chunk encoding. Is it correct to say that the default value of 1 gives the best quality and it's only slower?

[Atak_Snajpera]

Just to verify, for x264 8-bit encodes, there is no way for me to tell Staxrip to use 100% of my CPU? It typically ranges between 70-80% with occasional spikes of up to 91%. I just want to make sure since locking it at 100% would be even faster of encodes.
Even if you see 75% of CPU usage this does not mean that you lose 25% of performance. SMT !=CORE. Probably you already get 90% of your max FPS.
Besides. If i'm not mistaken x264 Has hard thread limit set at 24. Devs discovered that more threads reduce quality.

[StormMeows]

If your player can handle mod2 then good for you. As I already explained not all hardware players can. My 3 Amlogic CoreELEC players can handle only mod 8.

Hey, yeah my player has no issues with mod2 (nvidia shield pro) so I will stick to that. Thanks again for the insightful information.


Currently only x265 and AOMEnc are capable of chunk encoding in StaxRip. AFAIK, chunk encoding was not enabled for x264 since there was not much demand.

If you want to see chunk encoding in x264, you need to submit a feature request in the Issue Tracker on GitHub (https://github.com/staxrip/staxrip/issues). And of course, whether it will be adopted or not depends on our main developer Dendraspis's mind. :D

If you can't wait to use x264 chunk encoding, you may want to use other software that has such feature like RipBot264 or Av1an.



You need to save the option in a template not in a particular project.

Start StaxRip, don't open any source file, change Options, and click on File > Save Project As Template.... Use that specific template (File > Project Templates...) to use the saved options afterwards.

For more info about templates in StaxRip, read the corresponding section (https://github.com/staxrip/staxrip/wiki/Usage#templates) on the GitHub wiki.

It's strongly recommended that users take time to read the basic StaxRip usage guide (https://github.com/staxrip/staxrip/wiki/Usage) on the wiki. And you may be able to find answers to many of your questions on the wiki as well. Please read/search the wiki guides first before asking questions.

Wow, thank you so much for the thorough response! It definitely sounds like with x264 i will just stick to Staxrip because I want to maximize quality. As mentioned down below, after 24 threads are used, there be a downgrade in quality. I would rather have a slightly slower encode time than lose quality. Transparency to the source is my goal for bluray 1080p backups and that's why I use x264 over x265 for this content. When I start doing 4k encodes, I'll switch to x265.

Sorry for not reading through the Wiki all the way. I will definitely get to that soon and will refrain from asking generic questions. Thank you!

Even if you see 75% of CPU usage this does not mean that you lose 25% of performance. SMT !=CORE. Probably you already get 90% of your max FPS.
Besides. If i'm not mistaken x264 Has hard thread limit set at 24. Devs discovered that more threads reduce quality.
Thanks so much for the detailed reply! I stick to what I'm doing because I don't want a quality loss. I have 32 threads on my CPU so if I can't fully take advantage of that for x264, then so be it.

[StormMeows]

If I do Chunk Encoding on x265 10 bit, the default value is 1. Should this be changed to use more of my CPU then? I am only using 50% of my CPU when testing x265 10-bit. Also, why is there so much fluctuation of the CPU usage% when encoding. It will be at like 50% then go to 70%, then back down and so forth.

Edit: I looked into it and perhaps I should change Settings > General maximum number of parallel processes to help max the CPU out? I could also just open up staxrip and run 2 encodes at the same times to possibly max out the CPU usage, right? There has to be a way with x265 10bit to get it to 100% cpu usage constant.

Thanks guys

[BobDig]

There has to be a way with x265 10bit to get it to 100% cpu usage constant.
No problem here. Just turn off SMT in the UEFI, it does nothing for video encoding with x26*. If you want to keep it on, it doesn't matter anyways. Do a test encode with a sample and see yourself.

[Khun_Doug]

Due to the way x265 uses parallel threads for the decision trees, each thread will run a different amount of time. This is not like x264. The effect is that a single x265 cannot really saturate a CPU. There are a few things to try to ramp up your saturation. First is to make sure to use a PreFetch, depending on the filters you use. Some filters, such mClean, SMDegrain, SMDegrain with motion vectors, LSFMod, and many others, really benefit from PreFetch. In my experience with a Ryzen 3950x, now my 5950x, I didn't see any benefit by using PreFetch higher than 14 on HD source, despite having 32 threads available. I find a PreFetch of 8 is adequate for SD sources. Remember that you can only get x265 to go so fast because of the decision-making parallel threads.

The other thing to do is run one than one job at the same time. On my 3950x and 5950x, I was easily able to run 3 and 4 SD encodes simultaneously. Please keep in mind that the number and types of filters you use will affect CPU usage.

[StormMeows]

Due to the way x265 uses parallel threads for the decision trees, each thread will run a different amount of time. This is not like x264. The effect is that a single x265 cannot really saturate a CPU. There are a few things to try to ramp up your saturation. First is to make sure to use a PreFetch, depending on the filters you use. Some filters, such mClean, SMDegrain, SMDegrain with motion vectors, LSFMod, and many others, really benefit from PreFetch. In my experience with a Ryzen 3950x, now my 5950x, I didn't see any benefit by using PreFetch higher than 14 on HD source, despite having 32 threads available. I find a PreFetch of 8 is adequate for SD sources. Remember that you can only get x265 to go so fast because of the decision-making parallel threads.

The other thing to do is run one than one job at the same time. On my 3950x and 5950x, I was easily able to run 3 and 4 SD encodes simultaneously. Please keep in mind that the number and types of filters you use will affect CPU usage.
Thank you for the detailed reply. I typically do not use filters so I'm not sure how much PreFetch would help me. I am just mainly doing standard 1080p high quality/transparent encodes. I may just use x264 8 bit since that's the same as the source and is much, much quicker for these backups. Perhaps I could speed up x264 8 bit blu-ray encodes by running 2 staxrip encodes at once? :) Thanks

No problem here. Just turn off SMT in the UEFI, it does nothing for video encoding with x26*. If you want to keep it on, it doesn't matter anyways. Do a test encode with a sample and see yourself.

Thank you, I will definitely give it a try. Does this help for x264 8 bit encodes as well or just x265? Anything to help use more of my CPU power for x264? It sounds like not a whole lot, unless I want to just run 2 simultaneous encodes.

[StormMeows]

Does anyone know what quality of FLAC is used in Stax Rip? It has a quality scale from 0-11 with 11 being the best quality/compresses the best. Does Stax use this by default or is there a way to encode FLAC to 11 quality?

*Edit* I downloaded FLAC.exe and directed it to Staxrip with command line, but then staxrip wants the following for my DTS-MA track: Error for encoding a raw file you must specify a value for --endian, --sign, --channels, --bps, and --sample-rate . If anyone can help, it would be great. Hopefully the standard FLAC user a high quality/best compression like 11.

Thanks

[JKyle]

@StormMeows,

You're trying to reinvent the wheel.

If you look at the command line for flac encoding (bottom of Audio Settings), or at the log, you'll see that ffmpeg (more precisely, flac encoder wrapped in ffmpeg) is used. (As a matter of fact, all audio codecs other than AAC use ffmpeg as their encoders in StaxRip. You'll be able to find it out if you look at the command lines.)

In StaxRip, some private options for a specific audio encoder are missing from the menu to avoid complications. Instead, you can always put custom options in the Custom field.

Refer to the flac encoder section in the ffmpeg manual (https://ffmpeg.org/ffmpeg-codecs.html#flac-2), and put the compression level related option as follows (12 is the maximum):

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

If you want to encode an audio track only, right click on the corresponding track > Execute. You can find the encoded audio track in the project temp folder.

[StormMeows]

@StormMeows,

You're trying to reinvent the wheel.

If you look at the command line for flac encoding (bottom of Audio Settings), or at the log, you'll see that ffmpeg (more precisely, flac encoder wrapped in ffmpeg) is used. (As a matter of fact, all audio codecs other than AAC use ffmpeg as their encoders in StaxRip. You'll be able to find it out if you look at the command lines.)

In StaxRip, some private options for a specific audio encoder are missing from the menu to avoid complications. Instead, you can always put custom options in the Custom field.

Refer to the flac encoder section in the ffmpeg manual (https://ffmpeg.org/ffmpeg-codecs.html#flac-2), and put the compression level related option as follows (12 is the maximum):

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

If you want to encode an audio track only, right click on the corresponding track > Execute. You can find the encoded audio track in the project temp folder.
You're awesome! thank you so much!!!! :D Have a great weekend!

[Schattenspieler]

If you want to encode an audio track only, right click on the corresponding track > Execute. You can find the encoded audio track in the project temp folder.

On that note I got a question: Is it possible to deactivate the confirmation dialogue for audio encoding? And maybe to encode more than a single audio track in one session at once (maybe cued, not parallel)?

I use it once in a while to convert AC3/DTS to AAC and thus decrease file size.

Gesendet von meinem H8324 mit Tapatalk

[JKyle]

Is it possible to deactivate the confirmation dialogue for audio encoding?

The confirmation dialog is a required process for stream selection/mapping when you encode an audio track not demuxed from the source file.

But it's not necessary when you encode a single audio file that is already extracted from the source file.

If I'm not mistaken, there's no way to disable the dialog for extracted files. So it amounts to a feature request.

Use the Issue Tracker (https://github.com/staxrip/staxrip/issues) to submit a feature request, as I always recommend. Feature requests written here will not be considered.

And maybe to encode more than a single audio track in one session at once (maybe cued, not parallel)?

I don't get it. What do you mean by 'cued not parallel'? :rolleyes:

If you mean 'batch encoding' of audio files, use audio encoding programs such as fre:ac (https://www.videohelp.com/software/fre-ac), etc.

But if you want to make use of qaac, you need to compose a DOS batch for AAC encoding due to license issues, AFAIK.

If anyone knows about an audio encoding program that enables users to use a custom encoder like qaac, plz post here.

[-QfG-]

One question, i didn't know if this is a bug or feature. I Use StaxRip 2.6.0 and the included Patman x264 Encoder.

In the Settings i can choice under "Input/Output2" the SEI Output. If i change the options, a command --opts 1 will be added. But the Encoder says that is an unknown command.

My fail, or needed a special x264 Encoder?

1- DGReinhard()
2- DGHable()
3- DGHDRtoSDR(mode="pq", white=50)

4-HDRTools

I have the best results with HDRTools (https://forum.doom9.org/showthread.php?t=175488&highlight=HDRTools) -

Loadplugin("%startup_dir%\Apps\Plugins\AVS\HDRTools\hdrtools.dll")
ConvertYUVtoXYZ(Color=0,HDRMode=0,OOTF=false,OutputMode=2,threads=1)
ConverXYZ_BT2446_C_HDRtoSDR(PQMode=true,Lhdr=30000.0,Lsdr=100.0,pColor=0,pct_ref=0.6,pct_ip=0.6,pct_wp=1.0,pct_sdr_skin=1.0,pct_hdr_skin=0.44,threads=1)
ConvertXYZtoYUV(Color=2,pColor=0,OOTF=false,threads=1)
Tweak(bright=-3.5, coring=false, realcalc=false, dither=false)
ConvertBits(8)

[JKyle]

I Use StaxRip 2.6.0 and the included Patman x264 Encoder.

In the Settings i can choice under "Input/Output2" the SEI Output. If i change the options, a command --opts 1 will be added. But the Encoder says that is an unknown command.

You're right. I could reproduce the same issue.

The opts option is not present in the full console help. And if I run x264 with --opts only, the encoding fails with the following error.

--------------------------- Video encoding ---------------------------

x264 0.163.3059+11-1aa8b82-.Mod-by-Patman.-x64-gcc10.3.0

D:\Tmp\StaxRip-v2.6.0-x64\Apps\Encoders\x264\x264.exe --opts 1 --synth-lib D:\Tmp\StaxRip-v2.6.0-x64\Apps\FrameServer\AviSynth\AviSynth.dll --output "D:\Test\Two audio sample_temp\Two audio sample_new_out.h264" "D:\Test\Two audio sample_temp\Two audio sample_new.avs"

D:\Tmp\StaxRip-v2.6.0-x64\Apps\Encoders\x264\x264.exe: unknown option -- opts

This needs to be fixed. I reported this issue on the Issue Tracker (https://github.com/staxrip/staxrip/issues/748) and it will be fixed in the next release.

--------------------------------------------------



4-HDRTools

I have the best results with HDRTools (https://forum.doom9.org/showthread.php?t=175488&highlight=HDRTools) -

Loadplugin("%startup_dir%\Apps\Plugins\AVS\HDRTools\hdrtools.dll")
ConvertYUVtoXYZ(Color=0,HDRMode=0,OOTF=false,OutputMode=2,threads=1)
ConverXYZ_BT2446_C_HDRtoSDR(PQMode=true,Lhdr=30000.0,Lsdr=100.0,pColor=0,pct_ref=0.6,pct_ip=0.6,pct_wp=1.0,pct_sdr_skin=1.0,pct_hdr_skin=0.44,threads=1)
ConvertXYZtoYUV(Color=2,pColor=0,OOTF=false,threads=1)
Tweak(bright=-3.5, coring=false, realcalc=false, dither=false)
ConvertBits(8)

Thanks for the sample script. It showed me there's a loophole in the current StaxRip release.

Since plugins_JPSDR is a merge of the following AviSynth plugins,

AutoYUY2, NNEDI3, ResampleMT, aWarpSharpMT, HDRTools

you should be able to call filter functions provided by HDRTools natively in StaxRip. But since some filter functions like ConverXYZ_BT2446_C_HDRtoSDR are missing from the registration in StaxRip, you may encounter a dependency issue as of now.

Just put

LoadPlugin("%app:JPSDR%")

instead of

Loadplugin("%startup_dir%\Apps\Plugins\AVS\HDRTools\hdrtools.dll")

and remove the redundant HDRTools folder from the program tree. This way you can save drive space and avoid duplicates.

==================================================

[UPDATE]

I've added the following two missing filters to JPSDR in StaxRip plugin registration.

ConvertLinearRGBtoYUV_BT2446_A_HDRtoSDR, ConverXYZ_BT2446_C_HDRtoSDR

The update will be reflected in the next release, v2.7.0, so you are not gonna need the extra LoadPlugin("%app:JPSDR%") line starting in the next version.

[-QfG-]

THX @JKyle for the informations.

[Atlantis]

Thank you so much for including HDRTools.

Maybe also add this if it works well for HDR to SDR as it was said
ConvertYUVtoXYZ(Color=0,HDRMode=0,OOTF=false,OutputMode=2,threads=1)
ConverXYZ_BT2446_C_HDRtoSDR(PQMode=true,Lhdr=30000.0,Lsdr=100.0,pColor=0,pct_ref=0.6,pct_ip=0.6,pct_wp=1.0,pct_sdr_skin=1.0,pct_hdr_skin=0.44,threads=1)
ConvertXYZtoYUV(Color=2,pColor=0,OOTF=false,threads=1)
Tweak(bright=-3.5, coring=false, realcalc=false, dither=false)
ConvertBits(8)

I have not tested it yet.

[Atlantis]

I noticed that in the staxrip log the date is not written if I'm not mistaken. You get the time, the duration but not a date. It would be useful if the date was written at least once somewhere. Maybe at the beginning so we could tell how old is an encode.

[JKyle]

Thanks to @-QfG-'s pointer, the following HDRTools related HDR to SDR tonemapping filter profiles will be added by default in the next release version, v2.7.0.

(FYI, PQ(Perceptual Quantizer) = st2084 = SMPTE ST 2084, and HLG(Hybrid Log-Gamma) = std-b67 = arib-std-b67)


[PQ videos]

HDR to SDR | HDRTools | PQ =
ConvertYUVtoXYZ(Color=0, HDRMode=0, OOTF=false, OutputMode=2)
ConverXYZ_BT2446_C_HDRtoSDR(PQMode=true, Lhdr=$enter_text:HDR max mastering luminance level (in cd/m2)? (Default: 10000.0)$, Lsdr=100.0, pColor=0)
ConvertXYZtoYUV(Color=2, pColor=0, OOTF=false, OutputMode=2)
ConvertBits(8)

[HLG videos]

HDR to SDR | HDRTools | HLG =
ConvertYUVtoXYZ(Color=0, HDRMode=2, OOTF=false, OutputMode=2)
ConverXYZ_BT2446_C_HDRtoSDR(PQMode=false, Lhdr=$enter_text:HDR max mastering luminance level (in cd/m2)? (Default: 1000.0)$, Lsdr=100.0, pColor=0)
ConvertXYZtoYUV(Color=2, pColor=0, OOTF=false, OutputMode=2)
ConvertBits(8)

AVS only.

Add the above code to your AVS Filter Profiles under the [Color] section (blank lines above and below) if you want to use them now.

For reference, whether an HDR video is PQ or HLG can be verified in its mediainfo.

Refer to the HDRTools manual (http://avisynth.nl/index.php/HDRTools) for further customization.

[Atlantis]

This is the second time that this has happened to me. An encode finishes and later I find out that it has not encoded the full video. Like half of it.

So, without any errors and without saying anything in the log, the video encoding finishes sooner. The job is finished, everything is muxed. The running time in explorer and media info looks correct. So you can't actually tell that there is only half of the video, the running time is of the audio. You have no idea of knowing something went wrong unless you play the very end.

this is what it shows in the log

x265 [INFO]: HEVC encoder version 3.5+10+13-7c9bc0cb14 [Mod by Patman]
x265 [INFO]: build info [Windows][GCC 10.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-3.1 (Main tier)
x265 [INFO]: Thread pool created using 8 threads
x265 [INFO]: Slices : 1
x265 [INFO]: frame threads / pool features : 3 / wpp (9 rows)
x265 [WARN]: 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 TU depth : 32 / 1 inter / 1 intra
x265 [INFO]: ME / range / subpel / merge : hex / 57 / 2 / 3
x265 [INFO]: Keyint 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 : 2 / 1.0 / 32 / 1
x265 [INFO]: Rate Control / qCompress : CRF-22.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

Start: 2:36:27 AM
End: 3:51:09 AM
Duration: 01:14:42

HEVC : 448 MiB1280*536 (2.40:1), at 23.976 (24000/1001) FPS, HEVC (Main 10@L3.1@Main)

---------------------------- Muxing to MKV ----------------------------

mkvmerge 56.1

...
...

As you see at the end of video encode it doesn't show the usual

encoded 180432 frames in 11045.61s (16.34 fps), 1022.70 kb/s, Avg QP:26.84

[creeve4]

A couple questions:
1. Regarding this commit (https://github.com/staxrip/staxrip/commit/d70a8338c24e0a6bb4c915ca37040eef5670479c): How can I change these default values (after Staxrip is compiled)? Previously (version 2.5.0 and earlier) I would just modify the complied scripts themselves.
2. I have been using Staxrip to benchmark my CPU settings (I am playing around with PBO for my R9 5950X) and I noticed that for the same file my encodes decrease by 0.25-0.30 fps when my computer has been running for several hours vs if I start the encode shortly after a reboot. I have tried setting the Staxrip priority to High, but this has no affect. Any ideas?

[Atak_Snajpera]

Higher temps will reduce turbo boost frequency on your CPU. That's normal after several hours of encoding using AVX2 instructions.

[Atlantis]

I just re-encoded the same movie and this time it was complete. So it's strange, I can't reproduce it on the same file.

It would be great if staxrip showed an error if it didn't complete the video encode.

[Khun_Doug]

I also have the Ryzen 5950X and use a 240MM AIO. With PBO the voltages go high and some of the cores hit high frequency. But the heat from this is wild and the AIO does its job but the CPU still gets close to 80C or even a bit higher. What I decided to do was set several frequency and voltage combinations in the BIOS and with the Asrock A-Tuning tool. I found that I can get a clock of 4200 with a low voltage, and the entire machine runs cool. The small difference in encode times is minimal versus having a cooler machine. I also made another profile for 3850 GHz and an even lower voltage. The machine blazes along, does everything I need, and no crazy CPU temperatures. One thing to be aware of. If you go this route, make sure to try something like Prime95 to taste your CPU for stability. The voltage too low will cause some failures and you don't want that.

[creeve4]

Higher temps will reduce turbo boost frequency on your CPU. That's normal after several hours of encoding using AVX2 instructions.

Maybe I was not clear in my question.

As an example:
If I start an encode shortly after a reboot, I get 3.5fps average for the 5 minute clip I am using to benchmark.
If I start an encode with this same clip after I have been using the computer for several hours (non-encoding use) I will only get 3.25 fps.
In both cases I am not experiencing any thermal throttling (temps are about 72C the entire encode). I am using a 360mm AIO cooler.

[Atak_Snajpera]

Why don't you run hwinfo and log temps and cpu frequency during encoding?

[creeve4]

Why don't you run hwinfo and log temps and cpu frequency during encoding?

I have been 😂
Like I said temps are very low. Frequencies seem to be approximately the same in both situations.

[JKyle]

StaxRip v2.7.0 is released.

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

Don't forget to back up your custom Encoder Profiles before update. See this post (https://forum.doom9.org/showthread.php?p=1947159#post1947159) for detail.

This is the VirusTotal scan result: here (https://www.virustotal.com/gui/url/c07fbb5eb981064f8e04cad74a5a513d35edc20f680533105fc4e10dfced8978/detection).

And about false virus warnings, see this wiki document (https://github.com/staxrip/staxrip/wiki/About-False-Virus-Detection-Warnings).

[Atlantis]

I installed it. What happened to Neo FFT3D? It is not included in the package like before. I think you forgot it.

It's like the most important filter!

https://github.com/HomeOfAviSynthPlusEvolution/neo_FFT3D

[Atlantis]

Something wanted to say for a long time about the main window. The size is fixed, can't it be resizable?

If it is hard to program it that way and fixed is easier, at least it should be a little larger. It's too small for today needs. For example I have 8-9 filters and would like to see them all at once and not to scroll.

[Atlantis]

I see that in the new version we get muxing timestamps in mkv. I have done a little research but don't get it. Why do we need it? We didn't use it before. Is it only for syncing audio and video? if yes why it worked before without it.

[JKyle]

There was a hiccup in the release of v2.7.0.
It's fixed and everything is working OK now. Plz re-download the file.