It seems to be a great thing for upcoming SexLikeReal peer to peer sex toy connectivity or live cam girls sex toy shows.

Got some interesting follow up:

This is a nice idea - basically the presets feature of the Random Stroker app on handyfeeling, but you can control the preset selection with MIDI buttons, and the speed/stroke-range with MIDI sliders/dials. Could easily be broadcast to a multicontrol session.

For scripting, I suppose a linear MIDI slider (like a crossfader on a MIDI mixer unit) oriented vertically would be a pretty nice way to script in realtime (or half speed or whatever).

It makes me wish that the Handy team had added that ‘pattern’ mode where the script contains little loopable patterns that can be switched between. I always wanted to make a kind of dynamic cock-hero type app that used such a feature to switch between common cock hero patterns :stuck_out_tongue:

https://m.media-amazon.com/images/I/71sV-3t5mPL.jpg

doublevr I would say we don't need a new format if we use MIDI for scripting as it can be actually embedded into MP4 file as a separate audio track.

    Few thoughts on the topic.

    We need to come up with specification of how MIDI data translates into haptic signals/messages and make it universal and flexible (which can still be tricky).
    Main points of interest:

    • MIDI format is binary, can be embedded into MP4 as an audio track
    • Lots of MIDI devices on the market and software for editing/viewing MIDI data (just google "midi controller")
    • We can utilize hardware MIDI controllers for "control my sex toy" project
    • MIDI can simultaneously control up to 16 different devices (for example: sex toy + gloves + body suit)
    • Recording MIDI data is easy with existing DAW software (like Reaper, Ableton Live, Studio One, etc). It is focused on audio mainly, so video preview is limited but possible
    • We can support both JSON and MIDI formats, create a converter tool

    Limitations:

    • 16 channels (e.g. 16 different devices per script)
    • 31 message types with 14-bit precision (values from 0 to 16383), most of the data has 7-bit precision (value from 0 to 127).
      • 7-bit value maps to the 0-1 range with 0.01 precision
      • 14-bit value maps to the 0-1 range with 0.0001 precision
    • Not really flexible format but usable (it was introduced in 80s)

    There is room for discussion and priorities, but this idea has a great potential in my opinion in terms of "standardization" and usage of existing tech instead of reinventing the wheel.
    We could start with "control my sex toy" and then apply this approach universally.

    We need to come up with specification of how MIDI data translates into haptic signals/messages and make it universal and flexible (which can still be tricky).

    MIDI also has a concept of "voices" or different instruments, you can assign different voice per channel so maybe we would just need a voice font for each device?

    Those aren't embedded in the MIDI file though, they are generally stored on the instrument. Each device would need to know which channel it's 'playing'

    Channel/voice names could just be a UUID generated by the manufacturer, if there are enough bits to store a UUID. That would eliminate the need for anyone to keep a 'list' of which devices are using which ids.

      So from the haptic device point of view it's "I'm sending you this midi file and you should 'play' the channel(s) that match your manufacturer's UUID(s)"

      I really love the direction this discussion is going:-)
      Midi is a really good idea.
      It might circumvent the problem of the audio channel of the video already uses the sound card so that the audio that could be used for electro stimulation can come from the Midi device.

      ethicalperv I see your idea, yeah. It's not necessarily though to hardcode it this way and put additional limitation for manufacturers. They shouldn't care about channels and UUIDs, it can easily be configurable

        3 months later