# Volume flashing

**URL:** <https://unity.neuraldsp.com/t/volume-flashing/11384>\
**Category:** Bug Reports\
**Created:** [July 3, 2023, 9:49pm UTC](https://unity.neuraldsp.com/t/volume-flashing/11384 "2023-07-03T21:49:25Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Okimotdm](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@Okimotdm](https://unity.neuraldsp.com/u/Okimotdm)\
**Post date:** [July 3, 2023, 9:49pm UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/1 "2023-07-03T21:49:25Z")

</div>

**CorOS Version:** 2.0.3

**Describe your issue:**  
When touch the master volume knob there are times it will flash values passing from a random min and max. I keep the volume at 50 typically and if I go up or down 10 there are times it will flash a value above and below the new value for an extended period of time. I set to 40, it may flash and 39 to 42 at random quickly.

I typically look the volume when playing live so this doesn’t create problem but it is an odd issue, like the volume knob sensor is dirty

**Steps to reproduce your issue:**

1. Step 1
2. Step 2
3. Step 3

**I expected this to happen:**  
When I do x, I expect y to happen

**I have tried the following things:**

- I have tried x
- I have tried y
- I have tried z

---

<div class="post-metadata">

**Author:** ![HonestOpinion](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/honestopinion/32/3398_2.png) [@HonestOpinion](https://unity.neuraldsp.com/u/HonestOpinion)\
**Post date:** [July 4, 2023, 7:56am UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/2 "2023-07-04T07:56:49Z")

</div>

I would contact Neural support. I have seen this issue reported by a few users.

---

<div class="post-metadata">

**Author:** ![manrik](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/manrik/32/4231_2.png) [@manrik](https://unity.neuraldsp.com/u/manrik)\
**Post date:** [July 4, 2023, 9:30am UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/3 "2023-07-04T09:30:24Z")

</div>

sometimes this happens to me too

---

<div class="post-metadata">

**Author:** ![purp](https://avatars.discourse-cdn.com/v4/letter/p/f07891/32.png) [@purp](https://unity.neuraldsp.com/u/purp)\
**Post date:** [July 4, 2023, 9:47am UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/4 "2023-07-04T09:47:24Z")

</div>

same with my unit, I contacted the support and they asked me to send the unit back to them to give it a look, but I need it for the time being so maybe I’ll send it a few months later. I haven’t tried resetting to factory settings yet, but I’m gonna try it soon. I’ll let u know if it works. As it is, it is just a little bit annoying and doesn’t affect me much, since I keep the volume wheel always at 100, but it would be nice not to have this problem.

---

<div class="post-metadata">

**Author:** ![Okimotdm](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@Okimotdm](https://unity.neuraldsp.com/u/Okimotdm)\
**Post date:** [July 4, 2023, 1:18pm UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/5 "2023-07-04T13:18:57Z")

</div>

Thanks for the feedback. Good to know it isn’t just me. it doesn’t cause a problem cause I just lock the volume and it goes away. Thx again

---

<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:** [July 4, 2023, 5:36pm UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/6 "2023-07-04T17:36:01Z")

</div>

I believe this is an actual bug they are aware of, I’ve read that somewhere but can’t seem to find it now. Supposedly doesn’t really affect anything, more of a glitch with the graphics. Hopefully addressed in forthcoming update

---

<div class="post-metadata">

**Author:** ![ChrisFer](https://avatars.discourse-cdn.com/v4/letter/c/3be4f8/32.png) [@ChrisFer](https://unity.neuraldsp.com/u/ChrisFer)\
**Post date:** [July 9, 2023, 7:39pm UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/7 "2023-07-09T19:39:07Z")

</div>

Hi! I do have this issue since around 1 year.  
Comes and goes, but i have notice that i can recreate the issue if i tried to ultra carefully dial an specific random number and microadjust the volume knob.  
Then after some seconds, it starts to flicker from 0 to 50 and random values.

---

<div class="post-metadata">

**Author:** ![purp](https://avatars.discourse-cdn.com/v4/letter/p/f07891/32.png) [@purp](https://unity.neuraldsp.com/u/purp)\
**Post date:** [July 9, 2023, 8:16pm UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/8 "2023-07-09T20:16:16Z")

</div>

I bought mine last September. I didn’t have this problem for the first few months, I believe something got messed up with the update 2.0. Hopefully, it’s just a software thing that will be fixed with the coming updates.

---

<div class="post-metadata">

**Author:** ![TheStarOfOrion](https://avatars.discourse-cdn.com/v4/letter/t/dbc845/32.png) [@TheStarOfOrion](https://unity.neuraldsp.com/u/TheStarOfOrion)\
**Post date:** [July 29, 2023, 6:55am UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/9 "2023-07-29T06:55:53Z")

</div>

I have the same problem with my Quad Cortex the last couple of months. I think it appeared after the last update. Volume jumps are very annoying. I hope that it will be fixed in the next update.

---

<div class="post-metadata">

**Author:** ![TheStarOfOrion](https://avatars.discourse-cdn.com/v4/letter/t/dbc845/32.png) [@TheStarOfOrion](https://unity.neuraldsp.com/u/TheStarOfOrion)\
**Post date:** [August 14, 2023, 4:50pm UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/10 "2023-08-14T16:50:41Z")

</div>

[![](https://us1.discourse-cdn.com/flex020/uploads/neuraldsp/original/2X/1/1b4098fbe5fb832e017b25fef39f6a13df4b4d82.jpeg "Volume issues on Quad Cortex") ](https://www.youtube.com/watch?v=0scq0ygsZ_U)

---

<div class="post-metadata">

**Author:** ![MP\_Mod](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@MP\_Mod](https://unity.neuraldsp.com/u/MP_Mod)\
**Post date:** [August 14, 2023, 5:03pm UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/11 "2023-08-14T17:03:16Z")

</div>

I would definitely email [support@neuraldsp.com](mailto:support@neuraldsp.com) so that they can log the issue and provide resolution via repair and or firmware update if considered a bug.

---

<div class="post-metadata">

**Author:** ![VapnFagan](https://avatars.discourse-cdn.com/v4/letter/v/b5a626/32.png) [@VapnFagan](https://unity.neuraldsp.com/u/VapnFagan)\
**Post date:** [August 16, 2023, 11:38am UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/12 "2023-08-16T11:38:25Z")

</div>

I also have this issue. Purchased my unit new about a yr ago. Never had it before till i did one of the last 2 updates. It doesnt do it all the time. I didnt know wtf was happening.

---

<div class="post-metadata">

**Author:** ![NuttyViperDriver](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/nuttyviperdriver/32/3245_2.png) [@NuttyViperDriver](https://unity.neuraldsp.com/u/NuttyViperDriver)\
**Post date:** [August 26, 2023, 12:33pm UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/13 "2023-08-26T12:33:15Z")

</div>

I’ve got the same. Seemed to happen after a much earlier update although that might just be a coincidence? Is the volume knob a pot on the QC?

Anyone tried to fix this themselves?

Cheers

James

---

<div class="post-metadata">

**Author:** ![Okimotdm](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@Okimotdm](https://unity.neuraldsp.com/u/Okimotdm)\
**Post date:** [August 29, 2023, 3:13am UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/14 "2023-08-29T03:13:13Z")

</div>

Don’t do it yourself - you may void the warranty. Support is seamless, the only thing u have to manage is not having your QC for a couple weeks. I feel naked defaulting back to analog but it’s an easy problem to have. Contact support

---

<div class="post-metadata">

**Author:** ![NuttyViperDriver](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/nuttyviperdriver/32/3245_2.png) [@NuttyViperDriver](https://unity.neuraldsp.com/u/NuttyViperDriver)\
**Post date:** [October 26, 2023, 5:29am UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/15 "2023-10-26T05:29:33Z")

</div>

Just a final post on this. As advised, I contacted support who were **excellent**. They arranged at their cost for my QC to be sent to them, repaired and returned. Seamless.  
Very impressed.

---

<div class="post-metadata">

**Author:** ![suraisoumyajit](https://avatars.discourse-cdn.com/v4/letter/s/b38774/32.png) [@suraisoumyajit](https://unity.neuraldsp.com/u/suraisoumyajit)\
**Post date:** [October 28, 2023, 2:05pm UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/16 "2023-10-28T14:05:27Z")

</div>

Hello,

I’m having same problem with my unit. Dropped an email to the support. Haven’t got any reply yet.

Do i need to send the unit ? I thought it could be a software issue but seems something related to hardware.

Thanks

---

<div class="post-metadata">

**Author:** ![Fischer96](https://avatars.discourse-cdn.com/v4/letter/f/9fc29f/32.png) [@Fischer96](https://unity.neuraldsp.com/u/Fischer96)\
**Post date:** [December 10, 2023, 11:57am UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/17 "2023-12-10T11:57:16Z")

</div>

Hey, did anyone find a fix for this or is this indeed a hardware issue? I also had the feeling it started after updating my Quad Cortex but not 100% sure though.

Will probably send it in for repair soon.

---

<div class="post-metadata">

**Author:** ![Okimotdm](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@Okimotdm](https://unity.neuraldsp.com/u/Okimotdm)\
**Post date:** [December 10, 2023, 3:03pm UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/18 "2023-12-10T15:03:00Z")

</div>

You will have to send it in. They will ask for a video to confirm, then they ask you to send it back with box/cables. They fox and send back in about 10 days for me. Just long enough to really start to miss it but it’s perfect now. But I also just set it at 100% and run levels to a board / headphones.

---

<div class="post-metadata">

**Author:** ![purp](https://avatars.discourse-cdn.com/v4/letter/p/f07891/32.png) [@purp](https://unity.neuraldsp.com/u/purp)\
**Post date:** [December 10, 2023, 4:34pm UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/19 "2023-12-10T16:34:50Z")

</div>

What if this doesn’t get fixed? Will it affect other things in the long run, or are we good if we set the wheel always at 100?

---

<div class="post-metadata">

**Author:** ![suraisoumyajit](https://avatars.discourse-cdn.com/v4/letter/s/b38774/32.png) [@suraisoumyajit](https://unity.neuraldsp.com/u/suraisoumyajit)\
**Post date:** [December 20, 2023, 1:12am UTC](https://unity.neuraldsp.com/t/volume-flashing/11384/20 "2023-12-20T01:12:14Z")

</div>

This happened with my unit as well.  
Check out the yt link below.

[![](https://us1.discourse-cdn.com/flex020/uploads/neuraldsp/original/2X/5/50c63f3b4191f28ab58398a4d91963299efeed1b.jpeg "Quad Cortex Volume issue - after CorOS 2.2 update") ](https://www.youtube.com/watch?v=6pQNqOdARYU)

QC support team asked me to send my unit for repair. Got it done within a week.

[Next page](https://unity.neuraldsp.com/t/volume-flashing/11384.md?page=2)
