My new plugin/app, Rhapsody, is finally released into the wild!

https://librewave.com/rhapsody/

https://youtu.be/F_uNx2GlZZU

I'm currently building an app which I hope will allow batch exporting of HISE projects, auto notarization on Mac, and auto-generating installers. So far I have the basics working on GNUx. I need to finish the interface and add the batch handling, but that shouldn't be too difficult, then I'll tackle the other platforms.

This app should make it much easier for everyone (and especially beginners) to export their projects from HISE and build installers.

This is what it looks like so far (it's an ugly work in progress).

https://youtu.be/7i1vdOz3PSI?si=ZdTWoSeg_gNx4EFY

The AudioDevSchool site that I've been putting together for the last few months is finally ready!

For the initial launch I'm starting with a single course that I'm calling The HISE Bootcamp.

The course is 100% free and is designed for beginners, although there's probably stuff in there that more experienced users will also find useful.

The videos walk you through the process of building two simple plugins with HISE (a sample library and a scriptnode effect). We then move on to building HISE from source and compiling our projects.

Along the way we'll cover a bunch of subjects from basic things like finding your way around the HISE UI to more advanced concepts like Ad-Hoc codesigning for testing your plugins on MacOS.

Here's the link to the course: HISE Bootcamp.

Feel free to share it with anyone you think would find it useful.

Please let me know if you run into any issues with the website or any of the course material - there's usually something that goes wrong on launch day!

@MikeB

Dave, 34, UK, doer of many things.

It's becoming hard to find VS2017, I can no longer see the community edition at Microsoft's website, only a pro version trial.

@Christoph-Hart Is it possible to bring HISE into the new decade and add a VS 2022 export option?

I know we can already use VS 2022 with a bit of fiddling around, but it's not straightforward and requires additional steps for every export.

It's starting to look a little nicer now.

Just wanted to share something I'm working on. It was briefly discussed last month here.

It's a grid based layout system, inspired by html and other layout languages. The idea is you define your components once in a JSON type format, pass it to the layout engine, and it will do the rest. It can layout components in a vertical or horizontal stack, or use a flexible grid.

If no dimensions are passed components will stretch to fill the available space. Dimensions can be passed either as numbers or percentages relative to the parent/column/row.

By default components are centred horizontally and vertically within each grid cell but you can specify their alignment (top/bottom/left/right). For stacks components butt against each other, I have plans to add some alignment options here as well though as well as margins/gutters.

If you want to add multiple controls you can define one control and specify a number of clones, and they will be created and positioned automatically.

I think it will make it easier for me to transfer layouts between projects as well as quickly build complex projects. I have a lot more functionality planned.

With HISE reaching its 10th birthday recently I thought it was a good time to look at some of the commercial plugins that have been built with it.

I've put together a little blog post and video featuring some of the plugins that have stood out to me. See if you recognise any of them.

https://audiodevschool.com/a-showcase-of-hise-plugins/

A couple of years ago I proposed making a general purpose downloader/installer app. In the time since I've created a downloader/installer for my own libraries and it works really well. I thought I'd see about adapting it to be an option for more developers.

I'm currently prototyping some things but before I get too deep with it I want to know if any of you would actually use it.

Unlike other similar apps (Pulse, Conduct, etc) what I'm creating is decentralized. Your customers will log into the app using the account they have on your website and downloads will be served from your servers. The app will of course be free software.

The app is more limited in scope than those other options. I don't intend to include an integrated shop and I don't plan support for non-HISE formats - but who knows what the future will bring.

The benefits for you is it's very cheap (you don't need to pay a middle-man), you don't have to develop your own downloader, new customers will discover your products when exploring other plugins available through the app, it's HISE focused and will support expansions and additional presets, etc..

The app supports serial keys to limit access to downloads. It does not (and cannot) provide any DRM but you can include this in your plugins if you wish.

It can integrate with any website, you just need to setup some endpoints and make sure they return the correct data. If you're using a Wordpress/WooCommerce site I can (for a fee) supply you with a Wordpress plugin that will integrate seamlessly with the app - this is the plugin I'm using on my own site.

So is this something any of you would use? If so I'll continue developing, if not then I won't bother, I don't want to be the only one using it :)

Here's a preview of where I'm at with it.

https://youtu.be/SeetYsUX9YQ

@DJJD12345 said in xcpretty Not Detected After Install on macOS Tahoe M1: Compiling Fails in HISE Export:

fatal: not a git repository (or any of the parent directories): .git

That means you didn't use git clone to download the source code.

Start over, remove all copies of HISE and the HISE source code from your system. Then make a video showing me the full process you are following.

@Orvillain said in Invalid use of incomplete type vSIMDType:

I think this is a Linux compiler thing.

Linux user here

@NISHI_MUSIC Post the network so we can try it

@Dominik-Mayer Can you change it to "David Healey"?

@Dan-Korneff said in Linux vs ThirdParty Nodes:

@d-healey Exported plugins store their data (presets, documentation, etc.. ) in .config within the Company subfolder. Just like the structure on MacOS and Win. I just don't understand why it would be different for Linux.

Yep that's true. It's just HISE itself that stores it in the home folder. According to the Filesystem Hierarchy Standard dumping them in the home folder is acceptable.

However the XDG Base Directory Spec recommends a .config folder.

It's a mess. I'd prefer it to all be in .config too. Maybe we can put it to a vote.

@bendurso I'm stumped then... You could use cURL directly from in HISE by calling it as a process - @aaronventure posted about this a while back I think.

@bendurso Does it work in a private browser session?

@Dan-Korneff said in Linux vs ThirdParty Nodes:

Is there any reason that HISE creates an additional folder .hise in the first place?

This is the correct folder. The one in .config is not used (and was never created on my system). Some programs store their settings in .config, others (like HISE) just dumb them in the home folder.

However one thing I've just noticed is if you use the snippet browser, this does create a "HISE" folder in .config

@Christoph-Hart Might want to check that.

@bendurso said in Server.downloadFile with signed Amazon S3 URL:

The link contains 1359 characters. Maybe that could be the issue? Is there max limit for the link length?

Could be, I'm not sure. I believe HISE is using cURL to do the download so you can test that by running it manually in a terminal.

@ustk Confirmed

@Dominik-Mayer Usernames with . in them don't work as links when using the @ feature.

@d.healey for example