son décalé

[berbon]

Bonjour

 

Désolé je ne parle pas l'anglais mais j'aimerais beaucoup (je suis trop vieux pour m'y mettre).

 

Depuis la version 1.02 j'ai un problème de son décalé d'une dizaine de seconde pendant la mission

C'est très gênant surtout quand on essaye d'ouvrir une porte

 

Je suis sous Linux Ubuntu 10.4

[Tels]

Google translate says:

 

Hello

 

Sorry I do not speak English but I would love (I'm too old for me to).

 

Since version 1.02 I have a problem of its lagged about ten seconds during the mission

It's very annoying especially when trying to open a door

 

I am running Linux Ubuntu 4.10

 

Answer:

 

Does it always happen at every door? If it happens only once, the likely reason is that your system needs to load the new textures that appear when you open the door. This can hardly be avoided, unless you get a faster harddisk and/or more memory.

 

Bonjour

 

Mon français est inexistant:)

 

Est-ce toujours le cas à toutes les portes? Si cela se produit qu'une seule fois, la raison probable est que votre système a besoin de charger les textures nouvelles qui apparaissent lorsque vous ouvrez la porte. Cela peut difficilement être évité, à moins que vous obtenez un disque dur plus rapide et / ou plus de mémoire.

 

(I wonder what Google did mangle it to

[STiFU]

From the "Frequently asked Questions"-article on the wiki: Try disabling EAX 4.0

 

Google translate:

De l'article "Questions fréquemment posées" sur le wiki: Essayez de désactiver EAX 4.0.

[OrbWeaver]

EAX isn't available on Linux as far as I know.

 

He said specifically the sound (son) is lagging, which could be a Linux/ALSA/PulseAudio configuration issue. I've never heard of a 10 seconds lag though.

[Tels]

EAX isn't available on Linux as far as I know.

 

Yep, so disabling it shouldn't help.

 

He said specifically the sound (son) is lagging, which could be a Linux/ALSA/PulseAudio configuration issue. I've never heard of a 10 seconds lag though.

 

Hm, yes that was missing from the translation. Changing Alsa <=> OSS might in that case. Never heard of a 10 second lag, tho.

[Serpentine]

There was someone else that spoke about extremely large delays on sound under Ubuntu shortly after TDM 1.00 release. I seem to recall that it was related to the audio backend. It's always strongly recommended to use OSS as the doom3 ALSA support is just an OSS wrapper anyway.

[OrbWeaver]

It's always strongly recommended to use OSS as the doom3 ALSA support is just an OSS wrapper anyway.

 

Are you sure about that? It looks like some of the audio-related settings refer specifically to alsa devices and the like (e.g. default, hw:0 etc).

 

I didn't know modern Linux distributions were even shipping with OSS enabled.

[Serpentine]

Are you sure about that? It looks like some of the audio-related settings refer specifically to alsa devices and the like (e.g. default, hw:0 etc).

 

Hmmm, yeah it looks like I was wrong, however due to ALSA being added only late after release I doubt it's as mature... As some distros include alsa-oss wrapper by default you could end up with this happening doom3 -> oss -> alsa oss wrapper -> alsa -> pulse alsa wrapper -> pulse -> output. In either case, it's more likely that it's Pulse's alsa wrapper which is actually the cause of this problem. So perhaps swapping between alsa<->oss might avoid that, else he may have to find a way to avoid/disable PulseAudio.

 

I didn't know modern Linux distributions were even shipping with OSS enabled.

 

Yeah, the whole OSS unfriendliness on the linux side of the fence was/is retarded. GPLtards are still feeling the fallout years later and the whole sound services selection are all still terrible, OSS was and still is essentially the only decently wide ranged and powerful way to do things unless you require easy abstraction (a bit like C++ really). Magic solutions like PulseAudio in this case are nothing but trouble in the long run :/

 

tl;dr my money is on PulseAudio being stupid.

[berbon]

Google translate says:

 

 

 

Answer:

 

Does it always happen at every door? If it happens only once, the likely reason is that your system needs to load the new textures that appear when you open the door. This can hardly be avoided, unless you get a faster harddisk and/or more memory.

 

 

 

(I wonder what Google did mangle it to

 

Non c'est valable dans la mission en entier

[OrbWeaver]

Yeah, the whole OSS unfriendliness on the linux side of the fence was/is retarded. GPLtards are still feeling the fallout years later and the whole sound services selection are all still terrible, OSS was and still is essentially the only decently wide ranged and powerful way to do things unless you require easy abstraction (a bit like C++ really). Magic solutions like PulseAudio in this case are nothing but trouble in the long run :/

 

I was under the impression that the OSS vs ALSA debate was long dead and buried. You're right about PulseAudio though, I think it would work great if everything used it, but when some things do and others don't it can be problematic.

[demagogue]

As some distros include alsa-oss wrapper by default you could end up with this happening doom3 -> oss -> alsa oss wrapper -> alsa -> pulse alsa wrapper -> pulse -> output. In either case, it's more likely that it's Pulse's alsa wrapper which is actually the cause of this problem. So perhaps swapping between alsa<->oss might avoid that, else he may have to find a way to avoid/disable PulseAudio.

 

This is what you need to translate to French. He probably just sees a flood of words and doesn't know what to translate and what's fluff.

 

So babelfish says:

Car quelques distros incluent l'emballage d'alsa-oss par défaut vous pourriez finir vers le haut avec ce doom3 de événement - > ; oss - > ; emballage d'oss d'alsa - > ; alsa - > ; emballage d'alsa d'impulsion [pulse] - > ; impulsion [pulse] - > ; rendement. Dans l'un ou l'autre cas, it' ; s plus probablement qui it' ; s Pulse' ; emballage d'alsa de s qui est réellement la cause de ce problème. Ainsi peut-être la permutation entre les alsaoss pourrait éviter cela, d'autre il peut devoir trouver éviter de manière pour/débronchement PulseAudio.

[i30817]

EAX isn't available on Linux as far as I know.

 

He said specifically the sound (son) is lagging, which could be a Linux/ALSA/PulseAudio configuration issue. I've never heard of a 10 seconds lag though.

 

If you use wine the problem goes away. Pulseaudio configuration for sure (wine probably merits some additional config work from the distro).