@d-healey Thank you! I will thy that 🙏

@dustbro A 4k monitor (or higher resolution monitors) user can't use the screen zoom in 100%, because the texts are very small with this setting.

So everybody uses higher rates like 150% or even 200%. I think this issue should be solved. @Christoph-Hart

@civet If you can achieve the result you want with a FloatingTile then use that. It's the native widget for this task and saves you work.

@Christoph-Hart said in Now M2...:

If you already have M1 hardware there‘s no reason to update IMHO.

Yes indeed. Maybe next year there will be M3, then A1, F1, Z9... :)

If the architecture is the same with just iterations, no need to follow that :)

@d-healey Ok thanks, I thought that it was a flag something like this format or something VST23AU=1 :)

@d-healey That's interesting and good. I have to do it on mine.

@Christoph-Hart Good to know that thank you!

@d-healey I'm haven't been working with scriptnode so any example will be a good starting point for me, if anyone has the time to do it.

Thanks

@d-healey Yeah but because it only measures the CPU usage of the audio thread (this is how CPU meters usually work in DAWs).

It's basically this:

My favorite one from yesterday‘s commit is the scriptnode bugfix for the random property reset. This drove me crazy for months but I couldn‘t reproduce it...

@ustk neither a mac nor a windows machine :)

@d-healey really good catch! thanks for this quick solution.

My best guess is that this bug is system dependant because its using the underlying fonts of the system. Good thing we have other Linux users here :)

@Christoph-Hart

ok thank you!

@d-healey said in Scriptnode - octave doubling effect:

@Lindon This is for an audio effect plugin? I believe you can pitch shift with scriptnode - https://github.com/christophhart/hise_tutorial/tree/master/PitchShifting

yes well Christoph wasn't kidding when he says:

"The sound quality of the pitch shifting algorithm is orders of magnitudes worse than the current industry standard,...."

@Steve-Mohican No, first export as a standard release build and see if there are any issues. If there are then you need to export as a debug build, to do this you open the project's .jucer file (it should be in the binaries folder) and export through xcode/vs as you would when building HISE and create a debug build.

@UrsBollhalder Sent you a message. I knew you would get it to work!

@Natan I’m just pulling your chain mate 😂 new ones do look good 👍🏻

@d-healey I'll return the favor and make a video 😁