First I have to say I like this synth very much for its sound.
Unfortunately some of the presets (about 10-20%) I can't play on my P4 2.8Ghz because of a quite heavy CPU comsumption. I get a CPU-spike to the red when I play a note resulting that I can hear only a loud click.
I'm using version 1.02 of Ogun in CubaseSX3.
I hope this is just a bug and could be fixed in the near future.
Further: My system supports MMX/SSE/SSE2/SSE3 instructions (whatever this is).
Last but not least a suggestion:
When browsing through the preset list, the current selected preset name could be in bold letters. This could make life easier when you try/demo many presets.
Ogun: very good sounds but quite heavy on CPU
-
- KVRian
- 1394 posts since 28 Mar, 2002 from Austria
i7 870, 8GB RAM, ATI Radeon Sapphire, RME Multiface,
Win7 Home/64bit, Studio One 3 Professional/64bit, Wavelab8/64bit
Win7 Home/64bit, Studio One 3 Professional/64bit, Wavelab8/64bit
-
- KVRAF
- 37408 posts since 14 Sep, 2002 from In teh net
I think if you consider what it does - additive synthesis/resynthesis with up to 32767 partials - it is hugely impressive that it manages all that and only takes 20% or so.
This is a sound designers instrument - I think it's not meant really for having lots of instances in a composition but for concentrating on it's sound creation qualities and crafting other-worldly and metallic timbres. In a composition context synths like Ogun are meant to be used in conjunction with freeze/bouncing down if you want complex multi track compositions using their sounds.
This is a sound designers instrument - I think it's not meant really for having lots of instances in a composition but for concentrating on it's sound creation qualities and crafting other-worldly and metallic timbres. In a composition context synths like Ogun are meant to be used in conjunction with freeze/bouncing down if you want complex multi track compositions using their sounds.
-
- KVRian
- Topic Starter
- 1394 posts since 28 Mar, 2002 from Austria
Thanks aMUSEd for the clarification.
So this is the VSTi with the heaviest CPU consumption I ever experienced.
I tested just one instance alone in an empty project.
Preserving this VSTi until I will get an OctaCore CPU
So this is the VSTi with the heaviest CPU consumption I ever experienced.
I tested just one instance alone in an empty project.
Preserving this VSTi until I will get an OctaCore CPU
-
- KVRAF
- 37408 posts since 14 Sep, 2002 from In teh net
You think so? It's still a lightweight compared to Sytrus with oversampling turned all the way (or even to Tassman - some patches take CPU to over 60% on a more powerful PC than yours)
-
Touch_the_Universe Touch_the_Universe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=107005
- Banned
- 128 posts since 10 May, 2006
its a f**king dream.. thanks for t he star kcr. self baning. now days
-
tony tony chopper tony tony chopper https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=3103
- KVRAF
- 3561 posts since 20 Jun, 2002
Ogun, like Sytrus, is only 'guilty' of leaving you freedom. You can use Ogun with a very low CPU usage, if you don't abuse the # of partials (but of course we do, in our demo presets).
It shouldn't be a problem at all with up to 512 partials (which is already more than most additive synths do).
About the note-on CPU hit, yes, the major problem is that the CPU isn't (& can't be) spread very well. There are huge precomputations at note-on, thus even a 20% average CPU usage can cause a buffer underrun. Tip: don't use too small audio latencies.
It shouldn't be a problem at all with up to 512 partials (which is already more than most additive synths do).
About the note-on CPU hit, yes, the major problem is that the CPU isn't (& can't be) spread very well. There are huge precomputations at note-on, thus even a 20% average CPU usage can cause a buffer underrun. Tip: don't use too small audio latencies.
DOLPH WILL PWNZ0R J00r LAWZ!!!!