[CLAM] SMSTools / Network Editor - crashes

[Jay LeBoeuf]

Hi Pau,

1)  I'm using the M-Audio AP 24/96.   Seems to have worked so far with most
of my other audio apps.

2)  Running ./AudioApplicationExample, I hear a wonderous sine tone from my
card's outputs.
      What's interesting is that when I hit enter to Terminate the app, I
receive the same error as when trying to play audio in SMSTools.

    [ets at localhost AudioApplication]$ ./AudioApplicationExample
    Press enter to terminate
    Scheduler set to Round Robin with priority 98...

    Press enter to terminate
    Scheduler set to Round Robin with priority 98...
    terminate called after throwing an instance of 'SndPcmError'
      what():
    Aborted
    [ets at localhost AudioApplication]$


Anything come to mind?
best,
-Jay



----- Original Message ----- 
From: "Pau Arumi" <parumi at iua.upf.es>
To: "Jay LeBoeuf" <jleboeuf at ccrma.Stanford.EDU>
Cc: <clam at iua.upf.es>
Sent: Monday, October 24, 2005 8:59 AM
Subject: Re: [CLAM] SMSTools / Network Editor - crashes


> Jay,
> This problem seems quite wierd.
> What sound card are you using?
>
> I recommend you to try the CLAM simple example that uses alsa:
> AudioApplicationExample
> in  CLAM/build/Examples/Simple/AudioApplication/
> and report what happens to the list.
>
>
> Pau
>
>
>
>
> En/na Jay LeBoeuf ha escrit:
>
> >Hi Xavier,
> >
> >I'm using PlanetCCRMA with FC3, and all seems well with other ALSA apps.
> >(AlsaPlayer, Audacity, etc)
> >
> >When SMSTools quits, it does output :
> >
> >          terminate called after throwing an instance of 'SndPcmError'
> >          what():
> >          Aborted
> >
> >The alsa highlights of my CLAM configure script seemed to indicate (to
me)
> >that all was working :
> >
> >    checking alsa usage specified... yes (default)
> >    checking alsa in sandbox... searching headers
> >    checking alsa/asoundlib.h for alsa in sandbox... no
> >    checking alsa header(s) found in sandbox... no
> >    checking alsa has pkg-config... yes
> >                    ...
> >    checking compiling, linking and running with alsa... ok
> >                    ....
> >    alsa         YES     SUCCESS      HAS_ALSA=1 , USE_ALSA
> >
> >
> >Is this helpful ?  Anything else you'd recommend?  (I rebuilt everything,
> >but with no luck)
> >thanks,
> >-Jay
> >
> >
> >----- Original Message ----- 
> >From: "Xavier Amatriain" <xavier at create.ucsb.edu>
> >To: "Jay LeBoeuf" <jleboeuf at ccrma.Stanford.EDU>
> >Cc: <clam at iua.upf.es>
> >Sent: Tuesday, October 18, 2005 4:29 PM
> >Subject: Re: [CLAM] SMSTools / Network Editor - crashes
> >
> >
> >
> >
> >>Hi Jay,
> >>
> >>You are probably right, it sounds like you have some problems with the
> >>ALSA configuration. Don't you get some sort of message saying something
> >>like "No Device available...". Is alsa well configured in your system?
> >>Do you have any program that might be blocking the ALSA driver while you
> >>are trying to execute CLAM? Did the output of the CLAM configure script
> >>tell you that you had ALSA correctly installed?
> >>
> >>Jay LeBoeuf wrote:
> >>
> >>
> >>>Hi All,
> >>>
> >>>I'm probably missing something simple.  CLAM, SMSTools, and the
> >>>NetworkEditor all seem to build without error.
> >>>
> >>>HOWEVER :
> >>>SMSTools crashes when I try to play any audio, after analyzing it.
> >>>Additionally, my machine locks and freezes when I tell the
NetworkEditor
> >>>to START.
> >>>(This occurs without any blocks,  or if I configure a simple spectral
> >>>processing block.)
> >>>
> >>>Is there a step to configure the CLAM Apps for ALSA that I'm missing?
> >>>
> >>>thanks again,
> >>>-Jay
> >>>