I thank you for your effort and I really thought you might have struck on a solution, but after trying to make it work for several hours, I am not sure I will ever make it work with this approach.
There are basically two problems. The first one is that you have to kill the 0 Hz output before you go with new process to produce a tone. If you don’t, they are both running at the same time and you end up with a unpleasant garbled tone, not a pure sine wave. I finally came up with a way of doing that, but it created a new problem. I am not sure if there is a lag in killing the first process so there is overlap or lag in starting the next one so there is gap, but regardless, there is quite a bit of noise at the transition. You might think of it as a “click” but it is really much louder and lasts a little longer than what you might associate with the term click. It is certainly not something you would want to live with.
I have also spent hours trying to get pulseaudio to work and I have managed to keep it from suspending and have even found a way to make it work from the console when logged in a root, but I cannot find a way for it to do what I want unless a user is logged in.
Why pulseaudio has been designed to only allow logged in non root users to use it without a lot of mickey mouse tweaking is beyond me. If it is for security, all I can say is “Lord, protect me from those who would protect me from myself!”
At the moment I am trying to work with only alsa, but no matter what I do the hum starts again after the sound generating script ends. With pulseudio there are .pa files etc that you can modify to prevent suspension, but I have yet to find a way to do so using only alsa.
On the old server I use to use “beep”, but it no longer works on some of the newer motherboards and my Gigabyte Z790 appears to be one of them.
I never thought I would say this, but sound is one area Windows is handling things much better than Linux. Image may be NSFW.
Clik here to view.
There are basically two problems. The first one is that you have to kill the 0 Hz output before you go with new process to produce a tone. If you don’t, they are both running at the same time and you end up with a unpleasant garbled tone, not a pure sine wave. I finally came up with a way of doing that, but it created a new problem. I am not sure if there is a lag in killing the first process so there is overlap or lag in starting the next one so there is gap, but regardless, there is quite a bit of noise at the transition. You might think of it as a “click” but it is really much louder and lasts a little longer than what you might associate with the term click. It is certainly not something you would want to live with.
I have also spent hours trying to get pulseaudio to work and I have managed to keep it from suspending and have even found a way to make it work from the console when logged in a root, but I cannot find a way for it to do what I want unless a user is logged in.
Why pulseaudio has been designed to only allow logged in non root users to use it without a lot of mickey mouse tweaking is beyond me. If it is for security, all I can say is “Lord, protect me from those who would protect me from myself!”
At the moment I am trying to work with only alsa, but no matter what I do the hum starts again after the sound generating script ends. With pulseudio there are .pa files etc that you can modify to prevent suspension, but I have yet to find a way to do so using only alsa.
On the old server I use to use “beep”, but it no longer works on some of the newer motherboards and my Gigabyte Z790 appears to be one of them.
I never thought I would say this, but sound is one area Windows is handling things much better than Linux. Image may be NSFW.
Clik here to view.
Statistics: Posted by dhunt2206 — 2024-02-26 15:20
