Loopy Pro: Create music, your way.

What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

A request for a rough Cubasis roadmap

krassmannkrassmann
edited September 2021 in General App Discussion

Cubasis 3 is my main software for music production. It has not all the features of Cubase but it is improving constantly - so much that it is my tool of choice. Like all software on this planet Cubasis has some bugs and the defect rate is within normal figures for a professional product. Nonetheless some bugs really make it impossible for me to do certain things I’d like to do.

I know the issues I reported go into the bug tracker of the Cubasis team and I’m confident that they will be treated. Anyway, I’d really like a communicated rough roadmap of bugfixes. I’m also in the software industry and I know that bugfixes are very hard to estimate as you can always discover on the way that a bug is more difficult to fix than expected and might be moved to the next release train. I would also definitely prefer shorter release cycles for bugfixes. You have a beta program - I am also part of it - and the community would support you in testing.

@LFS I don’t want to lecture you how you develop your software - this is just my user perspective. In the past there were some issues that were not fixed in years although being ‘on the list’. Being a bit more open about bugfixes and a more transparent release schedule would definitely give users more trust to invest into Cubasis as their tool of choice for their projects. If this is communicated as a preliminary rough roadmap, I think the vast majority of users wouldn’t chop your head off if it is not exactly followed but rather appreciate the transparency and feeling of progress.

I also posted that at the Steinberg forum.

Comments

  • MAtrixplanMAtrixplan

    Yes, and I wouldn't expect that they would like to show it

  • MisplacedDevelopmentMisplacedDevelopment

    A mid-cycle interim bug fix release would be appreciated, outside of the main feature release cycle. I know, for example, a bug I raised very soon after the last release was found and fixed very quickly but it will be some (unknown) time until I see it in a release. I do seem to recall that the Cubasis updates appear on a fairly regular cadence though so I don’t know if we are due/overdue one.

  • SimonSimon

    A pledge?

    Isn't it a request?

  • ervinervin

    @krassmann said:
    Cubasis 3 is my main software for music production. It has not all the features of Cubase but it is improving constantly - so much that it is my tool of choice. Like all software on this planet Cubasis has some bugs and the defect rate is within normal figures for a professional product. Nonetheless some bugs really make it impossible for me to do certain things I’d like to do.

    I know the issues I reported go into the bug tracker of the Cubasis team and I’m confident that they will be treated. Anyway, I’d really like a communicated rough roadmap of bugfixes. I’m also in the software industry and I know that bugfixes are very hard to estimate as you can always discover on the way that a bug is more difficult to fix than expected and might be moved to the next release train. I would also definitely prefer shorter release cycles for bugfixes. You have a beta program - I am also part of it - and the community would support you in testing.

    @LFS I don’t want to lecture you how you develop your software - this is just my user perspective. In the past there were some issues that were not fixed in years although being ‘on the list’. Being a bit more open about bugfixes and a more transparent release schedule would definitely give users more trust to invest into Cubasis as their tool of choice for their projects. If this is communicated as a preliminary rough roadmap, I think the vast majority of users wouldn’t chop your head off if it is not exactly followed but rather appreciate the transparency and feeling of progress.

    I also posted that at the Steinberg forum.

    I get the sentiment but, with respect, this poll is about as realistic as one about "Do you like paying taxes?" or "Is world peace desirable?" would be. :) Genuinely interested what you think the result will tell you - or, more importantly, the Steinberg team.

    (I also spent much of my life in the software industry and I can't recall any major company voluntarily announcing a bugfixing roadmap AND then successfully sticking to it. I'm quite confident you have the same experience, hence my comment.)

  • krassmannkrassmann

    @ervin said:

    @krassmann said:
    Cubasis 3 is my main software for music production. It has not all the features of Cubase but it is improving constantly - so much that it is my tool of choice. Like all software on this planet Cubasis has some bugs and the defect rate is within normal figures for a professional product. Nonetheless some bugs really make it impossible for me to do certain things I’d like to do.

    I know the issues I reported go into the bug tracker of the Cubasis team and I’m confident that they will be treated. Anyway, I’d really like a communicated rough roadmap of bugfixes. I’m also in the software industry and I know that bugfixes are very hard to estimate as you can always discover on the way that a bug is more difficult to fix than expected and might be moved to the next release train. I would also definitely prefer shorter release cycles for bugfixes. You have a beta program - I am also part of it - and the community would support you in testing.

    @LFS I don’t want to lecture you how you develop your software - this is just my user perspective. In the past there were some issues that were not fixed in years although being ‘on the list’. Being a bit more open about bugfixes and a more transparent release schedule would definitely give users more trust to invest into Cubasis as their tool of choice for their projects. If this is communicated as a preliminary rough roadmap, I think the vast majority of users wouldn’t chop your head off if it is not exactly followed but rather appreciate the transparency and feeling of progress.

    I also posted that at the Steinberg forum.

    I get the sentiment but, with respect, this poll is about as realistic as one about "Do you like paying taxes?" or "Is world peace desirable?" would be. :) Genuinely interested what you think the result will tell you - or, more importantly, the Steinberg team.

    Yeah you are right. It was an emotional moment when I wrote the post. I tried to convert my frustration into something constructive. The poll was meant to get a quick feedback also from users who don‘t reply, but yeah… makes no sense. Deleted.

    (I also spent much of my life in the software industry and I can't recall any major company voluntarily announcing a bugfixing roadmap AND then successfully sticking to it. I'm quite confident you have the same experience, hence my comment.)

    In some projects in my career we were actually doing that. Promising customers that we will fix certain things in the upcoming releases. But I must admit that it was rare if the product was sold to a large audience. Most of my software projects were a custom solution for a single customer and was produced following the omnipresent agile methodology where the customer is a stakeholder in the development process - I guess you know what I mean. Of course such projects can not be compared to an off the shelf product like Cubasis.

  • krassmannkrassmann

    @Simon said:
    A pledge?

    Isn't it a request?

    Yep, thanks. Bug fixed 🤣

  • ervinervin

    @krassmann said:

    In some projects in my career we were actually doing that. Promising customers that we will fix certain things in the upcoming releases. But I must admit that it was rare if the product was sold to a large audience. Most of my software projects were a custom solution for a single customer and was produced following the omnipresent agile methodology where the customer is a stakeholder in the development process - I guess you know what I mean. Of course such projects can not be compared to an off the shelf product like Cubasis.

    Fair enough. Working on something directly for a large customer (large, and therefore having a strong negotiating position) makes for a dramatic difference in companies' bugfixing capabilities. :)

  • LFSLFS

    Hi @krassmann,

    Thank you for your message.

    Normally, we do announce new features and fixes alongside when releasing new versions.

    We constantly monitor the forums and exchange with our users, to learn more about the most frequent feature requests and problems.

    Given this information, we carefully work out the scopes and schedules for upcoming releases (which are subject to change from time to time in case of unforeseeable events).

    Best wishes,
    Lars

Sign In or Register to comment.

© Vanilla Keystone Theme 2025