NDSP support again not answering for weeks

Hey NDSP how about answering? Or should I just file a lawsuit at this point?

more then 20 videos of bugs

1
Input bug that sometimes makes the incoming signal very quiet. By changing the impedance settings it jumps back to normal.

2
I/O Settings - USB - Out Signal of instrument not detected when no USB signal is incoming at the same moment. Only a visual bug, as sound still works.

3
WIFI / Cloud not working. Eventhough every other device in the same spot has very good signal, the QC doesn’t and only connects to cloud at random. Some days not at all, some days it works. The signal strength doesn’t seem to matter for this.

4
When having trouble connecting, the QC also freezes for random periods of time, reaching from a few seconds to minutes.

5
In and/or Outputs not working. This bug happens at random and is only fixable by restarting the QC.

6
Send 1 output signal is very low. Not fixable. QC unit was exchanged, so it seemed to be an hardware issue.

7
Global EQ sometimes doesn’t work although there is no indication that the core is overloaded. In this case, removing the looper from the lane, thus reducing the number of blocks on the first lane leads to the Global EQ not working anymore.

8

Loading some presets leads to the QC crashing. Warning screen says “something went wrong”. Support got reports and checked the QC unit after sending it in but didn’t find anything wrong with it.

3
WIFI still not working a few patches later. Hotspot doesn’t solve it either.

3+4
WIFI and Hotspot still not working a few patches later. QC still freezes when failing to connect.

9
Editing preset names and saving them leads to the QC crashing. This problem was present on CorOS 2.0.2 and solved by the next firmware update.

10
QC crashing at random. No text or warning to it.

11
All sounds in and out stop working at random. Sometime later, a few seconds to minutes, a warning pops up and the QC restarts itself.

12
QC doesn’t turn on and freezes. Removing the power supply and restarting the unit sometimes works instantly, sometimes not. This occurred since the latest firmware Coros 2.1.0. but not directly after the update but a few boot ups later.

13
QC suddenly makes insanely loud noises. Coros 2.1

14
QC / Cortex Control (CC) suddenly jumps in volume. This can happen by tapping buttons on the QC but sometimes also happens at random. At the very start, the volume wheel of the QC is turned all the way up. In CC, it is set to 74. You can hear music coming out of the speakers connected to the QC. At min 0:28 you can hear the volume jump up to full. Both the QC and CC don’t show this, but you can hear it. It becomes clear what happaned when at min 0:49 you can hear the volume drop a lot, even though the volume in CC only gets reduced by 1 from 74 to 73.

15
QC freezes (when in tuner mode). Restarting is the only option to resolve. CorOs 2.3.1

16
Switching scenes comes with delay. CorOs 2.3.1

17
QC freezes input receives guitar signal but no sound.

18
Capture process randomly doesn’t work at times. In this case, the pedal to capture is set to very high output level. But it still passes the sanity check. Then I turn down the output of the pedal. Now it doesn’t pass the sanity check.

19
Splitters Crossover not working

20
Splitters bugged, getting removed when editing the grid

21
QC freezes randomly, only restarting solves the issue

22
Preset Names are shown wrong, grid shows it correctly

23
Freeze signal isn’t constant but moves about 9dB up and down over a cycle of about 30-60 seconds

24
Cortex Control lagging for seconds when editing a block on the grid

Please send DM with your email and contact details. I will escalate directly to support which unfortunately is all I can do.

1 Like

Wow, I don’t have any of these issues and my unit is one of the first ones off the block. I don’t plug my QC into a computer so I haven’t experienced any of your issues. The only one I get is when changing presets while a note is ringing results in a huge volume spike.

I can see why you’d be frustrated though.

Just for transparency: support has answered and I returned the QC.

1 Like