HISE Logo Forum
    • Categories
    • Register
    • Login

    Question about AAX and License with Hise!

    Scheduled Pinned Locked Moved General Questions
    2 Posts 2 Posters 853 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • alexaudio10A
      alexaudio10
      last edited by

      Hello,

      I have some questions. In fact, I am finishing (within 6 to 8 months) a project that will be available for sale.

      I wanted to export under mac.

      My first question is, do I absolutely need a mac to export it to "AAX" ...?

      If so, would a mac mini do the trick? I know a lot about computers but I do not know anything about mac? I imagine there are people working under mac who could tell me more? I wish I did not have to buy one soon.

      Last question, how does it work for the license with Hise? Do I have to pay a commission to Hise's devellopeur or is there something else?

      1 Reply Last reply Reply Quote 0
      • Christoph HartC
        Christoph Hart
        last edited by

        I think your confusing AU with AAX.

        AU is Apple's native plugin format for Logic, Garageband etc (although VST is also supported on OSX). AAX is the plugin standard for ProTools and is available on both OS (Windows and macOS).

        And yes, you definitely need a Apple system to compile AU plugins (and AAX plugins for ProTools on macOS). A mac mini will be just fine as long as it has an Intel CPU (you can't compile Universal Binaries on PowerPC CPUs). I am myself using one as main system (I am running Bootcamp for Windows so I have both OS on the same machine).

        In order to compile AAX plugins, you need to register at Avid, compile their SDK, get a iLok, register at PACE for a code-signing account, get a digital codesigning certificate for Windows from Comodo (or another company), build the AAX versions and sign them using their codesign utility which I can tell you is a very tedious and annoying procedure.

        RE Commercial license, I am cooperating with a few companies that are building commercial plugins, where I offer my support during development and after release. If you want to discuss the specifics, drop me an PM.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post

        19

        Online

        1.7k

        Users

        11.8k

        Topics

        102.7k

        Posts