Iām mainly using vibrating toys and added support for stroke to vibration transformation and some other features (including min/max power/length) in the fork I created.
Let me know what you think about those features, If you like it let me know and I will do a PR or you can take the parts you like.
Glad when I found this web app but when I tried to get this working on an iPhone 11 with IOS 15.5 (for a Lovense vibrating toy) it stops when the device is connected in WebBLE. Error message below, any ideas on the cause or more important, the cure? The toy stays connected based on the LED status but is not responsive to the script.
Damn. Do you have a non-iOS device to try this on? Say a computer or the likes? If so, do try that, would rule out your iPhone. Unfortunately, it is difficult to troubleshoot this. If you are a developer, best bet would be to clone the project, update the buttplug library from 1.0.10 to 1.0.17. Thereās also one thing youāll need to do to get it to work but I will tell you if you are interested in going down this path, developer experience preferred. I would deploy with the upgrades the library but it fails to compile, been tied up for a while, I did mention it in discord but as of yet no update on this. The later versions support a wider array of devices, among other things.
Tried on PC Win11. Toy (Gush) is discovered and connected but do not react on script so it seems to be a toy issue. Have some other Lovense toys, will test with those as well to see if the issue is there. Other apps on PC do find the toy and interact correct, shibbydex haptic files as an example of other web based apps.
Computer geek but not developer, loooong time since I last wrote code in C so donāt think that I should go down in that rabbit hole unless I have to ā¦
Edge 2 on PC work OK, connect and vibrate. Gush connect but donāt vibrate.
Edge 2 on iPhone connect but donāt vibrate. WebBLE do only give a single word āERRORā messages but no further text. Gush connects with the error message in above post and donāt vibrate.
LED status in all cases show that the toys are connected and they can not connect to other applications either before released from the Web Funscript Player.
All toys and scripts work as expected via Intiface Desktop and ScriptPlayer.
So, seems that I need to wait until new versions are released that have better support for Lovense toys. Let me know if I can help testing if needed.
Updating the values on seek explains why that can sometimes fix or improve playback. Iāve found it helpful to routinely seek back to the start a few seconds after each video starts, it seems to work better that way than if I just leave it running.
On the timing, usually script actions will aim to be timed to the nearest frame, with frames being at 16.7ms intervals in a 60 fps video and 33ms intervals in a 30 fps video. If the app is checking and playing moves as soon as it comes within 50ms of the timing of them, that goes some way to explain why the timing sometimes seems to work reasonably (the points were probably near some multiple of 50ms apart to start with) and why it sometimes feels a bit randomly off. Doesnāt explain why if left to itās own devices it has a more like 250 or even 500 plus delay to it, but seeking at least once after the start does seem to fix that.
Have you considered changing the timing interval to 33 or maybe 17 ms increments for now to see if that improves the accuracy? It wouldnāt be the same as a system that just runs everything at the scripted time, but it might close the gaps a bit with the timings system as is.
I like this. Iāll add an number input box that can be adjusted and automatically takes effect. The value will be this āpollingā variable in question, currently set to check every 50ms. Itāll be persisted in local storage so you donāt lose it when refreshing the page.
I havenāt had much time towards this site in recent times. When I do spend time on this, Iām open to exploring a webVR player, albeit there are a couple of other things that I also wanted to do.
Okay, Iām working on a new release that should hopefully be released sometime soon.
Hereās what to expect;
Reduced the current checking of funscript events from 50ms to 15ms (@Novice).
Introduce Handy SDK for users with The Handy. This should be the preferred choice for users with The Handy as sending the funscript directly to the device reduces latency, a currently known issue with the not perfect current algorithm the site uses.
Introduce vibrate invert feature for vibration devices (@Testinout4u)
Upgrade Buttplug SDK from 1.0.10 to 1.0.17 (@tm6).
Hey chaps, sorry for the silence recently. Itās still on my mind to improve this site but Iām working on a couple other things at the moment, this hasnāt gotten priority in recent times. I hope I can get around and push improvements in the near future.
Thanks so much for everything youāre doing @amango134 !!
I had noticed that delay too @Novice , in addition to the occasional lost unsynced points of action (which sounded like @amango134 's upcoming update would help mitigate with the interval shortening), there does seem to be an overall significant delay sometimes, what would cause that/how would that be fixable?
Hey everyone, Iām doing other things these days. I havenāt worked on this project in a while, just want to state in writing that the site will no longer be worked on. The GitHub can be forked and worked on. Itās currently hosted on Vercel for free so will be left as-is for the near future most probably.
I do recommend the Handy users to checkout the HandyVerse app on their devices, itās an interesting development that may replace the need for this site. Hope more actively developed projects from others can fulfil the requirements yāall have.
Thanks again everyone, was nice chatting with yāall and working on this project! Am planning on anonymising this account in the coming days so will no longer be able to reply when that happens.