I might be wrong but, from the work-in-progress they have shown over time, I would guess that SLR is using AI to track features optimized for porn (dick, mouth, hand, eyes, hips, shoulders, etc), followed by algorithmic rules (i.e. not AI) to generate the actual scripts.
But they might have pivoted to something else, I don’t know.
For me, the holy grail would be to have AI model that uses left and right VR images to create a 3D pose. Unfortunately, this is not useful outside of porn so there might not be a lot of money poor into that field. I wonder if it would be possible to train a model like that using data generated by Virt-A-Mate.
followed install to the letter but am receiving this error when running the bat. Never installed before.
‘FunscriptToolbox.exe’ is not recognized as an internal or external command,
operable program or batch file.
If the error occurs when running “–FSTB-Installation.bat”, you need to make sure to run the batch file on a drive (ex. C:), it won’t work from a network path (ex. \my-other-PC\share.…).
If the error occurs when running “–FSTB-PrepareVideoForOFS.1.0.bat”, make sure that the path found in the batch file is correct:
It’s not meant to be able to help with every type of action. Right now, it does an OK job of hardcore actions (and it is still not perfect even for those).
When the original resolution of a 2D video is ‘not standard’ (in your case, 1216x2160), and FunscriptToolbox tries to scale it to a fixed height (i.e. 2048), the resulting resolution might not be divisible by 2 (in your case, 1153x2048) and ffmpeg doesn’t support that. See this reply for more details: link
You should try this (i.e. no scaling): "--ffmpegfilter=-filter:v scale=-1:-1" ^
instead of --ffmpegfilter=2D ^
Hi, first of all - Top job. With the Demo File all works fine, but I’am not able to configure a 2D bat File without an error. What are the latest .bat changes to process a 2D File? Could you please provide a example ? What did wrong?
Thanx in advance
My current bat.part.
" …FunscriptToolbox.exe ^
motionvectors.prepare ^
–ffmpegfilter=-filter:v scale=-1:-1 ^
*.mp4
PAUSE"
Video Name is “test1.mp4” with a resolution 1280x720
Error message is:
— motionvectors.prepare —
scale=-1:-1: Creating a motion vectors optimized video (i.e. p-frames only file) ‘-1.mvs-p-frames.mp4’
scale=-1:-1: using provied filter: -filter:v… System.AggregateException: Mindestens ein Fehler ist aufgetreten. —> Xabe.FFmpeg.Exceptions.ConversionException: ffmpeg version 6.1-full_build-www.gyan.dev Copyright (c) 2000-2023 the FFmpeg developers
built with gcc 12.2.0 (Rev10, Built by MSYS2 project)
configuration: --enable-gpl …<many text>…
libpostproc 57. 3.100 / 57. 3.100 Unrecognized option ‘1.mvs-p-frames.mp4.temp.mp4’.
Error splitting the argument list: Option not found
bei Xabe.FFmpeg.FFmpegWrapper.<>c__DisplayClass14_0.b__0()
bei System.Threading.Tasks.Task`1.InnerInvoke()
bei System.Threading.Tasks.Task.Execute()
There is definitely something wrong. You seem to end up with the filename “-1.mvs-p-frames.mp4” passed to ffmpeg, which is then interpreted as an argument by ffmpeg because it starts with a “-”.
I just tested it.
The problem is that you need quotes around the ffmpegfilter argument because it contains spaces. Like this:
I’ve been playing with various optical flow codes the past month or so, RAFT seems to generate the best outputs but it’s slow. And that’s after downsampling one half of each frame to 512x512. Downsampled to a consistent resolution followed by optical flow is my current choice of input image format. Have you found better? OpenCV methods seem pretty slow as well with inferior outputs.
Thanks for that, after a bit of trial and error I got it right with my own video!
But the whole thing only works with one body moving, it doesn’t work with two bodies moving in different directions, or is there a trick?
First off, thanks so much for making this! I’m getting into scripting and this seems to be an indispensable tool in expediting the creation process. Now that I’ve got cooking I can see even without the automated insertion that the visual indicators can help you “see the future” on where a stroke is going to begin or end. That in turn helps you to see where to place the markers to get the automation insertion to do much of the work for you after that.
Something else I didn’t realize is that the min/max/center pos and other options adjust the insertion on the fly. I thought I was going to need to adjust this before the automatic insertion. Very, very useful.
That said I wanted to give some feedback on some stumbling blocks I ran into getting things started. Towards the top of the instructions it’s mentioned:
Note: If you move the “FunscriptToolbox” folder in the future, you will have to re-run --FSTB-Installation.bat to update the plugins and ‘use-case’ scripts.
This isn’t the full story and after installing it, I wanted to move it to a different location, but ran into the issue memeweaver encountered with FunscriptToolbox not being recognized as an internal command as the path in --FSTB-PrepareVideoForOFS.1.0.bat did not get updated even though I re-ran the batch script as instructed. (Perhaps because I moved it into the ProgramFiles/OpenFunscripter directory and didn’t have administrative privileges?
I patched this up and got rolling however I ran into another issue where after running the batch file I did not have the *.mvs-visual.mp4 file. Instead I had *.mvs-p-frames.mp4 and *.mvs-visual.mp4.temp.mp4. These as you may expect did not work correctly.
So I decided to move it again and do a “complete uninstall/reinstall”. With this I deleted where I had extracted this MotionVectors plugin saved to (C:/ProgramFiles/OpenFunscripter/FunscriptToolbox) as well as %appdata%/Roaming/OFS/OFS3_data/extensions/FunscriptToolBox.MotionVectors.
After this I re-extracted to a non-admin place, and followed install instructions. Everything seems to be working.
My lingering question is if I missed anything in “completly uninstalling” the plugin before re-installing it; in case I run into any more issues. Also just wanted to document my troubles if anyone else runs into them.
Thanks for creating this. I’m finding it helpful, and I’m trying to improve my technique with the tool.
I’m looking for a “best practices” way of handling a particular kind of scene:
The girl is rubbing her pussy in a circular motion, so at the top all of the vectors are pointing right (3 o’clock), down as she moves her hand down (6 o’clock), left at the bottom (9 o’clock) , then up again as her fingers move up (12 o’clock), finally turning to the right (3 o’clock) .
In setting up the stroke points in OFS to prime the tool for the best outcome, is it better to ‘lead’ the top and bottom point so that they are still on the up/down vectors, or at the top and bottom of the swing, where the motion is 3/9 o’clock?
Also: Some of us are red/green colorblind, so if there’s not-green arrows out there (not the black and white arrows), I can’t tell.
When you’re adjusting the Activity/Quality/Min sliders, and the vectors on the part of the video you’re interested in are going the correct direction, but thin black arrows, and not the fat (green) arrows, what does that mean?
Do the mpg files have to be in the .\FunscriptToolbox\FSTB-PrepareVideoForOFS folder once you’ve prepped them, or can they be moved to a project folder to be opened with OFS?
