It would be great if the keyboard keys at the bottom were highlighted when their remix is playing to make it easier to see which one is playing. Like this, if D is the remix being played at the moment:
Yes, it will be added. Thank you.
Too bad the highlight is only active when Playbeat is in play mode. Stopped, one has no idea which Remix is currently displayed.
Hi, when you press Play again, it will resume from the last remix key, which is the one currently displayed. That said, we can definitely keep the highlight set to “on” until a new one is triggered, so it provides clearer visual feedback.
If you are not updating your product, you could stop pretending you are making changes. I have version 1.1.3 and this was 2022.
When I go to your website and click the link you provide to download the trial, for example, it’s the exact same version. That means you haven’t made any updates since 2022, yet, you keep saying that XYZ feature will be implemented.
I was excited when I knew about your company, until I came to this forum and noticed that it’s lie after lie. You like to keep your customers stuck in this loop, promising that this and that feature is being implemented, yet your products remain the same, but you like to shift focus into new products, when the old ones clearly need major changes.
This is how you stain a company’s reputation, for me. When an alternative to Loopmix comes to the market, I’m done with Audiomodern.
The question referred to the Playbeat app rather than Loopmix; however, since both apps use similar triggering functionality, the same approach would apply to Loopmix as well. We haven’t received many requests for this specific visual implementation, but it’s a straightforward addition and something we can include in both apps.
The current desktop version of Loopmix is 1.1.4, and the iOS version is 1.1.7, which was updated a few months ago with improvements that did not affect the trial version.
This forum provides valuable guidance on which features users want next, and we actively monitor all requests. Sorry that you see it this way, but at this point, we’ve implemented around 90% of the major requests for our apps, and these have directly influenced the updates we’re currently rolling out.
This is a topic about Loopmix, so you as part of the company, should automatically move their reply to a new topic to avoid mixed replies in Loopmix feature request.
Sure, and that makes sense. So, for you to say that it “would” apply, and “we can include”, that means it still hasn’t been applied, which takes me back to this comment 3 years ago:
As you see, you keep saying that this and that feature is being implemented or will be implemented, 3 years later, it’s still in the “would apply” and “can include” folder.
Then maybe, just maybe… you should update the file that allow users to download the trial? Just a simple procedure, I would believe.
I guess it really depends on what “major requests” really mean to you. Just because a request has 100 upvotes and one has 10, that doesn’t mean anything. For example, a request to increase the font (which is tiny) could maybe have 10 votes, because some users have a good resolution screen, opposed to another request that has 100 votes. That doesn’t mean that the request for the font is not as valuable or even more valuable to all users.
But it’s up to you what you decide to implement.
It’s not the first time I see you guys saying that XYZ would be implemented or fixed in the next version, and things remain the same.
As I said, when a company’s reputation is stained, it’s a not-coming-back step for me. I see the value in some of your products, but I have no trust left anymore.
Over and out.
We always review requests based on what comes in most frequently, and we prioritize them accordingly. Some requests remain pending because others are more urgent or impactful. Our focus is on addressing what matters most to users, rather than simply what’s easiest or quickest to implement.
For Loopmix, we prioritized refining and optimizing the time-stretching algorithms, overall sound quality, and CPU efficiency (especially important when using multiple instances of the app) while some minor visual details were left behind.
Regarding the font size, we’ve implemented a font size control across all our recent apps already. Loopmix hasn’t received it yet, but we’ll add it shortly there and in our older apps too.
That said, if a company’s entire reputation could be judged solely on a few features that haven’t been released yet, we’d hope users might consider the bigger picture, our ongoing commitment to improving all apps and the many features, expansions and Instruments that already deliver a great experience.
[That said, we can definitely keep the highlight set to “on” until a new one is triggered, so it provides clearer visual feedback.]
This would be helpful thanks!