@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

@nesta99 on my side I always have to change it manually inside the xml because it's never remembering it from the preferences window

@d-healey Thank you sir ! 🙌

@christoph-hart Wow! Great feature, I will start to work with it right now. Thank you!

You can make an entirely custom tool tip panel, I posted a video about this on patreon a few weeks ago.

@christoph-hart Awesome ok! so all effects will be compiled into the one DLL.

Thanks @Christoph-Hart

@lindon As you see, I never talked anything about Gaurav or never talk any bad things about him.

I started by asking who did this Hise project of Beatskillz. I am curious because I like their products. And I think he is a very very successful and talented guy. I appreciate thier stuff.

So I agree, no racism, no personal things or gossips. It should be forbidden here 👍

@d-healey Yes.. I forgot the recent stuff.
Thank you.

In case anyone has the same question in the future, I'll leave the settings I used to capture a nice plate yesterday that seems to have given good results. At least in Reaper's ReaVerb.

I recorded at 96k/24bit and used a 10 sec sweep. The gain staging took some finessing.

@ustk j ai essayé de contoller une fréquence avec un label et j'ai mis par exmeple 6568.76. il l a bien validé mais je voulais savoir si il enregistrait cette valeur sur l eq ou si il arrondissait. donc cool je peux me lancer dans un truc encore bien relou ^^ merci