winmm wave recording is supposed to be supported, at least at the low-level wave API level. Maybe less so at the MCI level, though,
support at the MCI level should be more or less ok... (at least the Macadamiam folks did a great effort there)
and not supported at all yet in the DirectSound layer. What kind of API does it
use to record these sounds? You don't say what kind of app it is...
post the output of runnnig with the -debugmsg +wave,+mciwave,+dsound would help us pinpointing the issue
A+ --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle
On Mon, 5 Feb 2001, Eric Pouech wrote:
winmm wave recording is supposed to be supported, at least at the low-level wave API level. Maybe less so at the MCI level, though,
support at the MCI level should be more or less ok... (at least the Macadamiam folks did a great effort there)
and not supported at all yet in the DirectSound layer. What kind of API does it
use to record these sounds? You don't say what kind of app it is...
Yeah, I know I didn't say what kind of app it was...I was really just looking for the status of sound recording support.
The app is the "COMM1 Radio Simulator" for VFR flight. It's a tool that allows pilots (like myself) to practice their radio communication skills. It's target audience is either newbie pilots or rusty pilots (like myself) who haven't flown in a few years. Essentially, the program presents the pilot with some ATC scenerios and it records the pilot's responses. Afterwards, the pilot can compare his responses to an "expoert" (a proficient pilot). I would figure that it's not a terribly difficult program to write. In addition, it works on both Mac and Windows (two separate binaries, same data files), so I figured it requires pretty generic functionality and is not tightly bound to MS. Sounded like a good candidate to try out on wine :)
Recording is the only thing that doesn't work (unfortunately, it's a pretty necessary port in order for the program to be useful). The rest of the program seems to work flawlessly! Great job!
Unfortunately, I've reached a point where I need to go through the entire ATC sequences in order for it to be of any benefit. And that means I need to be able to record sound.
After using `strings` on a couple of the data files, it appears as though they are data files for Macromedia's Director 6.0. Looking at Macromedia's website (the faq for Director 8...i guess Director 6 is too old), it appears as though one can create executable binaries for both Windows and Mac that show your presentation. Which is what the Comm1 Radio Simulator appears to be a product of.
Unfortunately, that's the limit of my knowledge about the app at this point. I'm not a Windows guy. I'm definately a Unix/Linux person. This is the first Windows app I've ever bought. (I really don't want to have to go out and buy a copy of Windows and mess with installing it, just to run this one app). So I downloaded "Preview 1 of CodeWeavers Wine".
post the output of runnnig with the -debugmsg +wave,+mciwave,+dsound would help us pinpointing the issue
Unfortunately, that doesn't seem to be outputting anything to the console for me :(. Perhaps, I'm doing something wrong...I dunno at this point. I suspect it might be easier for me to download the source and compile a debug version of wine myself and see what info I can get out of the app and what it is it might be doing.
I'll play with it a bit more and let you guys know what I find out. thanks, tom
-- "Mongooses are famous for their snake-fighting ability, and are almost always victorious because of their speed, agility, and timing and also because of their thick coat."
Unfortunately, that doesn't seem to be outputting anything to the console for me :(. Perhaps, I'm doing something wrong...I dunno at this point. I suspect it might be easier for me to download the source and compile a debug version of wine myself and see what info I can get out of the app and what it is it might be doing.
this debug facility shall be turned on for every distribution you can try to tun it with -debugmsg +wave,+mciwave,+dsound,+msacm,+mmsys to see what gives A+
On Tue, 6 Feb 2001, Eric Pouech wrote:
this debug facility shall be turned on for every distribution you can try to tun it with -debugmsg +wave,+mciwave,+dsound,+msacm,+mmsys to see what gives
Well, I don't know what the difference between last night and tonight is, but tonight, I'm getting all kinds of debug spew (even with the arguments that didn't do anything for me last night). I ran the program with: -debugmsg +wave,+mciwave,+dsound,+msacm,+mmsys as you mentioned above and now have a nice long log file. I put the log file here: http://reality.sgi.com/flynnt/debug_log
The most interesting piece for me seems to be where it says:
fixme:mci:MCI_LoadMciDriver Couldn't load driver for type WAVEAUDIO. If you don't have a windows installation accessible from Wine, you perhaps forgot to create a [mci] section in system.ini
Then again, the reason I could find that interesting is that I have no idea what it means :-). It seems to be pointing out that I'm missing something, but I don't know if that peticular message is relevent.
The debug spew seems to end at the point in the program where I get to click on a phrase and record my voice. Then I go and click on the phrase, and I get that stupid dialog that says it can't record. I would have expected to see some debug messages at that point, but nothing came out. I quit the app just fine with no further debug messages.
does this help narrow things down any? -tom
-- "Mongooses are famous for their snake-fighting ability, and are almost always victorious because of their speed, agility, and timing and also because of their thick coat."
The most interesting piece for me seems to be where it says:
fixme:mci:MCI_LoadMciDriver Couldn't load driver for type WAVEAUDIO. If you don't have a windows installation accessible from Wine, you perhaps forgot to create a [mci] section in system.ini
Then again, the reason I could find that interesting is that I have no idea what it means :-). It seems to be pointing out that I'm missing something, but I don't know if that peticular message is relevent.
Hi Thomas,
I've seen this problem before. You probably don't have a system.ini file in your designated WINE 'c:\windows' directory. (This is configured in your ~/.wine/config)
Create a file in there called system.ini, and you need at least the following two lines:
[mci] waveaudio=mciwave.drv
You can see a sample in CVSROOT/documentation/samples/system.ini
-James
-- James Hatheway Software Designer - Macadamian Technologies, Inc. james@macadamian.com ~ http://www.macadamian.com
"Man könnte froh sein, wenn die Luft so rein wäre wie das Bier" "One could be happy if the air were as pure as the beer"
On Wed, 7 Feb 2001, James Hatheway wrote:
Create a file in there called system.ini, and you need at least the following two lines:
[mci] waveaudio=mciwave.drv
You can see a sample in CVSROOT/documentation/samples/system.ini
I think we're on the right track...
I tried with just the two lines you mentioned as my system.ini, and the app starts and then hangs. These are the messages at the bottom:
trace:mmsys:mciSendCommandA (00000001, MCI_GETDEVCAPS, 00000102, 4054637c) trace:mciwave:MCIWAVE_DriverProc (00000001, 40357F30, 0000080B, 00000102, 4054637C) trace:mmsys:mciGetDriverData (0001) trace:mciwave:WAVE_mciGetDevCaps (1, 00000102, 0x4054637c); trace:mmsys:mciSendCommandA => 00000000 trace:mmsys:mciSendCommandA (00000001, MCI_STATUS, 00000102, 40546374) trace:mciwave:MCIWAVE_DriverProc (00000001, 40357F30, 00000814, 00000102, 40546374) trace:mmsys:mciGetDriverData (0001) trace:mciwave:WAVE_mciStatus (1, 00000102, 0x40546374); err:ntdll:RtlpWaitForCriticalSection Critical section 0x400f320c wait timed out, retrying (60 sec) fs=0247
I also tried the system.ini from documentation/samples/. Same messages. Although I no longer get any messages about MCI_LoadDriver failing to load. Any ideas what else I could be missing? thanks, tom
-- "Mongooses are famous for their snake-fighting ability, and are almost always victorious because of their speed, agility, and timing and also because of their thick coat."
err:ntdll:RtlpWaitForCriticalSection Critical section 0x400f320c wait timed out, retrying (60 sec) fs=0247
I also tried the system.ini from documentation/samples/. Same messages. Although I no longer get any messages about MCI_LoadDriver failing to load. Any ideas what else I could be missing?
hard to tell from here. at least now the MM drivers are loaded and working the last message means there's a deadlock somewhere... this is really hard to debug remotely. can you try (and we'll see what can be done) to run with -debugmsg +relay and post the 200 before & after this err message. please compress the result. TIA
On Mon, 12 Feb 2001, Eric Pouech wrote:
err:ntdll:RtlpWaitForCriticalSection Critical section 0x400f320c wait timed out, retrying (60 sec) fs=0247
I also tried the system.ini from documentation/samples/. Same messages. Although I no longer get any messages about MCI_LoadDriver failing to load. Any ideas what else I could be missing?
hard to tell from here. at least now the MM drivers are loaded and working the last message means there's a deadlock somewhere...
Agreed. I looked into the code a bit this past weekend. I was really looking to just get a stack trace. Wasn't as easy as I thought it would be :). winedbg wasn't quite acting as I expected, but maybe I need to read the docs more carefully. I was able to get stack traces via gdb, but they didn't make a whole lot of sense (they weren't what I expected them to be)...plus I wasn't sure which of the three wine.bin processes was the one that was holding the lock and which one set the lock. I would just need to spend more time with it maybe.
this is really hard to debug remotely. can you try (and we'll see what can be done) to run with -debugmsg +relay and post the 200 before & after this err message. please compress the result.
Ok, will do. I could also put the result up on a webpage if you'd rather I didn't send a compressed file to the list.
Thanks for your help, tom
-- "Mongooses are famous for their snake-fighting ability, and are almost always victorious because of their speed, agility, and timing and also because of their thick coat."
-
Eric Pouech -
Eric Pouech -
James Hatheway -
Thomas Flynn