Having used all 3 fairly extensively, here are my thoughts on the 3 different pieces of software for what it's worth.

I came from both Romplur & Maize before transitioning to HISE. They are easy to use but you hit issues and/or limitations pretty quickly IMO.
Maize & Romplur are very similar to each other despite the Romplur CEO saying otherwise.

Romplur has a huge issue if you want to use real sample mapping for each individual note and will just grind your DAW to a halt if you have even a modest number of presets/banks.
Maize doesn't have that issue at all depsite being the significantly older software.
With both, you are limited to the built in effects and functionality so if you have far reaching or even moderate ambitions you will hit the ceiling fairly quickly.

They only really have 2 advantages over HISE and one was mentioned by the OP - that you can export both Windows & Mac format plugins on 1 platform, you don't need to have a Mac to export Mac plugins and so on.
The other advantage is ease of install.
Other than that, I would say HISE wins hands down in every other category.

But in fairness to HISE, once you have got your head around the HISE install/build process & how it works, it's not really an issue tbh

After making the move to HISE I would 100% never consider moving back to either of the other 2 and the more I learn with HISE, the more possibilities there are and the more powerful/flexible it becomes.

@d-healey Turns out you were kinda right and I had done something stupid.

When I changed the preset browser from 3 to 2 columns I just left the default widths as 3 x 0.33333
It didn't seem to matter as it worked fine in HISE but in a built plugin it was doing what I described in my OP.

After your suggestion I flicked it back to 3 columns, re-exported and sure enough the factory presets weren't editable & the add buttons were there as they should be.

I then changed it back to 2 columns but set the widths to 2 x 0.5 and when I re-exported it this time it was also working correctly.

Glad I have that sorted as it was really bugging me. Thanks for the assist

@d-healey ah ok strange.

Thankyou for your help as I now have it working properly and selecting the correct samplemaps.

I've also got the expansion load working in daw as well so I can progress with my project which is great news.

Thanks again, your help is always invaluable

@d-healey Ok thankyou. I have created a minimal project and sent it to you via DM

@d-healey Thankyou, as usual your help was invaluable.
Ironically I have been using autocomplete quite a bit recently but it didn't even occur to me in this case.

Thanks again, it is doing what I want it to do now

@Lindon @d-healey

Thankyou both. I tried both methods and have come up with something that works.

I need to do a little rejigging of the samples once to get it working 100%.
That is a one time job and after that I can add new samplemaps without messing up my presets and having to manually reassign the samplemaps which is exactly what I wanted.

Thanks again, your help is much appreciated

@gorangrooves said in FL Studio midi problem:

@gorangrooves Found it. For anyone else looking, it is in:

top menu Options-> Audio Settings-> CPU-> Align Tick Lengths

Apologies I've only just seen this. Glad you found the setting though

@d-healey I forgot to say earlier but this worked like a charm. Thankyou for your help as it would have taken me forever to figure that out (if ever)

@DabDab yes that the code I used to get it working in he first place but it didn't translate across when I made firther changes in daw.

@Christoph-Hart said that it should though so I'll double check something else isn't stopping it

@bendurso said in Fader/mixer between multiple samplers:

@rzrsharpeprod I was thinking in making the same a few days ago.

This is how I managed it to do it:

HiseSnippet 1456.3oc6Z80aSbDDeuXu.wkhfHdsRmxSlVHx1DfJUghIN+QtzjXEGnz9Br4t0wqxc6d5t8BXP7VeuR8iQenpeCJpR86Q4a.eCZmcuy916pww0BhfVaoXkY1Yl82N6LyNiR5DJbnQQhPj0hGLHfhrtHt6.treq9DFG0dCj0kv6PhjzP6DVqOHfDEQcQVVk1VwvZwxH8m2r15DOB2glwBgdnf4P+FlOSlwsSy6y771h3ROf4aH8pMa6H3sDdhX.Okv0PADmiIGQ2knDaALx5ba5xjhvtRhjFgrJutvcP29hmxSj+grH1gdTEQcTWvPIr26DZ3IL5S2R34pPthGpUelmamgm+HDX7NYdiRIdiqh2g4xFwOyqbY8B1YZX5WrVHOLKkCl0MgYMCXNFHYY.oxIP5J3tNgr.Y1JJ77I31b3RpGAb+lPIQVzB+7B3VBPBtbEexwzsBAhQZT810pcca3qq8UUp.WAQR6SHg1pSnRoPgmGMrt8cs0gFqbDUtivM1i.GwpKq8CFhsLXj2lMZLc1nwx4Ax84hCUa+vS.nbKgeffCDUWVupVCF2iwo18h4NRlfaK350RMbUmg5bcvpdwzqU4EUVrvgbkHp7dRYH6vXIsZwE2f1iD6IenR6qaWuwcr+b6pZaA+RsUtk8Wn99Z.VJX2FSxtMlrcuQNCW4kvOSzQn1pTi2h34cHjCUMumPYlJFdocER5d7pZ+QkWVwt3R85M10xNAicYUxc3jTrJO1+PZn4sgRPHROe5y4d6oOlY4NINECAE71blbu.ZJcV9e8wjrgR8ppztTDBhJ0IcWJMoqqGykFhXfQNOV6RQZvmVD6I+3u+GqgdP6MHRxPy.VD1k.ZnjoNLVaPOAJIljKuHdCZzwRQfV1zKRHY9T2zmMpp4qNp4frRn7lQxAJWy4zBh7YttdzNhHlx0aVXFJoGzk8bMxewU+kse8y+g07yUN+2hh60i8Lcg2dLO+HH5MnsOTOFYsD9AQTa2jvV6niAEgTuiotGHzxi9m0sfJlCS3MKipdCIcAEBMqcopOwAjOv7Mlh0VKOc0VOkq9oDtWA2gIc5Od7tvXvKDD79FuouT8o3M60i5Hy.aY7VOZhOKUd5xql7qllP4yRfxR3txPJAhlNpKwO.pOnwSEbJU82EMQDL0MQzIj5IHtCC1SD6UMWGhtog449qM0a087Ew7b6UJx2mFPIpGtLz4BM2e+sCEwAE05MqoCVNHDJ.CtByE1iSA+tz7L1JTDE0CNNZaEYtTm3viT9pLN6SgNZhxya2Xe3tmyodfxXKKfEjiptqYN6Pfb2mYJsdWpc.QeeCIrZ55EnaTf9lEnWs.8sJPe6Bz2IiNwgtCIPEYn5rqPM+yOcwlfA5PfirQOfqyNZjwSDOeIFCiNxmqwkgMNKaN7Ls.1605s0Oaq2V5+k0ayMRvEFMyFSEwuc1LaILrUblT4VDZCpGImC7aYtx9YL9tliofbaNT+Q1Q3QBK59KM0i9Texi9TdpiQTGI6yzX5S8hYwQ.NWm9Z.uDt3HSmNhgJ4o0NKdIj+QfLitqt2Zy055KDx94esj0zbziT9Me8Osey+EyvN4KxoMWeIrNTz9illAWBqSU93AvWFCuU9A.b2WDKgFhF1TBFBU6Bcq4PM6eYAUzbBcMEsNBlxc0D+E7Icw5Ca1QsX8gKNstjKk1SpMbBCkefe+cQrtKJaUSu+W9tyYnofyV5uqGn1pDkqJBpG1xCZA1K2.sYSqNCyjzXBOR9mymIY9LIymIY9LIymI4c0LIMlOSxG1yjz3rXlj2r1TOSxSt62+0ymIY9LIymIY9LIebNSxYAJ8INghG6jTvUg0Kn4.njq+WnXQ7NJZ6Q+UKw3ZqTS8WIj8XGGU6B2.7viWmFyfN2bFzY0YPmaMC5b6YPm6LC57kSTG0yt2KVJ7Sp9AL5rYRfk0liBrJg9a.+BjeqA

