@d-healey Yeah I think this has been around for a while. MIDI FX only works as AU. For VST3, you have to compile VST3i .

It's been a few months since I last tested MIDI FX. I think I have a bug report on github about the differences between HISE and compiled version MIDI output as well.

@d-healey Yeah I agree, but my tests showed that all flags weren't reliable when set within Hise.

I think FORCE_INPUT_CHANNELS was not working

JUCE_USE_BETTER_MACHINE_IDS=1 DONT_CREATE_EXPANSIONS_FOLDER=1 USE_SCRIPT_COPY_PROTECTION=1 FORCE_INPUT_CHANNELS=1 HISE_DEACTIVATE_OVERLAY=1 ENABLE_ALL_PEAK_METERS=1 USE_IPP=0 CONFIRM_PRESET_OVERWRITE=0 HISE_USE_OPENGL_FOR_PLUGIN=0

Also I have some hardened runtimes, microphone flags, microphone access, access text, etc...

This is something that is still not clear in my mind as where I should set them all. So I kept setting them manually (until I could keep the jucer with Git)

@ustk Perfect, thanks! 🙌

@d-healey Great thank you so much. I think I need a refresher on the String API.

@Lindon said in Interface Preview - gone mad:

@Christoph-Hart -no it inst doing that - I havent set the UI scale factor anywhere, but in the end I found that GeneralSettings.xml had:

SCALE_FACTOR="1.75"

flipping this back to 1 fixed it...

Same here

@griffinboy 🌞🌗🌍

A Faust generated code is never supposed to crash. If is does, then its a Faust compiler problem, but surely not with freeverb.

@d-healey Please specify. If I release an instrument and a sample under Gpl3 and it is important for me that no one can ever close the code - that it is always Gpl3, so how does Hise allow you to buy a license for closed code? How can Gpl3 not be preserved?

@orange Thank you!

@Christoph-Hart you can see in the video that the network itself gets saved to a file. This happens by default when you Save XML.

Doesn't a network (in this case UpDown) have to be a file in order to be importable into another network as a node?

Why wouldn't hitting Save XML also save the changes in the external/child network?

Can something be done about the UX of making changes there where a reload of the entire host network (either by ejecting it and loading it back or by reloading HISE) is necessary when any changes are made to the external/child network and Save XML is executed?

Any networks that also host the changed network should automatically reload when the project is saved.

Just came looking for this again and noticed Christoph solved this a couple of weeks ago - https://github.com/christophhart/HISE/commit/2057eb72499e0be24b8effe0e908588d40d8311d

We now have Modulator.setIsBipolar() and Modulator.isBipolar()

@Dan-Korneff
@DabDab

For nonlinear circuits (amps, filters) I'm working towards using HSIM: (https://www.researchgate.net/publication/354894471_Multidomain_modeling_of_nonlinear_electromagnetic_circuits_using_wave_digital_filters)

Essentially breaking down the tree into smaller sections and solving nonlinearities locally. A bit different to Kurt Werner's suggested approach of grouping the nonlinearities at the root. Apparently this way is the most efficient (with SIMD), but nobody has compared them yet, so I am looking into doing that and writing a paper.

Apart from that, yeah your process is similar to mine.
Creating models for each component, using iteration to inch closer to the benchmark results from the real component. After that you have to deal with representing the connections :face_with_tears_of_joy:

Lots of work. WDF is good if you know electronics, state space modelling (+MNA) can be tidier and a heck of a lot less code, but I find it more confusing. I've only done filters using such techniques but I know that it's the industry standard.

12ax7_1.png

I'm working on a WDF header library for Hise which I intend to release, but it's still in progress, I need to talk to Christoph more about SIMD support in Hise, to see what the best way to optimise it.

@Mighty23 your roomsize parameter doesn't seem to do anything, is there something wrong in the Faust code maybe?

@d-healey @Dan-Korneff @orange Thank you for your answers, I'll look into that!

@Christoph-Hart thanks I will try this...

@treynterrio When starting the plug-in, I check whether the GeneralSettings file exists. If not, I automatically set the scale factor to 75%. Works on the Mac. I have not yet tested whether it works on Windows. There is also the option of querying the user's display size.

const appData = FileSystem.getFolder(FileSystem.AppData); const settingsFile = appData.getChildFile("GeneralSettings.xml"); if(settingsFile.isFile()) Console.print("General Settings exist"); else Settings.setZoomLevel(0.75);

@orange if possible you can also use a slider pack to reduce the number of parameters (if that is a sensible choice for your node).

But 40 should be fine, the node interface might look ugly as hell though…

@Lawrence Currently not available, it's been requested a couple of times though.

You can use ctrl+# to comment a line and if you use multiple cursors you can comment multiple lines at once.

Peek 2024-10-15 18-03.gif

@Lawrence said in Still Struggling with Multi-Outs:

Is it at all possible to have 16 mono outs instead of 8 stereo?

As far as I know HISE always works with stereo outputs. Although with FX it's possible to have them in a mono mode so perhaps it's possible with instruments too, but I don't know.

@bendurso Thank you very much, I understood its function.

@ulrik sadly there isn't