After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 588532 - Error while playing newmessage.wav
Error while playing newmessage.wav
Status: RESOLVED FIXED
Product: ekiga
Classification: Applications
Component: Devices
GIT master
Other Linux
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
: 594432 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-07-14 11:39 UTC by Eugen Dedu
Modified: 2009-09-08 15:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
re-created wav (23.44 KB, audio/wav)
2009-09-08 12:39 UTC, Dominik Kopp
Details
recreated wav with silence at the beginning (57.89 KB, audio/wav)
2009-09-08 12:45 UTC, Dominik Kopp
Details
wave screenshot (97.87 KB, image/png)
2009-09-08 14:41 UTC, Dominik Kopp
Details

Description Eugen Dedu 2009-07-14 11:39:27 UTC
100% reproducible, both stable and master.  Also seen at http://mail.gnome.org/archives/ekiga-list/2009-May/msg00139.html

Go to Preferences->General>SoundEvents.  Press Play button for each of the 5 items.  All of the them are ok, except the last one, newmessage.wav, which shows an error dialog box (Error while opening audio output device Default) but still plays the sound.

I noticed that this .wav file is different than the others:
snoopy:~$ file /usr/share/sounds/ekiga-snapshot/*
/usr/share/sounds/ekiga-snapshot/busytone.wav:   RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono 8000 Hz
/usr/share/sounds/ekiga-snapshot/dialtone.wav:   RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono 8000 Hz
/usr/share/sounds/ekiga-snapshot/newmessage.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, stereo 44100 Hz
/usr/share/sounds/ekiga-snapshot/ring.wav:       RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, stereo 44100 Hz
/usr/share/sounds/ekiga-snapshot/voicemail.wav:  RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono 44100 Hz

A workaround is to change the type of the sound file, but the real solution is to see what happens...

There is something wrong in lib/engine/audiooutput/audiooutput-core.cpp...
Comment 1 Damien Sandras 2009-07-15 06:57:57 UTC
Or in PTLIB (which reads and plays the files).
Comment 2 Eugen Dedu 2009-09-07 22:02:54 UTC
*** Bug 594432 has been marked as a duplicate of this bug. ***
Comment 3 Dominik Kopp 2009-09-08 12:39:50 UTC
Created attachment 142693 [details]
re-created wav

With thanks to audacity.
Now the newmessage.wav won't bring an error message in ekiga.
(I did just an import/export)
Comment 4 Dominik Kopp 2009-09-08 12:45:31 UTC
Created attachment 142695 [details]
recreated wav with silence at the beginning

The same as before, but with a 0.2 sec silence at the beginning.
Decide yourself, which is better. (This one, can be played in vlc better. It makes no difference in ekiga.)
Comment 5 Eugen Dedu 2009-09-08 14:01:20 UTC
Your file has only one sound.  If you play the original with aplay, you have 2 sounds...
Comment 6 Dominik Kopp 2009-09-08 14:41:41 UTC
Created attachment 142701 [details]
wave screenshot

I'm sorry, but I don't hear any differences between the original and my version using aplay.

Even when I import the two files in two instances of audacity. (see screenshot)
- the top contains the original newmessage.wav
- the bottom contains the re-created newmessage.wav
=> There are no differences.

Would you mind viewing and playing the original newmessage.wav in audacity?
Do you hear any differences to aplay?
Comment 7 Eugen Dedu 2009-09-08 14:50:56 UTC
You're right, sorry.  There is a minor bug in vlc, it does not play the very beginning of the file.

So I commit the first version, without the 0.2 sec added, ok?
Comment 8 Dominik Kopp 2009-09-08 14:54:06 UTC
Right, it seems vlc has a bug.
I prefer the first version (without 0.2 sec), too.