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).

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.

@MikeB

Dave, 34, UK, doer of many things.

It's starting to look a little nicer now.

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.

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.

https://youtu.be/SeetYsUX9YQ

I've made a few additions to the preset browser which some of you might find useful. These are available in my fork and I've also opened a pull request for Christoph to merge them into the main source. Nothing I've done should break anything although I've made the favourite icon in the preset column take the text colour instead of the highlight colour which may be important to you. Really I'd like this to take the itemColour2 property but haven't figured out how to do it yet.

Added Data properties to:

• Show/hide the Add, Rename, Delete buttons
• Change the bounds (x, y, w, h) of the search bar
• Add vertical padding to the rows of each column. Fav icon in preset column is not affected.
• Apply vertical offset to y position of edit buttons, so you can move them up. The list box is adjusted accordingly.
• Apply offset to bounds (x, y, w, h) of the list boxes, so you can make them shorter, longer, fatter, thinner, etc.

Also

• Fixed a bug where selecting or deselecting an item in the expansion column didn't clear the other columns correctly.
• Use column area instead of list area for painting the column background - this might have the effect of visually shifting the edit buttons down slightly (they are actually in the same place but will look lower) you can counteract this with the edit button vertical offset property I added.

Status update:

GNU/Linux: Fully working (standalone, vst2, installer). x64 only
Windows: Fully working (standalone, vst2, vst3, installer). x86/x64
MacOS: Fully working (standalone, vst2, vst3, au, codesigning). Needs a bit of tuning but almost there (installer). x64 only.

When I say fully working, that's in my own tests, I expect many a bug report when I release it into the wild.

It's quite possible that AAX plugins will compile just fine on Windows and MacOS too, I've implemented it in the app but haven't tested it.

If all goes well I should finish up the tuning of the MacOS build tomorrow and it will be ready for my patrons to test this weekend!

@Christoph-Hart Could you merge my juce_template pull request (if all is well) as the mods there are needed for my app. The mods are also useful for regular exporting from HISE, bigobj is enabled by default and the VST3 SDK is set correctly to the one that is in the JUCE folder.

@EwanBristow yes

@EwanBristow and you definitely built HISE from the one remaining copy of the source that you have?

@EwanBristow said in VST3 Export -:

i removed any trace of my other juce installation

How many copies of the HISE source do you have?

@EwanBristow said in VST3 Export -:

have a funky feeling that manually re-installing the directory might help? No idea

Shouldn't be necessary to ever mess with those files.

@EwanBristow Did you clean the build folder after compiling the vst2 and before compiling the vst3? Are you using the version of JUCE/Projucer that comes with the HISE source code?

@EwanBristow Can you show me the content of your tools/sdk folder?

This is how mine looks:

@EwanBristow

Why do you want to compile HISE as a plugin?

What error message do you see?

What operating system are you using?

@pede

1. When you create the monoliths HISE will automatically split them based on the size you select.

2. I think most of what you need is in the docs - https://docs.hise.audio/working-with-hise/project-management/expansions/index.html#features

@VirtualVirgin said in saveInPreset not working for panel data?:

Do you have cases where you need to store panel data in presets?

I don't think I have. If I have a bunch of data to store that isn't directly tied to a component I use a slider pack. For example for my AHDSR I have one set of knobs to control the different parameters, but each articulation in my instrument gets its own set of values. So I use a sliderpack to store the AHDSR values for each articulation and when the user switches articulation I just pull the values from the sliderpack and apply them to the knobs.

Do you have a link to that bit of documentation that you've posted?

@aaronventure Not sure what you mean exactly. In this case there is no child processor beyond this script. I'm only working with artificial notes, so ignoring the message shouldn't make a difference - in fact if you remove the ignoreEvent line the issue still occurs.

The line that checks if the event ID is artificial (which is must be because it is only ever populated from a call to Synth.playNote) seems to be returning the wrong response.

@VirtualVirgin You could do it like this which might make it seem like it makes more sense

const panelObj = Panel1.getValue();

Console.print(panelObj.test1);