New Motherboard/Processor

stefan · 2 Nov 2006

Regarding glitches in audio, have you made sure that the soundcards IRQ isn't shared with some other hardware in your computer? I've had glitches due to IRQ sharing in the past.

Go to: start menu->run->msinfo32.exe->resources something->conflicts/sharing

Or something like that. My current setup has the audio card on IRQ 10, and that IRQ is also shared with the network adapter and something called "ALi PCI to USB Open Host Controller". No issues on this computer though, but on my last I had issues and those got solved if I made sure the soundcard was on its own IRQ.

sequencer · 2 Nov 2006

You might want to look at the PCI Latency timing that the graphics card is using. Some graphics cards have been known to hog the PCI bus.

I use this program to configure my latency. It's freeware.🙂

http://downloads.guru3d.com/download.php?det=951

Try adjusting latency to the lower end for your graphics card, i.e. somewhere around 64 did the trick for me, but you may have to jiggle it about a bit to get a setting that works for you.

You can set this to automatically load up at start time and adjust your latency every boot, otherwise it will go back to what it was, presumably because the graphics drivers etc set it that way. Anyway give it a whirl, sorted my glitches ( my graphics card was setting itself to a latency timing of 256 before I reined it in 🙂

doug4350 · 2 Nov 2006

Hi Mike,

I'm using a P4 2.6GHz, 512MB ram .. .. .. I had similar problems you are having when recording. I found out that the network services were a big contributor to the problem. Whenever I record, I physically unhook the network. I also go into services and stop all non-essential services (including non-network) as well as task manager and kill all those nuisances that hang out in the system tray. I also disable anti-virus as it's "safe" at that point. I use Sonar to drive the midi to my h/w synths and feed it back to my M-Audio 2496 via fiber, or my Roland RPC multitrack pci card via 25 pin din cable.

You may wanna give that a shot (if you haven't already) before forking out precious £/$.

Aloha, Doug

infuzion · 3 Nov 2006

doug4350 wrote: I'm using a P4 2.6GHz, 512MB ram .. .. ..Whenever I record, I physically unhook the network. I also go into services and stop all non-essential services (including non-network) as well as task manager and kill all those nuisances that hang out in the system tray.

A few links, update if you find something really good please: [old link]

I used a AthalonXP 2100 for quite a while with Win98se, with no real problems, but I messed with the IRQs, minimized my OS install, etc.

Could also be that your ram or ram slots are bad: In the same computer, I can only use 1 Ram slot since the others are blown from a power serge.

electrogear · 3 Nov 2006

Hello,

@Stefan: Thanks for that info. I had a look, and it seems that my USB slots are all sharing the same IRQ. My soundcard is built into a Midi keyboard, which is plugged into the USB port, however I am not using any other USB devices, so it shouldn't be a problem should it? I noticed there wree quite a few other devices sharing IRQs, so there could be something to look at there. How do I go about reassigning IRQs then? and how many IRQs are available? I think I'm using 21 at the moment, although 16 and a couple of others are free.

@sequencer: The graphics card is the only PCI device in my PC. The soundcard is USB, so I don't trhink that would be the problem. Thanks anyway for your help

@doug: My PC isn't on a network so I don't think that's the problem, but thankyou.

@infuzion: My Ram slots themselves are fine. My 2 x 1GB RAMs are made by different manufacturers though. It wouldn't be that would it?

Thankyou all for your help,

Mike

stefan · 3 Nov 2006

Some hardware allows reassignment of IRQ's if you go to your device manager under "system" in the control panel. Not all hardware does these days though.

It might just as well be sucky USB drivers or whatever in your case. Hard to nail these things :/

rlahalla · 3 Nov 2006

Mike,

Check to make sure that the memory you are using is the same type (ie..pc2700, etc.). Make sure you update your audio interface's drivers. I've gone through a number of Ozones myself, they do have very crappy USB drivers. If you have a computer running 2 GB of memory, a 3GHz processor, and a decent amount of dedicated video memory, there is no reason that you should be recieving glitches and pops in your audio. I would say that it's most likely either how your setup is configured (as doug say, turn off non-essential services, etc.) or the way your audio card is configured, or their drivers just suck (no offense to any m-audio freaks in here). 😀

doug4350 · 4 Nov 2006

Hi Mike,

@infuzion: My Ram slots themselves are fine. My 2 x 1GB RAMs are made by different manufacturers though. It wouldn't be that would it?

If you can, and if you have the specs on the ram, remove the "intuitive" slow simm. I've seen systems run slow with wierd mem configs and a gig is way more sufficient for a test.

I also never did like that shared irq scheme. By today's standards, irq's are slow, and sharing them compounds the problem. However, as Stefan mentioned, hard to nail these things :/ 🙂. There's also some ambiguity in the irq calling convention with sharing irq's as for the "parent" handler whether to setup another irq for it's decendant or just capture the entry point and use that 😕 It's been a while since I fooled with those at the code level, but no walk in the park.

But also as Stefan mentioned, reassign them if you can. You'll need to map your irq table for that (not a lot of fun -- even for a geek 🙂 ).

the way your audio card is configured, or their drivers just suck (no offense to any m-audio freaks in here).

Rlahalla, now .. now, I am not an m-audio freak 🙂 that was a funny comment though... I use m-audio for the price. It seems the engineers over there developed there stuff for geeks like me over here. Their rtfm leaves a lot for the crystal ball, but it's pretty robust if you're the right kind of psychic 😀 . Out of context, I have an easier time with their gear than with SM 😮 😀 . That was a funny. Really though, SM keeps life from being a bore zzzzzzzzz.

Aloha, Doug

cAPSLOCK · 4 Nov 2006

I like underdogs. AMD held the lead in processors for quite a while. I own stock in both AMD and Intel, but more AMD.

That said the latest batch of Core 2 DUO chips smoke the AMD64 chips. ESPECIALLY if you plan to keep running a 32bit OS, but even on the 64 bit ones.

The only problem is your budget. The motherboards and memory that are compatible/optimal for these chips are in themselves very expensive. But take the time to look into it.

For less dough, the AMD64 chips are nice and fast. A good-for-audio inexpensive 939 motherboard is the GigaByte K8U.

But here's to solving your glitches, and maybe a new machine.

cAPS

electrogear · 4 Nov 2006

Hmmm, yes I've just looked into the Core 2 Duo chips. It looks like I'd have to spend around £200, and then another £80 - £90 on a motherboard. That would probably mean updating my RAM I guess (Sorry I'm not very up to date with computer specs over the last year or two) so I'd be looking at £350 - £400 altogther. 😕 I just can't afford that at the moment. I might wait a while (say 6 months??) and see if it goes down in price a bit. I'm not at Uni 'til next September anyway, so I can wait until then,

Cheers,

Mike

rlahalla · 4 Nov 2006

@doug, I tried m-audio products but couldn't ever get into them. For me, the quality wasn't there, and the performance wasn't there. I had a few of their products and one was the oxygen 8 (who didn't have one?), and every other day the thing had driver issues. That was the last m-audio product I ever purchased. Tascam, RME, and Echo are all I use in the studio now. Rock solid drivers and crazy support on their products. And actually, it seems I am now having a much easier time with SM than M-audio products!

doug4350 · 4 Nov 2006

@rlahalla ...

Seems this thread is doing a lot of @'ing 🙂. That's cool. Point those fingers 😀 . nah, I know where you're coming from. There is definately some "cheezy-ness" in their product line. I must be one of the fortunate ones who got some of their better stuff (or, less intense). I have the midiman usb midi i/f, dio 2496, RPC (formerly Roland), and the Pro-Key 88 midi controller. I haven't tried midi over the rpc 'cuz I heard that's pulling teeth. I was actually surprised how robust the PK-88 was, but definately *NOT* user friendly. No biggy to me, I'm used to that... There's one feature I haven't figured out and haven't put enough elbow grease into breaking the drivers which is the raw midi thing. They have a way to do the high/low byte thing or whatever it is, but haven't gotten that to work. Even the yahoo forum has come up dry on that post. But hey, for $300, and all the bells & whistles, it's stood up to my bands abuse (classic rock/blues). The action is kinda mushy, but better than non-weighted. It's kind of a give and take between the suitcase piano and Hammond patches I use 🙂.

Aloha, Doug

infuzion · 4 Nov 2006

doug4350 wrote: @infuzion: My Ram slots themselves are fine. My 2 x 1GB RAMs are made by different manufacturers though. It wouldn't be that would it?

If you can, and if you have the specs on the ram, remove the "intuitive" slow simm. I've seen systems run slow with wierd mem configs and a gig is way more sufficient for a test.

If you use a program that loads waves into memory, like Ableton Live, & you're loading tons of samples/full songs, 1GB might not be enough.

But they could be different CAS timings, & that can be an issue. You can try tweaking the CAS in BIOS, but that is iffy also.

doug4350 · 4 Nov 2006

But they could be different CAS timings, & that can be an issue. You can try tweaking the CAS in BIOS, but that is iffy also.

iffy is kind of light 🙂. I generally don't mess with mem settings (excluding cache) outside the bios defaults. Everyone likes pushing their machines, but most (like me 🙂 ) ended up with a bootless beeping system 🙂 😠 . Have your screwdriver handy (and m/b docs) to do this, 'cuz you'll end up having to set the bios reset jumper.

Aloha, Doug

rlahalla · 4 Nov 2006

If they are different CAS latencies, then I'm pretty sure there WILL be a problem. Memory should always be done is exact's to ensure proper performance (and prevent crashing 🙂 ). Then again, it's all IMO. And as doug said, tweaking memory settings such as your CAS latencies is a whole world of iffy.

infuzion · 16 Nov 2006

Keep watching DealNews for deals from Dell (don't buy Compaq/HP). I found a stripped-down (if you call 1Gb mem stripped, but no monitor, DVD burner, onboard gfx) XP x2 dual core for $400 USD, Intel Core2Duo for $650. Might be worth the shipping, but you can use that as price guides for local shopping.