@d-healey It’s a bit old but.. I just wanted to say that I was able to get the internet connection working in the exported plugin using your fork of HISE (Linux). Thank you :) Not sure why it doesn’t work in the main dev HISE.

@d-healey said in Problem launching HISE build on Windows (Parallels Desktop):

unless Parallels can fake it.

It can but it's really (really) slow.

@lloyduss said in Problem launching HISE build on Windows (Parallels Desktop):

Or do I absolutely need to use a computer or virtual machine running a proper x64 Windows environment to get HISE working correctly?

Yeah, I spent a lot of time trying to run Windows x64 on an Apple Silicon Mac. It’s not worth it. The solution is buying a decent Intel computer. I got a $200 Lenovo ThinkCentre with an Intel i7 7th gen, and it works like a charm — it compiles HISE in just 4–5 minutes.

In the end, if you spend too much time trying to make that setup work, you’re probably losing more than $200.

@tobbentm Sounds good. One question: once the user completes the browser activation, can the user token be saved and used to download their products (licenses)?

@Christoph-Hart Perfect. Thank you very much!

It works now! You can now go back with Cmd+Z and you can also use the track's automation panel.

The only minor issue is that if I load a preset that has macro modulation, then close the plugin window and open the track's automation, it becomes laggy again. But if I open the plugin window again, it's fixed and the parameter disappears from the automation list. Kinda weird, but not so important.

I think the problem is that the macro modulation system interferes with the DAW's automation system.

Ideally, the DAW would ignore parameters with isPluginParameter if they have a macro assigned. But... isPluginParameter can't be set dynamically.

Is there a solution for this? @Christoph-Hart

@ILIAM said in VST3 / Ableton / Macro Modulation Issue:

Worst than that is that you can't undo redo anything, try to bypass / unbypass something, you'll see

Oh yeah, that's another issue. With VST3 and also AU.

I’m experiencing an issue when using a macro modulator in Ableton (with VST3 plugin only). When a macro modulator is active, you can’t change anything in the automation menu—it gets stuck.

The AU version works fine.
I tested this on Ableton 11.3.42 / macOs Sequoia 15.6.1

@tobbentm Hise uses Juce 6 :)

@d-healey said in SoundSync: Reseller, Security & Serial Management Platform:

Sounds similar to Moonbase

The Juce module of Moonbase could work with HISE? Never heard about moonbase but looks cool.

@trillbilly said in SoundSync: Reseller, Security & Serial Management Platform:

SoundSync is meant to put all of that in one place, while still letting you own your brand.

SoundSync looks good as well :) But in my case I already have most of these features.

@Straticah Yeah, this is my code to install the expansions (i'm actually saving other things on that json file, so that's why I used "SampleFolder" to retrieve it from the json)

var CompletePath;

inline function InstallPackage()
{
	local parentFolder = FileSystem.getFolder("../");
	local SampleFile = parentFolder.getChildFile("settings.json");
    local SampleObject = SampleFile.loadAsObject();
    
    local DirectoryFile = FileSystem.fromAbsolutePath(SampleObject.SampleFolder);
    
    CompletePath = DirectoryFile.createDirectory(InstrumentName);
      
    if (CompletePath.isDirectory())
    {       
           expHandler.installExpansionFromPackage(selectedInstrumentFile, CompletePath);  
    }
    else
    {
        Console.print("Could not create the installation directory.");
    }
}

When I use expHandler.installExpansionFromPackage, it creates the link file on expansion samples folder with the samples path. It always worked for me, and I never received a support ticket.

And then I created my own button to change the samples path on settings. This will change the sample paths for all the expansions.

inline function onbtnChangeSamplesDirectoryControl(component, value)
{
    if (value)
    {
        FileSystem.browseForDirectory("", function(selectedFolder)
        {
            if (selectedFolder)
            {
                if (selectedFolder.hasWriteAccess())
                {
                    var path = selectedFolder.toString(0);
                    currentSampleFolderPath = path;

                    var notFound = [];

                    for (e in expHandler.getExpansionList())
                    {
                        var name = e.getProperties().Name;
                        var fullPath = path + "/" + name;
                        var folderObject = FileSystem.fromAbsolutePath(fullPath);

                        if (folderObject.isDirectory())
                        {
                            e.setSampleFolder(folderObject);
                        }
                        else
                        {
                            notFound.push(name);
                        }
                    }

                    if (notFound.length > 0)
                    {
                        Console.print("Not found");
                    }
                    else
                    {
                        Console.print("All sample folders updated successfully");
                    }
                }
                else
                {
                    Console.print("The selected folder can't be accessed due to insufficient write permissions. Please choose a different folder.");
                }
            }
        });
    }
};

