#Tonegenerator best alert type series#
While researching this article, however, I stumbled onto a Web page where someone had created full-blown musical compositions using a series of beep commands in PowerShell.
#Tonegenerator best alert type windows#
So what about the portion of the command? Again, I couldn't find anything definitive, but this seems to be a way of redirecting output to the Windows console.īeing able to signal the end of a long-running script with a tone can obviously be useful. I wasn't able to find anything that confirmed the correlation between this number and the number of seconds that the tone plays, but a value of 1,000 seems to be roughly about a second.
In case you are wondering, the second number used by the beep command controls the duration of the tone. So I think that the lesson here is to ignore Microsoft's recommendation to use tones between 190 and 8,500. The same error message indicated that the highest-frequency tone that PowerShell could produce was number 32,767. I was able to hear tone number 37 with no problems. Doing so actually caused PowerShell to produce an error message saying that the lowest supported value was 37.
That being the case, I decided to go with the ridiculously low value of 20. On the low end, I tried using a value of 50 and was able to hear the tone. I will be the first to admit that everyone's hearing is different, and I have really good hearing, so your results may vary. Out of curiosity, I decided to put this to the test for myself. On other Web sites, however, there are those who claim to be able to hear higher and lower frequencies. According to Microsoft, anything lower than 190 or higher than 8,500 is beyond the range of human hearing. The valid range of these numbers is debatable. You can experiment with different numbers to change the sound of the tone. This number controls the pitch of the beep. Obviously, the beep portion of the command is what generates the sound, but you will notice that there are two numbers following the beep. So let's take a look at what this command is actually doing. The technique used for producing a basic tone is simple. That way, you can go do something else while the script is running, but know the instant that the script completes. For long-running scripts, it can be handy to get PowerShell to play a sound when the script completes.
I have, on occasion, built scripts that took upwards of 20 minutes to execute. Some PowerShell scripts take a long time to run. As obnoxious as this probably seems, it does have its place. Recently, I have been experimenting with adding auditory prompts to PowerShell scripts. However, it is also possible to use PowerShell to produce audible output. Think about it for a moment: When you enter a cmdlet, PowerShell displays something on the screen in response, even if the output is only another PowerShell prompt, or even an error message. I have always thought of PowerShell as being primarily a visual interface.
0 kommentar(er)
