# HELP: Newer in Audio Plugin

**URL:** <https://forum.juce.com/t/help-newer-in-audio-plugin/16057>\
**Category:** The Projucer\
**Created:** [November 25, 2015, 3:58pm UTC](https://forum.juce.com/t/help-newer-in-audio-plugin/16057 "2015-11-25T15:58:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nycholas\_Maia](https://avatars.discourse-cdn.com/v4/letter/n/45deac/32.png) [@Nycholas\_Maia](https://forum.juce.com/u/Nycholas_Maia)\
**Post date:** [November 25, 2015, 3:58pm UTC](https://forum.juce.com/t/help-newer-in-audio-plugin/16057/1 "2015-11-25T15:58:08Z")

</div>

Hi, I'm newer in JUCE and I need to create a simple VST Audio Plugin.  
  
Here I post a PDF file attached with a list of errors of ProJucer 4.0.2.

What I did to see this list of errors:

1- Open ProJucer -\> New Project  
2- Audio Plugin (MacOSX - XCode)  
3- Config Tab: just BUILD VST and BUILD VST 3 enable  
4- Mark: Plugin is a Synth, Plugin MIDI input, Plugin MIDI output  
5- In Config Tab: XCode (Mac OSX): I set a full path of the VST 3 SDK Folder: /Applications/VST3\_SDK/  
6- In Release and Debug: I set&nbsp;OSX 10.10&nbsp;in OSX Base SDK Version, Deployment Target  
7- OSX Arquiteture: 64 bits Intel

Then I click:&nbsp;Menu Build -\> Clean All

**Then Projucer start to build...and I see this list of errors attached here.**

I saw&nbsp;some warnings....That some AudioHardwareService is deprecated in OSX 10.11 (El Captain)...but I'm using 10.10 (Yosemite)...

And I saw one error: "enumerator value evaluates to -2147483648, which cannot be narrowed to type uint32\_t (aka unsingned int)"

What can I do?

My system:

OSX 10.10.5 (Yosemite)  
VST SDK 3.6.5  
ProJUCER 4.0.2

Thanks!  
Nyck

---

<div class="post-metadata">

**Author:** ![jgerrard](https://avatars.discourse-cdn.com/v4/letter/j/b782af/32.png) [@jgerrard](https://forum.juce.com/u/jgerrard)\
**Post date:** [November 25, 2015, 11:10pm UTC](https://forum.juce.com/t/help-newer-in-audio-plugin/16057/2 "2015-11-25T23:10:25Z")

</div>

Hmm, this should have been fixed a while ago, but a few users (including yourself) have been reporting it again recently.

The fact that you're using 10.10 is curious, I'll take a look at this soon. Thanks for the report!