ah... probably now dialer is 'configured' to assume that ringtone is
just a second or so... thus every other second (if call is not dropped
yet) it sends a new notification to pulse to play the ring tone. ho ho
so there is no native way seems to me to
* provide natively long ringtone (at least
after reboot it plays but incorrectly, it stutter, and even sounds
like
multiple instances playing simultaneously. So, I wonder what is the
reason -- is that a feature or a bug
RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, stereo
44100 Hz
^^^ sample rate is
nah... that is though the first thing I thought -- pulse is there to
do resampling if needed. I think that my suspicion (said in my prev
email to the thread) is the root -- dialer's logic is a big weaked and
it doesn't really get idea either the sound has finished playing within
its timeout of
So I did a blind copy of my ringtone (you can sample it from
http://www.onerussian.com/tmp/v_mir_jiv.wav) by copying over
/usr/share/openmoko/sounds/ringtone_classy.wav
which is
RIFF (little-endian) data, WAVE audio, Microsoft PCM, 8 bit, mono 22050 Hz
whenever original was
RIFF (little-endian)
the mystery of effect 'multiple instances' is somewhat revealed.. pulse
audio indeed creates multiple inputs for some reason... I dunno why.
I converted that file to stereo using sox (thought it would resolve the
issue). converting to 44800 sampling rate was bogus since then pulse
reported that
5 matches
Mail list logo