Released: Free Synthesizer Odin 2 [Win / Mac / Linux]
- KVRAF
- 7012 posts since 19 Apr, 2002 from Utah
I’m grateful you did consider us users of HiDPI screens. 
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
- KVRist
- Topic Starter
- 306 posts since 10 Apr, 2020
Hey folks,
I just uploaded version 2.3.3 to my homepage
Highlights this time are
- support for the new CLAP plugin type
- native support for Apple M1
- much improved UI visuals when using OS display scaling
- some bug fixes which had been piling up
- switched build system to CMake
A big shout out goes to Baconpaul from team Surge / CLAP. All the name worthy features were implemented by him!
The switch to CMake is a rather big change and I didn't have a lot of time to extensively test things, but today was the deadline. So if you find any issues please let me know.
Full changelog:
- added CLAP plugin support
- added native M1 Mac support
- much improved UI appearance when using OS display scaling
- switched build system to CMake
- made WinInstaller suitable for systems not mounted on C:
- fixed symbol name clashes for "Knob" and "Filter"
- fixed issue where renaming a soundbank would select the bank above
I just uploaded version 2.3.3 to my homepage
Highlights this time are
- support for the new CLAP plugin type
- native support for Apple M1
- much improved UI visuals when using OS display scaling
- some bug fixes which had been piling up
- switched build system to CMake
A big shout out goes to Baconpaul from team Surge / CLAP. All the name worthy features were implemented by him!
The switch to CMake is a rather big change and I didn't have a lot of time to extensively test things, but today was the deadline. So if you find any issues please let me know.
Full changelog:
- added CLAP plugin support
- added native M1 Mac support
- much improved UI appearance when using OS display scaling
- switched build system to CMake
- made WinInstaller suitable for systems not mounted on C:
- fixed symbol name clashes for "Knob" and "Filter"
- fixed issue where renaming a soundbank would select the bank above
- Banned
- 3197 posts since 23 Jan, 2022
Coming out of nowhere, giving nice stuffTheWaveWarden wrote: Mon Jun 13, 2022 9:09 pm Hey folks,
I just uploaded version 2.3.3 to my homepage
Highlights this time are
- support for the new CLAP plugin type
- native support for Apple M1
- much improved UI visuals when using OS display scaling
- some bug fixes which had been piling up
- switched build system to CMake
A big shout out goes to Baconpaul from team Surge / CLAP. All the name worthy features were implemented by him!![]()
The switch to CMake is a rather big change and I didn't have a lot of time to extensively test things, but today was the deadline. So if you find any issues please let me know.
Full changelog:
- added CLAP plugin support
- added native M1 Mac support
- much improved UI appearance when using OS display scaling
- switched build system to CMake
- made WinInstaller suitable for systems not mounted on C:
- fixed symbol name clashes for "Knob" and "Filter"
- fixed issue where renaming a soundbank would select the bank above
aliasing plugin owner

