-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pedalboard Store #54
Comments
it is planned but needs a whole bunch of other things to happen first before that can be enabled |
Those other things that need to happen - are they business things or tech things? Because if they're business things, then opening up the store to more potential customers (with paid plugins) could be a great business move ;) |
the business side is sorta easy, the technical stuff is the complicated part. in rough steps:
|
Ah ok. Yeah that is a lot. Thanks for the quick response though! |
Is there any potential for a low-hanging-fruit where you bring over the working Linux implementation from the Dwarf etc to just the Linux release of mod-desktop? I'm aware that doesn't work with your points 2 (and maybe 5?), but all I'm (naively) thinking is: if it works on your own MOD hardware, and that runs a version of Linux, is it not easier to port that to a normal desktop Linux installation than it would be to Windows or Mac? Sorry if this is a stupid question! I'm an Android developer, musician and daily Linux user, and I'm not too familiar with systems programming. |
For sure it would be quite more doable to just do a Linux store thing first. |
Hello, for point 1: why not reading HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\MachineGuid ? Is this implementation good enough? Reference: https://stackoverflow.com/questions/99880/generating-a-unique-machine-id |
I noticed the Pedalboard store is missing from mod-desktop. I tried just navigating the site and clicking Try Now on a pedalboard, but it fails to connect. Are community pedalboards not intended to work with mod-desktop?
The text was updated successfully, but these errors were encountered: