Re: sound problem
Rein Klazes a écrit : > > Hi, > > Last nights cvs commits gives a problem with sound in Agent. It is the > ping played when new mail is received. The first time goes alright, > the second time it kills agent: could you send me the full -debugmsg +winmm,+wave,+msacm trace TIA
sound problem
Hi, Last nights cvs commits gives a problem with sound in Agent. It is the ping played when new mail is received. The first time goes alright, the second time it kills agent: | trace:wave:OSS_wodMessage (0, 0005, 42E12C74, 42E12CA4, 00030008); | trace:wave:wodOpen (0, 0x42e12ca4, 00030008); | warn:wave:OSS_RawOpenDevice Couldn't open out /dev/dsp (Device or resource busy) | err:wave:wodOpen ioctl can't 'SNDCTL_DSP_GETOSPACE' ! | trace:wave:OSS_wodMessage (1, 0005, 42E12C74, 42E12CA4, 00030008); | trace:wave:wodOpen (1, 0x42e12ca4, 00030008); | warn:wave:OSS_RawOpenDevice Couldn't open out /dev/dsp1 (No such device) | err:wave:wodOpen ioctl can't 'SNDCTL_DSP_GETOSPACE' ! | trace:wave:OSS_wodMessage (2, 0005, 42E12C74, 42E12CA4, 00030008); | trace:wave:wodOpen (2, 0x42e12ca4, 00030008); | warn:wave:OSS_RawOpenDevice Couldn't open out /dev/dsp2 (No such device) | err:wave:wodOpen ioctl can't 'SNDCTL_DSP_GETOSPACE' ! | wine client error:806fe00: sendmsg: Bad file descriptor And the wine returns to the prompt in the xterm from which it is started. Some other thread continues: | trace:wave:OSS_wodMessage (0, 0005, 42E12C48, 42E12C78, 00030008); | trace:wave:wodOpen (0, 0x42e12c78, 00030008); | warn:wave:OSS_RawOpenDevice Couldn't open out /dev/dsp (Device or resource busy) | err:wave:wodOpen ioctl can't 'SNDCTL_DSP_GETOSPACE' ! [these 4 messages repated 11 times] | trace:wave:OSS_wodMessage (1, 0005, 42E12C48, 42E12C78, 00030008); | trace:wave:wodOpen (1, 0x42e12c78, 00030008); | warn:wave:OSS_RawOpenDevice Couldn't open out /dev/dsp1 (No such device) | err:wave:wodOpen ioctl can't 'SNDCTL_DSP_GETOSPACE' ! [those too] | trace:wave:OSS_wodMessage (2, 0005, 42E12C48, 42E12C78, 00030008); | trace:wave:wodOpen (2, 0x42e12c78, 00030008); | warn:wave:OSS_RawOpenDevice Couldn't open out /dev/dsp2 (No such device) | err:wave:wodOpen ioctl can't 'SNDCTL_DSP_GETOSPACE' ! [and those] | err:ntdll:RtlpWaitForCriticalSection section 0x40875b7c "../../windows/user.c: |USER_SysLevel" wait timed out, retrying (60 sec) tid=08fc03c0 this happens sometimes. If so it is followed by an attempt to start the debugger. Any suggestions? Rein. -- Rein Klazes [EMAIL PROTECTED]
Re: MCI Question -- sound problem
> fixme:dsound:IDirectSoundImpl_SetCooperativeLevel
> (0x4283302c,1a3c,3):stub
> fixme:dsound:IDirectSoundBufferImpl_QueryInterface
> {279afa86-4981-11ce-a521-0020
dsound gets used...
> Warning: /halflife.wad not accessible from a DOS drive
this is stranger... did you start hl from its directory ? (you should)
> Well the game is having a differente behaviour than earlier today but i
> still have no sound at all. Ah! allright, if i launch the game without
> the -console parameter, i get the first screen errors:
>
> "Could not open MCI file for playback: 266: There is an undetectable
> problem in loading the specified device driver." that message is
> prompted twice and whenever i click on the OK option i get the Click
> sound played.
[snip]
> If i run the game with -debugmsg +mciwave i get the very same first
> screen error message
for this one, try with -debugmsg +mci (error seems to have occured
earlier
than I first thought)
> "Unable to initialize wavein. Trying DirectSound unable to initia li ze
> Wave input . You wont be able to speak to other players throught a
> microphone."
this is another part, current directsound implementation doesn't
supports recording... (used here...)
A+
--
---
Eric Pouech (http://perso.wanadoo.fr/eric.pouech/)
"The future will be better tomorrow", Vice President Dan Quayle
Re: MCI Question -- sound problem
> > > > I have been doing some winsock changes recently so I am interesteed >in this one. Can you tell me more precisely which version (date) of the >winsock works and the one that does not? > What happens with the one that does not work? Do you get any error >message that would give a hint about what goes wrong? > Well the recent post by Lawson Whitney should do. Thats the same kind of problems i had. i debugged wine with winegdb and found out Winsock wasnt returning any valid values at all. Its that same file date, Wine-20011004 which i downloaded in a .targz file from your last sources directory. Anyone has any news on my sound problem? =( Have a great day raddy > > >-- >Francois Gouget [EMAIL PROTECTED]http://fgouget.free.fr/ >In theory, theory and practice are the same, but in practice they're different. > > > > >
Re: MCI Question -- sound problem
On Sun, 21 Oct 2001, Francois Gouget wrote: >I have been doing some winsock changes recently so I am interesteed > in this one. Can you tell me more precisely which version (date) of the > winsock works and the one that does not? >What happens with the one that does not work? Do you get any error > message that would give a hint about what goes wrong? > > > -- > Francois Gouget [EMAIL PROTECTED]http://fgouget.free.fr/ > In theory, theory and practice are the same, but in practice they're different. Maybe a little excerpt from wine-users would do. Subject: Re: Forte Agent Socket Problems On Sat, 6 Oct 2001, Jason wrote: > Hi All, > > I'm a newbie to WINE, and for my first application I'm trying to set > up Forte Agent RedHat Linux (Roswell). I can run it fine (well, there > is a constant flow of error messages on my console, but the program > window still looks allright). But I can't connect to the internet. > This is the message I keep getting: > > fixme:winsock:_get_sock_fd handle 164 is not a socket (GLE 6) > fixme:winsock:_get_sock_fd handle 164 is not a socket (GLE 6) > > I got the latest rpm today, and upgraded the WINE binaries, and the > only configuration I did was to make the ~/.wine directory and edit > ~/.wine/config file to show my windows configuration, and filesystem > mapping. > > Anyone have any ideas? > Juno 4 had that problem with Wine-20011004, but if you get this, it is fixed in the current CVS. This is the ID of the patch that fixed it: ChangeSet ID: 1002311145503006032668054 CVSROOT:/opt/cvs-commit Module name:wine Changes by: julliard@wine2. 01/10/05 15:45:45 Modified files: server : named_pipe.c sock.c Log message: Added get_file_info support to named pipes and sockets to avoid breaking the get_handle_fd request. Patch: http://cvs.winehq.com/patch.py?id=1002311145503006032668054 Revision ChangesPath 1.5 +20 -1 wine/server/named_pipe.c 1.21 +20 -1 wine/server/sock.c I think. Lawson ---oof--- I just applied the first 9 patches in a batch, but that looks like the one that fixed it.
Re: MCI Question -- sound problem
On Sat, 20 Oct 2001, raddy wrote: [...] > Btw, ive downloaded the last source targz file from your site, and i was > unable to make Winsock support work at all, ive heard of another guy > that had the same problem, so i made him download the previous one and > worked as it did for me too. Please check that out. I have been doing some winsock changes recently so I am interesteed in this one. Can you tell me more precisely which version (date) of the winsock works and the one that does not? What happens with the one that does not work? Do you get any error message that would give a hint about what goes wrong? -- Francois Gouget [EMAIL PROTECTED]http://fgouget.free.fr/ In theory, theory and practice are the same, but in practice they're different.
Re: MCI Question -- sound problem
Eric, one last thing. If i got to the Sound Settings panel inside Counterstrike and unselect Hex support and A3D support and instead i just select High Quality Sound for fast computers, whenever i try to join a game the Wine console says: err:wave:wodDsCreate DirectSound flag not set This sound card's driver does not support direct access The (slower) DirectSound HEL mode will be used instead. i hope this might help. (oh, i ran the game just with -game cstrike -console parameters and wine just with the --winver parameter. ) raddy
Re: MCI Question -- sound problem
Eric, thanks a lot for your reply, here is the information you requested:
whenever i run my rad.sh script that does :
#!/bin/sh
wine --winver win98 -- HL.EXE -game cstrike -console
im getting no error on the first menu screen, its weird since the errors
i told you about showed up earlier this day. Anyways, when i join a
game, i have the following messages in my wine console:
first (when connecting to a server):
fixme:dsound:IDirectSoundImpl_SetCooperativeLevel
(0x4283302c,1a3c,3):stub
fixme:dsound:IDirectSoundBufferImpl_QueryInterface
{279afa86-4981-11ce-a521-0020
once connection is accepted, i get a :
Warning: /halflife.wad not accessible from a DOS drive
and then get some:
fixme:dsound:DSOUND_CreateDirectSoundCaptureBuffer
(0x4056ff20,0x4532553c): ignoring lpcDSCBufferDesc
fixme:dsound:IDirectSoundCaptureBufferImpl_GetCaps
(0x4284b6fc)->(0x4056fefc): stub
fixme:dsound:IDirectSoundCaptureBufferImpl_QueryInterface
(0x4284b6fc)->({b0210783-89cd-11d0-af08-00a0c925cd16},0x4056fef0): stub
Well the game is having a differente behaviour than earlier today but i
still have no sound at all. Ah! allright, if i launch the game without
the -console parameter, i get the first screen errors:
"Could not open MCI file for playback: 266: There is an undetectable
problem in loading the specified device driver." that message is
prompted twice and whenever i click on the OK option i get the Click
sound played.
So if i join a server i get the follo wing messages in the console:
when still connecting :
fixme:dsound:IDirectSoundImpl_SetCooperativeLevel
(0x429e3c6c,1a3c,3):stub
fixme:dsound:IDirectSoundBufferImpl_QueryInterface
{279afa86-4981-11ce-a521-0020
then the same:
Warning: /halflife.wad not accessible from a DOS drive
If i run the game with -debugmsg +mciwave i get the very same first
screen error message
i also have the menu sound. i get the same wad warning , etc..
If i run with +dsound, woha, i get LOTS of console message, kind of a
FLOOD. they dont seem to be errors at all, let me see if i can paste any
of them in here:
344
trace:dsound:DSOUND_MixerNorm (0x42837190) Best case
trace:dsound:DSOUND_MixOne new primary_mixpos=0, primary_advbase=0
trace:dsound:DSOUND_MixOne mixed data len=8192, still_behind=0
trace:dsound:DSOUND_timer completed processing
the game keeps loading..
and i get in Cstrike the following errors in the console:
"Unable to initialize wavein. Trying DirectSound unable to initia li ze
Wave input . You wont be able to speak to other players throught a
microphone."
and the console still flooded with messages.
Any ideas?
regards,
raddy
-
Re: MCI Question -- sound problem
> Ive been able to make counter-strike (half-life game mod) run perfectly > on my system, i have network support, opengl support and it all works > perfectly ...still, i have no sound. > > (forgot to say that no sound in ANY applications i run besides this game) do you mean that sound isn't working for any other linux app ? > I also copied all mci* files from a working Windows installation in > order to fix my problem but it seems it did not work. > > I have ALSA installed in a 2.4 kernel (soon 2.4.12). The errors the game > prompts me are all about not being able to use the MCI system for > playback ( i believe that means the mci wave driver for playing wav > files ). well, you should be more precise on the error (sent back by hl or by wine...) exact wording... did you get any message on the console ? > Another weird thing is that THERE IS some sound while browsing the game > menus (whenever i click in any menu option ) once i accept the error > messages. Still, when the real thing starts its all muted. AFAIR, HL uses different types of playback mechanisms depending on where it is (mciavi for splash screen, dsound for the game...) > A strange thing i noticed is that my ~/.wine/config file didnt have any > mci files in any of its config tags, but other people did, so i added > them. using the native and builting options: > > "mcicda.drv" = "builtin, native" > "mciseq.drv" = "builtin, native" > "mciwave.drv" = "builtin, native" > "mciavi.drv" = "native, builtin" > "mcianim.drv" = "native, builtin" you should add this too (or the native part) "msacm.drv" = "builtin" "midimap.drv" = "builtin" > So, im no wine expert at all, but it seems Wine isnt using *at all* my > windows 98 mci drivers located in wines c:\windows\system directory. well, as I wrote above, I don't remember HL using mci for playback but rather dsound in the game... so, it could simply mean that your issue is not MCI related but linked to another lib the best way to start would be to: 1/ give the exact error messages 2/ try running wine with -debugmsg +mciwave and check if something is spitted out (if not, -debugmsg +dsound should be a better alternative) A+ -- --- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle
MCI Question -- sound problem
Hello guys. I've had a problem for a week already, and ive tried #winehq but they told me to suscribe to winedevel list so here i am. The problem is with sound support. Ive been able to make counter-strike (half-life game mod) run perfectly on my system, i have network support, opengl support and it all works perfectly ...still, i have no sound. (forgot to say that no sound in ANY applications i run besides this game) I have no previous windows installation, so i grabbed a system.ini file from a working windows 98 system. I also copied all mci* files from a working Windows installation in order to fix my problem but it seems it did not work. I have ALSA installed in a 2.4 kernel (soon 2.4.12). The errors the game prompts me are all about not being able to use the MCI system for playback ( i believe that means the mci wave driver for playing wav files ). Another weird thing is that THERE IS some sound while browsing the game menus (whenever i click in any menu option ) once i accept the error messages. Still, when the real thing starts its all muted. A strange thing i noticed is that my ~/.wine/config file didnt have any mci files in any of its config tags, but other people did, so i added them. using the native and builting options: "mcicda.drv" = "builtin, native" "mciseq.drv" = "builtin, native" "mciwave.drv" = "builtin, native" "mciavi.drv" = "native, builtin" "mcianim.drv" = "native, builtin" Yes, in my override tag. So, im no wine expert at all, but it seems Wine isnt using *at all* my windows 98 mci drivers located in wines c:\windows\system directory. Please, id rather need instant help, the linux gamers require gamming hours daily. Btw, ive downloaded the last source targz file from your site, and i was unable to make Winsock support work at all, ive heard of another guy that had the same problem, so i made him download the previous one and worked as it did for me too. Please check that out. Feel free to check out my cave at : http://community.core-sdi.com/~raddy/ Have a nice day, raddy .-
