I been trialling AudioCodex and like it a lot. But as I have a couple of audio interfaces (Line 6 TonePort UX2 and Presonus Firebox) I often change my audio interface to which ever one I've got connected - as I'm playing my guitar with a track. In GarageBand I can select which audio interface to use - then I can use that in GB. I also have SoundSource (from Rogue Amoeba) that easily in the menu lets me select the audio interface to use for input, output and system sounds - saving launching Sys Pref panel and AudioMidi Setup.

In iTunes it recognises the change and I can then play my guitar into my MacBook through my audio interface and out into my powered speakers. And it will play both the Itunes stream and the real guitar stream out together. However, with AudioCodex (AC) it does not recognise the change of interface, and I have to quit AudioCodex and re-launch it. There is no where I have found to select the audio interface from within AC. It is because I want to jam along with a track in AC - where I can easily change the pitch and the tempo as well as loop parts to help practice.

Ideally. I'd like to see both features in a future release, but at present one of them would be a good step forward.

Thanks
Vince

Hi Vince,

At launch AudioCodex always selects the output device specified as the Default Output in Audio Midi Setup; AudioCodex 'links' to the device itself, and currently won't automatically re-link to a different device if the Default Output device is changed. You can instead manually switch between the available output devices on your system at any time using the 'Device' popup button on the 'Output' section of the 'Adjust' tab of the Inspector.

However, in testing this morning I have discovered that this functionality is currently broken, and any attempt to change devices using the 'Device' popup button will cause Core Audio playback to fail; when we introduced our internal FFT analyzer (several releases hence), the configuration of the AUGraph which AudioCodex uses for CoreAudio playback changed, and I neglected to update a reference in the device switching code to match this change... my bad

I have fixed this issue this morning, so the fix will be included in the next update, but for now, the workarounds are to either quit & relaunch AudioCodex, or otherwise you may wish to try the 'Reset Audio Engine' menu item in the 'Advanced' submenu of the 'Help' menu; this will re-link AC to the output device specified as the Default Output in Audio Midi Setup without the need to quit & relaunch.

There are some annoying issues with 'Reset Audio Engine' function; in testing today I noticed that the Mix volume is being set to maximum internally, without updating the Mix volume slider visually, so you should tweak the Mix volume slider after using this function; you will also need to manually re-initiate playback, as any current Core Audio playback will stop.

Thanks for raising this issue, we will get a patched update available as soon as possible. I'll also look at the possibility of providing an option to have AudioCodex switch devices automatically if it is using the Default Output device.

Cheers,

Mantis

I'm glad to have helped improve and hone the functionality of AC. And I continue to be impressed with the rapid response and attention to detail.It inspires confidence in the products and the company!

Vince

Mantis,
I think I'm having a similar issue. AC will display my MOTU interface but when I select it, it goes to the QT setup. My MOTU is the default in the MIDI setup. Same thing? and will the patch be available in that AC is a important part of my studio setup?

Thanks

Hi Dogma,

I don't have access to a MOTU rig for testing, but it sounds like you are falling foul of this same bug; using the 'Device' popup to change Output device in 1.49 'breaks' the CoreAudio signal processing graph, which forces AudioCodex into QuickTime mode until such time as the app is either reset by using the 'Help:Advanced:Reset Audio Engine' menu item or else quit & relaunched... my bad for not testing device switching more thoroughly before releasing the last update

The good news is that the Device menu has been fixed for our impending version 1.5 release. As well as restoring manual device-selecting functionality, we've also added a new 'Default Output' option that forces AudoCodex to use whatever device is set as the 'Default Output' at the System-level, and to automatically switch devices on-the-fly if the 'Default Output' device changes.

We're projecting 1.5 to be in-the-wild sometime in the next two weeks, so watch this space, bugfixes for these issues should be close at hand

Cheers,

Mark