[App] MetroVerter - Metronome-Tcode Converter

[47dahc]

MetroVerter is here!!!

Current Version: 2.2

MV.png (187.21 KiB) Viewed 13881 times

The only Metronome to Linear Tcode converter...that I know of, anyway.

Have you ever wanted to use restim, OSR, OSR2, or any other linear tcode driven device with the teases or games found here on Milovana or else where but just couldn't because they wouldn't connect with each other?

Well now you can!!!

This program runs using python and connects to Intiface Central which then, can connect to just about any linear tcode device like the ones I mentioned above. It listens to a virtual audio device like VB-Cable and converts metronome beats to LinearCMD commands that Intiface Central will process for the device you are using.

How to use
Start Intiface Central and start its server
Ensure your virtual audio device is selected as your audio device in Windows
Make sure your tcode device is connected to IC or start restim if using that.

Spoiler: show

Follow the instructions at Eroscripts to connect restim to Intiface.

Either way, take note of its "Index" number on the "Devices" tab
Start MetroVerter
Select "Scan" and select the correct virtual audio device that matches the Windows audio device selected earlier
Ensure the proper "Intiface Address" and "Target Device Idx" is correctly set.
Choose if you want half or full strokes
Select "Connect"
Play whatever tease or game you want, whether it's got a metronome, written commands or a mix, MetroVerter should make it more interactive.

MetroVerter can be used with just about any tease or game that either has a metronome or simply tells the user how to stroke. It even does mixtures like Malena's Maze of Teasing, which I used extensively for testing the different features listed below.

Please see original post at the bottom of this post if curious about its background and third party software needed

User Interface

Spoiler: show

Screenshot 2025-04-29 151107.png (31.57 KiB) Viewed 14664 times

List of functions added

• Always on Top:
  An option checkbox for "Always on Top" to allow sitting on top of tease window. More for laptops and single screen setups

and

• Pause and Resume:
  Pause button to pause all functions and actions until resumed

  Spoiler: show

  

  Pause_AOT_BI.png (5.02 KiB) Viewed 14664 times

• Manual Stroking Section:
  Seven buttons, "1/4", "1/3", "1/2", "1", "2", "3", & "4", each representing BPS.

  Spoiler: show

  

  Manual Stroking.png (2.69 KiB) Viewed 14664 times

• Numerical Stroking:
  Three sets of buttons with each set being labeled Slow, Medium, Fast with user customizable BPM.
  Each set has buttons numbered 5-35 in increments of five and 40-100 in increments of ten.
  When a button is pressed, the corresponding number will result in that number of commands being sent at the corresponding speed set by the user. When multiple buttons are pressed, it will sum the remaining strokes and the new amount. It will take the speed of the last number selected.
  For example, if 50 is pressed in slow, it will start sending 50 commands at the slow BPM,
  if 5 is pressed in fast, while the original 50 is still being processed, it will add 5 more strokes and change the speed to fast.

  Spoiler: show

  

  NumStroke.png (9.71 KiB) Viewed 14664 times

• Edge and Ride buttons:
  Two buttons, "Edge!!!" and "Ride!!!". Each one with an input box that the user can input a BPM of their choosing. Everybody is different so this allows for customization depending on the user and restim settings or tcode device selection and what sensations make them edge and what makes them ride the edge (some testing by the user will be needed to fine tune their individual settings). When either button is pressed, the set BPM will play until it is pressed again or another manual function (manual stroking, numerical stroking) is selected. Audio detection is disabled when any of the manual functions are activated

  Spoiler: show

  

  Edge and Ride.png (2.9 KiB) Viewed 14664 times

• User Config file:
  The program will save the current session's settings in a config file for reuse the next time the program is opened. If no config file is found, it will load the defaults.

List of fixes and changes

• Fixed: Issue with reconnecting after disconnecting.
  Note: User must wait until Intiface Central shows the client disconnected before attempting to reconnect

• Fixed: Made the min/max positions usable while the program is running to allow dynamically changing the stroke length without stopping the program

