@Orvillain

Blooming blooms of bloomington! That was a lot easier than I had thought it was going to be! More or less the example in the documentation was all I needed to do. Here's the code for setting up the broadcaster. This happens in the main interface onInit function.

const var b = Engine.createBroadcaster({ id: "sampleListener", args: ["eventType", "samplerId", "data"] }); b.attachToSampleMap("Kick_sampler", "SampleMapChanged", ""); b.addListener("", "funky", function(eventType, samplerId, data) { build_sampler_routing(samplerId); });

This triggers a function called build_sampler_routing, which takes the samplerId in as an argument:

inline function build_sampler_routing(sampler_id) { local parts = sampler_id.split('_'); local slot_name = parts[0]; local routing_matrix = slots[slot_name]['sampler_routing_matrix']; routing_matrix.setNumChannels(sampler_channel_count); local slot_default_routing_data = default_channel_data[slot_name]; for (channel in slot_default_routing_data) { local channel_data = slot_default_routing_data[channel]; routing_matrix.addConnection(channel_data['source_idx'][0], channel_data['sampler_output_idx'][0]); if (channel_data['source_idx'].length > 1 && channel_data['sampler_output_idx'].length > 1) { routing_matrix.addConnection(channel_data['source_idx'][1], channel_data['sampler_output_idx'][1]); } } }

That's how I needed it to work for my script anyway. Your mileage may blooming well very.

Also shout out to @d-healey - signed up to your patreon guv, and learnt about broadcasters from your video. Would definitely love to see more there. Seems like broadcasters can handle a lot of the heavy lifting when it comes to communicating between different parts of a plugin.

@CyberGen Oh, I never thought there is a third place where I have to turn it on. 😅

Nevertheless, everything works fine finally! Thanks a lot!

@d-healey Thx, here's hoping for the best

@d-healey that's awesome . i will check it out

@Lindon ok so I have a hacky work around....if anyone ever gets here with this problem...

Set up your Global LFOs as bi-polar...

add a constant modulator to each LFOs "LFO Intensity Mod" section - and invert the values produced by your UI's depth control to modulate this instead of the LFOS intensity...

At this point the LFO will work correctly... but will send modulation values in inverted order, so you need to invert every "target modulator"... now your modulation should work properly, but if you are using a plotter to display the Global LFOs state, this will also be inverted...so:

set up a "dummy" sound source(a silent synth wont work) that issues no sound and add to it a "target modulator", suitably inverted, for each of your Global LFOS, (you can do this in the GAIN section if you like - it really doesnt matter where - but Im gun-shy of the Pitch section right now) now use the output of these in your Plotters...

Finally that export wizard is giving some meaningful feedback for once :)

i installed visual studio by changing the default shared location C:\ to another drive by using regedit because of storage problems.)

There's a lot in the process that will assume the default location. You can manually edit the system variables so that msbuild is accessible from anywhere, but there will be lots of glitches going forward if you don't stick to the default installation path.

okay guys.. finally i fixed it by manually changing the sample folder in a custom setting floating tile.

P3.png

Both .hwm and .hr1 are work fine now.
The popup installing sample window seens like not works well in this project for some reason...

For the warnning C4715, I not quite sure if it actually matters in this case. I bypassed it by simply adding a return 0 but I think it's ok to just leave it alone cuz it won't prevent anything from compiling.

@ally it's true that loris only accepts one velocity layer per sample map. What I was trying to explain is that you can work around that by having all the dynamics layered within each individual sample that you add to the map. You can easily morph between dynamics using velocity after they have been converted to .hwt.

WavetableSynthesiser1.setAttribute(WavetableSynthesiser1.TableIndexValue, vel/127);

@11235813

https://forum.hise.audio/post/82031

See if you can modify this to suit your needs.

Issue was unrelated to HISE. The "User Preset" folder had admin privileges set to "Read-Only". Altered the settings of the installer to fix the issue.

@DanH Thanks. I also just realized that it only happens with Vel Mod inside Global Modulators. In my case I can use Velocity Modulators directly in the Samplers and it works ok.

@Matt_SF Oh nice! I was certain I tested this too but apparently not!

@d-healey Yeah the apparence I could just treat it this way but unfortunately the number I need to return in the case of a NaN is depending on the context, so it's not that simple i the end

@alfaholic There is no way to show the sample mapping window on the front end of the plugin, you'd have to create your own interface through scripting. It is possible to allow the user to import samples though.

@d-healey I found the files. Thank you. They launched successfully.)))

@tomekbruml thank you for the quick response! Much appreciated.

adb32698-490b-4f2f-9b53-0def7a2c5f5b-image.png
e3fe4cc0-b597-4155-9089-612fadbcbd13-image.png

This is how I handled it:

Main container. Inside:

Sampler Send container

Sampler FX:

A series of send effects. Each one selects a channel pair (0 being 1+2, 2 being 3+4, etc)

Sampler routing matrix:

For the outputs that I need to duplicate.... route the left through to the container inputs. Leave an empty socket for the right. Any top row sources that are genuinely stereo just route through as normal.

Send Container routing matrix:

Connect the top row channels to the 'empty sockets' for the right source. This means that 1+2 now carry the same signal. 3+4 carry the same signal.

Main container:

Now you can add Simple Gain insert effects and assign them to the pairs. This gives you a volume control for the dual-mono pairs, as well as the regular "true stereo" sources.

@alobassmann Well, @d-healey just went to the most important point to begin with...