Hi all. I bought Titan and Nitron on Christmas Eve (my time) due to the 2for1 promotion and started messing around with Titan yesterday. I use a MacBook Pro 17" (specs below) with MainStage as my live performance DAW and was running Titan as an AU plugin in 32-bit (64 sample buffer). Something that really surprised me was the incredibly poor performance of Engine when it was running with the GUI onscreen. I was constantly getting audio dropouts and crackles and my CPU meter was virtually always at 100%. I checked Console and sure enough, there was message after message of audio engine overloads. This never happens with any other synth I own, even Omnisphere!

However, as soon as I closed the Engine GUI the Titan sounds became playable and I experienced almost no audio overloads at all. My CPU meter rarely got above 30-40% with the GUI closed. I couldn't believe the difference....it was very noticeable.

Why is Engine virtually unusable when its GUI is onscreen? I run a LOT of virtual synths and never have any issues with them, regardless of whether their GUI is onscreen or not.

Yes, I'm running the latest version of Engine. I tested the standalone last night and it suffers with the same issue. Here's what I did: with Engine onscreen, I used my trackpad to click notes on Engine's virtual keyboard. I had a digital atmosphere pad and sure enough, I got audio crackles using a 64 sample buffer. I then minimized Engine (so it wasn't onscreen) and tested it the same way by using a freeware virtual MIDI keyboard called MIDIMock - guess what, no audio crackles.

The only thing I can think of is that there seems to be an issue with CPU usage when Engine is onscreen.

PhilG, would you mind emailing Best Service tech support to report this? I communicated with Martin from BS the other week but they can't seem to replicate the issue. If BS is made aware this isn't just a one-off situation, they might look into it a bit further for us.

I'm 100% convinced there is a bug in Engine....what I've experienced can't be normal behavior.

229 posts since 8 Dec, 2004, from A small village in the north of Germany

by PhilG; Mon Dec 31, 2012 12:19 am

Maddcow wrote:PhilG, would you mind emailing Best Service tech support to report this? I communicated with Martin from BS the other week but they can't seem to replicate the issue. If BS is made aware this isn't just a one-off situation, they might look into it a bit further for us.

I'm 100% convinced there is a bug in Engine....what I've experienced can't be normal behavior.

CheersGary

Done, I'm sure too that this is a problem with Engine.
After I had it installed I experience some strange behaviour in projects, where an instance of Engine is involved.

we're already into this issue... and have it on our list of improvements.
This problem happens in an earlier version of engine (as far i remember version 1) and actually should be gone.. but it seems that some people still experience this problem.

Obviously the mac version is broken. I have exchanged many emails in the last week with support at Best service for precisely the same issue, although i have 5 libraries installed and have had over 100 crashes in 7 days (always when choosing presets from the drop down menu rather than arrow keys, especially when switching libraries)

That, coupled with the most atrocious performance i have ever seen on a sample player, has rendered all my purchases effectively unusable.

Man, sometimes a single patch will spike multiple cores in logic. It's crazy.

So now, i have simply thrown over $500 away.

I am negotiation a refund as this is unacceptable and there was no way of knowing pre purchase.

Wanna hear about bad cpu performance? i got the k size loop pack, and with elastic enabled (which it has to be to sync to tempo) just pressing ONE note, playing ONE loop, uses and ENTIRE core. Yep, a WHOLE core of an I7 for a single drum loop

It's a joke, and offensive, and one has to wonder at some point ,how these products even make it into the wild in this state

I also have experienced performance issues with engine (not as bad as above, but enough that I have to bounce in place - and this is with plenty of headroom).

I've also got an unusual crash on quit in logic which is apparently related to the copy protection. No ETA on that particular issue, but at least Magix and BestService have continued to be in touch and so the support side seems to be much improved over the YT days.