It allows apps to play all kinds of audio files. You can play, pause, change volume, etc. It is a toolkit for sound, so you can use it in apps that you write. Jeff Weiss
From: RicksPlace [mailto:[email protected]] Sent: Monday, January 13, 2014 8:50 AM To: [email protected] Subject: Re: [BULK] Possible bug in the GWAudiokit Hi: What does this kit do? I couldnt find it googling. Is it an app or is there more to it than that? Rick USA ----- Original Message ----- From: Jeff Weiss<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Sent: Monday, January 13, 2014 9:45 AM Subject: RE: [BULK] Possible bug in the GWAudiokit I have seen this also. I use the AudioKit in my music menu program, and It generates errors especially when I change volume. Jeff Weiss From: David [mailto:[email protected]] Sent: Monday, January 13, 2014 8:36 AM To: [email protected]<mailto:[email protected]> Subject: [BULK] Possible bug in the GWAudiokit Importance: Low I have installed and enjoy the GWAudiokit a lot. Yet, there seems to be something going on, that I hope can be fixed or explained. Many times, if I try to log off my user account, I am seeing an Error message on the screen. Usually, the logging off will happen before I can get the chance to read it in full. But today, I got it in full. It says that an error occured, and please see the GWAudiokit.Exe.log file for more info. OK, first we got that far, it was easy enough to open my user profile folder under WE, and find the mentioned log file. And that was a rather interesting one. It held no less than 64597 lines, and from all I could see, the lines were identical. Each line read: pythoncom warning: Too many results supplied - 2 supplied, but only 1 can be set What does this mean, and why do I get the error message whenever I try to log off; or, at least, just about whenever. Sometimes if WE has crashed, when I manage to restart it, this error will present itself as well. Hope the Author of the GWAudiokit will be able to look into this, and get things fixed. Besides, maybe a good idea to somehow restrict the size of that log file. It was more than 5MB in size by now. :)
