I have Genie 2 2023.1 installed under Fusion on a Mac. I’ve run it in simulation mode and it seems to work fine.
I now have a Noahlink Wireless, DLL Version 1.2.00 with firmware at 2.2.3
I have taken the following steps to get these environment working so I can program my Oticon Real 1 HAs.
Install Genie 2 as indicated above under Fusion running on Macbook Pro.
Stop BT on my iPhone and iPad.
Plug in Noahlink (NL) into usb port on Mac.
Fusion prompts me to ask where to attach the NL – Mac or Windows. I select Windows.
I can see in Windows Device Manager that the NL has loaded cleanly.
Go to Preferences in Genie and have Genie successfully detect the NL. I’m also prompted to upgrade the NL firmware which I successfully complete.
Go back and select my previously created client name as the client.
Click on Welcome to proceed to next fitting step.
Click on Connect to try to read setting on my HAs which are “read” mode (just rebooted).
At this point I get the error:
"Genie 2 cannot communicate with NoahLink Wireless. Please try the following:
– unplug / replug the NL
– Reselect NL in Preferences
– Start instruments again
When I look at the log file the main thing that stands out is the following line:
“Enumerated device is not compatible. Reason: internal firmware mismatch. Run upgrade to repair.”
I cannot get past this error.
At this point I’ve tried the following:
– reboots of Windows machine and Fusion.
– multiple USB ports for the NL
– removing and adding back the NL in Device Manager
– trying to find a later version of either Genie or NL drivers (I don’t think there is)
Although I’ve tried to read everything in the DIY folder and elsewhere, it feels like I’m missing something obvious. Any thoughts?
I am willing to install Boot Camp and remove Fusion as a possible source of problems, but my gut says the problem is something else. NL seems to load very cleanly under Fusion.
So yeah most people use bootcamp, one thing is to downgrade the firmware, NL needs to be downgraded and then re-upgraded to the desired version, it’s a known issue that this sometimes happens.
Follow the procedure exactly from here. Hopefully this will fix it
Thanks. I’ll give it a try now. The firmware problems looks like it’s related to Windows 7, but who knows. The error message does refer to a problem with software levels.
Also, I’m not using an activated version of Windows 10. Hopefully, that’s not an issue.
It looks like there’s a problem with the 2.2.3 Noah Link firmware . It took awhile but I finally got the 2.2.4 firmware to install and it fixed the problem. Thanks much for your help.
I did thanks to your help! And we know Fusion works fine (knock on wood) with Genie and Noah.
I have two related questions now that I’ve started experimenting.
I unpaired my Connectclip in Accessories because it’s been giving me issues and I want to start over. . How do I “pair” (not sure it’s a real BT pairing) CC back to Genie.
The CC is attached via USB and is recognized by Genie in Firmware Transfer as being up to date. I also paired the CC via BT to the Windows VM (not sure this was needed). But I don’t see any way to make Genie “pair” with CC. I still see the Connect Clip showing up in accessories but Accessories says no CCs are paired.
When I run Feedback Analyzer where should my hearing aids be — in my ears or on the table next to the Noah. If they are on the table in my main program modes they will be squealing with feedback. If the aids are in my ears, does it matter what program mode the are in?
For pairing the CC you need to pair your hearing aids with CC.
The hearing aids must NOT be paired with Genie!
Close Genie ; restart the hearing aids ; and follow the pairing instructions
After you paired the CC with your hearing aids, connect the aids with Genie via Noahlink.
Then you should see CC as paired in the Genie software.
during Feedback Analyzer the hearing aids must be sitting in your ears
Thanks, I managed to get past the problem while your post came in …
The steps I took were:
Remove CC pairing to Windows in Settings
Clear all pairings in CC by depressing multi button and both vol keys for 10 seconds
Pair Oticons aids with CC via normal process
Now the CC shows up in Accessories after connecting via Genie / Noah
After basically resetting the CCs, I’m now able to use the CC as a remote mic and, amazingly, also pair / connect with my Mac and hear audio without audio cut-outs!
I don’t know how long this miracle will last but at least I can start over again by deleting the Genie “pairing” and following the above process.
What disturbs me is the above “reset” process is completely dependent on having a Genie / Noahlink to remove the Genie “pairing” since there’s zero way of removing that pairing without having a self-programming environment. You have to wonder how many CCs are bricked because people get tired of going to their Audis to clear the Genie “pairing” – if the Audi even knows that’s the initial recovery step.
I have been a Mac and Windows user in my career as a composer for over 3 decades. Trying to run Windows on a Mac can be incredibly frustrating and isn’t worth it IMHO. In your situation (and mine) I would get would get a used PC tower meeting the requirements and dedicate it solely to your purpose of programming. When you have your rig running flawlessly, lock the system. No auto updates. Turn off anything unnecessary. All the major post houses run their systems two years behind.
Not sure why you’re using the Feedback Analyzer? What hearing aid model do you have? The OPN or OPN S or More or Real or something else?
Starting with the OPN S and later, the Feedback Shield (by way of running the Feedback Analyzer and enabling it) is no longer necessary if the new Optimizer Feedback Manager works OK for you. You’d only want to use the Feedback Shield if your aids are OPN when there was no Optimizer yet back at the time.
For people with very heavy loss where the Optimizer is not sufficient to manage feedback (or because it must be turned OFF to get rid of the fluttering because even set to LOW still bothers the user), the Feedback Shield “can” be used in conjunction with the Optimizer to augment it. But if the Optimizer alone is good enough to manage your feedback issues, then you shouldn’t use the Feedback Shield anymore.
The reason for avoiding the Feedback Shield if you can help it is because for pure tones, the 10 Hz frequency shift (as a strategy to minimize feedback) may cause a warbling sound when you listen to pure tones. Also, the Feedback Shield will implement gain reduction in the frequency location(s) where the Feedback Analyzer finds to have more potential for feedback, so the gain margin can be greatly reduced in those areas EVEN IF you’re in a wide open place or when the sound is soft enough as to not have triggered any feedback in the first place. You basically lose your gain margin in those areas for good. It is actually precisely for this reason that Oticon came up with the new Optimizer feedback scheme, to restore any potential gain margin loss that the Feedback Shield might have claimed. The end result is a better signal to noise ratio when you have better gain margin than not.