[Home]

Summary:ASTERISK-08027: [patch] wav49 format generates 50% compatible files with Windows Media Player
Reporter:gchrist (gchrist)Labels:
Date Opened:2006-10-30 07:57:52.000-0600Date Closed:2007-01-18 17:26:06.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) 20061112__bug8248.diff.txt
( 1) not_ok.wav
( 2) ok.wav
Description:Hi,
When playing a wav-format (( low compression),(wav49-format?)) file with Windows Media Player, it plays the file and then sometimes bombs out with an error about how the file is corrupt or unsupported. If you listen to the file in wavepad you will hear the whole file, in Media Player the last 2-3 sec. is missing (not played). The file is recorded with monitor function. The problem is reproduceable in Asterisk version 1.2.4 til 1.2.13.

The problem is earlier reported ( and fixed) in bug 254, but the problem still exist

****** ADDITIONAL INFORMATION ******

Error dialog: "Windows Media Player cannot play the file. The file is either corrupt or the Player does not support the format you are trying to play."

Clicking on More Information gives "0xC00D1199: Cannot play the file" and a fair bit of troubleshooting stuff.

The problem is earlier reported ( and fixed) in bug 254, but the problem still exist
Comments:By: Jason Parker (jparker) 2006-10-30 10:40:06.000-0600

wav49 is gsm format.  This is certainly not a bug.

By: gchrist (gchrist) 2006-10-31 02:24:34.000-0600

Yes, I know that wav49 is GSM format, but that doesn't explain why some files recorded in this format will play OK in MediaPlayer and others end with an error, or am I incorrect?

File with the error is attached as well as one that's OK



By: Tilghman Lesher (tilghman) 2006-11-12 21:28:33.000-0600

Please test this patch.  What this does is to ensure that there are always an even number of frames that constitute a wav49 file.  I suspect an odd number of frames causes this issue.

By: gchrist (gchrist) 2006-11-13 07:08:38.000-0600

I've added the things you wrote, but it doesn't seem to help.
In the last couple of weeks I've been using the mixmonitor option instead of the monitor option and it has lowered the volume of broken files a lot but the problem still exist.



By: Anthony LaMantia (alamantia) 2006-11-17 12:39:37.000-0600

i can confirm that the file "not_ok.wav" file fails in windows media player at the 13 second mark.

By: gchrist (gchrist) 2006-12-20 01:56:58.000-0600

For a while I've been using mixmonitor instead of monitor and this seems to "solve" the problem for me.

By: Anthony LaMantia (alamantia) 2006-12-20 07:31:07.000-0600

i have been unable to reproduce the invaid wav49 files using monitor on my system then importing them into WMP. all of the files are playing fine at the moment.

i do have some questions regarding the issue.

when asterisk was producing these bad files were you getting any errors/warnings/notices sent to your logs or the console?

also, how often was this problem popping up on your system?



By: Anthony LaMantia (alamantia) 2007-01-11 17:17:46.000-0600

after testing this about 10 times with monitor all of the generated files still play 100% fine in windows media player and the structure of the files also checks out.
gchrist, can you respond to my previous questions?

By: Anthony LaMantia (alamantia) 2007-01-18 17:26:05.000-0600

gchrist, please reopen this issue if you are still having problems with wav49