# Cubase 10 Mac OSX

**URL:** <https://forum.juce.com/t/cubase-10-mac-osx/31477>\
**Category:** Audio Plugins\
**Created:** [January 26, 2019, 3:53pm UTC](https://forum.juce.com/t/cubase-10-mac-osx/31477 "2019-01-26T15:53:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![TypeWrit3r](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/typewrit3r/32/3993_2.png) [@TypeWrit3r](https://forum.juce.com/u/TypeWrit3r)\
**Post date:** [January 26, 2019, 3:53pm UTC](https://forum.juce.com/t/cubase-10-mac-osx/31477/1 "2019-01-26T15:53:37Z")

</div>

I have one Juce plugin, that works on the new Cubase 10 and another that is not showing up at all?

Any ideas where to start?

---

<div class="post-metadata">

**Author:** ![lalala](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/lalala/32/8577_2.png) [@lalala](https://forum.juce.com/u/lalala)\
**Post date:** [January 26, 2019, 7:34pm UTC](https://forum.juce.com/t/cubase-10-mac-osx/31477/2 "2019-01-26T19:34:44Z")

</div>

> [@TypeWriterAudio](#):
>
> Any ideas where to start?

you can test your plugin with pluginval : [GitHub - Tracktion/pluginval: Cross platform plugin testing and validation tool](https://github.com/Tracktion/pluginval)

---

<div class="post-metadata">

**Author:** ![TypeWrit3r](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/typewrit3r/32/3993_2.png) [@TypeWrit3r](https://forum.juce.com/u/TypeWrit3r)\
**Post date:** [January 29, 2019, 8:14pm UTC](https://forum.juce.com/t/cubase-10-mac-osx/31477/3 "2019-01-29T20:14:10Z")

</div>

I used that, and said it all passed. Could it be the plugin code?

It is scanned during start up, however it’s not recognized. It’s only this daw. I don’t have the new mac version or cubase 10.

---

<div class="post-metadata">

**Author:** ![KoenTanghe](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/koentanghe/32/533_2.png) [@KoenTanghe](https://forum.juce.com/u/KoenTanghe)\
**Post date:** [January 31, 2019, 4:43pm UTC](https://forum.juce.com/t/cubase-10-mac-osx/31477/4 "2019-01-31T16:43:03Z")

</div>

Long shot, but: maybe double-check that your “missing” plugin and Cubase 10 are both 64-bit (or both 32-bit if Cubase 10 still supports that)?

---

<div class="post-metadata">

**Author:** ![lalala](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/lalala/32/8577_2.png) [@lalala](https://forum.juce.com/u/lalala)\
**Post date:** [February 1, 2019, 10:06am UTC](https://forum.juce.com/t/cubase-10-mac-osx/31477/5 "2019-02-01T10:06:19Z")

</div>

> [@TypeWriterAudio](#):
>
> I used that, and said it all passed.

be sure to not only test your release build with a release build of pluginVal.  
rather debug you plugin with it, so that you can get the assertions being triggered.

also, it’s unlikely that this is your case, but be sure that the name of the package (Plugin.vst) does match exactly (case sensitive) the name of the executable (Plugin.vst/Contents/MacOS/Plugin)  
I had a plugin not showing up in cubase10 because of that.