@Yannrog There's an unmerged PR for it here: https://github.com/christophhart/HISE/pull/823

@Chazrox so is there ever going to be a windows version?

@Sounddiy
No problem! Good luck!

sometimes you have to change the values ​​specified in the schematic

Not only that, but even if you go so far as to rip the components out of the real circuit and measure them electronically to create a model of each component, it won't be accurate.
Because an assembled circuit behaves differently to a disassembled one! So the true solution is to build mini circuits that are loaded the same way as the specific circuit you are modelling.

The deeper you go into Analog Modelling, the deeper the rabbit hole becomes!

It's not necessary to go to such lengths to create a great sounding product though. You'd be surprised to learn that almost all of Arturia's plugins are not real Analog models but are waveshapers and compressors in certain arrangements... ; )

@resonant Glory to God,
It worked, thank you so much.

God bless you 🙏

@David-Healey It's not perfect but I'm still figuring it out. Chat may not be the best option but I think it did pretty well. I have high hopes once its dialed in.

@orange Amazing! Thank U!

@Sampletekk can you load an audio file into the controller panel for testing? I know it works for midi.

@Christoph-Hart said in Filmstrip knob value display:

Hi,

the code you posted works, but it's ugly:

Don't use these autogenerated JSON blobs. They are so 2017 :) You need to somehow process the raw value, or it will look ugly on the label. The function Engine.doubleToString() was added for exact this purpose. Did you check out the value popup feature? It does something similar and requires no coding plus it shows the correct value including suffixes and tempo names.

not that ugly

@justinfitzmusic Select any Preset that you saved

Spending two years learning HISE to release two plug-ins in the same few months the market is FLOODED with AI plug-ins has been a bit disheartening, and I did start to slopcode for a few weeks, but found I was wasting too much time trying to understand/correct the code.

Learning from Davids vids and the forum has been enjoyable in that it is a challenge and feels like progress I am making. My plug-ins are very much based around samples from vintage gear and samples, so still feels HISE like a good option. I also want to have a strong understanding of what I am doing without being reliant on AI so I can continue to offer support and upgrades to customers.

Interested to see where this convo goes, as I do feel uneasy using AI for ethical reasons like environmental harms.

Hope it continues to be enjoyable for you @Christoph-Hart!!

My Plug-Ins if anyone would like to check them out! --> https://partybagplugins.com/

@ulrik said in How to Crop button bounding boxes:

@Jeetender This is a simple Laf version

