# Suggestion: MIDI output for standalone plugins

**URL:** <https://forum.juce.com/t/suggestion-midi-output-for-standalone-plugins/26170>\
**Category:** Audio Plugins\
**Created:** [January 29, 2018, 6:00pm UTC](https://forum.juce.com/t/suggestion-midi-output-for-standalone-plugins/26170 "2018-01-29T18:00:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![erteash](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@erteash](https://forum.juce.com/u/erteash)\
**Post date:** [January 29, 2018, 6:00pm UTC](https://forum.juce.com/t/suggestion-midi-output-for-standalone-plugins/26170/1 "2018-01-29T18:00:48Z")

</div>

For some plug-ins like MIDI effects or arpegiators in standalone mode, there is a need for a MIDI output to connect to a host or another device. Is it possible to have this feature added to JUCE in next updates?

---

<div class="post-metadata">

**Author:** ![t0m](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/t0m/32/16413_2.png) [@t0m](https://forum.juce.com/u/t0m)\
**Post date:** [February 5, 2018, 6:05pm UTC](https://forum.juce.com/t/suggestion-midi-output-for-standalone-plugins/26170/2 "2018-02-05T18:05:59Z")

</div>

I’ll add this to the list to things to look at. No promises on any timeframes though!

---

<div class="post-metadata">

**Author:** ![nikolas-k](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/nikolas-k/32/2307_2.png) [@nikolas-k](https://forum.juce.com/u/nikolas-k)\
**Post date:** [June 4, 2018, 8:53pm UTC](https://forum.juce.com/t/suggestion-midi-output-for-standalone-plugins/26170/3 "2018-06-04T20:53:27Z")

</div>

Bump! Are there any news on this?

---

<div class="post-metadata">

**Author:** ![ed95](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ed95/32/7635_2.png) [@ed95](https://forum.juce.com/u/ed95)\
**Post date:** [August 21, 2018, 11:17am UTC](https://forum.juce.com/t/suggestion-midi-output-for-standalone-plugins/26170/4 "2018-08-21T11:17:35Z")

</div>

[https://github.com/WeAreROLI/JUCE/commit/92141bf2792b4a8d5645087a80db4dc7e752f7a4](https://github.com/WeAreROLI/JUCE/commit/92141bf2792b4a8d5645087a80db4dc7e752f7a4)

---

<div class="post-metadata">

**Author:** ![erteash](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@erteash](https://forum.juce.com/u/erteash)\
**Post date:** [August 21, 2018, 10:23pm UTC](https://forum.juce.com/t/suggestion-midi-output-for-standalone-plugins/26170/5 "2018-08-21T22:23:29Z")

</div>

That looks great. It lists all the devices available as a midi output.  
But is it possible for the stand alone to create its own midi device? Then it can be used in other apps similar to a physical midi controller.

---

<div class="post-metadata">

**Author:** ![t0m](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/t0m/32/16413_2.png) [@t0m](https://forum.juce.com/u/t0m)\
**Post date:** [August 22, 2018, 8:02am UTC](https://forum.juce.com/t/suggestion-midi-output-for-standalone-plugins/26170/6 "2018-08-22T08:02:45Z")

</div>

Not in a cross platform way, unfortunately. It’s relatively easy to do this on MacOS but Windows doesn’t support virtual MIDI devices.