• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Solved Studio One v6 major issues (nahimic audio driver issue)

@sintil8, better than that I've just done a DDU with windows in safe mode and then re-installed the graphics driver using "driver only" and "minimum build" options.

No luck unfortunately

"If I'm nothing without my second monitor, then I shouldn't have it"
 
At the minimum it's an reasonable indicator the Drivers are not at issue, so it moves forward a small step.
You can also discount 3D enhancement or GPU audio driver conflicts.
It's not the leads or Hdmi sockets
Resolution or refresh rates, to mention some of the checks you have run through.

I suppose it's a waiting game until support can get back to you, hopefully they can track it down from the logs you have sent them.
As I said, one last thought. If anything else should spring to mind I will be back in touch.

It's as frustrating little bugger this one. After all the suggestions folk have made I'm surprised there is not some indicator jumping out.
I don't know about "If I'm nothing without..."

You will probably be sanctified for sticking to it. I admire your fortitude.

Kindest regards for now.
 
Presonus support have "tapped out" as they can't re-recreate the problem as none of them have AMD cards in their machines.

They suggested that I contact Fabfiler but I've done a bit more testing. It's not just the FF plugins, I threw 5 more at it and 2 worked fine (Standarclip and Shaperbox) but 3 from different developers produced the same problem (Auto-align, Speccraft and Split EQ). Add that to ones I'd already discovered don't work: TB Proaudio DSEQ3 and Oxford Drum Gate.

So it definitely isn't plugin developer specific.

Rather more worryingly (for me) is that I realised I had an evaluation version of Reaper so I thought I'd see what happened if I did the same thing there. Well, it took a few times opening and closing the plugin window on the 2nd monitor but eventually it stopped responding too.

Think I'm going to have to try AMD support next but I'm not hopeful
 
Studio One is designed for Standard HD (1920x1080p) @ 60hz.
I wouldn't say that. Studio One is designed in HDPI since nearly 10 years.
Although it still supports some lower resolutions, but Studio One was one of the first DAWs that supports system native HDPI completely.
 
@darren
It might be worth trying to find a cheap secondhand GPU with a couple of Hdmi sockets, or if a friend or a family member will let you cannabalize their computer for a day, Just to make sure the GPU hasn't developed a fault.
I had a GPU fail due to a build up of dust in one of the fans and the card slowly died developing faults along the way.

I'm a dab hand with a small car vac these day's, as silly as it sounds keeping all the fans and inlets clean and free can extend the life of computer components and shouldn't be ignored. It's the temperature overs that can cause damage. It shouldn.t be a problem with a Daw as they are not Graphics intensive. Anyway I'm waffling on.

Be good if you could keep us informed as to how you get on with AMD support.

Best of regards.
 
Last edited:
It's sorted! The problem was some audio driver called "nahimic" which was somehow installed on my system 13th June of this year. I have an Asus motherboard and my best guess is that it must have been part of some kind of asus motherboard tools update that I installed but it certainly wasn't intentional.

It's also a complete pain to get rid of but I think it's now gone.

I found it because AMD support suggested I do a clean boot by disabling all non-MS service and all startup items and see what happened. Well, what happened is that it then worked so I then had a painstaking few hours trying to work out which of these services and startup options was causing the problem. And although it was one of the last that I tried (because honestly I didn't know what it was) as soon as I started the service and re-booted the problem came back.

So, it's definitely that. How on earth an audio driver caused the issue I was having I can't even begin to explain but at least it's sorted now.

Thanks to everybody for trying to help and although this problem is nothing really to do with S1 I can't believe I'm the only person who's going to run into this issue so hopefully this adds to the knowledge base.

Regards

Darren
 
I wouldn't say that. Studio One is designed in HDPI since nearly 10 years.

Well - keep in mind - just because Studio One can run HiDPI - does not mean anything hosted within it can.

Have dealt with more "resolution" issues regarding Studio One and the display limits of hosted plugins than I care to remember.

And to downgrade even more - the system specs on the website are not even 1920x1080 anyway:

1751406497211.png


Instead of saying "Designed for" - I should have said everything "just works" when running in Standard HD.

VP
 
Last edited:
No luck unfortunately

"If I'm nothing without my second monitor, then I shouldn't have it"
@darren
You will have your second monitor and keep it.
🫡

Driver conflict, "nahimic" it's bloatware, it's installed by a selection of motherboard manufacturer's.
I googled it out of curiosity and also self preservation. Man I hate it when the gremlins take control.


Best of regards and thanks for posting the AMD info, will you be marking the thread solved.

Take care.
 
@darren
You will have your second monitor and keep it.
🫡

Driver conflict, "nahimic" it's bloatware, it's installed by a selection of motherboard manufacturer's.
I googled it out of curiosity and also self preservation. Man I hate it when the gremlins take control.


Best of regards and thanks for posting the AMD info, will you be marking the thread solved.
I will be marking it solved just as soon as I find the button to do that!

One last piece of information just in case anybody else runs into the same problem. Nahimic (also A-volute) is very hard to get rid of but I followed this post on reddit and it seems to have done the trick. It's almost virus-like in its attempt to infect various parts of your system and re-install itself.

It's been a journey but I'm pleased that not all those who wander are lost ;)
 
