Nabble - Jack Audio

Re: Jack2: Jackd and jackdbus

2009-12-24T10:52:02Z

Patrick Shirkey wrote:

>
> On 12/25/2009 05:21 AM, rosea grammostola wrote:
>> Nedko Arnaudov wrote:
>>> rosea grammostola <rosea.grammostola@...> writes:
>>>
>>>> Because I think a Linux audio session handler could improve my
>>>> workflow on Linux a lot, I am testing the new LADI software. To be
>>>> able to use it, I need jackdbus, so I builded jack2 with --dbus,
>>>> --classic and --prefix=/usr/
>>>>
>>>> I can imagine that it is not preferable to have two types of Jack on
>>>> the Linux platform. But alas, it seems the situation is so now, if you
>>>> want to use LADI. This might be more a point for developers to
>>>> discuss.
>>>>
>>>> My question is NOT about whether jackdbus is bad in itself or not. But
>>>> it's more about having them both installed on my system. Let assume I
>>>> have Jack2 build as described, so having both jackd and jackdbus on my
>>>> (Debian) system. Are there disadvantages to have it like this and how
>>>> bad is that?
>>>>
>>>> One step further would be the situation where distributions have both
>>>> jackd and jackdbus installed. What could be good or bad about this?
>>>> Would this be problematic or not?
>>>
>>> jack2 distro packagers should read this:
>>>
>>> http://trac.jackaudio.org/wiki/JackDbusPackaging
>>>
>>> That page describes pros and cons of the mixed scenario. The pros and
>>> cons are there mainly to help packagers decide how to package
>>> jack2. The text for the mixed scenario:
>>>
>>> Both D-Bus launcher (jackdbus executable) and classic launcher (jackd
>>> executable) are installed. Server auto-launching is implemented as
>>> fork+exec (starting new process) of jackd executable - the classic JACK
>>> server launcher. Audio card negotiation with PulseAudio in implemented
>>> in jackdbus only.
>>>
>>> * Pros:
>>> * If D-Bus session bus gets misconfigured/non-functional, user is
>>> able to fallback to jackd, with its pros and cons. * User
>>> can start the JACK server both through jackdbus and jackd (and
>>> thus through qjackctl too).
>>> * Audio card negotiation with PulseAudio if and only if jackdbus is
>>> used.
>>> * Cons:
>>> * non-dbus aware tools (like qjackctl) or auto-launching will start
>>> jackd, associated with: * User is blind about what happens
>>> with JACK server execution if
>>> jackd is autolaunched. * No JACK D-Bus aware
>>> control/monitor applications can be
>>> used. They will claim JACK server is not started (cannot be
>>> contacted) even when JACK server is actually running and normal
>>> JACK applications are connected and probably using it. *
>>> PulseAudio will not know whether JACK server is running
>>> * jackd and jackdbus will use different storage for JACK server
>>> configuration. jackd will be typically started through the
>>> ~/.jackdrc *script* or qjackctl. jackdbus reads and stores
>>> settings
>>> in ~/.config/jack/conf.xml
>>>
>> Thanks.
>> So having jackdbus support in qjackctl and/or in jackpanel would
>> solve at least an part of the problem...
>>
>> Is this planned?
>>
>
>
> Latest qjackctl has basic dbus support already. I haven't tested it
> yet and have seen no reports either.
>

I think I use the last without problems.

But dbus support doesn't mean jackdbus support afaik. It would things
more easy to have jackdbus support in qjackctl. So you as a user can
choose to stick with either jackd or jackdbus.

Btw. What do people on this list advise people to do? Choose for jackd,
jackdbus or both? I'm interested in your opinions.

\r
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Jack2: Jackd and jackdbus

2009-12-24T10:42:36Z

On 12/25/2009 05:21 AM, rosea grammostola wrote:

> Nedko Arnaudov wrote:
>> rosea grammostola <rosea.grammostola@...> writes:
>>
>>> Because I think a Linux audio session handler could improve my
>>> workflow on Linux a lot, I am testing the new LADI software. To be
>>> able to use it, I need jackdbus, so I builded jack2 with --dbus,
>>> --classic and --prefix=/usr/
>>>
>>> I can imagine that it is not preferable to have two types of Jack on
>>> the Linux platform. But alas, it seems the situation is so now, if you
>>> want to use LADI. This might be more a point for developers to
>>> discuss.
>>>
>>> My question is NOT about whether jackdbus is bad in itself or not. But
>>> it's more about having them both installed on my system. Let assume I
>>> have Jack2 build as described, so having both jackd and jackdbus on my
>>> (Debian) system. Are there disadvantages to have it like this and how
>>> bad is that?
>>>
>>> One step further would be the situation where distributions have both
>>> jackd and jackdbus installed. What could be good or bad about this?
>>> Would this be problematic or not?
>>
>> jack2 distro packagers should read this:
>>
>> http://trac.jackaudio.org/wiki/JackDbusPackaging
>>
>> That page describes pros and cons of the mixed scenario. The pros and
>> cons are there mainly to help packagers decide how to package
>> jack2. The text for the mixed scenario:
>>
>> Both D-Bus launcher (jackdbus executable) and classic launcher (jackd
>> executable) are installed. Server auto-launching is implemented as
>> fork+exec (starting new process) of jackd executable - the classic JACK
>> server launcher. Audio card negotiation with PulseAudio in implemented
>> in jackdbus only.
>>
>> * Pros:
>> * If D-Bus session bus gets misconfigured/non-functional, user is
>> able to fallback to jackd, with its pros and cons. * User can
>> start the JACK server both through jackdbus and jackd (and
>> thus through qjackctl too).
>> * Audio card negotiation with PulseAudio if and only if jackdbus is
>> used.
>> * Cons:
>> * non-dbus aware tools (like qjackctl) or auto-launching will start
>> jackd, associated with: * User is blind about what happens
>> with JACK server execution if
>> jackd is autolaunched. * No JACK D-Bus aware
>> control/monitor applications can be
>> used. They will claim JACK server is not started (cannot be
>> contacted) even when JACK server is actually running and normal
>> JACK applications are connected and probably using it. *
>> PulseAudio will not know whether JACK server is running
>> * jackd and jackdbus will use different storage for JACK server
>> configuration. jackd will be typically started through the
>> ~/.jackdrc *script* or qjackctl. jackdbus reads and stores settings
>> in ~/.config/jack/conf.xml
>>
> Thanks.
> So having jackdbus support in qjackctl and/or in jackpanel would solve
> at least an part of the problem...
>
> Is this planned?
>