(I used a Midi Controller to control the Gain).

For my plugin it makes more sense that in the middle both samplers are at 100%, so I changed the value to:

	MidiController1.setAttribute(MidiController1.DefaultValue, 127 * (1 - value));
	MidiController2.setAttribute(MidiController2.DefaultValue, 127 * (1 + value));

Ah nice. I shall load this up in a bit and have a proper look.

Much appreciated

@d-healey it's a 1 to 1 relationship in this case so I think I might be ok. I'll test it in the morning and see if it works for me though. I appreciate both your input and replies, thankyou

@DanH oh wow interesting. I'll give this a go as it sounds like the sort of solution I was looking for. I'll give it a try tomorrow and let you know how it works out. Thankyou for the reply

@Chazrox thanks for the reply. I tried that the other day but it didn't seem to work.
If I dragged the start/end point in saw when using it in a project, when I reopened the saved project next time they were back at the start and end of the waveform as they were originally.

@rzrsharpeprod Further info in this.

I just added an audioloopplayer to the project and it recalled the drag points just fine in DAW.

I also just built a basic project separate from the one above with just a sampler and waveform in it.
That didn't recall the drag points correctly in DAW so that leads me to believe that the sampler itself is the issue and not any clashes of code in my project etc.

So now I am hoping that there is some script that I can use or add to my script that will allow the drag points to save and be recalled in DAW?

Hi all,

I am an issue that I can't seem to solve and I am hoping that somebody can point me in the right direction.

I have a sampler in my project and an audio waveform in the UI. The user can drag the start and end points on the waveform and this will affect the start and end points of the sample.
This all works fine but inside a DAW when you reload a project in which you have changed the start/end points via the drag feature then the new points are not reflected and the full sample range is selected again.

My questions are as follows:

• Is there something I need to add to my script to allow these to save?

• Is this how it is supposed to work or could it be something else in my script causing a clash? I can't find anything but maybe there is something.

• I have done this before using the audio loop player instead of the sampler and it recalled fine.
  It may be worth noting that I am using expansions. I have never used them before and a few unexpected things had to be solved because I was using them, could this be causing a problem too?

Any help is appreciated as I can't figure this out after countless tests and builds but with no change

@mehmethand sorry for the long delay in reply. Can this then be used in the search bar in the preset browser? If so I can't figure out how you would go about doing that

Hi all,

Just a couple of questions I have regarding the standard preset browser. I have had a look around the forum but couldn't see anything about these specifically so I am asking here hoping somebody can help.

If you minimise the plugin and then bring it back up again, currently my preset browser is defaulting to going all the way to the top of my expansions list rather than still showing the selected expansion. It is doing the same with the presets as well, the one further down is still selected and playable but it is going to the top of the list when you bring the plugin back up. Functionally it is fine as the correct preset is selected, but it just looks a bit odd from a users point of view so I would like to fix it if possible.

My second question is about the speed of the scroll up and down the expansions/banks/presets. Can this be changed at all as it is quite fast?
It doesn't seem too bad on the presets as there are 50/60 per expansion, but there are only 10 or so expansions so it is a much shorter list and seems to be much quicker. Maybe the speed is tied ot the number of elements in the list I am unsure but hopefully there is a way for me to tweak it a little?

Thanks in advance

@mehmethand Thankyou, I will give this a go at the weekend and see how I get on

@d-healey said in Searching across all expansions:

@rzrsharpeprod You'd need to modify the HISE source code for this

That sounds like fun...!!

@d-healey I thought that might be the case. I'll try the solution above first to see if can do it without the need to modify the source code