Restim: e-stim audio generation software

[darthjj]

I just did an experiment with Restim which might have some potential.. I duplicated alpha and beta, then using the three phase pulse based algorithm I alternate between using alpha/beta and alpha2/beta2 when generating each pulse. Using audio based device btw. It makes the stroking feeling a little bit less defined when playing two signals at the same time, but you can feel both of them. Haven't got any funscripts to really test it, but just playing two circles at different speeds is quite interesting. Normal funscript to stim usually feels nice, but for some videos with deep penetration I feel like I'm missing intensity on the tip if there is a lot of action in the bottom range of the alpha axis. I was thinking I'd like to use the additional channel to add intensity to the common to simulate deep penetration in these cases. It's not something I imagine would be used all the time, more for a few special cases to "fine tune" the feeling.



Uploaded the fork in case anyone wants to try it. Didn't bother duping volume for the second channel since it's just a POC. https://github.com/darthjj420/restim

[yetatu]

no idea what you guys are talking about. Any pictures to help tell the story of what actually needs to be done here to get this to run on a mac?

Hello everyone! I will try to describe in detail how I launched Restim 1.30 on my computer MacBook Air (13-inch, 2017), Intel Core i5, macOS Monterey 12.7.5

1. Download and install Python https://www.python.org/downloads/release/python-3130
2. Download the source code zip archive «Source code (zip)» or «Source code (tar.gz)» from github https://github.com/diglet48/restim/releases
3. Unzip the file «restim-1.30.zip» or «restim-1.30.tar.gz»

4. If Restim is run from source code for the first time:
4.1. On the unzipped folder «restim-1.30» right-click and select «Services > New Terminal at Folder»
4.2. Insert the following code into the terminal:

Code: Select all

python3 -m pip install -r requirements.txt
python3 restim.py

4.3. Press Enter
4.4. We'll wait until it's installed
4.5. Python will start, then Restim

Updated! Thanks for the advice to user darthjj > Post
5. To run Restim next time:
5.1. Select the file «restim.py» in the Restim folder, right-click and then «Open With > Python Launcher.app».
5.2. Python will start, then Restim

5. To run Restim from source code next time:
5.1. On the unzipped folder «restim-1.30» right-click and select «Services > New Terminal at Folder»
5.2. In the unzipped folder «restim-1.30», open the file «run.sh», copy all the contents and paste into the terminal
5.3. Press Enter
5.4. Python will start, then Restim

6. «restim-master.zip» – Restim source code updated. In this version the script «run.sh» has been changed viewtopic.php?p=372941#p372941
Now Restim starts like this:
6.1. Download the source code zip archive from https://github.com/diglet48/restim/arch ... master.zip
6.2. Unzip the file «restim-master.zip»
6.3. Right-click on the unzipped «restim-master» folder and select «Services > New Terminal at Folder»
6.4. From the unzipped «restim-master» folder, drag the «run.sh» file into the terminal
6.5. Press Enter
6.6. Python will start, then Restim

[darthjj]

Hello everyone! I will try to describe in detail how I launched Restim 1.30 on my computer MacBook Air (13-inch, 2017), Intel Core i5, macOS Monterey 12.7.5

Awesome that you're making a guide to help people out!

The run.sh script creates a Python virtual environment for Restim, this is a good practice to avoid dependency issues between different Python programs. But if Restim is the only Python program you have then I suppose it doesn't matter much. However, if you do want to use a virtual env then it should be created and activated before running "pip install" for the first time, and when you run it again in the future you need to activate the virtual env again (it stays activate as long as you have the terminal open).

If you don't use virtual env, which is perfectly fine, then I don't see why you would need anything more than just "python3 restim.py" when running it again in the future (point 5).

If you download the latest run.sh from github, i.e. from master, since it has been modified after the 1.30 release, then it should handle setting up the virtual environment, installing requirements using pip, and then launching restim. However, I realized that zip probably removes the execute permission from the script, so you might have to add it back yourself. If you download a future release and the get .tar.gz instead, or clone the repository using git, then it should have correct permissions.

To run Restim on Linux, I would try the following:

1. Download https://github.com/diglet48/restim/arch ... master.zip
2. Unzip the file somewhere
3. Open a terminal in the unzipped folder
4. Make the launcher script executable (only before first run):

Code: Select all

chmod +x run.sh

5. Run the launcher, which should install dependencies the first time:

Code: Select all

./run.sh

However, I think it's possible that it needs Qt to be installed in the OS, which would be a different procedure for different distributions. No idea how that works on Mac.

[yetatu]

Hello everyone! I will try to describe in detail how I launched Restim 1.30 on my computer MacBook Air (13-inch, 2017), Intel Core i5, macOS Monterey 12.7.5

If you don't use virtual env, which is perfectly fine, then I don't see why you would need anything more than just "python3 restim.py" when running it again in the future (point 5).

I am not a developer and I know Python very superficially! I just tried to describe in detail the steps by which I was able to launch Restim.
Indeed, I just checked, for run Restim next time you can select the file «restim.py» in the Restim folder, right-click and then «Open With > Python Launcher.app».
Thanks for the tip!

[Bouncyboingboing]

I've mainly been using my DIY box with audio tracks but after seeing the thread about the FOC circuit I thought I'd give restim another go.

I tried restim about 6 months ago. I guess I really didn't have any luck straight off the bat, so parked it as an idea. However the FOC thread changed my mind, and particularly this post viewtopic.php?p=361250#p361250 from diglit

