Xhun Audio LittleOne : version 4.x Released

[muswellhillbilly]

I mentioned this to him a couple of years ago now, but for some reason he doesn't seem to agree that it's important. I'm still on the previous version and won't upgrade until this is fixed. Obviously it still isn't.

Might I add that because of the preset browsing problems highlighted here I've not even opened it for ages, which is a shame because it sounds great.

Which version is the last one which worked? I had 1 or 2 older versions and there was this issue already. Is it possible to get to older version?
Thx

[dermage]

I'm currently demoing this, and the GUI is really too small on 1x on my 1080p monitor.
2x is too big and only suitable for 4k displays.

Please either implement a free resizing or a 1.5x size model.

[wltchris101]

I mentioned this to him a couple of years ago now, but for some reason he doesn't seem to agree that it's important. I'm still on the previous version and won't upgrade until this is fixed. Obviously it still isn't.

Might I add that because of the preset browsing problems highlighted here I've not even opened it for ages, which is a shame because it sounds great.

Which version is the last one which worked? I had 1 or 2 older versions and there was this issue already. Is it possible to get to older version?
Thx

But that's just it - I'm on the previous version and this problem has always been there for me. I'm not sure if there is a version that has a perfectly working preset browser - at least not in my experience (Windows 10, Studio One 4).

[wltchris101]

I'm currently demoing this, and the GUI is really too small on 1x on my 1080p monitor.
2x is too big and only suitable for 4k displays.

Please either implement a free resizing or a 1.5x size model.

+1

Another often asked request I think.

[xhunaudio]

Hi,

exactly, advancing the presets with the arrows generally works fine, but on some Hosts could have a strange behaviour : it advances +2 presets instead of +1.

Yes, this could be annoying but, considering that is linked to some low-level sub-routines of the framework I use (based on WDL-OL), I prefer to take time to study the thing and (eventually) switch to a different framework - instead of a modification of the existing one, causing potential breaks in the future.

So it is a bug which don't cause BIG problems when it happens (with numerous DAWs the bug do not exist at all) but I don't fix it not because I'm particularly evil, but because it is better not to mess with low-level logics since sometimes the "cure" could be more dangerous than the potential "disease".

[wltchris101]

Hi,

exactly, advancing the presets with the arrows generally works fine, but on some Hosts could have a strange behaviour : it advances +2 presets instead of +1.

Yes, this could be annoying but, considering that is linked to some low-level sub-routines of the framework I use (based on WDL-OL), I prefer to take time to study the thing and (eventually) switch to a different framework - instead of a modification of the existing one, causing potential breaks in the future.

So it is a bug which don't cause BIG problems when it happens (with numerous DAWs the bug do not exist at all) but I don't fix it not because I'm particularly evil, but because it is better not to mess with low-level logics since sometimes the "cure" could be more dangerous than the potential "disease".

Well no, of course it doesn't make it unusable, but it is very annoying. And that, coupled with it not remembering the preset name when you reopen a project, is two very annoying preset browser issues. I have had a conversation with you in another thread I think about these issues, because to me they are quite a big problem. And as I said previously, so much so that I've stopped using it.

And then there's the 1.5x GUI question?

I would upgrade to version 4 of Little One, and potentially buy your Zerobox, if these problems were ironed out.

[xhunaudio]

Hi,

if there's any issue with specific DAWs, I'm going to address that - also if it would require an IDE change in the future.

Also, I think there's no problem to include a 1.5x or 1.4x GUI in the short term.

[wltchris101]

Thanks for engaging about this matter Bruno. I've just revisited it to check again what problems I was having, and as I've also just become a Bitwig user, I now have 2 DAWs to try it in (also Presonus Studio One 4). Firstly, the GUI issue in my opinion really needs sorting. The 1x size (which is really very small) seems more like a 0.5x size in comparison to the 2x (which is too big for the screen). This alone makes it no fun to use. I have a lot of plugins, and I can now count on one hand (actually, probably a few fingers of one hand) how many of them still have this problem - and yours are one of them. It doesn't do you any favours in comparison to the competition. I think it would be in your best interest to fix this.

Now to the presets problems. In both DAWs the VST3 has the changing presets via the arrows on the UI problem - it skips to every other preset. Furthermore, again in both DAWs, any user presets (which btw need to be loaded via the load button, and are not available from the preset browser) totally bypass the arrow selection method - if you load a user preset, and then use the arrows to try and select the next user preset, it instead selects a random Factory preset. And finally, any saved project, when reopened (again in both DAWs), the preset name reverts to the default preset (only the name however - the preset that reloads is the same one that you saved, just the name has changed).

The VST2 is better than the VST3 in both DAWs only in that the changing of presets via the arrows on the UI works as it should, and in Bitwig this also includes the user presets - in Studio One, selecting the user presets with the UI arrows has the same problem as the VST3 version. The VST2 version has the same saving/reopening preset name reverting to the default name problem (but again with the correct actual preset sound).

[Jopmanajop]

So, Bruno, are you gonna switch to different framework? I'm still considering upgrade, but with preset and syncing problem it would be pointless (for me). Again, i love the sound so much, but can't always render small phrases and sync them manually

[xhunaudio]

Hey,

I just replied on the IronAxe thread with a "similar" topic about future frameworks and IDEs.

In LittleOne the GUI size thing is something which can be addressed in a reasonably short term, the +2 presets is a minor thing but that requires a framework change. In the current framework, there's not a variable you can switch to fix the +2 preset without compromising the stability of the VST3 format.

(This +2 presets also just happens on a few DAWs but not on others, so it depends on how the VST3 standard is interpreted by the different Hosts).

I think I'll change the IDE framework only when a very solid one, with long-term compatibility and based on the new JIT concetp will be available. Adopting a new IDE is a very complex thing, so it can't be changed in the short-term.

[Jopmanajop]

Hey, Bruno
How's that framework change going? I recently tried ZeroBox and KickBeat, and they have the same LittleOne syncing problem

[xhunaudio]

Before a framework change, I want to see if the "plugin" concept will improve in the mid-term with the introduction of something similar to WAMs (but in a pro audio context).

I'm looking for a definitive framework, not something I have to upgrade or even rebuild from the ground up every 5 years.

Measure 100 times, cut once.

[Jopmanajop]

Hey there, how's it going?

[Lesha]

Is the aliasing going to be fixed?

There is no aliasing problem to be fixed in LittleOne.

If you want even better results, you can go with a higher sampling rate. LittleOne uses internal oversampling too. In any case (internal and/or external oversampling/sampling rate), you can't avoid a CPU hit (and it makes perfect sense).

I used DDMF Metaplugin to enable 4x oversampling, you can check it out for yourself.

Seq 1, no OS https://www.dropbox.com/s/ww0cvno1v2a9s ... _no_OS.wav
Seq 1, 4x OS https://www.dropbox.com/s/refu6mnlwnyqa ... _4x_OS.wav
Seq 2, no OS https://www.dropbox.com/s/953jfu6pd1ks5 ... _no_OS.wav
Seq 2, 4x OS https://www.dropbox.com/s/msazery1jenwr ... _4x_OS.wav

Is it too complicated to add a 4x OS option?

The sound difference is obvious and I would much rather have it natively than to bother with the Metaplugin. This is the main reason why I do not want to upgrade to v4.

[xhunaudio]

Yes, an internal oversampling selector for LittleOne could be done, but I think it's something not strictly needed.

Seriously (without making self-promotion) you get very good results @44.1khz. Obviously, if you want it to go even further, you can easily run it at higher sampling rates and/or use oversampling with external plugins/wrappers.