Audio Analyzer Suite - New Version Available - 1.0.0.76

New version of the Analog Discovery Audio Analyzer Suite is available for download.
Note: This software requires Analog Discovery (1 or 2) plus latest version of the Waveforms software to run.
This software is for Windows only, tested on Windows 7 and Windows 10.
New features include measurement of Preamps and RIAA phono stages, including input impedance and capacitance.
Plus other minor changes and bug fixes.
WARNING: If you live in a place where the number format decimal separator is comma instead of a dot then the software will not operate correctly. (Thanks to
Rüdiger Hoppe for reporting this)
Download here:
www.dropbox.com/sh/w3r2wycgdo...
Click the Download button in top right corner and select direct download.

[@RapperBC]

Many many thanks for writing this excellent software, and especially for making it available to all of us. You rock.

[@georgeswanson9483]

Thank you very much for taking the time to make this video and make the software available for us hobbyists to use, it is greatly appreciated.

[@PeterRidge]

Thanks for the update and providing demos of the new features.

[@fpliuzzi]

Thank you for the feature additions.

[@docholliday3150]

Great update and explanation. Thank you for the effort. Looking forward to exploring this.

[@cranegantry868]

Very nice, thank you for doing this.

[@Biky750]

A huge thank you for this and everything you give to the world

[@fernarias]

Amazing, thank you for the update.

[@Blueglow]

Awesome news! Thanks for the update.

[@materialsguy2002]

Thanks for the updated version. 👍

[@ViorelDehelean]

Thanks for the Phono section :)

[@EngineeringVignettes]

Nice set of updates, thanks!

[@richardmelville5973]

Thank you for a most wonderful tool.

[@timnixon8354]

Very nice feature additions.

[@johndooley2401]

Thank You, Great Stuff

[@curtislucka9954]

Just getting updated. Building test jigs. Have a few phono and regular preamps to test. Thanks for this tool!

[@TheStuffMade]

Have fun, leave a comment if you run into any issues. Thanks

[@curtislucka9954]

@@TheStuffMade Hello. Ran some tests with the jigs on a Cambridge Audio 640P phono preamp. Impedance readout looks good as expected (48.5K, 133pF); however, FR appear rolled off on the low and high end. I increased the 47nF cap to 1uF. This gave me a flat low end but still rolled off at the high end. I also ran FR on an LM4562-based preamp that is flat to +400kHz, but here is flat to around 5kHz and then gradually rolls off (RIAA turned off). Could you explain a bit more what the purpose of the 47nf cap is - it influences the FR but I am sure for a good reason. I may be doing something wrong. I am looking forward to using the other features on a few power amps. Thanks again!

[@TheStuffMade]

Hi @@curtislucka9954 , make sure you use the calibrate feature on the jig before doing the frequency response measurement, it will compensate for the frequency response of the test jig. The resistor/capacitor jig is only meant for phono stage measurements, it's basically to attenuate the AD's outputs and compensate a bit for the ~60dB (1000x) gain at 20kHz in RIAA preamps since the AD is limited to 14 bits resolution. When you measure a normal line level preamp, just connect it directly to the ADs outputs and inputs for best results, but you should still use the calibrate feature as the AD is not 100% flat. Hope this helps, Jake

[@curtislucka9954]

@@TheStuffMade Thanks Jake. Makes total sense and it works fine that way. I have another phono and several other regular preamps to try out. Impedance measurements have always been the challenge based on what I have and this tool is great. I know you have other impedance capabilities here and will look forward to trying them out. IMD distortion also.

[@CraigHollabaugh]

Great work.

[@dinochan1]

Thanks

[@neilsmith1826]

Hello, first thanks for your tremendous efforts here. I'm just starting out with measurement of phono stages, I do not understand the relationships between the input impedance and the series resistor and capacitance level fully. I want to measure a scenario where a MC cartridge and a phono stage with input impedance 100 Ohms. Could you suggest values for the capacitor and resistor, or at least direct me to a source of material where this is explained? Thanks in advance for any advice you can share.

[@JaqUkto]

Hi! I’m using your analyzer and wish to thank you very much for it! We appreciate your work! It is used all over the net and highly valued at channels of Skunkie Design Electronics, Gabster and others. Could I kindly ask you to complete the documentation and if possible make the reports function.

[@cowasakiElectronics]

