Welcome, Guest. Please login or register.

Login with username, password and session length


Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - FaberAST

Pages: [1] 2 3 ... 22
SignalScope / Re: upgrade IOS to 13.3 kills SignalScope
« on: January 31, 2020, 10:35:47 AM »
Unfortunately, iOS 13 broke compatibility with legacy versions of our apps. End of support for these apps was announced in January, 2018 and they were removed from sale on the App Store in July, 2018. At that time (when iOS 11 was current), we could not have known that Apple would break them in iOS 13.

Please understand that the apps you purchased still work just fine on the versions of iOS they were developed for and you can continue to run them on compatible devices.
If you have a device running iOS 12 or earlier, you can re-download the original app you purchased from your App Store account.

If you need to always be able to run SignalScope on the newest versions of iOS, we recommend that you download SignalScope X and choose a subscription option that best meets your needs (the Advanced Tool Set most closely matches the functionality of the old SignalScope Pro).

In case you prefer to avoid subscriptions, we still offer new perpetual license versions of our products for those who need them (with the understanding that they will also be retired and replaced at some point, as the old apps were).

Unfortunately, since our app distribution must go through the App Store, we cannot offer discounted upgrades for purchases of our earlier apps, which is largely why we moved to a subscription model for our software.
A note about SignalScope X’s auto-renewable subscriptions

SignalScope Pro / Re: IOS 13 breaks Signal Scope Pro
« on: September 30, 2019, 12:09:50 PM »
The end of support for the legacy version of SignalScope Pro was announced in January of 2018. The final update was published in March, 2018, and the app was removed from sale on the App Store in July, 2018.
Faber Acoustical Releases SignalScope X for iOS as a Free Download

Current alternatives:

Free Download + Subscription:
SignalScope X

Perpetual License
SignalScope Pro 2018
SignalScope Advanced 2018

The Advanced Tool Set subscription in SignalScope X and SignalScope Advanced 2018 most closely match the functionality of the old SignalScope Pro.

Subscriptions are recommended for anyone who plans to always run SignalScope on the latest version of iOS.
Perpetual license versions are recommended for those who need to run SignalScope as a dedicated instrument. This means on a device dedicated for measurement/analysis/data acquisition that can continue to serve its purpose indefinitely without the need to upgrade iOS. (Of course, upgrading iOS is fine in this case, as long as it is supported by the perpetual license version of the app.)

SignalScope / MOVED: Triggering
« on: December 17, 2018, 08:44:29 PM »

SoundMeter / Re: Calibrate MicW i437L
« on: October 01, 2018, 06:29:07 PM »
According to MicW's current instructions, you should set the device gain to Mid and the device units to FS. Then, set the sensitivity for the input channel according to the value that was written on the sheet that came with your i437L (e.g. 19.9 Pa/FS). (Make sure input channel units are set to Pa.)

We just tested this, today, with an iPhone X and XS Max, and the results agreed within 0.1 dB of a 94 dB field calibrator on both devices.

Keep in mind that the sensitivity given by MicW is valid for the Mid gain setting, only. If you want to measure higher or lower SPLs which would require Low or High gain, respectively, you would need to perform a calibration at the chosen gain.

SignalScope / Re: Frequency Measurement
« on: September 25, 2018, 07:02:25 PM »
It's true that there are no physical knobs for adjusting the Oscilloscope display.

Perhaps, you have already found that if you look in the Display tab of the drawer on the bottom side of the Oscilloscope window, you'll see the software controls for adjusting the amplitude (Vert) and time (Horz) scale of the scope.

Frequency measurements can be made with the Oscilloscope, using the dual data cursors, but it would be easier to measure frequencies with the FFT Analyzer. However, if you need very fine precision, it may be better to use the Oscilloscope.

Hello Martijn,

Which MicW model are you using? Which version of SoundMeter?

If you are not seeing the option to select between FS and V for the device, that suggests that your MicW is either not connected properly, or that you have the built-in mic selected as the current input device. (FS stands for Full Scale, which is the maximum digital value that can be represented by the input hardware.)

If you think it will help, you are welcome to attach or send screenshots that illustrate the problem you are experiencing.

Best regards,

Ben Faber

SoundMeter X / Welcome to the SoundMeter X discussion
« on: March 21, 2018, 04:33:53 PM »
SoundMeter X, the successor to SoundMeter and SoundMeter Pro, is available as a free download from the App Store and offers subscription-based upgrades for sound analysis and data logging.

See our note about moving to subscriptions on the blog.

SignalScope X / Welcome to the SignalScope X discussion
« on: January 10, 2018, 03:17:36 PM »
SignalScope X, the successor to SignalScope and SignalScope Pro, includes a free oscilloscope and subscription-based tool sets to meet your more serious needs.

See our note about moving to subscriptions on the blog.

SoundMeter / Re: Calibrate MicW i437L
« on: November 27, 2017, 04:50:01 PM »
Unfortunately, the i437L presents itself as if it were a standard headset jack. This means that apps like SoundMeter cannot automatically distinguish between an i437L and a standard headset jack.

Your approach is correct (i.e. Device Units = FS, Channel Units = Pa, Gain = Mid). We do not know the precise input gain used by MicW when testing the sensitivity of the i437L, but using the Mid gain setting in SoundMeter seems to work well.

It's too bad MicW didn't take advantage of the opportunity to produce a digital microphone that presented itself uniquely to iOS. That would have allowed automatic loading of sensitivity information, similar to what SignalScope does with the Digiducer digital accelerometers.

SignalScope / Re: RTA Averaging
« on: November 16, 2017, 10:05:20 PM »
Yes. With those settings, you'll get the average sound level over 20 seconds in each whole or 1/3 octave band, plus an overall (full bandwidth) average level. You can see the overall level by tapping the graph to turn on the cursor.

SignalScope / Re: RTA Averaging
« on: November 16, 2017, 08:45:38 AM »
Based on your description, I would recommend that you look in the Octave Analyzer options menu and set Level Type to Leq, turn on Auto Stop, and set the duration to 20 seconds.

SignalScope / Re: RTA Averaging
« on: November 07, 2017, 03:39:50 PM »
What would you like to do with averaging?

SignalScope / Re: RTA Averaging
« on: November 01, 2017, 02:46:45 PM »
In SignalScope, you'll see an info button (a little 'i' in a circle) on the right side of the toolbar at the top of the screen. Tap that, and then tap on Help.

SignalScope / Re: RTA Averaging
« on: October 30, 2017, 06:10:15 PM »

The Octave analyzer tool (RTA) supports both exponential (Lp) and linear (Leq) averaging of the signal in each whole or 1/3-octave frequency band. For exponential averaging, Fast, Slow, and Impulse time weightings are supported. For linear averaging, the average level is calculated over the entire duration of the measurement.

SignalScope's built-in documentation includes information on how to access the averaging options.

Let us know if you have more questions.

Electroacoustics Toolbox / Re: Basic setup guide
« on: April 27, 2017, 06:46:29 PM »

If you are trying to perform dual-channel measurements (e.g. frequency or impulse response), I would point you to the tutorial on the blog for reference.
Frequency Response Measurement with Electroacoustics Toolbox 3

Why can't you use the output of the Duet to use the built-in test signals? Perhaps, a more detailed description of what you are trying to do, and how you would like to set it up, would help us zero in on a suitable solution.


Pages: [1] 2 3 ... 22