The alpha/beta scripts relate to the position of the sensation. If you have multiple motors, you may be able to move sensation between the different motors depending on the alpha/beta position, but that might be pretty hard. For this specific file you can try to increase the speed of the glans motor when alpha is very close to 1, and the prostate motor when beta is very close to 1, and the perineum motor when beta is very close to 0. In this specific file alpha is rarely 0, so you don't have to write special code for that.give_a_nap wrote: ↑Sat May 25, 2024 2:08 amWow. Who knew I'd be schooled in DSP-ing in Milovana!
Thanks for sharing this, diglet.
I am a complete noob in all of this - discovered funscripting with Lovense toys only a couple of weeks ago ( viewtopic.php?p=363142#p363142 ) and have "lost myself" in the process (in a good way). Collecting funscript materials as I go, and wanted to ask you - which of the 5 funscripts you created would be the best one to use with vibrators?
Also: I hacked monsieur_so's Python script to drive my Edge2 and my Gush at the same time, but I'm also thinking that perhaps I can "push the envelope" here and use the data from two (or more? the Edge2 has two motors) of the funscripts at the same time?
The volume axis corresponds closely to the strength of the overall sensation, so definitely use that as a baseline for all motors, make small adjustments depending on the other axis.
If the pulse frequency axis is low you may try to on-off a few times per second. Maybe that won't work at all because the motors have too much inertia to turn on/off quickly. During the good boy sections (where pulse frequency is often low), the sensation is intended to be more intense than usual, so you may have to turn up the motor power during these sections.