Question re: iPad audio routing

Started by vtgearhead, July 17, 2017, 05:01:12 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

vtgearhead

I have a pair of Bluetooth headphones linked to my iPad Air 2 and am able to listen to streaming programs played on the device.  I can also turn on the internal microphone and have that signal appear in the phones.  What I'm not able to figure out:  How can route USB audio input (e.g. Roland Go-Mixer) to the phones?  Spent over an hour last evening fooling with this and cannot find the solution.  I can get the mixer signal to appear in Garage Band, but even after selecting monitor it doesn't come through the phones.  If I put GB into record, I get the iPad internal microphone (!) signal active, but never the line input.  Is there some sort of simple routing app available that can do this? 

Searched endlessly on Google, but find nothing exactly on point.

admin

#1
The Go mixer has severe limitations for Guitarists - IOS only see's this as an input device or output device and not capable of full duplex audio  ( so not possible for use with BIAS, ToneStack, JamUP for real time audio processing

rerouting audio within IOS apps requires a third party app (and added latency) of AUM IOS Mixer
https://www.vguitarforums.com/smf/index.php?topic=21187.msg153035#msg153035
http://kymatica.com/Software/AUM

vtgearhead

Quote from: admsustainiac on July 17, 2017, 08:37:54 AM
The Go mixer has severe limitations for Guitarists - IOS only see's this as an input device or output device and not capable of full duplex audio  ( so not possible for use with BIAS, ToneStack, JamUP for real time audio processing

rerouting audio within IOS apps requires a third party app (and added latency) of AUM IOS Mixer

Ah, so simple one-way routing from USB audio in to bluetooth headphone out is not generally possible?  Or, are there other types of iPad audio input schemes that do support this?

Elantric

1st of all - its pointless to use BlueTooth Audio for any serious music composition  / live performance work - due to the high latency - which at best hovers at 45 milliseconds  - but typically 120 to 240 miliseconds   

vtgearhead

Agreed.  I had no idea it was that bad.