Re: configure.ac portability bug

hi jack!

sorry for the late reply, been busy otherwise.

yes, the patch works. please apply.

regards,

jörn

Jack O'Quin wrote:
> Joern Nettingsmeier <nettings <at> folkwang-hochschule.de> writes:
> 
> 
>>to compile jack cvs on my athlon64, i tried
> 
> 
> [...]
> 
> Please try this recent patch from Linus Hicks, and let me know if it
> works for you...
> 
> --- jack-0.99.50-orig/configure.ac	2005-02-07 13:07:44.000000000 -0500
> +++ jack-0.99.50/configure.ac	2005-02-19 23:48:52.000000000 -0500
>  <at>  <at>  -206,7 +206,7  <at>  <at> 
>      
>      JACK_OPT_CFLAGS="-D_REENTRANT -O2 -mcpu=7400 $ALTIVEC_OPT_FLAGS_FLAGS -mhard-float -mpowerpc-gfxopt"
>  
> -elif echo $target_cpu | grep "i*86" >/dev/null; then
> +elif echo $target_cpu | grep "i.86" >/dev/null; then

CVS commit [0.99.51] fix x86_64 optimization parameters

  * applied Linus Hicks' patch for this bug.  (Thanks!)
--

-- 
  joq

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

[linux-audio-user] ANNOUNCE kluppe 0.3

dear JACKers!

after a long period of inactivity and a month of programming, i am happy
to announce version 0.3 of my jackified loopplayer kluppe.
you will find a description and a tarball with sources here:
http://dieb13.klingt.org/content/projects/kluppe.html

recent versions of libsndfile, libjack, libxml2 and libgtk will be
required to compile and run kluppe.

please let me know if you need help, find bugs or desperately miss
features ;)

regards
d13b

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Cannot start jack: cannot bind server to socket (Permission denied)

Hi,

I am having difficulties with starting jack as user. When I do:

jackd -v -d alsa

I get the follow error:

getting driver descriptor from /usr/lib/jack/jack_alsa.so
getting driver descriptor from /usr/lib/jack/jack_dummy.so
jackd 0.99.0
Copyright 2001-2003 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

registered builtin port type 32 bit float mono audio
cannot bind server to socket (Permission denied)
cannot create server sockets
cannot create engine

Does anyone know how I can solve this?

I have a feeling I did not include something in the kernel that jack needs, 
but I'm not sure.

These are the modules I have loaded:

Module                  Size  Used by
speedtch               15240  0

Re: SOLVED: Cannot start jack: cannot bind server to socket

Thanks Jack, that solved it.

Regards,

Ben

>From: "Jack O'Quin" <joq <at> io.com>
>To: "Ben Boomsma" <benboomsma <at> hotmail.com>
>CC: jackit-devel <at> lists.sourceforge.net
>Subject: Re: [Jackit-devel] Cannot start jack: cannot bind server to socket 
>(Permission denied)
>Date: Thu, 03 Mar 2005 09:52:52 -0600
>
>"Ben Boomsma" <benboomsma <at> hotmail.com> writes:
>
> > I am having difficulties with starting jack as user. When I do:
> >
> > jackd -v -d alsa
> >
> > I get the follow error:
> >
> > registered builtin port type 32 bit float mono audio
> > cannot bind server to socket (Permission denied)
> > cannot create server sockets
> > cannot create engine
> >
> > Does anyone know how I can solve this?
>
>I'm guessing you have an old JACK tmpdir directory that belongs to
>root and didn't get cleaned up for some reason, perhaps due to an

cannot connect input port jackrec:input1 to hw:0

Re: Cannot start jack: cannot bind server to socket (Permission denied)

"Ben Boomsma" <benboomsma <at> hotmail.com> writes:

> I am having difficulties with starting jack as user. When I do:
>
> jackd -v -d alsa
>
> I get the follow error:
>
> registered builtin port type 32 bit float mono audio
> cannot bind server to socket (Permission denied)
> cannot create server sockets
> cannot create engine
>
> Does anyone know how I can solve this?

I'm guessing you have an old JACK tmpdir directory that belongs to
root and didn't get cleaned up for some reason, perhaps due to an
earlier crash.