Latest qjackctl has basic dbus support already. I haven't tested it yet
and have seen no reports either.

Patrick Shirkey
Boost Hardware Ltd

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Jack2: Jackd and jackdbus

2009-12-24T10:21:25Z

Nedko Arnaudov wrote:

> rosea grammostola <rosea.grammostola@...> writes:
>
>
>> Because I think a Linux audio session handler could improve my
>> workflow on Linux a lot, I am testing the new LADI software. To be
>> able to use it, I need jackdbus, so I builded jack2 with --dbus,
>> --classic and --prefix=/usr/
>>
>> I can imagine that it is not preferable to have two types of Jack on
>> the Linux platform. But alas, it seems the situation is so now, if you
>> want to use LADI. This might be more a point for developers to
>> discuss.
>>
>> My question is NOT about whether jackdbus is bad in itself or not. But
>> it's more about having them both installed on my system. Let assume I
>> have Jack2 build as described, so having both jackd and jackdbus on my
>> (Debian) system. Are there disadvantages to have it like this and how
>> bad is that?
>>
>> One step further would be the situation where distributions have both
>> jackd and jackdbus installed. What could be good or bad about this?
>> Would this be problematic or not?
>>
>
> jack2 distro packagers should read this:
>
> http://trac.jackaudio.org/wiki/JackDbusPackaging
>
> That page describes pros and cons of the mixed scenario. The pros and
> cons are there mainly to help packagers decide how to package
> jack2. The text for the mixed scenario:
>
> Both D-Bus launcher (jackdbus executable) and classic launcher (jackd
> executable) are installed. Server auto-launching is implemented as
> fork+exec (starting new process) of jackd executable - the classic JACK
> server launcher. Audio card negotiation with PulseAudio in implemented
> in jackdbus only.
>
> * Pros:
> * If D-Bus session bus gets misconfigured/non-functional, user is
> able to fallback to jackd, with its pros and cons.
> * User can start the JACK server both through jackdbus and jackd (and
> thus through qjackctl too).
> * Audio card negotiation with PulseAudio if and only if jackdbus is
> used.
> * Cons:
> * non-dbus aware tools (like qjackctl) or auto-launching will start
> jackd, associated with:
> * User is blind about what happens with JACK server execution if
> jackd is autolaunched.
> * No JACK D-Bus aware control/monitor applications can be
> used. They will claim JACK server is not started (cannot be
> contacted) even when JACK server is actually running and normal
> JACK applications are connected and probably using it.
> * PulseAudio will not know whether JACK server is running
> * jackd and jackdbus will use different storage for JACK server
> configuration. jackd will be typically started through the
> ~/.jackdrc *script* or qjackctl. jackdbus reads and stores settings
> in ~/.config/jack/conf.xml
>
>

Thanks.
So having jackdbus support in qjackctl and/or in jackpanel would solve
at least an part of the problem...

Is this planned?

\r
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Connecting jackd to jackd

2009-12-24T10:16:04Z

On 12/25/2009 12:23 AM, Paul Davis wrote:

> On Thu, Dec 24, 2009 at 6:07 AM, Patrick Shirkey
> <pshirkey@...> wrote:
>
>> Hi,
>>
>> It's probably been discussed before but why do we not have a parent->child
>> option for running multiple jack instances?
>>
>> ie.
>>
>> jackd -i jack01 -d alsa -d hw:1,0
>>
>> jackd -i jack02 -d jack01
>>
> what possible use would that serve? You would have two JACK graphs,
> one triggered from the other. What's the gain here?
>

I'm thinking it might be an effective way to handle session management
with multiple sessions at the same time.

I'm not sure how much load managing each graph would require.

Patrick Shirkey
Boost Hardware Ltd

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Jack2: Jackd and jackdbus

2009-12-24T08:02:46Z

On Thu, Dec 24, 2009 at 9:31 AM, Nedko Arnaudov <nedko@...> wrote:

> "Jack O'Quin" <jack.oquin@...> writes:
>
>> On Thu, Dec 24, 2009 at 7:47 AM, rosea grammostola
>> <rosea.grammostola@...> wrote:
>>> Paul Davis wrote:
>>>>
>>>> more than this: you should assume that you cannot ever have *any* 2
>>>> versions of JACK simultaneously installed, even JACK 0.118.0 and
>>>> 0.118.2 or other similarly "close" versions. JACK is composed of a
>>>> server, a set of backends and a client library, and the versions of
>>>> each one must match precisely for things to work.
>>>
>>> Uh, but I have now two versions, both JACK2, jackd and jackdbus. And it
>>> seems to work ok...
>>> Could you answer my question a bit more specific towards the jackd and
>>> jackdbus case?
>>
>> He did answer your question: he said "don't do that".
>>
>> Complex system software like JACK embodies many complex design
>> assumptions that need to be met for reliable operation. One of the
>> most deeply embedded assumptions behind the JACK design is that the
>> server and the library version match *exactly*.
>>
>> Saying that "it seems to work ok" misses the point. Paul did not say
>> "it will never work", he said you should not *assume* it will work.
>
> jackd and jackdbus are executables that are frontends/launchers to very
> same JACK server. And it works indeed. Paul`s point was about different
> versions not about different frontends/launchers.

Correct. That was stated very explicitly by both of us.
--
joq
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Connecting jackd to jackd

2009-12-24T07:38:28Z

Paul Davis <paul@...> writes:

> On Thu, Dec 24, 2009 at 6:07 AM, Patrick Shirkey
> <pshirkey@...> wrote:
>> Hi,
>>
>> It's probably been discussed before but why do we not have a parent->child
>> option for running multiple jack instances?
>>
>> ie.
>>
>> jackd -i jack01 -d alsa -d hw:1,0
>>
>> jackd -i jack02 -d jack01
>
> what possible use would that serve? You would have two JACK graphs,
> one triggered from the other. What's the gain here?

While I'm not sure why Patrick wants to do this, ladish aims to provide
something very similar by fragmenting the JACK graph. Apps sit in
"jails" (chroot analogy) where they see (can use) only part of the JACK
graph. These "jails" are called rooms in ladish and provide virtual
hardware ports. Projects (sessions) are loaded in rooms. Room virtual
ports appear in the studio (a fragment of the JACK graph too) and user
connects them to the real physical JACK ports.

--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

attachment0 (203 bytes) Download Attachment

From forum: Jackit

Re: Jack2: Jackd and jackdbus

2009-12-24T07:31:20Z

"Jack O'Quin" <jack.oquin@...> writes:

> On Thu, Dec 24, 2009 at 7:47 AM, rosea grammostola
> <rosea.grammostola@...> wrote:
>> Paul Davis wrote:
>>>
>>> On Thu, Dec 24, 2009 at 6:02 AM, Patrick Shirkey
>>> <pshirkey@...> wrote:
>>>
>>>
>>>>
>>>> My understanding is that you cannot have jack1 and jack2 installed in the
>>>> same dir as they have create identically named library and binary files
>>>> with
>>>> only the internal versioning symbols and applications details being
>>>> different.
>>>>
>>>
>>> more than this: you should assume that you cannot ever have *any* 2
>>> versions of JACK simultaneously installed, even JACK 0.118.0 and
>>> 0.118.2 or other similarly "close" versions. JACK is composed of a
>>> server, a set of backends and a client library, and the versions of
>>> each one must match precisely for things to work.
>>
>> Uh, but I have now two versions, both JACK2, jackd and jackdbus. And it
>> seems to work ok...
>> Could you answer my question a bit more specific towards the jackd and
>> jackdbus case?
>
> He did answer your question: he said "don't do that".
>
> Complex system software like JACK embodies many complex design
> assumptions that need to be met for reliable operation. One of the
> most deeply embedded assumptions behind the JACK design is that the
> server and the library version match *exactly*.
>
> Saying that "it seems to work ok" misses the point. Paul did not say
> "it will never work", he said you should not *assume* it will work.

jackd and jackdbus are executables that are frontends/launchers to very
same JACK server. And it works indeed. Paul`s point was about different
versions not about different frontends/launchers.

