Hello, I have been wondering for some time now, is there a way to keep the volume or maybe I should be calling it level from dropping when the beat speeds up on a script? It seems like most all of the scripts converted to estim using the converter at https://cfs6t08p.github.io/funstim/funstim.html end up that way and i didn’t know if there was an easy to to stop the drop.
The folks at Milovana have developed a player and device to handle funscripts without needing to convert - the program is called Restim and it’s windows based with linux and osx builds, if you’re ok with fucking around in Terminal or familiar with python. I’ve used it a little on a spare windows device in the early stages but found it fiddly without much in the way of explanation - and the development was early, so you couldn’t really expect a lot.
I primarily use my OSX machine for e-stim since I can split audio to different devices more easily, and it’s what I’m used to for decades stimming - I tend to rely on another converter based off the first one you linked.
https://edger477.github.io/funstim/funstim.html
I would also recommend getting familiar with Audacity - a free program that will let you look at the carrier signal/wave form of an audio file. It’s very helpful to see if there is a click or pop from bad download, and after some practice you can look at a file and tell how it might feel. And if you really like a file or a section, it can edit for repetition or isolate a part and adjust, mix files, tweak volume, etc.
The linked converter is not being supported anymore, as per the disclaimer, but it still works. The big difference is a volume adjustment related to funscript position - you can adjust the intensity between R and L based on the position of the script, at 0, 50, and 100 - it builds more of a curve to the signal. You can also keep the signal within a position range - lets say you want to feel it mostly in one area, you can narrow the band with start/end positions changes, take the script 0 to make it a 20 and the 100 an 80, it’ll keep things “shorter” on the stroke.
Its not any less fiddly than Restim, but with Restim you can do all the settings on the fly, while it’s playing. On the converter, you have to run a whole file through, test it out, then any adjustments you have to figure out through trial and error repeats… the “stock” settings aren’t that great IMO. But to each their own.
I usually stim in tri-phase and common at the head, with these converted scripts. Running a script with roughly these settings seems to get me the most bang for my buck, but again - this is all really individual.
Fade in/out at 100ms
Sample rate 22050, but the lower feels more…granular?
frequency I tend to use 693 or 792, or a pair low and high at 495,891. Different feel for different scripts.
Mapping i do the same for r and l
vol ~90 at 0
vol ~75 at center
vol ~90 at 100
Center stays at 50. With head as common, the postion at 50 is both channels combined at common, the lower volume keeps the sensation more even. I’ve also run a few at 75,85,90 to some success - you’re really just going to have to carve out some time and find a combo that works for yourself. and write it down, lol.
Normalized position, 5 and 95, but 0 and 100 work too, gets you the whole range.
Inverted no
Double time not unless I’m speeding up something to crazy fast
Expand to full range - I’ve never been sure of what this does, but I tend to keep it unchecked, and on Audacity the signal looks less noisy.
Fade out - if you want the script to have a signal when it’s not indicating a stroke movement, leave this unchecked. Without a setting to determine what a “slow” or “pause” section is, its entirely up to the black box, and I’ve had it miss plenty of stuff.
Good luck!
Wow thats a lot of info for my old dog brain too absorb. Thank you for the information and I guess I will be doing some testing.
the entire “don’t do that”, “this is better” mentality is really off putting - this insistence is telling a person that they are doing something wrong. Maybe that’s not your intent, but it is what you are communicating.
Maybe someone likes a thing a certain way. Maybe they have their own reasons for a preference. (and they don’t owe you an explanation for why)
edit: this was a response to a user who deleted their account and had also posted some kind of shitty reply to this one that I never saw.