I’m trying to use EDI with restim, and the results are very inconsistent. Because the more bespoke outputs don’t apply, to restim, it gets daisychained from EDI to Intiface to restim, being converted into TCode in the middle. Which I would think would be fine, but it unfortunately doesn’t work well in practice. Loops play perfectly the first time, then are choppy with no interpolation. Sometimes they fix themselves, but the experience is less than ideal.
example of choppy EDI → Intiface → restim output
I’m assuming there isn’t a solution for this.
My idea for one would be to output funscripts over WebSocket just like how MFP does. For restim users, this would be ideal because it would enable all of restim’s unique funscript types (volume, pulse width, etc.). I bring up MFP because it worked wonderfully playing funscripts into restim over WebSocket in the past. This sidesteps TCode altogether, letting EDI time the funscripts, and restim or any other end program interpret them. (for restim technically tcode works as well but it’s potentially error prone whereas labeled funscripts are more obvious)
Edit: the above is wrong, MFP outputs TCode over WebSocket, I just completely misremembered and didn’t double check.
don’t really think the below makes sense but i’ll leave it
Given the current UI, I think the best way to do this would be to allow users to create a websocket device. That device would show up in the window with the rest, so scripts can be chosen, etc.
No idea how feasible this is or if it even makes sense to pursue