Ok then......

[Teksonik]

Since you locked my other bug report thread.....

And it's not that we forgot it, but we have not been able to release a fix yet (we said "probably in 2023", which isn't even half way through yet).

According to your support : "this problem was introduced with the latest release version 2.1.1 (revision 12092)".

Hive 051523-2.png

On that note, there is no need to post sequels to the thread, our internal project management system reminds us daily about just how much work we need to do before we can release an update.

So you don't think a customer has the right to bring up a bug that's ONE YEAR AND NINE MONTHS OLD especially since it's been reported and acknowledged a long time ago? What do we know about your "internal project management system" other than it's apparently not working for you or us?

Is that how U-he rolls these day? Introduce a bug a year and nine months ago and then get offended when a user brings up a crash level bug again? "Probably 2023"? Like you're doing someone a favor for fixing a crash level and/or serious timing issue bug in a purchased plugin? Certainly you're better than that or at least your reputation says you should be.

There is not one developer in this business that is above criticism when it is deserved and quite frankly U-he deserves criticism for letting this bug that affects Hive 2 in one of the most popular DAWs (based on the number of users) go on for so long with no fix in sight. Yes FL Studio's buffer situation sucks for developers but like I said none of the many other plugins I own and use have this bug and if they did I'd be bitching about it on their forum or to their support too.

You can lock this thread or delete it but that doesn't change the fact that despite being one of the most popular developers in the business you are by no means above reproach.

I'm in no way a U-he hater but in this case after the crash/timing bug reared its ugly head again yesterday I'm venting my frustration that the bug still exists after all this time....in one of my favorite plugins.

If you can't take negative feedback from your customers then you shouldn't be in business. If you can't fix a serious bug going on two years then....well, you can take it from there.

Fanbois don't bother. I will not read your responses.

Have a nice day everyone.

[pdxindy]

IBTL

[Greenstorm33]

People are so entitled these days. Back in my day we had bugs that never got fixed and we worked around em. With spit and string! U-he is great and will get it fixed eventually.

[Urs]

What do we know about your "internal project management system" other than it's apparently not working for you or us?

Nothing. You know nothing. Obviously. Just like what you know about any other company, because most other companies don't even talk to you in a forum like this.

It might be great that me posting here gives you an outlet to yell at, but my approach these days is to block and ban people from this place if they try to bully me by instigating outrage over something I can not fix with a finger snip.

I did sit down and I have worked on this for more than a week with several people involved, and I truly wished I could have just put out a fix. But atm our codebase is not in a state where we can do that, we had to merge quite a few development branches and there are issues. It's unfortunate, but sometimes such is life.

You don't believe me? Cool. Then you do not need access to this forum, or me. You decide.

[Lectropunk aka influx808]

Bad manners is not just a marcel dettman label LOL

[Urs]

Here's an example of how I think things can progress, as opposed to how it went down with those toxic posts of the past couple of days:

viewtopic.php?p=8675173#p8675173

It's quite simple, really.