--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

attachment0 (203 bytes) Download Attachment

From forum: Jackit

Re: Jack2: Jackd and jackdbus

2009-12-24T07:26:53Z

rosea grammostola <rosea.grammostola@...> writes:

> Because I think a Linux audio session handler could improve my
> workflow on Linux a lot, I am testing the new LADI software. To be
> able to use it, I need jackdbus, so I builded jack2 with --dbus,
> --classic and --prefix=/usr/
>
> I can imagine that it is not preferable to have two types of Jack on
> the Linux platform. But alas, it seems the situation is so now, if you
> want to use LADI. This might be more a point for developers to
> discuss.
>
> My question is NOT about whether jackdbus is bad in itself or not. But
> it's more about having them both installed on my system. Let assume I
> have Jack2 build as described, so having both jackd and jackdbus on my
> (Debian) system. Are there disadvantages to have it like this and how
> bad is that?
>
> One step further would be the situation where distributions have both
> jackd and jackdbus installed. What could be good or bad about this?
> Would this be problematic or not?

jack2 distro packagers should read this:

http://trac.jackaudio.org/wiki/JackDbusPackaging

That page describes pros and cons of the mixed scenario. The pros and
cons are there mainly to help packagers decide how to package
jack2. The text for the mixed scenario:

Both D-Bus launcher (jackdbus executable) and classic launcher (jackd
executable) are installed. Server auto-launching is implemented as
fork+exec (starting new process) of jackd executable - the classic JACK
server launcher. Audio card negotiation with PulseAudio in implemented
in jackdbus only.

* Pros:
* If D-Bus session bus gets misconfigured/non-functional, user is
able to fallback to jackd, with its pros and cons.
* User can start the JACK server both through jackdbus and jackd (and
thus through qjackctl too).
* Audio card negotiation with PulseAudio if and only if jackdbus is
used.
* Cons:
* non-dbus aware tools (like qjackctl) or auto-launching will start
jackd, associated with:
* User is blind about what happens with JACK server execution if
jackd is autolaunched.
* No JACK D-Bus aware control/monitor applications can be
used. They will claim JACK server is not started (cannot be
contacted) even when JACK server is actually running and normal
JACK applications are connected and probably using it.
* PulseAudio will not know whether JACK server is running
* jackd and jackdbus will use different storage for JACK server
configuration. jackd will be typically started through the
~/.jackdrc *script* or qjackctl. jackdbus reads and stores settings
in ~/.config/jack/conf.xml

--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

attachment0 (203 bytes) Download Attachment

From forum: Jackit

Re: Jack2: Jackd and jackdbus

2009-12-24T06:56:04Z

On Thu, 24 Dec 2009 08:39:23 -0600, "Jack O'Quin" <jack.oquin@...>
wrote:

files

>>>> with
>>>> only the internal versioning symbols and applications details being
>>>> different.
>>>>
>>>
>>> more than this: you should assume that you cannot ever have *any* 2
>>> versions of JACK simultaneously installed, even JACK 0.118.0 and
>>> 0.118.2 or other similarly "close" versions. JACK is composed of a
>>> server, a set of backends and a client library, and the versions of
>>> each one must match precisely for things to work.
>>
>> Uh, but I have now two versions, both JACK2, jackd and jackdbus. And it
>> seems to work ok...
>> Could you answer my question a bit more specific towards the jackd and
>> jackdbus case?
>
> He did answer your question: he said "don't do that".
>
> Complex system software like JACK embodies many complex design
> assumptions that need to be met for reliable operation. One of the
> most deeply embedded assumptions behind the JACK design is that the
> server and the library version match *exactly*.
>
> Saying that "it seems to work ok" misses the point. Paul did not say
> "it will never work", he said you should not *assume* it will work.

Hey there,

Ok, I'll try to clarify here, since the original question remains mostly
misunderstood.

You have only 1 (one) jack 2 version installed on your PC. not 2 (two),
but 1 (one). You happen to have done the classic + dbus install. That's not
2 versions, but 2 options of a same version installed.

--
Marc-Olivier Barre
XMPP ID : marco@...
www.MarcOChapeau.org
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Jack2: Jackd and jackdbus

2009-12-24T06:39:23Z

On Thu, Dec 24, 2009 at 7:47 AM, rosea grammostola
<rosea.grammostola@...> wrote:

