StaxRip 2.0 Support Thread

[stax76]

Originally Posted by Zgin

Hey, anyone here were using batch in staxrip? Let's say I have like 26 anime episodes in .mkv with .ass subtitles muxed in it. I want to encode it from .mkv to .mp4 with hardcoded subtitle. Were trying options > subtitles > every option and it just don't hardcode subtitles into .mp4 file. At the moment I have to open 26 stances of staxrip and in everyone manually open episode and then via ctrl + h add subtitle. Please help

I'm not if this is a well-supported scenario, feel free to create an issue on the tracker.

[DavidRyan]

Originally Posted by Atlantis

On the other hand if it was the average bitrate, it is very useful. At any moment you know how the end result will be. The more you get to the end of the encoding, the more the bitrate information is accurate.

The estimated size is telling us this though, just in another way. The closer to the end of the encoding the more precise the size information will be, and size is directly correlated to average bitrate of course. To me a combination of current bitrate and estimated average size is two different useful pieces of information. But having said that I always thought it was showing average bitrate, as it doesn't fluctuate much and gradually settles to a range.

[Atlantis]

Well, the formula doesn't help when I'm in the middle of encoding because I don't have the size when the file has not been written yet to disk. And when the job is finished, I don't need it anymore.

44vince44, I still have not gotten an answer to why current bitrate is important. What do you do with it exactly. What do you learn from current bitrate?

I am using the version that shows only the current bitrate and remaining time.

[44vince44]

Use builds "M" of Patman: any moment, you have the size written, AND an estimate of the total size.

[44vince44]

Monitoring the instant (current) fps allows me to check at times if there are peaks of data rate. When I see very high peaks, I can abort encoding and change my encoding strategy by setting a high limit (using VBV-Bufsize and VBV-Maxrate).
This monitoring is possible with instant fps, and it's NOT possible with average fps.

[Atlantis]

But if your encode takes 7 hours or 2 days, you sit in front of the monitor all that time? For how long do you sit and watch the current bitrate?

[Atlantis]

Thank you for stable release 2.1.3.0. I just clean installed it and using it.

Thank you for Extract DTS Core feature. As I said before this is more useful and makes more sense at the demux stage and not at the encoding stage.

There are 2 scenarios.

1- You want to keep the core. You demux to DTS Core at demux stage and then use copy/mux.
2- You want to encode the core. Because the core is 5.1 and the HD is 7.1 for example. You want to encode the 5.1 mix. You demux the DTS core at first stage and then at the encoding stage, you can encode it to AAC 5.1 for example.

With eac3to -core you can easily extract it.

[44vince44]

Originally Posted by Atlantis

But if your encode takes 7 hours or 2 days, you sit in front of the monitor all that time? For how long do you sit and watch the current bitrate?

If the film takes 1 day encoding, I do check on it at least once an hour (except sleep time) and I do often rethink how to encode.

But then this is not about me, it is about what Patman decides, and it is about that all encoders display an instant bitrate, since they are variable bitrate and it makes sense to show the variation of the bitrate.

[jlw_4049]

@stax76

In some of the later updates the ability to drag and drop srt subtitles into the container options window is gone.

Sent from my SM-G986U1 using Tapatalk

[44vince44]

Thanks Stax for the new release !!!

[DavidRyan]

Thanks for the hard work on the new release

[stax76]

In some of the later updates the ability to drag and drop srt subtitles into the container options window is gone.

It was lost in a modernization effort that involved moving code from a custom control that was no longer needed directly into the form. Fixed in the next build.

[jlw_4049]

Originally Posted by stax76

It was lost in a modernization effort that involved moving code from a custom control that was no longer needed directly into the form. Fixed in the next build.

Thank you again sir

Sent from my SM-G986U1 using Tapatalk

[DenFox]

I updated to 2.1.3.0, but now when I try to add a hardcore subtitle, staxrip crash! Even with the previous version (2.0.6.0)!

What could it be?

[stax76]

Originally Posted by DenFox

I updated to 2.1.3.0, but now when I try to add a hardcore subtitle, staxrip crash! Even with the previous version (2.0.6.0)!

What could it be?

It's probably caused by a change in avisynth 3.6, there is an issue on the tracker:

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

There are few possible solutions:

1. install avisynth 3.5, staxrip will not allow an old version to be used because of compatibility changes introduced with avisynth 3.6, but staxrip has a setting to disable version verification, in the settings there is a danger zone setting for it. It should probably only used by power users and not permanently.

2. install avisynth 3.5 and modify the file \Apps\Versions.txt, this file contains all the version information of all the tools. There might be two ways to edit the file, the first is deleting the avisynth line, that's easy and will probably work, if not the line can be modified with the last change date of the DLL and the version name.

3. Use VapourSynth instead of AviSynth.

4. Wait until somebody fixes AviSynth/VSFilterMod.

[DenFox]

Originally Posted by stax76

It's probably caused by a change in avisynth 3.6, there is an issue on the tracker:

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

There are few possible solutions:

1. install avisynth 3.5, staxrip will not allow an old version to be used because of compatibility changes introduced with avisynth 3.6, but staxrip has a setting to disable version verification, in the settings there is a danger zone setting for it. It should probably only used by power users and not permanently.

2. install avisynth 3.5 and modify the file \Apps\Versions.txt, this file contains all the version information of all the tools. There might be two ways to edit the file, the first is deleting the avisynth line, that's easy and will probably work, if not the line can be modified with the last change date of the DLL and the version name.

3. Use VapourSynth instead of AviSynth.

4. Wait until somebody fixes AviSynth/VSFilterMod.

Avisynth 3.6.0 uninstalled, after that I installed Avisynth 3.5.1.

It works!

Thank you so much!

[44vince44]

Stax, thanks for including me in the contributor's list, that was a nice surprise :-)

[mcjordan]

NVEnc 5.0.5 is released.
AVSMeter 3.0.1.0 also.

[Lynx_TWO]

Apologies if I already posted this, but couldn't remember...

Is it possible to get a Frame Sequence / Image Sequence option added for the Source input? Preferably 16-bit TIFF files (.tiff and .tif) but 8 and 16 bit PNG file support would be pretty sweet as well. You'd need to be able to tell Staxrip what frame rate to interpret, and those could be:

8 fps (anime)
12 fps (drawn animation)
15 fps (gif animation)
23.976 fps (NTSC)
24 (film)
25 (PAL)
26 fps (3-strip Cinerama)
29.97 fps Drop Frame (DF timecode)
29.97 fps non-Drop Frame (NDF timecode)
30 fps (TV show)
47.952 fps (2x 23.976)
48 fps (HFR)
50 fps (PAL)
59.94 fps Drop Frame (DF timecode)
59.94 fps non-Drop Frame (NDF timecode)
60 fps (NTSC HD)
120 fps (slow motion output)
240 fps (slow motion output)

With the addition of Topaz Video Enhance Ai and there 16-bit TIFF output being the fastest option, it would be nice not to have to input into Adobe After Effects or similar just to encode a 1.3TB AVI to re-encode it in StaxRip, especially if using to enhance old family footage.

Thanks so much for all you do!

[stax76]

There is a request issue on the tracker and it's still open, if you add your requirements and technical details then there is a much higher chance that I actually do something about it. With details, I mean sample script and filenames of the first and last file, media info and possible GUI options like the suggested frame rates.

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