@d-healey said in What format do you use to distribute plugins+samples?: You could deliver a zip contains the HLAC samples (don't use raw audio as it uses more disk space for no gain and HISE sample maps seems to get confused by it). I got an instrument that is already in use and uses .wav, I am just adding another way to play it. So multi-format is the way I am going to deliver it, which makes .wav the only option (or .aiff / pcm), for me. After all, delivering an instrument that is around 5GB plus on top of another format a user may already be using in mixes is a waste of hdd space, and web traffic / online storage for me. But for a new un-released instrument, it´s the best option. If there is an issue with sample-maps and the raw audio files the only option is to solve that issue instead, cause that really makes me worried. (if that´s a bug, I sincerely hope it´s high on the list) But an hr archive is the same as a zip, just specialised for HISE and the extraction tool is already built into your plugin. Excellent. I will have to tinker a bit with that. If it can deliver raw audio files.

@d-healey said in Linux standalone instrument application and settings folder locations: /home/.config is a folder. . on GNU/Linux means the folder is a hidden folder. The default vst folder is /home/.vst or /home/.vst3/ and LV2 plugins go in/home/.lv2`. I'm pretty sure most users are familiar with this. Windows and (especially) MacOS like to tell users what to do, GNU/Linux is a little more flexible generally, depending on the distro and desktop environment. Okay, that´s a big part of why a lot of people choose Linux instead of the others. That´s a part of the platform and most experienced users or intermediate will handle that fine. The obviousness/strictness of a mac is a big part of why an answer can be found almost anywhere. And having rules for it is a big part of a platform. Nevertheless, freedom is in the whole Linux air. To be respected. You can download an installer I created here to try it out. Will do! Thanks a lot for the info. This info should really go in the docs. The paths on Linux is an essential part of docs. One fine day. Perhaps I´ll get there first, you never know.

@Lindon said in Standalone app icon: @andioak -- no don't do this. Inserting your own icons in a mac build will cause it to fail to notarize (well that's my experience anyway,,). Aha, thanks for that caveat! So if i´m deadly serious about rez-snaz I gotta go into the hise source and add some if:s. Not sure that the amazing feeling seeing my logo in 8k instead of 4k is worth that atm. But one fine day, it shall shine.

I am a musician and i try to keep as a broader spectrum of listening to music materials as possible, but my favs are jazz, orchestral and contemporary classics and some of the stuff in electronic genres. Living in a quite poor country which has many problems especialy in arts and education made me think about building instruments and tools that are free and open source and available to anyone. HISE seemed to be a perfect platform for this especialy since i have none of programming background or knowledge.. Some of the instruments i'm building and developing are at musictop69.wixsite.com/orchestools and these two videos bellow are demo/teaser of the instrument i'm building right now for a FREE PUBLIC ORCHESTRA idea i'm trying to develop!

@dustbro thank you , but it look like my filmstrip doesn't have middle

@SampleScience from "WE transfert" or gmail directly.

@d-healey Thanks for the verification!

Just reviving this old discussion as I'm trying to think of how user presets might be updated when rolling out updates to a plugin. Example Version 1.0 of a plugin has a total of 10 presets Version 2.0 of a plugin has a total of 19 presets (9 of which are new) What's the best way to add the 9 new presets to the plugins 'Preset Folder'? If doing this on installation is still the only way, what installers are people using to achieve this? I've found that InstallForge is limited as it doesn't allow the creation of an installation exe that can install files to mulitple folder destinations. This is a requirement as the installer will need to: A. Install plugin vst/component to plugin directory B. Install the new presets to the presets folder Any thoughts? I'm thinking about how this might done on Windows and Mac. Cheers

@Christoph-Hart Sorry I just forgot to replace it with a string... but I'm sure after testing different config with unmerged and merged time API that it doesn't come from that. Just try this string instead "2020-12-01T14:02:45" (it crashes with the string in unmerged time API Hise)

I've fixed a few things in the autocomplete. Unfortunately the module constants is a bit harder to fix, but at least Console.print shows up after you type pri... I rewrote the entire autocomplete system to use the same API for SNEX and HiseScript as there was too much hardcoded stuff particular to HiseScript, but it seems some things broke during the transition. You can try and assemble a list of issues you noticed here, then I'll try to go through them when I find the time - it's obviously not the most high priority task though...

@D-Williams23 put a simple gain after the filter...

@d-healey Perfect! Just didn´t see any replies here for it in any earlier messages.

@Natanr https://en.wikipedia.org/wiki/Regular_expression

@DanH i'll check in a moment because now i just copy assets and code to fresh project on windows

@d-healey No more git to sync/update between machines...

@d-healey Yeeeeei!!! Supreme

@Christoph-Hart I was able to build a plugin on with a newer commit, but I still wasnt able to export midi using: MIDIPlayer.saveAsMidiFile("{PROJECT_FOLDER}FileMIDI.mid", 0); I'm I coding it incorrectly, or is this not possible yet on a compiled plugin?

@Lindon The issue seems to be with the samplemaps, I have 304 (yikes) the older commits or fine, just the newer ones. @d-healey I'll the debug today to see if it'll shed some light and possible same me some time.

@Christoph-Hart Wow , Thank you. I will add this to my project now ,

@DanH Yes it is weird... Apparently, it comes from the release and retrigger combo. If you put the release at zero it's kind of better, but set it above and the retrigger makes a weird click noise... @Christoph-Hart ?