[ardour-users] 32 v 64 bit

[Jack O'Quin]

On 11/17/06, Mark Knecht <markknecht at gmail.com> wrote:
> On 11/17/06, Thomas Vecchione <seablaede at gmail.com> wrote:
> > > I run a 32-bit chroot inside my 64-bit main environment. I haven't
> > > tried any VSTs in it but it works perfectly with win32codecs so I
> > > suspect VST support might work that way also.
> >
> > Fairly certain it does actually, may be able to answer that more
> > certainly in a bit, my machine is rebuilding itself at the moment, 64
> > Bit for the time being, I was going to try just compiling all my audio
> > software and wine with -m32 first.  My only real problem comes with the
> > ALSA drivers, and specifically the ALSA-Jack driver I am not sure how
> > those will work, or even if it is a good idea to mix -m32 and -m64 on
> > the same machine like that.  At the time I decided to try this I had
> > just wiped it though to go back to 32 Bit from 64, so I didn't have much
> > but an evening to lose, if that doesn't work though I may do the CHRoot
> > thing instead I have decided.
> >
> >         Seablade
> >
>
> Hi Seablade,
>    I've previously run Jack inside my chroot with the onboard sound
> chip and at the same time run Jack in my 64-bit environment with my
> HDSP 9652. I take the sound chip output and wire it to an input on the
> HDSP. I can hear both audio environments fine. Note that it's a two
> sound card system then so either the cards must be sync'ed to use a
> digitial hook-up or use an analog interface as I do.
>
>    I've just never run VSTs in the 32-bit chroot. I'm sure it will
> probably work with the right VST stuff and the right version of Wine,
> but I cannot say for sure.
>
>    Note that anyone reading this and thinking about it, it is a bunch
> of work to keep this all up to date, but maybe you just build the
> 32-bit environment and leave it there never to be updated. The chroot
> isn't be effected by normal emerge updates on a Gentoo so once it's in
> place Wine doesn't get touched and it goes on working.

I made some partial changes to jackd a while back, in the general direction
of supporting both 32 and 64-bit clients from a single server.  This task
was never completed.  Full support looks possible, but complicated, and
everyone agreed at the time that it should wait until *after* JACK 1.0.
-- 
 joq