Topics created by Lindon

@d-healey - no let me start with the documentation and I'l call if I'm drowning...

@ustk sadly they are not.

@Lindon bump bump???

@Christoph-Hart Any news on this side? I mean, I know codegen does not keep you that busy...

There's also a button in the custom settings panel to clear all MIDI learn assignments.

@d-healey I read too fast, I thought I read time streching ^^

@Lindon I hope you are right.

@orange said in AAX Compiles...: While compiling as "All platforms", have you selected VST3 or VST2? If I select VST2, "All platforms" work. but if I select VST3, "it doesn't work. I think it is because AAX plugins use .dll (VST2) platforms inside. err , not here they don't - the AAX compiles a VST3 and the uses that...unless I'm very much mistaken(which is a distinct possibility..)

@Lindon aaaand..in classic mode I think I found it as soon as I posted this: FrontendBar.cpp (line 57) addAndMakeVisible(installSampleButton = new TextButton("Install Samples")); addAndMakeVisible(ignoreButton = new TextButton("Ignore")); resolveLicenseButton->setLookAndFeel(alaf);

@Lindon Lindon Check The Font Size, ( If You have Custom Ones) I Faced with the same Issue Last week, With an almost Empty Project. And found out the Fonts Were Too big, Like 6 M.b And 10 styles. So Easily Jumped into The 90 M.b In Dll Size.

@Lindon yes I know no one has come to understand this thing with logic. but I will try to put a single capital letter

@Christoph-Hart I just wanted to ask if this is now a part of the HISE build or if I still should call...? const var th = Engine.createTransportHandler(); inline function onStop(isPlaying) { if(!isPlaying) Engine.allNotesOff(); }; th.setOnTransportChange(true, onStop);

Do you experience that with a barebone example (just the arp in the main container and a sine wave generator?) I played with it for a few minutes now and everything is fine with the HOLD button on my end.

@Christoph-Hart Ok --waiting, waiting...:-)

@Christoph-Hart - OK thanks.

@orange Nope, it's just for sending a message to plugins saying "please change tune now". It's up to the plugin to change the tuning.

Other than playing each key I can't think of a way to verify that it's loaded correctly from with the plugin. There are some functions to check if keys have samples mapped but I don't think that would help. You might be able to do it by building a standalone build in xcode with debugging symbols enabled and that might show in the output as each sample is loaded...

@Lindon I haven't had any issues using the AppData folder both for development in HISE and in the compiled plugin. It's actually nice because you don't have two sets of the same files. For example, in my code I create and store a custom settings file in the AppData folder, so when I'm developing in HISE it just writes to the same file as the compiled plugin, which is totally fine. Is there a specific use-case you want for saving things to the Project Folder instead of the AppData folder?

@Lindon The good news is that you save us from embarrassing ourselves

@Lindon - ok well deleting everything in the Build folder seems to fix it...