Option regarding entering FX

[Kubase]

Hi,

Would it be possible to have an option whereby an FX wouldn't take effect until Shift is released?

[depaffect]

That’s an awesome idea!! Always a nightmare trying to enter fx while a pattern is playing!

[XORadmin]

Please please please please please please no repeated feature requests.....That slows down the process only.

So this is already long on my list and guess what....and more....... (SPOILER ALERT)

[mvdirty]

Please please please please please please no repeated feature requests.....That slows down the process only.

So this is already long on my list and guess what....and more....... (SPOILER ALERT)

With utmost regard, Thomas, I understand how tiring it must be for you to have to repeatedly tell people that something has already been requested but it is really hard as a user to know what has or has not already been requested. The forum search engine is generally terrible, even google isn’t bringing up good hits for this particular topic in its indexing of this forum, and I’m not aware of a unified catalogue of accepted/rejected feature requests or a development roadmap as such. 

How are users reasonably to know what has or has not already been requested or what you are working on?

Could a forum software upgrade perhaps address some of its search weaknesses? Could a requirements management system be adopted and used to handle change requests? etc.

[XORadmin]

Please please please please please please no repeated feature requests.....That slows down the process only.

So this is already long on my list and guess what....and more....... (SPOILER ALERT)

With utmost regard, Thomas, I understand how tiring it must be for you to have to repeatedly tell people that something has already been requested but it is really hard as a user to know what has or has not already been requested. The forum search engine is generally terrible, even google isn’t bringing up good hits for this particular topic in its indexing of this forum, and I’m not aware of a unified catalogue of accepted/rejected feature requests or a development roadmap as such. 

How are users reasonably to know what has or has not already been requested or what you are working on?

Could a forum software upgrade perhaps address some of its search weaknesses? Could a requirements management system be adopted and used to handle change requests? etc.

I got to say that 9 of 10 things are mostly possible to find through the search function. I do that myself if I get this 'Deja vu' feeling and mostly with success.
My list is very long and I go from time to time through the requests and discussions to see if I missed something.
But generally I think it makes much more sense to check first for similar things. And to add a +1 there or a remark would be much better.
It saves me so much time which I can use to get these things actually implemented.

[XORadmin]

Just to clarify my spoiler alert. Something like this will be in my next release together with some more related things.

[mvdirty]

It saves me so much time which I can use to get these things actually implemented.

Absolutely! No disagreement at all from me there. I’d quite like to spare you more time for development work!

My list is very long and I go from time to time through the requests and discussions to see if I missed something.

Might it help folks if you published your list? (With disclaimers about it not representing any degree or timeframe of commitment, of course. ) Or would it just be so full of shorthand and other thoughts and little reminders of your own that people would still struggle to find things?

[XORadmin]

Might it help folks if you published your list? (With disclaimers about it not representing any degree or timeframe of commitment, of course. ) Or would it just be so full of shorthand and other thoughts and little reminders of your own that people would still struggle to find things?

Well I don't do that. Sure it would even take more time to 'format' it the proper way (and  keep). And where would be all the surprises then?
And the questions about when will function XY be included would surely raise in an expotentional way. Lets keep it like this with some spoilers here and there and sometimes reminders to try to keep the forum clean from duplicates.

[mvdirty]

Well I don't do that. Sure it would even take more time to 'format' it the proper way (and  keep). And where would be all the surprises then?
And the questions about when will function XY be included would surely raise in an expotentional way. Lets keep it like this with some spoilers here and there and sometimes reminders to try to keep the forum clean from duplicates.

I hear ya, I truly do, and not least because I also maintain some software too, and soon will maintain some more that’ll end up open source, so I definitely get the pros and cons of managing such roadmaps.

I had to ask, though, but I’ll try to refrain from asking more than once every couple of years.

[Kubase]

I tend to post on here when I'm making music and I see a potential improvement. I usually search but didn't this time - however I tried to search retrospectively and didn't find anything anyway