[Stk] crtsine.cpp gives RtApiAlsa: error starting callback thread!

[Charlls Quarra]

ok this is a bit strange (maybe not), i do:
 
 $ ./configure --disable-alsa --enable-jack --disable-oss
 checking for gcc... gcc
 checking for C compiler default output file name... a.out
 checking whether the C compiler works... yes
 checking whether we are cross compiling... no
 checking for suffix of executables...
 checking for suffix of object files... o
 checking whether we are using the GNU C compiler... yes
 checking whether gcc accepts -g... yes
 checking for gcc option to accept ANSI C... none needed
 checking for g++... g++
 checking whether we are using the GNU C++ compiler... yes
 checking whether g++ accepts -g... yes
 checking whether we are using the GNU C++ compiler... (cached) yes
 checking whether g++ accepts -g... (cached) yes
 checking how to run the C preprocessor... gcc -E
 checking for egrep... grep -E
 checking for ANSI C header files... yes
 checking for sys/types.h... yes
 checking for sys/stat.h... yes
 checking for stdlib.h... yes
 checking for string.h... yes
 checking for memory.h... yes
 checking for strings.h... yes
 checking for inttypes.h... yes
 checking for stdint.h... yes
 checking for unistd.h... yes
 checking fcntl.h usability... yes
 checking fcntl.h presence... yes
 checking for fcntl.h... yes
 checking sys/ioctl.h usability... yes
 checking sys/ioctl.h presence... yes
 checking for sys/ioctl.h... yes
 checking sys/time.h usability... yes
 checking sys/time.h presence... yes
 checking for sys/time.h... yes
 checking termio.h usability... yes
 checking termio.h presence... yes
 checking for termio.h... yes
 checking for unistd.h... (cached) yes
 checking for an ANSI C-conforming const... yes
 checking for size_t... yes
 checking whether time.h and sys/time.h may both be included... yes
 checking whether byte ordering is bigendian... no
 checking for RAWWAVE_PATH argument...
 checking for INCLUDE_PATH argument...
 checking whether to compile realtime support... yes
 checking for cos in -lm... yes
 checking for pthread_create in -lpthread... yes
 checking for gettimeofday... yes
 checking for select... yes
 checking for socket... yes
 checking whether to compile debug version... no
 checking build system type... i686-pc-linux-gnu
 checking host system type... i686-pc-linux-gnu
 checking for audio API... checking for snd_pcm_open in -lasound... yes
 using ALSA
 checking whether gcc needs -traditional... no
 checking for strstr... yes
 configure: creating ./config.status
 config.status: creating src/Makefile
 config.status: creating projects/demo/Makefile
 config.status: creating projects/effects/Makefile
 config.status: creating projects/ragamatic/Makefile
 config.status: creating projects/examples/Makefile
 config.status: creating projects/examples/libMakefile
 
 
 After that i go to src/ and do make, look the macros being passed
 
 $ make
 g++ -O3 -Wall -g -D__GXX__ -I../include -D__LITTLE_ENDIAN__  -D__LINUX_ALSA__ -D__LINUX_ALSASEQ__ -DRAWWAVE_PATH=\"../rawwaves/\" -c Stk.cpp -o Release/Stk.o
 g++ -O3 -Wall -g -D__GXX__ -I../include -D__LITTLE_ENDIAN__  -D__LINUX_ALSA__ -D__LINUX_ALSASEQ__ -DRAWWAVE_PATH=\"../rawwaves/\" -c Generator.cpp -o Release/Generator.o
 g++ -O3 -Wall -g -D__GXX__ -I../include -D__LITTLE_ENDIAN__  -D__LINUX_ALSA__ -D__LINUX_ALSASEQ__ -DRAWWAVE_PATH=\"../rawwaves/\" -c Noise.cpp -o Release/Noise.o
 make: *** [Noise.o] Interrupt
 
 
 It's maybe a problem in the configuration step?

"Gary P. Scavone" <gary at ccrma.stanford.edu> escribió: Hi Charles,

Perhaps you can recompile with only Jack support and see what  
happens.  Any error reports from STK or RtAudio would be useful.

Regards,

--gary

On 9-Feb-06, at 10:41 PM, Charlls Quarra wrote:

>
> Yes, jackd is running before starting the prog, i checked that the  
> samplerate were teh same just in case. other examples like  
> sineosc.cpp and foursine.cpp work ok, so the problem seems to be  
> the jack hook. the jack console doesnt report anything relevant,  
> besides a couple of xruns
>
> "Gary P. Scavone"  escribió: Hi Charlls,
>
> If you compile for all options, the order of priority is: Jack, ALSA,
> OSS.
>
> If you indeed have Jack support compiled in, then you need to have
> the Jack server running _BEFORE_ starting your application.
>
> Regards,
>
>
> ¡Llamá a todo el mundo con las mejores tarifas!
> Comprá tus tarjetas de llamadas en tres simples pasos
> en Yahoo! Telefonía



		
---------------------------------
 1GB gratis, Antivirus y Antispam
 Correo Yahoo!, el mejor correo web del mundo
 Abrí tu cuenta aquí
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/stk/attachments/20060210/5033daf1/attachment.html>