@David-Healey Another vote for disabling the Export menu the pre-built HISE.
Posts
-
RE: MacOS Parallels WIN build failposted in General Questions
-
RE: How to Fix Filters not working on DAW as they do on HISEposted in General Questions
@David-Healey Assuming that you just want me to load the snippet and open the filter module?
-
RE: VST - AU - AAX Logoposted in General Questions
@cassettedeath You can find a lot of brand vector logos on Wikimedia Commons:
https://commons.wikimedia.org/wiki/File:Cubase_6_logo.svg

You don't usually need permission to use the logos but you do sometimes need to attribute them and follow the brand's guidelines.
A blanket statement should be good: "DAW logos are trademarks of their respective owners." as long as you don't imply any sort of affiliation or link with the company.
Safest way is to just use text, no logos, like:
"VST3/AU/AAX versions. Works with Logic Pro, Ableton Live, Cubase, Reaper, Bitwig."
-
RE: MacOS Parallels WIN build failposted in General Questions
@griffinboy said in MacOS Parallels WIN build fail:
What's odd is that there is no error message above.
Yeah, weird.
@pelle Cool. What versions of macOS, Parallels, Windows and Visual Studio are you on?
Did you build HISE from the latest commit from the develop branch, with JUCE as a submodule?
Does exporting a minimal plugin (like a volume knob) work ok?
-
RE: MacOS Parallels WIN build failposted in General Questions
@pelle How do you know it stopped compiling?
-
RE: Samplerobot Loop Pointsposted in General Questions
@inlandempire Yeah, if you bought Logic at any time in the past you'll be able to download the latest version from your Apple account in the App Store on Mac. Free lifetime updates!

Not sure about the loop points, but I'd be surprised if HISE doesn't already support Logic loop points. And if it doesn't, it needs to because I'll be doing some sample-based plugins soon!

-
RE: Samplerobot Loop Pointsposted in General Questions
@inlandempire If you happen to be on Mac, I find Auto Sampler (part of Logic and Main Stage) to be way better than Sample Robot for recording and editing multi-samples.
If you don't have Logic, or don't want to buy it, then Main Stage is only about $50/£30 and I'm pretty sure it has the same full Sampler/Auto Sampler features as Logic.
-
RE: HISE Transformation to the new ageposted in AI discussion
@Christoph-Hart I've never told Cursor/Claude to match existing code styles and it seems to do a pretty good job.
Except it litters whitespace all over every empty line

But your guidance files will be valuable because I won't have to pretend I know what good C++ looks like!
-
RE: How to Fix Filters not working on DAW as they do on HISEposted in General Questions
@David-Healey This fixes it for me, but it needs testing in a real project:
-
RE: New LAF Properties for Modulation Display: Selected Source vs Accumulated Rangeposted in C++ Development
@David-Healey HISE master - do you know something I don't?

-
RE: New LAF Properties for Modulation Display: Selected Source vs Accumulated Rangeposted in C++ Development
@Christoph-Hart said in New LAF Properties for Modulation Display: Selected Source vs Accumulated Range:
that's precisely the difference between "lol AI cannot do s***" and "boy we're f***ed"....
1,000% this

-
RE: CSS Errors for every componentposted in Scripting
@Christoph-Hart said in CSS Errors for every component:
TLDR: Easy fix: add *{} at the top of your stylesheet
To the top of every stylesheet defined in the code?
I have a lot of small stylesheets like this:
lafCredits.setInlineStyleSheet(" label { color: #ccc; font-family: 'Barlow'; font-size: 17px; letter-spacing: 0.05em; text-align: left; }"); -
RE: CSS changes on 25th Jan seem to have broken button spacing....posted in Bug Reports
@DanH Interesting. Still, must be related to this my issue I guess:
https://forum.hise.audio/topic/14421/css-errors-for-every-component
-
CSS Errors for every componentposted in Scripting
Since the Jan 25th CSS updates, I'm seeing a large amount of CSS Error lines in the console when I load the plugin XML.
Interface:! CSS Error: can't find CSS for component btnIconPrev Interface: Use one of these CSS selectors to define a stylesheet for the base component: Interface: .scriptbutton Interface: #btnIconPrev Interface: button Interface: *One of these blocks for every component, plus the whole list repeats twice. So for my small plugin I see 442 lines of these errors when I load my plugin.
Is this expected?
-
RE: CSS changes on 25th Jan seem to have broken button spacing....posted in Bug Reports
@DanH Do you also see a large amount of CSS Error lines in the console with you load your plugin XML?
