StaxRip

[Netsurfer1793]

Hello,
Is it somehow possible to use the StaxRip version 2.5+ with VapourSynth on Windows 7?
As VapourSynth/Python dropped support for Windows 7 with R53 would it be possible to e.g. revert the VapourSynth (and probably also Python) version on StaxRip 2.5+ back to R52?

[guest]

What kind of question is that? What that has got to do with anything? I said it was not updated in staxrip.

That wasn't a question !!

I stated that FFT3DFilter v2.9 was released back in March.

And the other comment was merely a suggestion, of how to update it yourself...:sly:

[guest]

@Pauly Dunne

Atlantis has done the correct thing to do, and thanks for that Atlantis.

Fair enough, it's always good to "do the right thing", but sometimes you can "DIY" :sly:

[JKyle]

Is it somehow possible to use the StaxRip version 2.5+ with VapourSynth on Windows 7?
As VapourSynth/Python dropped support for Windows 7 with R53 would it be possible to e.g. revert the VapourSynth (and probably also Python) version on StaxRip 2.5+ back to R52?

Conceptually, you can

1) uninstall VapourSynth and Python from your system, if there's any, and restart Windows.

2) install Python 3.8.x x64 version, e.g., 3.8.10 x64 install version (https://www.python.org/ftp/python/3.8.10/python-3.8.10-amd64.exe), on your Windows 7.

3) install VapourSynth x64 R52 (https://github.com/vapoursynth/vapoursynth/releases/tag/R52).

4) Restart Windows, and launch StaxRip.

5) Go to Tools > Settings > Frameserver and select 'Use installed directly' for VapourSynth Mode.

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

6) Restart StaxRip, and you'll be able to use VapourSynth R52 on Windows 7.

Since VapourSynth is just a Python module, you should always install Python first, and there should be no VapourSynth on the system when Python is installed.

[Netsurfer1793]

Conceptually, you can

Thank you. That worked.
However I also had to adjust the version numbers in StaxRips Apps dialog.
But now it seems to work. :thanks:

Just to be sure:
Could there be any issues with using older Python and VapourSynth versions with newer StaxRip versions?
Or can I use the older versions without worries?

[Atlantis]

That wasn't a question !!

I stated that FFT3DFilter v2.9 was released back in March.

And the other comment was merely a suggestion, of how to update it yourself...:sly:

Again it was a useless comment that did not help anything or anyone. I tried really hard not to say stupid.

You say "Why don't you just add it / overwrite it, yourself !!!"
I'm not an admin or the project manager of staxrip, I have no access to staxrip project to update it.

If you mean on my own computer, you think I don't know how to download it? I'm following the project, provided a link so I know how to download and use it.

Again the post was to inform that a tool has not been updated on staxrip. It was not a personal question on what should I do on my computer.

[JKyle]

However I also had to adjust the version numbers in StaxRips Apps dialog.

I didn't mention it because it's a matter of course.

Could there be any issues with using older Python and VapourSynth versions with newer StaxRip versions?
Or can I use the older versions without worries?

If the VapourSynth scripts/filters/plugins were developed no later than R52, there should be no issues.
Otherwise, it's definitely case by case, of course.

AFAIK, all the VapourSynth plugins/filters registered in StaxRip as of version 2.6.0 are compatible with R52/Python 3.8.x.
But I cannot guarantee 100%.

[guest]

Again it was a useless comment that did not help anything or anyone. I tried really hard not to say stupid.

You say "Why don't you just add it / overwrite it, yourself !!!"
I'm not an admin or the project manager of staxrip, I have no access to staxrip project to update it.

If you mean on my own computer, you think I don't know how to download it? I'm following the project, provided a link so I know how to download and use it.

Again the post was to inform that a tool has not been updated on staxrip. It was not a personal question on what should I do on my computer.

Whatever, mate...now I think what you're doing with this, IS "stupid" !!!

You have blown it out of all proportion, you've also insulted one's intelligence !!!

All it was, was a reference to when that filter update was released.

And a simple suggestion on how one could update it within Staxrip.

THAT'S IT !!!!

There was no question, it's not useless & was nothing personal !!!

Your original post sounded a little impatient & annoyed, TBH !!!

