Hi,
My college is trying to bring a sound from the remote computer to the WAP3 or NEO, unfortunately without results. Any advice?
Kind Regards,
David Klein
My first tests to comfirm the sound setting was with a WAP3 on WM 6.1, as well as a WAP-G2 running Windows CE 5.0. Both performed the same. The NEO's I used a WINCE 5.0 BATCH device, and a WINCE 5.0 PRO device. -sean
Sean M. Kennedy {Americas Help Desk Application Support}
Hi Sean,
Thanks for your answer. We've created a sound from the server that is hearable in the customers envorinment.
Only I don't have any clue why the NEO Core and Prof. CE handhelds are both our reproducing the sound thrue RDP from the server at the customers site and in our network it produces the handhelds default sound? Should be a difference somewhere in the servers settings..
David
Sorry, forgot to mention that this both are CE devices.
Hi repairalfa.
In the connection options, did you set "remote desktop sound" setting to "Play on this device"? -sean
Thanks for your reply. I had a look with my college and actually it does make sound, but it seems to be the handheld 'default sound' (found in settings, sounds, events) and not the original sound played on the server. I've changed the default sound to the sound 'ring'. We are quite satisfied with this solution. Is it however possible to play the exact sound that was produced on the server?
On the NEO with Windows CE 5.0 batch device, it is likely that the sound that will come from the unit will be a simple Beep. On NEO with Window CE 5.0 Professional, the sounds will work if you check the Volume & Sounds control panel applet and test sounds in the [Sounds] tab.
(If these sounds produce only a Beep, then the NEO can only beep for .wav sounds.)
If these sounds work, the RDP session can be configured to "Bring to this Computer" for Remote computer sound setting in [Local Resources] tab.
NOTE: This setting needs to be set in order to get sounds. Otherwise the default will just be the Keyclick sound when you are doing an entry. I have confirmed this to be opertational on a NEO running F300k firmware and using an RDP to a Windows 7 PC and testing the mixer volume setting. (Which goes Windows 7 'bing'.) -sean
Great work Sean, thanks, very detailed info,, - David
I would like to ask you one other question concerning this matter. What is the reason why the scanner beep sound is much louder than the other sounds produced on the NEO? The default sounds and the sound brought to the NEO thrue RDP are to soft in the envorinment where the handhelds are being used. Can we enhance the volume of the sound (apart from the setting in the volume & sounds control)?
Hi David.
I neglected to ask, but is the volume on the Citrix / RDP host turned up to maximum as well?
For the Default Beep, that is done via electronics on the NEO, And it is minimally configurable in Software for different tones. But all are the loudness set by the control to the beeper.
For units where Audio playout is available, the audio for the windows sounds and the scanner is shared.
I am unsure however for the NEO if the Scanner Beep, rather than the .WAV audio sound played during a scan is done differently, and uses different methods to produce the sound for the Audio playout capable version.
-sean
Interesting David.
Without having side-by-side config checks for the scanner, the RDP client software settings, and server settings, this is only speculation. But I am glad to hear that you have a solution for your customer. -sean
Another sound related problem.. a customer brought a WAP3 CE handheld that doesn't produce the correct scan beep anymore, only the default sound is played. I've checked registry, windows folder, sounds/scanner settings, etc., but I cann't find the reason why it doesn't work anymore? Any ideas?
When troubleshooting for "hard-to-find" system changes, one of the recommended tactics is to begin with Factory defaults. (.CLEAN Boot)
Of course this means wiping a large amount of settings that one configures when setting up a WAP3 and you don't have a Total Recall profile that backs up your settings. But for the scanner beep, when it has changed and you cannot determine what addition changed it. I find the fastest method is to do a .CLEAN boot, and then (while taking notes) checking for each additional software install and configuration.
Mind you, I am a developer so the Microsoft Visual Studio 2008 (pro) development environment has some useful remote registry/task-manager tools. I use the remote registry tool to scan the registry after each step.
In a nutshell, to diagnose, you need to figure out what changed. A .CLEAN boot is the starting point we recommend.
Hi Sean, thanks for the quick reply.. sorry, forgot to mention that I indead preformed a clean start and removed the auto total recall, but even after that it has the same symptons.
What happens when you turn the Volume down to Zero (nothing) in Sounds? -sean
Moved the "cursor" completly to the left (soft), afterwards no sound after scan.