[LAD] Updates

[Fons Adriaensen]

Hello all,

Updates are available at

<http://kokkinizita.linuxaudio.org/linuxaudio/downloads/index.html>

for all of the following:

aeolus-0.9.7
ambdec-0.7.1
clthreads-2.4.2
clxclient-3.9.2
ebumeter-0.4.2
jaaa-0.9.2
jack_delay-0.4.2
jack_utils-0.0.1
japa-0.9.2
jconvolver-1.0.2
jkmeter-0.6.5
jmatconvol-0.3.3
jmeters-0.4.4
jnoisemeter-0.2.2
octofile-0.3.2
tetraproc-0.8.6
yass-0.1.0
zita-ajbridge-0.8.2
zita-alsa-pcmi-0.3.2
zita-at1-0.6.2
zita-bls1-0.3.3
zita-convolver-4.0.2
zita-dpl1-0.3.3
zita-jclient-0.4.2
zita-lrx-0.1.2
zita-mu1-0.3.3
zita-njbridge-0.4.4
zita-resampler-1.6.2
zita-rev1-0.2.2

For most of them this is just small bug fixes, general maintenance,
and above all a systematic cleanup of the Makefiles.

Also the jacktools python package (presented at LAC 2018) is
available now. I actually did upload the files just before
the conference, but forgot to update index.html...

Ciao,

[Christopher Arndt]

Hi Fons,

Post by Fons Adriaensen
Updates are available at
[...]
jmeters-0.4.4

when I run jmeters I get this warning:

$ jmeters -t vu "Master L"
jack_connect called with a NULL port name

jmeters' input port shows up with jack_lsp as "jmeters:in-1" though.


Chris

[Fons Adriaensen]

Post by Christopher Arndt
$ jmeters -t vu "Master L"
jack_connect called with a NULL port name
jmeters' input port shows up with jack_lsp as "jmeters:in-1" though.

Doesn't happen here:

***@zita1:~> jmeters -t vu "Master L"
***@zita1:~> jmeters -t vu "Master L" "Master R"
***@zita1:~>

??

[Fons Adriaensen]

Post by Christopher Arndt
$ jmeters -t vu "Master L"
jack_connect called with a NULL port name
jmeters' input port shows up with jack_lsp as "jmeters:in-1" though.

Should be fixed in jmeters-0.4.5 (available now).

[Christopher Arndt]

Post by Fons Adriaensen

Post by Christopher Arndt
$ jmeters -t vu "Master L"
jack_connect called with a NULL port name

Should be fixed in jmeters-0.4.5 (available now).

Confirmed.

[Ralf Mattes]

Just ashort feedback:
on my Debian (Testing) I needed to add '-I/usr/include/freetype2' to the Makefile of both
clxclient and aeolus.

Cheers, and thank's

RalfD

Post by Fons Adriaensen
Hello all,
Updates are available at
<http://kokkinizita.linuxaudio.org/linuxaudio/downloads/index.html>
aeolus-0.9.7
ambdec-0.7.1
clthreads-2.4.2
clxclient-3.9.2
ebumeter-0.4.2
jaaa-0.9.2
jack_delay-0.4.2
jack_utils-0.0.1
japa-0.9.2
jconvolver-1.0.2
jkmeter-0.6.5
jmatconvol-0.3.3
jmeters-0.4.4
jnoisemeter-0.2.2
octofile-0.3.2
tetraproc-0.8.6
yass-0.1.0
zita-ajbridge-0.8.2
zita-alsa-pcmi-0.3.2
zita-at1-0.6.2
zita-bls1-0.3.3
zita-convolver-4.0.2
zita-dpl1-0.3.3
zita-jclient-0.4.2
zita-lrx-0.1.2
zita-mu1-0.3.3
zita-njbridge-0.4.4
zita-resampler-1.6.2
zita-rev1-0.2.2
For most of them this is just small bug fixes, general maintenance,
and above all a systematic cleanup of the Makefiles.
Also the jacktools python package (presented at LAC 2018) is
available now. I actually did upload the files just before
the conference, but forgot to update index.html...
Ciao,
--
FA
_______________________________________________
Linux-audio-dev mailing list
https://lists.linuxaudio.org/listinfo/linux-audio-dev

