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

Have you checked the develop branch? I migrated to JUCE 6 there so maybe this fix is already included? If not it would be good to migrate as it might be easier to merge it to JUCE 6 than to the old one from master.

@Natan I just checked and that click comes from the fact that the macro modulation is not sample accurate and never will be - it was never intended to be a "real" modulation system that replaces the actual modulators in HISE but just a quick and dirty way to add some movement to controls.

You can think of it this way: if the sound that you want to make could be achieved by you manually moving the control with the mouse, then the macro modulation is a good approach (eg. slow pad movements or randomized jitters). If you rely on your modulation to be exact and fast, use the inbuilt HISE modulators.

I just checked and it behaves just as expected. The reverb of a hard panned signal is still going to be spread over the entire stereo field - that's just how diffusion works - there might be reverbs which under / overemphasize this effect, but this is not a bug.

And the signal is not MONO - slap a gonio meter on channel 3+4 to see the stereo field.

@Lindon Lol yes this one escalated quickly...

I think y'all can stop posting feature requests for now - there's enough on that list to keep me busy for a while.

The only exception to that would be bugs that slipped in between master to develop as these are the most critical ones at this moment, so if you see them, please keep posting.

A reverb effect will always create a stereo signal from a mono signal so not sure if this is a bug or a feature.

Ah yes good idea.

Try

if(virtualMidiPort = MidiInput::createNewDevice(portName, callback).release())

You can also do so with Ctrl + Scrollwheel. And the zoom centers around the mouse position which took me 8 hours to implement, I'm not kidding...

Yes, that's right, it doesn't matter which architecture, I just hacked something together to make it build on my Macbook M1.

Yeah, I changed that. The mouse wheel scroll is now deactivated when you deactivate the edit mode (the thing with the grid). This should fix almost all weird issues and now you can enjoy the seamless mouse-wheel zoom at the mouse position...