- Messages
- 4,252
Well, the blog posts are extraordinary - we know that much.
I'd better just finish reading this thread. I haven't decided whether to defend NDSP or make fun of them yet.
["why not both" meme]
CorOS 2.0 when?
- Thread starter Whizzinby
- Start date
James Freeman
Rock Star
- Messages
- 3,191
NDSP are "show first, think later" type of company, I imagine when they actually started working on hybrid mode they got a wake up call from reality.
- Messages
- 4,252
- Messages
- 13,577
i like jaws 3Wait, what? Again? Hybrid Mode 2??
- Messages
- 3,744
i like the Quad Cortexi like jaws 3
- Messages
- 3,744
On a couple of other fronts I'm inclined to agree. But Hybrid mode should have been (relatively) low-hanging fruit.
Lysander
Shredder
- Messages
- 1,890
On a couple of other fronts I'm inclined to agree. But Hybrid mode should have been (relatively) low-hanging fruit.
Yeah, it's weird. Not that i know shit about the QCs architecture, but button mapping functionality should by far one of the easiest things to modify. No idea why they kept pushing it back instead of rolling the feature out with an incremental update - you have WiFi downloads, for Pete's sake.
James Freeman
Rock Star
- Messages
- 3,191
What happened to CorOS 1.5, 1.6, 1.7, 1.8 and 1.9?
- Messages
- 3,744
I finally got to the "ask questions later" portion of my shooting at Hybrid Mode 2 (Jaws 4: Fish in a Barrel?), and I have to admit, the UI design looks (wait for it...) very elegant. :)
They kind of glossed over the individual assignment of switches, though. I guess it's going to be a top row/ bottom row affair, as opposed to a per-switch implementation? And then if you want to send MIDI out, you just use a Stomp mode switch assigned to nothing? This still only catches up to the HX implementation as it stood a couple of years ago. If it's any better than that, they should say so. (Or did I just miss something?)
They kind of glossed over the individual assignment of switches, though. I guess it's going to be a top row/ bottom row affair, as opposed to a per-switch implementation? And then if you want to send MIDI out, you just use a Stomp mode switch assigned to nothing? This still only catches up to the HX implementation as it stood a couple of years ago. If it's any better than that, they should say so. (Or did I just miss something?)
- Messages
- 3,744
There was a 1.41 that fixed a couple of bugs I'd never personally encountered.
It did not fix the problem of me thinking it was the 2.0 release announcement for 2.0 seconds and getting irrationally optimistic.
- Messages
- 3,744
The only thing I could see being complicated is the fact that there are already presets in the cloud that were built before this new mode was supported. But they've clearly gotten around that by continuing to support those modes, so... who knows?
Lysander
Shredder
- Messages
- 1,890
Yeah. My guess is they want to drop all these features together to make a big buzz wheh 2.0 finally lands. Because having WiFi, they could very easily just do rolling updates, automatically, every month or so.
Last edited:
- Messages
- 3,744
Legitimately "S O O N" would have been better PR than "B I G" IMO, but you may be right. They might also have been trying to avoid extra rounds of regression testing.
Elric
Roadie
- Messages
- 544
It was probably easy to implement (yeah I said it) the basic functionality of the hybrid switching but it was probably a major effort to actually put it into the UI (submenus, configuration, menus, dialogs, integrating it into the mode switching, etc). I suspect that is what they meant when they said it was 'implemented'. i.e. they had a proof of concept for it, which is different than something being ready for public release (IMHO).On a couple of other fronts I'm inclined to agree. But Hybrid mode should have been (relatively) low-hanging fruit.
Like James said above I think DC's mode of operation during the hype phase was to just give his first take (which was usually hyper-optimistic) and think things out or truly scope them later when responding on TGP.
It was lame/slimy to slink away to Discord when the 1.0 had so many issues, though. Should have learned the lesson to properly scope things and understand people were taking his statements as commitments and then own the botched release and do a hard reset on expectations and proceed transparently.
I guess they sort of succeeded in spite of that. Mostly because the capture functionality and UI absolutely crushed it and the hype train managed to keep the momentum. I think the covid supply chain issues creating an artificial scarcity may have even helped out.
- Messages
- 13,577
Run The Gauntlet. AlwaysTM
KingsXJJ
Roadie
- Messages
- 684
Yeah man, my trigger finger is ah-itchin‘ for sure. Sucks big time.
- Messages
- 13,577
Muuuuuuuuuuuuch better!
Similar threads
