Could you help? I am a bit confused... is this the wrongly labeled 2.0.1 SW? This is at least what I get atm when I login into my Neumann profile. Or where did you get the 2.0.1 version. Thx.MA 1 version 2.0.1 is available and fixes the crash-problem for me. I can load my old setups/alignments without re-calibrating.
Another old bug i had for some time (problems with volume jumps between changing things) is also resolved.
It is available through auto-update and the website.
Support says the download page has a wrong label that says "2.0.0" at the moment, but it is also version 2.0.1 there.
Yes, this should be the wrongly labeled version 2.0.1.Could you help? I am a bit confused... is this the wrongly labeled 2.0.1 SW? This is at least what I get atm when I login into my Neumann profile. Or where did you get the 2.0.1 version. Thx.
View attachment 320288
Ah ok... I am still on 1.5 or something, so no built-in updater, I guess. Does the new MA1 SW also update the KH... firmware (in my case KH80 Vers. 1.3.1.)?Yes, this should be the wrongly labeled version 2.0.1.
I got it from opening my 2.0.0-installation, then i got an update notification popup and made the update through the app. I think they added the updater in 2.0.0.
Edit: This is what Neumann support wrote to me yesterday: "You can actually update from MA 1 itself. The installer in your online Neumann account is now also 2.0.1, although it is incorrectly labelled as 2.0.0 (a labelling error)."
I don't know what the newest FW version is, but yes, when you update the MA1 software, it will update the firmware of connected speakers, if they don't have the newest version.Ah ok... I am still on 1.5 or something, so no built-in updater, I guess. Does the new MA1 SW also update the KH... firmware (in my case KH80 Vers. 1.3.1.)?
Bingo....I don't know what the newest FW version is, but yes, when you update the MA1 software, it will update the firmware of connected speakers, if they don't have the newest version.
Good it worked for you, but this means the version on the download page is actually 2.0.0 and not 2.0.1 (because if it where 2.0.1, it shouldn't need to be updated again).Bingo....
View attachment 320300
Can confirm. First one downloads and installs the version 2.0.0.6554. When starting up, it asks to update and upon confirming and restart one gets 2.0.1.6557.
It then updated my KH80 firmware from 1.3.1. to 1.3.5.
All worked like a charm and kept my previous setup .... cool.
Ah one question....
What do they mean by licencse key? (one gets it when pressing on the new key symbol in the upper right corner). I dont recall I ever needed one in the past. Previously, all what was needed were the MA1 Microphone Serial Numer as far as I remember and entering that did not do the trick.
View attachment 320303
Yes (today) the downloadable version is not 2.0.1 the file name says so, the download page says so (see my screenshot further up) and upon first startup it also says, 2.0.0. But immediately displays a message after starting, warning of a possible crash and advises to update and to press "Yes". It then updates to 2.0.1, but does not restart on its own. So restart and all is good i.e. 2.0.1.Good it worked for you, but this means the version on the download page is actually 2.0.0 and not 2.0.1 (because if it where 2.0.1, it shouldn't need to be updated again).
....
No it is meant you need either 2 balanced analog OR spdif OR...Hardware Requirements include:
• Audio interface with: o 1x balanced analog mic input with 48 V phantom power o 2 balanced analog outputs, S/PDIF outputs (only with KH 120 II KH 150), AES3 output (only with KH 750) or AES67 for AES67-enabled models
Does this mean that to measure the 120II, you need an interface with spdif outputs or will one with analogue outputs suffice? I only have an Arturia Minifuse 1 and will be using the digital connnections ongoingly after the measurements are finished,
I am on 10 too. Works ok. See above.well, mine is instantly crashing when i select the "create new measurement" option. made sure my interface is at 48 khz, updated the software, even disconnected my audio interface entirely, etc.... no luck.
im on windows 10.
*edit* fixed it. i had a random/additional driver that was causing it to crash. disabled it and everything works greatI am on 10 too. Works ok. See above.
Please notify Neumann as this obviously should not be.
personally i have a near-field listening situation as well. my problem was that almost ALL of the bass was a 2-3 feet behind my listening position. I ended up getting the MA and doing calibration, and it made a huge difference. everything is leveled at my listening position now. it definitely makes a huge difference, but if you wanted to save, you could use other software/mic calibration that's cheaper, maybe more bang for your buck.So I am considering buying a pair of KH-120 II for near-field listening at my computer desk. The MA-1 would add quite a significant chunk of change on top of the monitors. How much of a difference do you guys think the MA makes to the speakers for near-field? I feel that room modes for such close listening positions are less impactful and I can avoid using MA. Is that assumption fair?
Unfortunately not, even at very close range a room will mess-up the bass. Here's how my KH120A measure at less than 1m distance on my desk - notice the 50-80Hz bass suckout and the huge ~130Hz resonance, both very audible.I feel that room modes for such close listening positions are less impactful and I can avoid using MA. Is that assumption fair?