@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

@d-healey Thanks for confirming. i will go a different route.

@ustk

Understood.

I'll re-compile HISE today.

I appreciate the information.

Thank you!

@d-healey This works!!! The J pulls up the code and it can be copied to other buttons. across projects to. The only note is it will duplicate your position as well so it newly copied knob will be on top of the original (if your looking fot it, LOL) . so change that before hitting apply or drag the dupe away. Thank you!!! Thank you for your help and feedback!!!

Thanks @d-healey

@KashKash 2022 is the one to go with - also there are instructions on the HISE github page.

@Lindon yes

@ulrik Ok, my progress in finding a way to communicate midi to Effect plugins inside Logic and Ableton Live :

Using an extra plugin that send OSC messages to the Effect plugin seems to work quite nice, all I need for this plugin is to trigger the TransportHandler with note on and off messages.

In Logic the extra plugin (Send OSC) goes into the Midi FX Slot on the same track as the Effect plugin
In Live I need to set up an extra track with midi in enabled all the time (even if another track is selected)

osc send.gif

@d-healey This was the issue, changed the size of the knob before making the filmstrip and this solved it, thanks!

@LozPetts Working smoothly here. Try adjusting the skew factor, middle position, and mouse sensitivity

@d-healey Thank you. So a Fork isn't a living, breathing thing - it's just a snapshot of a repository. If I want the fork to inherit changes from the source, I need to ink them. As I understand, I can simply click the "Synch Fork" button to manually do that. (Or, as you suggest, I could connect it so this happens automatically.).

@d-healey No, I don't know what the situation is

@Christoph-Hart said in Convert complex SVG in HISE:

The SVG must be a single shape.

You can combine multiple shapes within the path converter. You have to paste them in one after another.

0a109a66-3ab2-4d92-8e49-c607920989ae-image.png

<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Created with Inkscape (http://www.inkscape.org/) --> <svg width="1000" height="1000" viewBox="0 0 264.58333 264.58334" version="1.1" id="svg5" inkscape:version="1.2.2 (b0a8486541, 2022-12-01)" sodipodi:docname="test.svg" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg"> <sodipodi:namedview id="namedview7" pagecolor="#ffffff" bordercolor="#666666" borderopacity="1.0" inkscape:pageshadow="2" inkscape:pageopacity="0.0" inkscape:pagecheckerboard="0" inkscape:document-units="px" showgrid="false" units="px" inkscape:showpageshadow="false" inkscape:zoom="0.69397447" inkscape:cx="359.52331" inkscape:cy="530.99936" inkscape:current-layer="layer1" inkscape:deskcolor="#d1d1d1" /> <defs id="defs2" /> <g inkscape:label="Layer 1" inkscape:groupmode="layer" id="layer1"> <path id="rect231" style="opacity:1;fill:#957f77;stroke-width:2.64583;stroke-linecap:round;stroke-linejoin:bevel;stop-color:#000000" d="m 55.765279,57.537357 h 63.757831 c 1.17263,0 2.11667,0.944034 2.11667,2.116667 v 22.488307 c 0,1.172633 -0.94404,2.116666 -2.11667,2.116666 H 55.765279 c -1.172633,0 -2.116666,-0.944033 -2.116666,-2.116666 V 59.654024 c 0,-1.172633 0.944033,-2.116667 2.116666,-2.116667 z" /> <path id="rect233" style="opacity:1;fill:#800000;stroke-width:2.64583;stroke-linecap:round;stroke-linejoin:bevel;stop-color:#000000" d="m 117.36963,118.56291 h 73.29874 c 1.17263,0 2.11666,0.94404 2.11666,2.11667 v 23.70573 c 0,1.17263 -0.94403,2.11667 -2.11666,2.11667 h -73.29874 c -1.17263,0 -2.11666,-0.94404 -2.11666,-2.11667 v -23.70573 c 0,-1.17263 0.94403,-2.11667 2.11666,-2.11667 z" /> </g> </svg>

@beatsthatpound you should choose export instrument, not fx.