Showing 6 results.
Items per Page 50
of 1
First Previous Next Last

CVP Forum

« Back to General Discussion

Problem when saving a record element to a wav file in Aud3.1

Combination View Flat View Tree View
Threads [ Previous | Next ]
Problem when saving a record element to a wav file in Aud3.1
Answer
2/21/03 11:16 AM
Hi,

We configure a record Audio element to save a wav file to disk in the following manner.

1) start with beep = true
Terminate on DTMF = False
Max Record Time = 180
Ftp in back ground = False
No Input timeout = 5s.

The wav file is saved to disk, however when we try to play the wav file in any of our windows players we do not hear anything?

Please can you assist us to find out why not?

Best Regards

michael.center@syntropy.com.au
Flag

RE: Problem when saving a record element to a wav file in Aud3.1
Answer
2/22/03 1:44 AM as a reply to Anonymous.
Hi Michael,

You should first verify that the voice browser you are using is saving the recording correctly. One quick way to check this is to use a RecordWithConfirm element. You should be able to hear the recorded audio in the confirm portion of the dialog.

If this works, can you tell me if the wav file actually any content (is the file > 0kb)? If so, is the file size changing for different length recordings?

Joe
Flag

RE: Problem when saving a record element to a wav file in Aud3.1
Answer
3/3/03 10:24 AM as a reply to Anonymous.
Hi
tested a recod with confirm element. It records correctly, plays it back correctly, however I cannot play the saved file back.
Error message form Windows media player:
Cannot play back the file. The format is not supported. (Error=80040265)

In addition to this is used the newest version of WinAmp anad it says the file is emtpy.

Hope for some help.

Thanx

david
Flag

RE: Problem when saving a record element to a wav file in Aud3.1
Answer
3/3/03 11:02 PM as a reply to Anonymous.
First, can you list:

  • The version of Audium you are using.
  • The voice browser you are using with version.
  • The Java application server you are using with version.
  • The operating system you are using with version.

All of these factors affect recording files and how they turn out.

By using the Record_With_Confirm element, you know that the voice browser is able to make the recording, so the issue is whether the problem is in transmitting the recording, receiving the recording, or playing the recording.

My suggestion is to do an experiment using the VoiceGenie developer node (developer.voicegenie.com). Make a simple application with just a Record element. See if a recording can be made with that voice browser and the same application server and operating system. If it works, you know the issue is with the way the data is transmitted from your voice browser. If it doesn't work, you can reasonably eliminate the voice browser as the issue.

Question: WinAmp says the file is empty. Is it? How big is it? Does the file come out larger when you make a longer recording or does it appear the same size no matter what the recording is?

Another potential source for the problem could be that the voice browser is sending the recording in a format other than what you are expecting, and you are saving it to a wav. That would explain the results you are getting. Check your voice browser documentation to make sure the formats jibe.
Flag

RE: Problem when saving a record element to a wav file in Aud3.1
Answer
3/4/03 3:23 AM as a reply to Anonymous.
Hi
used versions are:
Audium 3.1
Nuance VoiceWebServer 1.3
Nuance 7 Speech Recognition
Tomcat 4.0.6
Windows 2000 Professional

The Nuance VWS logs show that it saves the recording with an extension wav before it plays it back.

And yes, the file size varies in regard to the length of the recording. It is NOT 0KB, even if WinAmp tells me so.

I am using the above combination now for a couple of weeks and it works quite well, however I will have a look into the VoiceGenie developers node.

Which part does the Audium environment plays by handling the sound file ?

Thanx

David
Flag

RE: Problem when saving a record element to a wav file in Aud3.1
Answer
3/4/03 4:19 AM as a reply to Anonymous.
It is possible that the audio file is being recorded and sent correctly, but that your programs can't open up that format. Could you respond to this post and include one of those audio files as an attachment to the post, please?

We'll try to open up the file here.
Flag

RE: Problem when saving a record element to a wav file in Aud3.1
Answer
3/4/03 5:51 AM as a reply to Anonymous.
Hi
Unfortunately it looks like I am not allowed to attach files.
If you could send me your email to david.balzert@syntropy.com.au, I will send you one of my many recorded files.

Thanks for your help

David
Flag

RE: Problem when saving a record element to a wav file in Aud3.1
Answer
3/5/03 7:47 AM as a reply to Anonymous.
Hi
got your email yesterday and replied however got a message back from your server that the email address is not longer in use.

And I still havent figured out how to attach files to this messages.

If you have another mail address, that would be great.

Thanx

David
Flag

RE: Problem when saving a record element to a wav file in Aud3.1
Answer
3/14/03 4:52 AM as a reply to Anonymous.
David,

I listened to the file and converted it to a wav so you can hear. I used a program we have called Goldwave that opened up the file as Telephony, u-law (or A-law which it seems to actually be), 8000Hz sampling rate. I also had to boost significantly the volume as I heard only mumbles. When I did that the audio can be heard ok, though there is some static in the beginning and two weird beeps at the end.

The way you can tell what kind of file it is if you open the file in Wordpad. The file you sent me has a text header that gives information on the sample rate and stuff. After that it is just binary data representing the audio. If you open the converted one I have attached to this e-mail it begins with RIFF followed by WAVE. I have never seen the first audio file's format, though. It doesn't seem to be wav.

So, the data is being sent, received by the Audium Server, and saved, its just in an unrecognized format. Most likely the Audium Server is not the issue here, it is VWS.

So here are some suggestions for what you can do:

1) Look at the VWS documentation to see if you can change the way the recording is being encoded. This is probably controlled by a preference or setting on the VWS side.

2) Another thing to potentially look at is upgrading to Audium 3.2. We discovered issues with recording that was fixed in 3.2, though those came about only on Unix systems, not Windows. Its a long shot but worth a try.

3) If there are still issues, I can build you a static VoiceXML application that performs a recording and saves it, without the use of the Audium Server. If it works, then there is an issue with Audium software. If not, then it is defenitely either a browser issue or some other factor that is corrupting the data as it is being sent from the browser to the Audium Server.

Hope this helps,

P.S. For the interest of others on this forum, I will post the original file and the modified file here in a zip file. All future posts can now include attachments.
Flag