Hi,
first of all thank you for your hard work on developing advanced musical tools for ubuntu.
I just installed Jack2 (1.9.2) because i wanted to test it. Everything was ok when compiling and installing, but when i try to run Jackd, i get this error:
jackd: symbol lookup error: jackd: undefined symbol: jackctl_server_create
I'm sending you log of entire process:
./waf configure --dbus --enable-pkg-config-dbus-service-dir
Linux detected
Checking for program g++ : ok /usr/bin/g++
Checking for compiler version : ok 4.3.3
Checking for program cpp : ok /usr/bin/cpp
Checking for program ar : ok /usr/bin/ar
Checking for program ranlib : ok /usr/bin/ranlib
Checking for g++ : ok
Checking for program gcc : ok /usr/bin/gcc
Checking for compiler version : ok 4.3.3
Checking for program ar : ok /usr/bin/ar
Checking for program ranlib : ok /usr/bin/ranlib
Checking for gcc : ok
Checking for header samplerate.h : ok
Checking for alsa >= 1.0.0 : ok
Checking for libfreebob >= 1.0.0 : Package "libfreebob (>= 1.0.0)" could not be found or the found version is too old.
Checking for libffado >= 1.999.17 : Package "libffado (>= 1.999.17)" could not be found or the found version is too old.
Checking for dbus-1 >= 1.0.0 : ok
Checking for dbus-1 flags : ok
Checking for header expat.h : ok
Checking for header sndfile.h : ok
Checking for header ncurses.h : ok
Checking for library readline : ok
==================
JACK 1.9.2 exported from r3454M
Build with a maximum of 64 JACK clients
Build with a maximum of 1024 ports
Install prefix : /usr/local
Library directory : /usr/local/lib/
Drivers directory : /usr/local/lib/jack
Build doxygen documentation : no
Build with engine profiling : no
Build with ALSA support : yes
Build with FireWire (FreeBob) support : no
Build with FireWire (FFADO) support : no
Build D-Bus JACK (jackdbus) : yes
D-Bus service install directory : /usr/share/dbus-1/services
Configuration finished successfully (00:00:00); project is now ready to build.
.
sudo ./waf install
[sudo] password for marco:
* installing common/jack/systemdeps.h as /usr/local/include/jack/systemdeps.h
* installing common/jack/jslist.h as /usr/local/include/jack/jslist.h
* installing common/jack/control.h as /usr/local/include/jack/control.h
* symlink /usr/local/bin/jack_disconnect (-> jack_connect)
* installing example-clients/jack_control as /usr/local/bin/jack_control
* installing build/default/jack.pc as /usr/local/lib//pkgconfig/jack.pc
* installing build/default/dbus/org.jackaudio.service as /usr/share/dbus-1/services/org.jackaudio.service
* installing build/default/common/libjackserver.so as /usr/local/lib//libjackserver.so.0.1.0
* symlink /usr/local/lib//libjackserver.so.0 (-> libjackserver.so.0.1.0)
* symlink /usr/local/lib//libjackserver.so (-> libjackserver.so.0.1.0)
* installing build/default/common/libjack.so as /usr/local/lib//libjack.so.0.1.0
* symlink /usr/local/lib//libjack.so.0 (-> libjack.so.0.1.0)
* symlink /usr/local/lib//libjack.so (-> libjack.so.0.1.0)
* installing build/default/common/netmanager.so as /usr/local/lib/jack/netmanager.so
* installing build/default/common/profiler.so as /usr/local/lib/jack/profiler.so
* installing build/default/common/netadapter.so as /usr/local/lib/jack/netadapter.so
* installing build/default/common/audioadapter.so as /usr/local/lib/jack/audioadapter.so
* installing build/default/linux/jackd as /usr/local/bin/jackd
* installing build/default/linux/jack_dummy.so as /usr/local/lib/jack/jack_dummy.so
* installing build/default/linux/jack_alsa.so as /usr/local/lib/jack/jack_alsa.so
* installing build/default/linux/jack_net.so as /usr/local/lib/jack/jack_net.so
* installing build/default/example-clients/jack_load as /usr/local/bin/jack_load
* installing build/default/example-clients/jack_freewheel as /usr/local/bin/jack_freewheel
* installing build/default/example-clients/jack_simple_client as /usr/local/bin/jack_simple_client
* installing build/default/example-clients/jack_showtime as /usr/local/bin/jack_showtime
* installing build/default/example-clients/jack_cpu_load as /usr/local/bin/jack_cpu_load
* installing build/default/example-clients/jack_metro as /usr/local/bin/jack_metro
* installing build/default/example-clients/jack_evmon as /usr/local/bin/jack_evmon
* installing build/default/example-clients/jack_midiseq as /usr/local/bin/jack_midiseq
* installing build/default/example-clients/jack_zombie as /usr/local/bin/jack_zombie
* installing build/default/example-clients/jack_connect as /usr/local/bin/jack_connect
* installing build/default/example-clients/jack_monitor_client as /usr/local/bin/jack_monitor_client
* installing build/default/example-clients/jack_bufsize as /usr/local/bin/jack_bufsize
* installing build/default/example-clients/jack_lsp as /usr/local/bin/jack_lsp
* installing build/default/example-clients/jack_alias as /usr/local/bin/jack_alias
* installing build/default/example-clients/jack_thru as /usr/local/bin/jack_thru
* installing build/default/example-clients/jack_midisine as /usr/local/bin/jack_midisine
* installing build/default/example-clients/jack_unload as /usr/local/bin/jack_unload
* installing build/default/example-clients/jack_server_control as /usr/local/bin/jack_server_control
* installing build/default/tests/jack_test as /usr/local/bin/jack_test
* installing build/default/tests/jack_cpu as /usr/local/bin/jack_cpu
* installing build/default/tests/jack_delay as /usr/local/bin/jack_delay
* installing build/default/tests/jack_multiple_metro as /usr/local/bin/jack_multiple_metro
* installing build/default/example-clients/jack_rec as /usr/local/bin/jack_rec
* installing build/default/example-clients/inprocess.so as /usr/local/lib/jack/inprocess.so
* installing build/default/dbus/jackdbus as /usr/local/bin/jackdbus
Compilation and installation finished successfully (00:00:00)
Thank you very much guys; i'm new to development and understanding of Linux Audio and i will make my best to help the community.
Cheers,
Marco
Hi Nedko,
Looks cool :)
Just add a "visible" toggle button for each curve, should be fairly easy in your python based ui.
Cheers,
J.
--- On Sun, 6/21/09, Jörn Nettingsmeier <nettings(a)folkwang-hochschule.de> wrote:
> From: Jörn Nettingsmeier <nettings(a)folkwang-hochschule.de>
> Subject: Re: [LAD] [ANN] lv2fil version 2.0 "New hope" released
> To: "Paul Davis" <paul(a)linuxaudiosystems.com>
> Cc: "Nedko Arnaudov" <nedko(a)arnaudov.name>, linux-audio-dev(a)lists.linuxaudio.org, linux-audio-user(a)lists.linuxaudio.org
> Date: Sunday, June 21, 2009, 6:09 PM
> Paul Davis wrote:
> > 2009/6/20 Jörn Nettingsmeier <nettings(a)folkwang-hochschule.de>:
> >> Nedko Arnaudov wrote:
> >>> It is not that clean, but I can clean it more
> if such cleanup is
> >>> required for incusion in ardour 2.x.
> >> i don't know if this is still in time for 2.8.1,
> but yes, i would
> >> welcome this patch to go into the queue for
> 2.0-svn.
> >>
> >> haven't got a chance to test it yet (had some
> spurious ardour problems
> >> that i need to pinpoint before adding an
> out-of-tree patch), but hope to
> >> do so today.
> >
> > it has a few issues. not real showstoppers. sampo is
> "on the case",
> > whatever that might mean.
>
> great, thanks. a spiffy-looking equalizer could be a nice
> marketing
> advantage for ardour :-D
>
> while we're at it, we should really have an award for
> plugin spiffiness
> - so far, nedko and the calf team are hot bets. haven't
> checked the
> invada stuff yet, but it also looks very promising indeed.
>
> best,
>
> jörn
>
>
> _______________________________________________
> Linux-audio-dev mailing list
> Linux-audio-dev(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
>
Hi Nedko,
Looks cool. I would like to try it out.
Where's the ardour patch ? Thanks :)
J.
--- On Sat, 6/13/09, Nedko Arnaudov <nedko(a)arnaudov.name> wrote:
> From: Nedko Arnaudov <nedko(a)arnaudov.name>
> Subject: [LAD] [ANN] lv2fil version 2.0 "New hope" released
> To: linux-audio-announce(a)lists.linuxaudio.org, linux-audio-dev(a)lists.linuxaudio.org, linux-audio-user(a)lists.linuxaudio.org
> Date: Saturday, June 13, 2009, 10:40 AM
> Four-band parametric equaliser LV2
> plugin. DSP code by Fons Adriaensen.
>
> Homepage: http://nedko.arnaudov.name/soft/lv2fil/
>
> Screenshot: http://nedko.arnaudov.name/soft/lv2fil/lv2fil.png
>
> Tarball download:
> http://nedko.arnaudov.name/soft/lv2fil/lv2fil-2.0.tar.bz2
> http://nedko.arnaudov.name/soft/lv2fil/lv2fil-2.0.tar.bz2.sig
>
> = Overview =
> Stereo and mono LV2 plugins, four-band parametric
> equalisers.
> Each section has an active/bypass switch, frequency,
> bandwidth and
> gain controls. There is also a global bypass switch and
> gain control.
>
> = DSP =
> The 2nd order resonant filters are implemented using a
> Mitra-Regalia
> style lattice filter, which has the nice property of being
> stable
> even while parameters are being changed.
>
> All switches and controls are internally smoothed, so they
> can be
> used 'live' whithout any clicks or zipper noises. This
> should make
> this plugin a good candidate for use in systems that allow
> automation
> of plugin control ports, such as Ardour, or for stage use.
>
> = GUI =
> The GUI provides knobs and toggle buttons for tweaking
> filter
> parameters. It also provides frequency response widget
> with
> differently coloured curve for each section and separate
> curve for
> total equalization effect.
>
> The GUI uses the External UI extension. lv2rack (part of
> zynjacku)
> supports this extension. Ardour-2.8 needs patch to support
> the
> external UI extension.
>
> --
> Nedko Arnaudov <GnuPG KeyID: DE1716B0>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Linux-audio-dev mailing list
> Linux-audio-dev(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
>
hi everyone!
sorry if this has been discussed before, but i didn't find anything in
the archives...
consider the case of periodic control values of LADSPA plugins, for
instance the azimuth in a horizontal panner or the phase shift in a phaser.
currently, they are usually marked as BOUNDED_BELOW and BOUNDED_ABOVE,
but the host has no way of knowing that the upper bound is next to the
lower bound, so that it can chose the shortest path to the next value
when interpolating automation control points.
take ardour, for example: if i want to spin a source 360 degrees, i have
to start at 0, set a control point at 180, set another control point at
the exact next sample to -180 and then onwards. if there is even a
single sample between the control points, the interpolation will cause
the image to jump in weird ways, because it doesn't know that 180 == -180.
does it make sense to add a new hint to LADSPA, something like
LADSPA_HINT_PERIODIC? it would mandate LADSPA_HINT_BOUNDED_BELOW and
LADSPA_HINT_BOUNDED_ABOVE as well as the respective port range hints,
*and* imply that LowerBound is equivalent to UpperBound in the port
range hint structure.
this would enable hosts to do the Right Thing(tm).
best,
jörn
Hi,
I knew close to nothing about python but chose waf for the build environment of a project. Depending on how comfortable you are with learning prog. languages, this is not really difficult. And there are tons of examples to get inspired.
I would recommend waf as the project I set up with it is building nicely.
> There are lots of alternatives, including:
>
> Â Â Â Â * waf -- If you know the Python
> programming language,
> Â Â Â Â Â this may be a good
> choice. I've heard good things
> Â Â Â Â Â about waf.
>
Ardour3 switched to waf by the way. Jack2 uses waf as well (was a great source of inspiration for my introduction to waf).
J.
Heya!
The Linux Plumbers Conference 2009 CFP ends soon! If you are working on
Linux audio infrastructure then make sure to submit a paper for the
audio track! Do it now, it'll soon be too late, you have time until
June 15th!
Why attend or submit a paper? Because this is *the* conference where
you can make yourself heard and influence the lower levels of our
audio stacks. If you have some beef with or something to contribute to
the lower level sound (and other) infrastructure of modern Linuxes,
then *this* is where to go.
http://linuxplumbersconf.org/2009/
Papers go here please:
http://linuxplumbersconf.org/2009/submit/
LWN has some coverage of what happened last year, in case you want to
have a peek:
http://lwn.net/Articles/299211/
See you in Portland! And spread the word!
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
Four-band parametric equaliser LV2 plugin. DSP code by Fons Adriaensen.
Homepage: http://nedko.arnaudov.name/soft/lv2fil/
Screenshot: http://nedko.arnaudov.name/soft/lv2fil/lv2fil.png
Tarball download:
http://nedko.arnaudov.name/soft/lv2fil/lv2fil-2.0.tar.bz2http://nedko.arnaudov.name/soft/lv2fil/lv2fil-2.0.tar.bz2.sig
= Overview =
Stereo and mono LV2 plugins, four-band parametric equalisers.
Each section has an active/bypass switch, frequency, bandwidth and
gain controls. There is also a global bypass switch and gain control.
= DSP =
The 2nd order resonant filters are implemented using a Mitra-Regalia
style lattice filter, which has the nice property of being stable
even while parameters are being changed.
All switches and controls are internally smoothed, so they can be
used 'live' whithout any clicks or zipper noises. This should make
this plugin a good candidate for use in systems that allow automation
of plugin control ports, such as Ardour, or for stage use.
= GUI =
The GUI provides knobs and toggle buttons for tweaking filter
parameters. It also provides frequency response widget with
differently coloured curve for each section and separate curve for
total equalization effect.
The GUI uses the External UI extension. lv2rack (part of zynjacku)
supports this extension. Ardour-2.8 needs patch to support the
external UI extension.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
> does anyone have any idea on the uptake of VST 3 ?
Seems only VST3 works well on 64-bit systems. (VST 2 is supported, but runs
in a high-latency 32-bit emulation environment).
My hunch is VST3 uptake will track 64-bit Windows uptake.
Jeff
> Is this becoming the standard and 2.* being quickly
> deprecated?
> Comparing the two, there is a lot of stuff in VST3, it
> seems quite heavy, which seems to be a change
> from the relative simplicity of 2.*. Also 3 does not look
> backwards compatible (so older plugins would not
> work with it).
> On the FOSS front then, with 3 we are stuck again
> with Steinberg's terms. So my question is: are
> developers in general sticking with 2.* or has everyone
> moved to 3. Again, my question has an educational
> slant, should we be teaching 3 or 2 (or both, if we
> are teaching VST at all, that is) ?
>
> Thanks
>
> Victor
