Moonbase
-
@Christoph-Hart the biggest challenge in getting it JUCE v6 compatible is definitely machine IDs. When we were still using the native JUCE v6 utilities to fingerprint devices, we ran into quite some issues as our customer base grew, with collisions between very similar devices and some times changing fingerprints.
This is particularly a problem since you cannot easily change the way you do fingerprinting in one version of a plugin to the next, since you practically invalidate all license tokens and trials.
What could possibly be done here however, is to backport the more modern fingerprinting into your customized JUCE version, do you think that would be an option?Outside of fingerprinting, we are relying on some newer threading constructs, but I don't expect them to be a significant problem. If you'd like to have a look at the source of the module, feel free to create an account on our website, so you can have a look at our TOS, and sign it, after which I can grant you access to the module. We can also sponsor some work here if you're up for it!
Founded Moonbase.sh for licensing and payments with a JUCE module ready to go
-
@tobbentm I've already backported the changes of the machine IDs to be more reliable, which you can enable with
JUCE_USE_BETTER_MACHINE_IDSwhen exporting a plugin. Not sure if it is the JUCE 7 code, but I also ran into the problem of machine IDs changing between minor Windows updates. -
@Christoph-Hart said in Moonbase:
machine IDs changing between minor Windows updates
this was very annoying
-
@Christoph-Hart I think there's been an update since then. I've had to integrate from JUCE 7 to fix.
-
@Christoph-Hart said in Moonbase:
JUCE_USE_BETTER_MACHINE_IDS
https://github.com/juce-framework/JUCE/commit/120f9266dc881c81371109c69b37a0a246accdeb
Here's the fix
-
@Christoph-Hart cool! I've scheduled some time with our JUCE freelancer to make it JUCE6 compatible, using the APIs available there for machine IDs. We'll also implement an option to pass your own function for fingerprinting, so it's easy to plug in whatever else you may create, if you don't patch JUCE itself. Is there anything else we can do in the same go to make it more HISE-friendly? Let me know!
Founded Moonbase.sh for licensing and payments with a JUCE module ready to go
-
oooh I'd love to implement moonbase into my HISE projects. I have friends who talk highly of the service!
-
@tobbentm Sounds good. One question: once the user completes the browser activation, can the user token be saved and used to download their products (licenses)?
-
@tobbentm This looks like excellent work and sounds very promising. Please keep us updated when you integrate JUCE 6 compatibility. Would really love to see a HISE-example integrating Moonbase as well for us here to test out when it's ready :)
-
@tobbentm Now that HISE works with JUCE 6 and 8, this might be relevant. It’s not something I’m interested in right now, but maybe others will be :)
-
@bendurso Yeah, I saw some threads about JUCE 8 in HISE!
Is it fully supported already?
Caught me a bit by surprise, thought the JUCE license would prohibit that, but happy to see this.I know we've had a number of HISE users create accounts lately, but I'm not sure who is live yet.
-
@tobbentm so if we build hise with juce 8, we can use the moonbase module for activations?
-
@jeffd Our JUCE module is compatible with JUCE 8 out-of-the-box, so while I don't know the exact steps necessary to include it in a HISE project, in principle it should work, yes!
-
I bet if i try it it will probably break my project lol. no idea about any of this honestly.
I was assuming HISE only worked with juce6.
"The JUCE code is now handled as a git submodule so you can switch versions." --anyone know if that is an accurate statement?
-
@jeffd yup recompiled HISE yesterday without any issues so far. The setup is a bit different now however
-
do you have to change something here:
git clone --branch develop --recurse-submodules https://github.com/christophhart/HISE.git
how do i point to juce 8?
or this more complicated than that perhaps?
-
@jeffd The JUCE submodule is its own git repo with 2 branches juce6 and juce8. Go into that folder and checkout juce8
I think you'll also need a JUCE8 licence, not sure.
-
@David-Healey im on an old build before christoph switched to the submodules.
so im not sure if i should do that first ?
-
@jeffd Definitely. You can't use JUCE 8 without the submodule update.
-
@dannytaurus so i got hise to build with juce 8, but ive missed a step i think. when trying to export a plugin and build an audio unit i get this error:
Desktop/HISE/JUCE/modules/juce_core/system/juce_TargetPlatform.h:177:8: "Building for OSX 10.10 and earlier is no longer supported!"
177 | #error "Building for OSX 10.10 and earlier is no longer supported!"im looking in the projucer and it says it set for macos deployment target of 11.0
anyone run into this error?
what is Building for OSX 10.10 coming from?
