Re: [Jack-Devel] JACK 1.9.8 targets / MIDI Driver status?

PrevNext  Index
DateWed, 06 Jul 2011 16:16:56 +0100
From Peter L Jones <[hidden] at drealm dot info>
To[hidden] at jackaudio dot org
In-Reply-ToGraham Goode Re: [Jack-Devel] JACK 1.9.8 targets / MIDI Driver status?
Follow-UpPeter L Jones Re: [Jack-Devel] JACK 1.9.8 targets / MIDI Driver status?
Hi Graham,

On 06/07/2011 15:05, Graham Goode wrote:
> Hi Guys,
> 
> Just a quick question in regard to Jack2 in Windows - I've told
> everyone I'm in contact to start jackd from a command line before
> starting Jack Control as I've not been able to successfully select the
> audio device from within Jack Control before staring the jack server.
> 
> Has anyone been able to successfully start the Jack server from within
> Jack Control?

I was about to agree and say I've had no luck and have a separate start menu
option for the server (which I do).  I thought I'd try qJackCtl again.  And, er
um, it worked!
> 16:04:06.083 jackd.exe -R -S -P 91 -X winmme -R -dportaudio -d"ASIO::ASIO Echo FireWire" -r48000 -p256

In setup, I have "Server path" as "jackd.exe -R -S -P 91 -X winmme", Driver as
"portaudio" and Interface as "\"ASIO::ASIO Echo FireWire\"" (pardon the
quotes!), with Frames/Period "256" and Sample Rate "48000".  With a start delay
of 4 seconds, it even managed to run "jack_load netmanager" successfully.

This is with the 9th May JACK2 installer version of qJackCtl - I've not picked
up any later versions.  I thought I'd previously tested it and had still
experienced problems with it passing the portaudio device name.  Perhaps it's
because I've turned on aliases?

> 
> (and David, did that Windows tutorial ever go live on the Wiki?)
> 
> Kind regards,
> GrahamG
> 

-- Peter
PrevNext  Index

1309965450.27466_0.ltw:2,a <iv1u9e$dgo$1 at dough dot gmane dot org>