Xref: news2.mv.net comp.os.msdos.djgpp:4154 From: locke AT mcs DOT net (Peter Johnson) Newsgroups: comp.os.msdos.djgpp Subject: Re: allegro and mikmod Date: Thu, 23 May 1996 02:12:21 GMT Organization: BiLogic Lines: 42 Message-ID: <31785736.6898924@news.mcs.net> References: <31755CDF DOT 1248 AT gl DOT umbc DOT edu> <31776CA1 DOT 40D4 AT mailer DOT cefriel DOT it> NNTP-Posting-Host: locke.pr.mcs.net To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp On Fri, 19 Apr 1996 12:36:18 +0200, Massimiliano Mantione wrote: >Patrick L. Jenkins wrote: >Another problem... I compiled mikmod 2.09b and sb05 with DJGPP v2, >and it seems to me that the CPU load of mikmod is too high (I made >some experiment using Win95 multitasking, and mikmod went out of >sync often, while in the same conditions sb05 behaved fairly well). > >Have you tested the performance of mikmod 2.10? -----BEGIN PGP SIGNED MESSAGE----- i have a 486dx2/66 and mikmod 2.10 has what many have referred to as the Future Crew "slowdown" bug. It appears as though the timer routine is reentrant when its not supposed to be. Changing mikmod to use 8-bit mixing fixes this problem, but i would prefer to have 16-bit mixing. Symptoms include "echos" and skipping when playing any truly complex s3m file. Perhaps this problem can be fixed in the next version. I could never get 2.09beta to run on my machine, but 2.10 runs great except for that bug. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMXhYfHT/fRwwD8jhAQG51QP/eAqOYfz6fRrObOyNaemXpLdLB3cQIDwj 0ufjetpJGM1gTp5SY+Zeyflu67J3fIrYnxWqhFUBIA9JbIyOH7At7NLTvOvZSvDC uBNoBoHWMxv17aa9cC3U19Bm+fExAhjRwECrzwu/y4wd6fY091G0iFFHhTbqtoGx 9oV5/ft5zvc= =ysVx -----END PGP SIGNATURE----- ------------------------------------- Peter Johnson ------------------------------------- locke AT mcs DOT net http://www.mcs.net/~locke/ ------------------------------------- Freelance C/C++/Pascal/Asm programmer for DJGPP, Borland, and Watcom compilers Member of BiLogic demo group -------------------------------------