[Fons Adriaensen]

Post by Ralf Mattes
on my Debian (Testing) I needed to add '-I/usr/include/freetype2' to the Makefile of both
clxclient and aeolus.

That is what pkgconf --cflags freetype2 is supposed to do.
Could you be using an older version of freetype ? It used to have its
own config command which was removed and replaced by using pkgconf
in recent releases. This was one of the reasons to review all of
the Makefiles.

Ciao,

[Ralf Mattes]

Post by Fons Adriaensen
That is what pkgconf --cflags freetype2 is supposed to do.
Could you be using an older version of freetype ? It used to have its
own config command which was removed and replaced by using pkgconf
in recent releases. This was one of the reasons to review all of
the Makefiles.

Hmm - are you shure that program is called 'pkgconf'? If we are talking about that freedesktop.org
program (https://www.freedesktop.org/wiki/Software/pkg-config/) that tends to be called 'pkg-config' ...

Cheers, RalfD

[Fons Adriaensen]

Post by Ralf Mattes

Post by Fons Adriaensen
That is what pkgconf --cflags freetype2 is supposed to do.
Could you be using an older version of freetype ? It used to have its
own config command which was removed and replaced by using pkgconf
in recent releases. This was one of the reasons to review all of
the Makefiles.

Hmm - are you shure that program is called 'pkgconf'? If we are talking about that freedesktop.org
program (https://www.freedesktop.org/wiki/Software/pkg-config/) that tends to be called 'pkg-config' ...

For more info on pkgconf, see <https://github.com/pkgconf/pkgconf>.

I seem to have both pkgconf and pkg-config, and on Archlinux both
are even provided by the same package.

I used pkgconf as suggested by an Archlinux packager. Don't know
if this is the best choice to support other distros.

Anyway, all that is required is -I/usr/include/freetype2 and maybe
that is what I should use. Comments invited.

The whole issue in the case of freetype is rather strange anyway.
None of my application explicitly link with the freetype library.
The -I is necessary only to satisify a nested #include in
/usr/include/X11/Xft/Xft.h required by clxlient.h.

[Ralf Mattes]

Post by Fons Adriaensen

Post by Ralf Mattes

Post by Fons Adriaensen
That is what pkgconf --cflags freetype2 is supposed to do.
Could you be using an older version of freetype ? It used to have its
own config command which was removed and replaced by using pkgconf
in recent releases. This was one of the reasons to review all of
the Makefiles.

Hmm - are you shure that program is called 'pkgconf'? If we are talking about that freedesktop.org
program (https://www.freedesktop.org/wiki/Software/pkg-config/) that tends to be called 'pkg-config' ...

For more info on pkgconf, see <https://github.com/pkgconf/pkgconf>.
I seem to have both pkgconf and pkg-config, and on Archlinux both
are even provided by the same package.
I used pkgconf as suggested by an Archlinux packager. Don't know
if this is the best choice to support other distros.

No, it's not. At least the Debian/Ubuntu/Mint-ish distros depend on pkg-config. I'm pretty shure the
same is true for Redhat/Fedora/Centos do so as well, and, at least according to the SuSE RPM guide they
expect pkg-config as well (after all, it is the standard established byfreedesktop.org).
As far as I remember the pkgconf developers suggest to create a symlink linking pkgconf to pkg-config
(IMHO a replacement tool shoud do this as a default).

Post by Fons Adriaensen
Anyway, all that is required is -I/usr/include/freetype2 and maybe
that is what I should use. Comments invited.

Please don't. IIRC correctly there was a time when I needed to compile aoelus et al. with a self-compiled/installed
freetype (living under /usr/local). With that pkg-config invocation everything works as expected (as long
as I keep my PKG_CONFIG_PATH correct). With your hard-coded values I'd need to patch the Makefiles.

Cheers, RalfD

Post by Fons Adriaensen
The whole issue in the case of freetype is rather strange anyway.
None of my application explicitly link with the freetype library.
The -I is necessary only to satisify a nested #include in
/usr/include/X11/Xft/Xft.h required by clxlient.h.
--
FA

[Christopher Arndt]

Post by Ralf Mattes

Post by Fons Adriaensen
I seem to have both pkgconf and pkg-config, and on Archlinux both
are even provided by the same package.
I used pkgconf as suggested by an Archlinux packager. Don't know
if this is the best choice to support other distros.

No, it's not.

Post by Fons Adriaensen
Anyway, all that is required is -I/usr/include/freetype2 and maybe
that is what I should use.

Please don't.

Agree on both accounts. Just use 'pkg-config' like everybody else.


Chris

[David Runge]

Post by Christopher Arndt

Post by Ralf Mattes

Post by Fons Adriaensen
I seem to have both pkgconf and pkg-config, and on Archlinux both
are even provided by the same package.
I used pkgconf as suggested by an Archlinux packager. Don't know
if this is the best choice to support other distros.

No, it's not.

Post by Fons Adriaensen
Anyway, all that is required is -I/usr/include/freetype2 and maybe
that is what I should use.

Please don't.

Agree on both accounts. Just use 'pkg-config' like everybody else.

I don't.

pkgconf [1] is a valid replacement of pkg-config (by implementing it
with even more features and better .pc handling) and available on many,
if not all, distros (e.g. [2] [3] [4]). In some it is even the default
by now.

Additionally, this is all better, than relying on a convenience layer
hack job, such as the `freetype-config` script (that should've never
even been part of pkg-config to begin with).

Best,
David

[1] https://git.dereferenced.org/pkgconf/pkgconf
[2] https://packages.debian.org/sid/pkgconf
[3] https://packages.ubuntu.com/search?keywords=pkgconf
[4] https://fedoraproject.org/wiki/Changes/pkgconf_as_system_pkg-config_implementation

[Hermann Meyer]

Post by David Runge

Post by Christopher Arndt

Post by Ralf Mattes

Post by Fons Adriaensen
I seem to have both pkgconf and pkg-config, and on Archlinux both
are even provided by the same package.
I used pkgconf as suggested by an Archlinux packager. Don't know
if this is the best choice to support other distros.

No, it's not.

Post by Fons Adriaensen
Anyway, all that is required is -I/usr/include/freetype2 and maybe
that is what I should use.

Please don't.

Agree on both accounts. Just use 'pkg-config' like everybody else.

I don't.
pkgconf [1] is a valid replacement of pkg-config (by implementing it
with even more features and better .pc handling) and available on many,
if not all, distros (e.g. [2] [3] [4]). In some it is even the default
by now.
Additionally, this is all better, than relying on a convenience layer
hack job, such as the `freetype-config` script (that should've never
even been part of pkg-config to begin with).
Best,
David
[1] https://git.dereferenced.org/pkgconf/pkgconf
[2] https://packages.debian.org/sid/pkgconf
[3] https://packages.ubuntu.com/search?keywords=pkgconf
[4] https://fedoraproject.org/wiki/Changes/pkgconf_as_system_pkg-config_implementation

But why do you prefer to abuse users experience to promote a
replacement, when a simple silence replacement is already in place?
Using pkg-config means that it works on any system, even older ones, as
pkgconfig provide a symlink to pkg-config and replace it therewith
"really", without trouble for anyone.

[David Runge]

But why do you prefer to abuse users experience to promote a replacement,
when a simple silence replacement is already in place?

I'm not abusing anyone. If at all, I was assuming wrongly, that this
would actually be used more widely already (and apparently it is - on
newer systems).

Using pkg-config means that it works on any system, even older ones,
as pkgconfig provide a symlink to pkg-config and replace it therewith
"really", without trouble for anyone.

That's correct.
However, if one has to sed the Makefiles to remove optimization (for
packaging), it's not a big step to do a `sed -e 's/pkgconf/pkg-config/g'
-i Makefile` either. ;-)

All in all I'm happy the Makefiles see some overhaul after all this
time!

Thanks Fons (and sorry for getting you in pkgconf vs. pkg-config
trouble)!

[Ralf Mattes]

Ah, one more thimg I forgot to mention:
when I try to close aeolus windows (Instrument/Audio etc.) the window stays open but the
contents disapears (windows stays white).

Cheers, RalfD

[Fons Adriaensen]

Post by Ralf Mattes
when I try to close aeolus windows (Instrument/Audio etc.) the window stays open but the
contents disapears (windows stays white).

Nothing has changed in the Aeolus code, and I haven't seen this
on any on the 20 or so systems it was tested on. Probably some
problem with your desktop / window manager / X11 system.

[Ralf Mattes]

Post by Fons Adriaensen
Nothing has changed in the Aeolus code, and I haven't seen this
on any on the 20 or so systems it was tested on. Probably some
problem with your desktop / window manager / X11 system.

Oh, sorry. This is actually a problem I have since quite a while, but since I usually
run aeolus on a headless box I never bothered to report (and, somehow, I had the
impression that aeolus wasn't under active development).
The window manager is actually extremley simple (wingo) and seems to work fine
with all other applications (admittedly not a very sound argument ...).

Cheers, RalfD

Post by Fons Adriaensen
--
FA

[Ralf Mattes]

Post by David Runge

Post by Christopher Arndt

Post by Ralf Mattes

Post by Fons Adriaensen
I seem to have both pkgconf and pkg-config, and on Archlinux both
are even provided by the same package.
I used pkgconf as suggested by an Archlinux packager. Don't know
if this is the best choice to support other distros.

No, it's not.

Post by Fons Adriaensen
Anyway, all that is required is -I/usr/include/freetype2 and maybe
that is what I should use.

Please don't.

Agree on both accounts. Just use 'pkg-config' like everybody else.

I don't.

You seem to confuse two things here: pkgconf, the api compatible alternative to pkg-config, and
pkgconf, the name of the program that provides pkg-config information to shell scripts and makefiles.

Since pkgconf's sole purpose is the replacement of the original pkg-config implementation giving the
binary a different name seems questionable.
It's like writing a make-replacement and calling it murks and then expect the rest of the world to
change their build systems. That takes a lot of hubris/ego ...

Post by David Runge
pkgconf [1] is a valid replacement of pkg-config (by implementing it
with even more features and better .pc handling) and available on many,
if not all, distros (e.g. [2] [3] [4]). In some it is even the default
by now.

And they call the binary 'pkgconf'? I' impressed.

Post by David Runge
Additionally, this is all better, than relying on a convenience layer
hack job, such as the `freetype-config` script (that should've never
even been part of pkg-config to begin with).

Who was talking about freetype-config?

Cheers, RalfD

Post by David Runge
Best,
David
[1] https://git.dereferenced.org/pkgconf/pkgconf
[2] https://packages.debian.org/sid/pkgconf
[3] https://packages.ubuntu.com/search?keywords=pkgconf
[4] https://fedoraproject.org/wiki/Changes/pkgconf_as_system_pkg-config_implementation
--
https://sleepmap.de

[David Runge]

Post by Ralf Mattes
You seem to confuse two things here: pkgconf, the api compatible
alternative to pkg-config, and pkgconf, the name of the program that
provides pkg-config information to shell scripts and makefiles.

Hm, I'm not sure what you mean by that. If packaged correctly, pkgconf
is just a pkg-config replacement (done via symlinking).
So you can have pkg-config functionality, without the freedesktop
pkg-config (see Fedora or Arch package).

Post by Ralf Mattes
Since pkgconf's sole purpose is the replacement of the original
pkg-config implementation giving the binary a different name seems
questionable.

Well, you can read anything into that if you like... or not.

Post by Ralf Mattes
It's like writing a make-replacement and calling it murks and then
expect the rest of the world to change their build systems. That takes
a lot of hubris/ego ...

You seem to like judging from reading a lot.

However, I agree, that for Fons' packages calling `pkg-config` will be
the wiser choice for backwards compatibility.
As I was just merely suggesting to him a replacement for the obsolete
freetype-config script, I was using the current Arch default. What Fons
makes of that is out of my hands.
So, I'd rather not you play the blame game, but well, do as you please.

Post by Ralf Mattes

Post by David Runge
Additionally, this is all better, than relying on a convenience layer
hack job, such as the `freetype-config` script (that should've never
even been part of pkg-config to begin with).

Who was talking about freetype-config?

Me, as it was in the Makefiles before and I had to patch it out.

Generally it would probably be advisable to chill this conversation down
a little and take a deep breath.

Best,
David