KVR Audio

aciddose · Post by **aciddose** » Sun Aug 23, 2015 3:55 am

I don't care about you or anything you do. If you are going to be useless what makes you think I would care?

People to have genuine issues and genuinely want help usually ask for it in a more reasonable manner.

Teksonik · Post by **Teksonik** » Sun Aug 23, 2015 3:57 am

aciddose wrote: So in other words you've come here on a personal vendetta to waste my time while flooding the thread to make it hard for users with genuine interest to read genuine content.

No I came here earlier today before we had our words in the other thread just to report an obvious bug. If your ego or lack of talent prevent you from fixing it that's no longer my problem. Like I said good luck with future versions.

aciddose · Post by **aciddose** » Sun Aug 23, 2015 3:58 am

Teksonik wrote:Like I said that's for you to figure out and like I also said I have hundreds of plugins working in FL Studio so it's obviously not that hard to figure out.

I've been aware of this FL Studio bug for years. I've reported it to them. They've refused to fix it.

You can ask about whether VST2 plugins are expected to handle multiple simultaneous calls to functions on the VST mailing list or DSP forum here on KVR.

The release version has a work-around in place for this but the alpha does not and will not.

I will not fix other's bugs in my software.

aciddose · Post by **aciddose** » Sun Aug 23, 2015 4:26 am

Let me just be clear about this.

The options available to me are:

Do not access pointers in idle(), do nothing that would be compromised by simultaneous calls between multiple threads. (I.E. do nothing at all, making the function useless.)
Implement a cheap workaround (flag in_idle, if in_idle == true, don't enter the idle function.)
Use a mutex, which is expensive and could result in fatal deadlocks.
Implement a mutex specifically for each and every function which may be called from multiple threads. (Totally impractical.)

For release I'm happy with #2, but it is entirely possible to get crashes because the if (in_idle) check might occur at exactly the same time in_idle = true occurs, such that the check returns false while the value is actually true.

The solution is for FL Studio's wrapper to call editor->idle() only from their handler for WM_TIMER or otherwise from some other point in their message pump function (the GUI/window thread), or not at all.

murnau · Post by **murnau** » Sun Aug 23, 2015 6:21 am

I've been aware of this FL Studio bug for years. I've reported it to them. They've refused to fix it.

Then why you not said it right from the start? You asked Teksonik for details already knowing that the sequencer his FL Studio.

The release version has a work-around in place for this but the alpha does not and will not.

Why the earlier version Teksonik mentioned worked then? It's understandable that he come here and ask you.

I will not fix other's bugs in my software.

That's of course fine but at least you could set a note on your site to prevent FL Studio users (i know there are not so many *cough*) to waste their and your time.

Anyway, i have the impression you like the idea that people could read Xhip as Skip one day? I laughed loud when you wrote Vendetta altough Teksonik only was p*ssed off that you talked to him in a condescending tone.

Don't take it personal, it's not.

aciddose · Post by **aciddose** » Sun Aug 23, 2015 7:12 am

Well I still have no idea what actually causes it to crash.

To trigger the animation issue (idle function) requires certain actions like closing the GUI window, using certain buttons and so on.

During normal use it shouldn't occur.

(I.E. just playing some notes with it open.)

If he isn't going to tell me what makes it crash but simply "it crashed" my first post applies. I can't do anything about it.

He didn't even say "I opened the GUI and did nothing", he instead said "it is a waste of time for me".

I can't fix something like this.

Like if you have a mix and someone says "the mix is all wrong, it sounds crap".

How are you supposed to fix it? You could start taking random actions and attempting to identify the issue by trial and error, but if they also say "the mix is crap, listening to this again is completely a waste of time it isn't a genre I like" you can't actually test your changes to see if they make any difference.

It's a waste of my time to download FL and try to reproduce this. Can anyone else report an issue in FL? Does the issue also occur in any other host? (I.E. not FL specific?) What causes the issue?

If not, I'm not going to bother with FL because I know of some other issues it has already. This complicates everything and requires a huge amount of effort to blindly attempt to identify an issue... an issue that may not even exist.

aciddose · Post by **aciddose** » Sun Aug 23, 2015 7:42 am

This has been somewhat useful but at the same time extremely frustrating.

Xhip will be finished when it is finished, and those interested can contact me via the site directly, find new alpha versions if I post them and so forth.

New Xhip alpha