PresetBrowser

SettingsWindows

Hi everybody,

this thread is the next attempt of organizing bug reports & feature requests. In order to keep it clean, I would suggest a few rules:

1. Every post must be a distinctive bug report / feature request. If you want to emphasize a request / feature, upvote it or downvote it if you think it's a bad idea (but please do not downvote other stuff in order to bump your personal favorite). Any discussion about a certain bug / feature should be a dedicated thread (you can add a link to the discussion thread in the post).
2. When I find the time to implement it, I'll sort the list in my head based on the number of upvotes and feasibility. If it's implemented, I'll edit the post with a link to the commit and strike it through.
3. A feature request that is not feasible or not popular enough (number of upvotes less than ~5) will be removed after a grace period of a few days, so anything that survives this process can be considered to be implemented at some point. If you find your post to be deleted, please do not repost it.

Normally I don't to any redacting / moderating, but in this thread I try to keep it clean, so don't take it personally if I delete any post in here that violates the rules above.

Are you on Windows or mac?

This shader stuff is beyond awesome. Check out this 3D keyboard prototype:

Alright, I'm currently trying to improve the user friendliness of the export process to make it even more fun. Let's be honest, HISE will never win the "Most easiest app to use"-award, but this is ridiculous even for my low standards

So this is what I've done so far:

1. You don't need the snex_workbench anymore to compile the networks - there's a item in the Export menu in HISE that opens the same dialogue. It requires you to have at least one DSP network in your signal chain when exporting, but there's an error message that will tell you this.
2. There's a command-line option to do that process, so you can call HISE.exe compile_networks -c:Debug and it should do everything for you.
3. It will show which nodes are about to be compiled in the export dialog. After the compilation, you can query the state of the loaded DLL with Tools -> Show DSP Network DLL Info.
4. You should not rely on the workbench like @dustbro suggested anymore - if you choose "Create a network file" in the scriptnode welcome screen, it should create a file-based network that you can export as DLL (just remember to save the network using the save button before hitting the DLL export).
5. I am currently writing unit tests for scriptnode in this repository. This includes also a few test nodes that are compiled and tested against the interpreted node. All the nodes here are supposed to be compileable on macOS and Windows (at least with my setup). If you encounter a DspNetwork that throws a compilation error (or crashes on loading), please post it as issue in this repo, then I will create a test file from it and make sure that it works.

Hi everybody,

I'm not sure whether I'm the idiot or if GitHub's pull request tool has it twisted, but I ended up merging the codegen rewrite branch into the scriptnode branch (instead of the other way around).

Anyways, I took this as an opportunity to get back to a branching model that is not completely pointless, so we're back on master / develop! That means:

1. The branch formerly known as scriptnode is now the master branch. I just used the commit just before the messed up merge with codegen, so you can use this in production.
2. The branch formerly known as scriptnode-codegen-rewrite is now the develop branch.

I will add all features / bug fixes to the develop branch from now on, so unless you are working on a live project that has already been released, it's highly recommended to use the develop branch. In the foreseeable future, the develop branch will be merged into master, which is the exact time that HISE 3.0 is released.

EDIT: Also wait an hour or two before switching, the merge process has messed up the compilation...

Thanks man - it was a gigantic amount of work - writing a compiler is no joke - but I also learned much in the process...

Yes Merry Christmas everybody. It's nice to see the community grow and the increasing amount of christmas wishes each year is a good indicator - a few years ago it was just David and me

I'll be on standby mode for another few weeks (my yearly theatre production), but then we'll be full force heading towards HISE 3.0..

Actually I've added a few more advanced effects some weeks ago including box & gaussian blur. I'll update the docs for this soon.

Alright guys, more than 6 upvotes and I‘ll look into it

@d-healey Does it work with other floating tiles (eg. the keyboard)?

@ustk nope, that's even worse, you're creating a string in the button callback and it might reallocate it in each loop iteration

@ustk that works? I didn‘t knew you can use array literals as switch cases.

But if this comes in the vicinity of a realtime callback I wouldn‘t trust it not allocating so a bit fiddling might be better suited.

@d-healey Oh wow, that might be the commit with the weirdest looking fix in the history of HISE...

https://github.com/christophhart/HISE/commit/2bdd95a60d094c577dd7a0199130756c7de955c3

Like you see the code change and immediately know, "yeah, that makes total sense".

@d-healey I don't think so but if you can make a minimal example, I'll take a look (not sure if you did that already).

@ustk Do you mean this:

Yeah, that's me basically not liking #0 (there's even not a name for this abomination, #1 is first, #2 is second, but #0 does not exist) so I incremented the display value, but the actual system is zero-based like everything that is good and logical.

@d-healey it depends I actually don't have a MIDI device that produces (monophonic) aftertouch so there might be something obvious I'm missing, but the polyphonic MPE keyboard produces aftertouch.

@danh use the linkedTo property?

@ustk I stole KONTAKT's way of slapping the pitch bend and aftertouch at the end of the list, but yeah, that offset by 1 is a bit annoying, better fix it now before people actually use it

It's fixed now, it was indeed looking in the audio files folder of the expansion.