I wouldn't call this a bug, you just happen to write super inefficient graphics code. Drawing a line with an angle with a gradient is likely to mess up the rasterizer of the software renderer while the OpenGL renderer has a different pipeline.

There's nothing I can do here except for suggesting to write faster code.

@d-healey Thanks :) And sorry, I didn't find that post.

@bendurso No they all must be the same. You can probably pad them with silence to the same length using Sox and soxi. This might be something chatgpt can help with, I've found it quite useful for simple scripts.

@Christoph-Hart Yeah the more I use broadcaster the more I realise I need... More... 🤤

-12 Looks Safe!!!
This is weird, anything Lower than -12 Causes Crash!

@ObsydianX Yeah Christoph modified a few things related to buffer processing recently...

@DanH I've just done a test with an instrument. Using the ramp shape in the LFO you can clearly see a little peak when I play notes nearly every time, showing that the LFO isn't starting the modulation from zero as I would expect it to. Moving the smooth function to 0 prevents this.

@Christoph-Hart is there perhaps an issue with LFO smoothing in FX pugins?

@d-healey @d-healey Your kindness knows no bounds - I'm just seeing your post now; I will try and let you know. Thank you as always.

@Christoph-Hart Effectively, so I need to find a way to make this work like before without rolling back your entire update... 🤔
Do you consider implementing audio inputs in an official release? It would be much easier than correcting what changed each time you fix something related to channels or buffer processing, knowing that I am not the only one who needs audio inputs...

@d-healey such a weird out of nowhere issue to have. thats hise i guess lol

@Christoph-Hart ok it obviously worked perfectly fine in a clean new small project. Still it's pretty strange.. I think I deleted a xml network I initially compiled a Faust node in. I still could export the c++ nodes if there was no rnbo node present in the src. I couldn't find a trace anywhere of the deleted xml network but still somehow it's messed up and won't compile even if I delete the whole network binaries folder. is there any way to compile faust nodes independent of script networks like with rnbo nodes. it's super handy especially if you have nodes you often use in different projects.

@problema do you have snippet showing the problem?
It doesn't happen here when I try

@Lindon Oh, I'm sorry I didn't mention it: This was tested with no pitch tracking applied. Each sample just played back on its root note. But of course, you're correct. I never pitch track a sample more than 2 semitones up or down.

@Gwenao

and just with export in VSTi, i cant found the VST

did you get a message in the export window that it was successful? if so it has the path to the file there.

@Christoph-Hart I have to reopen this as there are a couple of bugs here.

1- Round Robin buttons are still overlapping when there are a lot of round robin groups.

Here is how they look when there are 12 of them. This is the smaller, default popup sampler editor.

HISE Sampler issues-screenshot.jpg

The larger workspace sample editor looks OK for the most part. The last 2 RR groups are overlapping.

HISE Sampler issues-screenshot2.jpg

2- Unable to select RR1 while the last RR group is empty on right-click menu.

If you right-click on the round robin group buttons and the menu pops up, and you click on the RR1 from the popup menu, it will display RR2 group. If you select the last RR group from the menu (eg. RR12), it will display an empty RR group (I assume RR13 in this case, which doesn't exist). So it seems that the numbers are off by 1.

@Christoph-Hart Aaah that did the trick indeed. That's odd though, I've noticed the warning icon before, but thought it was a glitch or something because the ranges of the mid-knobs are correct :

54e20c74-caba-4e8e-927b-e43b3c3b529a-image.png
474b3c10-8915-4f16-b400-d97b720b0e18-image.png

So in the end it was me who was the buggy thing... Thanks for the debug session :)

Is there an extensive overview on which XML attributes are required as a minimum?

I was tinkering with the XML files of a HISE project a bit and figured out, there's a lot of attributes that can be omitted to keep a very minified object tree file.

But, it is not as simple as I guessed… I thought I would just discard every attribute-value pair which is only setting a default value on a parameter. But if I delete all occurrences of

Gain="1.0"

every instrument is turned down to give no output. That's a bit contradicting as every instrument you'd add via HISE UI will be set to full output level by default.

But, never mind! I just explored the beauty of organizing a whole project by just 3 XML files – which makes it easy to create plug-ins on machines I don't run HISE on.

What I found out works very well if you're up to work on a minified project XML file:

Sample maps can be embedded (though I know it's a bad practice, I never had any issues related to it but it helps having all components in one file)

A Bypass="0" can be omitted most of the times, provided your instruments functions are not based on bypassing some modules in exchange

All occurrences of .0" could be replaced by " in my tests.

Alright, I've tested it and there was in fact a typo in the code that caused the buffer glitch sound. I've fixed it so now it should sound at least as good as the default one :)