2 Feb
2008
2 Feb
'08
2:29 p.m.
On Sa, 02.02.08 19:13 Stéphane Letz <letz(a)grame.fr> wrote:
The author himself could explain it better I guess, but ar far as I
understand it:
- the wine asio driver part is compiled 32bit (-m32)
- the bridge is compiled 64bit
The jackbridge accepts connections from wineasio, and they connect
using semaphores.
So you start jackd as usual, then the jackbridge, then your application.
The author said it is a "hack" as the error why 64bit jackd doesn't
accept 32bit is a bug in jack itself.
With dssi-vst it is somewhat similar, split 32/64bit parts.
Le 2 févr. 08 à 12:23, Thomas Kuther a écrit :
Hmm. Ok.
On Sa, 02.02.08 08:02 Stéphane Letz
<letz(a)grame.fr> wrote:
The JACK config in winecfg has nothing to do with wineasio and is
not ASIO capable. The source for wineasio is here:
http://people.jacklab.net/drumfix/ (wineasio for 32bit, wineasio-x
for 64bit). See the README on how to configure the number of
in/outs.
But for
the first time, and as i have hoped for some time, jack
midi driver appears in wine audio config. Now if you tallented
fellows could configure Jack to present a user definable number
of midi ports in and out of wine (each port with 16 channels), it
would be most appreciated. If that's not possible then i'll take
32 midi ports in, and 32 midi ports out as a default.(Please! :) )
Thanks Stephane, this works fine so far.
As a new linux user, i'm not sure how much technical information i
can give you, so if you want to know about something in
particular, let me know, and i'll try and test it.
Regards,
I guess the number of jack ports is defined in the jack wine ASIO
bridge. Where is the source code of this component?
Thanks
Stephane Btw: does a 64bit compiled jackdmp accept 32bit
clients?
I don't think so. There is nothing in place for that.. I'll have
to check this out... :)
But I see that this "jackbridge" stuff seems to be there for 64/32
bits "connections". How concretely is it used?
Thanks
Stephane