Restim: e-stim audio generation software

[diglet]

I'm still trying to properly calibrate my setup using the circle on Restim (common head, left below balls with pad, right with anal plug), can't seem to adjust it to my liking cuz I don't really fully understand how it works, I just follow GitHub's default setting in the wiki. And a lot of times when it's trying to just stimulate the head, I find the signal very choppy and stingy for some reason, and not sure how to fix that.

The easiest way is to use the circle pattern, relatively slow speed, and keep clicking the calibration diagram in the location where you feel the least sensation. (opposite to the point where you feel most sensation).

Some electrodes are easier to calibrate than others, I find is especially difficult with internal electrodes.

If the signal is too choppy you can try increasing the pulse frequency.

[lotionBob]

my first FOC board crapped out on me, so I bought two more to try edgars double box set-up, but now I cant get even a single box to work. Instead of

Successfully opened: COMX
pulse generation started

or whatever it usually says I just get

Successfully opened: COMX

Literally the only thing that changed is the COM number from being a new device, same problem with the second box.

Any ideas where to begin trouble shooting?

Like if I unplug the box I dont even get a low voltage error, wtf is going on?

Oh, and I made sure to update the firmware before hand

[diglet]

You might be the first person here to kill a board.

Do you get any output from the board if you click 'upload and monitor' in VS Code? Close restim to make sure it's not using the serial port.

Are you are compiling for disco_b_g431b_esc1, and not nucleo_g474re (This is a different board, I added this yesterday).

Have you updated the ST-link firmware with STM32CubeProg?

If all else fails you can try to poke around with the debugger in VS Code, it might give us a hint on the cause.

[lotionBob]

Do you get any output from the board if you click 'upload and monitor' in VS Code? Close restim to make sure it's not using the serial port.

Thank you for the response diglet, turns out I was just tired and dumb and didn't build to the boards properly.

You might be the first person here to kill a board.

The first board that died was from a short I suspect, I was still using a macgyvered box. It stopped working one session and after a power cycle it would only flood restim with init failures


Sorry for the trouble, and thank you for your amazing work

[darthjj]

Small feature request: Don't make changes to volume/calibration active unless enter is pressed. I think calibration is like this too, but I didn't test with latest version. Anyhow yesterday when I was running the FOC-stim, I was reminded that volume changes apply instantly when a number is entered into the box rather than on submit. With positive numbers this isn't a huge deal, but if one is changing a negative number it will jump up in intensity if you backspace any digits.

[edger477]

Small feature request: Don't make changes to volume/calibration active unless enter is pressed. I think calibration is like this too, but I didn't test with latest version. Anyhow yesterday when I was running the FOC-stim, I was reminded that volume changes apply instantly when a number is entered into the box rather than on submit. With positive numbers this isn't a huge deal, but if one is changing a negative number it will jump up in intensity if you backspace any digits.

Should just disable typing instead. That way you can never cause sudden change, as you can only scroll with mousewheel or use up/down. And most people use wheel so don't need keyboard, having to press enter would break that workflow

[diglet]

I see your point but I'm not a big fan of using native controls and then adjusting them such that they *look* like native controls but behave different in subtle ways. It's a recipe for user confusion.

I agree the current behavior can be problematic, that should be solved by redesigning the entire control with non-native look&feel, but that's very hard.

[darthjj]

Should just disable typing instead. That way you can never cause sudden change, as you can only scroll with mousewheel or use up/down. And most people use wheel so don't need keyboard, having to press enter would break that workflow

I almost exclusively use typing :/ buttons are good when fine-tuning a value, but annoying when you want to make a bigger change. Would take forever to go between 10% and 100% volume for example. I guess it's less of an issue if you always use a FOC-stim since it's current-driven, but when using stereostim I sometimes have to change values more when with different electrodes, and even more when switching between the two devices.

[darthjj]

I see your point but I'm not a big fan of using native controls and then adjusting them such that they *look* like native controls but behave different in subtle ways. It's a recipe for user confusion.

I agree the current behavior can be problematic, that should be solved by redesigning the entire control with non-native look&feel, but that's very hard.

Had to search a little, but it seems you can achieve it with

Code: Select all

self.doubleSpinBox_volume.setKeyboardTracking(False)

[diglet]

Moving from 0% to 100% is quite fast with pgup/pgdn, it goes at 10x the speed of the arrow keys. But unfortunately there's a trend of not including these keys on newer keyboards

I did not know the KeyboardTracking thing. I just tested it and it works, I disabled KeyboardTracking on all controls that have a direct effect on signal generation. It will be included in the next release.

[darthjj]

I have a DIY keyboard and I didn't include PgUp/Down because they become quite redundant when you have Vim bindings in most text viewers/editors :)

[darthjj]

Thought it would be better to continue the discussion about volume conversion between funscript for stereostim and for foc-stim here..

I haven't been able to do any side-by-side testing, or measure currents on stereostim, but I do have tables for which percentages correlate with different subjective intensity levels.

Stereostim:
60% barely noticeable
70% tease
80% nice
90% a little intense
100% very intense

FOC-stim:
30% barely noticeable
55% tease
75% nice
85% a little intense
100% very intense

Are others getting similar numbers, or does it vary from person to person?

[edger477]

Thought it would be better to continue the discussion about volume conversion between funscript for stereostim and for foc-stim here..

I haven't been able to do any side-by-side testing, or measure currents on stereostim, but I do have tables for which percentages correlate with different subjective intensity levels.

Stereostim:
60% barely noticeable
70% tease
80% nice
90% a little intense
100% very intense

FOC-stim:
30% barely noticeable
55% tease
75% nice
85% a little intense
100% very intense

Are others getting similar numbers, or does it vary from person to person?

This corresponds roughly with values I use for my scripts but of course that depends on how long you have been stimming. It makes it easy to play foc-stim scripts on stereostim by simply setting minimum for volume axis to 40% (range 0.4-1)

Yes it is not linear mapping but this is not quantum physics, approximation is fine.

[Electro]

This corresponds roughly with values I use for my scripts but of course that depends on how long you have been stimming. It makes it easy to play foc-stim scripts on stereostim by simply setting minimum for volume axis to 40% (range 0.4-1)

Yes it is not linear mapping but this is not quantum physics, approximation is fine.

This is roughly where I've set things, usually 30% if I want the climb in intensity to be bigger, 40% if I otherwise feel like I might be surprised. I usually take notes from there while playing the video+script and go back and modify the other scripts based on those notes. I'm nearly done making adjustments that make CH Overtone feel ideal for me, but I won't release the changes until I've had a few good runs where it feels like there isn't anything I'd want different. Some files are different than others, for example with Overtone, I'm usually setting the bottom limit at 30%(I'm doing this in MultiFunPlayers limit sliders) at the start, but there's a few changes but it's mostly changing to 35% and then back to 0% in the last 10-15 mins to give a larger range for a 'teasey' ending that allows some nerve relaxation to give the cum push at the end a chance, but it also seems to end short and I'll probably add to that ending so it doesn't end sooner than expected.

[bobsynol]

Hello, is there a tutorial how to make funscripts from scratch especially for restim?