# JUCE Assertion failure in juce\_VST\_Wrapper.cpp:1783

**URL:** <https://forum.juce.com/t/juce-assertion-failure-in-juce-vst-wrapper-cpp-1783/19307>\
**Category:** General JUCE discussion\
**Created:** [September 29, 2016, 5:17pm UTC](https://forum.juce.com/t/juce-assertion-failure-in-juce-vst-wrapper-cpp-1783/19307 "2016-09-29T17:17:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![AmpZ](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@AmpZ](https://forum.juce.com/u/AmpZ)\
**Post date:** [September 29, 2016, 5:17pm UTC](https://forum.juce.com/t/juce-assertion-failure-in-juce-vst-wrapper-cpp-1783/19307/1 "2016-09-29T17:17:45Z")

</div>

The code at this assertion says “if this assertion is hit file a bug” so I’m here to try and troubleshoot it.

I have a Juce-based plug-in that I’m loading in a Juce-based host, both on Linux. The plug-in itself is an instrument, takes no inputs, and `getDefaultLayoutForChannelNumAndBus` correctly returns `AudioChannelSet::disabled()`. Accordingly the filter returns true when setting this as the preferred bus arrangement, so the assert `jassert ((! set.isDisabled()) && success);` fires.

Immediately afterwards, the host process is killed due to a floating point exception for reasons I can’t discern since all the variables displayed in the debugger make sense.

Should I be overriding my plug-in’s `setPreferredBusArrangement` to return false if a disabled set is provided even though it is technically a totally acceptable bus arrangement? Is there some other bit of information I’m missing?

---

<div class="post-metadata">

**Author:** ![fr810](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/fr810/32/841_2.png) [@fr810](https://forum.juce.com/u/fr810)\
**Post date:** [September 30, 2016, 3:17pm UTC](https://forum.juce.com/t/juce-assertion-failure-in-juce-vst-wrapper-cpp-1783/19307/2 "2016-09-30T15:17:21Z")

</div>

Can I see the simplified version of your AudioProcessor? That would help me to debug this. In any case, this bug is probably already fixed on develop - but you’ll need to update your code. Look at the JUCE/examples/PlugInSamples/MultiSynth example on the develop branch and modify it to only have a single bus.

---

<div class="post-metadata">

**Author:** ![AmpZ](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@AmpZ](https://forum.juce.com/u/AmpZ)\
**Post date:** [January 13, 2017, 11:45pm UTC](https://forum.juce.com/t/juce-assertion-failure-in-juce-vst-wrapper-cpp-1783/19307/3 "2017-01-13T23:45:08Z")

</div>

Hey Fabian,

Sorry for the months-later reply, your comment about it potentially already being fixed sent me on quite a wild ride of. The short version is that I was indeed using an out-of-date version of JUCE, and while I still see the assert pop up in the terminal from time to time, making sure I have been updating JUCE cleared up the exception so everything is gravy. I’m feeling a little embarrassed about ignoring updates, but I do very much appreciate the reminder, thanks for your help.

---

<div class="post-metadata">

**Author:** ![fr810](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/fr810/32/841_2.png) [@fr810](https://forum.juce.com/u/fr810)\
**Post date:** [January 14, 2017, 1:06pm UTC](https://forum.juce.com/t/juce-assertion-failure-in-juce-vst-wrapper-cpp-1783/19307/4 "2017-01-14T13:06:24Z")

</div>

No problem!&nbsp;&nbsp;
