Had this happen a couple times now randomly. The QC will stop showing incoming single on the I/O, will not produce any sound, AND the power button won’t respond. Screen will still work to change presets, etc.
I know the incoming signal is fine because it will register in my tuner that’s before the QC. I have to pull the power cable from the QC to reset it, and then it acts fine….
The only cause I can think of is that the XLR is plugged into the unit after it has booted up.
I leave everything plugged in on mine and it doesn’t affect bootups.
Sounds like hardware starting to fail. I’d contact Support@NeuralDSP.com immediately.
Have you tried a reset/restore?
Unfortunately leaving the XLR plugged in all the time isn’t possible when it’s on a pedalboard that tours a lot. Otherwise everything else is plugged in at all times.
This has now happened both live and in the studio. Usually with package tours I need to plug in my pedalboard so the QC can boot, and by that time have my power amp + guitar plugged in. FOH will plug in the XLR to a cable I have coming off the QC by the time it fully boots. This most recent time it wouldn’t pass audio was in the studio though.
Will contact support though, since it has been getting more frequent. It’s my second unit (first one wouldn’t boot at all) and only had this one for exactly a year.
Just a shot in the dark, because this happened to me yestreday… in the I/O menu, is your input is set to “Instrument” or “mic”? Mine was set to “mic” yesterday, and I got no signal (using 1/4 in).
Though, my situation is probably a little unique, because it only switched to “mic” because my cat sleeps on top of the unit and messed up all the settings lol
Totally reasonable question, but it was set to instrument. Seems to have only happened after I plugged in the XLR cable. Not sure if this somehow makes the unit glitch?
Hi, there, a bit late to the party, but exactly this issue started to happen during last night’s rehearsal with the band. Did you manage to solve this issue one way or another? I really hope it is not a hardware issue since I do not have warranty anymore..
Lol this kinda sounds like the problem i had experienced the first time 2 days ago: