FunscriptToolbox (FSTB?) is a command line tool that contains multiple features that can analyze and/or transform .funscript files.
Installation verb
installation
When starting --FSTB-Installation.bat in FunscriptToolbox folder will call this verb and it will install the OFS plugin and creates some use-case folder for the others verbs bellow.
AudioSync verbs
audiosync.createaudiosignature
audiosync.createfunscript
audiosync.verifyfunscript
Allow the synchronization of a .funscript to a video different than the one used by the scripter.
Use the application --help argument to see the application documentation.
See below, in the comments, for some use cases.
MotionVectors verbs
motionvectors.prepare: Prepare a video for others motionvectors verb
motionvectors.ofspluginserver: Starts a server to respond to plugin request.
Every .funscript file that the tool creates or overrides is saved in a “vault”, found in “%appdata%\FunscriptToolbox\Vault”. If you ever make a mistake and override the wrong file or something, check this folder for your old file.
The tool also keeps log files of the last 10 executions in the folder “%appdata%\FunscriptToolbox\Logs”.
Binaries and Sources
FunscriptToolbox is fully open source over at github.
The tool should be useful for some old scenes that have been altered after a script has been created. For example, NaughtyAmericaVR has a bad habit of altering their intro or even changing some parts of the scene (see Wake and Bake).
I know that @JohnSilverGold has been able to re-synchronize a few of his NA videos with this tool.
It should also be useful for 2D scripts that are often based on videos from free site (pornhub, etc), which can also change their video without notice.
So far, I haven’t found an application (OFS, scriptplayer, etc) that wasn’t able to read a .funscript with an embedded signature. Let me know if you find an application that is not able to read the file.
Fixed a stupid bug where I moved files, instead of copying, to the %appdata% vault.
So, when generating a file, the file was created and then moved immediately to the vault. So, it seems to disappear.
Oups. Fixed in 1.0.1.
Download & extract the tool somewhere (for example, C:\Tools\FunscriptToolbox)
Create a folder “ScriptToRelease” (or anything you like).
Create a batch file “PrepareForRelease.bat” in the folder “ScriptToRelease”, with the following content (modify the path of the tool if needed):
Notes:
If there is interest, I might expand the tool with commands that could be added to the PrepareForRelease batch file, like adding your default metadata, creating the heatmap image, downloading all images found on the video url, etc).
The tool might not work well with video with music since it’s trying to match similar audio sections. With music, there might be a lot of sections with almost identical audio.
After that, each time you create a script
Move new-scene.mp4 and new-scene.funscript to the folder ScriptToRelease.
Start “PrepareForRelease.bat”.
Your .funscript, with an embedded audio signature, is ready to be released.
Your job is done.
In theory, you should not have to synchronize your script with all versions that exist on the internet.
“Consumers” should be able to do that themselves.
Download & extract the tool somewhere (for example, C:\Tools\FunscriptToolbox)
Create a folder “ScriptsToValidate” (or anything you like).
Create a batch file “ValidateScripts.bat” in the folder “ScriptsToValidate”, with the following content (modify the path of the tool if needed, add --verbose argument if you want more logs):
How to create synchronized .funscript for a remastered video
If you have acces to scene.funscript, scene.mp4 and new-remastered-scene.mp4, the easiest way to create a synchronized funscript for the remastered scene is to open a command prompt and use this command:
For the last few weeks, I have been working on an OFS plugin to speed up scripting, tied to new features in FunscriptToolbox. It should be finished in a week or two but it’s already usable.
