Re: [Jack-Devel] Will development on Jack for Windows be continuing ?

PrevNext  Index
DateWed, 02 May 2018 16:38:29 +0100
From Michael Z Freeman <[hidden] at michaelzfreeman dot org>
To[hidden] at notam02 dot no
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToKjetil Matheussen Re: [Jack-Devel] Will development on Jack for Windows be continuing ?
Follow-UpGraham Goode Re: [Jack-Devel] Will development on Jack for Windows be continuing ?
On Tue, May 1, 2018 2:35 pm, Kjetil Matheussen wrote:
> On Tue, May 1, 2018 at 3:27 PM, Chris Caudle <[hidden]>
> wrote:
>
>>
>>
>> If we don't care, then should we start
>> marking those ports as only partially supported so users do not have
>> expectations that cannot be met?
>>
>>
> We shouldn't create a problem that doesn't exist. If there are problems
> with the windows or osx versions of Jack, they will be fixed. I will at
> least try to fix them since Radium uses jack and I don't see any reason to
> ditch jack. The main reason there
> hasn't been a new release for a while is because there hasn't been any
> reason to create a new release. They work just fine.

Thanks for this. That's what I was wondering. It does work fine in
32bit/x86 (see below) as I've found out. Below 5ms latency and now with 16
channels after I followed advice in other replies. Thanks people.

Docs mention contacting list if 64bit support required. I installed dual
32/64 version. Fine in 32, however with 64bit Mixxx it can't see the Jack
ASIO driver and with Reaper it can see it but the driver always crashes
and Reaper gives a message (have not got it in front of me just now).

Michael

> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
>
PrevNext  Index

1525276544.26540_0.ltw:2, <b4e830c9e851d472f7d3b00232f194f0.squirrel at server105 dot webhostingbuzz dot com>