• Fixed: Numerous bugs introduced while implementing features listed above

• Adjusted: Audio detection setting for better beat detection

• Changed: Start/Stop buttons to Connect/Disconnect

• Changed: Size and color of beat indicator for easier distinction of when beats are detected

So How do I get and install it

There is an executable and the python source code scripts at:

https://mega.nz/folder/5XZxzQaQ#uHt9dBY6ENxACdYg_aFi3Q

Download either one and just run the "MetroVerter.exe" or the "run_metroverter.py" file. It is completely portable and can be ran from any windows environment. The only thing it will create is the User Config file upon exit which will be placed in the same directory that MetroVerter was ran from. You will also need Intiface Central and VB-Cable as mentioned in the original post below.

Please see original post at the bottom of this post if curious about its background

Spoiler: show

Hey everyone,

I want to introduce an application I've been working on the last couple of days with the help of ChatGPT and Google AI Studio since, 1.) I'm not a coder and, and 2.) I had no idea where to start. I've wanted to come up with something like this for awhile since diglet released the awesomeness known as restim. I even asked diglet if they could implement something but, with other restim updates and bugfixes, diglet unfortunately didn't think they could get anything implemented anytime soon. So, I decided to give it a go and here we are.

The basic idea actually came from Batman314 with their cool EstimControl App that would listen for a metronome over a virtual sound device like VB-Cable and then create an estim signal and adjust it depending on the BPM of the beats. It worked great besides not being able to adjust frequency. It had a little adjustability and some other features like edging and being able to set a number of strokes and such but sometimes the stock frequency just didn't feel good. As the stimmers know, each session is usually different depending on your body and electrodes. Either way, ESC is a great program and I still use it from time to time when I come across a metronome tease. But, ESC's adjustability just wasn't there like restim's is.

Fast forward to now. My app, MetroVerter, just like ESC, will listen to VB-Cable and when a metronome is detected, will send a command to Intiface Central, which will then send the proper tcode command to restim for creation of whatever estim signal you have it creating. I have tested it with FapInstructor (voices, moans, and video need to be muted) as well as a few metronome teases here and it does fairly well up to 240bpm. You can select half strokes, where each beat is either up or down, or full strokes, where each beat is a full up/down cycle. It also has an indicator for beat detection, and status for the commands and time being sent. What I haven't tested yet but, I can only assume is, that it will also drive whatever linear stroker you might have as well if you have one setup in Intiface.

IC server must be started before connecting MetroVerter as a client

When it first starts...Set your Intiface address, Scan and select your VB-Cable or virtual input device that the metronome will be heard on, your position min/max values, and what mode (stroke type) you want

Screenshot 2025-03-31 103133.png (13.78 KiB) Viewed 16194 times

It is completely portable and should run as is, from anywhere in Windows and does not install anything.

The only other things you should need is Intiface Central, VB-Cable, and restim or a tcode linear stroker of choice.

Please give it a try and let me know of any issues or ideas. Please import before download. It's not a big file, only 23MB, but don't want to take any chances of filling download limits.

https://mega.nz/folder/5XZxzQaQ#uHt9dBY6ENxACdYg_aFi3Q

The mega folder contains the portable executable as well as the python script for those interested.

Version 1.1 List of Changes

• Name change to MetroVerter from MetroICRestim

• User must select Scan and select correct audio device that the metronome will be heard on

• Added the ability to change device ID as shown in Intiface Central

  Spoiler: show

  • Note: IC Server must be started to get ID from Device menu

• Added sliders for min/max position adjustability
  • Note: Not adjustable once connected

• Added more status lines in case errors are detected

[Electro]

I'm running into an issue, I scan for devices, choose the audio device, I click start when I've got audio running with metronome beats and it will show a couple of beats during the first few seconds and then it disconnects and the Metronome client says "Stopped. Ready." Intiface will show "MetronomeClient Connected" on the top, but only for that second and goes back to "Engine running, waiting for client". In the Intiface log, it shows "Connector closing connection Websocket server closed"

