Thoughts on Moonbase?

[HISEnberg]

@Sifres I'm curious then does HISE support Moonbase using JUCE 6? Or do you need to update to JUCE 8? My last memory around this topic is that the JUCE 8 integration into HISE is not fully stable to date.

@David-Healey do you have any content covering Moonbase integration, the advantages it offers, known bugs, etc.?

[David Healey]

@HISEnberg You need to use JUCE8, but it's currently not working, we're waiting for Christoph to fix it. Once it's fixed I've made a PR that makes integrating Moonbase into a HISE project really easy. The PR needs a bit more testing but I'm waiting for the JUCE8 fix first.

I'll be making a video showing how to integrate it once the fix is in place.

[Christoph Hart]

@David-Healey I met with Tobias last week and we discussed improving the integration with Moonbase. I'll be working on a "native" module that integrates with HISE nicely without having to go to JUCE8, but I'm currently swamped with other stuff to do.

[David Healey]

@Christoph-Hart Oh even better

[HISEnberg]

@Christoph-Hart @David-Healey niiiceee thank you for the updates. I'm looking to offer my clients a more consistent solution and Moonbase seems like the cleanest alternative. Glad to hear it is in the works

[dannytaurus]

@David-Healey @Christoph-Hart Is all the talk about JUCE8 and the Moonbase HISE integration related only to licensing?

I don't need to integrate Moonbase into HISE if I'm not using license, right?

[David Healey]

@dannytaurus Yes it only affects the integrated licensing - I'm not using it either.

[Sifres]

@HISEnberg So Moonbase JUCE module requires JUCE8 indeed. Hise isnt stable when being compiled, or when compiling plugins, on JUCE8. So yeah its not working atm. Christoph noted that this is because he did some funky stuff for the MCP integration.

BUT you can work around that by compiling hise on JUCE6, then exporting a plugin. It will fail but it will create a .jucer file and you can pick that up with JUCE8. At least thats my workflow. You could probably script the whole thing. It requires some other steps as well as modifying some Hise source.

TBH if you dont need it right now (as stated, for me it was a neccesary step) I would simply wait for Christoph to integrate it.

@Christoph-Hart great! I feel like it could really benefit the eco system surrounding Hise.

[David Healey]

I've just published a blog about my progress with Moonbase, this is based on a Patreon post from a few weeks back:

https://audiodevschool.com/moonbase-adventure/

[dannytaurus]

I had a great meeting with Tobias a few days ago. Sounds like Moonbase will be a good move for me.

Just signed up for an account exploring the admin interface.

[jeffd]

@dannytaurus
did they get the module running on HISE yet with JUCE 8?

actually i just read David's blog...and looks like Christoph plans to add native integration with moonbase at some point

[dannytaurus]

@jeffd I'm not using licensing so I don't need the module. We didn't talk about it in our meeting.

[jeffd]

@dannytaurus gotcha.

[David Healey]

@jeffd said in Thoughts on Moonbase?:

did they get the module running on HISE yet with JUCE 8?

You can use it already with HISE but you'll need to workaround the HISE juce8 branch not working properly and spend some time in C++ to integrate the Moonbase module - it's not too complicated and AI might be able to help you. I also made a PR to HISE (before Christoph announced his native module) which might provide some guidance.

[jeffd]

@David-Healey cool cool
I did make just a licensing system with traditional serial keys...so Ill probably just use that for now, and then update.
and I finally actually fininshed making this instrument

now just working on some vids and demos and final testing. but ill include some screenshots here.
Its just a sample based synth, where i sampled the f-k out of a LYRA 8 synthesizer..
recorded through some amps and speaker cab impulse responses etc.