There are two ways. The first is to add a script that has a knob that controls the volume of the sampler, then link the knob on your interface to this knob using the interface designer. The second is to use a simple gain module instead of controlling the sampler's volume directly, this also has the advantage that changing the volume during playback won't cause unwanted noises - again you need to link the knob on your interface to the module via the interface designer.

Another loop feature that would be useful is the ability to set the number of times the loop will be played after which the rest of the sample will play

@Christoph-Hart said in No Exporting the IR:

Engine.loadAllAudioFilesIntoPool()

note - if you're looking for this, this is now called:

Engine.loadAudioFilesIntoPool()

@d-healey thansk Davve, I removed all teh EQ code and re added it slowly (one widget call back at a time - and it worked - but I will do as you point out. Thanks.

@d-healey - thats my point I think - there ISNT a slider in my module....I'm just wiring it up in the UI, but its a working work-around for vibrato and tremolo so thats fine for now thanks.

@Christoph-Hart yeah this makes sense - but it'd be nice if there was something in the error message, or process/Console that said - "...checking every sample map in {project}/samplemaps" - just to remind us all

@ustk Yeah the samplemap creation process is a bit flakey at the moment, and needs to be made considerably more robust - luckily it looks like Christoph is working on it.

Bump bump

@Lindon thanks!!! First of all I need to turn my brain on :P

@orange awesome!!!!! perfect! thanks man

@d-healey oh ok - good work around Dave.

@Christoph-Hart Works great now, thanks!

I'll check this out & see if I can contribute. Thanks for sharing.

@Christoph-Hart Ok I see the workaround

But if you script the IR loading, this means no access to the length setting
And if you don't script it, you need to insert 2 audio waveforms in the interface (so the length is adjusted separately) and the user has to split his own files...

Yey that worked and it even says version 2.0 now instead of 1.6

Time to move to 2.1.0 then :)

@daslicht Yes

@d-healey Ok got it, Thanks. ;)

So with this way, "Mono Filter is allways on top in master fx rack" limitation can be solved.
Because there are a couple of filters in this core modules.

Since ScriptFX can be used everywhere; so the developer don't have to be stuck on Mono Filter that is allways first on the fx chain :) Maybe this way would not be flexible and fastly useble like Mono Filter but it should work in most cases.

Thanks! It is way easier...