> Paul Davis wrote:
>>
>> On Thu, Dec 24, 2009 at 6:02 AM, Patrick Shirkey
>> <pshirkey@...> wrote:
>>
>>
>>>
>>> My understanding is that you cannot have jack1 and jack2 installed in the
>>> same dir as they have create identically named library and binary files
>>> with
>>> only the internal versioning symbols and applications details being
>>> different.
>>>
>>
>> more than this: you should assume that you cannot ever have *any* 2
>> versions of JACK simultaneously installed, even JACK 0.118.0 and
>> 0.118.2 or other similarly "close" versions. JACK is composed of a
>> server, a set of backends and a client library, and the versions of
>> each one must match precisely for things to work.
>
> Uh, but I have now two versions, both JACK2, jackd and jackdbus. And it
> seems to work ok...
> Could you answer my question a bit more specific towards the jackd and
> jackdbus case?

He did answer your question: he said "don't do that".

Complex system software like JACK embodies many complex design
assumptions that need to be met for reliable operation. One of the
most deeply embedded assumptions behind the JACK design is that the
server and the library version match *exactly*.

Saying that "it seems to work ok" misses the point. Paul did not say
"it will never work", he said you should not *assume* it will work.
--
joq
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Jack2: Jackd and jackdbus

2009-12-24T05:47:12Z

Paul Davis wrote:

> On Thu, Dec 24, 2009 at 6:02 AM, Patrick Shirkey
> <pshirkey@...> wrote:
>
>
>> My understanding is that you cannot have jack1 and jack2 installed in the
>> same dir as they have create identically named library and binary files with
>> only the internal versioning symbols and applications details being
>> different.
>>
>
> more than this: you should assume that you cannot ever have *any* 2
> versions of JACK simultaneously installed, even JACK 0.118.0 and
> 0.118.2 or other similarly "close" versions. JACK is composed of a
> server, a set of backends and a client library, and the versions of
> each one must match precisely for things to work.

Uh, but I have now two versions, both JACK2, jackd and jackdbus. And it
seems to work ok...
Could you answer my question a bit more specific towards the jackd and
jackdbus case?

\r
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Connecting jackd to jackd

2009-12-24T05:23:50Z

On Thu, Dec 24, 2009 at 6:07 AM, Patrick Shirkey
<pshirkey@...> wrote:

> Hi,
>
> It's probably been discussed before but why do we not have a parent->child
> option for running multiple jack instances?
>
> ie.
>
> jackd -i jack01 -d alsa -d hw:1,0
>
> jackd -i jack02 -d jack01

what possible use would that serve? You would have two JACK graphs,
one triggered from the other. What's the gain here?
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Jack2: Jackd and jackdbus

2009-12-24T05:19:25Z

On Thu, Dec 24, 2009 at 6:02 AM, Patrick Shirkey
<pshirkey@...> wrote:

> My understanding is that you cannot have jack1 and jack2 installed in the
> same dir as they have create identically named library and binary files with
> only the internal versioning symbols and applications details being
> different.

more than this: you should assume that you cannot ever have *any* 2
versions of JACK simultaneously installed, even JACK 0.118.0 and
0.118.2 or other similarly "close" versions. JACK is composed of a
server, a set of backends and a client library, and the versions of
each one must match precisely for things to work.
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Connecting jackd to jackd

2009-12-24T03:07:30Z

Hi,

It's probably been discussed before but why do we not have a
parent->child option for running multiple jack instances?

ie.

jackd -i jack01 -d alsa -d hw:1,0

jackd -i jack02 -d jack01

-i = instance name

Cheers.

--
Patrick Shirkey
Boost Hardware Ltd

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Jack2: Jackd and jackdbus

2009-12-24T03:02:09Z

On 12/24/2009 09:23 PM, rosea grammostola wrote:

> Hi all,
>
>
> Because I think a Linux audio session handler could improve my
> workflow on Linux a lot, I am testing the new LADI software. To be
> able to use it, I need jackdbus, so I builded jack2 with --dbus,
> --classic and --prefix=/usr/
>
> I can imagine that it is not preferable to have two types of Jack on
> the Linux platform. But alas, it seems the situation is so now, if you
> want to use LADI. This might be more a point for developers to discuss.
>
> My question is NOT about whether jackdbus is bad in itself or not. But
> it's more about having them both installed on my system. Let assume I
> have Jack2 build as described, so having both jackd and jackdbus on my
> (Debian) system. Are there disadvantages to have it like this and how
> bad is that?
>
> One step further would be the situation where distributions have both
> jackd and jackdbus installed. What could be good or bad about this?
> Would this be problematic or not?
>

My understanding is that you cannot have jack1 and jack2 installed in
the same dir as they have create identically named library and binary
files with only the internal versioning symbols and applications details
being different.

It would be handy in some aspects if this were not the case but in other
aspects it would create a lot of confusion for non initated users.

Patrick Shirkey
Boost Hardware Ltd

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Jack2: Jackd and jackdbus

2009-12-24T02:23:58Z

Hi all,

Because I think a Linux audio session handler could improve my workflow
on Linux a lot, I am testing the new LADI software. To be able to use
it, I need jackdbus, so I builded jack2 with --dbus, --classic and
--prefix=/usr/

I can imagine that it is not preferable to have two types of Jack on the
Linux platform. But alas, it seems the situation is so now, if you want
to use LADI. This might be more a point for developers to discuss.

My question is NOT about whether jackdbus is bad in itself or not. But
it's more about having them both installed on my system. Let assume I
have Jack2 build as described, so having both jackd and jackdbus on my
(Debian) system. Are there disadvantages to have it like this and how
bad is that?

One step further would be the situation where distributions have both
jackd and jackdbus installed. What could be good or bad about this?
Would this be problematic or not?

Thanks in advance,

\r

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Mic In

2009-12-22T21:45:48Z

I was hoping this would have been more trivial than it has been, but after scouring the forums, I haven't found a suitable solution.

What I would like to do is stream one computers mic input over the network to another computer using JACK. The computers stream the way I want using mpg123. On the mic end, everything is unmuted and ready to go, as the mic input loops to the soundcard output (no idea how to turn this off, but doesnt really matter). The only thing I'm missing is how to connect alsa's mic in to JACK's playback channels. Any thoughts? I've tried mucking around with .asoundrc, but the formatting is above my head. Also, this is all command line, I don't have access to qjackctrl.

Thanks,
Matt

From forum: Jackit

Re: Other port type than JACK_DEFAULT_AUDIO_TYPE

2009-12-19T03:25:33Z

Martin Schneider wrote:

> Hi everyone,
>
> maybe this question seems to be rather stupid, but after spending a few
> hours of searching the web it is still there. Is it possible to use
> other port types than JACK_DEFAULT_AUDIO_TYPE or JACK_DEFAULT_MIDI_TYPE
> and other data types accordingly?
>
> I my case I need to transfer complex values "complex double" from one
> application to another. So I tried:
>

