Welcome!

This is the definitive landing page for our AudioUnit (AUv3) releases – exclusively – for Apple platforms. Our new releases are available as super universal apps for iOS, iPadOS, macOS and (recently) visionOS!

You are welcome.

  • JAX Essentials Series (ES) Squasher released
  • JAX ONE XModulator Extended released
  • JAX Essentials Series (ES) TubeFlavour released
  • JAX Selective Range [SR] : Flanger released
  • JAX ONE Delay Extended released
  • JAX Selective Range [SR] : Phaser released
  • JAX ONE Reverb Extended released
  • JAX Selective Range [SR] : Chorus released
  • JAX ONE : Frequency Shifter Extended released
  • JAX Dynamics : Flow released
  • JAX Triple Series [TS] : 3Verb released & updated
  • JAX Triple Series [TS] : 3Stereo released & updated
  • JAX MIDI Control Pad released & updated!
  • JAX Selective Range [SR] : Reductor released & updated

Cubase Patch Map for Roland Jupiter X/Xm

We did not find one elsewhere.

The Jupiter X / Xm is a nice hardware synthesizer, which is 5 channel multi-timbre and has included sets of thousands of factory voices. These patches must be selected with some cryptic MSB/LSB bank select commands.

We created a clickable patch map for Steinberg Cubase, that at least enables to select presets from the various banks in the Jupiter X / Xm for all channels. (Channel 5 is reserved by Roland for the drum sets, which are mapped too.)

All documented internal banks are mapped with correct MSB/LSB patch change commands but the names are generic (yet?) and not the real names from the Jupiter’s memory. Putting in thousands of patch names into a Cubase patch map editor is a nightmare. (Apple’s Logic Pro allows for instance easy import of lists for such and this is time consuming too but doable with some effort.) If someone finds the time to edit 5000++ patch names for Cubase manually, line by line, taken from the Roland docs, this would be awesome, but our basic goal (multi channel patch selection) is done with the current patch map.

We also mapped the scene patches, which should be sent on a MIDI channel other than 1 to 5 (reserved for the parts), i.e. MIDI channel 16. Different to the documentation, the scene patches are not organized in special small virtual banks but according to Rolands MIDI implementation chart in 4 extra banks a 128 patches with their own MSB/LSB bank select commands. Not supported are the waveform IDs from the doc, as these are not even useful nor selectable via MIDI commands.

The Jupiter X / Xm is a multi emulation device, which even features for instance nearly thousand of JX-5080 voices alone, alongside with loads of banks of their classic virtual analog emulations and also a large ‘common’ tone bank with all the production basics. All these patches are organized in several banks inside the memory (ROM) of the synthesizer. Also user bank tones can be selected this way. Total access to the available voices from the Cubase production environment becomes quite easy now.

There is a basic video, how it works on our youtube channel:

All the sound comes from the Roland Jupiter Xm external hardware synthesizer, controlled by MIDI.

The Cubase (version 13) patch map can be downloaded below. You can import the device map into Cubase after unzipping the file to your hard disk. The file is in XML format and is editable and widely extendable with Cubase afterwards.

There is a useful formula for calculating the strange Cubase 14 byte numbers for the bank select command: Just do : (128 * MSB number) + LSB number : from Roland’s documentation above. ^^ Alternatively the bank select commands in correct order could be done separately too. (This is merely of a meaning if you want to extend the patch map yourself.)

JAX Stereo Tool (Legacy) updated

Initially we wanted to remove our JAX Stereo Tool in favor of the new JAX 3Stereo, where it is integrated. Some users did want to keep the classic tool (one of our first releases). So we updated the old code for latest frameworks and devices and re-adjusted the price.

Users of our JAX 3Stereo do not need the legacy JAX Stereo Tool. Because 3Stereo implements the same tool in its all-pass mode.

Price Drop Mania and its Supporters

Recently a very popular app tracker site announced their shutdown. Most likely for financial reasons and missing support from Apple.

We find this is a logical consequence to the current, still raising situation.

Especially niche businesses are suffering from the current trend of overdriven price drop mania. It is a bad trend and some developers do then react with virtualised “normal” prices – this is raising the prices in general – as they otherwise could not keep their cost compensation for the app development. Because now they are forced to continuously drop prices and making one sales action after another, which short or long term, will result in a financial disaster.

I am wondering, why Apple even allows apps in their own AppStore, which obviously perform a kind of “smart developer punishment” by flagging raised prices in red (bad prices) normal prices in orange and dropped in green (good prices). So only dropped prices are green (and thus good). This is very consumer centric and also manipulating on the one side and potentially business damaging on the other side, the developers side – and also negative for Apple.

Nobody is raising prices for fun.

A price increase judgement or punishment of any sort is basically against Apples rules and the existing sales conditions and contracts. Developers are totally free to adjust their prices to the requirements and nobody, especially a 3rd party should not be allowed to perform any judgement or even punishment on that matter.

Also no developer is forced to do a price drop ever.

Developers have a strong contract with Apple. A third party cannot expect that Apple cooperates with them, if they perform continuously business-damaging promotional actions based on Apples own AppStore data, which is usually grabbed by just hijacking (stealing) their officially available and published data.

So for instance some of such 3rd party providers have insufficient and obviously incomplete data sets, actually hindering especially small developers to even appear there with their full set of releases (as happened with us : 9 of our releases were just not even in the 3rd party app’s database and thus, out of any access by the users of this app).

And some people, who see themself as kind of “influencers” or self proclaimed promoters obviously are thinking, they easily could (mis)use such platforms for playing God and for instance hindering selected developers to appear by promoting just everything but those.

There are several dangers with such app trackers, dangers of potential manipulation; and we would rather like to support Apple, as we have clear contracts with them. We also never have seen something similar discriminating from Apple. And if Apple chooses not supporting such providers and even removing their misused services from access this way or even removing such questionable app-tracker apps from their AppStore, we are absolutely with them.