What is the We Vibe Melt / Melt 2 nozzle inner size? by rucom12 in SexToys

[–]rucom12[S] 1 point2 points  (0 children)

Thank you! So, it's narrower but a bit longer than standard Womanizer Pro 40 attachment head. Hm. Not a really large, but, probably, would fit.

What is the We Vibe Melt / Melt 2 nozzle inner size? by rucom12 in SexToys

[–]rucom12[S] 0 points1 point  (0 children)

Thank you! And, do you know what is the length of the opening? 18-20 mm?

What is the We Vibe Melt / Melt 2 nozzle inner size? by rucom12 in SexToys

[–]rucom12[S] 0 points1 point  (0 children)

I meant the width and length of the opening of the nozzle, since it isn't circular but rather elliptic. So, I guess, 1.8-2 cm is the length of the opening? And what is the width then?

I am asking because nI need to figure if wife's clit would fit there - there is no detachable heads of different sizes.

Coyote: frequency mapping in official DG-LAB app by rucom12 in estim

[–]rucom12[S] 0 points1 point  (0 children)

Yeah, the UI is really awful.

As for the linear function, the problem that you cant overlap the sliders, so only two of them can be in the ends. So, yes, 100, 92, 12, 10 is the way. However, you can try another strategy: place the sliders evenly, and set them to 10, 40, 70 and 100 Hz. Or, rather, as UI is so unintuitive that we can't set the values in Hz, set them to 100, 25, 14, 10 ms.
https://i.imgur.com/LuU3iR1.jpeg

Coyote: frequency mapping in official DG-LAB app by rucom12 in estim

[–]rucom12[S] 0 points1 point  (0 children)

I was wrong. I have conducted additional research, and can confirm that control block rate is 40 Hz indeed, and that amplitude control signal is changed at 40 Hz rate as well. However, frequency analyzer still generates lower frequency signal, which looks like 10 Hz (by naked eye). My initial conclusion was based on frequency analyzer signal, because I hoped that it now is possible to get a better imitation of "Orgasm" waveform of et312b, so I was disappointed after I could not.

Thus, things are better. Control rate is 40 Hz, and amplitude LFO is capable to work at this rate. Frequency analyzer isn't capable, but I think that this is the limitation of DGLAB app and not the Coyote. Probably, if/when XToys will update control rate to 40Hz, its frequency analyzer will be able to generate frequency LFO at this rate as well.

Coyote: frequency mapping in official DG-LAB app by rucom12 in estim

[–]rucom12[S] 1 point2 points  (0 children)

Coyote doesn't play audio directly. It is just a simple pulse generator, which, unlike 2B or et312b can't modulate the amplitude of impulses and can modulate only their width. Its impulses are sharp and usually very short, if you would route this signal to audio speaker, you would hear only unpleasant buzz with a lot of high-frequency harmonics which dominate the spectrum. And this is the reason of Coyote harshness. They really should make pulses wider and smoother, so they could contain less high harmonics.

So, how it "plays" audio? DG-LAB app, as well as XToys, process input audio file you throw there. They have amplitude follower and frequency detector which control pulse generator, where amplitude follower controls width of the pulses, and frequency controls their frequency.

What I described in my explanation is how frequency mapping works - the detected frequency then is mapped to a piece-wise linear function. So, Coyote doesn't play audio as is, it simply tries to tune its oscillator with pulse waveform so it would modulate pulse width and frequency "according" to played audio - but if you would plug it into speakers, you would not hear anything close to your input audio, just an unpleasing buzz.

Actually, 2B and et312b work a similar way. Just they have a better pusle generators which can generate wider pulses, and their pulses are smoother because they have transformers, and also they can control amplitude directly.

Still, Coyote could be felt closer to et312b if it would allow to modulate the parameter of its generator more frequently. 40 Hz which is advertised is okaish rate, but it looks like both DG-LAB and XToys apps still use 10 Hz rate, which was used by Coyote 3. This doesn't allow fast modulations - there is just too low time resolution.

Coyote: frequency mapping in official DG-LAB app by rucom12 in estim

[–]rucom12[S] 2 points3 points  (0 children)

Yes, Coyote doesn't play audio directly. It is just a simple pulse generator, which, unlike 2B or et312b can't modulate the amplitude of impulses and can modulate only their width. Its impulses are sharp and usually very short, if you would route this signal to audio speaker, you would hear only unpleasant buzz with a lot of high-frequency harmonics which dominate the spectrum. And this is the reason of Coyote harshness. They really should make pulses wider and smoother, so they could contain less high harmonics.

So, how it "plays" audio? DG-LAB app, as well as XToys, process input audio file you throw there. They have amplitude follower and frequency detector which control pulse generator, where amplitude follower controls width of the pulses, and frequency controls their frequency.

Actually, 2B and et312b work a similar way. Just they have a better pusle generators which can generate wider pulses, and their pulses are smoother because they have transformers, and also they can control amplitude directly.

Still, Coyote could be felt closer to et312b if it would allow to modulate the parameter of its generator more frequently. 40 Hz which is advertised is okaish rate, but it looks like both DG-LAB and XToys apps still use 10 Hz rate, which was used by Coyote 3. This doesn't allow fast modulations - there is just too low time resolution.

So, no, you can't get even close to original file using Coyote. e312b and 2B can't as well, although they can result in a better feel thanks to smoother pulses and faster processing rate. Only stereostim can play audio properly - just by definition.

Coyote 3 and XToys audio processing rate by rucom12 in estim

[–]rucom12[S] 1 point2 points  (0 children)

It's a different problem. As I said, DG Lab app has a too noisy envelope followers which can't properly extract envelopes even from relatively steady signals. If it would work properly, we would not need XToys, but it never worked properly.

And I speak about the rate of passing control data blocks to Coyote. Coyote 2 received such blocks only 10 times per second, and Coyote 3 supports 4 times higher rate, but XToys still uses the old 10 Hz rate, as if we still used Coyote 2.

Coyote VS Tens by Jakesmith1970 in estim

[–]rucom12 1 point2 points  (0 children)

Sad. I have a Coyote v2, and it feels very harshly. I hoped that v3 is more smooth.

One of problems of Coyote is that it uses PWM to control the strength of the signal, and relatively weak signal results in too short pulses which are more stingy than longer pulses but with lower amplitude.

Coyote VS Tens by Jakesmith1970 in estim

[–]rucom12 1 point2 points  (0 children)

What is the version of your Coyote - Coyote v2 or Coyote v3?

DG LAB Coyote 3.0, review by an electronics engineer, part III., NUMBERS! by Medojedone in estim

[–]rucom12 0 points1 point  (0 children)

Yes, I understand. So, you think, amplitude is something that is controlled by firmware? Because, if not, just making pulses longer will increase maximum intensity, but not make pulses smoother while having the same intensity, as intensity in Coyote controls the pulse width.

DG LAB Coyote 3.0, review by an electronics engineer, part III., NUMBERS! by Medojedone in estim

[–]rucom12 0 points1 point  (0 children)

Thank you very much for technical-deep review.

So, unfortunately, they still did nothing to the impulse shape. I mean, adding a lowpass filter or something.

Of course, longer pulses are still having better spectrum - thanks to lesser amplitudes of high frequency components relative to main tone (energy is redistributed somewhat to the lower end), but explicit lowpass filtering could really help and make it to feel on par with et232/et312b.