RFP: ToneEmitterCmd

[qdot]

Name of Outgoing Message, if any:

ToneEmitterCmd

Message Fields:

• Id (unsigned int): Message Id
• DeviceIndex (unsigned int): Index of device
• Volume (double): Volume, with levels set by StepCount. May map otherwise if needed (Fucking Pavlok)
• Duration (unsigned int): How long to play tone for

Describe message usage scenario Used for tones on shock collars and other sound emitting devices. Assumption is that output will be a single tone emitted for a short period of time.

Additional context Duration here may be difficult as some tones may be momentary?

[blackspherefollower]

You might want to specify that this is not intended for driving audio vibes (which would also need a tone generator and might be emitted from such a device)

[blackspherefollower]

And just for consistency/because such a device will turn up if you don't, shouldn't this accept an array of tone emitters?

[qdot]

Yeaaaaaaaaaaaaaaaaaaaaaaaaah I'm sure some asshole will put 2 tone emitters on a homemade collar just to spite me.

And maybe I should change the name? ToneEmitterCmd?

[blackspherefollower]

SoundCmd? Oh... What if one of these devices with prerecorded moans goes BLE with the ability to trigger those clips?

What if it's an off the shelf MP3 module and you get to specify filename? (I think we can ignore this case for now: I'm way into theoretical hardware)

[qdot]

Nah this is for an extremely specific kind of tone generator. SoundCmd/SoundPlaybackCmd/Whatever would be something different.

[blackspherefollower]

Also, am I that asshole? I'm not sure I would be in this case... Collars aren't really my thing.

[qdot]

You are most definitely not that asshole.

Many people on telegram have potential to be that asshole, though.

[blackspherefollower]

Back to the tone generation, are tones specific to the device, or are there different ones?

Selected by number, representative of particular frequencies? Or potentially by frequency directly?

If there aren't any known devices with selectors like this yet, we can always add it later with appreciate MessageAttributes to describe the additional control.

[qdot]

So far, all I've run into is devices that make a single beep, sometimes with a duration. This is so far true of the 2 collars I have, and the pavlok. There's no choice in the way of tone frequency, and I'd kinda like to keep this message simple.

For something where tone output might vary, I'd want to have a frequency attribute, but we might just leave that as a new message that'd be like "VariableToneCmd" or something?

I suppose I could maybe call this "BeepCmd"? Beep is a little more narrow than tone.

[qdot]

Haaaaaaaaaaaaaaaaaahahahahaha.

The fucking Pavlok has a percentage setting in its app for tone.

Each percentage setting is actually a different tone. It's not setting a volume.

I quit.

[blackspherefollower]

Do those tones increase in frequency, or is it just 100 different random tones?

[qdot]

It's just 10 different frequencies (they only allow setting in 10% increments). There's no order to it. So we could probably just stepcount this and call it good.

[qdot]

Just calling this a no-go for the foreseeable future. We don't have any non-collar devices that emit tones, and I don't want to support collars.