Milovana.com

Will this software be able to encode the vids the way that fleshlight does with ones on their site?

This way CH creators can just create custom vids that take into account the launch speed limitations. Like I don't need anything automated or easy just a way to tell launch when and how to stroke throughout the video.

Thanks

pl3b wrote: ↑Tue Jun 20, 2017 7:21 pm As for the beats being too quick - yeah I've seen that the Launch may be too slow for some CHs. How about making it so that quick sections (and maybe after detecting how quick the overall video is on average) are beat=up, beat=down? And if that's still too slow, making the movement shorter so that we try to match the beat?

That's exactly what I'm doing

Some beatbars just go crazy and some random "stroke as fast as you can" text appears - which isn't helping.
The problem with the Launch is not the maximum speed itself - in manual mode it can go quite fast, the problem ist that it can't handle too many commands (The Launch only takes very simple commands: Go to position [0..99] at speed [0..99]) within a short period of time. 200ms works great, 150ms is borderline and anything below that makes it stutter around weirdly or skip commands.

That might sound bad, but properly encoded / limited videos are awesome, so don't worry about that

WatchItDry wrote: ↑Tue Jun 20, 2017 7:26 pm Will this software be able to encode the vids the way that fleshlight does with ones on their site?

If you mean the ones from Feel Me (If there are others, please tell me I can't find any content anywhere else), then yes - but without the app, webservice and all that - direct communication via Bluetooth to reduce lag (and overhead).

WatchItDry wrote: ↑Tue Jun 20, 2017 7:26 pm This way CH creators can just create custom vids that take into account the launch speed limitations. Like I don't need anything automated or easy just a way to tell launch when and how to stroke throughout the video.

There is a Blender plugin by Funjack but I don't think it's public yet. I plan on recreating something similar in my editor. The mechanics behind it will basically be a keyframe based curve that sets the position - speed will be calculated automatically. In case you are not familiar with all that technical stuff: You basically tell the program the position of the Launch at certain positions in the video (e.g. highest and lowest point during fucking/blowjobs/handjobs) and the software does the rest.

If everything goeas as planned the software will have the following modes:

• Single Beat based - e.g. extract them from a beatbar or set them manually (if you have too much spare time)
• Pattern based - queue up a couple of patterns like for a regular cockhero (Normal, 3-1-1, Doublespeed, etc.)
• Keyframe based - manually set the position of the launch based on the "position" of whatever bodypart is being fucked.

Since we all do this in our free time, it will take a while to get everything to be usable by "regular" users (and by that I mean people who don't want to clone our repos and compile the software themselves), but I believe that with open software and an active community the content that will be created will be amazing sooner or later

Oh, I wasn't aware that there was a limitation in how quickly Launch can accept commands, although about 5x per second sounds like it may be enough. Wondering how quickly you could really go if we were to write our own Firmware for it.

pl3b wrote: ↑Tue Jun 20, 2017 8:36 pm Oh, I wasn't aware that there was a limitation in how quickly Launch can accept commands, although about 5x per second sounds like it may be enough. Wondering how quickly you could really go if we were to write our own Firmware for it.

I think sending parametric commands to the device, versus single position/speed commands, could make a big difference. RealTouch did this and it worked well. The problem is mostly dealing with the timing to BLE messages to/from the device.

I /think/ writing our own firmware is an option, though right now we have yet to extract the bootloader, so I'm not sure if there's any sort of signing or anything happening. The firmware itself was just an intel hex file that encoded straight to PIC assembly though. Unfortunately I'm not fluent in PIC, so if someone else around here is, please let me know. Would love to get started on annotations. :)

pl3b wrote: ↑Tue Jun 20, 2017 8:36 pm although about 5x per second sounds like it may be enough.

Oh it is, especially if it goes on for a while and if the content is ... stimulating

@WatchItDry
By the way, what engine are you using for Decadence Island? If it's nothing too exotic or limited (supports some kind of networking or IPC) I could totally see Launch support happening

Aaaand I just realized I haven't tought of this before, but adding Launch support to the Webteases would be cool too . Does anyone know if the admin(s) are alive again and could make that happen?

Liquid wrote: ↑Tue Jun 20, 2017 8:46 pm @WatchItDry
By the way, what engine are you using for Decadence Island? If it's nothing too exotic or limited (supports some kind of networking or IPC) I could totally see Launch support happening

I use RPG Maker so nothing fancy. But I really would like to see an app to encode movies first tho. You know just something I can like open up, import movie, and set different strokes at precise keyframes. Like long and fast strokes or long and slow stuff like that. Something like this would be useful since we could encode CH's but also any other movie as well.

Also trying to make it work with a beat meter or audio beat is kind of a wasted effort. Like a beat meter and a beat sound were used as a way to instruct player when to stroke. But the launch is automated so those will no longer be necessary. And will only make it harder to sync. And the thing with CH's is if they are just a fraction of a second off it ruins the whole experience.

A PIC? Really? Which chipset model? Execution speed may be the cause of the scattered behavior, time to read the command vs time to activate the motor. Maybe if the communication was slightly changed to increase buffered commands, perhaps that the extreme beat changes could be better handled in the firmware.

doremi wrote: ↑Wed Jun 21, 2017 6:05 am A PIC? Really? Which chipset model? Execution speed may be the cause of the scattered behavior, time to read the command vs time to activate the motor. Maybe if the communication was slightly changed to increase buffered commands, perhaps that the extreme beat changes could be better handled in the firmware.

Yeah it's a PIC24FJ64. Check out this repo: https://github.com/metafetish/raunch-firmware

Honestly if I had it myself, I'd probably be willing to work on the firmware (I do that for a living). Doing cool stuff to get cool stuff :)

Yup, that's my repo. :D

Datasheets for the chips I ID'd are here:

https://buttplug.io/hardware/fleshlight-launch/

I believe there are exposed pads on the board too. See J3 in the image I've attached, from my Fleshlight Launch teardown video (https://www.youtube.com/watch?v=sA7MdO0rEoo). I haven't had a chance to try anything with it though.

This may indeed be a an unpopulated debugger connector. I haven't worked with PICs specifically, so I can't tell whether this is something standard for those, but it looks very likely. Easiest thing would be to measure if those pads connect to the MCU pins (and if so - which ones). If they do indeed connect, it's almost certain that those are used for debugging. At that point it'll be as simple as checking the MCU datasheet and creating your own connector to attach it to the debugger.

Thanks guys! This is very interesting! Time flies because what I worked with was an 8-bit PIC. Back then, we had to cut corners because the fw space was so limited. I'd love to help out, but I have too many on-going projects... The device simulation (of the actual stimulation device) could be done using a $60 Microchip development board and a cellular phone mini vibration motor. Certainly not stimulating physically, but very much so intellectually.

Looking forward to the Arduino adaptations ...

Version 1.0.0 of the ScriptPlayer is now (pre-)released:

https://github.com/FredTungsten/ScriptPlayer/releases

A couple of .FunScripts can be found here:

https://github.com/FredTungsten/ScriptP ... er/Scripts

Requires Windows 10 Creators Update, .Net Framework 4.6.2 and a Fleshlight Launch.