- Thread Starter
- #2,061
That's fine. It skips any steps in log sequence that would be less than 1Hz.And another,after 0hz where says 1/21 jumps at 2Hz saying 4/21 without 2/21 and 3/21.
That's fine. It skips any steps in log sequence that would be less than 1Hz.And another,after 0hz where says 1/21 jumps at 2Hz saying 4/21 without 2/21 and 3/21.
This is still OK. The question is, does it finish? There's not much room to do a log sweep between 0 and 31Hz, so only a few measurements will fit in that space. Those that are too close to each other will be skipped, so jumping from 1 to 9 isn't unexpected.
No,it only jumps from 1 to 4.This is still OK. The question is, does it finish? There's not much room to do a log sweep between 0 and 31Hz, so only a few measurements will fit in that space. Those that are too close to each other will be skipped, so jumping from 1 to 9 isn't unexpected.
Hmm, strange. Seems to work differently for me with exactly the same settings. I'll do another quick check, but I think that's an extreme case that isn't worth spending too much time on.No,it only jumps from 1 to 4.
From then on measures 2Hz,finishes and starts over at 2 Hz until 21.
It measures 2Hz 16 times and every time it finishes.
It doesn't measure anything else.maybe it likes 2Hz.
Ok,cleaned up everything and now measures 2Hz until step 20 (from 21) where it jumps to 26Hz and then to 31Hz which is the selected end freq.Hmm, strange. Seems to work differently for me with exactly the same settings. I'll do another quick check, but I think that's an extreme case that isn't worth spending too much time on.
No,it only jumps from 1 to 4.
From then on measures 2Hz,finishes and starts over at 2 Hz until 21.
It measures 2Hz 16 times and every time it finishes.
It doesn't measure anything else.maybe it likes 2Hz.
That sounds like a noisy result. When measuring sweeps, MT can skip a number of measurements that seem noisy. I think I’ll disable that, and just display whatever result is measured.The behaviour is exactly the same when I'm measuring the crosstalk with just one channel:
It tries 40 Hz over and over again:
Eventually it manages to get the measurement at the higher frequencies and plots it.
There are a lot of skipped frequencies on the plot when it's ready.
This is because of the "No signal" -detection and when MT doesn't get the strong enough signal, it just tries again when sweeping.
I think that this is actually a bug because it should jump to the next frequency and not just repeatedly try the same one again and again.
Actually I'm not even sure if it just prints the wrong frequency during the sweep or actually measures the wrong frequency.
It would be ok to try the same signal again too if the previous result is not ok , but then it shouldn't increase the sweep counter.
@pkane could the "No signal" detection be disabled on the settings when needed? Sometimes I'll have to use the second channel with full signal just to get past the "No signal" -detection and then hide the second channel plot when the measurement is ready. Disabling the limiter would make some measurements much easier.
That sounds like a noisy result. When measuring sweeps, MT can skip a number of measurements that seem noisy. I think I’ll disable that, and just display whatever result is measured.
Thanks!
Is your "Noisy signal" -detector different than the famous "No signal" -detector? When doing the crosstalk measurements the signal is still clear (Especially at 1 kHz), but it's level is under the "No signal" detection threshold.
Different.
To promote peace and harmony, and in the interest of relaxing some of the remaining hard limits in Multitone, I've changed the sweeps to:
https://app.box.com/s/qbrh3czrvudclkqs9n8lm806k3hzmjx5
- Not to skip measurements, no matter how noisy
- Not to skip log-based frequency measurement if the previous one was more than 0.1Hz away from this one
- @Blumlein 88 : also please check the level meter jumps below 5Hz. Do you still see them?
You can see some of this reflected in this sweep:
View attachment 232419
FM fc/fm/fd
fc = carrier frequency
fm = modulation frequency
fd = deviation span frequency
FM 1k/200/900
FM 1k/40/10k
FM 500/20/500
I don't know what it does to amps but E-MU seems to like it.For anyone interested, I updated v1.0.49 to generate frequency-modulated test tones, per @pma 's idea for amplifier testing. This can be used in place of multitones, and is a better test signal than even the decorrelated/crest-optimized multitones. This isn't good for testing frequency response, but to look at distortions and noise-floor modulation, this can be hard to beat:
https://app.box.com/s/qbrh3czrvudclkqs9n8lm806k3hzmjx5
There are no FM test tones in the list, but you can type one in directly. Just type this, replacing the three frequencies with the desired numbers:
FM fc/fm/fd
fc = carrier frequency fm = modulation frequency fd = deviation span frequency
For example, to use Pavel's test tone of 1kHz carrier, 200Hz modulation frequency and 900Hz deviation, you'd type:
FM 1k/200/900
As simple as that. You can alter any of the frequencies, of course. For example, to get a set of about 300 test tones spanning 40Hz to a 11kHz, enter this:
FM 1k/40/10k
And of course, you can alter the carrier center frequency to anything desired. For example:
FM 500/20/500
Curious to see what results others will get. Be careful feeding a 0dBFS signal directly into the amp, though, as it is likely to clip or overload due to the low crest factor in this test signal. You can always adjust the Play Gain to lower the level.
View attachment 232636