2 days) and to ignore that potential bug because all the other great things with MusicBee. Totally up to you and genuinely fine with me whatsoever.īut I begin to get the impression, that you try to tell me that I have an obligation to be grateful for being "swiftly" turned down within 1h (as this would be any better than to be turned down after e.g. Steven, you or anyone involved can take that feedback as food for thought for improvement, dismiss it or ignore it entirely. So consider this as my open and honest feedback as one of your many users on the decision made and the communication style. And I articulated exactly that with all due respect. Nevertheless, it was that response that left me disappointed. because of my use case being rare or because of dependencies on legacy third party libraries. And the decision can be very reasonable from his point of view e.g. I genuinly hope that we can agree upon that this initial post of mine is anything but a complaint.ġh after posting my report Steven stated that he won't take any action on it without any explanation or rational. I've tried to write my report in a way to make it as easy as possible to reproduce the behavior as I have experienced it. So I compiled a bug report, encouraged by the section in this forum explicitly asking for it. So, of course, there is some expectations - or let's say hope - that it would perform with my preferred plugins.Īfter a while I found out that one of my favourite plugins seems to be not properly working with MusicBee. Thus, there is an indication for me as a user that MusicBee would support such use cases. However, MusicBee offers a VST host plugin. So I'm aware that VST plugins are initially not built for being hosted by music players. I'm perfectly familiar with what VST is or originally has been designed for. Ok, so once more, let's try to straighten things out.
0 kommentar(er)
