• Coming over from Kontakt? Read this!

    Pinned
    8
    1 Votes
    8 Posts
    7k Views
    LindonL

    @d-healey said in Coming over from Kontakt? Read this!:

    @Lindon They live inside Kontakt's sample map too, it's just that with Kontakt there is only one sample map and it's part of the NKI.

    I think the main different between Kontakt's groups and HISE's is that with Kontakt you can route them individually and apply effects and other processing to them individually which you can't do in HISE (yet...?).

    In HISE the routing and modulation is at the sampler level rather than the group level.

    Absoloutely - valuable stuff to include - I guess I was thinking inside a group you see a mapping of sample audio files, inside a Sample Map you see....so (to start with) same same...as a starting point. But hey no problem.

  • AAX Build on MacOS

    22
    0 Votes
    22 Posts
    338 Views
    LindonL

    @ustk ok here is what I did:

    downloaded aax-sdk-2-6-1.zip unzipped it and got aax-sdk-2-6-1 folder copied this folder to HISE/tools/SDK/ opened SDK/aax-sdk-2-6-1/Libs/AAXLibrary/MacBuild/AAXLibrary.xcodeproj in xcode ran Product>Build For/Profiling. xcode tells me this was a success... renamed aax-sdk-2-6-1. to AAX in the HISE/SDK folder opened my project in HISE ran Export>Export As Instrument and selected AAX as my target....

    got this in the console window:

    ⚠️ ld: ignoring file '/Users/lindonparker/HISE/tools/SDK/AAX/Libs/Release/libAAXLibrary_libcpp.a[2](AAX_VDescriptionHost.o)': found architecture 'arm64', required architecture 'x86_64' Undefined symbols for architecture x86_64: "AAXStartup(IACFUnknown*)", referenced from: ❌ "AAXShutdown(IACFUnknown*)", referenced from: ❌ "AAXCanUnloadNow(IACFUnknown*)", referenced from: ❌ "AAXGetSDKVersion(unsigned long long*)", referenced from: ❌ "AAXRegisterPlugin(IACFUnknown*, IACFPluginDefinition**)", referenced from: ❌ "AAXGetClassFactory(IACFUnknown*, _acfUID const&, _acfUID const&, void**)", referenced from: ❌ "AAXRegisterComponent(IACFUnknown*, unsigned int, IACFComponentDefinition**)", referenced from: ❌ ld: symbol(s) not found for architecture x86_64 ❌ clang: error: linker command failed with exit code 1 (use -v to see invocation) [KeyEngine - AAX] Linking KeyEngine ** BUILD FAILED ** The following build commands failed: Ld /Volumes/Untitled/Nomad\ Sounds/KeyEngine/Binaries/Builds/MacOSX/build/KeyEngine.build/Release/KeyEngine\ -\ AAX.build/Objects-normal/x86_64/Binary/KeyEngine normal x86_64 (in target 'KeyEngine - AAX' from project 'KeyEngine') (1 failure) ⚠️ /Volumes/Untitled/Nomad Sounds/KeyEngine/Binaries/Builds/MacOSX/KeyEngine.xcodeproj: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.9, but the range of supported deployment target versions is 10.13 to 14.5.99. (in target 'KeyEngine - All' from project 'KeyEngine')

    so its something about this:

    found architecture 'arm64', required architecture 'x86_64'.

    for some reason its not set up to build properly on my M1 mac...

  • How To Fix this problem building HISE on MacOS

    8
    0 Votes
    8 Posts
    58 Views
    D

    @David-Healey Please check your dms for me

  • Oriental Drummer

    2
    4 Votes
    2 Posts
    62 Views
    Oli UllmannO

    @David-Healey
    Looks like they are selling Plug-Ins and knives. :-)

  • Channel Strip help

    2
    0 Votes
    2 Posts
    45 Views
    David HealeyD

    @pratitghosh move all the xml files into the new project and then compile the DLL there

  • Confused about set.Bypassed() and ChildSynth vs Sampler

    3
    0 Votes
    3 Posts
    44 Views
    ustkU

    @observantsound You can use both references at the same time. Just use the one that works for the bypass, and the other for your sampler job

    What I said might work, but do as @David-Healey said it's better implementation even if the reference are the same behind the scene 👍

  • 3 Votes
    1 Posts
    69 Views
    No one has replied
  • Disable frontend Macros on right click

    3
    0 Votes
    3 Posts
    60 Views
    David HealeyD

    I think you can probably do it using the MidiAutomationHandler: https://docs.hise.dev/scripting/scripting-api/midiautomationhandler/index.html

  • Apple team ID, code sign but ask for security to open the plugin

    36
    0 Votes
    36 Posts
    910 Views
    Y

    @David-Healey ok thank you

  • Thoughts on Moonbase?

    20
    0 Votes
    20 Posts
    842 Views
    J

    @JC Hey i actually got the moonbase module to work in juce 6..
    took David's advice and messed around with Claude and got it to work.

    little tricky for me but its working. I Havent shipped anything yet though--Hopefully soon.

  • Sample installer only extracts the first part on Intel Macs

    11
    0 Votes
    11 Posts
    149 Views
    J

    @jeffd

    So i got a notarized .pkg working of the .hr files. still need to test more but i got them into the plugin's own per-user app-data folder. Then when the plug-in opens and installs the samples it can also auto-delete the .hr files right after extracting. And no gatekeeper quarantine from macos. Ill have to do the same on pc and create .exe for the .hr files to match. but perhaps this will be best. less confusing for people i imagine?

  • Compiling VST files on Windows for macOS!!

    3
    0 Votes
    3 Posts
    60 Views
    David HealeyD

    @Oli-Ullmann Yes a vm is the way to go if you don't have a mac

  • Whitebox packages wont install multiple files (AU,vst,vst3).

    3
    0 Votes
    3 Posts
    44 Views
    Y

    @David-Healey payload is good.

    Oh ok, I didn't know. I do it right now.

  • compiled DSP network wont work after vst export

    3
    0 Votes
    3 Posts
    66 Views
    J

    @David-Healey Thank you. It compiled and worked just fine.

  • Show default preset name on first launch

    8
    0 Votes
    8 Posts
    226 Views
    ustkU

    @dannytaurus Oh nice one! 👍

  • Looking to hire a freelance dev for sample player build

    1
    0 Votes
    1 Posts
    52 Views
    No one has replied
  • New Release - RustEQ le bleu

    4
    9 Votes
    4 Posts
    170 Views
    DanHD

    @ustk very sexy!

  • I'm having trouble exporting my project in HISE.

    3
    0 Votes
    3 Posts
    93 Views
    E

    @ulrik Thanks for clarifying that detail, I was able to export my practice projects.

  • Automatic license file placement, like user presets

    11
    0 Votes
    11 Posts
    407 Views
    dannytaurusD

    @David-Healey No, because this is about persisting the file to the user's disk.

    Although as I said earlier, I think the final best answer is to display the license directly in the plugin somewhere.

    Then nobody could ever accuse the developer of not making the license easily available.

    Website goes down - no problem
    User moves the plugin to another machine - no problem
    User wipes/moves/modifies their AppData folder - no problem

    If the license is in the plugin itself, it can't be accidentally moved, deleted or overwritten, and it can't become unavailable because of server outage.

    Probably going this route now...

  • Couple of handy (free) Mac apps for checking code signs and notarisation

    8
    3 Votes
    8 Posts
    404 Views
    ustkU

    @Lindon Yup that's because it needs to be thought more as "container" rather than strictly "installer". PKG or ZIP are containers so -> notarisation

20

Online

2.4k

Users

13.8k

Topics

120.3k

Posts