# AudioDeviceManager

**URL:** <https://forum.juce.com/t/audiodevicemanager/878>\
**Category:** General JUCE discussion\
**Created:** [June 10, 2006, 3:29pm UTC](https://forum.juce.com/t/audiodevicemanager/878 "2006-06-10T15:29:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![haydxn](https://avatars.discourse-cdn.com/v4/letter/h/5fc32e/32.png) [@haydxn](https://forum.juce.com/u/haydxn)\
**Post date:** [June 10, 2006, 3:29pm UTC](https://forum.juce.com/t/audiodevicemanager/878/1 "2006-06-10T15:29:25Z")

</div>

Hey, just wondering…

It’s uber handy indeed consolidating the device selection settings together into one neat AudioDeviceManager class, and having the popup component to change these settings. However, even though it’s easy enough to handle Midi output yourself, i think it’s pretty strange that it’s not included in that little scheme. Is there any reason for this? I feel that it’s a bit of a shame having a single helpful pop-up panel for choosing devices but needing a separate place to choose MIDI output port selection.

or is it just something that you’ve not had time to do?

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [June 12, 2006, 8:22am UTC](https://forum.juce.com/t/audiodevicemanager/878/2 "2006-06-12T08:22:26Z")

</div>

Hmm - I guess it’s mostly just because I’ve not got round to it, and because there’s a lot less demand these days for using a midi out than a midi in…

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [May 12, 2017, 10:01am UTC](https://forum.juce.com/t/audiodevicemanager/878/3 "2017-05-12T10:01:46Z")

</div>

Closed on May 12, 2017, 10:01am UTC


