ModPlug Central

OpenMPT Development (Archive) => Bug Reports => Bug Report Archive => Topic started by: pera on September 03, 2006, 01:28:12

Title: .45 Albino2 VST
Post by: pera on September 03, 2006, 01:28:12
When I try use Albino2 with the last release of OMPT a alert message popup informing that an exception in processReplacing happen, and then set the instrument to bypass..
can i run OMPT in debugging mode with some parameter to get more information about the error?

(sorry my english :P)
Title: .45 Albino2 VST
Post by: rewbs on September 11, 2006, 20:04:17
Hi, what is the exact version number of albino2?
I'm able to use 2.0 with no issues.
Title: .45 Albino2 VST
Post by: pera on September 13, 2006, 01:08:54
Hi rewbs, the version is 2.2.1
thanks for reply :D
Title: .45 Albino2 VST
Post by: rewbs on September 17, 2006, 01:19:56
I couldn't find that version, but I tried the 3.01 demo on the linplug website and that seems to work fine. Are you able to use albino 3?
http://www.linplug.com/Download/download.htm
Title: .45 Albino2 VST
Post by: pera on September 19, 2006, 02:33:44
i don't know why, but in my computer the version 3 of albino don't work :S (i have donwloaded the demo with your link)... but I haven't the same problem that with the 2.2.1; with the v3 I can't listen anything (only the noise because is demo).

I have similar problems (the "exception in processReplacing") with others VSTs (like crystal or z3ta+)... but if I use other program (like ableton live), the vsts work fine..

(excuse my english :P)
Title: .45 Albino2 VST
Post by: LPChip on September 19, 2006, 09:32:31
Sounds like a problem with your drivers.

The best thing to do is to find out how to get 3 to work, as I'm not sure we can considder this a bug with OpenMPT.
Title: .45 Albino2 VST
Post by: pera on September 19, 2006, 21:18:42
I think that the problem is my old computer (I have a K6-II processor)..
Title: .45 Albino2 VST
Post by: LPChip on August 14, 2007, 20:52:05
I am going to close this bug. If it seems that it is still happening, please reply so we can reopen the bug for you.