The default tmpdir is /tmp, but it could be somewhere else, depending
on how JACK was configured.  `jackd --version' will reveal your
current value.  Look in the tmpdir for a directory named `jack' while
JACK is not running, and remove it.  It probably belongs to the `root'
user.
--

-- 
  joq

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

jack connect confusion

Folks,

I'm puzzled by a snippet of code from one of Jack's example clients,
called "simple_client.c," as follows:

/* connect the ports. Note: you can't do this before
	   the client is activated, because we can't allow
	   connections to be made to clients that aren't
	   running.
	*/

if ((ports = jack_get_ports (client, NULL, NULL,
JackPortIsPhysical|JackPortIsInput)) == NULL) {
		fprintf(stderr, "Cannot find any physical playback ports\n");
		exit(1);
	}

	if (jack_connect (client, jack_port_name (output_port), ports[0])) {
		fprintf (stderr, "cannot connect output ports\n");
	}

	free (ports);

One point of confusion for me is that the above-cited error messages refer
to "playback" and "output" ports, and the "jack_connect" function is
dealing with the "output_port;" however, the accompanying bit OR statement
seems to be handling the Input--as in "JackPortIsInput." Similarly, the
adjacent code within simple_client.c that handles "JackPortIsOutput" has
error messages that refer to the "capture" and "input" ports. On the face
of it, this would seem to be backwards, though I know the code is correct.
But not why it IS so!

My second point of confusion is regarding what is actually happening here.
Is the physical port being connected to the client's output port? Or are
the input and output ports within the client merely being connected to
each other (via the additional code not completely cited above, but which
parallels it). Or are both actions being accomplished?

Thanks,
Robert Hamilton a.k.a. seedpress 

	
		
__________________________________ 
Celebrate Yahoo!'s 10th Birthday! 
Yahoo! Netrospective: 100 Moments of the Web 
http://birthday.yahoo.com/netrospective/

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: jack connect confusion

On Sun, Mar 06, 2005 at 02:51:56PM -0800, Robert Hamilton wrote:

> if ((ports = jack_get_ports (client, NULL, NULL,
> JackPortIsPhysical|JackPortIsInput)) == NULL) {
> 		fprintf(stderr, "Cannot find any physical playback ports\n");
> 		exit(1);
> 	}
>
> ...
>
> One point of confusion for me is that the above-cited error messages refer
> to "playback" and "output" ports, and the "jack_connect" function is
> dealing with the "output_port;" however, the accompanying bit OR statement
> seems to be handling the Input--as in "JackPortIsInput." Similarly, the
> adjacent code within simple_client.c that handles "JackPortIsOutput" has
> error messages that refer to the "capture" and "input" ports. On the face
> of it, this would seem to be backwards, though I know the code is correct.
> But not why it IS so!

A JACK port that corresponds to a 'physical' output is actually itself an
input of something - a DA converter, or more general, an output interface.
It is only usually called a 'playback' or 'output' because it terminates
on a physical connection and does not belong to something that you would
normally see as a JACK client, even if you could look at it that way.
For me 'JackPortIsInput' is perfectly logical, but most people would
probably prefer something like 'JackPortIsWritable' instead.

--

-- 
FA

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Vexing compiler warnings

Folks,

When I compile a Jack client that I'm working on I get the following
warning message:

"warning: long unsigned int format, jack_nframes_t arg (arg 2)"

Here's the offending chunk of code, which is the standard "jack shutdown"
code that is used throughout many of the sample clients that are bundled
with Jack's source code:

jack_on_shutdown (client, jack_shutdown, 0);

	/* display the current sample rate. once the client is activated 
	   (see below), you should rely on your own sample rate
	   callback (see above) for this value.
	*/
	printf ("engine sample rate: %lu\n", jack_get_sample_rate (client));

The offending line is the last line--printf, its 2nd argument.
My program does compile, but the warnings make me nervous.

Thanks,
Robert Hamilton, a.k.a. seedpress

	
		
__________________________________ 
Celebrate Yahoo!'s 10th Birthday! 
Yahoo! Netrospective: 100 Moments of the Web 
http://birthday.yahoo.com/netrospective/

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click