-
- KVRAF
- 9520 posts since 6 Oct, 2004
Another great synth upgrades is crossplatformability
Nice to see excellent developers in cooperation with the CLAP plugin standard!
Nice to see excellent developers in cooperation with the CLAP plugin standard!
- KVRAF
- 1889 posts since 14 Jul, 2018
unfortunately the AU does not validate in logicX 10.5.1 under mojave (10.14.6)
in hostingAU it is listed, but upon loading it has a white, empty window
something new in the graphics library ? (pure speculation...)
in hostingAU it is listed, but upon loading it has a white, empty window
something new in the graphics library ? (pure speculation...)
- KVRAF
- 1889 posts since 14 Jul, 2018
here's the validation error report by logic
Code: Select all
validating Audio Unit Odin2 by TheWaveWarden:
AU Validation Tool
Version: 1.6.1a1
Copyright 2003-2013, Apple Inc. All Rights Reserved.
Specify -h (-help) for command options
--------------------------------------------------
VALIDATING AUDIO UNIT: 'aumu' - 'ODIN' - 'WAWA'
--------------------------------------------------
Manufacturer String: TheWaveWarden
AudioUnit Name: Odin2
Component Version: 2.3.3 (0x20303)
* * PASS
--------------------------------------------------
TESTING OPEN TIMES:
COLD:
FATAL ERROR: OpenAComponent: result: -1,0xFFFFFFFF
validation result: couldn’t be opened
- KVRist
- Topic Starter
- 306 posts since 10 Apr, 2020
Hm that doesn't sound good. I'll have to find a Mac somewhere..muki wrote: Tue Jun 14, 2022 5:14 pm unfortunately the AU does not validate in logicX 10.5.1 under mojave (10.14.6)
in hostingAU it is listed, but upon loading it has a white, empty window
something new in the graphics library ? (pure speculation...)
-
- KVRist
- 177 posts since 10 Mar, 2004 from Helsinki, Finland
I installed the CLAP plugin just out of pure interest (even if I have no way to actually test it before we get support in REAPER). The CLAP plugin installed itself into C:\Program Files\Common Files\CLAP with no way to customise it. Is this actually a recommended location, as in, does the CLAP plugin expect to find itself there? Or can I just put it wherever I like, like I've done with my VST plugins; apart from VST3, my VST plugins have lived under C:\Audio\VST literally since the last millennium. I'd really like to have a C:\Audio\CLAP dir for any future plugins 
- KVRAF
- 6529 posts since 9 Dec, 2008 from Berlin
Yes, that is the common directory for Clap plugins. I would recommend using it, since it's actually a standard, like VST3 in the same Common Files location and very different from VST2 where every developer used a different folder...
You can in theory move the plugins out of there after install, but other than "being used" to some location (I have my own VST2 folder location as well) it doesn't make much sense to do so.
The latest Bitwig 4.3 Beta now officially supports Clap and Odin2 works already splendidly.
Tomorrow is the "official" Clap release, so there will be more info then.
Cheers,
Tom
You can in theory move the plugins out of there after install, but other than "being used" to some location (I have my own VST2 folder location as well) it doesn't make much sense to do so.
The latest Bitwig 4.3 Beta now officially supports Clap and Odin2 works already splendidly.
Tomorrow is the "official" Clap release, so there will be more info then.
Cheers,
Tom
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube
UrbanFlow.art · Instagram · YouTube
- KVRist
- Topic Starter
- 306 posts since 10 Apr, 2020
Ok, we've figured out what the problem is. An update will be available later today. Everyone with MacOS 10.15 or later is on the safe side. Everybody else should waitmuki wrote: Tue Jun 14, 2022 5:14 pm unfortunately the AU does not validate in logicX 10.5.1 under mojave (10.14.6)
in hostingAU it is listed, but upon loading it has a white, empty window
something new in the graphics library ? (pure speculation...)
-
- KVRist
- 80 posts since 10 Mar, 2014
Mmm, for me, in Bitwig beta 6 Odin II clap version generates error:
com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Error establishing metadata connection for command "C:\Program Files\Bitwig Studio\4.3 Beta 5\bin\BitwigPluginHost-X64-SSE41.exe" metadata 1234 5 2
exit code:1
stdout:
PluginHost: Connecting to metadata service with id 5 on port 1234 using id 2
Interesting, as I uninstalled Bitwig beta 5 before I installed Odin II. Probably a minor thing, but for now, not working for me.
com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Error establishing metadata connection for command "C:\Program Files\Bitwig Studio\4.3 Beta 5\bin\BitwigPluginHost-X64-SSE41.exe" metadata 1234 5 2
exit code:1
stdout:
PluginHost: Connecting to metadata service with id 5 on port 1234 using id 2
Interesting, as I uninstalled Bitwig beta 5 before I installed Odin II. Probably a minor thing, but for now, not working for me.
- KVRAF
- 6529 posts since 9 Dec, 2008 from Berlin
Works fine here, Windows 10, Bitwig Studio 4.3 Beta 6
The error you see looks weird - are you sure you haven't somehow messed with locations on installation or are still using an old link?
You could try to delete all cache files and index files (not the other stuff!) in
C:\Users\YourUserName\AppData\Local\Bitwig Studio
Cheers,
Tom
The error you see looks weird - are you sure you haven't somehow messed with locations on installation or are still using an old link?
You could try to delete all cache files and index files (not the other stuff!) in
C:\Users\YourUserName\AppData\Local\Bitwig Studio
Cheers,
Tom
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube
UrbanFlow.art · Instagram · YouTube
- KVRAF
- 1889 posts since 14 Jul, 2018
TheWaveWarden wrote: Tue Jun 14, 2022 6:30 pm Ok, we've figured out what the problem is. An update will be available later today.
thank you!
- KVRAF
- 19775 posts since 16 Sep, 2001 from Las Vegas,USA
Odd that a new plugin format designed to free both developers and users from forced Standards would dictate an install location.ThomasHelzle wrote: Tue Jun 14, 2022 5:49 pm Yes, that is the common directory for Clap plugins. I would recommend using it, since it's actually a standard, like VST3 in the same Common Files location and very different from VST2 where every developer used a different folder...
It's true developers tend to use different default locations in their installers like Steinberg or Program Files/ VST and good installers read the registry entry, but with VST2 plugins we can create a custom folder and if the installer doesn't read the registry entry we can manually install to our custom location.
On this system my VST plugins reside on the D: drive so if CLAP forces install to the C: drive that is not a step forward.
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
