wine users - Nov 2009 - Jackd gives strange output while trying to test Jack

Running on:
Gentoo linux-2.6.30-gentoo-r4
gcc x86_64-pc-linux-gnu-4.3.4
wine 1.1.33
jack-audio-connection-kit 0.116.2

jackd gives the following output after testing jack in winecfg


Code:

jackd 0.116.2
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
JACK protocol mismatch (16 vs 24)
cannot complete client connection process
JACK protocol mismatch (16 vs 24)
cannot complete client connection process




Jack protocol mismatch (16 vs 24) seems to be the main problem.

I've uninstalled and recompiled jack and this still occurs. I've done a
revdep-rebuild --library=libjack.so.0 and recompiled wine.

What else can be done?

I'm having the same issue here, but with the stable version of jack
(0.109.2).
For me the error is (16 vs 22).
It's like wine is compiling using some older version of the jack library
than what is actually installed on the system.

After searching around a bit more, I discovered that the issue is with running
wine on 64 bit.
The jack lib it uses is part of the emul-linux-x86-soundlibs package.
I tried unmasking the emul-linux-x86-* packages to upgrade them to the current
version.
After I did this and ran jackd in debug mode and ran winecfg, when I hit test
jackd showed a client connecting.
However wine immediately crashed.

So it looks like jack with wine on 64bit is a no go at the moment.