Xhun Audio LittleOne : version 4.x Released

[xhunaudio]

Hi, as described here :

https://www.xhun-audio.com/site/xhun.php?page=support

On most recent versions of macOS, there's a thing happening :

instead of the proper "~/Library/" path, the system wants certain plugins installed under the "/Library/" in order to be visible to a Host.

Try "Library/Audio/Plug-Ins/Components/" instead of "~/Library/Audio/Plug-Ins/Components/".

[xhunaudio]

LittleOne version 4.x preview image : the new synthesizer panel GUI.

[Aloysius]

Very blurred. Tiny text, buttons, dials. Difficult to read.

[xhunaudio]

Just before being published, the image above has been pre-processed adding light glow shading and desaturation.

...because it's a "sneak-preview"

[steb_osc]

LittleOne version 4.x preview image : the new synthesizer panel GUI.

It looks great! I can't wait

[kylie]

Looks great so far.
Will a parameter change by any GUI element be reflected in the display, at least for a while?

Release Party is excatly when?

[xhunaudio]

Knobs are fully analogue, so you'll have to turn them up and turn them down until you'll get THE sound

Release party? Very soon. There *could* be a potential delay of 1 or 2 weeks so I'd prefer not to mention the exact day for now, until I'm sure any delay is avoided.

[JerGoertz]

Looking forward to more technical information. Any updates to the sound engine or features/functionality? (Not saying that this was needed, it already sounds really good.)

[sacer]

Yes it is natively backward compatible.

Anyway, for a possible missing compatibility scenario (the worst case, it should never happen), it is sufficient to :

- load your old project using LittleOne version 3.x
- for each instance of LittleOne version 3.x, manually save each of the "states" of the plugin (= simply press the SAVE preset button)
- close the Host, remove LittleOne version 3.x and install LittleOne version 4.x
- reload your project (now using LittleOne version 4.x) and if necessary, for each instance, load the corresponding presets you saved before

This will force into a 100% compatibility, if that is not achieved automatically.

hope you can bring V4 to work that it still open the used preset from V3 in a project. I have used littleOne in so many projects

[steb_osc]

hope you can bring V4 to work that it still open the used preset from V3 in a project. I have used littleOne in so many projects

I think in your case you’d just have both v3 and v4 installed. If you then want to swap over to v4 for some cases, you can then follow the steps. No point in running stuff in v4 for the sake of it.

[xhunaudio]

Looking forward to more technical information. Any updates to the sound engine or features/functionality? (Not saying that this was needed, it already sounds really good.)

Hi Jeremiah,

yes LittleOne version 4.x brings improvements in 3 main areas.

1-
On the GUI side, there's the new synth panel mentioned above. Also, there's a minor GUI overhaul for the rack too.

2-
On the DSP side there's an important accuracy improvement.

3-
And there's also a new rack unit, affecting the sequencer and trancegate effect.

I'll talk about the last two in the next few days.

[masterhiggins]

Hi, as described here :

https://www.xhun-audio.com/site/xhun.php?page=support

On most recent versions of macOS, there's a thing happening :

instead of the proper "~/Library/" path, the system wants certain plugins installed under the "/Library/" in order to be visible to a Host.

Try "Library/Audio/Plug-Ins/Components/" instead of "~/Library/Audio/Plug-Ins/Components/".

Hi there. I did that, rescanned all of my AUs, and restarted and they're still not showing under any of my AU hosts (Logic, MainStage, HostingAU).

[xhunaudio]

PS : There's also the Gatekeeper thing...

At today, many users are running LittleOne (and any other XA software) on latest macOS with M1 and Rosetta 2.

LittleOne didn't break compatibility with macOS. It is fully compatible with the plugin model Apple adopted for 2 decades.

From a general viewpoint, from a couple of years Apple (legitimately) decided to break compatibility with existing macOS softwares, introducing new and new incompatibilities and obtrusive requirements on a daily basis.

Apple is fully legitimate in doing what it does, my duty is not to blindly adhere. In addition, my opinion is that an OS should have to be JUST solid and transparent, period - not a way to change the rules every 12 hours. And sadly, this rarely happens today.

LittleOne and any other XA software come "as is". As a small developer and as always happened in the past, I'm happy to continue to give my support and help to customers for what is in my human possibilities, but I can't accomplish the *impossible* task of upgrading my IDE once a week.

My suggestion is to always try the demo before purchase. If the demo works fine, the full version will work fine too, 100% guarranteed.

Said that, we are about to enter a very exciting period for computer science, and in the medium-run the "pre-compiled audio plugin" concept could be replaced with something different. And AU/VST2/VST3/... differences could just belong to the past.

Let's see!

[masterhiggins]

PS : There's also the Gatekeeper thing...

At today, many users are running LittleOne (and any other XA software) on latest macOS with M1 and Rosetta 2.

LittleOne didn't break compatibility with macOS. It is fully compatible with the plugin model Apple adopted for 2 decades.

From a general viewpoint, from a couple of years Apple (legitimately) decided to break compatibility with existing macOS softwares, introducing new and new incompatibilities and obtrusive requirements on a daily basis.

Apple is fully legitimate in doing what it does, my duty is not to blindly adhere. In addition, my opinion is that an OS should have to be JUST solid and transparent, period - not a way to change the rules every 12 hours. And sadly, this rarely happens today.

LittleOne and any other XA software come "as is". As a small developer and as always happened in the past, I'm happy to continue to give my support and help to customers for what is in my human possibilities, but I can't accomplish the *impossible* task of upgrading my IDE once a week.

My suggestion is to always try the demo before purchase. If the demo works fine, the full version will work fine too, 100% guarranteed.

Said that, we are about to enter a very exciting period for computer science, and in the medium-run the "pre-compiled audio plugin" concept could be replaced with something different. And AU/VST2/VST3/... differences could just belong to the past.

Let's see!

That’s all fine. When I demoed it on my Intel Mac it worked fine. Now as I’m on M1/Rosetta it’s not working, and I can’t resell my licenses. So at this point I’m stuck with a license I can’t use. Awesome.

[Goony]

Works fine on my M1...