@noah are you using visual studio 2022? Are you building with IPP?

@noah said in Problem visual studio cannot find assert.h / crtdbg.h when building HISE:

Btw i took the "produjer.exe" in the Hise4.1 folder bcs there aren't on the HISE develop folder idk if that cause the issue

Oh sorry, forgot to mention that. With the new update Projucer is now in the JUCE folder. You don't need to copy in any external files.

@noah Take the Bootcamp course (it's free) https://audiodevschool.com/hise-bootcamp/

When you get to the part about cloning the HISE source code, use the command I posted above instead of the one I show in the video (unless I've updated the video by the time you get to it).

@noah That's a very old version. To get the latest version you should clone the develop branch using this command

git clone --branch develop --recurse-submodules https://github.com/christophhart/HISE.git

Remove any previous versions first.

@clevername27 I just realised a limitation with this. You've trained it on some of my Rhapsody code, which means it is going to produce code that follows similar patterns. But the next version of Rhapsody that I'm working on currently is using new patterns, so your code will be following old ways of doing things.

I also wonder about its use of broadcasters if you're working with the develop branch. Because I'm doing some stuff with broadcasters that relies on some customisations I made in my fork, if your AI isn't aware of those changes it might give confusing results.

I guess what it comes down to is AI doesn't innovate, it replicates.

@noah How did you get the source code?

@Christoph-Hart said in JUCE submodule PSA:

Was the previous build codesigned & notarized?

I just checked and no it doesn't seem that it was. I wonder why I never saw a warning.

@noah Are you building the latest develop branch?

@Christoph-Hart Some issues I've come across:

• The Linux build of Projucer doesn't have execute permission - I think this must be set on a Linux system, not sure.
• The MacOS build of Projucer has not been codesigned/notarized so it gets flagged by gatekeeper
• The export setup Wizard has not been updated so it's still looking in tools/projucer

@toxonic You can use update alternatives. Here are instructions for gcc

https://askubuntu.com/questions/26498/how-to-choose-the-default-gcc-and-g-version

@HISEnberg Maybe, I haven't used CSS in HISE much so haven't yet formed an opinion

@VorosMusic It's quite limited. I designed my settings page around the limitations. The only modification I made was I aligned the labels left in the HISE source code.

Actually looking at that gif it seems I forgot to adjust the font, but I think I can do that from laf...

@toxonic I've searched the HISE source code for /usr/lib/x86_64-linux-gnu/libfaust.so and there are no hardcoded references so I think it's just that the linker expects it in that location, but I'm not entirely sure.

I guess when you install faust using make install it puts it in a different location than if you used your distro's package.

@toxonic Yes that commit hash is correct :)

@ustk Yes I ran into this issue too a few years ago. I think it's the JWT plugin that was the issue, can't remember now.

I added this snippet to my site to prevent users using quotations marks in their passwords.

function prevent_quotation_mark_passwords($errors, $user) {
    if (strpos($user->user_pass, '"') !== false || strpos($user->user_pass, "'") !== false) {
        $errors->add('password_error', __('The password cannot contain quotation marks.', 'your-text-domain'));
    }

    return $errors;
}

add_filter('registration_errors', 'prevent_quotation_mark_passwords', 10, 2);
add_filter('user_profile_update_errors', 'prevent_quotation_mark_passwords', 10, 2);
add_filter('woocommerce_registration_errors', 'prevent_quotation_mark_passwords', 11, 3);
add_filter('woocommerce_save_account_details_errors', 'prevent_quotation_mark_passwords', 10, 3);

function custom_password_reset_validation($errors, $user) {
    $new_password = isset($_POST['password_1']) ? wc_clean($_POST['password_1']) : '';

    // Check if the password contains quotation marks
    if (strpos($new_password, '"') !== false || strpos($new_password, "'") !== false) {
        $errors->add('password_reset_error', __('The password cannot contain quotation marks.', 'your-text-domain'));
    }

    return $errors;
}

add_action('validate_password_reset', 'custom_password_reset_validation', 10, 2);

@inlandempire said in New to HISE, the forum – and a question about Voice Spread:

But I had not figured out at this tage of my developing career

As you can gather from the thread, neither had we

Doesn't seem to trigger any issues when installing an expansion, but since the error handler isn't triggering anyway it could just be being masked.

@Christoph-Hart The main thing about the flex envelope in Kontakt that differentiates it from HISE's table envelope, is you have a sustain segment that can loop. Maybe we need a new table envelope with three tables, the middle one being a looping sustain...

@Lindon said in How to control Flex AHDSR Decay time with Velocity?:

@Christoph-Hart said in How to control Flex AHDSR Decay time with Velocity?:

Should I make the sustain modulation dynamic so that you can modulate a voice while it's playing?

No, better to think about doing MSEG envelopes....

MSEG = Kontakt style flex envelope?