31 Mar
2015
31 Mar
'15
3:02 p.m.
Hi,
I wrote some code (in C++) using JACK1 API. It was quite easy to do that
with a plenty of example files.
Recently, I tried to utilize C++ libraries provided in JACK2 because I
don't like mixing OO code with C api. There are a lot of C++ classes in
JACK2 but I'm not able to link/include them.
For example: instead of #include <jack/jack.h> I'm trying to #include
"jack2/JackServer.h".
There are no example files.
What am I doing wrong? Or is it a bad way of using JACK2?
Thanks,
Vaclav
31 Mar
31 Mar
3:30 p.m.
On Tue, 31 Mar 2015, Vaclav Mach wrote:
Hi,
I wrote some code (in C++) using JACK1 API. It was quite easy to do that with
a plenty of example files.
Recently, I tried to utilize C++ libraries provided in JACK2 because I don't
like mixing OO code with C api. There are a lot of C++ classes in JACK2 but
I'm not able to link/include them.
I had always thought a jack client is not jack1 or 2 it should work with
both. I am assuming you are writing a jack client.
For example: instead of #include <jack/jack.h> I'm trying to #include
"jack2/JackServer.h".
I think (someone will correct me) that is for making jack2 modules such as
a new backend (net, alsa, etc.) or for changing jackd2 internals.
--
Len Ovens
www.ovenwerks.net
3:40 p.m.
On Tue, Mar 31, 2015 at 9:02 AM, Vaclav Mach <vaclav.mach(a)artisys.aero>
wrote:
Hi,
I wrote some code (in C++) using JACK1 API. It was quite easy to do that
with a plenty of example files.
Recently, I tried to utilize C++ libraries provided in JACK2 because I
don't like mixing OO code with C api. There are a lot of C++ classes in
JACK2 but I'm not able to link/include them.
For example: instead of #include <jack/jack.h> I'm trying to #include
"jack2/JackServer.h".
There are no example files.
What am I doing wrong? Or is it a bad way of using JACK2?
JACK1 and JACK2 are two different implementations of the same API. The API
is defined in C. Your code should work with ZERO changes regardless of the
version of JACK used at run time. If you want a C++ API wrapper for JACK,
there is at least floating around online.
You've entirely misunderstood what JACK2 is, it appears.
4:07 p.m.
On Tue, Mar 31, 2015 at 2:02 PM, Vaclav Mach <vaclav.mach(a)artisys.aero> wrote:
What am I doing wrong? Or is it a bad way of using
JACK2?
Hi,
You seem to want to write JACK clients - using C++. To do this you use
the JACK C API, which is the same for JACK 1 and JACK 2. Details of
the difference between JACK1 / JACK2 available[1] - but note that as a
JACK client developer, you do *not* need to care :)
For example: instead of #include <jack/jack.h>
I'm trying to #include "jack2/JackServer.h".
You misunderstand how
JACK2 works - JACK2 implements the same JACK C
API as JACK1. You do not need to, and should not directly include any
JACK implementation in your code.
Hope this makes some sense, cheers, -Harry
[1] https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_j…
--
http://www.openavproductions.com
1 Apr
1 Apr
8:30 a.m.
On 03/31/2015 04:07 PM, Harry van Haaren wrote:
You seem to want to write JACK clients - using C++.
In fact, I'd like to
implement a wrapper for both server and clients
You misunderstand how JACK2 works - JACK2 implements
the same JACK C
API as JACK1. You do not need to, and should not directly include any
JACK implementation in your code.
Yes, after all your answers, I finally understood
the concept.
However, I was confused of the version I have in my Gentoo Portage. The
available stable version of jack is 0.121.3-r1 where jslist.h and
systemdeps.h are missing. First I tried to simply copy these two headers
from jack2 github repository. I was not sure about the correctness of
this process, so I installed the proaudio overlay, emerged jack2
(1.9.10) and everything seems to work fine now.
Another point which is confusing to me is that after running a very
simple code, where the only jack running method is
jackctl_server_create(NULL, NULL); I obtain this leak summary
LEAK SUMMARY:
definitely lost: 1,320 bytes in 5 blocks
indirectly lost: 7,680 bytes in 4 blocks
possibly lost: 272,683 bytes in 7,782 blocks
still reachable: 370 bytes in 9 blocks
suppressed: 0 bytes in 0 blocks
and all the detailed leaks look like
64,656 bytes in 898 blocks are possibly lost in loss record 155 of 155
at 0x4C2C050: calloc (vg_replace_malloc.c:623)
by 0x53497EE: _snd_config_make (in /usr/lib64/libasound.so.2.0.0)
by 0x5349875: _snd_config_make_add (in /usr/lib64/libasound.so.2.0.0)
by 0x534B5BB: parse_defs (in /usr/lib64/libasound.so.2.0.0)
by 0x534B834: parse_defs (in /usr/lib64/libasound.so.2.0.0)
by 0x534BB86: snd_config_load1 (in /usr/lib64/libasound.so.2.0.0)
by 0x534BD91: config_file_open (in /usr/lib64/libasound.so.2.0.0)
by 0x534D7B0: snd_config_hook_load (in /usr/lib64/libasound.so.2.0.0)
by 0x534E222: snd_config_hooks.constprop.6 (in
/usr/lib64/libasound.so.2.0.0)
by 0x534E85A: snd_config_update_r (in /usr/lib64/libasound.so.2.0.0)
by 0x534ECE4: snd_config_update (in /usr/lib64/libasound.so.2.0.0)
by 0x53570D1: snd_ctl_open (in /usr/lib64/libasound.so.2.0.0)
But it seems to be not an issue of Jack
Thanks for any advice, comments...
2:13 p.m.
On Wed, Apr 1, 2015 at 2:30 AM, Vaclav Mach <vaclav.mach(a)artisys.aero>
wrote:
On 03/31/2015 04:07 PM, Harry van Haaren wrote:
unless you propose to write a new implementation of JACK, please forget
about the server. Normal JACK programming does NOT involve writing JACK
servers. It might involve starting and controlling them (via the control
API), but this client side, not server side.
You seem to want to write JACK clients - using C++.
In fact, I'd like to implement a wrapper for both server and clients
31 Mar
31 Mar
8:58 p.m.
On Tue, Mar 31, 2015 at 03:02:45PM +0200, Vaclav Mach wrote:
For example: instead of #include <jack/jack.h>
I'm trying to
#include "jack2/JackServer.h".
There are no example files.
What am I doing wrong? Or is it a bad way of using JACK2?
It is. Jack2 is written in C++, but the API is the same as
for Jack1 and defined in jack/jack.h, which you will find
in /usr/include or /usr/local/include. Any header file that
that is not there is not part of the public API but of the
source distribution. That goes for *any* package BTW.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
3307
days inactive
3308
days old
linux-audio-dev@lists.linuxaudio.org
6 comments
5 participants
participants (5)
-
Fons Adriaensen -
Harry van Haaren -
Len Ovens -
Paul Davis -
Vaclav Mach