Small update
Poll has been updated with status: poll
also:
API consolidated (just one api for Heresphere and MFP or others, you can also use HereSphere to playback in VR and connect to MFP to drive the toys with multiaxis scripts)
Can you add a way to manually pair scripts + videos? It seems to ignore everything that isn’t a 1:1 match and this makes using multiple scripts for one video especially difficult
The system expects files to be aside the video.
Naming is matched as follows:
[filename]. funscript - direct pairing
[filename].[description].funscript - additional scripts
[filename].[twist,pitch,rol,…].funscript - multi-axis scripts
Yes I was hoping you could add the functionality to pair the videos to their scripts manually regardless of file names. Or at least one that makes renaming automatic via some method.
BTW, can you make it can be show as folder? I mean, I have already sort some them by artist in different folders. But in manager, they are all showed there without any categories.
im working on a metadata assignment which is checking filenames and funscript tags and optionally TPDB to assign performers and studios alongside with categories, the sidebar allows filtering on this in the future (next release)
for the moment, you can filter by path in the search box
I added intiface/buttplug support, no direct lovesense.
It will only work if intiface is detecting your device and you konfigure intiface as a source.
Settings → General → Device Sync → Backend → Intiface Central
As already mentioned, this is a false positive caused by the build process.
Unfortuantely most malware is using the same processes to hide themselfves.
Also, you checked version 0.9.0 which was a singelefile build which has been changed due to this problem.
The actual version 0.9.13 is not using single-file builds anymore.
A section regarding this situation is mentioned in the readme shipped with the app.
Here are the actual scans from virustotal for the latest release version:
EXE ONLY:
ZIP FILE:
Please pay attention tho the behaviour analysis.
Why False Positives Occur
1. Packer/Compiler Signatures
Nuitka compiles Python code into a standalone executable by bundling the Python interpreter, libraries, and your code into a single file. This “packing” behavior is similar to what malware authors do to obfuscate their code. Antivirus engines flag these generic signatures.
2. Low Prevalence / Unknown Software
Antivirus engines use reputation-based detection. A newly compiled executable has zero reputation - no one has seen it before. Low prevalence = suspicious by default.
3. Embedded Python Runtime
The bundled Python runtime (DLLs, bytecode) contains code patterns that some heuristic engines flag as suspicious, even though they’re completely legitimate.
4. Generic Heuristic Detection
Names like “Trojan.Generic”, “Malware.AI”, or “Suspicious.Packer” indicate heuristic (behavior-based) detection, not actual malware signatures. These are educated guesses, not confirmed threats.