Son qui distortionne dans certains jeux.

Voici mon problème.

J'ai 2-3 jeux où, à tout bout de champs, le son ce mets à distorsionner vraiment intense. En gros, y'a un p'tit ''tac'' à travers mes haut-parleurs et après, tout les sons sont modifiés, comme s'ils étaient amplifiés X10 avec pleins d'échos et des aigus intolérables.

Ça me le fait parfois dans BF3, burnout paradise et à toutes les 1/2 heure dans Far Cry 3. Pour régler le problème, je dois quitter le jeu ou redémarrer l'ordi...C'est lassant.

J'ai une Creative X-Fi branché avec un câble optique (mais ça me le faisait avant aussi avec les 3 jack)

Quelqu'un a une idée du pourquoi ça me fait ça?

Merci

Même avec la version légale de FC3, ça bug encore plus lol...J'ai de la misère à jouer en direct output, mais j'ai juste le speaker rear à droite qui rush...Seulement dans ce jeu. Film, musique, les autres jeux, j'ai un 5.1 très bon...

Quelqu'un à une idée? Je cherche encore à temps perdu (faut aussi dire que mon logitech Z-5500 à quelques années et que je ne suis pas doux avec... )

Check si tes pas atteind de DPC latency

http://www.thesycon.de/deu/latency_check.shtml

moi aussi sa fait sa avec ma carte de son Sound Blaster X-Fi Surround 5.1 & mon logitech x-540

jai deja fixer le probleme avec un window update ! depuis peu c'est revenu donc je vais formater

Je croit que c'est des conflicts entre drivers mais je ne suis pas sur !

essais un window update bonne chance

C'est bon, merci pour vos conseille, j'essaie ça!

J'ai vérifié les updates, y'en avait pas.

Sinon, je roule le test de DPC et pour le moment, toujours du 100 us sauf au 3 sec où cela monte à 600 us, mais ça reste dans le vert...

j'vais retourner jouer et voir si cela affecte dès que ça bug.

Edit: Malgré le bug, le DPC reste exactement le même, donc je ne crois pas que ce soit cela

Siboire moi je suis atteint de DPC latency 1600 quand je rouvre MSI AFTER BURNER le song qui FUCK et se replace après ............

Je pense c'Est a cause d'un driver mon problème je vais faire des test! merci sector-z pour le lien

La version plus avancer est ici Mi7 http://www.resplendence.com/latencymon

Le lien est mort.

re essais, au fait si vous avez Windows 8 seulement le deuxieme programme fonctionne pour l'instant correctement.

J'ai fais le test moi aussi...J'sais pas trop ce que ça veut dire, donc je vous mets l'image de mon test après 9 min...

Je suppose que le rouge, c'est pas bon hein?



J'dois faire quoi?

Non toi ses bon, ta du déplacer ton curseur entre temps ou ouvrire quelque chose le temps de faire start et pause. Le logiciel te dit bien que tes ok .

Citation :

Report view

The report view displays a conclusion of the suitability of your system for playing real-time audio at the top. If the execution times of all DPC and ISR routines stay below 2000 µs (microseconds), your system is considered suitable for handling real-time audio without dropouts. If some routines have execution times between 2000 µs and 4000 µs, your system is considered doubtful. If ISR or DPC routines are detected to execute for longer than 4000 µs, a system is considered unsuitable for handling real-time audio. Note that these numbers are just chosen arbitrarily. For optimal midi to audio latencies, buffer sizes of a sound card and driver should be set to very low values then only very low execution times of DPCs and ISRs become acceptable.

The report view will display:


•highest measured DPC execution time
•the driver that was executing the longest executing DPC routine
•frequency of DPC executions (divided in execution time categories)
•highest measured ISR execution time
•the driver that was executing the longest executing ISR routine
•frequency of ISR executions (divided in execution time categories)
•highest measured hard pagefault resolution time
•the process in which the hard pagefault occurred that took the most time to resolve
•frequency of hard pagefault hits




Selecting CPUs

On a multi processor system, LatencyMon offers the option to exclude one or more CPUs from being measured by selecting them from the options menu. For a complete analysis you should select all available CPUs. This feature may be useful to check which CPUs are connected to interrupts and verify how ISRs and DPCs are distributed among available processors. Also it may allow you exclude certain processes to which you have assigned a certain affinity.




High DPC or ISR routine execution times: how to proceed

If LatencyMon reports the DPC and ISR execution times to be too high, you should take a look at the responsible drivers. It may be that these drivers belong to a device that is non-critical for the operation of your computer. If for example tcpip.sys or ndis.sys is reported as the culprit, chances are the problems are caused by your wireless network adapter, if you have one. You could consider disabling the WiFi adapter and receive internet via an Ethernet cable. You can disable devices by right-clicking on My Computer and selecting Device Manager, right-clicking a device and selecting disable. You should run LatencyMon again to check if the situation has improved, there might still be another device or driver causing audio latencies.

