# QC broken?

**URL:** <https://unity.neuraldsp.com/t/qc-broken/17804>\
**Category:** Support\
**Tags:** quad-cortex, support\
**Created:** [April 5, 2025, 4:35pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804 "2025-04-05T16:35:15Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joe\_Garcia](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/joe_garcia/32/8111_2.png) [@Joe\_Garcia](https://unity.neuraldsp.com/u/Joe_Garcia)\
**Post date:** [April 5, 2025, 4:35pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/1 "2025-04-05T16:35:15Z")

</div>

I love my QC, but lately it is driving me insane.

Whenever I power it on (after it has been completely powered down) it boots into this super loud noise (see attached video) - the tuner is going bananas…

After a while it functions as it should… What is wrong here?

[VIDEO ON YT](https://youtube.com/shorts/h2-IwNc7lVU?feature=share)

Tried different (Neural) power supply, changed ALL cables and factory reset the device - all to no avail… HELP PLEASE!!!

---

<div class="post-metadata">

**Author:** ![RN69](https://avatars.discourse-cdn.com/v4/letter/r/8797f3/32.png) [@RN69](https://unity.neuraldsp.com/u/RN69)\
**Post date:** [April 6, 2025, 11:56pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/2 "2025-04-06T23:56:25Z")

</div>

Same trouble happening here…  
Now I assume this might be a software bug, not a hardware failure.  
I’ve been suffered from this since I updated to CorOS 3.1.0(latest version).

---

<div class="post-metadata">

**Author:** ![electricblank](https://avatars.discourse-cdn.com/v4/letter/e/ea666f/32.png) [@electricblank](https://unity.neuraldsp.com/u/electricblank)\
**Post date:** [April 7, 2025, 5:41am UTC](https://unity.neuraldsp.com/t/qc-broken/17804/3 "2025-04-07T05:41:52Z")

</div>

I used to get the same thing until I started leaving it plugged in and manually turn it off and on with the button, maybe it’s something to do with loading the last preset in from a cold boot, the solution could be to just update it to be muted until everything is loaded correctly.

---

<div class="post-metadata">

**Author:** ![Joe\_Garcia](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/joe_garcia/32/8111_2.png) [@Joe\_Garcia](https://unity.neuraldsp.com/u/Joe_Garcia)\
**Post date:** [April 7, 2025, 12:27pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/5 "2025-04-07T12:27:31Z")

</div>

→ “I used to get the same thing until I started leaving it plugged in and manually turn it off and on with the button”

How else would you power it off and on?

Thx for the tipp tough. I have the same feeling (SW defect, not HW). Will try to have it boot into a totally quiet preset - then change manually to the next one (wich is my main tone) after the issue has gone (usually 1-2 minutes).

It´s a workaround tough not an permanent solution - I´d be happy if anyone had a better way of fixing this…

---

<div class="post-metadata">

**Author:** ![jndsp](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@jndsp](https://unity.neuraldsp.com/u/jndsp)\
**Post date:** [April 7, 2025, 2:02pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/6 "2025-04-07T14:02:42Z")

</div>

Hey Joe,

Sorry to see that you’re having trouble!

Please send the video and your issue to our support team on [support@neuraldsp.com](mailto:support@neuraldsp.com) - they will be able to help you out here.

---

<div class="post-metadata">

**Author:** ![Joe\_Garcia](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/joe_garcia/32/8111_2.png) [@Joe\_Garcia](https://unity.neuraldsp.com/u/Joe_Garcia)\
**Post date:** [April 7, 2025, 2:31pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/7 "2025-04-07T14:31:47Z")

</div>

Hi there,

thx for reaching out. Email is sent. I hope to hear back soon.

Regards

---

<div class="post-metadata">

**Author:** ![jamsden](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/jamsden/32/1607_2.png) [@jamsden](https://unity.neuraldsp.com/u/jamsden)\
**Post date:** [April 7, 2025, 4:11pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/8 "2025-04-07T16:11:38Z")

</div>

I noticed the 3.1 release notes recommend using the power on/off button to power of QC instead of removing the power. There could be something cached that needs to be flushed to the SSD when powering off.

---

<div class="post-metadata">

**Author:** ![Joe\_Garcia](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/joe_garcia/32/8111_2.png) [@Joe\_Garcia](https://unity.neuraldsp.com/u/Joe_Garcia)\
**Post date:** [April 7, 2025, 4:23pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/9 "2025-04-07T16:23:50Z")

</div>

I have never NOT used the power on/off function when shutting down the QC.

Who does such barbaric things to an electronic device?

---

<div class="post-metadata">

**Author:** ![electricblank](https://avatars.discourse-cdn.com/v4/letter/e/ea666f/32.png) [@electricblank](https://unity.neuraldsp.com/u/electricblank)\
**Post date:** [April 7, 2025, 11:48pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/10 "2025-04-07T23:48:00Z")

</div>

> [@Joe\_Garcia](#):
>
> How else would you power it off and on?

i’ve been leaving it plugged in and use the power button rather than unplugging and having it automatically power on when it’s plugged back in  
the digital distortion sound it makes never lasted more than maybe 10 second for me though switching presets or just loading a different preset when powering on seems to “fix” it

---

<div class="post-metadata">

**Author:** ![Joe\_Garcia](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/joe_garcia/32/8111_2.png) [@Joe\_Garcia](https://unity.neuraldsp.com/u/Joe_Garcia)\
**Post date:** [April 8, 2025, 11:58am UTC](https://unity.neuraldsp.com/t/qc-broken/17804/11 "2025-04-08T11:58:04Z")

</div>

As I use the Quard Cortex in different places (when on tour or playing shows) there is no option of “leaving it on power”. After the show I pack it back in the pelican it mostly lives in…

---

<div class="post-metadata">

**Author:** ![xush](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/xush/32/5100_2.png) [@xush](https://unity.neuraldsp.com/u/xush)\
**Post date:** [April 9, 2025, 4:26pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/12 "2025-04-09T16:26:15Z")

</div>

when the QC was first released, they officially recommended pulling the plug to shut down.  
Many users were understandably concerned when they reversed those instructions at the 3.0 manual revision.

---

<div class="post-metadata">

**Author:** ![Joe\_Garcia](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/joe_garcia/32/8111_2.png) [@Joe\_Garcia](https://unity.neuraldsp.com/u/Joe_Garcia)\
**Post date:** [April 9, 2025, 5:49pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/13 "2025-04-09T17:49:54Z")

</div>

That is a horrible idea…

Just stripping any electronic device from power is not good for a device with so many components I assume…

Luckily it seems that Neural has fixed this.

---

<div class="post-metadata">

**Author:** ![Sbrilly](https://avatars.discourse-cdn.com/v4/letter/s/7ea924/32.png) [@Sbrilly](https://unity.neuraldsp.com/u/Sbrilly)\
**Post date:** [April 10, 2025, 11:58am UTC](https://unity.neuraldsp.com/t/qc-broken/17804/14 "2025-04-10T11:58:21Z")

</div>

Hey how do they fixed it?

---

<div class="post-metadata">

**Author:** ![thebluesman666](https://avatars.discourse-cdn.com/v4/letter/t/90ced4/32.png) [@thebluesman666](https://unity.neuraldsp.com/u/thebluesman666)\
**Post date:** [April 12, 2025, 3:29pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/15 "2025-04-12T15:29:09Z")

</div>

I turn On/Off the device (QC) with the power bottom or the Cortex control power feature into the CC app.

I never pull the plug out the power source.

Remember it’s just like a computer. I assume it need a proper shutdown in order to avoid futur bugs or glitch.

---

<div class="post-metadata">

**Author:** ![dk55432](https://avatars.discourse-cdn.com/v4/letter/d/85e7bf/32.png) [@dk55432](https://unity.neuraldsp.com/u/dk55432)\
**Post date:** [April 25, 2025, 11:28pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/16 "2025-04-25T23:28:24Z")

</div>

I just wanted to add that I have the same problem on power up. I have to immediately put it in tuner mode so that machine noise doesn’t blow out everybody’s eardrums. The tuner acts berserk during this period.

Once the unit has “warmed up” and the tuner is actually responding to my input, I know it’s safe to take it back out of tuner mode.

I live in a cold climate, and I transport my equipment to practices. I’ve noticed that when the unit is physically cold, it takes longer, eg 10 minutes, in order to “warm up”, before it’s playable.

---

<div class="post-metadata">

**Author:** ![Joe\_Garcia](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/joe_garcia/32/8111_2.png) [@Joe\_Garcia](https://unity.neuraldsp.com/u/Joe_Garcia)\
**Post date:** [May 19, 2025, 8:06pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/17 "2025-05-19T20:06:08Z")

</div>

Interresting…

So far, I did not notice any difference in behaviour when the climate changes. I bought a new power supply from Thomann, my old one had two strains of cable, the new one has just one. Still no change. I have stopped the time it takes the device to go from “berserker” mode to normal function. Usually it takes about three minutes before it works as it should.

I have tried this “internet hotfix” today:

Switched on all “Ground lift” buttons for all outputs. Saved this as global setting. Rebooted the device and switched all “Ground lift” buttons off - saved again as global setting.

Whilst the problem is still not gone entirely, the time it takes the device to eeturn out of “freak mode” is now about 26 seconds.

Weird - but hey, the things you do for the things you love… I hope a SE update will fix this…

---

<div class="post-metadata">

**Author:** ![Joe\_Garcia](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/joe_garcia/32/8111_2.png) [@Joe\_Garcia](https://unity.neuraldsp.com/u/Joe_Garcia)\
**Post date:** [June 26, 2025, 1:02pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/18 "2025-06-26T13:02:38Z")

</div>

Problem still exists - weird that noone seems to have a solution for this.

Still hoping for that Software Update…

---

<div class="post-metadata">

**Author:** ![xush](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/xush/32/5100_2.png) [@xush](https://unity.neuraldsp.com/u/xush)\
**Post date:** [June 26, 2025, 5:32pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/19 "2025-06-26T17:32:42Z")

</div>

what did Support say?

---

<div class="post-metadata">

**Author:** ![Joe\_Garcia](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/joe_garcia/32/8111_2.png) [@Joe\_Garcia](https://unity.neuraldsp.com/u/Joe_Garcia)\
**Post date:** [June 27, 2025, 5:27am UTC](https://unity.neuraldsp.com/t/qc-broken/17804/20 "2025-06-27T05:27:12Z")

</div>

Support was absolutely willing to help. They offered to send in the device and repair it (free of charge, all I would have to pay is shipping).

Unfortunately, I cannot be without the device for potentially multiple weeks as I need it on the daily at the moment.

---

<div class="post-metadata">

**Author:** ![aa7bq](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@aa7bq](https://unity.neuraldsp.com/u/aa7bq)\
**Post date:** [July 5, 2025, 6:01pm UTC](https://unity.neuraldsp.com/t/qc-broken/17804/21 "2025-07-05T18:01:12Z")

</div>

If NDSP knows what’s wrong here, then why can’t they TELL us. Why can’t the condition have a name or diagnosis at this point? I’ve been living with this crap for 2 years and I’m blown away by the lack of affirmative response from the manufacturer. This support forum is designed to let users “figure it our for themselves” while the real support people won’t dare set foot in here.

[Next page](https://unity.neuraldsp.com/t/qc-broken/17804.md?page=2)
