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:

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

Do you need to distinguish between point add / remove / drag or do you just want to update stuff whenever something changed?

@Tania-Ghosh said in Write User Name on Plugins Registration/Authorization:

Engine.dumpAsJSON(data,"../userInfo.js");

This method is deprecated and it's recommended to use the File API for this (you also get optional encryption for sensitive user data).

@d-healey said in New Layout Bugs (not feature requests):

and that's not the correct way to solve it anyway

That's exactly the correct way to solve it

@d-healey said in New Layout Bugs (not feature requests):

You can use the browse button, however it appears to be a file browser rather than a directory browser.

Yes, this was a typo and is fixed now, along with the table crashes.

Oh and one last tiny thing:

AUTOTUNE!

ycdiws (you can do it with scriptnode)

plugin export should work now, tables and waveforms can be customized (still need to update the docs though).

Yes probably something wrong with the send / receive codegen (from the error it mixes up frame and block processing). I‘ll take a look later.

However I think we are both idiots, because if you use a scripted look and feel it will ignore this property.

HISE. From professionals for professionals.

You need to enable the useCustomColours property (or whatever it's called, the one below tableIndex.

@LinuxVst Yes, I'm working on that file at the moment, so I couldn't push the fix, you'll have to wait a few more minutes...