HiseSnippet 2193.3oc6Y80aabbDeOIcNlrwMwot.8ohEJEETxTL7zerchaQn9GSXijLgnrhCrDTWd2Rxs73sGt6njXcDPereExa8SPeuuEf1OGE8iP+.D.2Y18NdGknjkYiMpcMePP6Lyt6LyNyuY18pGHs4ggx.hQ98F3yIFuuYiAdQcVuCS3QpsAw3Vl62eaVTf3zsXsHqMvmEFxcHFFS+EnHF4lgn98u+70XtLOadJIBYeovluknmHJkZ8Jekv0sJygumnWFoWtRMao25RWYePcl1rLwmY2k0luCCEaJSxWxB6PLl2z1YY6ksuWyksXrV22p483Mef08s3OvdEmO01lYuRSaqkVhQLtwlNhHYPiHVDOjXLyZRmAM5HOwSuA6KBEMc43.KRCXm0jqJccPSDoRVuiv0odheJjPLLqm50lV60ti41BGwP5oduOTwflNirNPioFU8ldD0yJq5UNi5MFUxHiJMiVktsYC6.geTJGTe9Il07h3AsXv4TVUQKKYp+wLlqKAI7hJ0i0kWM.FLbFEtW4xEoKWt7bOLed3rJLhV0UxhDds2S3xWl9aoIStMOZcYOeoGLnvriH0rvr0S1k0JyTrC3faXKoMycKor6pdNU4b2BfzfbkB3sEgfdTsumcjP5UXVm.1I5.y5bV2s4.yYKRakvucQpr4eXt7OKet1kBQ0ACrJ.zJ0rsd.rz.uVPz3tx9dvQ9tb6HlWaWtRLFnPEoKhRkO2wr.ZO1oMbkQgfRCabmR1bg6PIe5RGR+DpZXHucOvhZH9ib5cQsnjOywArejxbnySsb1bzwBK1vkXwC+jEenlYHrQwrtxkKV7NYWlkNToxsjAzBBfQ4GREzeihuW+dPvomG2MDHd26NW9bfCRsD.qKZcJ6wG7ugOUbHcdZm4.iD0Mzq.6gdSB0aRHrIIqBLRs5pk+Bm.hHduzyfbW1ovS0tn4EfcWvZdwbEACcAZ37nFTL1AVToOKbN+xgEoVp09LsdJZoOafyv5Jyo7gzu8aoiPx5vgJL5PPytg9XP4PBP0qvnqxXbJYCUFNUvd3ERVvhTHMJIXJwALpCJheZzj6fR184oubNpyxeFFcNR5JpXWHoDxHm6gIoZTo2NxH9i7Jnx1xeVd54Y0p0X4go9ARWWdvXYi0GBtpIV.h1ZhF1wL297gBBXfiBrZd4.qYw8s0HQYDT5UySD8Het2kUMfDCegfvwZEHZjBB9mFCA2vU3vCHB.o88L+JOYSKhRgiq886WZoOtB4w01fEwRVFXEgcwmGDIPCvXC9wPkTMxdNyM3gcij9vFMDjEpbGEWJRuoYODUa8GXNx4J4zgkd+ScqLHsNbsJwJPRcjyAxRRfOgobib49nmiSJMgFo96964OG0EQxDhhJQYnS8KMLeVdJc1gdyZNy9YzYaH546xoXyEVyVDEnFDyeJvZAK0Pn5rq7juVFzMDZPfCLZwbC4JdMzPkawcvPaf0xkJqX7X+M31rAXDEPsbL0MfC5wQ+wg7FfRaySvJGcS5xOoJyFhu.xVwSodZFEPcwXpXnz1ZrhLxFupJ6hiq8SApTphIkZA+8v7mQNQ3D0I6wRGtncmzFo9W9URQIzt2eP6eyDTbqWXj3kDFToekdBGGWdcYn.y5x1VGTH1GszXZ+ku669aedurMC9MeO.AkNbsJg8a0R.TLMoNqQ5IchiisEM4tDzNfl0LUcT5mFOnT7LwCPGgAPyfPPHxKVdxDmCrRFi+6CdqMGn7+WkC7bs+8hMDCshKc56xhFs+bzIGy.ixy1TL13qGD8OH6sbNeS6yb8ZZ+puSw0UcusYcQjcmwquSMF8Epm7pVeiuBzsL2rUKnwjTkcFypO4Uz8cl9h9q7I47OQs4ue7PZ0mXMta5X7mMSanvOfCHK78j0cYCJDxvrucAcrHsoqztqps8KzERLN0ZnDEriSRljlUtw01qXckdEBzdHBsowp.r1cfdwGIEFnYLEVfPOtLNFiQZv8bTCdN7KloEN1HloUByz1cH6viNAAfvVVh+ehwMQe+O2Dv77g.T9QgJusGh2uOOHTUG48LALlRkIqhXXH3sHNVFNcTzpKcG32Q5IrQRZIRrgU6A8.GkXHoIBqkbPkXSeIKbOlvEyKZzOD5fy4QdMf0Q8BEPrnwNphP2PihMnNCAZtsI1CHD.yCJYOLPd71SZPEdbnejhwKItSIPTZkCrodpBVSYBSG4qRpRptEmgkz9m9983HHydJczcsv8QtPe4j808RBNjIoGxrox2b3a.oJ.8EouATJAqq3MffxZbHCJKgudTD7uoxXdknZdGCJIbpyBNO30z+HkaXLy0FgEMI5aLUD9HSkK+MIEVER7liB+gl0Y+uP.wqCz8qAVv45H+R.CT2o8cfAuCL3cfAuM.F7yR5we09NB4VRrqBk+3NZJTjDE6dlGb4MH7W+g+408iD4es+HQMF3Yus98DF5yUWRZu.lcWvGkcqP0bSOF3ucxJ+tRYD9NkY+HUMT2B.N0BhfkO6hrKGPnB4iPqJzYotEvmYt4mcPcl6B5qQDdvmVhBphOENebOXKlmf0kyvQdNgzER4Q+0zp8i5Gvo65s1AaDzu2Qn5FdvVM1qQ0cOZynN7.Ny8ngrNZwirrVYs5aez5eboSXGSTuAi9bV89K5+0EDUYGYIromSxvyiqNy0CW8E7Uxl4U0WI60b99+suOvONeTubI5nt36lPQRWHIbHpeKVe2nDpilAtszSlbaprAw.xQ617fr59XMnUihfDoTJ2oxtbWNKLS1xupxVvUlXAmOO7kvWX8R+ANG640uvTqtTD1f91w65L8aZuqyaNk3dcrG8X1Axir0OBDFKeSEEvt8TELxYtMNlN5GER8qGfJdjs8nK0El3hS5DWZRm3xS5DWYRm38lzId+IchO3EOQrn0p8ij8zorDx102T8.LFFCaxvXZx+gHAGLe

