Let’s get real… many of us will be 95 or older, waiting for the wish list to be complete, especially for those feature requests that are fx blocks. Why wait for QC, when just outside the QC door in the Mac/PC world there are actually THOUSANDS of fx developers.
IMAGINE IF YOU WILL… having a Strymon Big Sky plugin on your QC? or an Eventide Crystals plugin. AhhhhHHhhh - so much functionality available… if only…
Not to mention the hundreds, if not thousands of unique plugins that take music WAY WAY WAY beyond traditional pedals on a pedalboard. FOR EXAMPLE:
So - come on Neural - step outside the box, and get “global” from a compatibility perspective, instead of being such a bottleneck for sound development. Otherwise - I’ll have to just run my instrument into an audio interface, and into my Mac or iPad::: to get REAL fx processing.
Love that you’re trying and coming up with all these outta da box ideas, keep ‘em comin’, but you probably realize it’s a hit or miss attempt. Compiled all your suggestions, here and elsewhere, are unreasonable for any company to implement within a foreseeable future at this stage of technological development.
Don’t get bitter and burn out please! As stated; keep on keepin’ on tryin’ & dreamin’.
There are limited programming manpower resources in this field and all companies fight to keep up. It’s a business and they have to asses what to follow up and what to let go for Now.
Why post a feature request that includes the exact same (older) request? It’s unnecessary.
Also… AU plug-ins are for Apple operating systems only (MacOS, iOS). Even if this request could be considered for the QC, it would have to resort to VST3 format at best.
Unfortunately ndsp are struggling to get there own plugins on QC… how long is since the last real update with plugins being released I doubt this will ever happen… But I’d love it…
There are limited manpower /resources…
EXACTLY my point. We’ll NEVER get all of the cool fx that are available in the thousands of plugins that are out there.
So please DSP - quit wasting man hours on your fx blocks: and simply create an fx block that supports AU/AUV3 plugins.
For the same amount of hours your developers spend creating 3 new fx blocks :::: your users can get the availability of 1,000+ new fx blocks via plugins.
You’re simply asking them to blow up their business-plan to serve a minor dissatisfied part of their user base in here. First thing’s first and your “needs” are not in their order of priority.
Just glad I don’t have that itch that can’t be scratched.
(Okay, since it’s turned in this direction we can take that other discussion in here too, thanx for that).
It’s not a wider perspective… it was somtin that was promised without actual knowledge if it would work or if they could do it…and you feel you need to single me out because it doesn’t fit with what you think..
I just made a comment to the op, and in no way was running ndsp down just stating a fact that there struggling to get there own plugins running on the QC.. And I doubt they will do what he’s asking
It’s a wider perspective in the sence that it’s not just what any single user thinks/wants/need but what is the general satisfied user base. You stuck your neck out without the perspective of the unending complaints that’s been going on forever in here, from a few loud users, that is drowned completely out by the vast majority of satisfied costumers.
For one I never said I wasn’t satisfied with the QC… 2. I didn’t stick my neck out that’s what neural have said themselves it has been harder then they anticipated… 3. I did not complain about it either, so unsure what your going on about
AU and AUV3 plug-ins are exclusive to Apple architecture / operating systems. If you’re going to double-down on those formats, then just know that this request has already shot itself in the foot.
About plug-ins in the QC in general:
Years ago (it feels weird that I’m saying that), there was a long discussion in the forum about whether or not the promised NDSP plug-in compatibility would be implemented with the QC’s standard GUI, or if it would retain the more realistic (or skeumorphic) design of the amps in the original plug-ins’ GUIs.
What came to light was that there was no way that the QC could maintain the exact look of the plug-ins’ GUIs, because the touch screen did not have high enough resolution to support them. When PCOM finally rolled out, sure enough it was in the QC’s format, and editing parameters on the plug-in blocks looks the same as any other standard block. The lone exception being Parallax X, which doesn’t have a skeumorphic amplifier design.
Likewise, the QC touch screen doesn’t have the resolution to support the GUIs of most 3rd party plug-ins.
The whole thing about Neural’s ‘X’ plug-ins is that they had to be completely rebuilt to work on the QC’s ARM architecture. Not every 3rd party plug-in is going to have that.
Also, many plug-in brands like FabFilter actively check license purchases before you can use them. The QC itself would need to run iLok authentication just to run about half all plug-ins out there anyway.
I can say without a doubt, that this will not happen. Way too many variables.
I remember when the Paint Audio CE1 got announced–initially I was excited about the ability to run 3rd party plug-ins, but once I learned that it runs on Windows I backed out completely. What a nightmare.
