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.

Strange error message on Mac, latest Big Sur

2»

Comments

  • edited July 2021
    The user and all related content has been deleted.
  • edited July 2021

    @tja said:

    @SevenSystems said:
    Now imagine how exciting all this becomes when you actually DO want to deploy to the App Store, and need "entitlements" from Apple, and have to upgrade your Xcode (12 GB download) AND macOS (another 12 GB download) for every point update of iOS (with the added "bonus" that the latest Xcode never actually supports deploying to a device running the latest iOS (I'm not kidding!)).

    Good stuff! ;)

    Sounds like I will issue hate speech for days and weeks, then :smiley:

    We will see ...

    EDIT: But I am lucky to have a stable 100Mbit connection ... so 12 GB are not such a problem. 20 some minutes and it's there.

    I have an unstable 10 Mbit connection that costs 1 Euro per GB 😉 (it might be 50 cents or so, can't remember)

    But I still find it kinda outrageous that an IDE and compiler is 12 GIGABYTES. I mean, 12 MEGABYTES would be plenty!

    (yes yes, I know it includes all the damn simulators and documentation and whatnot, but why isn't that optional and why are there no delta updates?)

  • The user and all related content has been deleted.
  • @tja said:

    @SevenSystems said:
    I have an unstable 10 Mbit connection that costs 1 Euro per GB 😉

    Uhhh.

    Ireland also has some negative points ;-)
    Mine is a flatrate for ... 30 Euro monthly or so.

    But that's a fixed line connection right? I'm on an LTE connection because I always have to move house so a fixed contract doesn't make any sense...

    P.S.

    Is it really required to create 28 App Icons of different sizes?
    :D :D :D

    I use https://makeappicon.com for that! Auto-generates all sizes (the whole "asset catalog") from one high-res image.

    (yeah, for being a 12 GB download, they could've included that functionality in Xcode itself 😂)

  • @NeonSilicon said:

    @tja said:
    I just created a new Multiplatform Document App project, compiled it - which worked - but already here, I see error messages:

    2021-07-25 19:34:33.691651+0200 DocumentApp[2914:116157] +[NSSavePanel _warmUp] obviated
    2021-07-25 19:34:48.152925+0200 DocumentApp[2914:116157] [framework] CoreUI: Error Domain=NSCocoaErrorDomain Code=260 "RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: MyID.DocumentApp" UserInfo={NSLocalizedDescription=RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: MyID.DocumentApp}
    2021-07-25 19:34:48.153635+0200 DocumentApp[2914:116157] [framework] CoreUI: Error Domain=NSCocoaErrorDomain Code=260 "RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: MyID.DocumentApp" UserInfo={NSLocalizedDescription=RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: MyID.DocumentApp}
    2021-07-25 19:34:48.154024+0200 DocumentApp[2914:116157] [framework] CoreUI: Error Domain=NSCocoaErrorDomain Code=260 "RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: com.apple.AppKit" UserInfo={NSLocalizedDescription=RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: com.apple.AppKit}
    2021-07-25 19:34:48.154109+0200 DocumentApp[2914:116157] [framework] CoreUI: Error Domain=NSCocoaErrorDomain Code=260 "RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: com.apple.AppKit" UserInfo={NSLocalizedDescription=RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: com.apple.AppKit}
    2021-07-25 19:35:19.517562+0200 DocumentApp[2914:117344] [scoped] handle 0: sandbox_extension_release error [22: Invalid argument]
    2021-07-25 19:35:19.517601+0200 DocumentApp[2914:117344] [scoped] <0x600000333840 file:///Users/tja/Documents/Untitled.exampletext>: internal sandbox error for <StopAccessing>
    

    Apple is so strange in everything.
    I really wonder how people manage to develop App.

    Many of Apple's templates for project types are a complete mess. Sometimes it makes sense because the missing pieces are really project dependent. But the current AUv3 templates in particular are really confusing -- multiple and redundant files in Swift or Objective-C, some are empty, and the whole result is just confusing.

    Frankly, I wonder if this disarray is a side-effect of the programmers working at home and not being in the office together. Things can quickly spin out of control if people are not in constant contact with each other, even in this age of FaceTime and Zoom.

  • edited July 2021
    The user and all related content has been deleted.
  • @NeuM said:

    @NeonSilicon said:

    @tja said:
    I just created a new Multiplatform Document App project, compiled it - which worked - but already here, I see error messages:

    2021-07-25 19:34:33.691651+0200 DocumentApp[2914:116157] +[NSSavePanel _warmUp] obviated
    2021-07-25 19:34:48.152925+0200 DocumentApp[2914:116157] [framework] CoreUI: Error Domain=NSCocoaErrorDomain Code=260 "RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: MyID.DocumentApp" UserInfo={NSLocalizedDescription=RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: MyID.DocumentApp}
    2021-07-25 19:34:48.153635+0200 DocumentApp[2914:116157] [framework] CoreUI: Error Domain=NSCocoaErrorDomain Code=260 "RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: MyID.DocumentApp" UserInfo={NSLocalizedDescription=RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: MyID.DocumentApp}
    2021-07-25 19:34:48.154024+0200 DocumentApp[2914:116157] [framework] CoreUI: Error Domain=NSCocoaErrorDomain Code=260 "RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: com.apple.AppKit" UserInfo={NSLocalizedDescription=RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: com.apple.AppKit}
    2021-07-25 19:34:48.154109+0200 DocumentApp[2914:116157] [framework] CoreUI: Error Domain=NSCocoaErrorDomain Code=260 "RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: com.apple.AppKit" UserInfo={NSLocalizedDescription=RunTimeThemeRefForBundleIdentifierAndName() couldn't find NSAppearanceNameAccessibilityVibrantLight.car in bundle with identifier: com.apple.AppKit}
    2021-07-25 19:35:19.517562+0200 DocumentApp[2914:117344] [scoped] handle 0: sandbox_extension_release error [22: Invalid argument]
    2021-07-25 19:35:19.517601+0200 DocumentApp[2914:117344] [scoped] <0x600000333840 file:///Users/tja/Documents/Untitled.exampletext>: internal sandbox error for <StopAccessing>
    

    Apple is so strange in everything.
    I really wonder how people manage to develop App.

    Many of Apple's templates for project types are a complete mess. Sometimes it makes sense because the missing pieces are really project dependent. But the current AUv3 templates in particular are really confusing -- multiple and redundant files in Swift or Objective-C, some are empty, and the whole result is just confusing.

    Frankly, I wonder if this disarray is a side-effect of the programmers working at home and not being in the office together. Things can quickly spin out of control if people are not in constant contact with each other, even in this age of FaceTime and Zoom.

    Could be I guess, it could at the very least be making moving forward with the changes more difficult for them. My general cynical feeling though is that some in the audio team really don't see the move to Swift or even Objective-C as the right way to go so the disarray in the template is reflective of this. (I don't actually disagree with this mindset either. My own personal feeling is that these interfaces should be defined in C and then made available in higher level languages.)

Sign In or Register to comment.