- Thread Starter
- #81
All g, my illustrious brothaSorry you're correct this uses toroidal transformers
All g, my illustrious brothaSorry you're correct this uses toroidal transformers
Just the frequency range, I think. Yours goes down to DC mine to 20 Hz.Why do I get a different one?
View attachment 357727
(that's after the 25 sec where the buzz is audible)
We have very different levels,mine is some 30db lower.Just the frequency range, I think. Yours goes down to DC mine to 20 Hz.
Good call. The bold horizontal line is 100 Hz, so, yup, peak at 60 Hz.Using @mhardy6647's image and frequency analysis I am going to call this one at 60 Hz fundamental.
View attachment 357730
Just a bit, then I cropped out (so to speak) the non-noisy part and focused on a few seconds where it is relatively loud. The y-axis is arbitrary to my "record level" and not normalized to anything meaningful. I was simply looking for Gestalt.We have very different levels,mine is some 30db lower.
Is it the whole video you captured or the buzzing only as I did?
That's the thing with not having a proper oscilloscope to view and maybe even a frequency counter the waveform in the noise sample makes it difficult to acquire the waveform duration details.Good call. The bold horizontal line is 100 Hz, so, yup, peak at 60 Hz.
Do you have a option available for logarithmic scaling? That is better I think.I tried Adobe Audition on a portion between seconds 31 and 34 of the sample. Looks like this:
View attachment 357738
The freq bandwidth analysis output is better although something is preventing the peak value from being indicated as a larger dB value at the fundamental frequency of 60 Hz. To the degree that the curve is distorted and not accurate.
I'll be back to do a more accurate sample soon... make 20 minutes. stay tuned, this is very interesting....The freq bandwidth analysis output is better although something is preventing the peak value from being indicated as a larger dB value at the fundamental frequency of 60 Hz. To the degree that the curve is distorted and not accurate.
Well, I've got a scope (several ) and I do know how to use 'em -- but it was easier to point and click, you know? Even though I don't really know the more subtle ins and outs of Audacity. I am a brute force user of the s/w.That's the thing with not having a proper oscilloscope to view and maybe even a frequency counter the waveform in the noise sample makes it difficult to acquire the waveform duration details.
I'll be back to do a more accurate sample soon... make 20 minutes. stay tuned, this is very interesting....
I have had this happen in my Audio Design CareerBtw ... As long as this mysterious phenomenon isn’t fully understood, better don’t allow any folks with cardiac pacer anywhere near that »beaming« device
I think what is required is to get a fresh sample with the present settings and make the sample that is derived from the peak of a waveform. That should result in success.I have to admit that I’m not familiar with this at all ...
Playing around with the »FFT Size«, i. e. enlarging it, leads to results like this:
View attachment 357744
Here is a better sample video, tome starting about 1:09, and I go through it twice on each driver.Can you zoom in for more resolution of the waveform timing details. What we need is the time interval for a complete 360 degrees of the distorted sinusoidal waveform and that time duration will give us the frequency.... 1/T = F
PostedI think what is required is to get a fresh sample with the present settings and make the sample that is derived from the peak of a waveform. That should result in success.