Thank you for this software. I found out about it from Blueglow Electronics channel. I bought the AD2 and it is really helpful. If I wanted to test 5m lengths of speaker cable what setup would you use with the suite? Once again, thanks for doing this it is brilliant.

[@TheStuffMade]

Thanks, much appreciated. Do you mean 5 meters of cable between the amplifier and the load or 5 meters to the AD2? I'd recommend to keep the load close to the amplifier you are testing, it will be more accurate that way without the added resistance in the wire, but you can make the connection from the amplifier to the AD2 5 meters long without any issues. Cheers, Jake

[@cowasakiElectronics]

@@TheStuffMade no it’s to look at the difference between different cables. So hooking up ten different 5M lengths of cable and seeing how they compare.

[@TheStuffMade]

@@cowasakiElectronics Ah I see, well for something like this I'd measure the impedance, capacitance and inductance of the cables for comparison. I doubt you'd be able to see any difference in frequency response within the audible range. Check out my Impedance Analyzer project for a solution to use the AD to do these measurements. Cheers, Jake

[@cowasakiElectronics]

@@TheStuffMade Thanks, I will do

[@neilsmith1826]

Thanks for your explanation, I'm still learning about phono stage testing. I wonder if you would be willing to offer attenuation resistance and capacitance value for a phono stage set for MC with 100 Ohm input impedance?

[@TheStuffMade]

Hi Neil, I think I'll do a quick update video on how to test phono stages, including MC stages, within the next few weeks. I have an improved method but it does require a few diagrams and some explanation so I better do it in a video. Cheers, Jake

[@neilsmith1826]

@@TheStuffMade That really would be great. I appreciate your time and advice.

[@carlosbeltran9216]

I've been having an issue that started happening recently. I made a jig for power amplifier measurements with the 10K resistor network as you suggested and has been working nicely measuring my collection of vintage receivers and amplifiers but all of the sudden all measurements are clipping the input on the amplifiers. I measure around 10V peak to peak on Wavegen 1 when the measurements run (Like THD+N vs Frequency). Even when the jig is disconnected it's measuring 10V peak to peak. Any ideas?.

[@TheStuffMade]

Hi Carlos, I recommend you try do a measurement using your jig, but without any amplifier connected, as in just connect output to input and see what happens. I think likely it's a bad connection somewhere. The way the software works is that it will do a short gain test before running the distortion measurement, so it's likely the AD saw very little signal coming back and then it adjusts the output to maximum. I should probably add some safety like a configurable maximum output or give a warning in the next version. Cheers, Jake

[@rudigerhoppe5708]

Hi! I've used the AD2 with the Analyzer Suite for a while now and it works as intended. I'm just a bit puzzled over the measurements I get. They are all awfully equal, no matter what amp I measure, the good, the bad or the ugly. I set the amp so it outputs a bit over 10 watts at 0.2 mv. The scope tab looks very 'fuzzy' on low levels and smooths out a bit when getting up to the 10 watts. Still has 'jaggies' on the curves, though. THD/frequency is always around 0.2% for the frequency range. THD/power starts at about 1% and then goes down to a bit under 0.1%. Maybe I have some noise disturbing the signal? When I measure with my oscilloscope the cables, dummy load (providing a attenuation of 10) and connections deliver smooth graphs. I'm using the BNC board and it should and does connect the ground to the AD2. Any ideas?

[@TheStuffMade]

Hi Rudiger, that doesn't sound right, I recommend you try connect the AD outputs directly to the inputs without any amplifier attached (include the attenuation resistors etc you are using). Then you should measure about 0.02% distortion (this is the best the AD can do with it's 12 bits resolution). Keep in mind if you are using excessive attenuation then you will be losing bits, it could explain what you are describing. Also I believe the BNC board got some 50 ohm impedance jumpers, make sure they are not enabled, you want high impedance for this measurements. Cheers, Jake

[@rudigerhoppe5708]

@@TheStuffMade Allright, that helped. I tested with inputs directly coupled to outputs. 0.02% distortion, nice. I ditched the times 10 attenuation and the BNC board and wired the AD2 to unattenuated outputs of my dummy load. It works now. The good and the bad measure actually down to 0.02% distortion, only the ugly is still ugly. :-) Thanks a lot.

[@TheStuffMade]

@@rudigerhoppe5708 That's great, I'm current working on adding support for regular sound cards (see my latest video) that will allow measuring performance far beyond the AD's limitations. However for regular repair/testing testing of amplifiers I'll still recommend the AD as it's much more rugged and have a much wider bandwidth than any sound card.

