search for: xwave

http://bugzilla.mindrot.org/show_bug.cgi?id=125 jrj at purdue.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #192 is|0 |1 obsolete| | Attachment #355 is|0 |1 obsolete|

...list so any responses should be sent directly to me. ---------------------------------------------------------------------------- This communication (including all attachments) is intended solely for the use of the person or persons to whom it is addressed and should be treated as a confidential xwave communication. If you are not the intended recipient, any use, distribution, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately delete it from your system and notify the originator. Your cooperation is appreciated. -------------- ne...

...like a memory > allocation failure is the cause of the problem. Is the error easily > reproducible given the failed WAV file? Yes, always the same error - but only (no joke) on option -8 , not -9 or anything below. > Can you try trimming down the WAV file > (e.g., with a program like xwave) until you have the smallest chunk which > still triggers the failure? I tried to clip both ends of the original wav, but the error was only reproduceable, when I cut of the end of the wav. When i cut off only one second from the start of the soundfile verify did not complain anymore. So the &qu...

On 24-Jun-2001 Josh Coalson wrote: > hmm, I didn't see a bug report yet... can you make the .wav file > available for download? also, what version and options did you > use? this is interesting; I haven't seen a verify error in a > long time. > > Josh I also had this verify error encoding a wav I ripped from a CD. I didn't report this as it happended on flac

...state = 15:FLAC__ENCODER_MEMORY_ALLOCATION_ERROR This error appeared in the other report as well. It looks like a memory allocation failure is the cause of the problem. Is the error easily reproducible given the failed WAV file? Can you try trimming down the WAV file (e.g., with a program like xwave) until you have the smallest chunk which still triggers the failure? If you can make the WAV file (or a portion of it that exhibits the problem) available, that would be a great help. Note that there should not be any copyright issues associated with sending a small sample of a song. -- - mdz

On Mon, Jun 25, 2001 at 01:54:02AM +0200, kai@adminhell.org wrote: > On 24-Jun-2001 Matt Zimmerman wrote: > > Can you try trimming down the WAV file > > (e.g., with a program like xwave) until you have the smallest chunk which > > still triggers the failure? > I tried to clip both ends of the original wav, but the error was only > reproduceable, when I cut of the end of the wav. When i cut off only one > second from the start of the soundfile verify did not complain...

http://bugzilla.mindrot.org/show_bug.cgi?id=125 ------- Additional Comments From Brian.King at xwave.com 2002-11-16 07:20 ------- One of the suggested work-a-rounds was to set "UseLogin yes" in sshd_config. This does not work 100% of the time. SSH clients used in non-interactive modes still exhibit the problem. e.g.: ssh {hostname} "crontab -l >crontmp ; crontab crontmp&quot...

I am getting this whenever I start asterisk. Aug 15 15:03:58 WARNING[11754] chan_oss.c: Read error on sound device: Resource temporarily unavailable This is my sound card: Multimedia audio controller: Fortemedia, Inc Xwave QS3000A I am not sure... what I am doing wrong. Please help. Thanks,

I'm not sure if this is useful to anyone else, but around here people are insisting we use key-ed authentication with windows clients and Unix servers over SSH protocol version 2. I couldn't find a free windows client that would meet those requirements. The closest was PuTTY, but it would only use password authentication with SSH2. In the end, this means we will probably have to go with