The Quad Cortex November Development Update is up

[MP_Mod]

2.0 is going through BETA currently just like all previous and future updates. It’s a process to test and ensure a bug free deployment. Just as all previous and future updates, there are possibilities of issues making it through the BETA process. The BETA process is long and drawn out to identify any issues just for that reason. 2.0 will be the largest update yet and we appreciate the patience ‘the large majority’ of the customers are showing. If issues arise post update(s), they will be addressed as they have always been. Also, to note there is no current process for reversing the firmware version.

[HonestOpinion]

@hiromasa

am looking forward with great anticipation to the next major update of Quad Cortex, version 2.
And it seems to me that the completeness and stability of this update will determine the future of the Quad Cortex. If the update is full of glitches, it will mean that the Quad Cortex is a gadget and not a musical instrument, and I fear that.
So I hope the next 2.0 update will be as stable and complete as possible.
Then the reputation of the Quad Cortex as a new generation of gear that can be used as serious equipment will be established.

I don’t believe any one update will determine the QC’s status as a “gadget” versus a “musical instrument” unless they offer a gaming controller and the latest version of Fortnite with it That seems a bit extreme. I do agree that putting out stable code definitely is a better look for any company.

At a certain point though, you have to put your latest firmware out in the wild. If there are still bugs, so be it, hopefully they are minor and can be addressed shortly after by a hot fix minor version of the firmware. Once a piece of software is pushed out to the wider user base, they may well find bugs that the smaller beta testing team didn’t. The more feature rich and complex the code gets, the more likely that is to happen. User communities discovering arcane and hard to find bugs is a fairly common occurrence and one that usually shouldn’t result in wholesale condemnation of the device.

Like any artist, developers always want to wait until their “painting” is perfect before it is seen by the public. That is why there are project managers and marketing directors who also have a say on release dates.

I am a huge proponent for any device to have a mechanism to roll back to an earlier version of the firmware; just in case. Hopefully the QC will develop this capacity in the future in the event that either a new firmware version causes a catastrophic failure, or in the event that a new bug is a showstopper for a small segment of their users. It is good to have the flexibility. Perhaps QC will offer a USB/computer based firmware update mechanism at some point as an alternative or backup procedure for the WIFi update process.

[HonestOpinion]

@MP_Mod

2.0 is going through BETA currently just like all previous and future updates. It’s a process to test and ensure a bug free deployment. Just as all previous and future updates, there are possibilities of issues making it through the BETA process. The BETA process is long and drawn out to identify any issues just for that reason. 2.0 will be the largest update yet and we appreciate the patience ‘the large majority’ of the customers are showing. If issues arise post update(s), they will be addressed as they have always been. Also, to note there is no current process for reversing the firmware version.

Weird, I could see you responding as I wrote my comment directly above. Due to my tendency to being a bit long-winded it took me a few seconds longer but our responses were shockingly similar. Instant validation, I like it!

[MP_Mod]

Good minds think alike
I think this thread has run its course and then some.

Thanks everyone for all your thoughts and feedback!