This looks really cool. Another way this could work would be outputting values that can be plugged into VAM to control the parameters of random stroker plugins such as ForceForge, or FillMeUp, or to control a state machine that selects preset stroke states. That way the model in VAM would create the movement and that could be transmitted to at SR6 via ToySerialController.
This is amazing! I wonder if it’s possible to allow audio, from a video or a mic, to have some influence on the action? Perhaps a slider to control the level of influence? Concept being it could allow some influence from a video, without the need for funscripts dictating the action. IMHO, the Edgy concept is potentially better than funscripts because it’s based on the user’s arousal. But some loose coupling with video would be nice. Obviously, this depends on the audio following the action, but many PMVs do.
Bravo! Working perfectly with intiface central 3.x and lovense solace pro
This seems to not work with older versions of Intiface, and I am not updating Intiface to 3.xx since it breaks some other connections I use.
The serial connection is enough for me, I just figured I mention this
Wow this is great! It’s very exciting and I had been thinking of building something similar for a while. I think your curve-based approach is better than the state machine I had come up with.
Do you accept code contributions?
When it comes to features, I’d like to have the probability of triggering one gesture per orgasm (for instance, 50% of ruined orgasm). Other than that, I know that it’ll be the gesture’s probability curve, but if I set it to 50%, it means it’ll get 0.5 odds of triggering for each tick/random-draw, and I don’t know how many of those there will be, how often or how that’s calculated.
If I had a way to contribute to this, I’d also add a way to trigger an orgasm event when the dial is at 100 - For instance, you’re at 100%, you’re at the edge. 10% odds of triggering an orgasm event that gives you 7 seconds to cum, then it stops. Perhaps add an edge counter, and have a curve for the orgasm event trigger via a number of edges. Have the possibility to config it such that I cannot trigger the orgasm event, I have to earn it through edging, or through time.
4 Likes
Does anybody have any presets they could share?
Could you perhaps implement somewhere to share presets?
Hi everyone, new update with version 1.4: video player with funscript sync and arousal control + variation duplication. But before going deeper into this update…
@StyleMavin Thanks! VAM integration is an interesting idea, I’ve just discovered that. Exposing the arousal value and pattern data as an external output (WebSocket or OSC) could open the door to VAM plugins and other tools. Not on the immediate roadmap but I’m noting it down, it could be very fun.
@JakofClubs Glad you like the concept. Audio reactivity is something I’ve been thinking about. Using the audio signal (from a video or mic? Oo) to modulate the device would fit well with the existing arousal system. I’ve already planned some experiments with funscript profiles to create new behaviors from them, but using audio could be a good approach for PMVs indeed!
@Coreshirataki Nice, glad to hear it works with the Solace Pro!
@KinderAeg Interesting thing about older versions of Intiface, I will take a look but I don’t think I’ll manage multi-version connection for Intiface, it could lead to messy maintenance of the app and I suppose that Intiface will fix the issues you’ve mentioned.
@zumamu Thank you for your feedback! Indeed, curve-based feels good in that way. In fact Scripts Control was mostly a draft application of The Edgy with some kind of “state machine” that came with some limitations.
About code contributions, I’m actually a fresh freelancer and I’m planning to live from all my apps revenues. I know that The Edgy will not generate much revenue (only referral links and maybe a donation button for lovers 
) and I want it to stay free. But a small revenue is a revenue, so I can’t, for now, make the source code public. I hope you understand my point of view. Be sure that if I can no longer maintain the app, I will release the source code ofc 
For triggering one gesture per orgasm with a percent chance, like you mentioned, the fresh version has some fixes about it, so you can check how “The Cruel” can edge you: percentage of chance to play a flat shape for 10s, 6 times in a row. Tell me if this suits your needs!
And finally, the way you want to earn the orgasm through an edging counter or probability is something to think about. Let me just think about it.
@oramger There is already a feature to import/export presets that people can share here. For now it’s not planned to add a server-side sharing system, but you’re not the first to ask for it so I will take a look
2 Likes
Version 1.4 is out! Funscript video player, orgasm programs, and more
Funscript video player
You can now load a video + its .funscript and play them in sync with full arousal control. The player has a seekbar with waveform preview, thumbnail on hover, cinema mode, and fullscreen. Pause the video, pause the session. Simple.
But here’s the twist: your arousal dial still works on top of the funscript. At neutral (default is 50% of arousal level), the script plays as written. Turn the arousal up, the movements compress. Turn it down, they amplify. There’s a configurable neutral point slider so you can tune where the “as written” zone sits. Basically you get the precision of a funscript with the edging control on top.
You can also switch from funscript to behavior mode at any time. Don’t forget to set your behaviors as favorites to get quick access buttons in fullscreen:
Orgasm programs for funscript mode
Since funscripts don’t have an “orgasm phase”, I added standalone orgasm programs. Same curve system as behaviors (velocity, stroke zone, amplitude, hold + variations), but designed to temporarily override the funscript when you trigger an orgasm. 4 presets included (Fast & Intense, Progressive, Slow & Deep, Edging Release), and you can create your own in the editor.
Import/export works too.
Variations collection
Variations (gestures) are now stored in a shared library. You can link the same variation across multiple behaviors (edit once, syncs everywhere) or copy it for independent customization. I’ve added a link/unlink mode so that a linked variation and its modifications will be shared between the linked behaviors. Unlink with a simple click.
Full changelog at Changelog | The Edgy
Let me know how it feels, especially the sync accuracy. I’ve spent some time making the arousal changes as seamless as possible. Curious to hear if the neutral point default works for most scripts or if you need to adjust it.
You now have an easy way to cheat on cock hero videos btw ^^
8 Likes
Top tier thinking with the funscript on-the-fly adjuster, my dude.
1 Like
Legend.
I’m not a programmer by any means, but is it realistic that your service easily could to be ported to a local Electron-based app for offline use? Just a random thought
3 Likes
Looks really great! Regarding compression and amplification, right now it looks uniform. It would be great if you could compress it into a certain direction or make that dynamic too. This way you could compress it into a direction, e.g lower or higher strokes. Thresholds could also be useful, e.g. A curve for compression based on speed, length, location and similar.
what is neutral arr?
@KingCobraKush yep, always felt like funscripts needed that extra layer of control. Glad it clicks ^^
@Coreshirataki Legend right back at you 
Not off the table, but there are higher priority items right now. I’ll keep it in mind.
@Kumon Thanks! Good feedback. Right now it compresses uniformly toward center (moving average), which works for a basic “dial it back” use case but can lack some “nuance”.
Directional compression is interesting. Compressing toward the bottom (shorter strokes at the base) vs the top (tip-only) would give a completely different feel at higher arousal. And yeah, a curve for compression based on stroke properties would open up a lot of creative space.
Noted it down, this is the kind of granular control that makes it actually useful for different styles.
I’m also planning some feature to add/decimate points along the funscript througth the arousal level. But I have to take care to not going to deep cause there are limitless use case with funscript and I don’t want the to be messy with a lot of parameter. It’s actually growing in that way with the editor, a fresh user can be totaly lost without onboarding
BTW version 1.4.1 is out to include referral and a support link
2 Likes
Any way I could convince you to re-add the % clickers below the intensity dial?
My favorite mod was removed!
That is, unless it was moved and I didn’t spot it?
Well, the eom has a way to communicate its measurements. So this should make it possible.
But worth to note: the measuring is usualy not linear, because your body isnt. Between unaraused and decently araused it might not detect anything as your body isnt doing much. Only when you are getting close, your anus starts to react, which then is measured. And it usualy is a bit spikey (although, there are settings to mitigate this in the eom: clench detection).
So a side effect is that it cant realy do a slow build up that follows your arausal, the eom just handles this by always performing a slow ramp up. To which eventualy it reaches a high enough intensity. For some it can be 30s, and some it can be 120s. And during a session this can even change.
A machine/vibrator can easily perform things in a linear way. Which allows a linear build up, which works well for the eom. But if its going to also react to scripts. Slow/fast sections might get complete mismatches to what intensity is expected. After an edge in a fast section, it might therefor just perform very slowly the entire part,while during a slow section it might be faster.
But on that same note, maybe it doesnt have to. If the idea is to still follow the script action, then even if during a slow section it might not detect anything, just assuming a normal build up could still do its job well, as when a fast section starts and it starts detecting some contractions, it can very quickly adjust. Even if then slows down again, it might still feel more intense. Its not accurate to the action, but it might still feel that way.
1 thing the eom does good is detecting an actual edge, and giving a signal to stop any movement. Sure, it does require tweaking to avoid ruins (changing between vibrator or tremblr does already require a diffirent sensitivity, making the optimal treshold harder to find). But it is very consistent at detecting this, which will at least help if it can set the movement to 0 regardless of script.
But on that, i think scripting ranges isnt going to do what is desired. Because when you are truly close, an 80 unit move might still be far too much movement and force an orgasm.
I think that these ranges are good for most of the time, but near an edge, speeds should be hard capped. A 0-80 move might then only act for 10. And the action could then potentialy take 10 seconds before finaly reaching that 80.
Ranges will only help at low arausal to potentialy put just a little bit more feeling into some actions, putting you faster back into a high arausal state. But if the action is a full 0-100, when very close to the edge, you are still going to be needing to cap it to for example just 45-55, as more than that can always just force an orgasm. And for edging, forcing people over the edge is what you dont want.
(unless there is force orgasm button)
(and maybe a force ruin as well. which could be waiting a bit longer on the eom sensor going over the treshold configured by for example 1 seconds, or until the sensor is maxing out which nearly always is a real orgasm)
1 Like
@KingCobraKush I’m not sure about what your thinking, the % buttons are still here, in all mode, so… Am I missing something else ?
Heyhey Glavious,
the % controller I was talking about used to be just under the potentiometer dial. the special pattern names + % chance of hitting used to be listed beneath the dial, and were tap-able.
In your latest version, they don’t seem to appear anymore when using mobile - they show up under the display chart/graph with the bands and such, but in mobile it doesn’t seem to show up any more. the entire table is not visible, and with that, the tappables!
Using Firefox on Android, specifically.
I have a problem, lately my Handy is “stuttering” while using the Edgy. Its no longer smooth. The handy looks like not doing full movement and is “struggling” no idea why. The ranges are seted up correctly. firmware updated, no changes, it runs smoothly with Handyerse, Scriptplayer and sexlikereal.com. Any Idea ?
(sorry for my english)
@SomeoneRandom Interesting take of how the EOM works, thanks for sharing this.
The EOM can output its measurements so integration is definitely in the realm of possibility. Would be a great combo: The Edgy handles the behavior/pattern side, EOM handles the actual edge detection for real hands-free sessions. No promises on timeline but it’s noted. Though, the binary part is something to think about, I don’t know if going back to 0 then increase to 100 automatically is the right way.
@KingCobraKush Indeed, I forgot to mention that you have to set a preset as favorit to see them across the knob. Variations chips are missing on mobile, I will take a look soon.
@etronsupreme I’ve just been using the app this morning and didn’t notice any stuttering. The 1.4.2 is out but no changes to the engine. Try a hard refresh of the app with Ctrl+Shift+R on Windows and tell me if it fixes your issue. Tell me more about your connection (did you use Handy key? Intiface?) and your device? The Handy 1 or 2?
I will try soon. I m with handy 1 and handy key