Content.getComponent("btnChangeSamplesDirectory").setControlCallback(onbtnChangeSamplesDirectoryControl);

@Straticah What I do is this: when the user opens the plugin for the first time, I ask them where they want to store all the samples and save that path in a JSON file.

Then, during each expansion installation, when I call expHandler.installExpansionFromPackage, I always send the samples to that folder inside a new subfolder. The file link is created automatically by this function.

If the user later wants to change the location, I provide a master configuration option for relocating samples. So I call Expansion.setSampleFolder for all the expansions and change the path of the json file. This way, the user can simply move all expansions at once.

I analyzed different approaches a while back, and this one seemed the most reasonable.

When using WavetableController.getResynthesisOptions(), we get a json file like this:

{
  "PhaseMode": "StaticPhase",
  "MipMapSize": 12,
  "CycleMultiplier": 4,
  "UseTransientMode": true,
  "NumCycles": -1,
  "ForceResynthesis": false,
  "UseLoris": true,
  "ReverseOrder": false,
  "RemoveNoise": true,
  "DenoiseSettings": {
    "SlowFFTOrder": 13.0,
    "FastFFTOrder": 9.0,
    "FreqResolution": 500.0,
    "TimeResolution": 0.2000000029802322,
    "CalculateTransients": true,
    "SlowTransientTreshold": [
      0.8,
      0.7
    ],
    "FastTransientTreshold": [
      0.85,
      0.75
    ]
  },
  "RootNote": -1
}

How can we set this file to imitate the modes "Residual", "mix" and "solo" from the stock tool wavetable creator?

I tried changing "RemoveNoise" and different "DenoiseSettings" but no luck to imitate the "Mix" and "Solo" modes

@Straticah To get the Tags text you can use

ExpansionHandler.getCurrentExpansion().getProperties().Tags

Supposing that is for the current expansion getCurrentExpansion(), but you could use any expansion.

It doesn't contain a description field in the expansion_info.xml.

@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

@Christoph-Hart Nice, thanks. I rebuilt HISE with the latest commit and re-exported the plugin, but nothing changed for me.

What I find strange is that on Mac, the exported app (or plugin) opens instantly without any delay, while on Windows it takes about 5 seconds to load. My Mac is a bit more powerful than my Windows PC, but not five times more powerful.

@Christoph-Hart Thanks for your reply and details to debug it :)

It turns out I was mistaken—the commit I mentioned doesn’t work either.

I created a test project with a lot of sliders, labels, buttons, and comboboxes (using the latest commit), and exported it as a standalone app.

In HISE, the WebView works (the btnNews button shows and hides it), although the interface loads slowly. However, in the exported standalone app, it takes a long time to launch, and the WebView’s HTML doesn’t load.

If I remove the WebView, the interface loads much faster in both HISE and the standalone app.

This issue only occurs on Windows; everything works fine on Mac.

https://we.tl/t-S7yxRTEQQw

I found that commit ffc821ed0dcbde87c3b29dac9023b4b11eaeaf0e (enabled compilation of HISE with IPP by default) works fine. So the issue must be in a newer commit.

The plugin loads much faster, and the html file loads too. @Christoph-Hart maybe this info helps :)

@bendurso After a lot of testing, I figured out why the index.html file wasn’t loading. Once I deleted all the UI components (panels, sliders, etc.), it finally worked.

One thing I noticed is that the standalone app now opens way faster—went from 5 seconds to almost instant. Makes sense since there are fewer elements to load, but it always loads fast on Mac.

So maybe the HTML file isn’t loading because of too many UI elements? The weird part is I only see this issue on Windows, not Mac. A couple commits ago it was fine, but I can’t roll back since I’m using the new AHDSR Flex now.

@d-healey yeah I know. If I embed the Image Files will be into the plugin itself. But the issue is not here because I'm being able to make it work in a new small project with the same script and html (in the compiled plugin).