@Christoph-Hart said in AHDSRgraph animation:

Hmm, weird, it should be working also in the exported instrument. I'll add it to the pile of things to check :)

Thank you! :)

@Tod-Slaughter said in Floating tile audio analyser & analyser fx:

Ah thanks, I needed to set the index to 0,1 or2

I used -1 and 1 for two floating tiles that show the waveform1 and waveform2 of a waveform generator with 2 osc...

@d-healey Using Double vectors reduces the bluriness but it is so ridiculous :)

Even if you don‘t defer it, the paint routine will never be called on the audio thread so crackling audio will not be the problem here.

I've changed the image and now everything works good... weird thing... I checked the image and it looks perfectly normal 🤔

Most problems (actually all except for the Sampler crossfade) come down to something funky with the app data folder on Linux.

Good news is that I am thinking about buying a new computer in a few weeks and setting up a proper Linux / Windows dual boot so I stop shooting around in the dark :)

@dustbro Yes we can create variables almost anywhere but usually they should be either local or reg variables. I think the only time to use var is inside panel callbacks.

Oppsss... I left th -1 default value of the index... now it works fine! Sometimes some synapses of mine is out of duty 😆 😆 😆

@d-healey Thanks. I'll check it out.

@dustbro wow!!! That's what I need. Thanks. Doing some weird stuff here. Trying to do a sinewave bank but controlling pitch, dbs and decays by groups. I'm reinventing wavetables I think

Good day all! Great mood before a holiday! Hise compiled on Fedora 28 xfce.
But (base Ubuntu 18.04) everything works at Peppermint linux 9.
It is necessary to set alternative libraries for the correct compilation.
libgtk-3-0
libgtk-3-common
libjack-jackd2-dev

Download:

https://mega.nz/#!GT4XkIaR!hA0adfxyuK7GYMKN4n50cTzImg9Rn-LtQ4flWLUJVQ4

Perhaps someone will be helped by the compiled version for other systems.
But for other distribution kits it is necessary to look for the relevant libraries.

I wish you a merry Christmas and happy New Year!!!
May the blessings and happiness
Of Christmas season be yours
May the next year be better and happier
Happy Holidays!!!290250-We-Wish-You-A-Happy-Holiday-Merry-Christmas-Happy-New-Year.jpg

@d-healey said in Simplifying interface challenge:

@Tod-Slaughter The first problem then is that you can't have a control connected via parameter ID and use the control's callback in the script, it's one or the other. So you'll need to add code in the combo box callback to change the shape type. Then you'll be able to tackle the shape display.

Aha, now it begins to make more sense. I shall persevere. Thanks as always :D

@Tod-Slaughter Yeah, there's probably a reason behind it, but I have no idea.
You could probably use a label to display the sample rate if you needed.

@d-healey said in EQ CPU Usage:

@Christoph-Hart said in EQ CPU Usage:

Something between Nothing and TooLessTooCare. Why are you asking?

I was thinking of adding one into my instruments and based on your answer I will :)

There's also shelving modes in the filter options

Hi, guys.

I'm a software developer with 20 years of general experience. I'm interested in help with this platform.
Feel free to mail me at diazrm@gmail.com if you need to hire someone to help you.

Best regards,
Manuel

I was thinking of adding a different EQ to each dynamic. Not something I desperately need though and can definitely live without.

Without going into the gory details: David is right. HISEScript is not suited for "real" object-oriented programming and as soon as your talking about making dynamic GUI elements you're quickly getting into hacky workarounds.

There is one design paradigm in HISEScript which will get in your way pretty quickly and that is that every UI element has to be declared on script initialisations. This has implications on the user preset system, plugin parameter automation, state saving etc. In C++ it is no problem creating other UI elements if you press a button, because you can easily decouple the data from the UI elements.

Moreover, there's an uncanny value where any scripting language becomes a burden, because you start relying on industry grade debugging tools, and even if HISEScript tries to push that a little further than other scripting languages (which is why I bothered with breakpoint, local variable watch etc.) at a certain point the efficiency compared to C++ goes towards zero.

Once you get past the Bjorn-don't-torture-me-with-<thisTemplateSyntax> state, C++ (and especially with the new C++11 / C++14 enhancements) will quickly become the language of your choice for anything audio-related - and KSP really starts to look like assembly from the 1980s :).
JUCE also does a marvellous job of nudging you into a good coding style, which is why I decided to open the C++ API in HISE.

I don't know you personally, but from what I've read from you in the past (here and on VI-Control) you should be able to grasp the basics of JUCE/C++ pretty quickly and leverage the full flexibility of true object orientated programming (plus being able to write C++ is a very valuable skill). The screenshot you posted is trivial to implement in C++ BTW.

On the other hand, I won't stop you from playing around and trying to push the limits of what's doable. The code you posted looks reasonable (and I must contradict David here and say "leave the interface designer alone for this kind of stuff or you will shuffle pixels around forever").

@orange Ok, I've solved it. It works like a charm :)