@Christoph-Hart

Hi, I just had a question about the flex envelope feature request.
Is it going to be polynomial approximations used in conjunction with a state machine (and possibly SIMD), or a lookup table?

You said that there would be of course a higher overhead with a new flex envelope but does that mean you are planning to keep it efficient and limit the flexibility of the envelope, or will you go for a truly flexible table, like in Serum for example? My assumption is that it's likely to be LUT based right?

I just wanted to ask, because I might make my own envelope and not wait up if the flex one won't cover my needs for this current project I'm working on.

Is auto vectorization turned on for the hise compiler? I'm very unknowledgeable about this and have only just started to explore it and I have a suspicion this is true? My c++ nodes get significantly more efficient when I do things such as create loops that have predictable numbers of iterations. Leading me to believe there is already simd. I've been debating whether I should try and get XSIMD working in my c++ nodes, because I really care about efficiency in vsts, but if clang is on the job already, there is probably not as much need.

@Morphoice

Keep it up!

@Morphoice

Very good indeed, I'm jealous!

Release release!

@griffinboy

If we ever look into the 3rd party c++ node stuff in a meeting with Christoph, I'd be especially interested to know about how to properly interact with external data, and with polydata. I've figured out most of the c++ node stuff, and I'm working on tutorials for them, but these two things I don't fully understand. I can use them, but not efficiently. It especially causes me trouble when it comes to optimizing and I find that the way hise has things set up means that I can't realize optimisation ideas. A lot of the time I feel that I'm battling the hise framework, when I suspect there are likely solutions to most of my issues already built in, unbeknownst to me.

But then again, perhaps the solution is to learn more c++ and detach more from the scriptnode framework, I'm not sure. I'm always doing overcomplicated stuff

@Christoph-Hart

Wow lovely thanks, then I can release my filters here : )

@Allen

Ah, is that why my multiband is a bit wonky! I've been using my own C++ linear phase multiband and noticed it doesn't play well with hise oversampling...

@Chazrox

That's alright, if we can help in any way, make a forum post with details and we can chip in until it's working again. My code is questionable but I suspected it's likely something your end since I've had people compile this script on mac and windows successfully before despite it's flaws.

@Chazrox

Try make a fresh Hise project and see if my script will compile there. I took a look and I can't see anything obviously wrong with my script.

I'm going to revise the script anyway, which may resolve the issue

@Chazrox

I'll look today and see if I can clean it up for you.
I should probably just start sharing stuff, if I keep waiting for everything to be flawless, I won't get anything done lol

@Chazrox

Strange. If you're on mac, it could well be my fault. This script was not given out as a robust complete solution, but rather as a bit of hasty thing to give to Morphoice : )

I'm glad if it's been helpful to some people, but it's not well coded. If you want to use it, I'll work on a stable version. It sounds like maybe chrisoph will broaden support for c++ in Hise in the future so I'm hoping to release a bunch of modules I've just been too busy to work on them the last few months

@clevername27

That is quite a thing! Thanks

@Morphoice

There isn't a consistent system.
I always interpret the knobs at the last step.

I do it manually rather than use hise's skew.
Make everything work standardized behind the scenes (percentages when possible, or standard ranges) and then I use the UI script to interpret all of them with different curve functions. That way there is consistency and it's easy to change anything.

Then again I work with c++ so I'm able to be quite picky with how I want parameters to be interpreted in the code

@d-healey

Aw man I missed it again.
Was stupidly busy:

Next time

@Morphoice

I just match it against the plugins that I like the volume output of.
Compare in the daw and also monitor the dsp in scriptnode if you want to target something specific. Most daws are 32 bit so you don't have to worry about going over 0 you are allowed to clip from what I understand.

I'm a fan of gain staging so that a VU meter will hit the ideal readings for feeding into analog sims (peaking at 0db on the meter when using the plugin normally, calibrated to -18db).

Hise itself will clip if it gets loud. but if I'm correct I think it wont clip in the daw.

Not related to Hise but hopefully you'll allow it ; )

Just wanted to share this interesting app I encountered.

https://playasynth.com/index

It's a service where people can link up their analog synths (midi controlled) and have users rent them out over the internet. You can control real analog synths remotely in your daw.

They've just started supporting people selling access to their synths, and I know that a few people here have gear. I don't think many people know about this service; it's pretty niche and is in early development.

Just making a post here just in case it was interesting to anyone.

@d-healey

Did we do one on broadcasters already?

@d-healey

Would like that!

@tomekslesicki
Yep I agreed with you. I think the current system doesn't handle it in an ideal way.