I get a disturbing weird noise when i connect my new NI Komplete Audio 6 to Yamaha HS7

Ableton23Robin
Ableton23Robin Member Posts: 6 Newcomer
edited October 22 in Other Software & Hardware

Wednesday, July 12, I accidentally spilled some water over my audio interface, this wasn't very much, but enough to definitely immediately pull out my audio interface. After drying I noticed that a little bit of water behind my desk had also fallen onto my subwoofer (Yamaha HS8s), This did seem to be mostly just along the top and I just dried that off as well. After everything dried I tested to see if everything was okay. Then I heard a loud disturbing noise coming from my speakers. After this I immediately turned them off and waited a day to let the interface dry. The next day I tried again and again had a weird sound, I immediately took everything out and did not plug the interface in again. I then was able to use a Focusrite interface from a buddy to test everything, I did this to make sure my speakers were not broken and just my interface. I used this for 4 days and everything seemed, ok but I very occasionally had a quiet, buzzing sound similar to a record player. However, this was always resolved When I rebooted my computer. I had also plugged the temporary In the front of my computer and not directly into my motherboard, so I suspected that it could also be due to this. It definitely wasn't super distracting either and would be a problem I could live with. I did buy a new interface right away and I chose the Native Instruments Komplete audio 6. After I plugged it in, everything was perfect, I was playing music for at least half an hour. without problem and I was happy And reassured. But suddenly a strange Robot-like brr came whenever I played music. This sound does not play continuously, but is occasional. As a result, I of course immediately pulled everything out again. Then I thought, Maybe it's also my subwoofer after all so that's why I connected my studio monitors (Yamaha HS7) once back to my audio interface. But this same sound was also coming from my speakers. Then I thought maybe it was my cables, so I went and got new cables. But the same problem keeps happening. Now I am extremely confused, because my speakers have never come in contact with water and have never made a huge loud noise, so that would have blown them apart. I can't find an answer anywhere online what the problem could be and if my speakers could be broken because my interface came in contact with water. It could also very coincidentally just be a problem with the interface, but this seems very unlikely to me, especially after I was able to use everything perfectly for half an hour first. I now absolutely do not know what to do, what the problem could be and how I could troubleshoot further.

 

  Update: I've been using the speakers with the focusrite and everything is working fine, and i have hooked up my new interface to some edifier bookshelf speakers that I have and that also seems to be working fine... so I'm lost

Update 2

I used a DI box in combination with my new interface (native instruments), everything was perfect with my 2 speakers for about 30 min. So I plugged in my subwoofer, everything was perfect for about 10 min. I was finally able to breath a little and then the same noise came back, there is no consistent patern of problem, it just randomly occurres. My speakers also seem to be working fine for quite some time so they are not fully broken or anything…

NOISE.zip

Best Answer

  • Ableton23Robin
    Ableton23Robin Member Posts: 6 Newcomer
    Answer ✓

    PROBLEM FIXED !!!!! : After chatting with a employee of native instruments he gave the the genius idea to check if i also got the noise when i listend through headphones that are connected to my interface. I don't know how i didn't think of this before BUT THANK GOD i heard it through the headphones aswell !! This meant that my speakers were not broken so u can imagen how happy i was to hear that lol. It was just one big coinincidence because apperently it was just a software issue. After all the blood sweat and tears, a simple bios and chipset update fixed the problem!

Answers

This discussion has been closed.
Back To Top

Categories