@Onik-Sisodiya That code's quite hard to follow but I think you're only attaching to a mouse event there. You probably need to attach to the EQ events or possibly the context menu event.

https://docs.hise.dev/scripting/scripting-api/broadcaster/index.html#attachtoeqevents

@d-healey

This is very exciting news!

Another thing you can try is running your DAW (I recommend you use Reaper for testing) from within xcode or Visual Studio and see if you get any useful info there.

@BobCat you would use the new GlobalRoutingManager methods and send channel info for each note id, the do the routing in a scriptnode effect for that sampler, where you're taking the data for that node to direct the signal around the channel matrix.

However the receiving node in scriptnode is currently bugged as it doesn't react on 0, so we're waiting for the fix.

@treynterrio It is apparently possible to run XC14 under Sonoma:

HERE

I haven't tried it because I'm on Ventura but the comments in the thread seem to indicate that it works.

@bananaas007 said in Exporting:

Uninstall Xcode 15 and install the most up to date version of Xcode 14 from HERE

@diablo99 I tried using it but couldn't find a way to remove the closing X button, which then left my actual button in its on-state. It's far cleaner to set up a custom system with all your buttons in one array and your panels in another and then create a function containing (amongst other things)

panel.showControl(bool)

To show the active panel and hide the others. Obviously, if you wanted the option to have multiple panels open, you could code that.

@GUJIAN I'm not sure what to tell you, the code is there for you to modify how you like, but all the same rules apply as writing your own code from scratch. You can only assign one LAF object to a component, so you either need to remove the assignment that's in my code, or place your customisations within my LAF object.

@Matt_SF if I put my IR in the 'AudioFiles' folder in my project folder, the VST3 doesn't load the IR at all. If I use an IR from outside of that folder it works as long as the path of the file is maintained.

So somehow it's even worse?

@d-healey Thank you very much, I successfully referenced the font

@d-healey said in AudioLoopPlayer loading samples issues:

https://docs.hise.audio/working-with-hise/project-management/index.html

Thanks I am familiar with it, just been at the computer too long. Never hurts to brush up on it though.

@bananaas007 Not all heroes wear capes ;)

@d-healey Thank you David.
Samples only...

@clevername27 said in User-Facing Strings:

I'm interested in the ones I don't know about

I don't think there is a convenient way to locate them as they are not in a single file. Having them in a single location would be nice, and it would allow for HISE to be translated into other languages quite easily.

@Soundavid You star. Thank you so much for your help!

@Christoph-Hart as anticipated in the post: it was really stupid. Thank you for the time you have dedicated to me.

@d-healey On Mac, just a straight up library build with no adjustments works for me 👍

@modularsamples I haven't setup GitHub actions for this repo, but I'm using it for the HISE CI build, which does more or less the same (check out the repo and then run a script):

name: CI Build on: workflow_dispatch: push: branches: - develop jobs: ci_macos: runs-on: [self-hosted, macos] steps: - name: Cleanup working directory run: rm -rf "${{github.workspace}}" - name: Checkout HISE repository uses: actions/checkout@v1 with: ref: 'develop' - name: Build & Run CI script working-directory: ${{ github.workspace }}/tools/auto_build/ run: sh ./build_ci.sh ci_windows: runs-on: [self-hosted, windows] steps: - name: Cleanup working directory working-directory: ${{ github.workspace }} run: del *.* /Q /S shell: cmd - name: Checkout HISE repository uses: actions/checkout@v1 with: ref: 'develop' - name: Build HISE CI, run unit tests & export demo project working-directory: ${{ github.workspace }}/tools/auto_build/ run: build_ci.bat shell: cmd