Moderator: Redaktörer
dewpo skrev:Om du väljer UMIK, vilket jag inte skulle gjortSå rekommenderar jag att använda externa mätfiler med akustisk triggar signal.
MSO skrev:Caution: Measurements Taken With USB Microphones Require An Acoustic Timing Reference
Time-synchronized measurements with a USB microphone can only be done using Room EQ Wizard version 5.15 or greater, with its "acoustic timing reference" feature. For all other known measurement software, time-synchronized measurements with a USB microphone are not possible. Those familiar with HolmImpulse might be tempted to try HolmImpulse's "time locking" feature to work around this problem, but that workaround fails. The reason is described in the HolmImpulse section below.
MSO skrev:Using HolmImpulse With The Time-Locking Feature (Windows Only)
Another option for measurements using Windows-based systems is the HolmImpulse freeware. Unfortunately, the HolmImpulse documentation tends to be theoretical in nature and doesn't include much information about how to actually use the software. A worthwhile source of information for learning HolmImpulse is the HolmImpulse tutorial at the Parts Express forum.
HolmImpulse uses a single-input, single-output approach that nonetheless can achieve time-synchronized measurements using the so-called "time locking" feature. The diysubwoofers.org site has a very good step-by-step procedure for using the time-locking feature. A word of caution is in order regarding HolmImpulse and time-locking. When used with sound cards having clocks that are not locked to one another on the record and play sides, the timing reference will shift from one measurement to the next, causing them to be non-time-synchronized and thus unusable with MSO. To find out more about how time-locking can fail in HolmImpulse, see the "Holm Impulse - Timelock, creeping offset?" thread at the Parts Express forum. That thread contains a description of a test that can be run to determine if your sound device is compatible with time-locking. It also contains an explanation by Bill Waslo, author of the Dayton OmniMic measurement software, of the clocking issue as it relates to the potential failure of time-locking in HolmImpulse.
If the clocks on the record-side and playback-side sound devices are not locked to one another, then as Bill Waslo states in the "creeping offset" thread, the time locking cannot work. With that information, it can be seen why using a USB microphone will cause HolmImpulse time-locking to fail. The USB microphone contains an internal A/D converter, so the converter's clock must be contained within the microphone itself. An analog or digital signal from the computer's sound device supplies the input signal to the device under test in this configuration. This signal's clock is internal to the computer itself or in an attached external sound device, so the record and playback clocks are physically different and can't possibly be locked to one another. This will cause time-locking to fail. A similar situation will occur if one attempts to use HolmImpulse time-locking with HDMI supplying the measurement source signal.
It should also be pointed out that these failures of time-locking won't be flagged by the software. In order to find them, you'll need to look for them by performing multiple measurements and checking for consistency.
Dirac skrev:1.4. Avoid any combination of microphone and sound cards?
In general, it is difficult to say how different hardware and their driver software will work together on a computer system. It usually depends on how well they comply with standards. Simultaneous use of two USB audio devices must be through different USB controllers to work properly. Therefore, make sure to have a different USB controller for each USB audio device that will be used at any time.
DanNorman skrev:Jag fattar ärligt taligt inte grejen. Spara några hundra på en usb-mikrofon och aldrig kunna vara säker på mätresultaten?
Skaffa Windows, ett tvåkanaligt ljudkort med minst en kanal med fantommatning och en bra mikrofon och lite sladdar.
Tangband skrev:Angående ljudkort med så säger en test i audiosciensereview att denna är outstanding för priset:
https://www.audiosciencereview.com/foru ... 04hd.1658/
Tangband skrev:Angående ljudkort med så säger en test i audiosciensereview att denna är outstanding för priset:
https://www.audiosciencereview.com/foru ... 04hd.1658/
Johan_Lindroos skrev:Tangband skrev:Angående ljudkort med så säger en test i audiosciensereview att denna är outstanding för priset:
https://www.audiosciencereview.com/foru ... 04hd.1658/
Ööööh...
Att mäta spektrum på en ton och så mättes en annan ton en annan gång säger ju typ... ...ingenting.
Tangband skrev:Johan_Lindroos skrev:Tangband skrev:Angående ljudkort med så säger en test i audiosciensereview att denna är outstanding för priset:
https://www.audiosciencereview.com/foru ... 04hd.1658/
Ööööh...
Att mäta spektrum på en ton och så mättes en annan ton en annan gång säger ju typ... ...ingenting.
Nej det var ju inte så många mätningar,- men om du scrollar ned och läser kommentarerna så fortsätter han mäta med 4-5 andra mätsignaler samtidigt som hans läsare frågar vad de vill se för mätningar.
Enheten verkar ha ganska låg utnivå.
dewpo skrev:Om du väljer UMIK, vilket jag inte skulle gjort![]()
Så rekommenderar jag att använda externa mätfiler med akustisk triggar signal.
Det fungerar bra i senaste REW betan,
REW skrev:Measuring with a timing reference
REW can make use of a timing reference when it measures, according to the setting on the measurement panel or in the Analysis preferences. The timing reference selection controls whether REW uses a loopback on the soundcard as a timing reference, or an acoustic timing reference, or no reference. Using a timing reference allows REW to eliminate the variable propagation delays within the computer and soundcard so that separate measurements have the same absolute timing.
If a loopback is selected the reference channel signal must be looped back from output to input on the soundcard and measurements will be relative to the loopback timing. Usually this means measurements will have a time delay that corresponds to the time it takes sound to travel from the speaker being measured to the microphone.
If an acoustic timing reference is used REW will generate a timing signal on the output that has been selected to act as the reference before it generates measurement sweeps on the channels being measured. The level of the timing reference is set separately from the measurement level using the control at the top of the measurement dialog. The timing signal is a high frequency sweep to allow accurate timing, a subwoofer cannot be used as the reference channel. Measurements will have a time delay that corresponds to the difference in their distance from the microphone compared to the distance of the reference speaker - if the reference speaker is further away the delay would be negative. When an acoustic timing reference is used individual measurements taken from the same mic position will have the same relative timing, allowing trace arithmetic to be carried out on the traces in the All SPL graph. Note that multiple sweeps cannot be used when using an acoustic timing reference.
If using a timing reference REW can calculate the delay through the system being measured relative to the reference and show it in the measurement Info panel as "System Delay" in milliseconds, with the equivalent distance in feet and metres shown in brackets. For speakers the delay estimate is based on the location of the peak of the impulse response. Subwoofers have a broad peak and a delayed response due to their limited bandwidth so the delay is instead measured relative to the start of the impulse response. The start of the impulse response cannot be located as precisely as the peak, however, so delay values are less accurate for subwoofer measurements.
Multi-Sub Optimizer skrev:Caution: Measurements Taken With USB Microphones Require An Acoustic Timing Reference
Time-synchronized measurements with a USB microphone can only be done using Room EQ Wizard version 5.15 or greater, with its "acoustic timing reference" feature. For all other known measurement software, time-synchronized measurements with a USB microphone are not possible. Those familiar with HolmImpulse might be tempted to try HolmImpulse's "time locking" feature to work around this problem, but that workaround fails. The reason is described in the HolmImpulse section below.
SAC skrev:Using a loopback for timing reference is NOT the same thing as calibrating the frequency response of the soundcard.
REW can also be used for time domain measurements.
If you are intending to use REW in order to evaluate specular reflections, the arrival times of the direct signal and the indirect signals are important.
The problem arises in that the test signal does is not processed in zero time - there is some hardware propagation delay inherent in the hardware setup.
In order to eliminate this, a hardware loopback is used in the 2nd channel (typically the Left channel to connect Left out with Left in) to provide a reference for the delay in signal propagation that is then 'subtracted' from the timing of the actual test signal data received from the mic.
In this way the actual "time of flight" of the test signal from speaker to mic can be determined.
If all you are doing is making frequency response measurements (rather a waste of the capabilities of the platform), you do not need this feature. But if you are intending to move beyond the simple generation of frequency responses, you will need to know what the characteristics of the various direct and indirect signals are that interact (superpose) and that cause destructive interference in the frequency response.
Above the modal frequencies (actually above ~80 Hz), the frequency response is comprised of the interaction of non-minimum phase interaction of various direct and indirect energy arrivals, and EQ is NOT a valid method to correct for frequency domain anomalies, and this behavior must be viewed and treated in the time domain.
And for this, the ETC response is required. And for accurate time of flight values, the hardware loopback correction must be used in order to remove and compensate for the hardware propagation delay that is added to the measured time. (Note: In Preferences-> Analysis: "Use Loopback as timing reference" MUST be checked; and also "Set IR peak to T=0" must NOT be checked - as it is of no value anyway as it deletes the initial Time of Flight of the direct signal and ignores the hardware loopback correction!)
Thus the best advice I can give is to use the loopback correction by default. Then, when and if you do desire to convolve and view the time domain aspects of your measurements, the time values will be valid in the time domain.
Beakungen skrev:Om man som jag enbart är ute efter att mäta basen neråt. Dvs från 3-400hz och neråt och främst använda detta till att rätta till basen något. Det ska vara så enkelt som möjligt att använda. Skulle umik och rew funka då?
Användare som besöker denna kategori: Inga registrerade användare och 9 gäster