# Future direction with plugin and control surface

**URL:** <https://forum.juce.com/t/future-direction-with-plugin-and-control-surface/19455>\
**Category:** General JUCE discussion\
**Created:** [October 12, 2016, 11:21pm UTC](https://forum.juce.com/t/future-direction-with-plugin-and-control-surface/19455 "2016-10-12T23:21:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lob](https://avatars.discourse-cdn.com/v4/letter/l/ecae2f/32.png) [@lob](https://forum.juce.com/u/lob)\
**Post date:** [October 12, 2016, 11:21pm UTC](https://forum.juce.com/t/future-direction-with-plugin-and-control-surface/19455/1 "2016-10-12T23:21:08Z")

</div>

Hi,  
It is very intimidating posting amongst such great minds, but…

I updated and cleaned all my plugin(months of work) and then decided to go the the latest Projucer. This has meant a rewrite, which is fantastic considering how new things work. The parameters linking to the slider, etc.  
Are you planning on including control surface info in the parameter system? I am going to add control surface code and it would be a pity to go in one direction, when JUCE goes in another. If the answer is “no”, then I will continue as usual. If the answer is “yes”, how could I make my code go in the sort of direction you guys were planning on going?  
Thanks

---

<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:** [October 13, 2016, 7:56am UTC](https://forum.juce.com/t/future-direction-with-plugin-and-control-surface/19455/2 "2016-10-13T07:56:50Z")

</div>

There are no immediate plans to include this as part of JUCE, so go ahead and roll your own!

---

<div class="post-metadata">

**Author:** ![lob](https://avatars.discourse-cdn.com/v4/letter/l/ecae2f/32.png) [@lob](https://forum.juce.com/u/lob)\
**Post date:** [October 13, 2016, 11:43am UTC](https://forum.juce.com/t/future-direction-with-plugin-and-control-surface/19455/3 "2016-10-13T11:43:16Z")

</div>

thanks for the reply

---

<div class="post-metadata">

**Author:** ![carlosbarbosa](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/carlosbarbosa/32/772_2.png) [@carlosbarbosa](https://forum.juce.com/u/carlosbarbosa)\
**Post date:** [October 13, 2016, 5:49pm UTC](https://forum.juce.com/t/future-direction-with-plugin-and-control-surface/19455/4 "2016-10-13T17:49:50Z")

</div>

what is control surface code? can you expand maybe we can help…

---

<div class="post-metadata">

**Author:** ![lob](https://avatars.discourse-cdn.com/v4/letter/l/ecae2f/32.png) [@lob](https://forum.juce.com/u/lob)\
**Post date:** [December 3, 2016, 6:04am UTC](https://forum.juce.com/t/future-direction-with-plugin-and-control-surface/19455/5 "2016-12-03T06:04:54Z")

</div>

Hi Carlos,  
I am looking at connecting an IOS version of my plugin’s UI to the computer plugin. I assume midi control would be the safest way to communicate between the two. I would not want the user to have to set up the individual controls via the DAW. This implementation is currently on hold, but I will get around to it.  
Anyone got an IOS UI version of their plugin talking well to the plugin? Is midi control the only safe way to go?  
Thanks