Welcome, Guest. Please login or register.

Login with username, password and session length
 

News:



Recent Posts

Pages: 1 ... 7 8 [9] 10
81
Electroacoustics Toolbox / Re: Room Analyzer - best practice?
« Last post by gwarder on February 06, 2014, 01:35:48 PM »
One last point for now....I took another sample three minutes later and changed nothing on the setup. The results seem fairly different....and lots more "N/A"s on the chart.

This is a sanctuary where a starter's pistol excitation takes 3-4 seconds to decay....and in the countryside to the noise floor is pretty quiet.
82
Electroacoustics Toolbox / Re: Room Analyzer - best practice?
« Last post by gwarder on February 06, 2014, 01:23:17 PM »
After a restart, I do see signal and can capture some data (the excitation still doesn't stop on its own).

However, the numbers aren't making sense so I'm wondering if there's something wrong with the sample. I am getting NOTHING for C80 (just N/A) and the only C50 measurement is @ 63 Hz.

I need C80 at 500, 1k and 2k, RT60 at 125, 250, 500 and 1000, and EDT at 500, 1000, 2000 and 4000 for the paper I'm writing.
83
Electroacoustics Toolbox / Re: Room Analyzer - best practice?
« Last post by gwarder on February 06, 2014, 12:55:56 PM »
gwarder,

Quote
Next created a Dual FFT Analyzer. In the bottom drawer I set the source to the appropriate Apollo 16 input. Under the "Excitation" tab, I Selected the appropriate output channel...sine sweep...Logarithmic. I left all other settings at default.
Did you select the same (excitation) output channel for the Reference input (next to the Source input selection)?

Yes I have. Both my excitation output and my Live Input reference are set to Output 10 on the Apollo 16.

Quote
Next I selected Control->Start All Tools. I confirmed that I could hear the repeating excitation signal in the room and that the mic was picking it up. While the excitation signal was in progress, I selected Control->Capture all Data. Then I stopped all tools.
If you have any other tools in your project, I would recommend just starting and stopping the DFFT Analyzer directly, rather than all tools simultaneously. Also, for room measurements, you might want to set the averaging type to Linear and let the analysis complete (and stop on its own) before you capture the data. (The default number of averages, 10, may be overkill, but it won't hurt your measurement.)

I'm not sure I know what you mean by "waiting for the analysis to complete (and stop on its own). Once I start the Dual FFT, it just runs. The excitation signal continues until I stop the tool. I did let it run for two minutes before stopping it. Should I wait longer? Seems like 10 repeats should happen much more quickly.

At which point do I click on "Capture Data?" While the excitation is running? After I stop the tool? I've tried both and I'm just getting an empty graph.

Quote
Also, before capturing the data in the DFFT Analyzer, I would recommend that you inspect your measurement data to be sure it looks right. If you are familiar with ETC or squared impulse response curves, I would recommend that you select the Squared IR function in the Display tab and make sure you see the kind of acoustic decay you would expect in your measurement. If you don't have valid measurement data in the DFFT Analyzer, you can't expect to get meaningful results when you load it into the Room Analyzer.

The Coherence function can also be used to verify the quality of your measurement, as a function of frequency. A coherence of 1 is ideal. The smaller the coherence, the less meaningful your data is at a particular frequency.

Ben
84
Electroacoustics Toolbox / Re: Room Analyzer - best practice?
« Last post by FaberAST on February 06, 2014, 10:57:18 AM »
gwarder,

Quote
Next created a Dual FFT Analyzer. In the bottom drawer I set the source to the appropriate Apollo 16 input. Under the "Excitation" tab, I Selected the appropriate output channel...sine sweep...Logarithmic. I left all other settings at default.
Did you select the same (excitation) output channel for the Reference input (next to the Source input selection)?

Quote
Next I selected Control->Start All Tools. I confirmed that I could hear the repeating excitation signal in the room and that the mic was picking it up. While the excitation signal was in progress, I selected Control->Capture all Data. Then I stopped all tools.
If you have any other tools in your project, I would recommend just starting and stopping the DFFT Analyzer directly, rather than all tools simultaneously. Also, for room measurements, you might want to set the averaging type to Linear and let the analysis complete (and stop on its own) before you capture the data. (The default number of averages, 10, may be overkill, but it won't hurt your measurement.)

Also, before capturing the data in the DFFT Analyzer, I would recommend that you inspect your measurement data to be sure it looks right. If you are familiar with ETC or squared impulse response curves, I would recommend that you select the Squared IR function in the Display tab and make sure you see the kind of acoustic decay you would expect in your measurement. If you don't have valid measurement data in the DFFT Analyzer, you can't expect to get meaningful results when you load it into the Room Analyzer.

The Coherence function can also be used to verify the quality of your measurement, as a function of frequency. A coherence of 1 is ideal. The smaller the coherence, the less meaningful your data is at a particular frequency.

Ben
85
Electroacoustics Toolbox / Room Analyzer - best practice?
« Last post by gwarder on February 06, 2014, 10:34:27 AM »
I am having a great deal of difficulty getting any real results. So I'd like to start by ruling out "user error" as I am fairly new to this.

My goal is to measure a church where I have recorded a choir/organ ensemble. The end result is for a Masters paper I'm writing.

To measure the room, I have placed an AKG C414 XLIIS in omni mode about 10' up and slightly behind the conductor's position (same place I set the mic array). The mic went into a Millennia mic pre, then to an Apollo 16 interface, finally into a Mac laptop. The Apollo interface also fed a monitor speaker placed in the centre of the choir. This was for the excitation signal.

On launching Electroacoustics Toolbox, I opened Device I/O and selected (and started) the Apollo 16 interface.

Next created a Dual FFT Analyzer. In the bottom drawer I set the source to the appropriate Apollo 16 input. Under the "Excitation" tab, I Selected the appropriate output channel...sine sweep...Logarithmic. I left all other settings at default.

Next I selected Control->Start All Tools. I confirmed that I could hear the repeating excitation signal in the room and that the mic was picking it up. While the excitation signal was in progress, I selected Control->Capture all Data. Then I stopped all tools.

Next I created a Room Analyzer and selected the captured measurement. There are LOTS of n/a boxes in the analysis. Nothing captured in C80, nothing for 4 areas of C50, NO T60 measurements, several bands empty in T20 and T30. Nothing for D80 and 4 blanks for D50. The T measurements that I did get are quite different from a sweep done with "FuzzMeasure" and all seem extremely short.

This is a sanctuary that has a fairly low noise floor (lights, fans and organ turned off during measurement), and a "starter pistol" excitation produces a decay that lasts roughly 4-5 seconds to the naked ear.

I'm wondering what is wrong in my setup. Mic position? Polar pattern? Something in the excitation?

Thanks!
86
Electroacoustics Toolbox / Re: SNR, THD & THD+n dissapeared in Version 3.4.2 (1348)
« Last post by AudioFixer on February 06, 2014, 04:22:57 AM »
Silly me.... all is OK
87
Electroacoustics Toolbox / Re: SNR, THD & THD+n dissapeared in Version 3.4.2 (1348)
« Last post by FaberAST on February 05, 2014, 12:12:23 PM »
SNR requires that one of the cursors be turned on. THD measurements require a cursor, plus at least 1 harmonic cursor.
88
Electroacoustics Toolbox / SNR, THD & THD+n dissapeared in Version 3.4.2 (1348)
« Last post by AudioFixer on February 03, 2014, 02:58:37 AM »
In FFT Analyzer Signal measurement options the SNR, THD And THD+n are selectable in analyzer options but does not display any values.
89
Electroacoustics Toolbox / Re: Stops measuring after upgrade to OSX 10.9
« Last post by H3nry on January 27, 2014, 07:00:02 PM »
It is certainly much better. Memory usage is much reduced, but there is a slow creep upward. With Meter Bridge, XY Plotter, O'scope, and Octave Band windows running, memory started out a bit under 43MB and has gradually crept up to 111MB after an hour. Interestingly, for half that time the Toolbox windows were covered by other applications, and so not redrawing though Toolbox was running, and for that period no memory increase occurred. At the moment, there is no audio signal input, so meters aren't "moving" but memory is still ticking upward (meter windows are visible).

OS X 10.9.1, Mini with Core i7 and 16 GB RAM. Same behavior on 2009 Mini with Core Duo and 8 GB. Doesn't seem to be related to the audio interface in use, same with built-in I/O as external USB interfaces.
90
Electroacoustics Toolbox / Re: Stops measuring after upgrade to OSX 10.9
« Last post by FaberAST on January 27, 2014, 01:59:39 PM »
H3nry,

Version 3.4.2 addresses two issues that could potentially lead to excessive memory use. I would be interested to know if this version solves the issue you have been having.

Ben
Pages: 1 ... 7 8 [9] 10