Hello
Would someone know how to fix this please.
everytime i crash and hit the shift key withr it will replace me back onto
the track with scratching sound.
i have sblive
winxp
gf4 ti200
512 ram
just installed 1.2.0.0 Patch , disconection patch, and now cpu speed fix.
but still there :(
when i first race sounds are fine ( incar ) but again when i hit shift-r
it will sound shit from inside car .
thanks
> i have sblive
> winxp
This is the combination that causes the problem. I use this combination
also. I am currently scouring the 'net for solutions. I'll post one as
soon as I can. BTW, there is a thread from a day or two ago which offered
some possible solutions to the problem for some users.
Thanks Damien
will wait for your return ( with fingers crossed ) :)
"Damien Smith" <[email hidden]> wrote in message
news:as1fb0$mtg4h$[email hidden]...
Quoted text (9 lines)
> > i have sblive > > winxp > > This is the combination that causes the problem. I use this combination > also. I am currently scouring the 'net for solutions. I'll post one as > soon as I can. BTW, there is a thread from a day or two ago which offered > some possible solutions to the problem for some users. > >"Damien Smith" <[email hidden]> wrote in message
news:as1fb0$mtg4h$[email hidden]...
> > i have sblive
> > winxp
>
> This is the combination that causes the problem.
Agree that this combo is the problem. Installing the latest drivers from
the Creative site solved the problem for me, but it seems that this hasn't
helped everyone. Here are two other things that have fixed audio problems
I've had with a couple of other programs:
a) run the program in one of the "compatibility modes" (right-click on the
executable file, try all the different options)
b) reduce the hardware acceleration setting on your sound card -- obviously
not the best solution if you can avoid it (setting can be found somewhere in
your control panel -- I'd be more specific but I'm on my win98 box right
now)
> Thanks Damien
> will wait for your return ( with fingers crossed ) :)
No good news I'm afraid. The only solution it seems is to pull the SBLive
out and use onboard sound or upgrade to an Audigy (which seems kind of
silly.) Removing the SBLive isn't an option for me since I use the S/PDIF
digital output on it frequently. The other option is to use Win9X, but it's
not really stable enough for my needs.
So far I've discovered....
- Changing sounds from 8bit to 16bit makes no difference.
- Reducing hardware acceleration makes no difference.
- Using the latest drivers or indeed any other driver makes no difference.
- Reducing system volume or the volume of the wavs themselves makes no
diffrecen
"Damien Smith" wrote...
> > <snip>
It has been suggested to make sure you're not "on" or even touching the gas
when you go to track or reset.
Jan.
=---
"Jan Verschueren" <[email hidden]> wrote in message
news:95dF9.23814$[email hidden]...
> "Damien Smith" wrote...
> > > <snip>
>
> It has been suggested to make sure you're not "on" or even touching thegas
> when you go to track or reset.
In my experience this helped avoid sound corruption when joining the track,
but the problem could still come back after a shift-R etc.
One other, fairly drastic option that I successfully tried was to disable
ACPI in Win2k. Disabling it in the bios makes no difference to IRQ
assignments in Windows, which I think is where the problem lies. Your
graphics card and soundcard are probably sharing the same IRQ under ACPI,
and disabling it will allow them to take the IRQs specified by the bios
instead if Windows.
To do this you need to open the device manager and change the driver called
'Advanced Configuration and Power Interface (ACPI) PC' to 'Standard PC'.
This is not a simple thing to do, and may require a format & reinstall if it
goes wrong, so take a backup etc if you try this, and don't try it at all if
you're not absolutely sure about what you're doing.
This should cure the sound distortion but you will lose pretty much all
power management, eg. your PC will no longer automatically switch off when
you shut down Windows.
Please note that I do not recommend trying this if you are not sure how to
recover your PC if it fails to boot (ie if you get it wrong), and you do so
at your own risk.
It worked for me, plus cured a few other conflicts I was having at the time,
but I changed it back to ACPI when I found out about lowering the hardware
acceleration, since that cured it for me.
Malc.
> One other, fairly drastic option that I successfully tried was to disable
> ACPI in Win2k. Disabling it in the bios makes no difference to IRQ
> assignments in Windows, which I think is where the problem lies. Your
> graphics card and soundcard are probably sharing the same IRQ under ACPI,
> and disabling it will allow them to take the IRQs specified by the bios
> instead if Windows.
I might try this out of curiosity (not without Ghosting my C Drive first!)
It seems my sound card does indeed share the same IRQ as my VGA card. I
take it there's no other way of rearranging IRQs in Win2K/XP?
"Damien Smith"
> I might try this out of curiosity (not without Ghosting my C Drive first!)
> It seems my sound card does indeed share the same IRQ as my VGA card. I
> take it there's no other way of rearranging IRQs in Win2K/XP?
> I keep seeing this over and over. DESPITE what Microsoft says...DESPITE
what Motherboard manufactuers say... DO NOT LET YOUR VIDEO & SOUND SHARE
IRQ's with ANYTHING!!!
The techs and manuals all say that sharing irq's is not a problem, but
real world problems like Damien's continually disprove the experts.
(I might say, if Creative and Nvidia and other hardware manufacturers built
100% inspec, this wouldn't be a problem, but since they don't, it is.)
dave henrie
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.422 / Virus Database: 237 - Release Date: 11/20/02
> I keep seeing this over and over. DESPITE what Microsoftsays...DESPITE
> what Motherboard manufactuers say... DO NOT LET YOUR VIDEO & SOUND SHARE
> IRQ's with ANYTHING!!!
> The techs and manuals all say that sharing irq's is not a problem, but
> real world problems like Damien's continually disprove the experts.
> (I might say, if Creative and Nvidia and other hardware manufacturersbuilt
> 100% inspec, this wouldn't be a problem, but since they don't, it is.)
Yeah, it wouldn't be the first time I've seen IRQ sharing cause problems.
The SBLive also has a bit of a reputation for causing the occasional problem
when sharing IRQs. Sometimes the only solution is to juggle the PCI cards
around a bit since assigning IRQs in the BIOS has no effect on Win2K or
later OSes (including WinME.)
