I just entered the wagon a couple of weeks back. I am trying to make a project future proof, i.e. decoupling from the bespoke projucer and use hi_streaming as explained in streaming_example.
To do so I am updating the
hi_streamingto compile with JUCE 6.x (removing ScopedPointer and the warnings).
- is the streaming_example still supposed to work?
- Did somebody else work on that, so maybe there is a branch lying somewhere so I could save the trouble?
Thanks and happy coding
So I spent the night updating the said modules, here is the PR:
Sadly the AppVeyor CI fails already for a while, I would have been curious if windows builds as well.
The streaming_example needs a few modifications as well (e.g.
runThread()). I'll push a PR when I tidied it up a bit.
The createMemoryMappedReader I left out, since that might require changes in the rest of HISE ass well, but updating all of HISE to juce6 is a bit big task, especially as I am only interested in the sampler.
Let me know if that works for you or what I should change/improve. Would love to see that merged.
how is the status with the bundled JUCE sources?
You decided 6 years ago to use your own JUCE version ("because JUCE is too buggy").
Some time has passed and I think the JUCE API has greatly improved.
Do you consider moving back to a vanilla JUCE?
What are the major pain points not to do so?
I am tasked with updating a client project which involves a lot of C++ code around HISE, and I would like to remove as many dependencies as possible.
Thanks in advance
Christoph Hart last edited by
I‘m on vacation this week so I‘ll reply to all of your requests thoroughly next week.
I don‘t remember saying JUCE is buggy (or maybe it was taken out of context). It’s by far the best codebase I’ve seen - and that includes HISE There are a few things that I‘ve added to JUCE which are not very likely to make it in the official codebase so I never bothered them with pull requests (the VariantBuffer class might be the most intrusive change which adds a native float array to the var container) plus I added a few getter / setter methods whenever I needed to tweak a few internals (eg the code document class)
The develop branch is on JUCE 6 since April, so you might want to check out this branch if you want to use the latest JUCE. Let me know if you have issues migrating to the latest HISE branch.
Great, thank you for the answers and sorry for interrupting your vacation.
Sorry for teasing, the comment is from a commit (see .gitmodules )
I'll have a closer look at the develop branch. My questions stem from the fact that I never used the full features of HISE, and actually the clients codebase doesn't either, even though it is based on an old export.
Maybe I will know more details next week when you are back.
Cheers and enjoy the rest of your vacation