Audiobus: Use your music apps together.

What is Audiobus?Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.

Download on the App Store

Audiobus is the app that makes the rest of your setup better.

Komp 2.0 for iOS

Hello all,

Komp 2.0 for iOS is now available here: https://apps.apple.com/in/app/komp-create/id1103355632

A wiki describing various features of Komp is here: https://github.com/SemitoneGene/Komp-Support/wiki The documentation is sparse and I am filling it in as I create the demonstration script for the videos that will show how to use Komp. The documentation and programing department is just me so you may have to just discover features until I get them all documented.

You can ask for support, file bugs and request features here: https://github.com/SemitoneGene/Komp-Support/issues All the issues, bugs and product roadmap publicly available. This seems to be the best approach to developing an application with such a small and focussed community of users.

I have been the sole developer and user of Komp, so I am sure there will be many issues as I tend to get stuck in well-worn paths as I am developing features.

Thanks so much for taking the time to take a look at this post. I hope some of you are able to take a look at Komp and let me know what you think!

Gene

Comments

  • Thanks for popping in. App seems great! That link is for the first version, is 2.0 replacing it?

  • You do realize it's harder to charge for something later after you've given it away for free? Why are you just giving this away?

  • @NeuM said:
    You do realize it's harder to charge for something later after you've given it away for free? Why are you just giving this away?

    Not that I am presuming to answer,,,

    but:

    1 Considering the free versions of Dorico, and Musescore etc that are already there, only speaking for myself but I'm unlikely to try this if its not free

    2 the word community is mentioned by OP, easier to build such a thing around free

    3 Harder perhaps, but not impossible

    4 Perhaps there is a different "business" model, long term other than selling the app as such

    5 Not everything has to be monetized. "just giving it away" is, a loaded way to put it, implying one way of doing software or even business. albeit i admit im on thin ice in this particular context given apple's ios ecosystem is expensive to operate in and prohibitive, but, more widely in a free software / generative justice context a la Lessig / Stallman / Eglash. and in light of how many present era mega companies were bootstrapped completely on their free software, (even macOS being darwin) there are as sun ra said, other worlds!

    6 maybe its a portfolio / research project / labour of love?

    7 maybe its intended to be open sourced down the line, hence github for documentation already, hence charging would be antitthetical

    why actually, is this your one question? why shouldn't they "just" "give" it away, why does that concern you, at least enough to have you pose the question? would you or do you ask this of all app developers with free app offerings?

  • This is really useful. Man what a cool app. This can definitely, for me, inspire creativity. Thank you.

  • @Bruques said:

    @NeuM said:
    You do realize it's harder to charge for something later after you've given it away for free? Why are you just giving this away?

    Not that I am presuming to answer,,,

    but:

    1 Considering the free versions of Dorico, and Musescore etc that are already there, only speaking for myself but I'm unlikely to try this if its not free

    2 the word community is mentioned by OP, easier to build such a thing around free

    3 Harder perhaps, but not impossible

    4 Perhaps there is a different "business" model, long term other than selling the app as such

    5 Not everything has to be monetized. "just giving it away" is, a loaded way to put it, implying one way of doing software or even business. albeit i admit im on thin ice in this particular context given apple's ios ecosystem is expensive to operate in and prohibitive, but, more widely in a free software / generative justice context a la Lessig / Stallman / Eglash. and in light of how many present era mega companies were bootstrapped completely on their free software, (even macOS being darwin) there are as sun ra said, other worlds!

    6 maybe its a portfolio / research project / labour of love?

    7 maybe its intended to be open sourced down the line, hence github for documentation already, hence charging would be antitthetical

    why actually, is this your one question? why shouldn't they "just" "give" it away, why does that concern you, at least enough to have you pose the question? would you or do you ask this of all app developers with free app offerings?

    An excellent set of answers for an unpleasantly worded question. Thanks for coming up with them!

    As many people do get uncomfortable about the thought of a totally free piece of software that makes no attempt to monetize the user and turn them into a product, it could be possible to generate revenue by charging for more advanced notation features, virtual instruments, audio transcription and more.

    Apple has created a race to the bottom on iOS application pricing. There isn't any realistic price that could be charged for a general purpose music notation application that could make developing it worth doing based solely on initial purchase price. You only have to look at the failure of StaffPad (an excellent product) to exist as an independant company to see one example of how this works out.

  • @HotStrange said:
    Thanks for popping in. App seems great! That link is for the first version, is 2.0 replacing it?

    You should see the 2.0 version, at least I do when I click on the link. Let me investigate some more for you.

  • @SemitoneGene said:

    @Bruques said:

    @NeuM said:
    You do realize it's harder to charge for something later after you've given it away for free? Why are you just giving this away?

    Not that I am presuming to answer,,,

    but:

    1 Considering the free versions of Dorico, and Musescore etc that are already there, only speaking for myself but I'm unlikely to try this if its not free

    2 the word community is mentioned by OP, easier to build such a thing around free

    3 Harder perhaps, but not impossible

    4 Perhaps there is a different "business" model, long term other than selling the app as such

    5 Not everything has to be monetized. "just giving it away" is, a loaded way to put it, implying one way of doing software or even business. albeit i admit im on thin ice in this particular context given apple's ios ecosystem is expensive to operate in and prohibitive, but, more widely in a free software / generative justice context a la Lessig / Stallman / Eglash. and in light of how many present era mega companies were bootstrapped completely on their free software, (even macOS being darwin) there are as sun ra said, other worlds!

    6 maybe its a portfolio / research project / labour of love?

    7 maybe its intended to be open sourced down the line, hence github for documentation already, hence charging would be antitthetical

    why actually, is this your one question? why shouldn't they "just" "give" it away, why does that concern you, at least enough to have you pose the question? would you or do you ask this of all app developers with free app offerings?

    An excellent set of answers for an unpleasantly worded question. Thanks for coming up with them!

    As many people do get uncomfortable about the thought of a totally free piece of software that makes no attempt to monetize the user and turn them into a product, it could be possible to generate revenue by charging for more advanced notation features, virtual instruments, audio transcription and more.

    Apple has created a race to the bottom on iOS application pricing. There isn't any realistic price that could be charged for a general purpose music notation application that could make developing it worth doing based solely on initial purchase price. You only have to look at the failure of StaffPad (an excellent product) to exist as an independant company to see one example of how this works out.

    Alright, I see where you're going with this. Just was concerned about giving away the whole store when you didn't really have to. We've seen a number of developers disappear due to their business model and an inability to make a profit. Obviously, none of this is really any of our business, it's yours.

  • @SemitoneGene said:

    @HotStrange said:
    Thanks for popping in. App seems great! That link is for the first version, is 2.0 replacing it?

    You should see the 2.0 version, at least I do when I click on the link. Let me investigate some more for you.

    Is it just called “Komp Create”?

  • @HotStrange said:

    @SemitoneGene said:

    @HotStrange said:
    Thanks for popping in. App seems great! That link is for the first version, is 2.0 replacing it?

    You should see the 2.0 version, at least I do when I click on the link. Let me investigate some more for you.

    Is it just called “Komp Create”?

    Yes. This link should take you to the AppStore entry:
    https://apps.apple.com/us/app/komp-create/id1103355632

  • @SemitoneGene said:

    @HotStrange said:
    Thanks for popping in. App seems great! That link is for the first version, is 2.0 replacing it?

    You should see the 2.0 version, at least I do when I click on the link. Let me investigate some more for you.

    I love the app; it has great potential. Still, lots of things to work on...
    Here is my experience after just 20 minutes of testing the app:

    • There is no save score or versioning feature.
    • To add an instrument, you need to go to "Edit Inst."
    • In dark mode, the ink did not change accordingly. So you write with black ink on a black background.
    • No sound preview on lots of instruments (Clarinet, Oboe, Contrabasson, Piccolo, etc.)
    • Play works only once, then gets blocked afterwards.
    • Training is confusing; there is no example of what we actually need to write. Whole and half note variations were all the same in training; I didn’t test anything else.
    • I got one CTD.
    • etc.
  • @Luxthor said:

    @SemitoneGene said:

    @HotStrange said:
    Thanks for popping in. App seems great! That link is for the first version, is 2.0 replacing it?

    You should see the 2.0 version, at least I do when I click on the link. Let me investigate some more for you.

    I love the app; it has great potential. Still, lots of things to work on...
    Here is my experience after just 20 minutes of testing the app:

    • There is no save score or versioning feature.
    • To add an instrument, you need to go to "Edit Inst."
    • In dark mode, the ink did not change accordingly. So you write with black ink on a black background.
    • No sound preview on lots of instruments (Clarinet, Oboe, Contrabasson, Piccolo, etc.)
    • Play works only once, then gets blocked afterwards.
    • Training is confusing; there is no example of what we actually need to write. Whole and half note variations were all the same in training; I didn’t test anything else.
    • I got one CTD.
    • etc.

    Thanks for this!

    The score will be saved after every modification. I know some people don't like the concept of auto-saving. Versioning would be a really good feature to add.

    I'll create issues for the other bugs you ran into.

    What would you like to see improved with changing the instrument? Being able to change the instrument within the main score without having to display the Edit Instrument view?

    I do need to really get the example videos done. Regarding training, was Komp having a hard time recognizing your whole and half notes in the score?

  • @SemitoneGene said:

    @HotStrange said:

    @SemitoneGene said:

    @HotStrange said:
    Thanks for popping in. App seems great! That link is for the first version, is 2.0 replacing it?

    You should see the 2.0 version, at least I do when I click on the link. Let me investigate some more for you.

    Is it just called “Komp Create”?

    Yes. This link should take you to the AppStore entry:
    https://apps.apple.com/us/app/komp-create/id1103355632

    Great, all is clear now, thanks 👍🏻

  • @SemitoneGene said:

    @Luxthor said:

    @SemitoneGene said:

    @HotStrange said:
    Thanks for popping in. App seems great! That link is for the first version, is 2.0 replacing it?

    You should see the 2.0 version, at least I do when I click on the link. Let me investigate some more for you.

    I love the app; it has great potential. Still, lots of things to work on...
    Here is my experience after just 20 minutes of testing the app:

    • There is no save score or versioning feature.
    • To add an instrument, you need to go to "Edit Inst."
    • In dark mode, the ink did not change accordingly. So you write with black ink on a black background.
    • No sound preview on lots of instruments (Clarinet, Oboe, Contrabasson, Piccolo, etc.)
    • Play works only once, then gets blocked afterwards.
    • Training is confusing; there is no example of what we actually need to write. Whole and half note variations were all the same in training; I didn’t test anything else.
    • I got one CTD.
    • etc.

    Thanks for this!

    The score will be saved after every modification. I know some people don't like the concept of auto-saving. Versioning would be a really good feature to add.

    Auto-saving is a good feature, but not the exclusive and only option. Lots of times we open up a project, test some parts, change a few things, and want to get out without saving at all. Versioning is a mandatory process for me, to be or not to be.

    I'll create issues for the other bugs you ran into.

    What would you like to see improved with changing the instrument? Being able to change the instrument within the main score without having to display the Edit Instrument view?

    I really thought that "+" was for adding a new instrument; maybe just move ‘Edit Instruments’ there.

    I do need to really get the example videos done. Regarding training, was Komp having a hard time recognizing your whole and half notes in the score?

    In manuals, there is no visual representation of how to write notes. Regarding "Trainer", there's an ambiguous explanation in the app about what you're actually training; is it a complete symbol or just a variation of a style? I expected to train myself with visual guidance using the best gesture method. Don’t get me wrong, it is great for what it is; you can train Smiley to be a whole note, and it works. ;) Maybe just visual representations in the manuals, for the best writing practice. Not just words.

  • Any news? We are still keeping an eye on this phenomenal app. 🤩 I hope that the developer is fine and dandy, working diligently on the app and the new features. 🤞

  • @SemitoneGene said:

    @HotStrange said:
    Thanks for popping in. App seems great! That link is for the first version, is 2.0 replacing it?

    You should see the 2.0 version, at least I do when I click on the link. Let me investigate some more for you.

    It links to version 2.0.3 for me. It says that in the what’s new section on the AppStore page.
    Maybe ppl expecting 2.0 literally in the app name or something

Sign In or Register to comment.