I already put this on the page request long before 2.6.0 release and it is still not included with 2.6.0

[Netsurfer1793]

I didn't mention it because it's a matter of course.
Yes, you are right. I also didn't meant it as a criticism. I've just mentioned it.
After all, StaxRip also force you to adjust the version numbers before you can proceed. So no way to forget about it. :)


If the VapourSynth scripts/filters/plugins were developed no later than R52, there should be no issues.
Otherwise, it's definitely case by case, of course.

AFAIK, all the VapourSynth plugins/filters registered in StaxRip as of version 2.6.0 are compatible with R52/Python 3.8.x.
But I cannot guarantee 100%.
Thanks for the info. Yes, it makes sense. I will then keep in mind to check the compatibility with old versions.
I also hope that in case of issues the new plugins just won't work and would show an error instead of doing something unexpected silently.

[JKyle]

Based on our discussion here, I've added two new wiki documents:


About False Virus Detection Warnings (https://github.com/staxrip/staxrip/wiki/About-False-Virus-Detection-Warnings)
How to use VapourSynth on Windows 7 in StaxRip 2.5.0 and later (https://github.com/staxrip/staxrip/wiki/How-to-use-VapourSynth-on-Windows-7-in-StaxRip-2.5.0-and-later)


And if you're interested in applying a custom VapourSynth filter that is not registered in StaxRip, you can see this discussion thread on GitHub (https://github.com/staxrip/staxrip/discussions/718) for reference.

[JKyle]

AFAIK, normalizing to 0 dB is hard wired in the code.

Sorry but I was wrong about this. :rolleyes:

It turns out that gain can offset the normalize value.
See this post (https://github.com/staxrip/staxrip/issues/719#issuecomment-849140399) for detail. :)

[avinewbie]

Based on our discussion here, I've added two new wiki documents:

And if you're interested in applying a custom VapourSynth filter that is not registered in StaxRip, you can see this discussion thread on GitHub (https://github.com/staxrip/staxrip/discussions/718) for reference.

Thank you, thank you for that link to adding filters in VS

[Salem874]

I just updated staxrip and every time I launch it I get a pop-up dialog with the error
Load VapourSynth first
Filters > Filter Setup > VapourSynth
even though I have it installed. I've tried deleting the settings files and reset the load template I continue to get this error. I also tried to reset my filters so it's set to AVISynth instead and then save as template that loads on startup and it continues to load AVS Filters for vapoursynth instead. Appreciate any thoughts on how to fix this. Thank you.

Having the same issue...any ideas?

[JKyle]

Not easy to figure out what went wrong with such insufficient info. But my guess is that your frameserver setting is garbled up for some reason.

Try resetting it by switching b/w portable and installed, restarting StaxRip each time, and see if it resolves the problem. If not, you need to start afresh with a new StaxRip deployment.

[shodan5000]

Could AddGrain be added for vapoursynth or at least someone explain to me how to add it to Staxrip as a selectable profile? I've tried my best to research this for myself but with no success. I have the .dll from here https://github.com/HomeOfVapourSynthEvolution/VapourSynth-AddGrain

[JKyle]

Could AddGrain be added for vapoursynth or at least someone explain to me how to add it to Staxrip as a selectable profile?...
https://github.com/HomeOfVapourSynthEvolution/VapourSynth-AddGrain

Since it's a binary plugin, you just need to specify the path to the dll file, and use the function call provided by the plugin.
It's basically the same as DGHDRtoSDR (https://github.com/staxrip/staxrip/wiki/How-to-register-DGTonemap-&-DGHDRtoSDR-filters-in-StaxRip).

1. Switch to the VapourSynth mode in StaxRip by clicking AVS Filters ⇨ Filter Setup ⇨ VapourSynth.

2. Click Tools ⇨ Folders ⇨ Plugins.

3. Make a folder named AddGrain there and copy/paste AddGrain.dll into that folder.

4. Click VS Filters ⇨ Profiles....

5. Under the [Noise] section, put these lines (there should be an empty line above and beneath):


AddGrain =
core.std.LoadPlugin(r"%plugin_dir%AddGrain\AddGrain.dll")
clip = core.grain.Add(clip, var=1.0, uvar=0.0, hcorr=0.0, vcorr=0.0, seed=-1, constant=False, opt=0)


6. Apply Noise > AddGrain. Adjust var, hcorr, vcorr to your taste.

For example, (var=800, hcorr=0, vcorr=0.9) yields the following result:

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

I'm gonna register this VS plugin and its filter profile for the next release.

---

[Side Note]

Since it's just one dll file, maybe you can put AddGrain.dll in the Plugins folder directly, not in its subfolder, and remove the first line of the filter profile as follows:


AddGrain = clip = core.grain.Add(clip, var=1.0, uvar=0.0, hcorr=0.0, vcorr=0.0, seed=-1, constant=False, opt=0)


No empty lines are necessary.

This is because all the dll files in the Plugins folder of VapourSynth are autoloaded by StaxRip.

But there's a catch: files in the subfolders of Plugins folder or py script files in Plugins folder do not autoload. We need to load them explicitly in those cases.

[shodan5000]

I got it to work now. Thank you very, very much for the thorough explanation. Out of curiosity, why does the plugin's code look different in Staxrip than what's provided on its Github?

(Github)
grain.Add(clip clip[, float var=1.0, float uvar=0.0, float hcorr=0.0, float vcorr=0.0, int seed=-1, bint constant=False, int opt=0])

vs

(Staxrip)
AddGrain = clip = core.grain.Add(clip, var=1.0, uvar=0.0, hcorr=0.0, vcorr=0.0, seed=-1, constant=False, opt=0)

[JKyle]

It's a very basic combination of StaxRip filter profile syntax and VapourSynth syntax.
See the VapourSynth documentation (http://www.vapoursynth.com/doc/).

To add a side note, the code on the plugin's GitHub is not the real code to be used in reality. It's just a manual for the function call.
You need to distinguish them.

[tormento]

I usually do some compression tests with different parameters in SMDegrain. Is it possible to automate the parameter change inside the script and apply them on a few percentage of a video?

[44vince44]

I think this is planned for StaxRip v6.x.x

[tormento]

Did I lost some release note or the sound playing after encoding has not been implemented yet?

[44vince44]

It won't be done!

You have to do it yourself in Tools > Advanced > Event Command.

There you can program StaxRip to do whatever you want, including playing a sound for the selected event. This was already discussed and explained on Github.

[JKyle]

Hope these two simple samples will be of help.

Completion sound:
https://i.imgur.com/GfzRY1I.png

Copy target file log to the target folder
https://i.imgur.com/4CuEDFN.png

[MysteryX]

I saw 2 issues with StaxRip.

I imported a GoPro video with PC levels, but it exports by default as x265 with range Limited. I have to go and manually change the level in x265 settings. Is this by design?

Also, if you add KNLMeansCL, both Medium and Strong presets are exactly the same (h=4). Btw I personally found that setting d=2 is generally worth the extra computing (but not a=2).

The how does Open File Batch work? The first time it asked me how to do it, I said Automatic which added the videos straight into the job queue without allowing me to change or validate any options. Then when I do it again, it just adds raw videos to the job queue without asking me anything at all. So I'm just adding the videos 1 by 1 and resetting the config for each.

[JKyle]

I imported a GoPro video with PC levels, but it exports by default as x265 with range Limited. I have to go and manually change the level in x265 settings.

It's because you enabled Import VUI metadata in Options > Video, and your GoPro video has Color range : Limited video metadata in its media info. Disable the option if you don't want to import the VUI(video usability info) metadata.


Also, if you add KNLMeansCL, both Medium and Strong presets are exactly the same (h=4).

Thanks for the info. But it's already reported and will be fixed in the next release.


The how does Open File Batch work?

File Batch is definitely for videos with very similar properties.

For File Batch processing, you need to first load a template specifically customized for the videos in mind.

If you don't have any template, you need to compose one.

But since a template is an empty project, there should be no file in the project when you compose a template.

So my recommendation is as follows:

1) Load one of the video files that are to be processed by File Batch.

2) Do project settings: options (⇐ each and every item of Options matters), filter script settings, video/audio encoder settings, and muxer(mkv, mp4, etc.) settings.

3) Launch another session of StaxRip (right-click StaxRip icon on taskbar > Click StaxRip), and do the settings exactly the same as 2) without any source file.