[@AudioFanMan]

First, thank you for amazing software! I have not found anything for saving test results, is it possible ? How ?

[@TheStuffMade]

Thanks, I haven't added any feature to save or export the test result. I was planning to do some kind of test report, but I never got around to implementing it. What I usually do is CTRL+Print Screen to make a screen capture, then just paste it into a Word document where I can add notes on the measurements. Cheers, Jake

[@shazam6274]

Nice, but a few issues: 1) Frequency Response Test needs a STOP button, 2) THD Run / Stop Toggles ON-OFF, this is inconsistent with other tests 3) THD Power needs a STOP button 4) THD / Freq. needs adjustable output level in Vrms i.e. at what signal level is the THD v Freq being measured? Really neat application. Unfortunately The Analog Discovery 2 I just got, has noisy distorted signal sources (relatively speaking). The output impedance is not specified or ascertainable in the partial schematics. The one I found on Digilent states it is 1 Meg-ohm, in any case it is weak and single ended. The best "Loop Through" performance I could get was just above 0.01% THD. I am thinking of making a plug-in PCB with a Balanced Line Driver (< 40 Ohm Imp. Out) for the 2 outputs, with maybe some filtering to clean up the signal as well. Balanced Out would also allow CMRR measurements. Same for the Input: Balanced buffer with TVS, ESD and overload protection. PCB will have XLR, BNC and RCA connections (maybe 3.5 mm too). Some features could be switched or, if you can, add buttons to the screen and a GPIO from the AD2. Also needs a switchable load from 1 to 8 Ohms at a few (or more than a few) hundred Watts. This could also be controlled with a couple of GPIOs. If these are interesting to you, please contact me directly at [e-mail] (you have hidden well, I could not find another way to contact you). FYI: I am an EE and have been designing audio amplifiers and equipment, which have been mass produced, for many decades.

[@TheStuffMade]

Thanks, it's good feedback, I'll keep it in mind for the next version. The level for the THD vs Freq is based on the specified output load and wattage. The software will perform a gain test at 1kHz to determine the level before running the scan. The Analog Discovery (1 and 2) does have a low output impedance on the wave outputs, it's pretty much directly the output from the AD8067 with a PTC fuse in the feedback loop for protection. It can reliably drive a 50 Ohm load. Maximum continuous output current is something like 20-30mA if I remember correctly. Keep in mind this is not meant as a precision measurement solution, the ~0.02% minimum distortion you get sounds about right for what is achievable with the Analog Discovery. It's only got a 12 bit dynamic range. My software is meant as an easy way to perform various types of measurements on an amplifier to check if it's working correctly and help identify potential faults or design flaws. E.g. if you are designing/building an amplifier and you need a quick sanity check or assist in the repair of old amplifiers. It's not meant to perform precision performance measurements of low distortion or signal to noise ratios etc etc. I did start work on a plug in board at some point with balanced outputs and various filter configurations, loads etc using a number of analog switches, however in the end I decided against it. But if you proceed let me know how it goes then I'll see if I can assist with options to set various digital IOs for the various screens.

[@shazam6274]

@@TheStuffMade Thank you for your response. Since I wrote, I have looked at the audio band spectrum of the Waveform Generator with 1 kHz, and there are several (~ 9) frequencies with spikes up to -74 dBV at specific, non harmonic frequencies. These may be the "deal breakers" since removing them would be perhaps impossible. The noise floor could be improved a bit. The only way the residual THD could be improved is to have tracking notch filters for ~6 harmonics and ignore the noise and the spikes, but this may also have issues, especially if the spikes are constant, or the distortion of the DUT is non harmonic. I'll think about it, after I get some sleep.

[@TheStuffMade]

@@shazam6274 I don't think the intention of the Analog Discovery designers was to make a high end instrument, I believe their primary objective was to cram as many features as possible into a small space. And I think they were quite successful. The new owner (National Instruments) make similarly spec'd devices costing $2k or more (virtual bench) You can remove some of the major spikes using a few ferrites over the analog section, but I don't think it's worth the effort.

[@shazam6274]

