ACT sound issue.

Prugor · 12-24-2008, 03:15 PM

Problem - ACT isnt using any sound, from the beep to whatever you want to choose for windows. Windows sounds work, I can goto Youtube and look and listen to any newfag music video. Ive went to Windows Sound Panel and listen to the system sounds just fine.

Help. I want to time my auto attacks again.

EQAditu · 12-24-2008, 05:58 PM

If you cannot hear ACT attempt to use the default System "Beep" as it is labeled in most places, nothing can be done inside of ACT to solve that.

The most likely cause is you're in Vista and the Application volume for ACT is turned down or muted. I would say that except for the fact that not even the Vista Volume Mixer can reduce or mute the volume of ACT using the default windows beep nor can any setting in ACT change how it tries to use the default beep.

I would check for user error that you are not trying to use some non-existant WAV file instead of the system beep.

Prugor · 12-24-2008, 11:08 PM

Check the mixer, all volumes are set to max. All my notifications are set to system beeps. A friend said he had the same problem when his log file was too big, so I deleted all my log files. That did nothing. Currently, I just uninstalled the program and now I reinstalled it with a fresh download from the main site.

User error wise, the sound stopped working when there was a system update from ACT. Popup message that said download, install, cancel. Downloaded and installed, no sound since. Took a moment to remember, had to fumble through a few things that have happened this last week.

OS - Vista 64.

ACT's been working for the last 10 months, when I built the computer back in late Feb/March.

Alright, update.

I had to manually change all the trigger sounds using waves. The system beep notification was broken on update of the program. Which basically means, the default for ACT's idea of where the system beep notification wave is located in windows is probably wrong.

User Error - None.

Customer Support - None.

Program Error - Yes!

Next time someone has a problem, as from what I learned from you know, working with people, consider giving them suggestions on how to fix their problem, not tell them it's user error.

EQAditu · 12-25-2008, 12:34 AM

Quote:

Originally Posted by Prugor

Check the mixer, all volumes are set to max. All my notifications are set to system beeps. A friend said he had the same problem when his log file was too big, so I deleted all my log files. That did nothing. Currently, I just uninstalled the program and now I reinstalled it with a fresh download from the main site.

I can't imagine what too big a log file is unless you're on a partition that has a file size limit. Only one I've ever heard of is 4GB. The only way I can think of file size affecting anything is ACT's quickness at finding the current zone name... but ACT works backwards from the end, so the speed would be dependent on the zone change being far enough from the end to cause a delay.

Quote:

Originally Posted by Prugor

User error wise, the sound stopped working when there was a system update from ACT. Popup message that said download, install, cancel. Downloaded and installed, no sound since. Took a moment to remember, had to fumble through a few things that have happened this last week.

OS - Vista 64.

ACT's been working for the last 10 months, when I built the computer back in late Feb/March.

Alright, update.

I had to manually change all the trigger sounds using waves. The system beep notification was broken on update of the program. Which basically means, the default for ACT's idea of where the system beep notification wave is located in windows is probably wrong.

User Error - None.

Customer Support - None.

Program Error - Yes!

Next time someone has a problem, as from what I learned from you know, working with people, consider giving them suggestions on how to fix their problem, not tell them it's user error.

ACT's "idea" of where the system beep is the following:

Code:

System.Media.SystemSounds.Beep.Play();

As in it is 100% managed by Windows itself and why application based volume mixers cannot affect it. It tells Windows to beep, ACT does not do the beeping itself. I have used that line since v2.0.0 which was 18 months ago. Call it program error all you want, but I cannot fix it. I did not change anything regarding beeping in 18 months and isolated incidents do not guarantee a program error in computing. And complain about customer support all you want, but I doubt you are my customer. This is freeware.

I am bombarded every day with user errors on the silliest things and I still cannot discount that Vista is somehow configured wrong. Would you have preferred that I said nothing at all? I did try to help... I thought it would be Vista's application volume mixer, but that couldn't be the case since the system beep bypasses it. So as I wrote it, I discounted that thought but wrote it all anyways.

For giggles would you like me to show you the error log of a user with a similar problem? It's full of file not found messages for WAV files. Why couldn't I think your problem was the same?

Anap KaSplat · 12-25-2008, 10:31 AM

Quote:

Originally Posted by Prugor

Next time someone has a problem, as from what I learned from you know, working with people, consider giving them suggestions on how to fix their problem, not tell them it's user error.

Damn free software, eh?

From what I read, he suggested you check for user error, not outright tell you it was user error.

Good luck in future support with the awesome attitude you have.

Oh, and Happy Holidays.

EQAditu · 12-25-2008, 05:03 PM

@Prugor:
Given this thread, why did you also send me a direct Feedback ticket? Anyhow, the enclosed error log was extremely short, so it didn't really reveal anything if anything was ever recorded that could point at a cause.

Your symptoms seem to shift depending on when you talk about them. You said that there is no sound... but here, you said that you could get manually configured WAVs to work. Please at least be consistent in your reports... it gets very confusing otherwise.

EQAditu · 12-26-2008, 12:23 AM

I loaded up Vista on a VM and tried ACT there. Using the standard Windows API and using the optional DirectSound implementation, sound appears to act the same as it does on my normal Windows XP machines. The only thing that can affect ACT using the default system beep is the master volume slider or the Windows Sounds slider in the applications section. ACT's own volume sliders only affect WAV and TTS sounds from it's own DirectSound implementation. When the DirectSound implementation is disabled it cannot attenuate the volume as it is going through the Windows API which doesn't give such options. In either case the application volume slider for ACT will affect the WAV and TTS output but does not affect the system beep.

Casekil · 12-28-2008, 10:23 PM

I am having a sound issue with ACT as well. Though, it's boggled me as to where to even start to look for what could be wrong. I have configured ACT to do a system beep when the encounter has ended and a .wav file when my autoattack occurs via the doubleattack plugin. Everything will work fine for a random amount of time, ranging usually from 5 to 15 minutes, afterwhich, all sounds will stop broadcasting. ACT will continue to parse as normal. The only way to get the sounds audible again is to close down ACT and restart it.

I'm currently using Win XP x64 SP2 and a Xonar DX PCIe sound card.

Any advice?

EQAditu · 12-29-2008, 02:57 AM

I still cannot fathom the windows beep not working for any reason, but you could try to use ACT's DirectSound implementation for WAV files, or revert to the normal API if you're already using it. There will be a button on the far right of the Triggers/Sounds tab where you can select the audio device. If that button is greyed out, you might have to install this first.

Casekil · 12-30-2008, 01:09 AM

I have tried to switch between the 'Primary sound driver' and the option for my sound card in the Select Audio Device button. Same results, sound will eventually stop altogether until I close Act and restart it. Upon loading Act, I can sample the beeps by using the play button just to the left of the Select Audio Device button, and hear the beep fine, but after the sounds stop during gameplay, I no longer get any audible beep when pressing the play button. Same thing :/