@crd This is how I'd handle it

HiseSnippet 1069.3oc6VEtiaSDDdcRVD1.EpfG.S9kiTHxobWAoSU8ZxcGJpb2EQJmPBgp1rdykUYytV1qaaJ59GOC7BvKB+qOE8G8MnuAvrqcpsuKsDhn+iHcm7Ny7M9alclwy3DEkklpRPNtOZULC47w3Iqj54CmS3RzniPN2BK3xEb4kKjpoonAqhIoorHjiSyuyXiiaKj82qu+.hfHorRQHzEJNk887kbcozwG9PtPbBIh8H9xJVu2ginJ4PkPkA7oINDESnKHWxNiXLqAF47AGGw0pjIZhlkhbZMPEsZxb0Sk41eAOkOUvLG5il.NJW7IJQjgwFongy4hnwqi6TD3kwkYgl4Ygu.eJOh+F4kYiOypvuDQ07gSi5zqYM50uJ8BqPuMPoFUnTqbJca7DZBOVWpwvmOBORpYIyHPZuJUxsE03SahGp.Kj5dKIKXmj.GdChf6FF10G9WmC7.qRUBVOpfQRB.AdvcQp1+IjD+q8h66eOeaQRuKY5Z4of14lVle52ttqVHmlBv+40jhDE8PntJnsRxZ2MraXmtdtvOe+aXg9oJiE6G14Wp4RS44.sD7ZEHCxzZkLncgx1c86uODq6YBUuYpD+.pOWZoSGOWZuTl1fNQIFRDhoPcWfRZzVHEf454wkf+X9yxjTMWI8qYR.UsLFBCotKvKQFqi2u54JTTh.dUQrmALzXdO6gymUZu04tVVsnBq.zt7YFYe487KMFjZzXUUDdlKhKLuxfNF045cWXhpbw474fBwz4D4krnfbAW4k+GSjxLmu9sswKOPqS3SyzrfanEH653Eb2UdWAIXuJYnyTZ14x.axv6JO+qqZ1rMpqHoJXIaTsYxQx6BXfLa4TVR0qBigP6T8dT7auGs5HDZdoUECUxQRt97Xl7sMXAUTOB8yMKXE7j11Meqht4IBdDKAwglVLFteQV5VLS7O+i3WdezVAEZN9W.Mu6vB0EWTCUCtcbN5GGcDQS.56TDIPzEyRzbShy4H1SfY64CmbwGwRWnUw1PsnRE30+Pv9L3AGyKa05GR0r3I7mulGG9pm+alvXq7nIGT2i2YK7XqsH0X85uu1qA1OhskCn+b7MFItoA0Nu.WaHY8oY4C.Aw4iHOv++6up2e4rUMIPBbCMI6TUtyVVSZdkaYU9MqnfkMTQYBht9FHl0tJT.WI0plLeZWlx0qp1G+e1ZIaKEuMdLWSmuYN1XCbzrwy6ANVrL2mfOd1LFUWRvV3S9o2Oatg9AUlFVV9TB7ASyE+YYKm.6yRYvaWJguwZpAZXJdyOGttlXBSFYO7WvuBk8MmcJT1esRzRBMQ8XZdIuYcwOzJA3jztorK9TyY+9qq1w3vdgnkvpZOlRMg+WA8SaFyc1ALe8NfYuc.y96.l6tCX9lc.y29NwX1R9AYZ0x71APv3isScbbNVRfJKaUH5uA1oYwCC

@lindon I just finished an instrument that has 10. no problem. I think there's no reason why it shouldn't work for 64. even if it still seems super big ^^

Thank you everybody for your advice

@d-healey Ok, thanks!

Okay reporting back (let me know if any of this is wrong...):

So some clarification - if its needed - here we are talking about Audio Files: that's the contents of the Audio Files folder in your project not the samples used in a Sampler, but the wav files used in Audio Loop Player or the Convolution reverb....

So if your number of Audio Files is so large that it will break the Visual Studio compiler - with the "out of heap space" error - then you will need to ship your Audio Files in a separate (external) resources file...

-- First make sure you have all the required wav files in the Audio Files folder:

-- Put this at the top of your script:

Engine.loadAudioFilesIntoPool();

-- Select: <Export Pooled Files for Binary Resource> from the <Export> Menu...

