Clicks'n pops'n that sort of parafernalia

[Edu]

The following doesn't work (at least before your answers):

ASUS P2B motherboard / Intel Pentium II - 300MHz / Turtle Beach Multisound Monterey / Cakewalk 6 / Windows 98 release 2

 

Audio tracks in Cakewalk make clicks and pops, midi gets out of synchronization and finally the sequence stops. This gets worst as you add audio tracks. (I have 64MB RAM).

Sometimes it seems to be the D0000 memory address needed by the Monterey that is used by the ATI 3D RAGE PRO (or any other video card, since I tested the system with an old Realtek - 256kB (Ugh!)). This happens even reserving the memory window in the Bios, and verifying that the video doesn't map this window.

Sometimes it seems that the monitor displays a line or two with garbage for a milisecond, as audio is playing.

Even the Windows 98 sound logo at start up has hiccups and clicks!

 

All recommendations from Cakewalk and Turtle Beach proved to be a good approach to troubleshooting the problem but finally didn't work: changed DMA address, downloaded TB drivers & CW patches, reduced aperture (n/a), reduced resolution, run DMA auto configuration in Cakewalk, etc., etc.

 

I am having this problem since 1998. I finally bought a Yamaha RBX 260 and I'm playing bass!, but I would like to return to the good'ol days of the black and white keys.

 

Your turn...

[jonniepain]

You left out one very important fact when talking about audio in a

Computer based system . HARD DRIVE STATS. Do you have a drive just for your audio ? How big is it ? How fast does it turn ? These are all important factors in having audio work in a computer .

[Edu]

Thanks for the observation.

 

Now I have a 20Gb Western Digital. I don´t have specs at the moment but I'm sure it is not causing the problem.

 

Let's say that the monterey and MQX-32m worked well in my old Pentium 133 with a Western Digital 2.5Gb - just that I couldn't throw too much audio tracks in. But it didn´t cause the type of problems I am now having with the new computer.

 

Take my word: it's not the HDD.

 

Thanks again.