Audiobus


#1

Hi,

did anybody here ever manage to get Audiobus (http://developer.audiob.us/) to work with JUCE?

Fritz


#2

BUMP!!!

+1,000,000


#3

I’m interested in it too…


#4

Is there any way to get iOSAudioIODevice->audiounit??
I think this would make Audiobus implementation really easy


#5

Hi, 

It would be great if we could have access to the "AudioTimeStamp" by passing it to the audio IO callback.


#6

tricky.....


#7

Jules,

any infos on this ?

 

Thanks,


#8

Too busy with other things to learn about what the AudioBus is or how it works, but if someone wants to send me a suggested patch I'll take a look.


#9

iOS audio apps supporting AudioBus is quickly becoming a new enviroment for audio effects and synths to live in, similar to plugins on the desktop. So I'd love to see this as well (and have received requests from current plugin users for this).

This page might be a good quick read: http://developer.audiob.us/doc/_filtering.html , especially the "Adding Audiobus Filtering Capabilities to an Existing App" section (since Juce can already build for iOS using normal audio IO).

Not sure when I'll have the time to dive into this myself, but when I do, I'll share what would need to be done in Juce to make it work...

 


#10

A friend of mine just forwarded me this Retronymns blog post as an example of getting inter-app audio and AudioBus running. I'm just digging into this now but it looks great, and even has an Xcode project included! Thought it might be useful to you guys:

http://blog.retronyms.com/2013/09/ios7-remoteio-inter-app-audiobus-and-you.html


#11

Has anyone managed to get audiobus or interapp audio working? I'm just now getting back to this on my project and wondering if anyone has had any luck thus far.


#12

I believe you will never be able to support inter app audio (nor Audiobus 2) with the current Juce's audio implementation (which is still based on AudioSession).

The first step would be to rewrite JUCE::iOSAudioIODevice using the AVFoundation framework.

In addition to this, inter app audio and Audiobus require a few additions to the app's plist.


#13

Well, adding a few things to the plist isn't a big deal. Audiobus basically needs you to add 3 things (at least for a sender app): an AudioComponents array, a Bundle display name and a launch URL. While Introjucer doesn't know about those items, it's easy to at least add those in Xcode and then  use the Custom Plist field in Introjucer. 

So what is specifically missing from AudioSession that is needed?


#14

AudioSession is not missing anything per se, it's just completely deprecated (since iOS 7).

As I already said,  Juce's implementation needs a full rewrite based on AVAudioSession.

 


#15

And annoyingly, the newer APIs weren't available until fairly recently, so it's all at the tricky transitional stage where supporting both APIs would be necessary :(


#16

Ah yes, all of the dreaded yellow triangles make sense now. That's annoying huh :(

Jules, how big of a job do you expect this is, and is it something you were planning to address soon?

 

 


#17

It's on my to-do-list.. Probably not a huge job, but also can't promise how soon it'll be.


#18

Plus,  AVFoundation doesn't fully support iOS 5. Yeah I know, iOS 8 is on the way and supporting iOS 5 seems like an awkward thing to do, so just a heads-up.


#19

FYI, AudioBus themselves dropped support for iOS 6 because they found that only 7% of their users were still on it. This ain't Windows -- people don't expect to be using mobile OSs that are two versions behind. 

http://forum.audiob.us/discussion/3798/in-audiobus-2-were-discontinuing-support-for-ios-6/p1


#20

Yeah, I know. I'm in the Audiobus forum since day one.