Hise won't open on Windows 10

[d.healey]

@bendurso Oh now I think I might know what the issue is... A few commits back Christoph made it so that HISE requires AVX to be available on the CPU - this caught me out on one of my VMs.

https://github.com/christophhart/HISE/commit/d7b5a121a825bf9a3fb6153d5e81d3f6a5242420

[bendurso]

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

That makes sense.

[d.healey]

@bendurso What was the old CPU?

[bendurso]

@d-healey Intel Celeron N3350 1.1GHz.

Oh and I was also checking your new video (the course) on building HISE, and I noticed you selected the Windows 11 SDK when installing Visual Studio. On Windows 10, the default option is now also the Windows 11 SDK, and I’m not sure if plugins exported with SDK 11 will work on a Windows 10 computer.

[d.healey]

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

Intel Celeron N3350 1.1GHz.

No AVX support for this one.

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

I’m not sure if plugins exported with SDK 11 will work on a Windows 10 computer.

Yes should work, probably all the way back to Windows 7.

[resonant]

I'm experiencing the same issue when I install the Arm version of Windows 11 on my M3 MacBook via UTM.

Hise compiles but won't open. Do I have to install the Intel version of Windows to run Hise on this VM?

[bendurso]

@resonant I don’t think there’s an ARM version of HISE for Windows yet—only x64.

If you want windows x64 binaries on your Mac M3, you can virtualize an intel machine with UTM, but it’s really really slow. Another option is to buy a decent Intel machine to compile x64, which is what I did, hehe.

[d.healey]

@Christoph-Hart why does HISE require AVX now? Is it also required for plugins?

[Christoph Hart]

@d-healey ah I thought that it might be time to move on from SSE - the first CPUs that support AVX are from 2013 so that makes it 12 years and ~5 generations of intel CPUs.

There's no hard requirement, but yeah currently the plugins would also require AVX if they are built with the flag.

Anyways, looks like I need to add back the ability to switch that. In the meantime you can change this line:

https://github.com/christophhart/HISE/blob/eba4ff226406ae83b21cfeb6e7c83c9b772dbf5e/projects/standalone/HISE Standalone.jucer#L103

Just remove the /arch:AVX
 at the end and rebuild HISE.

But should I leave the default on or switch it back to SSE 4.2 as minimum requirement?

[d.healey]

@Christoph-Hart

Yeah might be fine actually. Although it doesn't list AVX on Intel's website for the N3350, I found specs on another site that say it is supported.

@bendurso If you still have that Celeron machine running it would be good if you could test disabling AVX as Christoph mentioned and see if HISE then works.

[bendurso]

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

If you still have that Celeron machine running it would be good if you could test disabling AVX as Christoph mentioned and see if HISE then works.

I’ve already uninstalled everything from that laptop, and installing/compiling things takes a long time, hehe. But when I export my plugin on the new computer with AVX, I’ll test whether the exported plugin works with or without that line.

[It_Used]

I found the file, as well as the string in it that prevent Hise from starting.
file editorData.json into %AppData% Hise folder.

Temporary solution:

You have into position variable, here you have a array

"Position": [
    x,
    y,
    w,
    h
  ]

decriment values for w and h variables and off "isFullScreen" parameter by false value, then Hise will launching again.

Broken strings:

{
  "Position": [
    0,
    0,
    2560,
    1345
  ],
  "isFullScreen": true,

Other broken settings (Hise has launched)

{
  "Position": [
    0,
    0,
    25659,
    1344
  ],
  "isFullScreen": false,

Resault screenshot

Manually repaired strings:

{
  "Position": [
    0,
    0,
    2555,
    1340
  ],
  "isFullScreen": false,

[d.healey]

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

Anyways, looks like I need to add back the ability to switch that.

I just helped someone who'd made a plugin and sent it to a friend that's using a CPU from 2007 - the plugin didn't work. After disabling AVX in the autogenerated jucer it did work. I think a checkbox in project preferences would be the way to go.

[bendurso]

@d-healey Did you remove /arch:AVX from extra compiler flags or did you something else? I tried and didn't work on that machine

[d.healey]

@bendurso extra compiler flags in Projucer, then save and open in ide