[...]

Hi Martin,

most probably you're doing this already, but...
...anyhow: As a quick hack interim solution I'd propose to transmit the
real and the imaginary part on different ports (or any other two
dimensions of an appropriate representation). The increased number of
ports shouldn't pose any problems since I don't think you're going to
send complex values to a physical port. Are there any sound cards that
take complex sample values? You aren't building a jack interface for
some software defined HF transmitter, are you? ;-)

ciao!
Achim

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Other port type than JACK_DEFAULT_AUDIO_TYPE

2009-12-18T02:44:40Z

Le 18 déc. 2009 à 10:25, Nedko Arnaudov a écrit :

> Martin Schneider <schneider@...> writes:
>
>> maybe this question seems to be rather stupid, but after spending a few
>> hours of searching the web it is still there. Is it possible to use
>> other port types than JACK_DEFAULT_AUDIO_TYPE or JACK_DEFAULT_MIDI_TYPE
>> and other data types accordingly?
>>
>> I my case I need to transfer complex values "complex double" from one
>> application to another. So I tried:
>>
>> jack_port_register (myclient, "some name", "complex audio",\
>> JackPortIsInput, sizeof(complex double)*buffer_size )
>>
>> which fails (returns NULL) without any useful error message when I do
>> not use JACK_DEFAULT_AUDIO_TYPE instead of "complex audio".
>> Nevertheless, the documentation says:
>>
>> "All ports have a type, which may be any non-NULL and non-zero length
>> string, passed as an argument. Some port types are built into the JACK
>> API, like JACK_DEFAULT_AUDIO_TYPE or JACK_DEFAULT_MIDI_TYPE"
>>
>> which suggests that there are other possibilities. Unfortunately I could
>> not find any programming examples on this nor more precise information
>> in the documentation.
>
> IMO, ability to register and use arbitrary port types should be
> available. Maybe configure time or runtime engine option for
> enabling/disabling it should be available too.

Thanks to the work done by Dmitry Baikov on the JACK MIDI port implementation in JACK2, this is already some abstraction done to represent port types: port types have to define how they are "initialized" and how they are "mixed" (assuming mixing data for the given port type makes sense...) (OTOH I don't think the port connection logic is ready to support port types where mixing would not make sense...; but it would not be complex to add that)

> OTOH, it seems more
> reasonable to have plugins loaded by JACK server that will handle port
> types. Such plugins combined with the more flexible driver
> infrastructure that is emerging in jack2 could be made to allow
> implementation of videojack over [non-forked] jack core.

Plugin way would be an idea to add new ports types, but there is still some deeper questions in the video case : handling video and audio in the *same* activation graph, (that is the same RT thread on client side) is presumably not a so good idea (video data are huge but less frequent and possibly require to be processed in a thread with lower priority than the audio one...)

So, interesting problem...

Martin, what is the typical user case of your "transfering complex double" example?

Stéphane
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Other port type than JACK_DEFAULT_AUDIO_TYPE

2009-12-18T02:44:17Z

On Fri, Dec 18, 2009 at 11:25:03AM +0200, Nedko Arnaudov wrote:

> Martin Schneider <schneider@...> writes:
>
> > maybe this question seems to be rather stupid, but after spending a few
> > hours of searching the web it is still there. Is it possible to use
> > other port types than JACK_DEFAULT_AUDIO_TYPE or JACK_DEFAULT_MIDI_TYPE
> > and other data types accordingly?
> >
> > I my case I need to transfer complex values "complex double" from one
> > application to another. So I tried:
> >
> > jack_port_register (myclient, "some name", "complex audio",\
> > JackPortIsInput, sizeof(complex double)*buffer_size )
> >
> > which fails (returns NULL) without any useful error message when I do
> > not use JACK_DEFAULT_AUDIO_TYPE instead of "complex audio".
> > Nevertheless, the documentation says:
> >
> > "All ports have a type, which may be any non-NULL and non-zero length
> > string, passed as an argument. Some port types are built into the JACK
> > API, like JACK_DEFAULT_AUDIO_TYPE or JACK_DEFAULT_MIDI_TYPE"
> >
> > which suggests that there are other possibilities. Unfortunately I could
> > not find any programming examples on this nor more precise information
> > in the documentation.
>
> IMO, ability to register and use arbitrary port types should be
> available. Maybe configure time or runtime engine option for
> enabling/disabling it should be available too. OTOH, it seems more
> reasonable to have plugins loaded by JACK server that will handle port
> types. Such plugins combined with the more flexible driver
> infrastructure that is emerging in jack2 could be made to allow
> implementation of videojack over [non-forked] jack core.

videojack is running at a different framerate.
its not just another datatype with different mixdown semantics.

the question is whether we want to have 2 jackd running with different
framerates. or enable process callbacks at different rates.

--
torben Hohn
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Other port type than JACK_DEFAULT_AUDIO_TYPE

2009-12-18T01:25:03Z

Martin Schneider <schneider@...> writes:

> maybe this question seems to be rather stupid, but after spending a few
> hours of searching the web it is still there. Is it possible to use
> other port types than JACK_DEFAULT_AUDIO_TYPE or JACK_DEFAULT_MIDI_TYPE
> and other data types accordingly?
>
> I my case I need to transfer complex values "complex double" from one
> application to another. So I tried:
>
> jack_port_register (myclient, "some name", "complex audio",\
> JackPortIsInput, sizeof(complex double)*buffer_size )
>
> which fails (returns NULL) without any useful error message when I do
> not use JACK_DEFAULT_AUDIO_TYPE instead of "complex audio".
> Nevertheless, the documentation says:
>
> "All ports have a type, which may be any non-NULL and non-zero length
> string, passed as an argument. Some port types are built into the JACK
> API, like JACK_DEFAULT_AUDIO_TYPE or JACK_DEFAULT_MIDI_TYPE"
>
> which suggests that there are other possibilities. Unfortunately I could
> not find any programming examples on this nor more precise information
> in the documentation.

IMO, ability to register and use arbitrary port types should be
available. Maybe configure time or runtime engine option for
enabling/disabling it should be available too. OTOH, it seems more
reasonable to have plugins loaded by JACK server that will handle port
types. Such plugins combined with the more flexible driver
infrastructure that is emerging in jack2 could be made to allow
implementation of videojack over [non-forked] jack core.

--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

attachment0 (194 bytes) Download Attachment

From forum: Jackit

Jackdmp 1.9.2 archive?

2009-12-17T14:07:12Z

Hello All

Does anybody know where I can download the archive of Jackdmp 1.9.2 for Windows?

I need to test an issue and cant find the download anywhere

Best Regards and appreciate the help!

-------- Original Message --------
Subject: Re: [Jack-Devel] Completely crazy: Linux to Windows by
netjack?
From: Peter L Jones <gmane@...>
Date: Tue, December 15, 2009 10:17 am
To: jack-devel@...

torbenh wrote:
> i guess i need to take the plunge and get wine asio to build.
> mapping jack_transport to the asio equivalent was on my list anyways.
> i had postponed that, because of problems with this thiscall stuff.

Any problems with building wineasio... erk, that's one I maintain! :D

>
>
>> Also, I guess I'm missing something but I couldn't see how to bring up the
>> netone server on Windows.
>
> define netone server.
> do you mean slave ?

My windows machine is the one with a soundcard in. I have Jackd 0.116 on
Ubuntu (started with "-d net") as the slave.

Thanks again,

-- Peter

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Other port type than JACK_DEFAULT_AUDIO_TYPE

2009-12-17T10:07:29Z

Hi everyone,

maybe this question seems to be rather stupid, but after spending a few
hours of searching the web it is still there. Is it possible to use
other port types than JACK_DEFAULT_AUDIO_TYPE or JACK_DEFAULT_MIDI_TYPE
and other data types accordingly?

I my case I need to transfer complex values "complex double" from one
application to another. So I tried:

jack_port_register (myclient, "some name", "complex audio",\
JackPortIsInput, sizeof(complex double)*buffer_size )

which fails (returns NULL) without any useful error message when I do
not use JACK_DEFAULT_AUDIO_TYPE instead of "complex audio".
Nevertheless, the documentation says:

"All ports have a type, which may be any non-NULL and non-zero length
string, passed as an argument. Some port types are built into the JACK
API, like JACK_DEFAULT_AUDIO_TYPE or JACK_DEFAULT_MIDI_TYPE"

which suggests that there are other possibilities. Unfortunately I could
not find any programming examples on this nor more precise information
in the documentation.

Thanks for your attention.

Bye Martin

[schneider.vcf]

begin:vcard fn:Martin Schneider n:Schneider;Martin org;quoted-printable;quoted-printable:Universit=C3=A4t Erlangen-N=C3=BCrnberg;Lehrstuhl f=C3=BCr Multimediakommunikation und Signalverarbeitung adr;quoted-printable:;;Cauerstra=C3=9Fe 7;Erlangen;;91058;Germany email;internet:schneider@... title:Dipl.-Ing. tel;work:+49 9131 85 27105 tel;fax:+49 9131 85 28849 x-mozilla-html:FALSE version:2.1 end:vcard

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Completely crazy: Linux to Windows by netjack? (And ASIO)

2009-12-17T01:47:55Z

Le 16 déc. 2009 à 21:03, Peter L Jones a écrit :

> Stéphane Letz wrote:
>>> cvs -z3 -d:pserver:anonymous@...:/cvsroot/jackosx
>>> co JackWASIO
>>>
>>> looks like it was intented for osx. dunno. on windows one doesnt need the
>>> separate winethread. i couldnt find sources of JackRouter.dll .. so i took
>>> winasio.
>>>
>>
>> This winasio stuff was done on OSX for access by wine. Not to be used in our
>> case.
>
> I will check it out -- if it's a branch of wineasio, I'd like to see where it
> diverged and if it can be rolled into the main line.
>
>>
>> Windows JackRouter.dll project is *not* yet public yes... well I don't think
>> it should go in JackOSX project, and I don't think it should directly go in
>> JACK2 SVN either.
>
> It's not? I feel it's a huge value add for Jack on Windows (as ASIO is what
> most "pro audio" users' software will expect as a driver).
>
>>
>> So should we place this JackRouter stuff in a new place?
>
> There's a "windows" folder for Jack2 already with some various bits in (e.g.
> winmme driver for MIDI); would that not be an appropriate place?
>
>>
>> Or define sub-projects on JACK SVN ?
>
> I feel it's merely platform-specific, rather than separate. (Certainly no more
> separate than tools like netjack (**hides** ;) )...)
>

