LittleOne, Little Phatty emulation

[novaflash]

i like the "mute me" feature

[Ingonator]

I think its a bad emulation...you can get a clean saw on a real Little Phatty

Sorry, but i don't really get it. For me the saw wave sounds like a saw when i set it to the corresponding position. Do you have such good ears to detect some amounts of other waveforms or did you use an oscilloscope ???

AFAIK i've seen somewhere that NO analog synth produces a "perfect" saw waveform. I guess that it would sound even worse if it would be perfect.



@wildfunk: the Little Phatty Stage Edition II has an arpeggiator. And why is adding an sequencer and FX bad ?? The synth could sound good without FX but a little of the distortion effect and/or filter overload makes the sound much fatter. I used this "trick" in the upcoming banks for LittleOne (the published ones have to be corrected because of the new envelope response).

BTW the new version 1.1 adds e.g. faster envelopes and velocity response for the filter.
I already told Bruno that some additional modulation features (which could be accessed from the menu in the Little Phatty) seem to be missing. I guess that he'll try to correct all those "failures" as soon as it's possible
I think that it's exactly such input (also the hints from other people in this thread) which could really help him and not only telling that the synth is bad after just using it for 5 minutes.

[Wildfunk]

Sorry, but i don't really get it. For me the saw wave sounds like a saw when i set it to the corresponding position. Do you have such good ears to detect some amounts of other waveforms or did you use an oscilloscope ???

Hm, seems like the plugin is still buggy. Yesterday i tried to select just a wave an there was still a square and triangle in the background hearable. Of course i've leveled the second osc down and disabled all modulations.

The filter overload just makes the output of the 2 oscs louder, nothing more.

This plugin is okay, but too buggy at the moment... and of course too expensive.

Should be declared as beta... i don't wanna buy this thing when every week new "updates" will be released that change the whole sound of all my patches.

[cosmosis]

i like the "mute me" feature

[xhunaudio]

Ahah, yes - the "mute me" (OUTPUT ON/OFF), is disabled.

At the beginning it worked properly, then I decided to disable it for two reasons:
1) Is it a really useful feature for a virtual instrument?
2) Maybe some user could accidentally turn it off and say :
"Why this synth have no sound?" - eheh.

Maybe in next update I will re-activate it again (umh, I'm not sure, suggestions?)

PS:(Cubase 5 users):
Read the v1.1 documentation. I wrote about C5 issue.
It seems to be due to the copy protection used by LittleOne.
When it's not authorized a popup with the activation dialog is displayed.
It works properly with all the Hosts, but not in Cubase ver 5.
Once activated, the popup is not displayed, and LittleOne works without problems.

2nd PS:the FILTER OVERLOAD.
the overload in LittleOne is a pre-post filter 'Soft Clipper' distortion with a signal
increment of +6dB (amplitude+softdist), like in the original Little Phatty,:).

See you next time,Bye

[bM3w]

PS:(Cubase 5 users):
Read the v1.1 documentation. I wrote about C5 issue.
It seems to be due to the copy protection used by LittleOne.
When it's not authorized a popup with the activation dialog is displayed.
It works properly with all the Hosts, but not in Cubase ver 5.
Once activated, the popup is not displayed, and LittleOne works without problems.

There's no documentation in the Demo included, so I can't read about the issue. That aside I can't authorize it, because I'd like to try the Demo first before I buy. No working Demo no potential customer. That easy

[xhunaudio]

The documentation is a .pdf file in "littleone_installer.zip".
If you install the demo the pdf will be copied in your VST folder and there's a link also in your applications shortcuts (Start menu).

Sure you have to try the demo before , but (since Cubase 5 is the only that has problems like this) you can try LittleOne for 30 days in another host (also a freeware one) .

[xhunaudio]

I've just seen the "mute me" feature on this forum.
Maybe Novaflash in previous posts was talking about that and not talking about the synth,eheh

So my reply was unnecessary

[bM3w]

The documentation is a .pdf file in "littleone_installer.zip".
If you install the demo the pdf will be copied in your VST folder and there's a link also in your applications shortcuts (Start menu).

Sure you have to try the demo before , but (since Cubase 5 is the only that has problems like this) you can try LittleOne for 30 days in another host (also a freeware one) .

Ah, ok. You named the PDF "EULA", which is why I didn't read it. Didn't expect a manual in there. Anyways, I've tried your recommended permission settings on the VSTPlugins folder, but that didn't change a thing. To be honest with you I don't think that's the problem, because the plugin DID unpack the SEM modules to a subfolder without these settings, too. I have a similar issue with Livemachine, which is also SynthEdit based and I suspect a general incompatibility in one of their modules.

[Ingonator]

PS:(Cubase 5 users):
Read the v1.1 documentation. I wrote about C5 issue.
It seems to be due to the copy protection used by LittleOne.
When it's not authorized a popup with the activation dialog is displayed.
It works properly with all the Hosts, but not in Cubase ver 5.
Once activated, the popup is not displayed, and LittleOne works without problems.

There's no documentation in the Demo included, so I can't read about the issue. That aside I can't authorize it, because I'd like to try the Demo first before I buy. No working Demo no potential customer. That easy

So why not trying the synth in a free host like e.g. Tobybear MiniHost (like Bruno already proposed). I use Minihost for doing the patches for LittleOne since it has an excellent patch/bank manager. To my experience the plugin (including the demo) works in Ableton Live, MiniHost and Reaper.

link: http://www.tobybear.de/p_minihost.html

[bM3w]

Sorry, but when compatibility can't be guaranteed in the demo, I'm simply not interested. Isn't the purpose of a demo to test it under real conditions in the environment you work with?

[OutCider]

The demo worked fine on a friends cubase, though he said something about running it in savihost first.

[Ingonator]

The demo worked fine on a friends cubase, though he said something about running it in savihost first.

Since Steinberg is the company that invented the vst format for me it's still a miracle how certain vst plugins seem to cause problems with Cubase opposing to other hosts.

[Wildfunk]

The demo worked fine on a friends cubase, though he said something about running it in savihost first.

Since Steinberg is the company that invented the vst format for me it's still a miracle how certain vst plugins seem to cause problems with Cubase opposing to other hosts.

That's because the developers don't follow the VST rules.

[Ingonator]

The demo worked fine on a friends cubase, though he said something about running it in savihost first.

Since Steinberg is the company that invented the vst format for me it's still a miracle how certain vst plugins seem to cause problems with Cubase opposing to other hosts.

That's because the developers don't follow the VST rules.

So are hosts like e.g. Ableton Live, Reaper or MiniHost not following the rules too and that's the reason why plugins like e.g. LittleOne run without problems ???
Or is the reason that those hosts are handling the specifications more "generous" ?!
I never found any free or commercial plugin not running with Ableton Live for example.
I admit that Live 8 has some stability problems but they're almost solved with the new updates now (8.1.1 is already very good and the betas even better).