Best posts made by Mighty23

I made this sketch in Faust to allow us to test different types of saturation

import("stdfaust.lib");

//  Parameters
drive = hslider("Drive", 1, 1, 10, 0.1);
saturationType = nentry("Saturation Type", 0, 0, 4, 1);
dryWet = hslider("Dry/Wet", 1, 0, 1, 0.01);
outGain = hslider("Output Gain", 1, 0, 2, 0.1);

// Saturation Functions
saturate(x) = 
    (saturationType == 0) * aa.tanh1(x) +  
    (saturationType == 1) * aa.arctan(x) + 
    (saturationType == 2) * aa.hardclip(x) + 
    (saturationType == 3) * aa.cubic1(x) + 
    (saturationType == 4) * aa.hyperbolic(x); 

// Main Process
process = _ <: (_, (*(drive) : saturate)) : dry_wet(dryWet) : *(outGain)
with {
    dry_wet(mix, dry, wet) = (1-mix)*dry + mix*wet;
};

Thank you for the tutorial. As someone new to this, I'd like to understand a few things. Apart from when we need to export script nodes to other projects, when exactly is it necessary to compile script nodes? Sometimes, I find that I need to compile the script node to get the sound output, while other times everything works smoothly without needing to compile

@DanH
Ok, it was easier than expected, There are some graphical glitches but the time in ms is correct.

@dannytaurus
have you tried adding this line in extra definition, in project settings?

ENABLE_ALL_PEAK_METERS=1

@aaronventure
the full code is in the snippet in the main post. inside Script FX1 there is the faust node.

    // Add gain reduction meters to the UI
    gainReductionLeft = gain_reduction(l) : vbargraph("Gain Reduction Left", -60, 0);   // Left channel
    gainReductionRight = gain_reduction(r) : vbargraph("Gain Reduction Right", -60, 0);  // Right channel
};

@clevername27 Thanks for the explanation. Your comment on the post helped me solve the memory management. Thanks again.

@aaronventure said in softbypass_switch crashes:

@Mighty23 first, build the latest commit, except if that breaks your project for whatever reason.

I'd rather not do that, I have some projects with different FAUST versions and often in the forum it is recommended not to have different HISE versions. With these two assumptions, the 4+ version still has to wait for me.

Hi,
I would like to know if there are any "tips & tricks" to be able to save the samples loaded on Audio Loop Player in the presets. I searched a bit in the documentation but I don't think I found anything to do this.

I would mainly like to understand if it is possible to save a sample loaded inside Audio Loop Player to be able to distribute it in the presets, not only" factory presets" but also to be able to let end users do it too.

@Straticah I would never have been able to find this solution alone, Wow. Using a panel is the most immediate, brilliant solution, thanks

@Matt_SF This version also seems to work reasonably well. Thanks for your time, it's time to add breakpoints and understand better. Thanks again for your time

@ulrik This solves the problem completely, thanks. By commenting that line I can get the desired result

@HISEnberg Thanks for this. I've compiled and tested in DAW, No problems here

Update / Solved

Add: (I Don't know why)

ENABLE_ALL_PEAK_METERS=1

In 'Extra Definitions' for all OS. Do it in 'Settings' menù or in 'autogenerated.projucer' file.

@ulrik said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

@Mighty23 so your questions
3/16 = tempo 1/16, multiplier 3, same with 3/4, tempo 1/4, multiplier 3

as I show in this video
video

1/3 meaning 1 third of 1 bar (4/4) = 1/2T

Thank you for the time spent trying to understand together. I am on Windows and have not yet tested on Mac if tempo_sync follows the values of the DAW. The title of the post is ironic and means that I have failed the basic concepts of music theory. Thank you again for your time. I'll try to run some tests myself

@Mighty23 said in Missing Binaries (vst3) but XCode notifies "Build Succeeded":

@d-healey said in Missing Binaries (vst3) but XCode notifies "Build Succeeded":

@Mighty23 said in Missing Binaries (vst3) but XCode notifies "Build Succeeded":

HISE-master.

I thought you were using the latest develop branch?

I'm using the the develop branch

You've found the issue, I feel so silly. Again, thank you for the always prompt assistance.

@udalilprofile
I tried using this project in a VST and tested it in my DAW, I had no problems.

There is also a scriptnode example called "transient designer" here, in the forum.
Both examples are good starting points.
https://forum.hise.audio/post/45656

Without making any further changes, I think this FAUST version introduces too much distortion.
(opinion of a newbie).

Something like this?
items: knbValue & lblValue

const var lblValue = Content.getComponent("lblValue");  // your label

inline function onknbValueControl(component, value)
{
	lblValue.set("text",  value); 
	StereoDelay.setAttribute(StereoDelay.DelayTimeLeft, value);   // i've used the stereo delay, use your fx or instrument
};

Content.getComponent("knbValue").setControlCallback(onknbValueControl);

If your knob has a 101 steps this should work.

@pgaudioworks try someting like this, where "cmbSampleMap" is my Combo Box

// My Sample Map on Combobox
const var sampleMaps = Sampler.getSampleMapList(); // get a Sample Map List
const var cmbSampleMap = Content.getComponent("cmbSampleMap"); //combo box
const var Sampler1 = Synth.getChildSynth("Sampler1"); // Sampler Reference

// populate combo box with sample maps
cmbSampleMap.set("items", sampleMaps.join("\n"));

inline function oncmbSampleMapControl(component, value)
{
	//Console.print(value);
	Sampler1.asSampler().loadSampleMap(sampleMaps[value-1]);
};

Content.getComponent("cmbSampleMap").setControlCallback(oncmbSampleMapControl);