Search results for all lists

10000 messages found
Sort by
List: great-loop@lists.trawlering.com
From: cooke_w@bellsouth.net
 
Re: Mobile Bay Marinas Info Requested
Sun, Sep 12, 2004 4:13 PM
List: great-loop@lists.trawlering.com
From: ALloyd217@aol.com
 
Re: GL: Big(er) sailboat-Chicago to Mobile
Fri, Apr 29, 2005 7:03 PM
List: pjsip@lists.pjsip.org
From: Samer Faour
 
Re: [pjsip] Application crash on Windows Mobile 5.0
Tue, Feb 19, 2008 4:04 PM
ad el Solh Square 1107 - 2020 Email: smf18@aub.edu.lb ----------------------------------------------------------------
List: pjsip@lists.pjsip.org
From: Benny Prijono
 
Re: [pjsip] Application crash on Windows Mobile 5.0
Tue, Feb 19, 2008 5:05 PM
shoot this is to run the debugger and see where it stops. cheers, -benny
List: pjsip@lists.pjsip.org
From: Samer Faour
 
Re: [pjsip] Application crash on Windows Mobile 5.0
Tue, Feb 19, 2008 7:24 PM
y to improve it further. There is a delay of 1 or 2 seconds at times and audio dropouts as well. The CPU Utilization is low so that's not an issue. I did not find any audio underflows/overflows either. What else can I do? And anyway, how can I make the other codecs work? The current behavior is either crash of application (on pcma and pcmu) or a weird humm [very bad understandable voice] (for speex/8000,speex/16000,speex/32000, and ilbc). The clock rate is the default of 8000 Hz. ______________________________________ Samer M. Faour Computer and Communications Engineering American University of Beirut P.O. Box 11-0236/ 1461 Riad el Solh Square 1107 - 2020 Email: smf18@aub.edu.lb ----------------------------------------------------------------
List: pjsip@lists.pjsip.org
From: Benny Prijono
 
Re: [pjsip] Application crash on Windows Mobile 5.0
Thu, Feb 21, 2008 9:56 AM
OUNT 16 > > The sound quality is not very good and I want to try to improve it > further. There is a delay of 1 or 2 seconds at times and audio > dropouts as well. The CPU Utilization is low so that's not an issue. I > did not find any audio underflows/overflows either. What else can I do? > > And anyway, how can I make the other codecs work? The current behavior > is either crash of application (on pcma and pcmu) or a weird humm > [very bad understandable voice] (for > speex/8000,speex/16000,speex/32000, and ilbc). The clock rate is the > default of 8000 Hz. I tried the latest SVN with PocketPC 2003 yesterday and it seems to work just fine. I can make call using pcma, pcmu, and gsm fine. No crash or anything nasty. Couldn't try with speex or iLBC since my poor PDA is too slow for the codec. What's in your config_site.h? Make sure it includes to activate WinCE specific settings. cheers, -benny
List: pjsip@lists.pjsip.org
From: Roland Klabunde
 
Re: [pjsip] Application crash on Windows Mobile 5.0
Wed, Apr 23, 2008 12:25 PM
WSOLA for PDA's and get back > to you soon. Do you already have one? Regards
List: pjsip@lists.pjsip.org
From: Benny Prijono
 
Re: [pjsip] Application crash on Windows Mobile 5.0
Wed, Apr 23, 2008 4:09 PM
this a feature > > ;-) ). > > Confirmed. WSOLA is called. > > > > Let me create a configuration to disable WSOLA for PDA's and get back > > to you soon. > > Do you already have one? > Just committed in r1941. I added configuration to disable WSOLA (see PJMEDIA_WSOLA_IMP macro in pjmedia/config.h), and set the default to disabled for WinCE and Symbian. Thanks Benny
List: pjsip@lists.pjsip.org
From: Samer Faour
 
Re: [pjsip] Application crash on Windows Mobile 5.0
Fri, Apr 25, 2008 1:32 PM
mer ________________________________________ Samer M. Faour Computer and Communications Engineering American University of Beirut P.O. Box 11-0236/ 1461 Riad el Solh Square 1107 - 2020 Email: smf18@aub.edu.lb ----------------------------------------------------------------
List: pjsip@lists.pjsip.org
From: Benny Prijono
 
Re: [pjsip] Application crash on Windows Mobile 5.0
Fri, Apr 25, 2008 3:18 PM
GSM is currently the only codec working > on these PDAs. Any suggestions? > You didn't say if you've upgraded your source to the latest svn version. If you haven't done that, my only suggestion for now is to upgrade. But if you've done that, then perhaps you can run the application from the debugger and see where exactly the crash happens. Without this info it's very hard to pinpoint what's wrong. Cheers Benny