Released: Free Synthesizer Odin 2 [Win / Mac / Linux]

[TheWaveWarden]

It does not uderstsand the AVX instruction set

Is this true?

Who does not understand? Odin 2 needs your CPU to be able to compute AVX instructions - or else it won't even show in your host.

Hope this answers your question

[empphryio]

Who does not understand? Odin 2 needs your CPU to be able to compute AVX instructions - or else it won't even show in your host.

Hope this answers your question

Excuse me, how does one know if their computer can do AVX instructions? Earlier in the thread you said you would check for me and then never said anything else.
Again: AMD Ryzen 7 1700X Eight-Core Processor 3.40 GHz

[TheWaveWarden]

Who does not understand? Odin 2 needs your CPU to be able to compute AVX instructions - or else it won't even show in your host.

Hope this answers your question

Excuse me, how does one know if their computer can do AVX instructions? Earlier in the thread you said you would check for me and then never said anything else.
Again: AMD Ryzen 7 1700X Eight-Core Processor 3.40 GHz

Sorry, my bad. I expected to have 10-20 beta testers. So far 4000 people downloaded the synth and my inbox is exploding. Needless to say I'm a little overwhelmed

Anyway, back to topic: Your CPU is capable of AVX - are you having trouble loading it? I'm sorry if you've emailed me or bug-reported me about it and I haven't answered- I'll come back to you.

[Spitfire31]

Excuse me, how does one know if their computer can do AVX instructions? Earlier in the thread you said you would check for me and then never said anything else.
Again: AMD Ryzen 7 1700X Eight-Core Processor 3.40 GHz

I'll tell you how. You just get a li'l bit proactive and use a service called, wait for it: Google.

Took me all of thirty seconds to come up with:
https://www.amd.com/en/products/cpu/amd-ryzen-7-1700x

Maybe you could be troubled to scroll down a bit on that page and read for yourself?
Hint: make a browser search for "AVX" on that page.

[empphryio]

Sorry, my bad. I expected to have 10-20 beta testers. So far 4000 people downloaded the synth and my inbox is exploding. Needless to say I'm a little overwhelmed

Anyway, back to topic: Your CPU is capable of AVX - are you having trouble loading it? I'm sorry if you've emailed me or bug-reported me about it and I haven't answered- I'll come back to you.

Oh sorry. Yes it doesn't show up in my list of vsts in my host. I filled out a bug report a few days ago.

[empphryio]

Took me all of thirty seconds to come up with:
https://www.amd.com/en/products/cpu/amd-ryzen-7-1700x

Maybe you could be troubled to scroll down a bit on that page and read for yourself?
Hint: make a browser search for "AVX" on that page.

I did search and didn't come up with it. Thanks so much for your help. How nice of you.

[teilo]

For those having issues getting the plugins to run in Catalina (which is probably everybody), you need to remove the quarantine flag from the plugin file. This is easy to do. Unzip the plugin. Open Terminal. Change to the directory where you unzipped the plugin. Then:

Code: Select all

xattr -d com.apple.quarantine Odin2.component

or

Code: Select all

xattr -d com.apple.quarantine Odin2.vst3

Then move the plugin to the appropriate folder. /Library/Audio/Plug-Ins/Components or /Library/Audio/Plug-Ins/VST3

[TheWaveWarden]

For those having issues getting the plugins to run in Catalina (which is probably everybody), you need to remove the quarantine flag from the plugin file. This is easy to do. Unzip the plugin. Open Terminal. Change to the directory where you unzipped the plugin. Then:

Code: Select all

xattr -d com.apple.quarantine Odin2.component

or

Code: Select all

xattr -d com.apple.quarantine Odin2.vst3

Then move the plugin to the appropriate folder. /Library/Audio/Plug-Ins/Components or /Library/Audio/Plug-Ins/VST3

Wow, thanks for that! You seem to be versed in this matter:
Can I do this before I upload the VST and it will have the same effect?

[Tj Shredder]

Unfortunately no, I don‘t think so...
The official way to do it, is to let it be notarized by Apple. But you need some donations as its not free, you need to subscribe as developer with Apple. In the dev forum here there are threads about the how to, and you‘ll get help there if you want to go that route...

[TheWaveWarden]

Unfortunately no, I don‘t think so...
The official way to do it, is to let it be notarized by Apple. But you need some donations as its not free, you need to subscribe as developer with Apple. In the dev forum here there are threads about the how to, and you‘ll get help there if you want to go that route...

Nah I don't think I will. Maybe I'll be forced to at some point, we'll see.

I'll add the workaround to the FAQs on my homepathe though.

[onerob]

You can also temporarily disable Gatekeeper in Catalina by typing this into Terminal

Code: Select all

sudo spctl --master-disable

