ProJucer possible bug

#1

Can anyone verify the following with ProJucer:

create a brand new Audio Plugin project.
Export to Xcode, Build all.
Open PluginVal, Test File (navigate to the compiled AU in ~/Library/Audio/Plug-ins/Components/)

All Test Passed

close xcode project, delete Builds folder, delete the compiled Audio Unit

now, go back to ProJucer, CHECK the following:
Plugin Formats: VST3, AU, Standalone (these are the half-checked default options)
Plugin Characteristics: Plugin Is A Synth, Plugin MIDI Input
Plugin AU Main Type: kAudioUnitType_MusicDevice
Save, export to Xcode, Build All
Open PluginVal, Test File (navigate to the compiled AU in ~/Library/Audio/Plug-ins/Components/)

Num types found: 0
!!! Test 1 failed: No types found
FAILED!!  1 test failed, out of a total of 1

clean Builds folder, delete the compiled Audio Unit
go back to ProJucer, UNCHECK the following:
Plugin Formats: VST3, AU, Standalone (these are the half-checked default options)
Plugin Characteristics: Plugin Is A Synth, Plugin MIDI Input
Plugin AU Main Type: kAudioUnitType_MusicDevice

save, export, rebuild, test with PluginVal

Num types found: 0
!!! Test 1 failed: No types found
FAILED!!  1 test failed, out of a total of 1

clean Builds folder, delete the compiled Audio Unit
go back to ProJucer, RE-CHECK the following:
Plugin Formats: VST3, AU, Standalone (these are the half-checked default options)
Plugin Characteristics: Plugin Is A Synth, Plugin MIDI Input
Plugin AU Main Type: kAudioUnitType_MusicDevice
save, export, rebuild, test with PluginVal

Time taken to run all tests: 14 secs
All tests completed successfully

Finished validating: /Users/xxxx/Library/Audio/Plug-Ins/Components/TestPlugin.component
ALL TESTS PASSED

I would love to not be the only person experiencing this bug. This happens in both 5.4.1 and the latest commit from the development branch.

0 Likes

#2

Do you get any similar errors from auval?

0 Likes

#3

I’ll test. the plugin wasn’t even showing up in Logic’s list of scanned plugins until I did the re-check/uncheck of those boxes, resave/rebuild steps a couple times.

0 Likes

#4

Ok, when testing in AuVal, I just get a bunch of

ERROR: Cannot get Component's Name strings
ERROR: Error from retrieving Component Version: -50

* * FAIL
--------------------------------------------------
TESTING OPEN TIMES:
FATAL ERROR: didn't find the component

for these settings:
44%20PM

unchecking EVERYTHING:


51%20PM
gets this result:

$ auval -v aufx Tstp Manu

    AU Validation Tool
    Version: 1.6.1a1 
    Copyright 2003-2013, Apple Inc. All Rights Reserved.
    Specify -h (-help) for command options

--------------------------------------------------
VALIDATING AUDIO UNIT: 'aufx' - 'Tstp' - 'Manu'
--------------------------------------------------
ERROR: Cannot get Component's Name strings
ERROR: Error from retrieving Component Version: -50

* * FAIL
--------------------------------------------------
TESTING OPEN TIMES:
FATAL ERROR: didn't find the component

Could this be related to the High Sierra - restart required bug?

0 Likes

#5

Sorry @t0m This appears to be that High Sierra ‘restart-required’ bug and nothing more. Apologies for the distraction!

0 Likes