@yall said in compilation problem:

I had around 120 xml backups

I doubt that was the cause of the issue but you should really use git to manage multiple versions of your xml. I only use 1 xml per project. For smaller test patches I use hip files.

So, if I understand correctly, the colors for combo boxes were set in the actual combo boxes without the LAF

I just reread your exampe and noticed you were using the popup menu LAF functions. The popup menu is not part of the combobox component, so there are no colours in the obj parameter.

A good practice for anything regarding LAF customization is to always use Console.print(trace(obj)) as first line of the function, then you'll see everything you can work with.

@rzrsharpeprod
I wonder if it is the same bug I reported here:

Link Preview Image 'getSourceGainValue' not working in compiled app

I have 2 types of meters. The 1st uses 'getCurrentLevel()' to get the value of ChildSynths. The 2nd uses 'getSourceGainValue()' to get the value of the synth...

favicon

Forum (forum.hise.audio)

@Christoph-Hart Can you please have a look at this issue as well? 🙏

@yall said in delay problem 2:

@Lindon
I just took the delay basic from scriptnode and on another project the delay module from hise. I don't have any concrete plans. I just tested by exporting with 3 knobs to control the delay. nothing crazy but I see it’s a mess

perhaps post a snippet =- and the network xml?

@d-healey
Thanks to you. Yes, that's right, that's not what I want to implement.

@d-healey JUCE 7 only added official support for LV2. CLAP support is not yet official. They also have yet to add any support for Wayland, which will become a problem soon - Linux DAWs are starting to consider Wayland support, as evidenced by PreSonus' beta release. VST3 GUIs straight up do not show up as of right now.

@RastaChess said in Phaser Effect Modulation possible inside a send container?:

degrade, the limiter

Yeah, they are gone for good. They sounded awful, the parameters didn't work and there are better alternatives in scriptnode.

polyshape.

This is still available, but the send container doesn't have any polyphonic effects (it's not polyphonic) so

Both worked Well 👌

@aaronventure SoX is faster as it doesn't have to re-encode the audio. I'm also more familiar with using it than I am with ffmpeg and found I could fine tune the trimming and fading more easily - I don't think that's a limitation of ffmeg though, just my knowledge.

@paper_lung
You could use the Math.random() function as a basis. And then you could, for example, play backwards for values below 0.5 and forwards for values above 0.5. But that's just an idea. I'm not sitting in front of the computer right now.

@yall

function onNoteOn() { var bpm_host = Engine.getHostBpm(); }

@Christoph-Hart can't believe i left showclones on... thanks for the tips!

@Dan-Korneff found it: https://forum.hise.audio//post/68431 cheers!

@d-healey thanks, yeah I’ve been following this and it’s been really helpful. Just stuck with distributing the samples, but I’ll have a look at that link, thanks!

@WepaAudio or just Ctrl-D on the selected Panel...

Aha I finally got it to work, Christoph was right, the force stereo output option must be enabled to get mono -> stereo!

However I notice that stock AU plugins show both mono -> mono and mono -> stereo under a single plugin, so this is what we should be aiming for, there shouldn't be a requirement to create two separate plugins.

This appears to be the solution https://forum.juce.com/t/how-to-enable-mono-stereo-option-for-plug-in-within-logic/41545/2

@Christoph-Hart What do you think?

@d-healey said in Velocity Randomization with percentage:

mySampler.noteOn(Message.getNoteNumber(), Message.getVelocity());

I just noticed this error

Also tell ChatGPT to use local variables not var

well do next time 👅

@0x7887 Omg! Thank you ❤❤❤❤

@Dan-Korneff I know I probably did it wrong.. I used the sln file to open the project in Visual Studio, then opened Cubase with my plugin, and then attached the Cubase process to Visual Studio.

However, the DAW project only has problems opening when the linking button is active. I can open the DAW normally with the plugin if the link button is inactive.

I have a lot of linked knobs like these:

const var btnLinkLayerFX = Content.getComponent("btnLinkLayerFX"); inline function onknbSaturation1Control(component, value) { Saturator1.setAttribute(Saturator1.PreGain, value); if (btnLinkLayerFX.getValue()) { knbSaturation2.setValue(value); knbSaturation2.changed(); } }; Content.getComponent("knbSaturation1").setControlCallback(onknbSaturation1Control); inline function onknbSaturation2Control(component, value) { Saturator2.setAttribute(Saturator2.PreGain, value); if (btnLinkLayerFX.getValue()) { knbSaturation1.setValue(value); knbSaturation1.changed(); } }; Content.getComponent("knbSaturation2").setControlCallback(onknbSaturation2Control);

Is there a better way of linking knobs to avoid problems?