@d-healey said in Hise won't open on Windows 10:

I have the latest updates installed

Latest updates from W11?

No antivirus.. only the default Windows Defender. I added the whole HISE folder to exclusions.

@Christoph-Hart said in Hise won't open on Windows 10:

What happens if you run the debug build from within VS?

Nothing happens..

I formatted Windows 10, reinstalled Visual Studio, Faust, and IPP. The build succeeded, but I still can’t open HISE.exe.

I’m suspecting something: when I reinstalled Visual Studio and selected Desktop Development with C++, it had the Windows 11 SDK selected by default. So I unchecked it and selected the Windows 10 SDK instead. Was that the correct choice?

@d-healey Thanks for checking :) yeah, I deleted that folder. It might be related to some windows update? I'll try to unistall the last updates

@d-healey Thanks, I will

@d-healey No errors in the console. When I click on "Start Without Debugging" from the Visual Studio exported project, nothing happens.

@It_Used said in Hise won't open on Windows 10:

had this on Win 11, and after clearing AppData path (Use Win + R, paste and run it) %AppData% delete folders HISE or HISE.exe.

Thanks I also tried this.. but the issue is still there..

@d-healey Nothing.. the mouse cursor changes to the loading icon for about 3 seconds, and then nothing. I also tried opening it with the console.

The build is successful with Visual Studio 2022, but I can’t open the HISE.exe app—not even in compatibility mode or as an administrator.

I’m using the latest develop branch, but I also tried older branches. I tested without IPP and without Faust, but I still can’t open HISE.

The only HISE app I can open is the compiled 4.1.0 from the Releases.

Any ideas what could be wrong? I’m on Windows 10 Home 22H2.

@Christoph-Hart Nice, thanks! Yeah, the idea is to start with just a few sound designers for now — actually, just one who reached out to me, hehe.

I’m developing a plugin built with the HISE commercial license. I’d like to allow third parties to create and sell expansions (image, samples + presets) that run inside Raizes.

These third parties would not use HISE at all — they would just provide me with the raw content (samples, presets, image), and I would do the integration into the plugin. End users would then load the expansions through my player.

Since I hold the commercial HISE license (closed source), is it OK to distribute 3rd party expansions this way?

@bendurso O wait.. I realized there's function called Engine.getGainFactorForDecibels() I can use to convert dB to gain factor.

I really like the new Flex AHDSR, but I noticed that its Sustain parameter ranges from 0.0 to 1.0.

In the previous regular AHDSR, Sustain ranged from -100 dB to 0 dB.

The issue is that I want to migrate a plugin that used the regular AHDSR to the Flex AHDSR, but the Sustain values don’t match. While I can easily update my preset values with a script, it becomes problematic if users save their own presets.

Would it be possible for the new Flex AHDSR to use dB for Sustain as before? Or perhaps include a toggle between normalized and dB values?

@JamesC Have you checked the macOS Deployment Target in the Projucer file? Check under the Release section (or 'Release with Faust' if you're using it).

It should be set to 10.13, but it looks like you have it set to 10.09

Wavetable Export – Residual Noise ignored
Preview applies residual noise correctly, but the exported HWT file bypasses it. All other settings are passed as expected.

Is anyone else experiencing this? I even tried the exported version 4.0.0 of HISE and ran into the same issue. I tested on Windows as well, same problem.

I also tested with the 3.6.2 release, with Loris installed in the HISE app data folder, and got the same issue. That’s strange.. maybe I'm doing something wrong?

This are my settings when trying to export:

I’ve noticed that the Loris wavetable converter (Zero, Static, and Dynamic) doesn’t seem to export correctly. Regardless of which residual noise option I choose (Mute, Mix, or Solo), the exported HWT always sounds the same.

In preview mode, everything works as expected—you can clearly hear the difference between the residual noise options.

Preview Mode - Dynamic Phase / Residual Noise: Mute

Preview Mode - Dynamic Phase / Residual Noise: Solo

However, once exported to HWT and loaded into the wavetable synth:

Dynamic Phase / Residual Noise: Mute

Dynamic Phase / Residual Noise: Solo

Both exports sound identical to the “Mute” version.

The same thing happens in the zero phase mode and static phase mode.

I’m on Mac and using one of HISE’s latest commits. I also tried an earlier commit from before the wavetable synthesizer rewrite (a86dd6e), but the same issue occurs. So I’m not sure how long ago this broke. I do know that about a year ago I created a wavetable-based instrument and it worked fine.

@modularsamples Nice, thanks for the details.

I think I’m going to get a decent Intel computer to compile for Windows and Linux x86—it’ll be easier, hehe.

@d-healey thanks I will check it :)
@modularsamples Thanks, sounds good. I ended up using UTM in emulation mode, but yeah… it’s really slow. I actually have an old Mac running Mint that feels faster than this emulation.

This virtualization with Rosetta sounds promising. But it’s really important that all the libraries and dependencies are installed for x86_64, right? Because if we build HISE using some ARM libraries, then the resulting plugin wouldn’t work correctly on x86_64 machines I think.

@d-healey Oh nice, but if I do it on my computer is free hehe
The proxmox server is a paid subscription right? Or there is a free version?

@d-healey said in OS for compiling in Linux?:

Great, thanks! I also just found something called QEMU, which allows you to emulate (rather than virtualize) any operating system on Silicon Macs. That means I could run Mint on my Mac M4. I’m going to give it a try.

@d-healey This is a bit old, but.. I’m now trying to use Linux on a Silicon Mac. I understand that Mint doesn’t work with ARM processors. If I use Ubuntu 20.04 Focal (ARM version), will the plugins I export work on non‑ARM computers? If not.. is there another alternative?

@VirtualVirgin Like this:

(right click on the container)