CPU Overload with AU 1.1.5 in Logic

[pkdick]

ive downloaded this update

==> http://www.arturia.com/downloads/obsemv/beta/Oberheim%20SEM%20V_115_rc5.dmg

It maxs out my cpu and everything grinds to a halt

[Adrien]

Hi

You mean you have a new problem with this update, not the readsize==bytesize ?
could you describe it please.
When does your CPU change, what happens ?

can you reproduce it !

is in as plug in or not ?
does it happen in another host ?
If you had this when loading a preset, could you please send us the project.


Best

[pkdick]

yeah, not the bytesize thing.

i have a song with minimal instruments running- couple of plug-ins, spark, couple of external instruments- not much cpu strain from this. as soon as i add the oberheim au and press one note the cpu goes through the roof and throws up a 'system overload' message. happens every time. ive attached a screenshot as it blows up

[Adrien]

Hi

Thank you for the informations,
I 've never seen this, I will try to reproduce.

Could you please send me your logic project, and your aupreset of the oberheim.
Also what is logic version, are you using it in 64 or 32bit, what os version ?

I could not reproduce it with logic 9, the obsem 1.1.5 on two different 10.7.
I Let you know if I have more info.

Best

[pkdick]

yep, here:

logic 9.1.7, 32 bit, Mac 10.6.8, 2.66 ghz dual-core intel xeon

[Adrien]

Hi

After several tests on different OSes and versions of Logic, including of courses your configuration we could not reproduce it.
So it may happen sometime on your configuration in a specific configuration, or depending on the sequence of action you did. Or it may be related to your set up, anyway currently I can't reproduce it.

We Will release the 1.1.5 to provide everyone a fixes which do not show any drawbacks except in your case, but we will continue to exchange with you and try to find out what is hapenning and hopefully we can find out for the next version.

So don't lose faith we really hope we can help you with this.

Best

[pkdick]

thanks for looking into it.

btw also got the jenkins root thing when using spark today

[Adrien]

Hi

With the 1.1.5 ?
the readsize==bytesize ?
because we noticed that some people who had the bug with 1.1.3 now have a warning saying "out_bytes_read==4"
Which is annoying but not dangerous, clicking ok should just ignore this warning, this is because of corrupted data written by the previous version when the bug readsize==bytesize occured.

best

[mortimer]

Hi,
Same problem here--whether using the standalone or the logic plugin the CPU load goes nuts and I get all sorts of clicks and noise when I play more than a single note. Not sure how to document this, but it seems to have happened since 1.1.3.

[mortimer]

HELLO out there...Arturia, are you listening? The plugin is unusable right now....

[Adrien]

Hi

Sorry for the late reply, we will see if that happens but it never occurred here.
Do you have a specific preset to reproduce this ?
What is your platform ? (midi controller, audio interface, os version, host version, plug in format, 32/64)

Best

[mortimer]

Hi Adrien,

SEM 1.1.5, Mac OS 10.8.2 64 bit AU plugin with Logic 9.1.8. I finally had the chance to do a bit more testing; the problem is intermittent. I had it the other day but now it's not as severe. I still get clicks and pops when I play, but without as much CPU load (around 20 percent because of a pitch envelope probably). How can I send you a preset (it's one I made) so you can hear this? Do you want me to try to record it?

In the meanwhile perhaps you can have a look at the midi learn business. I just managed to produce a new error (usually it just crashes)....and then it crashes. The report is in the attached RTF doc. This was produced with the standalone (since I don't want to keep crashing logic).

Thanks.

[Adrien]

Hi

Thank you for the information, the MIDI Learn bug is fixed in the 1.1.6 as far as I know.
We are currently starting beta on this version.

best

[mortimer]

OK, that's good news. But what to do about documenting the problem with SEM and CPU? As it stands, when I play a cluster of six or more notes (it seems to go this way) with a patch I've made that has a pitch envelope, I get chopped up sound. Nothing else is pulling CPU resources; SEM is running by itself. My impression is that it's barely able to do what it's supposed to do, that there's no headroom. And is thus unusable.  I'd be happy to make a sound file if you think this would help--what's the best way to document this?

[mortimer]

The case is getting handled now directly with tech support, but from some basic testing the problem appears to be the interface. When it's open, I get CPU spikes. When closed, things are more or less back to normal. More soon (hopefully in the next version)