AudioDeviceCmdlets

AudioDeviceCmdlets copied to clipboard

Fixing:

• #66
• #67
• #68
• #69

I have never been much of a maintainer so please bear with me. I will test this and try to look at the code more closely, but at first glance this looks like an interesting enhancement.

@frgnca Thanks!

If you want help maintaining the thing, I'm pretty sure I could step up to the plate.

Would it be possible to prevent Tab autocomplete suggestions such as these? Write-AudioDevice -PlaybackMeter -RecordingCommunicationMeter Write-AudioDevice -PlaybackStream -RecordingCommunicationStream Meaning parameter combinations that results in alternating meters or interwoven streams

I don't think I've ever figured out a way to make tab completion handle mutually exclusive parameters in the way you're wanting.

I also do recall it was possible to have both a playback meter and a recording meter active.

Personally, I'd consider that a totally valid scenario (think monitoring both your playback and recording levels).

When we're returning data, we could add a noteproperty indicating which stream it is coming from.

We could also get a notch more sophisticated with the return for a stream and return an object of our own design.

This may be preferred, as it gives us a way to provide some analysis of the audio.

For example, we could add a .Phase property (the ratio between two channels of audio)

Lemme know if you'd like me to add more / what you'd like me to add.

I'd very much like this to be updated on the PowerShell Gallery by mid-march, in preparations for some April releases.