Then install the plugin and run it (you may need to go into Security and Privacy preferences and specifically enable the plugin, but not always), and then re-enter the above command using --master-enable instead.

Or if you prefer, risk keeping gatekeeper permanently disabled, like me.

[Tj Shredder]

You can also temporarily disable Gatekeeper in Catalina by typing this into Terminal

Code: Select all

sudo spctl --master-disable

Then install the plugin and run it (you may need to go into Security and Privacy preferences and specifically enable the plugin, but not always), and then re-enter the above command using --master-enable instead.

Or if you prefer, risk keeping gatekeeper permanently disabled, like me.

This is a good example why the strategy of Apple to make the system more secure fails and the result is the opposite.
Mojave is not that strict, it allows you to run non notarized software at your own risk, which is not that high if you are careful...
Security and freedom is a contradiction. I clearly prefer freedom! No risk, no fun!

[teilo]

For those having issues getting the plugins to run in Catalina (which is probably everybody), you need to remove the quarantine flag from the plugin file. This is easy to do. Unzip the plugin. Open Terminal. Change to the directory where you unzipped the plugin. Then:

Code: Select all

xattr -d com.apple.quarantine Odin2.component

or

Code: Select all

xattr -d com.apple.quarantine Odin2.vst3

Then move the plugin to the appropriate folder. /Library/Audio/Plug-Ins/Components or /Library/Audio/Plug-Ins/VST3

Wow, thanks for that! You seem to be versed in this matter:
Can I do this before I upload the VST and it will have the same effect?

No. This is something that gets applied by the operating system automatically to any newly downloaded or unzipped files. Bascially, any way the file gets onto the system, it either must be signed and notarized to avoid this, or it must be manually dequarantined.

For executables on a Mac, or for installers, dequarantining happens when you right-click the app or installer package, choose Open, and then confirm you really want to run or install unsigned software.

This has been true before Catalina, but Catalina extended code signing requirements to plugins / extensions / libraries, etc.

If plugins are installed using a .pkg installer, this is not an issue. By running the installer using the right-click, Open method, any installed plugins will not be quarantined because you gave permission for the installer itself.

However, if an installer is not used, but files are manually copied to a plugin folder, there is no GUI method for de-quarantining them, and they will refuse to run. The only way is by using the Terminal.

So, long story short: Anyone developing plugins for Mac, but not signing them, should take the time to put together a PKG installer. It's not hard to do, and will avoid end-users having to mess with Terminal.

[teilo]

You can also temporarily disable Gatekeeper in Catalina by typing this into Terminal

Code: Select all

sudo spctl --master-disable

Then install the plugin and run it (you may need to go into Security and Privacy preferences and specifically enable the plugin, but not always), and then re-enter the above command using --master-enable instead.

Or if you prefer, risk keeping gatekeeper permanently disabled, like me.

This is a good example why the strategy of Apple to make the system more secure fails and the result is the opposite.
Mojave is not that strict, it allows you to run non notarized software at your own risk, which is not that high if you are careful...
Security and freedom is a contradiction. I clearly prefer freedom! No risk, no fun!

So does Catalina. You run non-notarized software exactly the same way in Catalina as in Mojave. The only difference between Mojave and Catalina, is that the code signing system is also applied to plugins. And there is no need to disable Gatekeeper. If you are in terminal, just de-quarantine the files manually and they work just fine.

[Tj Shredder]

You can also temporarily disable Gatekeeper in Catalina by typing this into Terminal

Code: Select all

sudo spctl --master-disable

Then install the plugin and run it (you may need to go into Security and Privacy preferences and specifically enable the plugin, but not always), and then re-enter the above command using --master-enable instead.

Or if you prefer, risk keeping gatekeeper permanently disabled, like me.

This is a good example why the strategy of Apple to make the system more secure fails and the result is the opposite.
Mojave is not that strict, it allows you to run non notarized software at your own risk, which is not that high if you are careful...
Security and freedom is a contradiction. I clearly prefer freedom! No risk, no fun!

So does Catalina. You run non-notarized software exactly the same way in Catalina as in Mojave. The only difference between Mojave and Catalina, is that the code signing system is also applied to plugins. And there is no need to disable Gatekeeper. If you are in terminal, just de-quarantine the files manually and they work just fine.

The terminal is for nerds, and needs a dozen more clicks and typing. That will lead people to disable the security parts permanently for convenience. This is not necessary in Mojave!
That is what I mean the result is the opposite of security. Mojave is more save or Catalina is an installation nightmare for non-nerds and nerds alike...
The hurdles convince people to apply less secure workarounds... If Apple would do the notarization as a free service for their customers and not charge the developers (at least for free software developers) it might be worthwhile... At the moment its really complicated...

Anyway thanks for sharing the workarounds, it might be useful in the future when I can't avoid upgrading...
Lets talk Odin again...