Staxrip Templates Download
Roseanne Devon
Ok, thanks! I've just ignored this 2nd exception and it converted the video.
However, the output is 47.952fps (which is double the source 23.976). Sorry for such a nub question, but where exactly do you set the target FPS rate?
Yeah, tried 2.5 before, didn't work, that's why I wasn't sure this was the right place.
Ok, 5 works, but is there a way to make it 60FPS? Of course 120FPS (=x5) is even better, but that comes at a performance price I don't really want to pay since my monitor is 60FPS.
25/10 works!
By the way, does it matter if it's not exact 60FPS? Does it have any effect on playback (something slowly going out of sync or something)? I guess not, but I don't really know this stuff very well.
Thanks for the GIFs!
Interesting though, when I open a file, I get this popup menu
and when I select e.g. Automatic VapourSynth or VapourSynth ffms2 my SVP settings get overwritten and I have to copy&paste script again.
How come you don't have that popup menu and can use your templates and then load a file?
My StaxRip crashes when I try to open your srip files
But it doesn't matter as much since your guides/screenshots are detailed enough and are working for me. I just don't get why opening a new file overwrites my preset. Plus if you could point to a good guide on those settings (specifically, am interested in a few quality presets that have already been tested and can be used so I don't have to spend a lot of time reading on each of the options)
I am lost. I do not understand this. Could someone please post a _full_ info on how to convert video files to 60/75/90FPS etc?
Maybe you guys were doing this for years, but when it says "First we need to add svp to VS chain (make sure to fix paths):" it's like black magic to me. I don't know how to add SVP to VS chain. I don't know how to fix the path.
Can you be more specific what you need help with? There are already steps laid out above, even with gif screencasts that show where to click. You don't really need to understand toolchains or anything to be able to replicate it. I also did it with 0 experience with this stuff
I also would like some help because when I try to copy and paste those srip files into that folder and try to use them, I also can get the same error.
I don't know how to change the directory anyway inside of the file because I can't get to the script editor I can see in the gif
For whoever is interested in this method and would like to give crf 0 a try, you can my have my staxrip profiles with the gamma fix and my custom x265 settings included here - downscale profile*.
The first time StaxRip starts, it will ask where to store the Settings Directory. C:\ProgramData\StaxRip x64 is the most logical choice or choose any of the other locations or browse for a custom directory (bottom menu choice).
Creating custom templates let you do the same conversions over and over without having to change settings each time. Once a template is created, it can be chosen from the list and all special settings are loaded automatically.
StaxRip is an Open Source video encoding software that can turn videos into mpeg-4 format using codecs like x264, XviD and DivX. It can for instance be used to turn a video DVD into a much smaller sized video with barely any quality losses that can easily be stored on the computer. One interesting way is to use it to rip a TV series season to the computer creating those handy 350 Megabyte videos per episode. That way a complete season takes between 4-8 Gigabytes of hard drive storage compared to the up to 17 Gigabytes that it would demand if stored in DVD format.
One of the nicest features of StaxRip is the fact that it can download needed codecs and utilities from within the program interface. If you dealt with Open Source video encoders before you might have experienced that you needed to download and install the needed extras manually before the tool could be used.
StaxRip makes use of templates to speed up configuring the various settings and can convert or merge single or multiple files in one go. A video file that is loaded as a source will automatically be analyzed by the video encoding software and important values such as framerate, length or size will be shown in the interface. The same variables are shown in the destination pane where they will be automatically updated when the user changes a setting.
The output audio and video codecs have to be chosen. Multiple encoding profiles are available that range from fast to high quality encodings. The codecs can be configured furthermore for optimal results.
Effectively the MainConcept AVC/AAC encoder has been replaced with the MAGIX AVC/AAC encoder, which inherits the same functionality and adds rendering acceleration via QSV or NVIDIA NVENC (supported NVIDIA GPUs) and, as of build 361, AMD VCE.
AVC and H.264 are the same thing. It is a modern video format with wide support and high-efficiency compression, meaning that (if done properly) it gives high quality per file size. It is a very popular format for both offline playback, web playback, and upload to video-serving platforms such as YouTube and Vimeo. This post concentrates on those destinations.
Let's first assume that your source video is progressive (not interlaced), as this format is becoming more and more common and is easier to deal with (you can use MediaInfo to see if it's progressive or interlaced).
YouTube's officially recommended upload encoding settings are here. Vimeo's are here. The bit rates are are rather low if maximum quality is your priority. Also see this social media cheat sheet for video specs.
To start, open one of the 2 "Internet..." templates from "Render As" > "Output Format" > "Sony AVC/MVC" that nearest matches your project/target resolution and change the frame rate to match your project properties (which should usually be the same as your source media unless it is more than 59.94fps).
This is generally the better quality encoder. It is slower than the Sony AVC encoder. You can speed it up a lot with legacy GPU rendering, if you have an old graphics card such as an NVIDIA GeForce GTX 580 or AMD Radeon HD 6970, but the quality will suffer a little.
To start, open the template from "Render As" > "Output Format" > "MainConcept AVC/AAC" that nearest matches your target settings (e.g. "Internet HD 1080p") and change the frame rate to match your project properties (which should usually be the same as your source media unless it is more than 59.94fps). Even though a high frame rate value (e.g. 48, 50, 59.94) does not appear in the drop-down menu and there is no "custom frame rate" option, you can over-type it in manually in the white field.
x264 is a free, open-source codec that enables you to achieve higher quality for the same file size as the built-in VEGAS AVC encoders. It may also be faster than the VEGAS encoders, especially without GPU rendering.
You can render a high-quality intermediate file from VEGAS Pro and open it in a rendering app for transcoding to AVC. Be sure to choose or save a template that matches your project settings. Popular formats for intermediates include XAVC Intra (included in VEGAS, but the rendering app might not read it), Cineform (installed with GoPro Quik Studio), MagicYUV, DNxHD etc..
If the rendering app is 32-bit (x86) (e.g. MeGUI) then you can frameserve to it using the Debugmode Frameserver instead of rendering an intermediate. This saves you time and storage space because it writes the intermediate file from VEGAS only as it is required by the encoder.
After installing Debugmode Frameserver, it appears as an Output Format in the VEGAS Pro Render As window. If you have Frameserver already installed for Vegas Pro 13 you can get it working in VEGAS Pro 14 by copying:
The x86 apps, MeGUI and RipBot264 will accept files directly from Frameserver. x64 apps will not. The x86 version of MeGUI has not been developed since 2015 but its plugins including x264 can be manually updated.
Note that there are 2 bugs with Frameserver in Vegas Pro 12 and later. Firstly it will only serve audio at 44.1kHz. That is not a major problem for web video, as much of it is delivered at 44.1kHz, although YouTube are now recommending a sample rate of 48 or 96kbps. Secondly, the last second of the audio stream is corrupt and extends beyond the video stream. You can ignore this if the very last part of your video is silent or unimportant, or you could work around it by rendering audio separately from Vegas at 48Khz and remuxing with the video, or you could use the following process...
The RenderPlus script within Happy Otter Scripts provides a convenient interface for rendering from VEGAS Pro using the x264 codec (and other codecs) via Debugmode Frameserver. The required installation and configuration of the third-party tools such as Frameserver and x264 is handled by the Happy Otter Scripts installer, and it compensates for the Frameserver bugs mentioned in part 4b.
For a straightforward render for upload to YouTube etc. it is recommended to use the "Simple" Render Mode and to choose either the x264-good quality-medium-crf 23-aac192 or x264-high quality-slower-crf 18-aac 320 encoder template. I usually use the latter, but note that it is slower and the file size is larger than the "medium" template.
It is also possible to access all sorts of AviSynth processing and encoder settings using the Advanced render mode, including GPU rendering, slow motion, denoising etc., or to do an x264 render using the AviDub script within Happy Otter Scripts.
Vegas2Handbrake (see here if that link doesn't work) automates the process of rendering with Handbrake and is popular with many community members for rendering AVC. By carefully following the instructions to add a 1 second buffer you can also compensate for the Frameserver audio bugs.
7fc3f7cf58