The external USB midi port shows up in the qjackctl graph.

The midi dongle works fine in other Windows apps. It was also working with jack not long ago since then I have upgraded the PC and reinstalled Windows.

Windows version is 10.

qjackctl messages:

03:45:32.764 Statistics reset.

03:45:37.209 JACK is starting...

03:45:37.210 D:/msys64/ucrt64/bin/jackd.exe -S -X winmme -dportaudio

03:45:37.281 JACK was started with PID=11604.

jackdmp 1.9.22

jackdmp 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

Drivers/internals found in : D:\msys64\ucrt64\lib\jack

JACK server starting in realtime mode with priority 10

self-connect-mode is "Don't restrict self connect requests"

03:45:39.479 JACK connection change.

03:45:39.483 Server configuration saved to "D:\msys64\home\johnm/.jackdrc".

03:45:39.486 Statistics reset.

03:45:39.492 Client activated.

03:45:39.493 Patchbay deactivated.

03:45:39.519 JACK connection graph change.

\\ midi keyboard note pressed here

03:46:24.154 Shutdown notification.

03:46:24.169 Client deactivated.

03:46:24.178 JACK is being forced...

03:46:24.379 JACK was stopped

.jackdrc:

D:/msys64/ucrt64/bin/jackd.exe -S -X winmme -dportaudio

commandline:

$ qjackctl
Cannot connect to named pipe after wait = \\.\pipe\server_jack_default_0 err = 2
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to named pipe after wait = \\.\pipe\server_jack_default_0 err = 2
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

\\ midi keyboard note pressed here

CheckRes error
JackWinNamedPipeClientChannel read fail
Server is not running
Server is not running