ffmpeg - staxrip/staxrip GitHub Wiki

Patman ffmpeg build

Features

• VapourSynth enabled
• Manifest to enable AviSynth Unicode support on Windows 10
• Manifest to enable Long Path support on Windows 10
• UPX packed to shrink the file size

Download

https://www.mediafire.com/folder/vkt2ckzjvt0qf/StaxRip_Tools

Note for ffmpeg and portability of StaxRip

So far ffmpeg has been the only hurdle for portability. (All other tools - including mod versions - started supporting portable AviSynth by incorporating a command line option to call portable AviSynth.dll.)

Since ffmpeg does not accept the PATH environment created by a StaxRip session, StaxRip has adopted so far a soft link to portable AviSynth.dll to force its priority on ffmpeg (over system AviSynth.dll).

But since many people are experiencing issues with this 'soft link' method, StaxRip changed its internal design to avoid this fuss, starting with 2.1.7.8 Beta.

Now StaxRip moves ffmpeg.exe itself depending on the use case. By default, it is located at the same folder as portable AviSynth.dll. Thus, portable AviSynth.dll has priority over system AviSynth.dll for ffmpeg.exe by default.

However, in case ffmpeg needs to use system AviSynth.dll instead of the portable one, ffmpeg.exe is moved back to the folder %startup_dir%Apps\Encoders\ffmpeg\.

But there's a catch here. It's not moved readily to the new location by the user's Frameserver Mode setting. It moves based on demand: that is, only when the system AviSynth.dll is needed by ffmpeg.exe - when it needs to read an avs script (Decoder: AviSynth, Pipe: ffmpeg).

To be precise, ffmpeg.exe and related files are moved on 4 occasions:

• Before the Apps dialog is shown (not strictly necessary)
• After the settings dialog closes (not strictly necessary)
• Before 'Execute Command line' (strictly necessary)
• Before Jobs are started (strictly necessary)

In order for this to work, the user is required to have write access to StaxRip folder and its subfolders.