Agreed, whining without constructive criticism doesn’t help anyone.
I don’t agree on the good vibe thing though, because I think as a company you reap what you sow. And if you treat your customers in a bad way, you can’t expect anything else but complaints.
I hear the criticism but the constructive part seems to be missing. Have you submitted a bug report or contacted NDSP about this? If the extended boot time is universal or even just common, I’m sure they will do what they can to improve it in future updates. It’s a complex machine that just got more complex. Even with the most advanced coding, there are limits to how fast start-up can be made. If a fast boot is a high priorty and you’re not willing to wait for improvement, perhaps buying a simpler but faster modeler would be your best course of action.
My constructive part was measuring the time and posting it here so more people can share their experience. And after seeing that it’s not a problem only I have I did report it.
About the complexity of the QC, well, Helix is faster. So is Axe FX, so is pretty much any modeller I know of. But again, that’s not even my point. My point is that the boot time got increased with a new update and without telling.
And no, I am not buying another modeller because a software update made my QC slower. I want NDSP to not make it slower in the first place.
Thanks for making them aware. Have you considered reverting to the previous OS? If a faster start‐up is more important to you than the new features, that might be a viable option. I’m not sure of the procedure but I assume it’s possible.
Yes sure. And I’d be happy to do so. Sadly it’s not. That’s another thing I simply can’t wrap my head around.
Unfortunately, once you update to CoreOS 3.0, you won’t be able to downgrade again per NDSP as @mgorn stated. I don’t know the reason why but they were specific on not being able to downgrade etc.
I just turn it on a minute before I want to use it, no biggy.
“I just turn it on a minute before I want to use it, no biggy.”
Sure…like waiting for the digital tubes to warm up. 
On jtm studio Marshall manual recommends two minuts of warmup 
Today the world Is too much fast for tubes
1st world problems, take that minute to reflect on your day and how wonderful it is to be alive 
Yes! This forum is no place for positivity!
Well, it IS a computer right? A faster boot time is preferable but I can live with it.
Compared to a lot of folks here saying “no big deal” I find the boot time issue to be a pretty major problem as a guitar tech, and one of the reasons I haven’t pressed more to get the bands I work for switched over to the QC. For home use or whatever, sure, who cares. For live it means a power blip or issue on stage could mean what feels like an eternity of dead air. I work a lot of international festivals and so forth with short changeovers and things where there’s a rush to get the band on stage and everything patched and setup, and there’s often a lack of control of the timing --get the risers out, boards placed, everything patched and leads dressed, tuned and line checked, picks and drinks and towels and set lists, etc–the time goes fast. Waiting 90 seconds for the unit to boot if anything else needs troubleshooting would add stress. Add in that for some shows I’m not getting the set list until minutes before changeover, or there’s a last minute edit, and the boot time has been at least a factor in not wanting to rely on the QC for live use. The bands I’ve worked for that are on fractals had them racked up off stage with just the foot controllers on their boards, meaning power cycling was rarely as much of an issue. I know plenty of bands are making them work in live settings but it’s fair to say it makes me nervous and I definitely see it as a consequential draw back.
If you have a temporary power failure, how long does it take to get the FOH rig and lighting rig up and running? I agree that 70 seconds (average boot time for my QC) is excessive but, compared to the advantages that QC brings to the table, is an extra few seconds really that big of a deal? For me, superior tone and navigation makes it worth the compromise. Could a small UPS (with battery backup) reduce the risk? Hopefully NDSP will be addressing this issue “soon”.
I was timing boot up around 40 seconds before I updated to 3.0.0, which is the fastest I’ve seen it, but now on 3.0.0 it is longer. You can say it’s no biggie, but I’ve had moments in gigs where the tuner/tap tempo stops working and I just can’t be rebooting it mid set - even after the end of a song. It’s just that little too long to be waiting before I get my guitar signal back. In a perfect world, we’d never have to reboot at a gig
I’d recommend submitting to Support@neuraldsp.com if anyone is hoping to see the boot times addressed. I haven’t seen it acknowledged as an issue, so it might not be on the radar yet unless enough users report it.
Boot time of some competing devices:
As a software developer, I can’t quite understand why an embedded system like the Quad Cortex would need 70 seconds just to boot. The device might be complex, but it feels like the software isn’t optimized at all for fast startup. It seems as though everything is being loaded and/or initialized before the device is ready, even components that aren’t part of the current preset. That would explain the additional load time since the plugin blocks are available—more blocks, more time. Wonder what additional plugins will do to the boot time…
Honestly, it’s been a while since I’ve had to wait 70 seconds for ANY computer to be ready to use.
HX stomp: 12 secs
QC CorOs 3.0.1 now 98 secs
Seriously, I am done with this. Good luck to all.
Probably the ilok check?
QC calls Cloud, Cloud ilok auth check and QC return infos?
Fractal takes way longer than 10s, at least with a recent firmware (and DynaCabs).