This will create a new folder in your Project called PooledResources

In this folder will be the following files:

AudioResources.dat
ImageResources.dat
MidiFiles.dat
SampleMaps.dat

(yeah it exports all the different types of media - dont worry you dont have use all of them)

-- in your Project Preferences make sure Embed Audio Files is unchecked

-- compile your project.....

Now you have a product that will look for Audio Files in the following location (it will report an error on start up if it cant find this):

{AppData}/<your company name>/<your product name>/AudioResources.dat

-- so you need your installer to make this folder if its not already there, and copy the AudioResources.dat file into this folder

@ulrik You're the man! Much appreciated!

@yall Glad to Help👋

@parabuh Excellent, I'll add it to the pull request :)

Anecdotally, the Arturia controllers feel better to me in terms of build quality. Granted I haven't owned an M-Audio controller in well over a decade, so take that with a grain of salt.

In terms of what the knobs and pads are for, you'd be able to assign those to parameters of the Slim Phatty using the appropriate midi CC#s (here's a forum post where a user mapped them out). So you'd be able to assign one of the knobs to the filter cutoff for example, and one of the pads to switch the octave of oscillator #1, etc. Possibly useful if the Phatty is racked and you don't want to walk over to it while making a patch, or if you want to manipulate parameters while playing live.

As far as I can tell, you're not really shopping for a feature set beyond what any standard MIDI controller would offer, so you're likely safe buying any well-built controller until your needs change. You might be able to get away with something even more basic without extra knobs/pads like an Arturia Keystep. I'd suggest heading over to your local instrument shop and demoing a few controllers and see if something like the width of the keys, build quality, etc. matter to you. Good luck!

It occurred to me people might want the best of both worlds, so I went with a different option and added a property called ButtonsInsideBorder if this is set to true you get the new appearance, if it's set to false (or omitted as will be the case for older projects) you get the old appearance.

By default the property is false so when adding a new preset browser you will get the old appearance. I've also set the default of the EditButtonOffset property to 10.

If this sounds good to you guys I'll make a pull request.

With this new setting you can do things like this:

c6d90267-8163-4999-a7c3-bea6400d462f-image.png

@d-healey Thank you so much, David, as usual!! I managed to solve this

@ustk Sure thing!

Anecdotally, all multimedia gear, audio cables, etc. are sold by the foot in this country. So that's likely the unit that your end user is expecting. The only thing we buy by the yard is fabric, haha.

Edit: Feet with a decimal point is likely the best option here until you're to measurements that are less than 1 foot. Sub-foot measurements should be in inches with a decimal point. Not ideal considering how all of our measurement devices are marked, but your average consumer would know how to navigate this. Ideally in sub-foot measurements, you round your inches to the nearest 1/16" unless that level of inaccuracy breaks functionality.

Found some useful info to retain attributes for AAX in Inno
https://www.kvraudio.com/forum/viewtopic.php?t=489036

Yes, you have to be careful when "recreating" the AAX. It's all about flags. Definitely works. We do this: [Dirs] Name: "{code:GetAAXDir_64}\{#MyBinaryName}.aaxplugin"; Check: Is64BitInstallMode; Components:aax_64; Attribs: system; [Files] ; AAX Source: "{#MyBinaryName}.aaxplugin\*"; DestDir: "{code:GetAAXDir_64}\{#MyBinaryName}.aaxplugin"; Flags:ignoreversion createallsubdirs recursesubdirs; Check: Is64BitInstallMode; Components:aax_64; Source: "{#MyBinaryName}.aaxplugin\desktop.ini"; DestDir: "{code:GetAAXDir_64}\{#MyBinaryName}.aaxplugin"; Flags:ignoreversion; Attribs: hidden system; Check: Is64BitInstallMode; Components:aax_64; Source: "{#MyBinaryName}.aaxplugin\PlugIn.ico"; DestDir: "{code:GetAAXDir_64}\{#MyBinaryName}.aaxplugin"; Flags:ignoreversion; Attribs: hidden system; Check: Is64BitInstallMode; Components:aax_64;

@dustbro I think if that was the case the error wouldn't be on line in the script containing the namespace.

grosssssss

i wonder if other DAWs will follow

@d-healey Thanks!

@yall https://docs.hise.audio/scripting/scripting-api/transporthandler/index.html

setOnTransportChange should work for this