[47dahc]

I'm running into an issue, I scan for devices, choose the audio device, I click start when I've got audio running with metronome beats and it will show a couple of beats during the first few seconds and then it disconnects and the Metronome client says "Stopped. Ready." Intiface will show "MetronomeClient Connected" on the top, but only for that second and goes back to "Engine running, waiting for client". In the Intiface log, it shows "Connector closing connection Websocket server closed"

I was able to replicate with settings in Intiface. Make sure you have "Device Websocket" (#1) turned on in the "App Modes" menu in Intiface. Then start the server (#2).

Screenshot 2025-03-27 235246.png (217.01 KiB) Viewed 17320 times

When I turned Device Websocket off, it did exactly what you described. Once I turned it back on, it worked as advertised, at least on my computer. If not, do Intiface logs show anything? What version of Intiface Central. It was tested with IC v2.6.5 and Restim 1.31.

[Electro]

I was able to replicate with settings in Intiface. Make sure you have "Device Websocket" (#1) turned on in the "App Modes" menu in Intiface. Then start the server (#2).
Screenshot 2025-03-27 235246.png
When I turned Device Websocket off, it did exactly what you described. Once I turned it back on, it worked as advertised, at least on my computer. If not, do Intiface logs show anything? What version of Intiface Central. It was tested with IC v2.6.5 and Restim 1.31.

I have the device websocket turned on in App Modes because it's also needed for Restim which works fine with Script Player. Script Player is not running when I'm trying to connect to the Metronome Client though. I do have the server running when I try to connect the two tools. It shows the MetronomeClient connected at the top, but only for a second and it disconnects after about a second of being connected. The log looks like this. Ignore the blacked out section, that's a different bluetooth device halfway across the house that doesn't interface with Intiface that I can't turn off but it doesn't interfere with Script Player or Restim when using those together and that shouldn't matter here either because I'll often see a neighbor's Samsung TV showing up too and it never causes any issues either. I'm also using the same version of Intiface and Restim.

IntifaceMetronomeClient.png (32.22 KiB) Viewed 17295 times

[47dahc]

Spoiler: show

I was able to replicate with settings in Intiface. Make sure you have "Device Websocket" (#1) turned on in the "App Modes" menu in Intiface. Then start the server (#2).
Screenshot 2025-03-27 235246.png
When I turned Device Websocket off, it did exactly what you described. Once I turned it back on, it worked as advertised, at least on my computer. If not, do Intiface logs show anything? What version of Intiface Central. It was tested with IC v2.6.5 and Restim 1.31.

I have the device websocket turned on in App Modes because it's also needed for Restim which works fine with Script Player. Script Player is not running when I'm trying to connect to the Metronome Client though. I do have the server running when I try to connect the two tools. It shows the MetronomeClient connected at the top, but only for a second and it disconnects after about a second of being connected. The log looks like this. Ignore the blacked out section, that's a different bluetooth device halfway across the house that doesn't interface with Intiface that I can't turn off but it doesn't interfere with Script Player or Restim when using those together and that shouldn't matter here either because I'll often see a neighbor's Samsung TV showing up too and it never causes any issues either. I'm also using the same version of Intiface and Restim.
IntifaceMetronomeClient.png

Hmm. Windows? (10 or 11). You could try and run it from the python script in the original post. It will have a console window (like restim does) for the program to see if it says anything.

[lr_x3]

Hi Electro, 47dahc,

I have/had the same problem when pressing start - it doesn't stay connected.
But after pressing the start a 2nd time (after it switched to stop again) it stays connected.
I tried it maybe 5-6 times and it happens every time after starting Intiface Central.
And once it even stopped the 2nd time and I had to press the start a 3rd time. (maybe Intiface Central needs some time after starting up?)

But when it's connected it works like a charm with metronome teases on Milovana and moving The Handy in sync.
Thank you so much for that piece of software.

[47dahc]

But when it's connected it works like a charm with metronome teases on Milovana and moving The Handy in sync.
Thank you so much for that piece of software.

It is my pleasure and a fun project and thanks for the info.

I have/had the same problem when pressing start - it doesn't stay connected.
But after pressing the start a 2nd time (after it switched to stop again) it stays connected.
I tried it maybe 5-6 times and it happens every time after starting Intiface Central.
And once it even stopped the 2nd time and I had to press the start a 3rd time. (maybe Intiface Central needs some time after starting up?)

For sure the IC server needs to be running and your selected device needs to be connected to it. Once that is done, then you should be able to start MetroVerter (possible new name...lol) and enjoy. Unless there is a conflict with ports or something that I can't duplicate on my setup, not sure I will be able troubleshoot. Only devices I have are restim and an OSR2 which I haven't tested yet along with three Windows 10 computers. I have tested it with metronome sites, FapInstructor, and a few teases here. I need to test and see if I can run TeaseAI Awakening because it connects as a client to IC. So I'm not sure if it will work with that but, it should as long as you don't enable interactive toys and connect it to IC.

I'm curious if there might be a port conflict causing issues. I left it as 12345 because that's what I had in my IC. It can be changed though.

[Electro]

Hi Electro, 47dahc,

I have/had the same problem when pressing start - it doesn't stay connected.
But after pressing the start a 2nd time (after it switched to stop again) it stays connected.
I tried it maybe 5-6 times and it happens every time after starting Intiface Central.
And once it even stopped the 2nd time and I had to press the start a 3rd time. (maybe Intiface Central needs some time after starting up?

That's a little bit confusing to me because Intiface will connect one-sided to Restim or one-sided to Script Player (without Restim running). Is it possible that Metronome tool is not seeing Restim fast enough and is timing out after a second or two? My computer isn't a slow machine, at least I don't consider an 11th gen Intel chip to be slow, so I don't know. I've tried to click the start button dozens of times and it won't stay connected to Intiface. Is there a timeout setting somewhere or a way to have the Metronome tool not fail if it doesn't see a T-Code connected device right away, similar to how Script Player can be connected without Restim if I launch Restim after? This is happening if I launch Restim first, start Intiface with the play button, then launch Metronome tool and click start on the Metronome tool, or click scan and then start because it seems to ask me to despite the audio device being connected.

[lr_x3]

But after pressing the start a 2nd time (after it switched to stop again) it stays connected.
I tried it maybe 5-6 times and it happens every time after starting Intiface Central.

Unfortunately I have to report that I have now the same symptom as Electro - the connection to IC doesn't stay connected anymore today - no matter how many times I press the start button.
Seems it was just a lucky coincidence that it worked yesterday.
FYI: installation is on a Win11 Home Laptop. But after it didn't work anymore today I also installed it on my Win10 Pro Desktop - with the same problem there.
I might try the raw python script and see if there are further messages - but this may not happen today.

[lr_x3]

After playing around with the raw python script I found the problem

The first problem was that the status information in the gui window is only one line - so every message written there by the program gets overwritten with the next message. So you'll only see the last message "Stopped. Ready" and not the real error message 1 or 2 lines before. So I've inserted a few print statements into the python script that are written to the cmdline window - which then showed me the problem.

At the beginning in the script there are some default config values:

Screenshot 2025-03-29 at 14.31.22.png (24.56 KiB) Viewed 16421 times

Specifically the "DEFAULT_TARGET_DEVICE_INDEX" is the culprit here. That's the device index in Intiface for the restim device and the default value is 0. Although it says above that this config may be overwritten by the GUI - that is not the case because that config variable isn't on the GUI window to change. So the restim device in Intiface has to have the index no 0.

Which isn't the case in my config because I am using my existing Intiface config

Screenshot 2025-03-29 at 14.30.58.png (35.73 KiB) Viewed 16421 times

and there it has the index value 3. So I always got the error "Device Index not found" and the connection was closed.

Because I was starting MetroICRestim already via the raw script I just changed the default config value to 3 and from there on it worked.
But for the Windows executable to work it would be best to put this config variable also on the GUI window.
Maybe deleting all devices in Intiface Central und re-defining them - starting with the restim websocket device - might work - if IC is starting with 0 when defining devices.

[47dahc]

After playing around with the raw python script I found the problem

The first problem was that the status information in the gui window is only one line - so every message written there by the program gets overwritten with the next message. So you'll only see the last message "Stopped. Ready" and not the real error message 1 or 2 lines before. So I've inserted a few print statements into the python script that are written to the cmdline window - which then showed me the problem.

At the beginning in the script there are some default config values:
Screenshot 2025-03-29 at 14.31.22.png
Specifically the "DEFAULT_TARGET_DEVICE_INDEX" is the culprit here. That's the device index in Intiface for the restim device and the default value is 0. Although it says above that this config may be overwritten by the GUI - that is not the case because that config variable isn't on the GUI window to change. So the restim device in Intiface has to have the index no 0.

Which isn't the case in my config because I am using my existing Intiface config
Screenshot 2025-03-29 at 14.30.58.png
and there it has the index value 3. So I always got the error "Device Index not found" and the connection was closed.

Because I was starting MetroICRestim already via the raw script I just changed the default config value to 3 and from there on it worked.
But for the Windows executable to work it would be best to put this config variable also on the GUI window.
Maybe deleting all devices in Intiface Central und re-defining them - starting with the restim websocket device - might work - if IC is starting with 0 when defining devices.

Oh wow. Thanks for doing that. I'll take a look when I can get back to my computer and see about getting that corrected. Will do a rebuild as well and get it uploaded.

[47dahc]

MetroVerter 1.1 is available from the mega folder below. Portable executable as well as the python script are in it.

https://mega.nz/folder/5XZxzQaQ#uHt9dBY6ENxACdYg_aFi3Q

Screenshot 2025-03-31 103133.png (13.78 KiB) Viewed 16197 times

List of Changes

• Name change to MetroVerter from MetroICRestim

• User must select Scan and select correct audio device that the metronome will be heard on

• Added the ability to change device ID as shown in Intiface Central

  Spoiler: show

  • Note: IC Server must be started to get ID from Device menu

  

  Screenshot 2025-03-31 103437.png (13.73 KiB) Viewed 16197 times

• Added sliders for min/max position adjustability
  • Note: Not adjustable once started

• Added more status lines in case errors are detected

Thanks to all who provided some feedback and please keep it coming

[lr_x3]

MetroVerter 1.1 is available from the mego folder below. Portable executable as well as the python script are in it.

Thank you very much for the quick changes and improvements.
It's working really good now and the gui has everything what's needed now.

Only one minor remark:
The status window has now the space to show more lines - but it still shows only the last message line -
I guess because of the self.status_label.delete (in update_status) at line 472.
I tried it with this modifications and then it works like intended

Screenshot 2025-03-31 at 18.01.34.png (13.84 KiB) Viewed 16173 times

I also added a newline at the end of every message for better readability (line 473).

Not sure though what consequences it can have (only appending lines to the status field/variable) - I'm not familiar with python.

[47dahc]

MetroVerter 1.1 is available from the mego folder below. Portable executable as well as the python script are in it.

Thank you very much for the quick changes and improvements.
It's working really good now and the gui has everything what's needed now.

Only one minor remark:
The status window has now the space to show more lines - but it still shows only the last message line -
I guess because of the self.status_label.delete (in update_status) at line 472.
I tried it with this modifications and then it works like intended
Screenshot 2025-03-31 at 18.01.34.png
I also added a newline at the end of every message for better readability (line 473).

Not sure though what consequences it can have (only appending lines to the status field/variable) - I'm not familiar with python.

Cool. Will get it corrected on next build. I am currently trying to smooth out the transitions from fast to slow and vice versa so, If I get something working, I'll get a new build done.

[Electro]

Thank you, this is working great for me