Should be possible by cloning the SD card to a new one. Maybe somebody here did already try that and is able to confirm it? 
My point of contention, and not just with NDSP, but with all of the companies that deal with updates isâŚwhy not more frequent smaller updates. With CorOS 3.0, there are a ton of features being added, and working on ALL of them at the same time, is, what I assume, whatâs causing it to take longer.
âA small number of issues were found that have taken some time to resolve.â
Curious as to what the issues might be? Is it specific to PCOM? The Midi expansion? The implimentation of bulk actions? Side chaining? Or is it something as simple as the tracking on the pitch correction? Why did all of these features have to be developed and included simultaneously?
It just seems to mee that smaller, more frequent updates would be better for âappeasing the masses.â For all we know, the Circular Delay, might have been 100% complete and ready to roll out back in January, but itâs been sitting there waiting for PCOM to be complete. Side Chain may have been ready to go a month ago, etc. etc. So, in order to make a big splash, and release a gargantuan update, they are delaying 90% of the features to makes sure that the last 10% is perfectâŚ
And like I saidâŚall companies do this, well, except Line 6. Theyâve released updates without people even knowing that they were doing it. Thereâs nothing better than a surprise tiny update that includes 3 new drives and a couple bug fixesâŚ
I just want my pitch correction so that I can finally get rid of another pedal on my boardâŚ
3 Likes
But in this case, itâs 11:59 and they havenât even parked yet.
3 Likes
Thatâs a good question. I think a lot of users are expecting that now that theyâve gotten a lot of the BIG features out of the way, smaller updates should come more often. Guess weâll see if that actually happens.
1 Like
Or wouldnât you think it was weird if your friend showed up to the bar several weeks later?
5 Likes
Youâre right and for matching their initials promises, way more (little and big) updates are needed.
NDSP, are you still working on the synth block ??
Thatâs cool, bars round here are open til past 6am, itâs Friday and I have plenty of drinks at home too. 
Hi Xush
You and I have exchanged message before and Iâm a big fan of your posts and even more so your videos on YouTube
You make a fair point, and for the record if any posts I make are seen as âcomplainingâ I assure you theyâre not; but they probably are written with a great sense of frustration, having made feature requests, contacted Neural directly, and discussed often with other users here what are, IMHO, glaring flaws or omissions in some aspects of the QC UI. And sadly it feels very much to me (and I know this is also felt by others) that Neural seem very much more interested in focusing on the big headline stuff like Plug-in compatibility.
I donât want to start a whole conversation about that, as to be fair Plugin compatibility is something promised a long time ago - but I canât see why it would be difficult to include in the next big firmware update that provides plugins fixes for the poorly implemented things like mode selection (my greatest gripe and Iâm sure lots of you here will have seen me banging on about this repeatedly; I canât tell you the number of times Iâve changed preset accidentally while trying to change modes, because I accidentally press the preset down a fraction of a second before I press the tuner switch, in my attempt to press both simultaneously)
For the record I come from a background (commercial aviation) in which ergonomics and UI are absolutely paramount (for example you wonât see a system analogous to the mode changing on the QC on a Boeing Dreamliner, where simply mis-timing pressing two switches together has embarrassing consequences!) so Iâm pretty focused / easily bemused by what to me seems to be poorly thought through implementation. But the good news is these should be easy fixes; the problem remains however that Neural donât even seem to want to acknowledge and address the everyday issues, and instead want to keep on with the headline stuff.
All that said, Iâll be the first to offer suggestions and help to anyone here if I think I can offer it, and raising issues that I think should be address by Neural arenât a form of complaint but rather a way of highlighting things - hopefully constructively - to help make the QC user experience more enjoyable for everyone.
In short I like the QC a lot (Iâve owned mine for longer than Iâve owned any modeller so thatâs saying something) but Iâm not a fan-boy (of anything regardless of what itâs designed for; be it a camera, a modeller, a phone, a piece of scuba equipment) and I believe in constructive yet robust suggestions to help improve things. Then itâs down to the developers to prove that our thoughts and views are of value to them.
5 Likes
cool to see a fellow scuba diver 
While PCOM is certainly the dev teamâs white whale, they have revealed to us that several non-PCOM things will also be wrapped up in the CorOS 3.0 release (yay sidechains!). Working on an update as big as 3.0 means you have draw a line somewhere on the feature set.
Once 3.0 is outâand immediate hot fixes taken care of because we know that will happenâIâm betting the devs will have a lot more breathing room to tackle QoL improvements.
1 Like
I do hope so (and I have no idea what side-chains are so it will be interesting to see!) I would personally have preferred it if they fixed the basic stuff like getting the UI right first - but I do wait in hopeâŚ
I would assume itâs something along the lines of; lots of little updates still require lots of testing each time. Roll a bunch of updates out together, and it all gets tested by their user group simultaneously, rather than each feature getting rolled out to testers, each thing potentially coming back with bugs, then a subsequent small feature update causes issues with a previous one, each requiring a fix and more testing.
It could quickly become a clusterfuck.
2 Likes
That level of communication would certainly be preferable!
1 Like
I donât expect that our Quality of Life requests will be implemented right after the release of CorOS 3.0.
Initially, with the introduction of PCOM on the Quad Cortex, only the Gojira and Plini plugins will be available.
In my opinion, NDSP will first try to port all other X plugins to the QC.
I donât expect the feature requests to be implemented before then.
1 Like
Oh, yes., absolutely - to be clear I wasnât suggesting they roll out lots of small updates individually, I was saying that I wish theyâd fix all the little things that may be of minor importance individually but when combined with the numerous other small things, make the QC sometimes very frustrating to use. And Iâm perfectly happy for them to do this all at once in one big update.
1 Like
That would be a serious error of judgement. As a newish user I expect the 3.0 update to deliver what should have been in the unit a long time ago, thatâs why I waited so long to buy my QC. Not talking about the plugins, not waiting for those at all.
Whatâs going to happen when Line 6 release their next gen Helix? They had years and years to hone that to perfection and I expect nothing less than a fully loaded unit of outstanding quality when it comes out, possibly witin a year.
How many QC users will then stick around waiting until Neural finally delivers the functionality they promised when they released the unit? QoL improvements and bug fixes should be all the way on top of their to do list, together with the plugin stuff for those who bought the unit for that reason.
BTW, Iâm pretty amazed by the quality of my QC, even though a lot functions are still missing. My wife thinks I play much much better then before but thatâs 100% due to the amazing sound quality.
2 Likes
Sigh, another weekend, no update.
Highly doubt the helix is updating to a new hardware unit in the next year
There was an update 10 days ago 
3 Likes
Weâll see. At one point they must release something to replace 10 year old tech. Despite how good it may still be.