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.

My humble plea to all developers in preparation for iOS11!

Hi All!

I've been watching thru the WWDC'17 sessions and one session in particular made was a real eye opener for me.
https://developer.apple.com/videos/play/wwdc2017/229/
(Building Great Document-based Apps in iOS 11)

Most of us here have a 'Love & Hate' relationship with iTunes File Sharing and much prefer to use other file managers...

This simple addition would bring the content of the apps Documents folder easily accessible thru the iOS 11 Files.app and all other apps that use the standard Document Picker!

Just think about it, browse the apps Documents folder to access the files when needed.
No need to use DropBox or other Could-Services to transfer files from one app to another.

I do feel that this is one of the single most important productivity boosts for iOS musicians!

The best part of this is that no additional coding is needed. Just a small modification to the apps Info.plist file!

Since manually hacking existing *.ipa bundles would ruin the signing of the app developers need to update the info.plist file and re-upload the app to the Appstore.

I'm seriously looking forward to the release of iOS11!
/Samuel

Comments

  • The user and all related content has been deleted.
  • @Max23 said:
    Any info if the files folder is searchable with the system search?
    Any Siri yadda yadda?
    Don't want to spend an h watching this.
    (Together with drag and drop this is the bomb, hello computer, good by telephone os)

    The content can be index by spotlight on iOS so the answer is YES to that one ;)

  • I agree and hope that all developers make it possible, good that it's an easy modification.

  • edited June 2017
    The user and all related content has been deleted.
  • So does this just mean you can copy files between apps easier and not that a file stored in one location can be directly used at runtime by various apps?

  • @AudioGus said:
    So does this just mean you can copy files between apps easier and not that a file stored in one location can be directly used at runtime by various apps?

    You can directly access the files created by the other apps and copy if needed which is usually a good idea anyway so the original doesn't get messed up :)

  • edited June 2017

    @Samu said:

    @AudioGus said:
    So does this just mean you can copy files between apps easier and not that a file stored in one location can be directly used at runtime by various apps?

    You can directly access the files created by the other apps and copy if needed which is usually a good idea anyway so the original doesn't get messed up :smile:

    Uhhh... wait. Can I have a file in one place accessed by two apps (say Auria and Cubasis) without duplicating it several times on my iPad? Your answer made it sound as though I have options of some sort but I am curious about the requirements due to OS limitations.

    EDIT: deleted low blood sugar bitching

  • @Samu, thanks for bringing it up, noted.

  • edited June 2017

    @AudioGus your point is not well thought out ;)
    what you describe only works in a very limited way on any 'professional' system under any OS.
    It requires that the original samples CANNOT be altered.
    Physical copies of the original data are the common way, often unnoticed by the user as the respective software does it in a background process.

  • @Telefunky said:
    @AudioGus your point is not well thought out ;)
    what you describe only works in a very limited way on any 'professional' system under any OS.
    It requires that the original samples CANNOT be altered.
    Physical copies of the original data are the common way, often unnoticed by the user as the respective software does it in a background process.

    lol

  • Class
    UIDocumentBrowserViewController
    A view controller for browsing and performing actions on documents stored locally and in the cloud.

    Overview
    With the document browser view controller, users can browse through and access their documents. By default, the document browser can access both the system’s local file provider and its iCloud file provider.
    The local file provider grants access to all the documents in the app’s Documents directory. Users can also access documents from another app’s Documents directory, if that app declares either the UISupportsDocumentBrowser key, or both the UIFileSharingEnabled and LSSupportsOpeningDocumentsInPlace keys in its Info.plist file. When the user opens a document from another app's Documents directory, they are editing the document in place. The changes are saved to the other app's Documents directory.
    The iCloud file provider creates a folder for your app in the user’s iCloud Drive. Users can access documents from this folder, or from anywhere in their iCloud Drive. The system automatically handles access to iCloud for you; you do not need to enable your app’s iCloud capabilities.
    Third-party storage services can also provide access to the documents they manage by implementing a File Provider extension (iOS 11 or later). For more information, see FileProvider.

  • @Mark B said:
    Class
    UIDocumentBrowserViewController
    A view controller for browsing and performing actions on documents stored locally and in the cloud.

    Overview
    With the document browser view controller, users can browse through and access their documents. By default, the document browser can access both the system’s local file provider and its iCloud file provider.
    The local file provider grants access to all the documents in the app’s Documents directory. Users can also access documents from another app’s Documents directory, if that app declares either the UISupportsDocumentBrowser key, or both the UIFileSharingEnabled and LSSupportsOpeningDocumentsInPlace keys in its Info.plist file. When the user opens a document from another app's Documents directory, they are editing the document in place. The changes are saved to the other app's Documents directory.
    The iCloud file provider creates a folder for your app in the user’s iCloud Drive. Users can access documents from this folder, or from anywhere in their iCloud Drive. The system automatically handles access to iCloud for you; you do not need to enable your app’s iCloud capabilities.
    Third-party storage services can also provide access to the documents they manage by implementing a File Provider extension (iOS 11 or later). For more information, see FileProvider.

    Whoa hugeness!!

  • edited June 2017

    @Mark B said:
    . When the user opens a document from another app's Documents directory, they are editing the document in place. The changes are saved to the other app's Documents directory.

    Woah! OK, I think we have actually hit on some valuable layman's/dock worker english here.

    So from the sounds of it (assuming the following apps adopt this) I should be able to have 200 gigs of samples in Audioshare. I could load up Egoist and access all 200 gigs of those samples. I could load up Borderlands and access all 200 gigs of those samples. ETC. I do not need to copy any samples into Egoist or Borderlands to do this...

    Correct?

  • I'll make it so.

  • The apps need to be updated to the 11 SDK to take advantage of this. What's not clear to me is if apps built for lower iOS versions can just add the key to the Info.plist to have their document folder viewable.

  • @AudioGus said:

    @Mark B said:
    . When the user opens a document from another app's Documents directory, they are editing the document in place. The changes are saved to the other app's Documents directory.

    Woah! OK, I think we have actually hit on some valuable layman's/dock worker english here.

    So from the sounds of it (assuming the following apps adopt this) I should be able to have 200 gigs of samples in Audioshare. I could load up Egoist and access all 200 gigs of those samples. I could load up Borderlands and access all 200 gigs of those samples. ETC. I do not need to copy any samples into Egoist or Borderlands to do this...

    Correct?

    The way is seems to work is it requires user interaction (for security) to access the files stored in another app. So you need to open the document picker and select one or multiple files to open in the app.

  • @AudioGus said:

    @Samu said:

    @AudioGus said:
    So does this just mean you can copy files between apps easier and not that a file stored in one location can be directly used at runtime by various apps?

    You can directly access the files created by the other apps and copy if needed which is usually a good idea anyway so the original doesn't get messed up :smile:

    Uhhh... wait. Can I have a file in one place accessed by two apps (say Auria and Cubasis) without duplicating it several times on my iPad? Your answer made it sound as though I have options of some sort but I am curious about the requirements due to OS limitations.

    EDIT: deleted low blood sugar bitching

    yep you sure can

  • @Mark B said:
    The apps need to be updated to the 11 SDK to take advantage of this. What's not clear to me is if apps built for lower iOS versions can just add the key to the Info.plist to have their document folder viewable.

    As I've understood it the system level service exposes the apps 'Documents' folder ones they are correctly tagged in the info.plist file (no need to change the apps code).

    So it should be of no harm to add the tags to the info.plist file of an existing app and install it under iOS11 to check the functionality?

  • Looks like it might be time to put the Beanie Babies up on Ebay.

  • @Samu said:

    @Mark B said:
    The apps need to be updated to the 11 SDK to take advantage of this. What's not clear to me is if apps built for lower iOS versions can just add the key to the Info.plist to have their document folder viewable.

    As I've understood it the system level service exposes the apps 'Documents' folder ones they are correctly tagged in the info.plist file (no need to change the apps code).

    So it should be of no harm to add the tags to the info.plist file of an existing app and install it under iOS11 to check the functionality?

    Looks like it does need the app built for iOS 11 :/
    I just did a test with Xcode 9. I set the "Application supports iTunes file sharing" and "UISupportsDocumentBrowser" keys and then set the app to create a Documents folder with a subfolder. Building the app with a target for iOS 10.3 does not show anything in the Files app but building it for 11.0 shows the app with the folder.

  • @Mark B said:

    Looks like it does need the app built for iOS 11 :/
    I just did a test with Xcode 9. I set the "Application supports iTunes file sharing" and "UISupportsDocumentBrowser" keys and then set the app to create a Documents folder with a subfolder. Building the app with a target for iOS 10.3 does not show anything in the Files app but building it for 11.0 shows the app with the folder.

    Thanks for the explanation, good to know!

    The dilemma here will be how to support iOS10 while still taking advantage of the new iOS11 features?!
    (Personally I'll go full on iOS11 when gets released).

    Considering all the nice features in iOS11 will bring it's likely going to be one of the fastest transitions in iOS history!

  • @Samu said:
    Considering all the nice features in iOS11 will bring it's likely going to be one of the fastest transitions in iOS history!

    Probably the highest number of beta testers as well!

  • edited June 2017

    Agree with you. I hope the devs are able to quickly support iOS 11. looking at some music apps they built for older versions, maybe to get the largest possible audience. For example the new Mood synth is iOS 8.

  • You can can build with a higher iOS SDK and set a lower deployment target. But not until the iOS version has been officially released. So we can't do that until iOS 11 is the current version.

Sign In or Register to comment.