Jynx
Roadie
- Messages
- 583
I just really hope NDSP doesn't release these plugins with partial content, e.g. amps but no effects.
Unlikely.
I just really hope NDSP doesn't release these plugins with partial content, e.g. amps but no effects.
This is looking good.Unlikely.
LOL I think we posted diametrically opposed viewpoints simultaneously.Y'know I just realised I never looked at that above picture closely 'til now. It's actually a very neat and tidy way to do it instead of trying to put the amps, effects, and cabs, in with the others of the QC and having them greyed out or not depending on whether you have them or something like that.
I wonder if the plugins only appear in the list if you have them or will it show all of them regardless of whether you have them or not, only inactive if you don't possess it?
I just really hope NDSP doesn't release these plugins with partial content, e.g. amps but no effects.
LOL I think we posted diametrically opposed viewpoints simultaneously.
I'm guessing e.g. the Plini submenu would only appear if you owned it. Otherwise, eventually, major clutter.
But personally, I'd rather see all the amps where amps go, all the distortions where distortions go, all the reverbs where reverbs go, etc. (Call me crazy...)
This is looking good.
Next observation/ hope/ concern: I hope that menu structure isn't going to be the only way to get at plugin content. Meaning, I hope e.g. "Plini Crunch" can be found under the amp model menu, "Plini Overdrive" under the OD/DIST menu, and so on. Having amp models and amp captures in disparate menus is already a minor annoyance; new folders for every plugin would compound matters significantly.
This is an important question. The CME stuff is really low-latency (compared with most generic Bluetooth devices.) It still comes down to personal sensitivity, though.Nice option….not sure if the added latency would allow wahwahcontrol…is assume no…
I guess we’ll know soon (no pun intended) enough if they start releasing a Cortex LT, QC Stomp XL, and even a Quad Express.Yep. Much as I'd prefer a QC Native* plugin over their current a la carte model (and now this tail-wagging-dog paradigm of buying plugin content for one's hardware modeler), I don't see how they could get there without a) charging a fortune for it, or b) completely undermining revenue from their current line of Archetypes, etc. etc.
*Aside: I don't think "ripping off" this name even bears mentioning, really. "Native" is as much part of the common vernacular as "plugin". If anything, everyone is ripping off Native Instruments, and even that's a stretch.
Naming concerns aside, I can't imagine they have the bandwidth. They barely got the QC out the door. (That sounds a bit negative so I'll add: I'm glad they did.)I guess we’ll know soon (no pun intended) enough if they start releasing a Cortex LT, QC Stomp XL, and even a Quad Express.
Is there a summer NAMMNaming concerns aside, I can't imagine they have the bandwidth. They barely got the QC out the door. (That sounds a bit negative so I'll add: I'm glad they did.)
This is what I've been on (and on, and on, and on) about from the beginning. NDSP's approach was never going to result in "QC Plugin Compatibility" per se, but merely "QC-Compatible Plugin Compatibility". Which will always be a work in progress.
(I just had that weird thing where "compatibility" doesn't sound like a word anymore.)
“The QC is now fully compatible with select Neural Plugins that are compatible with the QC. Neural Plug-ins that are not compatible with the QC, (which is is now fully compatible with select compatible Neural Plugins) will be made compatible soon. Future Neural Plugins may not be QC compatible at release, but will be brought to full compatibility at a future date with the QC, which is now fully compatible with select compatible Neural plugins”
Is that a real quote or“The QC is now fully compatible with select Neural Plugins that are compatible with the QC. Neural Plug-ins that are not compatible with the QC, (which is is now fully compatible with select compatible Neural Plugins) will be made compatible soon. Future Neural Plugins may not be QC compatible at release, but will be brought to full compatibility at a future date with the QC, which is now fully compatible with select compatible Neural plugins”
Is that a real quote or
I still don’t know why they don’t fix it going fwd with new plugThey asked me to make a draft for the revised manual post 3.0.
99% legit.
It feels like it's been awhile since NDSP released a plugin? And by "awhile" I mean with their previous release schedule but I have not looked up anything to confirm that lolI still don’t know why they don’t fix it going fwd with new plug
It’s like they continue to buy size 40 pants and then have to take them to a tailor because their waist is a 34
If they were using common sense they would be making X plug-ins going fwd , but we will seeIt feels like it's been awhile since NDSP released a plugin? And by "awhile" I mean with their previous release schedule but I have not looked up anything to confirm that lol
Yeah it would but idk, I have to imagine they realize not doing so would duplicate efforts.If they were using common sense they would be making X plug-ins going fwd
“The QC is now fully compatible with select Neural Plugins that are compatible with the QC. Neural Plug-ins that are not compatible with the QC, (which is is now fully compatible with select compatible Neural Plugins) will be made compatible soon. Future Neural Plugins may not be QC compatible at release, but will be brought to full compatibility at a future date with the QC, which is now fully compatible with select compatible Neural plugins”