"nahimic" it's bloatware, it's installed by a selection of motherboard manufacturer's.
I googled it out of curiosity and also self preservation. Man I hate it when the gremlins take control.

This is why I disable everything hardware related - in the BIOS - on every motherboard I use for a custom build - espeically the onboard audio chip and in the case of ASUS - their insidious toolkits like Armoury Crate, MyASUS and their goofy AI suite.

Then when Windows is installed - there is zero chance of any of these onboard devices to even exist and no chance for anything like "nahimic" to install either.

VP
 
This is why I disable everything hardware related - in the BIOS - on every motherboard I use for a custom build - espeically the onboard audio chip and in the case of ASUS - their insidious toolkits like Armoury Crate, MyASUS and their goofy AI suite.

Then when Windows is installed - there is zero chance of any of these onboard devices to even exist and no chance for anything like "nahimic" to install either.

VP
Yep,
I follow that general priciple as well, there are a lot of liberties taken by the distribution of unwanted software and features by certain companies.
Anyway @darren must have put a lot of hours into tracking this down. :cool:
That in my book is worth a lot he stuck with it.

Anyway best of regards
 
  • Like
Reactions: AAV
I had an issue but I don't recall what it was a few years back and it turned out it was Nahimic. I shut it down from start up in the App settings and all has been fine since then.
 
FWIW it's not just Nahimic. Many years ago an Nvidia graphics card installed a "high-definition audio" driver on my machine. I was shocked at how much it increased latency, and how disabling it improved the computer's performance. Ever since then, I disable the driver whenever it's "helpfully" re-enabled or re-installed with a driver update.
 
FWIW it's not just Nahimic. Many years ago an Nvidia graphics card installed a "high-definition audio" driver on my machine. I was shocked at how much it increased latency, and how disabling it improved the computer's performance. Ever since then, I disable the driver whenever it's "helpfully" re-enabled or re-installed with a driver update.
Yes, it's really annoying. I had to read so many forums, blogs and what not for months when I first had my 12th Gen CPU. I almost gave up to be quite honest.

The combo Windows 10/11 + Nvidia & modern CPUs is a nightmare for latency. You need to disable so many things that you didn't even know existed.
 
The thing with Nahimic it's not even Nvidia software, SteelSeries make peripherals Keyboards Mice and Headsets.

I survived with the onboard intel Graphics running 2 monitors for ages and would still be with that setup. It wasn't until I introduced a 3rd monitor as a touch screen I needed more HDMI/video ports so I installed a Graphics card, and then only with the bare bones video driver.
This just my own experience and as others have said, reading forums and blogs etc. for information.

Best of regards
 
I think one of the things that threw me (and also Presonus and AMD support) was that it didn't act like an "audio" driver issue. The specific behaviour that caused S1 to hang was opening certain plugin on the 2nd monitor window. So it really felt like a graphics driver issue.

Even now I have no idea (and no wish to understand why) an audio driver would cause this type of issue but it was really perplexing.

My big learning from this is that it's an important debug step to go to msconfig and close all non-windows driver to see if that solves the issue. If I'd done that early doors then this would have been a few days rather than few weeks problem.
 
@darren
I take it all is well and SO1 operating as expected.
On a lighter note, it's one of the strangest things, "you always find things in the last place you look". :ROFLMAO:
Philosophy 101.

That debug step is duly noted should it be needed. Cheers for the info.
I thought the GPU had an Audio driver conflict. The reality it was an unrelated driver that had worked it's way onto your system says a lot about having a computer dedicated to Daw use.

Kindest regards.
 
@sintil8 thanks, yes all been working fine since and I've been on it fairly intensively since a lot of things had backed up over the few weeks I was out of action.
 
My big learning from this is that it's an important debug step to go to msconfig and close all non-windows driver to see if that solves the issue.

The most important debug step for any DAW based computer is to disable all non-essential hardware prior to the OS even being installed. And then install only the drivers required for basic motherboard operation and your assorted audio hardware.

The mere presence of the 'Nahimic" driver indicates the OS is sensing availability of specific hardware (most likely on the motherboard) - that should not be enabled for any DAW - and it's clear this is some sort of gaming mobo if MSI/SteelSeries elements are being installed. All these devices should be disable in the BIOS.

This is no different from the scads of issues I have worked on over the years where users are dumbfounded when they discover RealTek or other cut rate drivers being present - and wonder why they have 32ms of latency and so on within their DAW.

VP
 
it's clear this is some sort of gaming mobo if MSI/SteelSeries elements are being installed. All these devices should be disable in the BIOS.
I'm wondering where in the BIOS you would disable this as I don't seem to be able to find that functionality?

For reference my motherboards is in my signature and I have American Megatrends Inc. 1403, 30/03/2022
 
Back
Top