Why do some plugin devs not accept feature request?

[Leo1999]

I have noticed that there are some devs or plugins with issues and people write
about it, but some devs do not seem to care.


1. Acustica audio high on cpu
I know some people don´t buy AA because of high cpu usage, but AA keeps on
releasing many new plugins, but do not improve cpu. I know some devs who could
improve cpu usage after some complaints.

2. Plugin Alliance Bettermaker sloppy gui
Plugin is good, but gui indeed hurts my eyes and it´s not nice to work with it.

3. Softube released native British Class A, but with 3 eq knobs only
Why releasing a worse version of a great version? The console 1 version has a
low mid and high mid knob!

Pulsarmodular and Kitplugins improved their plugins P42 and BBN105 pretty
quickly after some feature requests!

Do you also know some plugins or devs with known issues or feature requests?

[Ploki]

1) Acoustica: maybe they can't. Maybe the underlying tech is limiting. Convolution can be very CPU demanding.

2) PA: They don't care as long as subscriptions keep selling

3) console version is made to fit the hardware controller, native version is made to fit the original

in general, the bigger the company the less likely they're respond to request and customer feedback.

[foosnark]

General answers, not addressing your specifics:

1. Because software development is harder and more complex than most people realize it is. It's not a matter of "if you cared about your customers more, your code would run faster."

2. Because design decisions are made that way for a reason. Often they know that a choice will have downsides or limitations, and that some people won't like it. It's pretty hard to make something that's good for everyone without being completely generic and flavorless. So there is no automatic promise that the design will be changed to suit the whims of every potential customer. People sometimes ask for things that seem reasonable to them, but:

- don't fit the designer's vision.
- goes against what other customers are asking for.
- would require a lot of effort/cost for not very much gain.
- sometimes, potential customers' ideas are just stupid. (This can also be true of designers of course! But generally, they have put WAY more thought and effort into their own product than anyone else has, and are more likely to know what they're doing.)

3. Because people think posting about it on a forum or their blog or whatever counts as feedback, when the developers/designers/etc. don't have time to keep up with everything everywhere.

[Zaphod (giancarlo)]

1. Acustica audio high on cpu
I know some people don´t buy AA because of high cpu usage, but AA keeps on
releasing many new plugins, but do not improve cpu. I know some devs who could
improve cpu usage after some complaints.

Acustica: just today we released the first in a class of limited consumption and latency products, the FIRE products.

Honestly, we've always maximized audio quality output by penalizing other variables, but that doesn't mean we can't build products that consume less.
Our choice as a market position has always been to provide a product without compromise.

For some products it is still possible to have a low consumption solution, and this is happening in the FIRE line.

[Ploki]

how quaint, developer response in a thread about developers not responding

[cryophonik]

I'm not a developer, so I could be wrong, but I would assume that many/most developers have a road map in mind for their products, in which case they probably aren't likely to stray off course, unless there was a lot of demand for a particular request(s) and it made technical and economic sense for the product.

[plexuss]

Some (many) products are one-offs that are released, sold and that's it - no product development beyond the initial release. This is occuring more often because of the perceieved cash-cow of audio software products - people getting on the bandwagon with the focus of releasing a software product but no plan and/or ability to maintain it afterwards. It's not worth the customer banging their head against the wall with respect to these products - they are to be purchased as-is with no expectations of future development. Some devs have good intentions to update and maintain but then find out they can't do it because of whatever challenges and disappear.

[Teksonik]

It's probably because there are far more feature requests than time available to implement them.

For every feature request you have there are many more from other users.

No developer can implement every wish made by every user.

[cryophonik]

No developer can implement every wish made by every user.

Exactly... because they have to prioritize mine

[psynical]

Every dev accepts feature requests, but that doesn't guarantee that ALL OF THEM will be implemented.

[DCrown]

No developer can implement every wish made by every user.

Exactly... because they have to prioritize mine

I don't think that there are so many different requests as to a certain plugin, in most cases it's one feature or one issue. It's not that someone wants green knobs, someone else blue and someone else yellow knobs.
And indeed some devs even appreciate feature requests and quickly improve their plugins like Pulsar Modular, Kitplugins, Matthew Lane managed to make a lower cpu usage of his Tico comp and some more.
Great to see a reply of AA!

[vurt]

id imagine most do, they just don't make a point of letting people know, as then it encourages more.
but most will keep an eye out for good ideas, which if they can implement without detriment to the product, they just do it.

[Googly Smythe]

It ain't jus softwere where this sh!t appen, its all over. I bought a can of soup and it was 457 grams. Bit it's a lquid, innit, so it should be in milimeters, enniit, on top of wich, wy not make it an even 500?!?!. I keep emailing the cumpne but do they fix, do they eck.

[vurt]

ml not mm

[vurt]

cat litter comes in litres