On Mon, Apr 30, 2018 at 03:38:33PM -0500, Chris Caudle wrote: Indeed, same as on Linux. At work I have a Windows machine running Jack with RME's USB MADI interface, that's 64 in and 64 out. There's a Windows version of qjackctl as well. Ciao, -- FA

On Tue, May 1, 2018 1:10 am, Stephane Letz wrote: It seems that the details of Windows specific and OS X specific features are not documented fully, or at least not collected together into an easily accessible location. I'm not sure how to fix the problem of matching incentives to interests and capabilities for that. Jack has been (I think) much more widely used on linux than OS X or Windows, so the user base to find people willing to contribute documentation, wiki updates, etc. is a lot smaller. How important is cultivating the Windows and Mac user base for the health of jack? Should we care? If we do care then how do we recruit some caretakers for those platforms? 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? -- Chris Caudle

On Tue, May 1, 2018 2:35 pm, Kjetil Matheussen wrote: 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

Hi, sorry, I forgot about that. I did do that with 64bit Mixxx and then Mixxx always crashed on startup until I unregistered the DLL again. Then Mixxx startup was OK. Could be a bug with Mixxx but I think the 64bit version could see and use ReaRoute 64bit. I have not yet tried registering the DLL and checking Reaper 64bit again. On Wed, May 2, 2018 5:08 pm, Graham Goode wrote: > For JACK in Windows 64-bit you have an extra manual installation step > See http://jackaudio.org/faq/jack_on_windows.html > From ...The Jack v 1.9.8/64bits/JackRouter.dll still has to be registered > “manually” with regsvr32 > Have you done that? >>> On May 2, 2018 at 5:38 PM, <Michael Z Freeman >> (mailto:michael-jack-devel@michaelzfreeman.org)> wrote: >>>>>> On Tue, May 1, 2018 2:35 pm, Kjetil Matheussen wrote: >>>> On Tue, May 1, 2018 at 3:27 PM, Chris Caudle &lt;chris(a)chriscaudle.org>>> 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 >>> Jack-Devel(a)lists.jackaudio.org >>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org >>>>>>>>>> _______________________________________________ >> Jack-Devel mailing list >> Jack-Devel(a)lists.jackaudio.org >> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org >