this is absolutely amazing.. thanx again for the snippet.

Capture d’écran 21-10-2026 11.33.44.png

Empire VST v3.5 is ready! 🚀

Create your own instrument and effect plugins without writing a single line of code.

Have any questions? Feel free to DM me!

TS EMPIRE 🔥

Thanks, that’s really useful. 10 hours is a lot. Which part of those steps would you most want to skip? And if someone made the plugin capture and sync part for you, would that be worth paying for, or would you rather keep control of it?

Quick follow-up on the documentation gaps raised earlier: we’ve expanded SoundSync’s public pages so the features, fees, and commercial policies are easier to find.

Product migration is now supported. You can bring a catalog from another platform using public store/product pages or a supported spreadsheet/JSON export. Imports become drafts for review before publishing. Customer accounts and existing recurring payments are separate from catalog migration. Migration details

Security and integrations have expanded too. We support authenticator-based two-factor authentication, recovery codes, and team accounts with role and product-specific access. HISE developers have both HISEScript and native C++ integration paths, alongside the JUCE package. The API documentation now covers substantially more of the platform, including licensing, refunds, subscriptions, and partner integrations.
Account security · Developer documentation

We’ve also expanded the Website Builder and branding tools, including root-domain support and SoundSync-provided SSL, plus native affiliate and collaborator programs alongside reseller integrations.

The commercial details are now explicit: Stripe and PayPal checkout, USD-only pricing, and one 10% SoundSync fee covering ordinary payment processing on SoundSync-managed checkout. Developer, affiliate, and collaborator payouts follow the same schedule: the 1st and 15th, after the minimum 14-day hold.

The updated pages also explain Merchant of Record responsibilities, tax handling, refunds, disputes, and payout eligibility.
Pricing · Trust Center · Payout policy

Thanks again for pointing out what was missing. That feedback helped us make the information much clearer.

Thank you for the help @David-Healey ! This worked perfectly.

I would like to include a few additional notes. There is a good bit of information that needed to be passed to each sampler. The interface relayed this information to controls in the MIDI Processors via interface control callbacks in the following format:
scriptProcessor.setAttribute(controlIdx, value);

In the onNoteOn block, Message.ignoreEvent(true) and Message.makeArtificial() were called. The note IDs produced by the Synth.playNote() command were stored in an array that was referenced when turning off the notes with Synth.noteOffByEventId() in the onNoteOff block.

@David-Healey - well that seems to work so thanks again.