Re: [ladcca] ladcca 0.4.0 aborts on startup : configuration problem??

[guenter geiger]

Hi,

You have to update the /etc/services file (this should be done
automatically at startup)

This reminds me that I wanted to clean up and send the changes I made
for the debian package in order to make these changes optional.
It's attached (its not very clean sorry, .. )

Guenter




On Tue, 13 Jan 2004, [iso-8859-1] Alex Timmer wrote:

> hello,
>
> this problem was first posted on planet-CCRMA mailinglist, but it seems
> packaging unrelated. please read on.
>
> i try to run ladcca 0.4.0 with jack 0.92. on startup of ladcca, both go
>  wild and the following messages fill my console:
>
>
> ladccad startup:
> =====
> [ guitar]$ ladccad -d temp/ladcca/
> Connected to JACK server with client name 'LADCCA_Server'
> Opened ALSA sequencer with client ID 129
> conn_mgr_start: could not look up service name: Servname not supported
> for ai_socktype
> [ guitar]$ loader_run: server closed socket; exiting
>
> jackd:
> =====
> 00:01:57.449 Audio connection graph change.
> 00:01:57.520 MIDI connection graph change.
> 00:01:57.522 MIDI connection graph change.
> 00:01:57.548 MIDI connection graph change.
> 00:01:57.570 MIDI connection graph change.
> **** alsa_pcm: xrun of at least 1.112 msecs
> 00:01:57.612 XRUN callback. (1)
> 00:01:57.779 XRUN callback. (2)
> subgraph starting at LADCCA_Server timed out (subgraph_wait_fd=24,
> status = 0, state = Triggered)
>
> **** alsa_pcm: xrun of at least 1.665 msecs
>
> cannot read event response from client [LADCCA_Server] (Connection
> reset by peer)
> bad status for client event handling (type = 8)
>
> **** alsa_pcm: xrun of at least 2.225 msecs
>
> 00:01:57.807 Audio connection graph change.
> 00:01:57.808 XRUN callback. (3)
> 00:01:57.811 MIDI connection graph change.
> =====
>
>
> p.s. normally i have no xruns at all, i run with a 512 buffersize.
>
> one other user from CCRMA confirms exactly the same error messages, but
> Fernando from CCRMA runs this setup without problems. he suspects its
> maybe something with services (/etc/services)? now i dont know anything
> about how this services works, but i do have an /etc/services file.
> grepping it does not match ladcca, jack or alsa.
>
> okay, i just had a look in /etc/services and it mentions ports. hmm,
> could ladcca have problems with the firewall running on the machine?
> i'm not sure what "ports" are all allowed and such...
>
> anyway, just guessing around here. i hope this is some good info.
> thanks, hope to get ladcca running soon.  :)
> ALEX
>
> ________________________________________________________________________
> Yahoo! Messenger - Communicate instantly..."Ping"
> your friends today! Download Messenger Now
> http://uk.messenger.yahoo.com/download/index.html
>
>
> _______________________________________________
> Ladcca-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/ladcca-devel
>

ladcca-0.4.0-services.patch
Description: Text document