SEM AU Blowing up Old Logic Pro Songs...

[JDoo]

I've had the exact same error message with a Logic Pro session of mine using the SEM. JDoo's way of disabling the audio and opening the affected session worked great. Thanks a lot!!

Wish I could take credit for the fix.      It actually came from a post by David Nahmani on a different forum.

Oddly - I had a near identical issue with the Wurlitzer AU in MainStage. I was on stage in the middle of a set, and didn't have time to capture a screenshot (had to reboot MainStage to get my sounds back).  Anyway - not sure the precise error, but it looked similar - and was referencing the Wurlitzer V AU.  After restarting MainStage, I didnt have any other issues..

[qube123]

Having the same issue, it doesn't happen all the time but seems to affect the saved project, if I go back to an earlier save then it'll load.

32-bit and 64-bit operation have the same issue.

[pkdick]

im also getting this when using spark, happens all the time when opening a project with spark and sem, tried Jdoos fix, worked once, when i went to open the project the next day after closing down computer I got the error again

[qube123]

Any word from Arturia on this error. get it all the time, on both my 10.6.8 and 10.8.2 machines under Logic 9.1.8 in 32 and 64 bit modes. It's sufficiently frequent that I've had to write this plugin off until there's a fix, which is a shame as it does sound lovely.

[Marcus Gorstein]

Same here. It even crashed a Logic song I was working on and gave a

file: /jenkins/root/workspace/Oberheim_SEM_Mac_Release/Oberheim_SEM/project/Mac/../../../AudioFramework/ArturiaLibAudioV2/src/Software/Event.cpp
line: 81

I mailed tech support and hope to hear from them. Until then, I will also stop working with it.
Darn...
Take care,
Marcus

[Kevin]

Hi all,
sorry for not getting back to you sooner on this problem.
We may have found a solution, we will get back to you on this ASAP.

Kevin

[pkdick]

this is also junk for me until there is a fix

[Dav1d]

Hi db3,

This issue may be solved in the newer version:
--> http://www.arturia.com/downloads/obsemv/beta/Oberheim%20SEM%20V_115_rc5.dmg

[georgelegeriii]

Having the exact same problem, sent a crash report and also sent an email with the current bad Logic Pro song file.

George

[Adrien]

Hi did you testedthis with the 1.1.5 ?

This issue may be solved in the newer version:
--> http://www.arturia.com/downloads/obsemv/beta/Oberheim%20SEM%20V_115_rc5.dmg

Best

[badcatblackcat]

Just had this exact problem.  Had a backup of the effected song so I just deleted the versions with the problem and removed the Oberheim from the backup copy.  Worrisome.

[Adrien]

Hi

You mean you had this problem with the 1.1.5 or You had the read size byte size issue ?
If you have a backup of your project, that is great, very often restoring a previous version of your project can help.
However, if you want to solve this issue, you should try 1.1.5 if you did not.

best

[ponynop]

I had this problem with the Oberheim SEM. Updated to 1.1.5 but the error still comes up. With this version I can now at least get past the error message and open the project but it has made my whole DAW unstable and finding it constantly crashing when using the Oberheim. Shame as it's a beautiful VSynth

Using Cubase 6.02 on Mac OSX 10.5.8

[Adrien]

Hi

The error message can not make your DAW unstable, basically you probably see "read_size==4" or something like that.
It happens because in the past the preset had been corrupted by the other bug.

Don't worry, you just ignore that, the only problem that this reveals is that some parameter value might be different from what you saved.
It will not make the plug unstable and even less the DAW. it is annoying just because it says that some data might be different from what you saved in the first place.

I'm sorry about this inconvenience.

Now if you have problems in your DAW, this must be for another reason.
BTW, cubase 6 does not support 10.5 and there is also a 6.0.7 update