@@TheStuffMade I agree, the Analog Discovery is indeed great, and is much better than anything else, especially for the price. The noise spikes are right in the middle of the audio band, most likely caused by PCB layout and lack of shielding from all the digital stuff and sub harmonic noise from the switching V-Regs. RC filters and FBs are not going to help much. Since you are interested in an RIAA phono amp: check out the new TI / BB OPA1656 data sheet page 11. The SOIC-8 dual IC is ~ $2.50 ea from TI or ~ $1 @ > 1k.

[@TheStuffMade]

That opamp does look great for low noise, high gain use, a worthy successor to the old opa2134. I have been contemplating building my ultimate Phono Preamp, as in no coupling capacitors, all servos, perhaps even no decoupling capacitors, but using high quality opamps as voltage regulators. etc etc, as crazy as I think might make sense. However then I would also construct my ultimate tube based phono preamp, all shielded, low noise tubes, regulated supplies. high quality coupling capacitors, equalization using silver micas etc etc. Both aiming for as close as possible to the RIAA curve and equal gain. Then I would like to do a blind test over several months to see which one I like the best. Just a fun experiment.

[@davethomas796]

is the testing open loop or closed loop. thanks for the software I am thoroughly enjoying using it

[@TheStuffMade]

It's open loop, as in it doesn't measure the output to compare with the input. The output of the Analog Discovery is fairly accurate out of the box, but you can run the calibration procedure to improve accuracy. Cheers, Jake

[@davethomas796]

@@TheStuffMade thanks... I assumed it was. I did run the calibration. Your software is great stuff. Thanks

[@TheStuffMade]

@@davethomas796 Thanks, I expect to have a new version available within the next few weeks.

[@TheStuffMade]

Leave a comment if you have trouble with the install.

[@philleigh1768]

I wouldn't work … (Windows 10 + updates) …1.75 work once nice! (I work a Stroke and aphasia)

[@TheStuffMade]

@@philleigh1768 Did you get any error message? Thanks

[@philleigh1768]

PLATFORM VERSION INFO Windows : 10.0.17134.0 (Win32NT) Common Language Runtime : 4.0.30319.42000 System.Deployment.dll : 4.7.3056.0 built by: NET472REL1 clr.dll : 4.7.3394.0 built by: NET472REL1LAST_C dfdll.dll : 4.7.3056.0 built by: NET472REL1 dfshim.dll : 10.0.17134.1 (WinBuild.160101.0800) SOURCES Deployment url : file:///C:/Users/Phil/Downloads/AudioAnalyzerSuite_1.0.0.77/AudioAnalyzerSuite/AudioAnalyzerSuite.application ERROR SUMMARY Below is a summary of the errors, details of these errors are listed later in the log. * Activation of C:\Users\Phil\Downloads\AudioAnalyzerSuite_1.0.0.77\AudioAnalyzerSuite\AudioAnalyzerSuite.application resulted in exception. Following failure messages were detected: + The referenced assembly is not installed on your system. (Exception from HRESULT: 0x800736B3) COMPONENT STORE TRANSACTION FAILURE SUMMARY No transaction error was detected. WARNINGS There were no warnings during this operation. OPERATION PROGRESS STATUS * [16/04/2019 15:39:42] : Activation of C:\Users\Phil\Downloads\AudioAnalyzerSuite_1.0.0.77\AudioAnalyzerSuite\AudioAnalyzerSuite.application has started. ERROR DETAILS Following errors were detected during this operation. * [16/04/2019 15:39:51] System.Runtime.InteropServices.COMException - The referenced assembly is not installed on your system. (Exception from HRESULT: 0x800736B3) - Source: System.Deployment - Stack trace: at System.Deployment.Internal.Isolation.IStore.GetAssemblyInformation(UInt32 Flags, IDefinitionIdentity DefinitionIdentity, Guid& riid) at System.Deployment.Internal.Isolation.Store.GetAssemblyManifest(UInt32 Flags, IDefinitionIdentity DefinitionIdentity) at System.Deployment.Application.ComponentStore.GetAssemblyManifestFromStore(DefinitionIdentity asmId) at System.Deployment.Application.ComponentStore.GetAssemblyManifestWithRetry(DefinitionIdentity asmId, TimeSpan retryInterval, Int32 maxRetryCount) at System.Deployment.Application.ComponentStore.GetSubscriptionStateInternal(DefinitionIdentity subId) at System.Deployment.Application.SubscriptionStore.GetSubscriptionStateInternal(SubscriptionState subState) at System.Deployment.Application.SubscriptionStore.CheckAndReferenceApplication(SubscriptionState subState, DefinitionAppId appId, Int64 transactionId) at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation) at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options) at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl, Uri& deploymentUri) at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl) at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state) COMPONENT STORE TRANSACTION DETAILS No transaction information is available.

