Just tried the Discovery demo...beautiful sound. However, as soon as I loaded up FM7 to lay down some pads to play Discovery over, it sent my system into overload - 100% CPU usage. I've tried rebooting, and there are no issues with my setup. As soon as I load FM7 while Discovery is open, it's an instant cpu overload.

Anyone else have this problem? I have a feeling the problem is with Discovery as FM7 has never given me grief with any other VSTis.

My Setup:
Intel P4 1.6Ghz, Asus P4S533 Mobo, 512Mb PC2700 DDR,
Audiophile 2496

OIC

I wonder if the demo is the older version... The new 1.3 doesn't not give me any problems with FM7. I don't know if they've updated the demo or not... But I am using a 2.0 P4, with xp 512 megs ram... I've run 4 instances without any problems....

The demo seems to be 1.3. Strange, maybe it's just my setup then.

Thanks for the reply dhrose

Maybe you have to register it to get it to play nice...

Yep this is a definite problem I've experienced too.

What you need to do is install the MMX version as from what I've experienced the SSE/SSE2 verions would cause 100% CPU usage and thus pretty much cripple your machine.

the SSE/2 verions were always problematic for me, so I just stick to the MMX one.

DiscoDSP guys if you're reading this you might wanna fix this little issue

P.S. I have a P4.

Good idea, thanks ArneyS

OrderInChaos wrote:

Just tried the Discovery demo...beautiful sound. However, as soon as I loaded up FM7 to lay down some pads to play Discovery over, it sent my system into overload - 100% CPU usage. I've tried rebooting, and there are no issues with my setup. As soon as I load FM7 while Discovery is open, it's an instant cpu overload.

ArneyS wrote:

What you need to do is install the MMX version as from what I've experienced the SSE/SSE2 verions would cause 100% CPU usage and thus pretty much cripple your machine.

We are aware, that there was similar problem in the past. FM developers were bugged about identical issue happening with RGC Pentagon-I. Later it was found, that only pirated FM7 copies were acting in this way.

Well I don't know about that, taking into consideration 2 facts.

1) I've bought FM7.
2) I've had problems with the SSE/2 verions of discovery with my sequencer (FLP) since they were introduced.

Only with the introduction 1.3 was I actually able to use the SSE2 version.

It's either, as you mentioned, FM7 related, or sequencer related. And why would the SSE2 version only conflict with 1 synth in particular? It doesn't make sense to me.

I have bought FM7 as well, and I'd say it was my mistake.

FM7 aliases like hell, crashes, and makes other nasty stuff to operating system.

Finally, I have uninstalled FM7, and never had problems again.

DiscoDSP discovery seems to be a nice synth, and I never had problems with it. It was CPU hog, but version 1.3 seems to be nice to my CPU.

rrtdj wrote:

I have bought FM7 as well, and I'd say it was my mistake. FM7 aliases like hell, crashes, and makes other nasty stuff to operating system.

haven't tried discovery so this may not be relevant, but fwiw, FM7 has been totally stable for me, and I love the sound, whether it's partly the result of aliasing and other misbehavior (like 99% of other vstis) or not.

rrtdj wrote:

I have bought FM7 as well, and I'd say it was my mistake. FM7 aliases like hell, crashes, and makes other nasty stuff to operating system. Finally, I have uninstalled FM7, and never had problems again. DiscoDSP discovery seems to be a nice synth, and I never had problems with it. It was CPU hog, but version 1.3 seems to be nice to my CPU.

Aliasing, where? You must be kidding or tried some of my sounds I realy have problems to get aliased sounds out of the FM7 even when it comes to sounds where my FS1R and even more the TX81z already starting to "whistle" and "crackle"... I mostly have to do some quite extreme programming actions to bring the FM7 to do sounds with lots of aliasing...
Never heard of stability problems caused by the FM7, what kind of problems?