@11235813 amp sim huh? General DSP learning, loopback signal in non-linear algorithms, hysteresis, tube/diode simulation DSP, filters combined with non linear systems, convolution, tone stack sim, bias… and much more! Other simple functions like tanh or quadratic equations used alone will produce distortion, but they are far far from being called an amp sim.
Not even talking about real measures of existing hardware…

@Lindon yes you have to draw a panel. There's an example in the snippet browser. Look for 'Visualisation 101'

@modularsamples Thank you!! I ran into this error today, had no idea how to fix.

Your method worked!!

For anyone following the steps, be sure the follow ALL the steps 😎

Thank you again!

@robledosilva Doesn't Plugdata already have the ability to compile to a plugin? (And isn't it built on JUCE?)

@d-healey hehe yes, that would be better. But it's a bit late for this project :(

@d-healey said in AAX SDK Compiling - Windows:

@CHEXHOmusic Have you setup your ilok with your PACE developer account? This should provide you with a link to their documentation that guides you through building the SDK and the demo plugin. Once you have the demo plugin working you should have no problem building your own.

We are limited with the guidance we can give here due to the NDA, but basically PACE/AVID documentation provides everything you need beyond putting the SDK in the tools folder.

you dont need a PACE account or their documentation to compile the AAX SDK, and thus compile AAX plugins in HISE - but you will need t to authenticate your plugin so it runs in ProTools.

@CHEXHOmusic theres a lot of posts here about how to get on the Avid developer program, search for that?

@d-healey @aaronventure Thank you, both - you collectively led me to the solution. (VST plugins must go in the VST plugins folder, smh.) All set now.

@d-healey said in Next/Pre Preset & Label what am I doing wrong?:

The only problem with this is it doesn't work for presets made by the user

Ok I think I understand and it's not a problem for this implementation. Thanks.

@Lindon
what an idiot I am. I didn't put the /100 in the right place ^^ thank you it works

@BobCat said in How to draw a transport into a panel？:

@Lindon Maybe my expression is wrong, it should be the playhead

do you know the playhead position, as a percentage of the total playable?

@pelle 15+

@Orvillain Thanks, it was designed by @Straticah

@Lindon ah yes thank U ;)

@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. :grinning_face_with_sweat:

Nevertheless, everything works fine finally! Thanks a lot!