Ok so after racking my brains for the last week on this, I've thought of a possible third workaround making a filmstrip slider (Knob1) to do the animation and having that linked to the lfo modulation (LFOModulator1).

I have a similar thing in another project running gain reduction meters from the dynamics module reduction that works perfectly so I'm trying to adapt it to fit this, but it doesn't seem to work the same way trying to link the slider to the lfo modulation.

I think I know where the problem is in the code but not sure what I need to replace it with. (I think 'GainModulation' needs to be replaced with something else. I've tried a few things but I'm still stuck :( )

I'm basically trying to get the slider to animate up and down on its own so that it reflects the behavior of the custom table in the lfo modulator (so frame 0 on the slider when the custom tables volume is 0, and frame 128 when the custom tables volume is all the way up)

Heres the code:

const var LFOModulator1 = Synth.getEffect("LFOModulator1"); const var Knob1 = Content.getComponent("Knob1"); const var t = Engine.createTimerObject(); t.setTimerCallback(function() { var v = LFOModulator1.getAttribute(LFOModulator1.GainModulation); v = Engine.getDecibelsForGainFactor(v); GainModulation.setValue(v); }); t.startTimer(30);

Snippet here if anyone can please help...

HiseSnippet 1229.3oc0X0raaaDDdoj2Fa0pzjzbnGIL5AEzTEo5eZKJJBskrBD7ORnz0oE8P5JxURaL4tLjKkqRP.xgdnOFE8InuR4MnuAsyRRQsLQw1PMoHlGHzL6Ly9MyN+rT8CENznHQHxXsimFPQFeD1dJWNt0XBii51FY7Y3ioQRyNhPyc8holGv3vqN8Ls8XtzPyc3LeztSCHQQTWjgQ4GnzzXsUPIO+882k3Q3Nz4rPnSDLG5ALelbN29V6y775PboGy70jdSqtNBdKgmHFPYYbCT.w4TxH5QDkXkvHiOXOWlTDZKIRZDxXkcEtSsGKNimJ+IrH1.OphnIxFLTJ6NBOWEhUbQsFy7b6OKZDg.qzedrobZr413CYtrb9yiQ2HYAy4ZnGOLJcdvqoN7Zb4gmgF7VIEd2Da6DxBjyWQgsOD2kKogCIvQfNrRkEUpUIbKAHAWV2mbJsSHPjqQssaz3tla0nwc91pUpV4d2qZE3v.RGlPBUIAGJbi8Hfy0z76LSRbpOhJ2a3Ppir15EDX8TSLW884hAJ0ls6fhsD9ABNPTa8jUeMcjf76wGAof0cBoP7TkqD1aviU6mRXY8HpLgYKhm2.HSo1vXtijI30tS0JOqZES3QYpIfoJ.PE.1QJCYChkzZEWRkSmQBVRsQJyjYr4XBrPapCa.0KBpWTJ0g3.Fn1jhpTzbJHeBApsRE64oNM3IRRXpuTaijCfYdhofejPR6AtTkmUYsJOuh4qtzvgKbMUrNT34AlbQKmtYmih03w9Cng2Ehf.dyEDRAKliiey435kfNoG8ZBJ3c4LYu.J+Mk4ixxWfZfRYnBDUlTAb8rJfzVSHFjneMbRlDJAv58fP4JuRpxUyT9XhBoJcWEm76EnrKQRPFag2X65Eelz6r8eb8OW8yuoUBM7ZnNMB8CcaqTGJBybEv8BngRlJxYzlNAZNlVQuFtMM5ToHHwWypMfn6E5s+ZNXew.qo4Dl+hUjjFXyd5Luw5kO82tORy1W6BCFZ19.Ma+hSsBlcL0Ej+iwEJgPmwbkiyk9udh0XJaz34C.9CWKzq2SC5rNyD5saKV.Unulp2EOhImpOC5cRO3KKbuItOS5Ldw3szBvqJ09cLdylnUEm1qdNXWA24GW1wWKd5ZiKZ70p427f4G3QevLnTUiQyy4JFHTapGoP76gER1P+j0BtDRW9DnnquviD9pQ+xEc4xWNW9BtDw4mhnbIy+KozKOH0OKtdJHwph2Dj8pkwWHt5DReRLk6nw71Vpq00svQ1CISnCEg9YM5x3+oVGPGAajtjGSglSvcKbz2EaegPNlwGocYQqW9m+t0ABQvdbUmJWc46OlDolJBiZ0scq3HoveFVV1N51PO0jV5F+Ld6MqWb8M581gF816.uzkLq7STm8l4mxpzy2ya0lh37Tvq.H9V3jlWlWYllcKbRy0qN.9F39D96Av86EwRng0gD3SLf6PgOJ12F9lVGJ.UNG9jAfmQIUSoT5FJZEfrob2Dh+AdxVroh1HawlyV7+k8vm3DJdjS5smUsSVMgC327juHeM7gJZy7qMiwMp2.4Ceg7ibbT2v3Kf3yh04KWBc1XIzYykPmsVBc1dIz4qVBc95yUG0eNwNwvftz7efQ+8RmWYjOpznL5eAj9CDyF

@Christoph-Hart Ableton 10 Live, Reaper lastest version. scale is 100%. also compiled with UI 100%. Images are x4 so you can scale on Mac or Win standalone to x4 without seeing a pixel.

Funny thins is when I scale, it gets better. I mean, pixels remain same size but size of the knobs/text etc gets obviously bigger

@d-healey I haven't noticed anything strange when enabling it for all parameters/plugin formats yet...

mhhh... :-/ maybe i'm too naive regarding these coding subjects. i thought that it might only be an question of implementing standard streams somehow. ;-)
i had some success writing a shell script, which calculates aubio-onset-timestamps and filepath of a selected file and saves these into a JSON file, which can be loaded by pressing a button in my hise instrument interface. then i was able to map the corresponding loop ranges to single midi-notes.
Peek 2019-11-26 11-19.gif
but nevertheless, i now found out, that the loop ranges don't work in polyphonic mode, so you can't play 2 different ranges at once. :-/ this is somehow quite unsatisfying, so it seems, that i have to discard my idea of building a loop slicer in hise for the moment.

@Christoph-Hart Great! Thanks

You can also use .contains even though that's not in the docs for strings @Christoph-Hart ?

Console.print(sampleMaps.contains("sampleMap2"));

This is helpful for a partial search, for example if you wanted to get all of the samplemaps with the word drum you could do .contains("drum") even if the name contains other words too.

it would also be possible to load loops via

AudioSampleProcessor.setFile(String fileName)

but then i needed a kind of file browser / open panel for selcting a file and getting it's filepath.

referring to this old thread, a file browser once existed - what happend to it? i cannot find something like this within HISE. any ideas?

@d-healey sorry, I was to anxious, I'm watching now!

@d-healey said in Creating sample based instruments using Pianobook?:

I doubt it, unless he gets a proprietary HISE license, otherwise anyone would then be free to redistribute Spitfire's samples.

The samples don't have to inherit the GPL license, as long as they are publicly available, I don't care (and the JUCE guys also won't sue you).

Just ask the Spitfire guys if they are OK with it, then put your instrument project on GitHub, add a link to Spitfires Download site and done.

How many loops will be loaded at one time?

@Lindon Spot on mate. Fixed. Thank you 😀

Export as 64bit

@Lindon I don't know much about Macs, the one I have is a dual core from 2012 I think, it was gifted to me earlier this year. The only thing I've done with it is partition the HDD and install Windows 10 and Linux Mint.

@ustk
oh man, you made my day! :-) this was indeed pretty simple, but i would have spend hours or maybe days, to find out, that you only can use these container parameters. thank you very much! :-)

@Christoph-Hart Glad it was an easy fix boy 👌