Note that if high latencies have been reported to be caused by drivers which are critical for the operation of your computer such as motherboard drivers, there may be nothing you can do to get your computer suitable for processing real time audio.




Hard pagefaults: how to proceed the investigation

We believe that hard pagefaults are the most common cause of audio dropouts. The effect of a program hitting hard pagefaults while playing audio is usually dramatic. One problem with pagefaults is that they often come in groups so that a row of pagefault causes interruption of the audio stream. Another problem with them is that unlike ISRs and DPCs, putting in more processors into a system will not help you to avoid them. Page faults need to get resolved immediately and any thread that hits them is suspended until the pagefault is resolved. Hitting a hard pagefault on a page file or memory mapped file that is backed on a drive that is spun down because of a power feature may interrupt a program for several seconds until it can proceed.

If hard pagefaults are reported but no high DPC and ISR execution times you should investigate if these are the cause of audio dropouts. The difficulty with pagefaults is that they are common to occur so it's hard to find out if they are the cause of audio dropouts and stutter. In order to find out if pagefaults are the cultprit you need to know that the pagefault occured in the process responsible for producing audio and also while it was producing audio.

To verify that the hard pagefault occured in your audio program, take the following steps:

•Stop the monitor by clicking the stop button
•Click the Processes tab
•Now click on the Number of pagefaults column so the view gets sorted
•Now look for the process name of the audio application that was running and see if it was hit

Hard pagefaults should only be considered a problem if you can hear they are actually interrupting the audio stream. It is common for any program which uses a lot of memory to hit hard pagefaults. By observing the Processes view while audio is playing you can find out if hard pagefaults are being hit while audio is playing. If you found out that pagefaults are the cause of audio dropouts you should read the next section on how to avoid them.




How to avoid hard pagefaults

If you have concluded that hard pagefaults are the cause of audio dropouts, you can do any of the following to resolve the problems:


•Close down unnecessary applications which consume a lot of RAM
•Close down unnecessary service applications which consume a lot of RAM (the Search Indexer service is notorious)
•Increase the amount of RAM in your system
•Increase the working set of the audio application, only an option if you are the author of the software.
•Make sure audio data is paged-in (resident). Pages of memory are swapped out based on their use counts. If you use Windows for live playing, do a silent run of your software synthesizer. After changing patch on a sampler, touch all keys so that all memory it uses is paged-in to avoid embarrasing scenes.
•Disable the pagefile altogether. You can disable the pagefile by right-clicking My Computer and selecting Advanced System Settings->Advanced->Performance Settings->Advanced->Virtual memory->Change. Note that if you have no pagefile, the system can run out of memory if not enough memory is available. Also the system will no longer create crash dump files in case of a system crash.




Other causes of audio dropouts, pops and clicks

This section summarizes a list of other possible causes of audio dropouts, clicks and pops. If there are no high DPC or ISR execution times reported and hard pagefaults are not the cause of the problems you should consider these.

Audio buffer sizes
To reduce midi to audio latencies (that is the time between a key press on a MIDI keyboard and the occurrence of the actual sound), the audio buffer size of the audio driver should be as low as possible. But it must be supportable by the system. The acceptable limit of 2000µs for DPC and ISR execution times has been arbitrarily chosen. The lower your audio buffer size, the lower the tolerance for long execution times of DPC and ISR routines and page fault resolution. In order to retain a system that does not drop out you may need to increase your audio buffer size. So it might be that your system is not suitable for low midi to audio latency but you might still be able to find an acceptable balance that works.


CPU overloading
If a software synthesizer or effect requires too much execution time to compute its audio buffers in time it will cause stutter, clicks or pops. This can for example easily happen when playing too many voices or too many virtual instruments at the same time in a software synthesizer.

Thread Contention
If there are simply too many threads competing for CPU time an audio program may not get enough attention from the scheduler to process its audio buffers. Threads are selected based on a priority scheme but if there are multiple programs running with threads running at high priority, there may just be not enough CPU time available for the audio software to fill its buffers in time. Threads responsible for producing audio normally run at highest or real-time priority. Competing threads with a lower priority may still get scheduled because the balance set manager which is part of the operating system will boost threads with a lower priority to avoid thread starvation. Closing down unnecessary programs, services and getting more CPUs will help you.

Bugs in audio software
Bugs in audio software can of course create all sorts of artifacts including pops and clicks. If problems are limited to one particular audio program or plugin, chances are it's the program's fault. It also deserves mentioning that exception handling requires a lot of processing power and causes interrupts to occur on the processor on which it's running. A very common example is an audio plugin program which does not mask off floating point exceptions so that each division by zero or other forseeable problem causes an interrupt to occur.

Bugs in hardware or audio drivers
Bugs in hardware and audio drivers may also be responsible for causing stutter, pops and clicks.






Considerations

All execution times are calculated based on a fixed CPU clock speed which is listed. For most accurate results you should disable variable clock speed settings in your BIOS setup such as Intel TurboBoost, SpeedStep and AMD Cool N Quiet.

Because of the nature of the software, it does not make sense to run this program inside a virtual machine if you wish to obtain useful measuring results.