[@TheStuffMade]

@@philleigh1768 I have added a new file in the dropbox download named _no_installer, please try this one. You only need to extract to a folder and run from there. It might solve your issue. Regards Jake

[@philleigh1768]

Jake, Thanks - OK!!!!! best regards Phil

[@tgirard123]

I don't suppose you might be inclined to update the software for the new Discovery 3? I tried it on the discovery 3 but I don't think it's working right. I would definitely pay to have this too lset on my Disc 3!

[@TheStuffMade]

It should work with AD3, please share more details on what issues you're experiencing. Cheers, Jake

[@rudigerhoppe5708]

Hi, thanks for the software. It installed fine and seems to work as intended. I use the AD2 with a dummy load and a attenuation factor of 10 on the outputs. It looks like the THD+N vs Power does not take the attenuation into consideration when calculating the @watts. I measured an amp and the app said 3.7 watts at clipping when a more reasonable value would have been 37 watts. I'm also struggling with the output level values. For example when using the scope, no matter the level I set, the AD outputs 10.6 vpp, measured by my oscilloscope. The same happens also for the frequency response. I thought my AD was defect because all I could see was square waves on the scope tab, when actually the amp was totally clipping even at moderate volume settings. Maybe I'm using the software wrong?

[@TheStuffMade]

Hi Rüdiger, do you mean you set the attenuation factor only in the software? You need to also add resistors on the AD input to match the attenuation factor you set in the software. There is a PDF file included in the download that explains in more details.

[@rudigerhoppe5708]

​@@TheStuffMade Thanks for fast the answer. I have the resistors added on the amp output to get me the attenuation of 10 using a divider as shown in the pdf. But I think I found the problem with the watt calculation and the output levels. I'm in Europe using a danish windows setup. We write decimals with a comma, not a dot and the windows setup takes that into account. When I use a comma instead it sets the output level correct to e.g 0.2 (we write it as 0,2). Don't know what the software makes out of a 0.2, but it is obviously a too high a value. The same is true for the Load Impedance. I need to manually set it to 8,0 instead of the default 8.0. Then all works fine. Me being a software engineer myself I know the can of worms I just opened here. I will watch my inputs from now on. :-)

[@rudigerhoppe5708]

Sad thing is, the high output levels seem to have destroyed the input stage of a 1963 all germanium amp. Well, need to get hunting for those rather unobtanium parts.

[@TheStuffMade]

Hi @@rudigerhoppe5708 that's unfortunate, I believe your conclusion is correct. You are the first to report this issue, so it's another item to add to the todo list for the next version. I'll also add a warning to the video description for the current version. Thanks for reporting this.

[@richardweisman6556]

Is there published information about the test jigs that you use? I am not sure how to make them.

[@TheStuffMade]

Hi Richard, I have a PDF document with the various test jig information included in the download called AudioAnalyzerSuite_Guide.pdf. It's however not up to date anymore. I will probably make a long boring video at some point going through all the screens and describe what everything means and how to connect your Analog Discovery to make all the measurements.

[@richardweisman6556]

Thanks for responding so quickly! Where is the pdf located? Not apparent on your home page.

[@richardweisman6556]

Oh, I just found it!

[@cowasakiElectronics]

Is there any advantage to having analog discovery 2 rather than 1 whilst using your software? I just need to know before spending the extra money. Thanks

[@TheStuffMade]

Hi Darren, the only difference between AD 1 & 2 is the built in power supply output, on AD2 you can adjust the +/- output 0-5V and up to 500mA, on the AD1 it's fixed +/- 5V and limited to 50mA. For my software it makes no difference which one you use, you will get the same results. Cheers, Jake

[@cowasakiElectronics]

@@TheStuffMade Sorry all the analog discovery 1 units they had in stock have sold. Is that one of the older legacy units that you are using? If so would you happen to have the model/part number so I can be sure I get something that works with your software. Also are you running windows 10? Just checking if their are drivers for the legacy model for windows 10. Many thanks.

[@TheStuffMade]

