I'm new fan of estim and I'm also trying to work on my own estim weabtease. There are some great creations on this site. But unfortunately the device I have doesn't support different frequencies. It is probably controlled only by volume level. Because of that some signals are processed wrongly and sometimes realism of the game is ruined .
In my webtease I would of course like to avoid that problem. And I'm thinking about using literally one frequency for all signals. I event wrote small program to generate such signals to be sure that there is no "noise":
frq.jpg (31.79 KiB) Viewed 3199 times
1. I'm wondering if such approach would be acceptable for users who have devices which does reflect frequencies properly?
2. If yes, then which frequency to use to please both groups ?
Be specific because this might help with more info on how to best control amplitude too. For example, the 2B has a delay in volume increases to 'smooth unexpected spikes and prevent pain, the Coyote only can handle an update through the Bluetooth API to an accuracy of about 5 times per second(at least when fed with xtoys.app which is the only thing that makes a reasonable audio interpretation for the device), so ramps with that device generally need to be slow to not 'get lost'. Not sure if you are using a Sensavox/Axis or Abox type device?
DIY Stereostim(and BTStim) devices duplicate the frequency identically and 600hz is the sweet spot between not feeling stingy when having a slightly loose or not ideally lubricated electrode from a lower frequency and not putting too much power in from being desensitized by a frequency above 1000hz. I've stimmed comfortably between 300-2500hz and there's some wiggle room. The ET312B will extrapolate to a lower pulse frequency and 600hz puts it on the edge of one of the step downs and I've seen recommendations of 555hz to keep it towards the 'top of the range. ..so 555hz is probably a great choice. I don't think it matters too much for a 2B, but I think owners could chime in, I know there are teases that drop super low for some files making it painful for DIY Stereostim devices and ET312B and it doesn't seem to cause issues on the 2B to use a wide range of frequency.
I think you can't reliably make a tease for devices you do not own. What you could do is ask authors of existing files which are known to work with certain devices for files/permission to reuse them, i.e. Estim Hack and Estim Chatroom have files for several different device types. I am not sure if some of devices (i.e. 2B and ET312) are sharing (some) files, it is possible.
That would require your tease to have settings and choose group of files that are used.
Maybe @rillo or other authors who developed such teases see this thread and drop a message.
Electro wrote: Wed Sep 21, 2022 3:14 am
Be specific because this might help with more info on how to best control amplitude too. For example, the 2B has a delay in volume increases to 'smooth unexpected spikes and prevent pain, the Coyote only can handle an update through the Bluetooth API to an accuracy of about 5 times per second(at least when fed with xtoys.app which is the only thing that makes a reasonable audio interpretation for the device), so ramps with that device generally need to be slow to not 'get lost'. Not sure if you are using a Sensavox/Axis or Abox type device?
...
Thanks. Yeah, 5 times per second that's not to much. But if you use much higher volume, then it still should be intense/painful, right? I use Axis. I checked that 50ms spikes are still happening. Shorter ones sometimes disappear or have lowered volume.
So I think good idea would be generating files with different length of spikes and then allowing user to choose during calibration. Would be good to know what is the exact limitation of 2B, because it seems to be quite popular.
edger477 wrote: Wed Sep 21, 2022 9:59 am
I think you can't reliably make a tease for devices you do not own. What you could do is ask authors of existing files which are known to work with certain devices for files/permission to reuse them, i.e. Estim Hack and Estim Chatroom have files for several different device types. I am not sure if some of devices (i.e. 2B and ET312) are sharing (some) files, it is possible.
That would require your tease to have settings and choose group of files that are used.
Maybe @rillo or other authors who developed such teases see this thread and drop a message.
Yeah, it seems that many versions of files are unavoidable :).
verynicekojak wrote: Thu Sep 22, 2022 10:58 pm
Would be good to know what is the exact limitation of 2B, because it seems to be quite popular.
What limitation you have in mind? I have 2B and I think its processing has a delay but it is very hard to tell number of updates per second - which is not even important. If you want me to check something I could, i.e. if you want me to try 50us or 100us pulse or something... but I think for 2B it does not make sense to use pulses. If you need to create painful section, just make sure that all normal signal is quieter than pain section, and have "device calibration" before signal calibration.
2B has something like vu-meter for input so you can set the volume of input to be close to max (when you play device calibration signal that would be as loud as pain section), then you play calibration which is 20-30% quieter - user sets output levels on 2b here so it feels fine and it will same with normal signals that have same volume as calibration. Thanks to proper calibration you are able to play louder sections and that is it.
edger477 wrote: Fri Sep 23, 2022 10:20 am
What limitation you have in mind? I have 2B and I think its processing has a delay but it is very hard to tell number of updates per second - which is not even important. If you want me to check something I could, i.e. if you want me to try 50us or 100us pulse or something... but I think for 2B it does not make sense to use pulses. If you need to create painful section, just make sure that all normal signal is quieter than pain section, and have "device calibration" before signal calibration.
2B has something like vu-meter for input so you can set the volume of input to be close to max (when you play device calibration signal that would be as loud as pain section), then you play calibration which is 20-30% quieter - user sets output levels on 2b here so it feels fine and it will same with normal signals that have same volume as calibration. Thanks to proper calibration you are able to play louder sections and that is it.
Yes, that's all clear. I have Electrastim Axis and it seems that it works in a similar way. By limitation I meant: what is the shortest pulse that is reproduced at specified volume. 50us? Is that microseconds? For Axis minimum is I think 50 milliseconds and if you play something shorter, it disappears completely or the volume level is lowered (by some sampling and averaging mechanism probably).
I would need to set up oscilloscope to answer that, but until then, I am pretty sure that no pulse is specified at max volume, the processing is always averaging several samples, so it takes probably 100-200ms to reach the full volume.
.
?
