need some mac testers :)

[iamlamprey]

howdy partners, after a long day of troubleshooting i think I finally got my mac Installer working and signed/notarized/stapled so now I need a few testers before sending it out to my pre-existing customers

if any of you want to give it a spin and let me know what works/doesn't work I'd be very appreciative I've included a free library to load and make sure it can play inside your DAW

Player Download:

Instrument Download:

thanks in advance, those links will be up for a few hours

[ulrik]

@iamlamprey The installation works great all is installed, however the VST3 should go in the "VST3" subfolder

[iamlamprey]

@ulrik Ahh okay, thanks for that!

[iamlamprey]

updated the directory

[ulrik]

@iamlamprey failed in Logic

[d.healey]

Should test with pluginval - https://github.com/Tracktion/pluginval

[Lindon]

@d-healey ..and auval:

https://developer.apple.com/library/archive/documentation/MusicAudio/Conceptual/AudioUnitProgrammingGuide/AudioUnitDevelopmentFundamentals/AudioUnitDevelopmentFundamentals.html#//apple_ref/doc/uid/TP40003278-CH7-SW38

[iamlamprey]

Alrighty I'll get to debugging thanks for that guys I didn't know pluginval was available for mac

[iamlamprey]

Okay everything works for pluginval, but auval prints this out:

ParameterID=1291929201, Scope=0, Element=0: Saved Value = 0.250000, Current Value 0.200000
ERROR: Parameter values are different since last set - probable cause: a Meta Param Flag is NOT set on a parameter that will change values of other parameters.
Cannot perform Parameter Value check across initialization and reset

I think this is the cause of the issue, how do I find that ParameterID inside HISE? I have no idea what it is.

[ustk]

@iamlamprey this mean you have a parameter somewhere that changes the value of another (or more) parameter somewhere else…
find the one that controls the other and set it as meta in the property editor.
How you can find it? only you know this mystery…

[iamlamprey]

Would this Meta Parameter necessity also include things that control other parameters via script?

[iamlamprey]

Okay now I'm a bit more confused... I patched the auval issue (auval passes successfully) but Logic still says my plugin is incompatible due to failing AU Validation.

auval -v aumu Neat Lamp -strict

* * PASS
--------------------------------------------------
AU VALIDATION SUCCEEDED.
--------------------------------------------------

Is there some other check or strictness level above -strict?

[iamlamprey]

Oh I'm dumb, I just had to re-scan in logic

Now everything works

Ok updated original linky again

[iamlamprey]

bumpy bump just need 1 or 2 people to give the updated dmg a go in Logic and I can start sending it out

[DanH]

@iamlamprey fire it over

[iamlamprey]

@danh Links are in first post

[Matt_SF]

@iamlamprey tryed everything here : Installation runs NEATly, instructions are clear. No validation/detection problem in Logic

2 tiny tiny bugish things :

after loading the plugin in Logic > the library is loaded correctly > after reaching 100%, a "Loading 0%" is still displayed :

this just happened once, I reloaded it in Logic and tried in Ableton : the thing was correctly disappearing

The RANDOMIZE menu is not closed automatically when clicking on other sections (sample/FX/etc...). You have to click it again to close it. (unless this is intended)

I'll make some music with the plugin later today and report back if anything comes weird

[iamlamprey]

@matt_sf Thanks so much for that!

[Matt_SF]

@iamlamprey no problem. Really nice job you did here

[DanH]

@iamlampreyOk so I haven't read any install instructions / docs.

• Installed the DMG
• Opened NEAT Player in Logic
• Clicked 'Add Library'
• Installed the Cloudburst .hr1 file you supplied
• Selecting Presets from the Cloudburst folder in the browser...
• No sound!!
• Reopened plugin, no sound, restarted Logic, no sound. Any ideas?

2 things I've noticed:
1 - Your window tabs should close eachother as @Matt_SF mentioned - this also applies to the top tabs (Preset Browser, Add Library) - perhaps put all the buttons in a radio group? @d-healey also has a neat solution for this on his Patreon I think.
2 - The CPU usage is running at about 10% on here!