OK, JackRouter sources and project added in JACK2 SVN. Note that compilation needs to install ASIO SDK and correctly refer to some files of the SDK.

Stephane
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

JackWASIO / wineasio

2009-12-16T15:49:25Z

Ah, talking to myself... ;)

Peter L Jones wrote:

Looks like it's a fork of 0.5 and the main line is up to 0.7.5+. I could merge
with 0.5 but I wouldn't like to try a merge with 0.7.5+ as I couldn't test it.
The two aren't /that/ far apart, so it might be more feasible to bring
JackWASIO up to 0.7.5+ (which would be nice as it has some nice features, I
think :)). I also think it might be feasible to then merge it into the main
tree if that's desired.

(I say "0.7.5+" -- 0.7.5 is in SVN but I have a patch for building under 64bit
Ubuntu that I need to finish. It's currently not backward-compatible with
32bit...)

Regards,

-- Peter

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Completely crazy: Linux to Windows by netjack? (And ASIO)

2009-12-16T12:03:49Z

Stéphane Letz wrote:

>> cvs -z3 -d:pserver:anonymous@...:/cvsroot/jackosx
>> co JackWASIO
>>
>> looks like it was intented for osx. dunno. on windows one doesnt need the
>> separate winethread. i couldnt find sources of JackRouter.dll .. so i took
>> winasio.
>>
>
> This winasio stuff was done on OSX for access by wine. Not to be used in our
> case.

I will check it out -- if it's a branch of wineasio, I'd like to see where it
diverged and if it can be rolled into the main line.

>
> Windows JackRouter.dll project is *not* yet public yes... well I don't think
> it should go in JackOSX project, and I don't think it should directly go in
> JACK2 SVN either.

It's not? I feel it's a huge value add for Jack on Windows (as ASIO is what
most "pro audio" users' software will expect as a driver).

>
> So should we place this JackRouter stuff in a new place?

There's a "windows" folder for Jack2 already with some various bits in (e.g.
winmme driver for MIDI); would that not be an appropriate place?

>
> Or define sub-projects on JACK SVN ?