Finalement, il me dit quoi faire ...Test après 16 min.



Bon, j'ai les indications de mes problèmes. En gros, ce serait un manque de jus ou un problème de drivers?

Merci!

Quand il parle de power management, ça veut dire quoi?

Là, je cherche pour des drivers pour ma carte son. Est-ce que de tester la carte son intégrée de ma mobo pourrait donner des résultats différents?

Creative on sorti un update de leur driver cette semaine au fait . Pour ton info regarde je tes copier le texte de comment trouver ce qui peux engendrer sa. Moi sous mon laptop j'avait 4 programme et sur le pc des enfant c'était le drivers audio et USB 3.

Citation :

CPU Power Management Issues--------------------------------------------------------------------------------

Many users have reported that they suffered latency problems due to CPU power management issues. Several problems can be solved by disabling variable speed related settings in the BIOS setup program such as:


•Intel Speedstep technology
•Intel TurboBoost technology
•AMD Cool N Quiet technology
•CPU C-states

It may be that these problems are caused because these power features cause the system to temporarily operate in SMM (System Management Mode). It may also be these latencies are caused by CPU bugs related to these features. Check out the following page regarding SMIs and CPU stalls.

Good, merci Sector!

J'vais m'installer ben confo et lire ça!

Sector-z a écrit:

Citation :

CPU Power Management Issues--------------------------------------------------------------------------------

Many users have reported that they suffered latency problems due to CPU power management issues. Several problems can be solved by disabling variable speed related settings in the BIOS setup program such as:


•Intel Speedstep technology
•Intel TurboBoost technology
•AMD Cool N Quiet technology
•CPU C-states

It may be that these problems are caused because these power features cause the system to temporarily operate in SMM (System Management Mode). It may also be these latencies are caused by CPU bugs related to these features. Check out the following page regarding SMIs and CPU stalls.

Est-ce qu'un Overclock pas encore super stable pourrait en créer? Sinon, toutes les options de boost de CPU ou de cool'n Quiet sont désactivés sur mon pc.

Non je ne pense pas exemple pour moi mon logiciel de monitoring de température en était une des cause sur mon laptop. C'est très long parfois le plus facile est d'aller dans le gestionnaire de périphérique et de désactiver chacun et de refaire le test après, comme sa si ses la carte réseaux, ou la carte de son, tu va pouvoir le détecter rapidement, si ses logiciel, ba tu désactive tout ce qui est pas essentiel dans les service et processus en cour afin de trouver le bon.

quand tu fait le test exemple deux minute et que tu le lance et touche a rien et le stop, ta encore cette barre qui va dans le rouge ?

Sector-z a écrit:

Non je ne pense pas exemple pour moi mon logiciel de monitoring de température en était une des cause sur mon laptop. C'est très long parfois le plus facile est d'aller dans le gestionnaire de périphérique et de désactiver chacun et de refaire le test après, comme sa si ses la carte réseaux, ou la carte de son, tu va pouvoir le détecter rapidement, si ses logiciel, ba tu désactive tout ce qui est pas essentiel dans les service et processus en cour afin de trouver le bon.

quand tu fait le test exemple deux minute et que tu le lance et touche a rien et le stop, ta encore cette barre qui va dans le rouge ?

Ouep J'vais encore tapper le rouge.

Exemple le mien, j'avait un vrai probleme, je ne pouvais pas jouer en ligne a des jeux qui demandais beaucoup de frame rate, j'avait des spike lag, ennemis qui se téléporte ou encore je voyais les autre joueur foncer dans les mur et continuer de foncer dedans des 2 seconde par si par là. Mon ping était pourtant de 60 et mon frame rate entre 60 et 45 minimum alors c'était autre chose et j'ai découvert ce que c'était finalement, j'était bien victime de DPC latency.

Mouin, j'suis pas si pire que ça...J'ai des troubles de son et c'est pas mal tout...Peut-être quelques lag dans genre Far Cry 3, mais j'peux pas dire. Bref, j'vais faire des tests à temps perdu en suivant tes conseils

Merci

La principale probleme que sa donne avoir du DPC latency ses le son que tu perd avec la video désynchronisation et autre coupure, a ce que j'ai pus comprendre alors ya bin des chance que ton problème sois régler après.

J'espère bien, j'veux juste jouer à Far cry lol (j'ai déjà fait le tour une fois pis j'me le refais encore. Y'a vraiment pas eu beaucoup de jeux où j'ai autant accroché.

En tout cas, pour revenir au problèmes, on a mis le doigt sur quelque chose, le seul hic est que les possibilités sont énormes. Un peu comme si le seul signe et symptôme que j'ai est nausée/vomissement et qu'il faut que je trouve le pourquoi du comment avec celle seule info...Impossible. Alors, on creuse!

Edit: Le AMD dual-core optimizer sert à quoi? J'l'ai désactivé pour refaire un test et ça l'a rien changer, mais j,ai aucune idée à quoi ça sert pareil lol

Après 5 minute une fois régler