@@cowasakiElectronics The latest version of the Audio Analyzer Suite has been tested to work with both AD1 and AD2 under both Windows 7 and Windows 10. I used to test Windows XP, Win 8.x as well, but I think no point so now I only test Win 10 and Win 7. I also use the latest version of digilent drivers/software while testing and I can confirm the latest drivers/software are compatible with both AD1 and AD2. Cheers, Jake

[@cowasakiElectronics]

@@TheStuffMade I can't find any AD1 any more :-( I thought I had found something from RS but it is the logic analyser and just looks the same. Oh well only had enough money this month for the AD1 so will have to wait till next month...... Looks a great package.

[@recordingstudiotech]

This run on Mac? The entire reason I bought an AD2 was to do basic audio tests on my mac, if you could make it work for Mac that would be awesome!

[@TheStuffMade]

Windows only, sorry, I don't have the time to support multiple OS builds. You can still use your AD2 on Mac with the AD software, it''s just not really streamlined for audio measurements

[@telefunkian]

FWIIW, I use this (TheStuffMade Audio Analyzer) on a MacBook Pro running Windows in 'Parallel', it works great! If you are flipping from MacOS to Windows you need to unplug the AD, plug it back in to the computer and select the Windows OS for the USB connection. This suite is the whole reason I got an AD and I am glad to be able to use it on my Mac laptop on the bench.

[@AlejandroGonzalez-AGS]

Hi, Could you please direct me where I can download the latest software? Thank you. Cheers..

[@TheStuffMade]

Get latest version here: www.dropbox.com/sh/ecgo4oiw7u9o3e0/AADu20wAB4aP10wQsXyrwCpNa?dl=0 Cheers, Jake

[@angeloocchi05]

Hello!! I’m trying to help my dad download your program we have windows 10 it’s downloaded but for the life of me I can open or run the program I tried though internet explorer and Firefox any thoughts on what I could be doing wrong? Thanks so much

[@TheStuffMade]

Hello, can you share what kind of errors your are experiencing? You must have latest version of the Digilent Waveforms installed, if not you usually get some dll error message. Cheers, Jake

[@angeloocchi05]

@@TheStuffMade Hi, I’m happy to report back that we got it working just don’t ask us how 😂 thank you for replying have a wonderful day!

[@hollisvarney2243]

Can I just use the scope probe across the dummy load set on 10x and set the attenuation to 10 at the bottom of the window? Also is there a way to save the files so Yhat I can print them? Thanks Great program hollisav

[@TheStuffMade]

Hi Hollis, I would not recommend using 10:1 attenuation unless you are measuring a very large amplifier at full output. Keep in mind the Analog Discovery is only 12 bit range and you want to keep as many bits as possible for the results. E.g if your amplifier is below 50W then you will probably not need any attenuation, beyond that I recommend you have a look at the pdf that is included with the download, it's got some details to consider when adding attenuation.

[@hollisvarney2243]

@@TheStuffMade I have seen the guide and see what you are doing with the 4 10k resistors. Wouldn't using the probe in 10x use the same bits as your setup? Most amps I test are over 50 watts and a few over 150 watts. It would be much easier for me to just use the probe in 10x than to build a voltage divider circuit. I also found that I just have to print screen and then put them in a folder for printing if I need to. Thanks

[@TheStuffMade]

@@hollisvarney2243 Not quite, the way scope probes do the 10:1 attenuation is by adding a 9 meg resistor in series with the signal line and then create a divider by assuming the scope got a 1 meg input impedance. However the Analog Discovery's inputs are differential so you need a divider on each input, not just the positive input, this is especially important when you measure amplifiers with bridged outputs like e.g. most class D amplifiers. Also 10:1 attenuation is way too much, it would allow measuring a 3500W @ 8 ohm amplifier without clipping. That might sound cool, but the cost is a loss of resolution, meaning you will not get much detail when measuring lower output amplifiers. I'd recommend not adding more attenuation than you absolutely need and perhaps make something where you can switch between 1:1 and e.g. 1:3 attenuation.

[@hollisvarney2243]

@@TheStuffMade I am using the AD2 with the BNC adaptor board. Are the scope inputs still differential? How would I use a attenuation circuit with that? Would I use say 30K and 10K resistors and what wattage would they have to be?

[@TheStuffMade]

@@hollisvarney2243 I had a quick look at the schematic for the BNC adapter board and it does short the negative inputs to ground, meaning if you measure a bridged amplifier using this configuration you will be shorting the amplifier's outputs and something will let out the magic smoke. So I cannot recommend using the BNC board. For the divider you can use 20k and 10k to get a 3:1 attenuation, standard 1/4W resistors will be fine.