After installing and getting the software up and running I loaded up the Mistress and the control box vid and diglet's funscripts and my world changed. I had tried the audio estim version and never really enjoyed it. But the restim version had me on the edge for the full video. Climaxing uncontrollably (without mistress's permission ) near the end.

I've now ordered the parts to build the FOC device. New addiction unlocked!

I also have a coyote V3. I've searched the forum and read the WIKI for restim and it would seem that it's possible to connect the coyote to receive the restim signal, but I can't figure it out. Is it possible? Can anyone help me with directions on how to do it?

Thanks

[diglet]

I just did an experiment with Restim which might have some potential..

Cool. There was some discussion about this recently on discord, but I haven't taken the time to implement/test it yet. I would like to move towards a new protocol in the future that support per-pulse control, but that is still a long way off.

If you want more focus on the head, you can also try to restrict the circle (adjust limits, below the calibration controls). Or create a custom funscript conversion algorithm.

However, I think it's possible that it needs Qt to be installed in the OS, which would be a different procedure for different distributions. No idea how that works on Mac.

Qt libraries are installed via pip.

I also have a coyote V3. I've searched the forum and read the WIKI for restim and it would seem that it's possible to connect the coyote to receive the restim signal, but I can't figure it out. Is it possible? Can anyone help me with directions on how to do it?

Thanks

It is possible via some elaborate audio routing, it requires voicemeeter and the xtoys desktop app, it's not very easy to setup. Mostly because the voicemeeter UX is terrible. But I don't really recommend this, the entire point of restim is to create nice threephase signals and the coyote hardware doesn't support threephase. Neither does the xtoys audio parsing algorithm.

I recommend one of these apps for controlling the coyote.
https://github.com/Amethyst-Sysadmin/Howl
https://discuss.eroscripts.com/t/dg-lab ... 3/144399/1

[Bouncyboingboing]

Thanks diglet. It sounds like a bot of a faff. Hopefully I'll get my FOC device built soon.

[emiumfinal]

Just getting started with Restim - had it configured with MPV and MFP and then realized that is no longer really needed so thanks for making things simpler. Question I had though, maybe I missed it somewhere, but is it possible to configure a different folder location for the Funscripts from the videos themselves? I have a folder with all my videos in it, and it would be nice to keep that folder clean by having another folder where I put the funscripts (since there are now quite a few for some videos) but I didn't see a way to do that.

[diglet]

Just getting started with Restim - had it configured with MPV and MFP and then realized that is no longer really needed so thanks for making things simpler. Question I had though, maybe I missed it somewhere, but is it possible to configure a different folder location for the Funscripts from the videos themselves? I have a folder with all my videos in it, and it would be nice to keep that folder clean by having another folder where I put the funscripts (since there are now quite a few for some videos) but I didn't see a way to do that.

Yes, click the 'search paths' button at the bottom of the media sync screen.

[Bouncyboingboing]

I’m having trouble with the funscript conversion tool. I’ve tried to convert 3 different funscripts and each time I only end up with a partial conversion

The initial few minutes are just outstanding. And then it seems to hang in one position (if that makes sense) for the rest of the track. There’s no further movement of the signal. There doesn’t seem to be any common time frame either. One track was 22 mins before hanging. The other two were about 6mins and 12 mins respectively.

I’ve tried both a Mac and a PC. With the same results.

What am I doing wrong? Any help would be greatly appreciated as I can see this is an amazing tool.

Thanks.

[diglet]

I haven't seen this before. Can you send me the funscript files so I can investigate?

[Bouncyboingboing]

Thanks Diglet.

PM'ed you.

[icehash23]

I messed around today a bit in Python trying to get XToys to talk to Restim.

I got position/duration data (custom "Stroker" toys) from two funscripts going, synced to video, with the python code handling the websocket server, translation of XToy's JSON to tcode, and relaying it to restim's websocket.

Turns out though, looks like xtoys only sends updates from funscripts every ~100ms, which leads to pretty erratic movement of the point on Restim's phase display. Likely not much of a problem with stroker toys and vibrators, but with estim...

Patterns weren't any better, compared to what MFP can do with its Motion provider. Same issue I think, just updates too slow.

Has anyone else gotten this working? It's sad that XToys doesn't support Restim, or custom multi-axis toys, or even sending more than one channel's data per websocket message.

Emailed their support about it a couple days ago, no response yet. I just want to let people share their FOC-Stim! ;D

[Pinco]

hi diglet,

How can I start restim with 100% of volume-volume ramp by default?

When I start restim the volume-volume ramp is set at 10% and any volume.funscript is applied to this 10% (I mean if volume.funscript is at 10% the overall output volume is 1% etc). So every time I have to increase the volume-volume ramp to 80-100% to achieve a good output level.
I also tried changing Funscript/T-code min volume value with no success.
Thanks

[edger477]

hi diglet,

How can I start restim with 100% of volume-volume ramp by default?

When I start restim the volume-volume ramp is set at 10% and any volume.funscript is applied to this 10% (I mean if volume.funscript is at 10% the overall output volume is 1% etc). So every time I have to increase the volume-volume ramp to 80-100% to achieve a good output level.
I also tried changing Funscript/T-code min volume value with no success.
Thanks

There is [volume] section in ini file... set to what you want to be default (20 here)

Code: Select all

[volume] 
...
default_level=20