JACK, cmt and swh (LADSPA plugins) in incoming

filoktetes · 2004-01-07 02:01:04

Yoohoo! This is fun!

I think I'm getting it now.

Well, I've submitted three packages to incoming:

cmt-1.15 and swh-plugins-0.4.3 are plugin packages for LADSPA.
If you install them and try to start e.g Audacity, you will see 141 new audio effects in the menu.

Of course they need ladspa, which is in the dp TUR.
And swh-plugins needs fftw3, which is in the staging TUR.

JACK (Jack Audio Connection Kit) is a low-latency audio server,
which works well with ALSA and e.g the Rosegarden midi /audio
sequencer, and lots of other things too, which I haven't tried yet.

And big surprise (at least for me); I got Rosegarden to compile,
so I'll upload it as soon as it finishes building again (I forgot some
dependencies the first time). By the way, also Rosegarden has support for the LADSPA plugins

If anyone looks at my PKGBUILDs, and finds them totally stupid, or perhaps just has some constructive comments, please tell me, since I'm quite new to this kind of magic.

Xentac · 2004-01-07 05:21:24

I used to have a jack package. Just as a note, you probably want to rename it to jackit, because that's the project name. Jack is actually the name of a different program.

filoktetes · 2004-01-07 15:50:54

Xentac wrote:

I used to have a jack package. Just as a note, you probably want to rename it to jackit, because that's the project name. Jack is actually the name of a different program.

Yes, I think the naming of this package is quite complicated...

From the jack faq

Jack
Jack is the name of the whole system. It may be written as JACK if you prefer, because it is an acronym for "Jack Audio Connection Kit". Do you know Jack?
...
jackit, jack-audio-connection-kit
As luck would have it, by the time we got around to registering a sourceforge site for Jack, there was already another program out there by the same name. "jackit" is a play on the original Jack acronym. Not only does that other project have the sourceforge name, it has mandrake and debian packages too, so we needed a new name for releases. At the moment, we're releasing tarballs as jack-audio-connection-kit.

So I named the package jack-audio-connection-kit-0.91.1.tar.gz and call it jack or JACK when I'm writing, since I've never really seen anyone call it jackit yet.

But I agree that jackit perhaps is shorter and nicer than jack-audio-connection-kit, so what do I do, then? Should I upload the package with the new name to incoming. I'll have to make a new Rosegarden package as well, since it depends on jackit

Xentac · 2004-01-07 16:01:19

jack-audio-connection-kit is fine. I'm not one to complain about having to type too much I just wanted to make sure it wasn't "jack", that's all.

dp · 2004-01-07 17:13:10

you uploaded them to incoming? .. i can put them in my TUR, if you like; the install will be then much easier --- feel free to contact me

great job with rosegarden 8)

filoktetes · 2004-01-07 17:47:19

Yes, please do

neri · 2004-01-07 18:11:11

reb wrote:

Yoohoo! This is fun!
Of course they need ladspa, which is in the dp TUR.
And swh-plugins needs fftw3, which is in the staging TUR.

I currently have a problem with ladspa, cause the header is provided by
sweep. This results in a conflict of the sweep and the ladspa package. I
currently try to rebuild sweep with a dependency on ladspa and alsa
enabled. To make that official, ladspa will have to be included to the extra
repo. I think for people working with audio (not only listening) alsa
is really better than OSS. When it finishes, the maintainer will be informed.

reb wrote:

JACK (Jack Audio Connection Kit) is a low-latency audio server,
which works well with ALSA and e.g the Rosegarden midi /audio
sequencer, and lots of other things too, which I haven't tried yet.
And big surprise (at least for me); I got Rosegarden to compile,
so I'll upload it as soon as it finishes building again (I forgot some
dependencies the first time). By the way, also Rosegarden has support for the LADSPA plugins
If anyone looks at my PKGBUILDs, and finds them totally stupid, or perhaps just has some constructive comments, please tell me, since I'm quite new to this kind of magic.

Using namcap (pacman -S namcap) helps you with the dependencies:
JACK needs alsa-lib and readline additionally to the ones you already
included:

pkgname=jack-audio-connection-kit
pkgver=0.91.1
pkgrel=1
pkgdesc="a low-latency audio server"
url="http://jackit.sourceforge.net/"
depends=('alsa-lib' 'readline' 'libsndfile')
makedepends=(doxygen)
conflicts=()
replaces=()
backup=()
install=
source=(http://heanet.dl.sourceforge.net/sourceforge/jackit/$pkgname-$pkgver.tar.gz)
md5sums=()
build() {
cd $startdir/src/$pkgname-$pkgver
./configure --prefix=/usr
make || return 1
make DESTDIR=$startdir/pkg install
}

Since the JACK server needs to be started before apps like rosegarden
or ardour can be opened it might be useful to have a start script. Maybe
as an idea for the future.

Now, when dp will include JACK to his TUR and bison is fixed, ardour can
be build. I already finished it and will put it to incoming. When it's done
a new thread is opened in teh forum.

bye neri

dp · 2004-01-07 21:49:05

all 3 packages are now in my TUR ... the dependences are corrected for jack-com...

have fun :-)

if someone writed a script to be put in /etc/rc.d/jackd , feel free to contact me to update the package

Arch Linux

#1 2004-01-07 02:01:04

JACK, cmt and swh (LADSPA plugins) in incoming

#2 2004-01-07 05:21:24

Re: JACK, cmt and swh (LADSPA plugins) in incoming

#3 2004-01-07 15:50:54

Re: JACK, cmt and swh (LADSPA plugins) in incoming

#4 2004-01-07 16:01:19

Re: JACK, cmt and swh (LADSPA plugins) in incoming

#5 2004-01-07 17:13:10

Re: JACK, cmt and swh (LADSPA plugins) in incoming

#6 2004-01-07 17:47:19

Re: JACK, cmt and swh (LADSPA plugins) in incoming

#7 2004-01-07 18:11:11

Re: JACK, cmt and swh (LADSPA plugins) in incoming

#8 2004-01-07 21:49:05

Re: JACK, cmt and swh (LADSPA plugins) in incoming

Board footer