[@jansen2810]

Can someone help me with this? Measuring THD+N the input generated bij the AD and software (TUNER =150mV sensibility) for my amp gets way to high (sometimes over 1Volt) with clipping as a result and unrealistic THD values. What could be the reason? Can I set the value on a 100mV f.i? I presume the numbers on the left upper corner of the scope-frame is the voltage which is fed into the amp. Right? For some reason measuring on a tube amp everything works fine. (500mV input sensibility) AD generated input values are much lower than. I am puzzled..... (dot - comma issue is corrected by me)

[@TheStuffMade]

Hi Adri, first make sure you are running latest version: www.dropbox.com/sh/ecgo4oiw7u9o3e0/AADu20wAB4aP10wQsXyrwCpNa?dl=0 Then try connect the AD output directly to the input and run a test with the output set to 100 or 150mV. It should look like this: imgur.com/Pj1EGZg Upload or send me a picture if you get different values. Cheers, Jake

[@jansen2810]

@@TheStuffMade I have, no other version to be found.

[@TheStuffMade]

@@jansen2810 Good if you are running version 1.2.0.3 then try the next test I suggested.

[@jansen2810]

I will check my version once more. I don’t have those options.

[@jansen2810]

@@TheStuffMade Sorry for my ignorance. I have 1.0.0.76

[@jameswarren1831]

Has anyone tested your software on the Analog discovery 3?

[@TheStuffMade]

Not that I'm aware of, but I'd like to know if it runs.

[@jameswarren1831]

@@TheStuffMade kzbin.info/www/bejne/an7ZiHubfphsabssi=oLvaq_QHBtGgxDDH there's the answer!

[@clytle374]

Not sure if you have commercial interest related to this project, but if not it'd be awesome if you'd release this as source code. Might find that it makes a good open source project. I keep meaning to try it out, but Linux user here.

[@TheStuffMade]

Hi Cory, I have no commercial interests in this product and it will remain free, however my experience with open source is pretty bad tbh. Usually everyone asking for the source to anything I've made just want to butcher it for their own use instead of contributing to a better product.

[@clytle374]

@@TheStuffMade I understand, that unfortunately does happen. Guy that designed that open source amature radio sure had the China making copies and using his code pretty quick. Who knows how much open code has been stolen and being used in commercial products. My interest was solely to get it to run in Linux

[@andresmartinelli5276]

@@TheStuffMade can this be run on Linux? Thanks!

[@erikkonka7853]

I can not start the software working. I kind of a starts up and then the error message appears. System is Windows 10 version 1909. The error message from Audio Analyzer Suit: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************ Exception Text ************ System.FormatException: Input string was not in a correct format. at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt) at .⁡. (Object , EventArgs ) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************ Loaded Assemblies ************ mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- AudioAnalyzerSuite Assembly Version: 1.0.26.374 Win32 Version: 1.0.26.374 CodeBase: file:///C:/AudioAnalyzerSuite/AudioAnalyzerSuite.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.3761.0 built by: NET48REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.3761.0 built by: NET48REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.3761.0 built by: NET48REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Deployment Assembly Version: 4.0.0.0 Win32 Version: 4.8.3761.0 built by: NET48REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Deployment/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll ---------------------------------------- System.Numerics Assembly Version: 4.0.0.0 Win32 Version: 4.8.3761.0 built by: NET48REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll ---------------------------------------- ************ JIT Debugging ************ To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

[@TheStuffMade]

Hi Erik, didn't see your comment earlier because it got blocked by youtube. Anyway, my best guess is that this error is caused by a localization issue. I guess you run Windows with a locale where you use , instead of . as decimal separator. This is a known issue that I will address probably in the next version. Until then you can try temporarily change your number format in Windows under Region Settings and see if that works. Cheers, Jake

[@erikkonka7853]

@@TheStuffMade Hi! Thank you very much for the advice! Yes the comma versus "." was the case here. I corrected it and all started to work. Thanks again!

[@TheStuffMade]

@@erikkonka7853 Good to hear that was the problem. I'll try address it in the next release. Thanks

[@ujjalkohli7930]

Does this work on Mac?

[@TheStuffMade]

Sorry about late reply, this is windows only, unfortunately I don't have the time to maintain multiple platform builds so I expect it will remain Windows only.