Atomic, possible bug?

[swonderme]

Hey guys,

I've been playing with Atomic a lot over the last couple of days and I've got two projects (in Live 7) that are using 2 instances of Atomic, and both are crashing with the following error.

Assertion failed: next_event -> time_stamp >= current_sample_clock, file C:\Borland\BCC55\se\se_sdk\SEModule_base.cpp, Line 209

In each project I am using two Atomics to drive a drum machine (analog drums vsti from pluggo) and a bass (minimonsta vsti).

What happens is that first the Atomic interface won't draw properly, then ableton to goes into a state where the transport controls stop working, and eventually I get the above error message.

I have no idea if Atomic is the cause of this error or not, I've used both of these vsti's plenty of times before without problem though, so that's why I'm asking here.

Does the above error have any meaning in determining what could be cause this error?

No rush on this. I'm going to play around with it some more and see if I can rebuild the projects from scratch with different vsti's to see if that helps. I will be going out of town tonight until early next week, so I may not be here to provide feedback until next week.

Thanks!

[swonderme]

Just to update this,

I built the same project from the ground up and got the same error in the end. The only thing I did differently was to use one of Live's buit in Drum Racks instead of the pluggo drums (to eliminate pluggo as being the problem).

Everything works fine until I add the second instance of Atomic and then feed it a midi clip. (I enter a midi clip just playing "C" so I don't have to keep my finger on the keyboard as I tweak the settings in Atomic.)

So, I don't know if there might be a problem with multiple instances of Atomic? Or if something funny is just happening on my machine.

When I have time I will try the same thing on my studio comp (I'm using my laptop right now).

Thanks.

[tconrardy]

Sorry you are having issues

are you using a duo core?

Here is what we have on our Support page:

======================
Regarding Duo Core Issues:

Multiple instances on a duo core system with multiprocessing enabled have been known to cause issues. This is regarded as a known Synth Edit bug.

The workaround fix: Copy the dll and re-name it for as many instances as you need if you want to run in multi-processor mode. Otherwise, you can also just turn Multi-processor mode off in your Host preferences

========================


Does this describe your issue?


Tim

[swonderme]

That could very well be it as I do have a Core Duo, sorry for not reading your web page before posting here.

I will try that workaround and see if it takes care of things.

Thanks!

[swonderme]

That fixed it! Thanks!

[tconrardy]

That fixed it! Thanks!

Great! Sorry for the hassle, but at least there is a fix for it.

Tim

[swonderme]

Yeah, it's no problem at all to just make a bunch of copies of the dll.