fixed in preview version
Hi, does the app have a safety “quiet mode” meaning that when that modality is ON, the handy never make the loudest noise that could be heard by other people outside the room?
When I go to select the video/funscript, it does not show the funscript files that I have in the folder. Is that a format issue with my scripts or potentially another issue on my end?
Edit: It helps if you have “All File Types” selected when you are trying to load the video and script files lol.
I’m tryin to connect the bluetooth but keep gettting “connection error”. It worked before so I dunno what changed.
Nevermind. apparently that happens when it doesn’t see any devices.
“stroke range” doesn’t seem to affect the limits for the vibe. is that possible to fix/add?
Would be great to have two different funscripts running for two seperate devices. One funscript to The Handy and the second funscript to an Intiface device.
Also a no video option, so just playing a script without the need for a video.
Thank you so much for the Vibrator support!
So far it seems to work pretty well for me. No interuptions or lost connections (Lovense Domi 2, windows 11, connected by a asus bluetooth stick, intiface version 3.0.4+40).
The translation of stroking script to vibrator seems to be a bit on/off, not allowing for much variation (medium paced strokes cause pretty much full speed vibration). And dedicated vibrator scripts (where usually position = vibration speed) can’t be used. Maybe there could be an option to switch between different ways of interpreting a script. But if you are going for a simpler interface fit for mobile, this might just be to much. There are so many options that COULD be implemented, i cant imagine it is possible to keep it simple/intuitive.
My first session was over much faster, than i wanted it to be, because edging with the domi is quite difficult for me. But there are already so many options to play around with, i am sure i will have a lot of fun with this project!
Edit: Oooohhhh! I did not see the “Neutral ARR” setting, it works even better, than i thought! (disregard the part about the conversion from stroking script to vibration earlier)
Thank you! I will check this out!
Wingman was a little disappointing and it lost connection a lot.
The handy phone app is really nice, but I their website doesn’t have the same controls.
Will let you know how I find it! :)
I gave the audio only feature a try in preview. First of all, I appreciate that WAVs can used as well as other formats. I happened to have something in a WAV format that I wanted to try …
I tried it on the phone. The experience was a little rough. When choosing audio, the same controls don’t show up as for video – at least not on the phone – and one of the ones that doesn’t show up is pretty important — the one that lets you toggle between funscript and behavior. Wiithout that control, I was able to get the funscript playing, but I had to first load a video, flip it to funscript, and then load the audio + funcscript file.
I also noticed that on the phone, the option to change the files goes away after a video is loaded. I had to drop the video and funscript (with the X that resets that box) before I could make different choices.
I also ended up trying to run just the funscript. I had a file that would only play when I ran it with VLC player, so I tried to run the action from my phone while watching the video on a different device. If you choose only the funscript file, it doesn’t change the box at all. This might be as intended. But in case there’s flexibility for this, I thought I’d mention that I did have a use-case. For some reason, the video wouldn’t even run on Handy’s player – just VLC player.
I tried to use the left/right controls on the handy device to change the arousal meter while watching a video, and it doesn’t seem to work. I’m going to try it while playing audio. It might work because I can just put the audio on and give the meter full focus.
+1 on support for the Edge-o-matic 3000. It would be awesome to fully automate everything.
Ideally it would be an external app that acts as the opposite of Intiface.
Multiple types of generic Bluetooth devices as input sources.
These would measure your stress/arousal through heart rate, skin conductivity and temperature.
I’ve intentionally omitted anal clenches and breathing rate as these could be manually controlled and muddy the data.
It would run for about a minute to get your baseline after which you would edge yourself once. (This could be saved in a .txt document so you can skip this step later)
This would give both an upper and lower bound for what your three values are as well as a curve of you approaching them over time.
It could then output up, down, left, right keyboard strokes to tell The Edgy to increase / decrease your stroke speed.
As your three curves approach the top it would stop again, wait an arbitrary amount of time to let it naturally drop then start up again.
(Maybe those three curves could be fed into a neural network NOT a LLM so you would get one clean “arousal meter” instead. Each time it successfully edges you would count as “correct” data and whenever you override it by telling it you’re coming would be “incorrect data”. Ideally it would learn YOUR personal preferences, though refining a neural network on your own is computationally expensive so that part might be too lofty.)
I don’t think you would even need to make it a websocket server if the outputs are just keyboard strokes so you don’t have to worry about web security either.
can we add subtitle(srt file) support?
Hi there, some replies in one shot, hope I’m not missing anything ^^
@SeraSeraSera @Umbra250, vibration is derived from the stroke motion for now, so it comes out “binary” and there’s no separate vibration range. I’m reworking behaviors so vibration becomes its own channel, which means real variation, its own intensity settings, and support for dedicated vibration scripts (position = intensity) instead of reinterpreting a stroke script. No ETA but it’s the main focus so far. (@SeraSeraSera glad Neutral ARR clicked for you.)
@hamps87 independent scripts per device is part of that same work of vibration and multi channels, each device will gets its own channel instead of mirroring the Handy. Full no-video / script-only mode isn’t there yet but it should not be complicated to add. Audio-only already works in the meantime if you want a script without video (still have some issues reported by @atxhazen that I’m working on).
@atxahzen thanks for stress-testing audio-only. The mobile gaps are real (like always on the app), the audio path on mobile needs work and I’ll dig in.
For the left/right buttons during video: can’t reproduce it here, works well from my testing with all buttons. Which Handy (1 or 2) and firmware version, how are you connected (connection key / mode), (can’t find in the thread if you already mentioned it )? I’m not convinced that the issue,but who know.
@HentaiHorse hope it works better than Wingman for you, let me know how the connection holds up.
@Benjaminbarker glad you sorted the file picker. It should default to showing .funscript like file and video formats, maybe it’s to permissive.
@becot your sketch lines up with a generic input layer I’ve thought about. It’s longer term though, I want the core device and behavior engine solid first before digging into a fully automated edging setup, but that’s a dream ^^.
@hue04476.test1 subtitles aren’t planned right now, but noted, should not be that hard implement.
Hey! Are multi-axis devices such as OSR2 anywhere on the horizon as a feature ? Its the only thing missing for me in this amazing app. Using my multi-axis device as single only kind of sucks
But i love the other features that no other player has…
Hey, I’m still using this almost daily lol
I’ve found some minor bug related to my “misuse” of the Device Profile picker. When I just want reduce the intensity (speed), I select Custom from there and change the Max Speed value - eg to 201 (it will not accept 200 ;). This is not reflected instantly but needs other changes to take effect, eg. changing the stroke length shortly. There’s probably a incorrectly wired onchange or so.
Another issue for me is that i relatively often lose the connection - the handy just stops. Maybe thats related to my wifi, but I’ve not encountered that somewhere else before? Perhaps the app can try to reconnect automatically? But I’m unsure it even knows its disconnected because it just continues with the pattern changes etc. This can often only be resolved by reconnecting manually.
My last thing relates to my Device Profile use - would this be something other people would find useful in an additional controller component, similar to the addition of the stroke length; a manual speed slider from 0 to 100% or so?
Great project and especially a wonderful work regarding the editor mode!