I feel it's merely platform-specific, rather than separate. (Certainly no more
separate than tools like netjack (**hides** ;) )...)

>
>
>>> There is no "jack_netsource" in the jacknone-0.4_setup.exe file --
>>> that's why I was confused.
>> argh :( i have based that branch on 1.9.4 and forgot to add netsource to
>> the installer stuff.
>
> JACK2 SVN is now correct on that also. I just fixed some problems this
> morning. Maybe you should synch the git branch again.
>
> Stéphane

-- Peter

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Jack port names

2009-12-16T08:45:01Z

On Wed, Dec 16, 2009 at 11:40 AM, <linux@...> wrote:
> Go and read Eric Raymonds wonderful essai at:
> http://www.faqs.org/docs/artu/
> and search for "be generous in what you accept, rigorous in what you emit"
>
> That more and more data representation is changed to be more
> human-readable is just not true.

I think you're confused. Applications developers and users provide
port names. JACK simply accepts them subject to a couple of simple
rules, and some JACK utities display them when asked. Quoting is an
old Unix artform. You need it for filenames, you need it for JACK
ports. Done.

--p
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Jack port names

2009-12-16T08:40:42Z

On Sun, Dec 13, 2009 at 09:32:21PM +0100, Melanie wrote:

> Hi,
>
> Tinram wrote:
> > Le dimanche 13 d??cembre 2009 ?? 20:55 +0100, Melanie a ??crit :
> >> In today's GUI driven world, applications that can't handle embedded
> >> spaces are on the wane. One can't look backwards, especially since
> >> most applications using Jack are GUI apps.
> >>
> >> IMHO, if you're dealing with Jack, you need to be able to accept
> >> white space. No use crying for a change to that.
> >>
> >
> > My opinion is just that I think it would be cleaner to manipulate id's in the code and use alias for GUI rather than manipulate string for names and have unused alias...
> >
>
>
> Not being able to manipulate names containing spaces is the hallmark
> of applications that were designed 20 years go.
>
> I know. I designed some of them.
>
> Today, one has to be prepared for spaces. More and more data
> representation is being changed to be human-readable. Why should one
> go to some cryptic, abstract ID?
>
> We have the processing power to throw it away on interpreted
> languages and bytecode stuff. So, what is a string compare?
>
> Melanie
>
> _______________________________________________
> Jack-Devel mailing list
> Jack-Devel@...
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Hello,

I agree with Martin about that it would make things easier if jack
emitted only strings without whitespace. This is one of the
fundamentals of UNIX programming. Just because jack is mostly used by
gui apps, this doesn't mean we have to forget about the art of UNIX
programming.

Go and read Eric Raymonds wonderful essai at:
http://www.faqs.org/docs/artu/
and search for "be generous in what you accept, rigorous in what you emit"

That more and more data representation is changed to be more
human-readable is just not true. In the semantic web for example we do
have a tendency to move to machine-readable formats, in order for
programms to be able to be automated. I don't want to go on about
this, since it's off-topic. Eric Raymond already said enough about it.

Gabriel

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Completely crazy: Linux to Windows by netjack?

2009-12-16T03:33:26Z

>>
>
> cvs -z3 -d:pserver:anonymous@...:/cvsroot/jackosx co JackWASIO
>
> looks like it was intented for osx.
> dunno. on windows one doesnt need the separate winethread.
> i couldnt find sources of JackRouter.dll ..
> so i took winasio.
>

This winasio stuff was done on OSX for access by wine. Not to be used in our case.

Windows JackRouter.dll project is *not* yet public yes... well I don't think it should go in JackOSX project, and I don't think it should directly go in JACK2 SVN either.

So should we place this JackRouter stuff in a new place?

Or define sub-projects on JACK SVN ?

>>
>> There is no "jack_netsource" in the jacknone-0.4_setup.exe file -- that's why I
>> was confused.
>
> argh :( i have based that branch on 1.9.4 and forgot to add netsource
> to the installer stuff.

JACK2 SVN is now correct on that also. I just fixed some problems this morning. Maybe you should synch the git branch again.

Stéphane
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Completely crazy: Linux to Windows by netjack?

2009-12-16T03:09:43Z

On Wed, Dec 16, 2009 at 07:23:28AM +0000, Peter L Jones wrote:

> torbenh wrote:
> > On Tue, Dec 15, 2009 at 06:17:28PM +0000, Peter L Jones wrote:
> >> torbenh wrote:
> >>> i guess i need to take the plunge and get wine asio to build.
> >>> mapping jack_transport to the asio equivalent was on my list anyways.
> >>> i had postponed that, because of problems with this thiscall stuff.
> >> Any problems with building wineasio... erk, that's one I maintain! :D
> >
> > the windows version ?
> > well... i found some weirdly modified version of wineasio in the jackosx
> > svn. i made that compile on windows now, and removed the separate
> > thread.
>
> Windows version of Wineasio?! No, I meant the Linux version. Though if
> there's a Windows version around, I'd like to know -- I'm /trying/ to keep the
> SourceForge site current with all known WineAsio versions.

cvs -z3 -d:pserver:anonymous@...:/cvsroot/jackosx co JackWASIO

looks like it was intented for osx.
dunno. on windows one doesnt need the separate winethread.
i couldnt find sources of JackRouter.dll ..
so i took winasio.

>
> >
> > also added jack_transport via asio timecode. (reaper eats that nicely)
> > in case wine asio doesnt support that yet, i am gonna isolate that.
> > so you can apply it.
>
> Much appreciated.
>
> >
> > the version i have is using 32bit ints. i would be really happy,
> > if i could use float.
> > what is your experience regarding app support ?
>
> It's not something I've looked into.
>
> > i am also interested, if apps honor the process now flag.
> >
>
> Again, not something I've looked into.
>
> >
> >
> >>>
> >>>> Also, I guess I'm missing something but I couldn't see how to bring up the
> >>>> netone server on Windows.
> >>> define netone server.
> >>> do you mean slave ?
> >> My windows machine is the one with a soundcard in. I have Jackd 0.116 on
> >> Ubuntu (started with "-d net") as the slave.
> >
> > and running jack_netsource on the windows machine doesnt work ?
> > dns resolve doesnt work iirc. you need to provide an IP.
>
> There is no "jack_netsource" in the jacknone-0.4_setup.exe file -- that's why I
> was confused.

argh :( i have based that branch on 1.9.4 and forgot to add netsource
to the installer stuff.

>
> >
> >
> >> Thanks again,
> >>
> >> -- Peter
> >
>
> _______________________________________________
> Jack-Devel mailing list
> Jack-Devel@...
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

--
torben Hohn
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Completely crazy: Linux to Windows by netjack?

2009-12-15T23:23:28Z

torbenh wrote:

> On Tue, Dec 15, 2009 at 06:17:28PM +0000, Peter L Jones wrote:
>> torbenh wrote:
>>> i guess i need to take the plunge and get wine asio to build.
>>> mapping jack_transport to the asio equivalent was on my list anyways.
>>> i had postponed that, because of problems with this thiscall stuff.
>> Any problems with building wineasio... erk, that's one I maintain! :D
>
> the windows version ?
> well... i found some weirdly modified version of wineasio in the jackosx
> svn. i made that compile on windows now, and removed the separate
> thread.

Windows version of Wineasio?! No, I meant the Linux version. Though if
there's a Windows version around, I'd like to know -- I'm /trying/ to keep the
SourceForge site current with all known WineAsio versions.

>
> also added jack_transport via asio timecode. (reaper eats that nicely)
> in case wine asio doesnt support that yet, i am gonna isolate that.
> so you can apply it.

Much appreciated.

>
> the version i have is using 32bit ints. i would be really happy,
> if i could use float.
> what is your experience regarding app support ?

It's not something I've looked into.

> i am also interested, if apps honor the process now flag.
>

Again, not something I've looked into.

>
>
>>>
>>>> Also, I guess I'm missing something but I couldn't see how to bring up the
>>>> netone server on Windows.
>>> define netone server.
>>> do you mean slave ?
>> My windows machine is the one with a soundcard in. I have Jackd 0.116 on
>> Ubuntu (started with "-d net") as the slave.
>
> and running jack_netsource on the windows machine doesnt work ?
> dns resolve doesnt work iirc. you need to provide an IP.

There is no "jack_netsource" in the jacknone-0.4_setup.exe file -- that's why I
was confused.

>
>
>> Thanks again,
>>
>> -- Peter
>

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Completely crazy: Linux to Windows by netjack?

2009-12-15T14:59:06Z

On Tue, Dec 15, 2009 at 06:17:28PM +0000, Peter L Jones wrote:
> torbenh wrote:
> > i guess i need to take the plunge and get wine asio to build.
> > mapping jack_transport to the asio equivalent was on my list anyways.
> > i had postponed that, because of problems with this thiscall stuff.
>
> Any problems with building wineasio... erk, that's one I maintain! :D

the windows version ?
well... i found some weirdly modified version of wineasio in the jackosx
svn. i made that compile on windows now, and removed the separate
thread.

also added jack_transport via asio timecode. (reaper eats that nicely)
in case wine asio doesnt support that yet, i am gonna isolate that.
so you can apply it.

the version i have is using 32bit ints. i would be really happy,
if i could use float.
what is your experience regarding app support ?
i am also interested, if apps honor the process now flag.

>
> >
> >
> >> Also, I guess I'm missing something but I couldn't see how to bring up the
> >> netone server on Windows.
> >
> > define netone server.
> > do you mean slave ?
>
> My windows machine is the one with a soundcard in. I have Jackd 0.116 on
> Ubuntu (started with "-d net") as the slave.

and running jack_netsource on the windows machine doesnt work ?
dns resolve doesnt work iirc. you need to provide an IP.

>
> Thanks again,
>
> -- Peter

--
torben Hohn
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Completely crazy: Linux to Windows by netjack?

2009-12-15T10:17:28Z

torbenh wrote:
> i guess i need to take the plunge and get wine asio to build.
> mapping jack_transport to the asio equivalent was on my list anyways.
> i had postponed that, because of problems with this thiscall stuff.

Any problems with building wineasio... erk, that's one I maintain! :D

>
>
>> Also, I guess I'm missing something but I couldn't see how to bring up the
>> netone server on Windows.
>
> define netone server.
> do you mean slave ?

My windows machine is the one with a soundcard in. I have Jackd 0.116 on
Ubuntu (started with "-d net") as the slave.

Thanks again,

-- Peter

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Completely crazy: Linux to Windows by netjack?

2009-12-15T03:19:01Z

On Mon, Dec 14, 2009 at 08:29:02PM +0000, Peter L Jones wrote:

> torbenh wrote:
> > On Wed, Nov 25, 2009 at 11:28:50PM +0000, Peter L Jones wrote:
> >
> > i have found the cause of the netxruns.
> > windows default socketbuffer size is only 8KB.. so its a matter of luck
> > if the kernel drains the buffer fast enough that it doesnt overflow.
> >
> > i am setting the buffers to 256k now. works okish in the VM now.
> > a celt compressed stream at -p1024 -n2 works nicely.
> > uncompressed gives a few ocasional xruns.
> >
> > but i think i can start pointing at the VM now.
> > binary build is at http://netjack.sf.net/jacknone-0.4_setup.exe
> > gonna prepare it in netone-fixes soon.
> >
> >
> Hi torben.
>
> First bit of bad news is I couldn't use JackRouter with the build you posted above.

bah. shit. i didnt test that.
i guess i need to take the plunge and get wine asio to build.
mapping jack_transport to the asio equivalent was on my list anyways.
i had postponed that, because of problems with this thiscall stuff.

> Also, I guess I'm missing something but I couldn't see how to bring up the
> netone server on Windows.

define netone server.
do you mean slave ?

--
torben Hohn
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit

Re: Completely crazy: Linux to Windows by netjack?

2009-12-14T12:29:02Z

torbenh wrote:

> On Wed, Nov 25, 2009 at 11:28:50PM +0000, Peter L Jones wrote:
>
> i have found the cause of the netxruns.
> windows default socketbuffer size is only 8KB.. so its a matter of luck
> if the kernel drains the buffer fast enough that it doesnt overflow.
>
> i am setting the buffers to 256k now. works okish in the VM now.
> a celt compressed stream at -p1024 -n2 works nicely.
> uncompressed gives a few ocasional xruns.
>
> but i think i can start pointing at the VM now.
> binary build is at http://netjack.sf.net/jacknone-0.4_setup.exe
> gonna prepare it in netone-fixes soon.
>
>

Hi torben.

First bit of bad news is I couldn't use JackRouter with the build you posted above.

Also, I guess I'm missing something but I couldn't see how to bring up the
netone server on Windows.

-- Peter

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

From forum: Jackit