@d-healey

Thanks David, will try that.
Have a great evening.

@ILIAM said in Abeleton shows An error about a plugin I Compiled with the Latest Commit:

@d-healey Is there a way to completely reset all settings and make Projucer 100% clean?
I suspect something might be hidden in Projucer—are there any folders I should delete to ensure a truly clean build?

There will be an app data folder on your system for Projucer, you can delete that.

@ILIAM said in Abeleton shows An error about a plugin I Compiled with the Latest Commit:

@d-healey For FX plugins, do we need to add or remove anything new in the build process?

Nope

@HISEnberg
Thanks for the suggestion! :-)
I had to open a panel anyway to display the ViewPort. I opened the panel using a button. In the button callback, I then always set the ViewPort to the correct position. That solved the problem for me.

@d-healey Hi there, I am replying to this post three years later. Is there any workaround for this at all? (Making the .tablePoint in a table larger than the boundary restrictions for g.drawEllipse(obj.tablePoint, 1.0);

Thank you!

@Christoph-Hart Maybe Anubis can help - github.com/TecharoHQ/anubis

@Christoph-Hart So i've compiled the latest branch to try it out and it looks really cool! my only issue is that when enabling the Spectrum Meter in a parametriq EQ it crashes. I suppose it's because of the CSS or maybe I'm missing something?

here's how I did it

HiseSnippet 1406.3ocuW07aaTDEe1jrUXSQzhJHNAqRTUSPIEuq+nN1BgahioVzzZpCsbqLd2wdGk0yrc1wIwTUUNvA5UNwQtxeCboG3uBN0abkybAdy9g8tdcKUQ.9fkeeMyu2adyu23dBtMIHfKPZEOZpOAocQ89SYR28cwTFpaajltd61sQ6M0GGDPbPZZq9YJSZEVCE94O9z8vdXlMYtJD59bpM41zwT4bs8Z84TOuNXGxQzwo7tRqt1b19bO9D.FqpWB4isOFOhbGrxsUzQ2BG3hz9H8pVksq3bCGKqp6VyFWir6P7vglkcpToV8cMKuKtR8ZjRUQZW3.GpjK5KwRR.Ras83NS66xOkEsA2mFPG3QTBln9vNGotC2yQkhJsn8codN8RpOAHXU5MuZsZT05J5GRcnyzOupcoPCFyiHcATakrva0LvyLM7JkBdKARZofzZQP5x58sETe4bKJ77l5cYRhXHFNmRCkHeQqXrl99bvCl75iwGS5H.gYQrYsRk11.9ZqlEUefiq.owIXgQmdFehQRfiHx84i84LPXy063wwRJazQTOh45wQlNVO7vTAaKHPw31bar2s47iuIyoCg3soJNvwqGP.33QYj9xodj9tDBrEEKd8gTO.jiDXe2hOtXgAPmyHAeByogwFVVVMAUbgCQzvvz+Li.tG0wXiJUpzrPhkcDXG5jfFFk8OKz8y1IvE6vOsgAkAaqQIHPvlgo5GC7fcnYwmjcqazX.YHWPTPvNJgZXbsq0LMf1wFNHAbrQ4xkyZfNFZ1anpIatyNQqZOrzcqTf2ZN3wXLXXLVLhxx.Z52.U6FFwYEnJMLuEl43EhuEx5pktZyEpa0qWWUdR1hpwaQtxHgPVnfopPJnVcYUpHHzvkeBQj6rJLqx4abYsA1VROIa0MtZIHOZBgYOcqlK8v2G63DVUhQUyW5odtrqZ0pKI6JmM6JH49ML1wrTXUL9D9TWpTUY3.OFUNMtFCIW7sfN8Tsy4Z0g17sZNbBCxUNyfytCWRtKaysToMDswhlFNbo1TWnDbOOhXolUbuhWUfaxlLd.QrMTg8lPl4HvujkzR+kSZklSM9.KkibVWFUdWeB6kwzhhIEfe8kcaikXESWrNvOehPRUPPqM4DXNSDuWA81jfigyiPeiogf4YxXh5HltzrRHJPA915YHpPmkdvzzYBOePqX.DsaumdaAdzHLjwchuwxHdnAiROGCZCFmHeQcKyZUrpUpdsxoLXonlqWsZsx0KYVCElrZ2S+wEMLVeVIoqy5M.Qr.FHJEzGYbvWXt91JW5xbHmstpCLTDFf4wO8AbwwAPuGALLD6EPJ9DzoTGo6rr4EOskKgNxc9z4W32RRNSlf1BW3ufOQisyMgAlswcl3gkYG3odVPrAngJyTF0jDV.bWH8yF9WaJ3qKDurdOpz1c4XbkkfQns6+BLF+1g2R+fgCI1x4.bM8Ne0+COT3CRtvr+DwIjCdT74W19qL33NSFG0kqt2qoCoyd.Aco3J029Kuy61RovLQw1+vogJrx9LQlS4EUTYthKEFR0XEF0+vMdtRQsjE86+0eNziar3ZTeQE6t3hZNCpO62hgZBV+5O9GeVjlbf0LGZMyAWyD7h9c6KEhWyD.it5UdPjO4PrYNHalCyVIXt0e99WLbksRv7O8zuyKxmbX1JGlsxf4NcN5.lh0Jp+Z0W69KyWc6883STbnGhg9GfBUG5X5CLI1Dn6lALigMNqnn1ijKojUPpOIrQRWSQ3DazTIqEazLw3+K6wXrsf+P6nQgpKNuQnFHuYg+ajB5GpjMLQgiGSyULFdv+CssytT4Bz57FX4yafUNuAV87FXsyaf237FX8+4.U+eraNQxGGQ8iPG16fnwsZotQf9ajvCcHC

@pcs800 Content.createLocalLookAndFeel I think - check the API browser

@d-healey Ok, I think I know what's going on. When duplicating knobs, the duplicated knob inherits the links from the original one. So if I change the gain of the original knob and compile, HISE applies the value from the duplicated knob, not the original. Thanks anyway!

@d-healey Yes David, adding the following has fixed the issue, thanks!

// Ensure state is saved with user presets Engine.addModuleStateToUserPreset("Parametriq EQ1");

@DanH yup previous commits crash when you connect a non eq module to a draggable floating tile.

@mehmethand said in Searching across all expansions:

@rzrsharpeprod

const var exh= Engine.createExpansionHandler(); var presetList=[]; var expList= exh.getExpansionList(); for (e in Engine.getUserPresetList()) presetList.push(e); for (i=0;i<expList.length;i++) { for (e in expList[i].getUserPresetList()) presetList.push(e); } Console.print(trace(presetList));

I'm not in front of the computer but this should work.
@mehmethand
Your code did work. I have now populated a viewport with the list of all presets across all expansions. I can also type into a 'search box' which is actually a label and then the matching results are shown which is a good start.
I am struggling to figure out how to link further code to it so that I can load the relevant preset when one of the results is clicked. Do you know if this is possible?
Thanks in advance

@d-healey

In case anyone else should ever run into this problem here is the solution (I'm kicking myself).

The Expansion Selector has to be higher than the sample map selector in the UI tree.
That's it.

That's why the minimal project worked, and that change seems to have completely fixed it in my main project.

Thanks again for all your help. Hopefully this will help someone in the future!

@dannytaurus nice. I'm new to HISE and don't know exactly how the Audio Looper works, but it sounds good, I'll give it a go. Thanks

@elemen8t loop points are not a standardized format so I'm doing a best guess to extrapolate whatever info is in the metadata. Can you upload a sample that doesn't detect its loop points, then I can improve the parser.

@gryphonsegg ah apologies I didn’t piece together you were using the dynamics module. If you check out this HISE tutorial I believe it has an example of displaying gain reduction:

Link Preview Image hise_tutorial/DynamicsFX at master · christophhart/hise_tutorial

The Tutorial project for HISE. Contribute to christophhart/hise_tutorial development by creating an account on GitHub.

favicon

GitHub (github.com)

@HISEnberg Ah thank you so much mate, that is exactly what I needed to do, works great. 👍

@rglides yeah I figured that out. Not a good design as far as functionality goes. This is the simplest thing someone might need to do. Needs to be made better to accommodate that. Thanks for helping.

@d-healey In this post you were asking about time-based modulation of the Saturation effect. I know (I think) that this is different to the Saturation parameter in the Sine Wave Generator, but you proposed a solution of a triggered timer controlling the param.

Link Preview Image Saturation modulation

Is there a reason we can't have a monophonic envelope? Essentially a timer that controls a parameter, I mean I can script it... Or is a poly saturator possib...

favicon

Forum (forum.hise.audio)

If we can't currently modulate the Saturation param with an envelope, it sounds like your timer approach would work.

Can you give me an example? I assume there would be a timer trigger in the onNoteOn function?

My use-case is a monophonic synth, if that makes it easier! 😀

EDIT: just found your video on synth timers - looks exactly like what I need! 🙏

@bendurso Thanks!