4) Save the settings of 3) as a new template, and do File Batch after closing the first StaxRip from 1) (you don't have to save the project from 2)).


[Side note]

Source: Automatic determines what source filter is employed based on the settings in Tools > Settings > Preprocessing & Source Filters.

So for File Batch, don't choose Automatic unless you know how it works. Otherwise, it's highly probable that you end up with unexpected results like you said.

[MysteryX]

Even if VUI Range remains Auto, it still encodes as Limited.

Question is: why did GoPro set VUI Range to Limited if it's in fact Full.

Now I'm encoding as x264 10-bit manually setting VUI to PC.

Log contains this, and the output has broken color range.

resize [WARN]: converting range from TV to PC

After testing, it's possible to properly encode it as Full with x265 but not x264.

[JKyle]

Now I'm encoding as x264 10-bit manually setting VUI to PC.

Log contains this, and the output has broken color range.

After testing, it's possible to properly encode it as Full with x265 but not x264.

Have you tried force-setting Input Range to PC along with the (Output) Range setting to PC?

In my case, I see no warning message if I set those two options for a TV-range (⇐ video metadata) source file.
And the output file has the expected video metadata: Color range : Full.

But if you find that the actual color range is limited unlike the metadata, then you better report it to x264 developers.

[MysteryX]

Have you tried force-setting Input Range to PC along with the (Output) Range setting to PC?

In my case, I see no warning message if I set those two options for a TV-range (⇐ video metadata) source file.
And the output file has the expected video metadata: Color range : Full.

But if you find that the actual color range is limited unlike the metadata, then you better report it to x264 developers.
I'm not very familiar with StaxRip, just started using it. If you tell me exactly what to write and where, I can try it quickly. For now I encoded the videos as H265 and it's fine.

[JKyle]

If you tell me exactly what to write and where, I can try it quickly.

This will illustrate how to search & set color range related encoder options in x264.

https://i.imgur.com/Y7vXcRp.gif

This Search & Set feature is available for any video encoder in StaxRip.

[44vince44]

@MysteryX

This is not related to staxrip, this is related to the command line encoders, so that's what we call "tool issue"

In x265, you have to set as undefined, it will be interpreted as Limited, and you'll get the whole 0-255 range. This is something I'm sure of, and use all the time.

In x264, which I don't use, I believe you have to try encodes and see what setting you must use. I would not be surprised if TV would give the you correct result.

This is counterintuitive. But since there is no explanation of how those switched work...


How to test: try selecting a range of frames in the preview, encode them with the TV setting.
Compare the encode with the original using a color picker. You'll see the impact on whites and blacks....

You should not care about the mediainfo. You should care about how it plays and if it renders blacks at 0.0.0 and whites at 255.255.255.

[StormMeows]

Hey guys, I plan to build a PC dedicated to video encoding. Staxrip was recommended by another awesome member here. If I get something like an AMD threadripper, will staxrip be able to take advantage of all of the cores and threads at 100%? I'm assuming with a dedicated encoding rig I could run multiple movies in staxrip at once? I'm currently trying to weigh all of the pros and cons of building a dedicated machine. I have a lot of bluray backups that I need to encode the video only and pass through the lossless audio. Do you guys think building a dedicated rig would be worth it? I currently have a i9-9900k and Nvidia 2080 Super. I was considering just using the slowest preset and using the GPU, but it sounds like the CPU is going to blow that out of the water. I like the video to be as close to possible to the original and just need some space savings from the original. Any thoughts appreciated. Thank you guys!

[jlw_4049]

Hey guys, I plan to build a PC dedicated to video encoding. Staxrip was recommended by another awesome member here. If I get something like an AMD threadripper, will staxrip be able to take advantage of all of the cores and threads at 100%? I'm assuming with a dedicated encoding rig I could run multiple movies in staxrip at once? I'm currently trying to weigh all of the pros and cons of building a dedicated machine. I have a lot of bluray backups that I need to encode the video only and pass through the lossless audio. Do you guys think building a dedicated rig would be worth it? I currently have a i9-9900k and Nvidia 2080 Super. I was considering just using the slowest preset and using the GPU, but it sounds like the CPU is going to blow that out of the water. I like the video to be as close to possible to the original and just need some space savings from the original. Any thoughts appreciated. Thank you guys!An i9 9900k is plenty to get you started with cpu encoding. Staxrip will use as many cores as x264/x265 can utilize based on the content.

Going to a thread ripper would allow you to get more encodes done at once, but won't always give you more fps on a single encode at a time.

With that i9 9900k once you Q up a few to encodes, it'll catch up with you quicker you think.

Main thing is, make sure you have adequate cooling, since the cpu will be at ~100% for multiple hours to even days depending on your Q or content.

Keep in mind you won't be able to encode AND game at high fps at the same time. It'll be one or the other. Pausing the encode will free up some cycles, but it still is running and holds the ram.

Sent from my SM-G986U1 using Tapatalk

[Khun_Doug]

I was doing X264 and X265 encodes with an I7-6850K and moved to an AMD 3950X. On the I7 an X265 HD encode could go as long as 17-24 hours for one movie. That same task dropped to 4-7 hours with the 3950X. Shorter encodes, such as an episode Start Trek TOS was taking 4 1/2 hours, and dropped to about 2 hours. Filtering will make a difference. And with the 3950X I find I can encode more than one video at a time.

I just recently changed the 3950X out for a 5950X. I was able to encode old B&W movies that are 4:3 SD with a good amount of filtering, with 3 encodes running simultaneously, and the CPU was not maxed out. I had no trouble using Outlook and Firefox while the encodes were running. That 5950X is a beast!

[jlw_4049]

I was doing X264 and X265 encodes with an I7-6850K and moved to an AMD 3950X. On the I7 an X265 HD encode could go as long as 17-24 hours for one movie. That same task dropped to 4-7 hours with the 3950X. Shorter encodes, such as an episode Start Trek TOS was taking 4 1/2 hours, and dropped to about 2 hours. Filtering will make a difference. And with the 3950X I find I can encode more than one video at a time.



I just recently changed the 3950X out for a 5950X. I was able to encode old B&W movies that are 4:3 SD with a good amount of filtering, with 3 encodes running simultaneously, and the CPU was not maxed out. I had no trouble using Outlook and Firefox while the encodes were running. That 5950X is a beast!But the i9 9900k and ryzen 3xxx series have similar ICP.

X264 can only use about 8 threads, so it would be similar speeds.

I actually went from an i7 6800k to the ryzen 1700, it was a massive difference then too

Sent from my SM-G986U1 using Tapatalk

[Khun_Doug]

I bought the Ryzen 3950X in March of 2020, before inventory went to nothing. I was on a waiting list for the Ryzen 5950X and got it at MSRP, not the crazy prices scalpers are asking. That 5950X with all those threads is a serious piece of silicon (big iron back in the mainframe days). Actually, so was the 3950X. I'm amazed that everything runs faster, but at the same thermals or less, and in the same socket on the same motherboard. The X265 encodes move along quite quickly.

[Joekiwi]

[QUOTE=MysteryX;1944442]I saw 2 issues with StaxRip.



Also, if you add KNLMeansCL, both Medium and Strong presets are exactly the same (h=4). Btw I personally found that setting d=2 is generally worth the extra computing (but not a=2).


Thanks for that - I saw they were the same as well - I will try d=2 as well - I don't try too hard to be the best encoder - but I believe temporal noise reduction is the safest - I mean if a film is 24 fames/second - you just have to be aware of effects flashes of brief light.
I only use light if at all - my GPU does it - so too much slow down

[StormMeows]

Hey guys, I have finally started encoding with Staxrip. I originally backed up my blu-ray collection (lossless), but now I am encoding the backups to save on space. I am trying to figure out how to approximate the end file size. The problem I am having is the first movie ended up being 10GB BIGGER than the original lossless file so I know my CRF value is too low.

I did the "Run Compressibility Check" within Staxrip. This uses my encoder settings, but with a CRF 18. Here are the results for this movie:

Size in MB: 9,162
Video Bitrate 8,000
Quality 44%
Compressibility .38

How can I determine the lowest CRF value to use based off of this compressibility check? In my original encode I used a CRF of 14 and it made the bitrate 40.9 MB/s. The original blu-ray is only 23 MB/s. It appears I would need to use at least a CRF of 20 on this movie, but is there a way to roughly tell what CRF to use based off of the information I have provided? I want the new encoded version to be as close to lossless, but I need to save at least some space, definitely not almost double the original lossless file.

*EDIT* I think I am most likely going to need to use Selectrangevery in the script and do test encodes per ~10 minutes of the film at different CRF values and estimate the final value size. Please let me know if this sounds like the best plan of action.*

Hopefully this all makes sense. I'm loving StaxRip so far for backing up my collection and hope you guys can help. Thanks!

[Atlantis]

I also use SelectRangeEvery for compressibility check. It is by percent. Here are the values I calculated for myself:

1% Compressibility Check = SelectRangeEvery(4800,48)
2% Compressibility Check = SelectRangeEvery(2400,48)
5% Compressibility Check = SelectRangeEvery(1440,72)
10% Compressibility Check = SelectRangeEvery(1200,120)

2% and 5% are the best to get an approximate of the final bitrate. Sometimes the final bitrate is a little lower.

To make you feel good I always use CRF 22 for 1080p.

[shodan5000]

Any idea of when a new beta release might be dropping?

[JKyle]

Dendraspis is working on the next release (v2.7.0) and it will be available no later than next week according to him. See here (https://github.com/staxrip/staxrip/discussions/734#discussioncomment-965751).

I'd like to take this opportunity to post a BIG WARNING in advance regarding the next release version: if you want to carry along your custom Encoder Profiles to the new release version, you need to back up the custom Encoder Profiles before update and restore them after the update.

This is because aomenc is now renamed to AOMEnc at the source code level and thus all the Encoder Profiles are reset accordingly.

And since I've added/updated dozens of filter plugins and profiles, there's gonna be a big change in the filter menus (default filter profiles) for both AVS and VS. If you have any custom filter profiles, back them up and restore them after resetting the AVS/VS filter profiles. Refer to the Changelog (https://github.com/staxrip/staxrip/blob/master/Changelog.md) to see what filters will be added/updated.

[StormMeows]

I also use SelectRangeEvery for compressibility check. It is by percent. Here are the values I calculated for myself:

1% Compressibility Check = SelectRangeEvery(4800,48)
2% Compressibility Check = SelectRangeEvery(2400,48)
5% Compressibility Check = SelectRangeEvery(1440,72)
10% Compressibility Check = SelectRangeEvery(1200,120)

2% and 5% are the best to get an approximate of the final bitrate. Sometimes the final bitrate is a little lower.

To make you feel good I always use CRF 22 for 1080p.

Thank you, I am currently doing SelectRangeEvery(2000, 50, 10000)
and really like this.

Guys, what's the best way to check the encode sample to the source? Is there an easy way to do this so I can see the same frame on the source and encode simultaneously? I want to check for transparency between the new encode and source.

Also, is changing the "threads" and "lookahead threads" the best way to put my CPU at 100% usage with Staxrip? My current AMD 16/32 processor only uses 75% most of the time. I have the threads set to the default 0 each. This is what they look like in MediaInfo after the test sample threads=25 / lookahead_threads=6 / . Also, if there is a way to force the CPU at 100% saturation, then will there be a quality loss compared to the stock Staxrip settings? I should finally mention that this is for x264 8-bit blu-ray encodes.

Thanks for any help! I really appreciate it. I am new to Staxrip and loving it so far for high quality blu-ray encodes.

[Atlantis]

in Tools-Advanced there is Video Comparison.

SelectRangeEvery(2000, 50, 10000)
What does that 10000 do? Is that an offset and why are you using it?

[JKyle]

in Tools-Advanced there is Video Comparison.

FYI, there's another simple external tool for vertical-slider/split-screen two-video comparison: video-compare (https://github.com/pixop/video-compare/tree/20200724).

https://user-images.githubusercontent.com/18571394/117585888-d1a66900-b10c-11eb-9479-c3aabe4ddf97.gif

Since video-compare is a CLI tool, I made a very simple GUI for it: video-compare_GUI (https://github.com/JJKylee/video-compare_GUI/releases).

For more info, see this issue thread (https://github.com/staxrip/staxrip/issues/702).

[StormMeows]

in Tools-Advanced there is Video Comparison.

SelectRangeEvery(2000, 50, 10000)
What does that 10000 do? Is that an offset and why are you using it?

Thank you, I will definitely check this out! The 10000 value starts the movie at that segment so I am ensuring to not test the opening credits, etc. So 50 frames done every 2000 frames, starting at frame 10000. I have still been making some adjustments to this, but it seems to be working well for my test encodes.

Edit: I tried the program within Staxrip (Video Comparison), but the problem now is that my source is the full movie and my sample's first frame is 10000 at about the 5:30 minute mark of the movie. Any way that I can make it so it does the source at the SelectRangeEvery(2000,50,10000) like my test? Thanks!

FYI, there's another simple external tool for vertical-slider/split-screen two-video comparison: video-compare (https://github.com/pixop/video-compare/tree/20200724).

https://user-images.githubusercontent.com/18571394/117585888-d1a66900-b10c-11eb-9479-c3aabe4ddf97.gif

Since video-compare is a CLI tool, I made a very simple GUI for it: video-compare_GUI (https://github.com/JJKylee/video-compare_GUI/releases).

For more info, see this issue thread (https://github.com/staxrip/staxrip/issues/702).
Edit: I gave the program a try, but with any videos I try, it just gives me a [Win2Error] The system cannot find the specified file. I tried it on multiple blu-rays on my hard drive .MKV files. Also, if I can get it working, similar to my question above, how would I alter my source .MKV so it starts at the same frame as all of my tests? Thanks

[JKyle]

Edit: I gave the program a try, but with any videos I try, it just gives me a [Win2Error] The system cannot find the specified file. I tried it on multiple blu-rays on my hard drive .MKV files.

Make sure you put the executables in the same folder.

Unzip the compressed 7z file and put video-compare_GUI.exe in the same folder as video-compare.exe.

And you need to cut the video files to make them in sync.

[StormMeows]

Make sure you put the executables in the same folder.

Unzip the compressed 7z file and put video-compare_GUI.exe in the same folder as video-compare.exe.

And you need to cut the video files to make them in sync.

Sorry I do not see where to downloaded the executables. Can you link me to them please? I just see the GUI.exe file. I see a bunch of "Code" in the link, but I tried those in a folder with the GUI and it still doesn't work.

So I should cut the source using the same SelectEveryRange that I used on the test encodes? What program should I use to cut the source to match the test encodes? Thanks

[JKyle]

For video-compare, download the file in the release page.

And you shouldn't re-encode the reference video. Use stream copy cutting with MKVToolNix or ffmpeg. Google for how to do it.

[StormMeows]

For video-compare, download the file in the release page.

And you shouldn't re-encode the reference video. Use stream copy cutting with MKVToolNix or ffmpeg. Google for how to do it.

Thank you! I didn't even think about using MKVtoolnix. That makes it WAY easier! I use that program all of the time. Thank you again :)

[JKyle]

Thank you! I didn't even think about using MKVtoolnix. That makes it WAY easier! I use that program all of the time.

Or you can do the stream copy cutting of the reference video on StaxRip with Preview (for trims) and Copy/Mux (for video encoder), No Audio, and MKV(mkvmerge).
That's basically the same as using MKVToolNix and maybe more intuitive.

[StormMeows]

Or you can do the stream copy cutting of the reference video on StaxRip with Preview (for trims) and Copy/Mux (for video encoder), No Audio, and MKV(mkvmerge).
That's basically the same as using MKVToolNix and maybe more intuitive.

Awesome! I also found a way by using Asynith+ and AVSpmod with the help of a fellow member. This is such an awesome community!

Also, I made a post in regards to this, but I figured I would ask it here in case you guys know. In Staxrip if I leave the GOP settings default, it rounds down the min keyint value to 23 since my bluray source is 23.976. I have seen others highly recommend to set this value to 24 (min--keyint24). Which is technically the correct way of doing this? I realize it is 24 FPS on most blurays but 23 isn't far off. Also, how important is this setting for video quality? I realize it is the minimum distance between I-frames but I'm not an expert so I don't know what that entails for my final encode. Thoughts greatly appreciated! Thanks guys