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

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS Odin 2

Post

TheWaveWarden wrote: Sun Dec 11, 2022 4:20 pm
audiojunkie wrote: Sun Dec 11, 2022 3:22 pm No Linux support? 😢 Will Filter Force or your new “Odin 3” synth support Linux?
Yeah this bugged me quite a lot (I'm on linux myself). I hit a roadblock with OpenGL during development, which I couldn't solve at the time hence only macOS and Windows for Filter Force. That being said I found a workaround earlier this week, so the upcoming synth will (in all likelyhood) have a linux version :tu: I'm not sure if the fix will be applied back into Filter Force as well. Only if I have spare time on my hands :)
Thank you for the response! I look forward to your new synthesizer! Will it be Open Source as well?
:)
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.:mad:
(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.) :roll:
Top

Post

Tj Shredder wrote: Mon Dec 12, 2022 6:07 am It probably does not communicate the preset name (and only the name) to the host. It must not recall that preset, as you might have tweaked it without saving it…
This is within the same session. Just closing the Odin plugin GUI and reopening it resets the Odin preset browser to no preset selected, even though the same one is still loaded and playing in the synth.
Windows 10 and too many plugins
Top

Post

Paul Eye wrote: Tue Jun 14, 2022 8:20 pm If the plugin's functionality isn't dependent on it being in some hardcoded path, then at least give us an option. Most users probably will install in a default/standard location, and that's fine. Let the rest of us (control freaks) install the plugins wherever we please. Best of both worlds, and everyone's happy :D
Currently my C: drive has only 4GB free space. In all my computers it gets full pretty quickly, I need to be able to install in custom location.
Now the installer also doesn't let me choose VST location, although I have previous version in custom location.
New Surge version has also fixed installation locations for both CLAP and VST.
It would be really nice to be able to choose.
Top

Post

Pweg wrote: Wed Dec 14, 2022 1:01 pm
Paul Eye wrote: Tue Jun 14, 2022 8:20 pm If the plugin's functionality isn't dependent on it being in some hardcoded path, then at least give us an option. Most users probably will install in a default/standard location, and that's fine. Let the rest of us (control freaks) install the plugins wherever we please. Best of both worlds, and everyone's happy :D
Currently my C: drive has only 4GB free space. In all my computers it gets full pretty quickly, I need to be able to install in custom location.
Now the installer also doesn't let me choose VST location, although I have previous version in custom location.
New Surge version has also fixed installation locations for both CLAP and VST.
It would be really nice to be able to choose.
I agree with the need for being able to choose paths, but for a completely different reason:

Currently (and probably always), DAWs using Flatpak packaging can only see plugins not using Flatpak if they are located in, and their library files are accessible from the Home directory.

Odin2, being open source, may already be packaged as a flatpak, but many aren’t. It would be nice for plugins that are not flatpak packaged to have an option to install to a Flatpak supported location such as in the Home directory under .VST, .VST3, .CLAP, .LV2, etc. subfolders.
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.:mad:
(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.) :roll:
Top

Post

You can always create symbolic link from another drive to the system location of VST3 or CLAP and it will all work. And then you don't need to worry at all about installer allowing or not allowing custom paths for installation...
Top

Post

EvilDragon wrote: Wed Dec 14, 2022 5:25 pm You can always create symbolic link from another drive to the system location of VST3 or CLAP and it will all work. And then you don't need to worry at all about installer allowing or not allowing custom paths for installation...
The only problem with that is that some installers will crash when attempting to write to a location that is on the other side of a symbolic link or junction, and debugging such installers when they seemingly don't work for 'some random reason' is beyond most users.
Top

Post

EvilDragon wrote: Wed Dec 14, 2022 5:25 pm You can always create symbolic link from another drive to the system location of VST3 or CLAP and it will all work. And then you don't need to worry at all about installer allowing or not allowing custom paths for installation...
I would have thought so too. But I saw a developer discussion where it was said that that doesn’t work in this case. I don’t remember what the detail was that made it not work though. ☹️
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.:mad:
(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.) :roll:
Top

Post

NikkiA wrote: Wed Dec 14, 2022 8:06 pm
EvilDragon wrote: Wed Dec 14, 2022 5:25 pm You can always create symbolic link from another drive to the system location of VST3 or CLAP and it will all work. And then you don't need to worry at all about installer allowing or not allowing custom paths for installation...
The only problem with that is that some installers will crash when attempting to write to a location that is on the other side of a symbolic link or junction, and debugging such installers when they seemingly don't work for 'some random reason' is beyond most users.
Good point!
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.:mad:
(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.) :roll:
Top

Post

I've never had that happen and I have like 400+ plugins installed...

Not saying it can't happen, but a good installer tech will have means of resolving symlink paths... Inno, NSIS, InstallShield all seem to do just fine from my experience.
Top

Post

Symlinks are solid here on Windows 10. For example, that's the only way to use multiple scan paths for plugins in Ableton Live.

https://www.howtogeek.com/howto/16226/c ... -or-linux/
Windows 10 and too many plugins
Top

Post

EvilDragon wrote: Wed Dec 14, 2022 9:18 pm I've never had that happen and I have like 400+ plugins installed...

Not saying it can't happen, but a good installer tech will have means of resolving symlink paths... Inno, NSIS, InstallShield all seem to do just fine from my experience.
But are you using Flatpak for your DAW? Flatpak is a sandboxing package manager on Linux that only allows specific things to be seen by the packed DAW in certain ways. I believe that’s where the difficulty lies.
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.:mad:
(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.) :roll:
Top

Post

No I'm on Windows. :P
Top

Post

You are always welcome to join us 😊
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.:mad:
(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.) :roll:
Top

Post

I prefer my symlinks always working, haha. :D
Top

Post

:D
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.:mad:
(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.) :roll:
Top
Post Reply

Return to “Instruments”