Re: [Jack-Devel] Using Jack to route ASIO audio over Remote Terminal session

There must have been some weirdness with the first run of these apps. I closed everything down and when I tried the documented instructions again (opening Jack Port Audio first, and then declaring Jack Router inside my ASIO app) the cmd window stays open and I can make the connection. Furthermore, now the Patchbay displays my ASIO app and I can make the connection from it to "system/playback 1 and 2".
 
However, still no audio...
 
Am I getting close? ;)

 

Ben Eggehorn/Recording Services

P.O. Box 181

Monrovia, CA 91017-0181

 

626-260-4219

 

http://beneggehorn.com

 
> Date: Fri, 30 Aug 2013 22:07:27 +0200
> Subject: Re: [Jack-Devel] Using Jack to route ASIO audio over Remote Terminal session
> From: [hidden]
> To: [hidden]
> CC: [hidden]
> 
> Hi Ben,
> 
> See http://jackaudio.org/jack_on_windows
> 
> Looks like you are missing the final '-d' option and the quotes around
> the ASIO driver string
> 
> %SystemRoot%\system32\cmd.exe /k "C:\Program Files
> (x86)\Jack\jackd.exe" -R -S -d portaudio -d "ASIO::ASIO4ALL v2"
> 
> See if that helps...
> 
> Kind regards,
> GrahamG
> 
> 
> 
> On 8/30/13, Ben Eggehorn <[hidden]> wrote:
> > Hi,
> >
> > I'm looking into finding a solution that will allow me to route audio from
> > an ASIO audio application (ASIO4ALL) through an internet based Windows
> > Remote Desktop connection.
> >
> > My audio host is Avid ProTools running ASIO4ALL as the playback engine. I
> > had limited success using Virtual Audio Cable in that it worked fine over
> > LAN but did not pass audio over a Remote Terminal session (known limitation
> > of the software).
> >
> > I've just discovered Jack and am trying to wrap my head around the
> > configuration. Here is my current installation and setup:
> >
> > Windows 7x64
> > ASIO4ALL 2.10 installed
> > Jack 1.9.9 installed and 64bit .dll has been registered successfully
> >
> > After running Jack Port Audio, I get the message in the command window that
> > "Jack Server started in realtime mode with priority 10" however the command
> > window does not stay open as detailed in the Using Jack on Windows FAQ. It
> > appears as though something is failing at this stage? I used the following
> > command  to keep the cmd window open so I could try to find more info about
> > the possible error:
> >
> > %SystemRoot%\system32\cmd.exe /k "C:\Program Files (x86)\Jack\jackd.exe" -R
> > -S -d portaudio ASIO::ASIO4ALL v2
> >
> > (the /k switch simply forces the cmd window to stay open after executing the
> > command)
> >
> > After running this command, the window displays this information:
> >
> >
> >
> >
> > At this point I can't figure out how to get past this issue.
> >
> > Even though the command windows closes I do see JackRouter listed in *one*
> > of my ASIO apps audio setup pages. I have several ASIO based audio apps on
> > my system but so far the only one that shows the Jack Router is GForce MTron
> > Pro (my desired application, ProTools, does not show the Jack Router as an
> > option). Regardless, trying to select Jack Router as the playback device
> > fails with the message:
> >
> > "Couldn't load the ASIO Driver because the device is not connected"
> >
> > I'd appreciate any help you can offer me into getting this properly
> > configured. Thanks so much!
> >
> > Regards,
> >
> > Ben
> >
> >
> >
> > Ben Eggehorn/Recording Services
> >
> > P.O. Box 181
> >
> > Monrovia, CA 91017-0181
> >
> >
> >
> > 626-260-4219
> >
> >
> >
> > http://beneggehorn.com
> >
> >
> >
> >
 		 	   		   		 	   		  

1377898187.14250_0.ltw:2, <COL126-W758167CE00A5C78E2D4CCB6350 at phx dot gbl>