Re: [Fwd: Re: netJack2: Master doesn't show up as readable/writable client on slave side]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey Chris,

thanks again for the explanation!
Yep, I think I had a pretty big misunderstanding on how Jack worked...
Right now the Pis HDMI is connected to a small screen with integrated speakers, later on this will be replaced by my stereo receiver.
I've selected the proper device and confirmed its working locally on the Pi.
I assumed on Windows when I select the proper device Jack would just take its stream as an input, but thats obviously wrong (I feel pretty stupid now for assuming that :D, but then again I was jsut focussed to much on the goal of getting all audio output from the Laptop to the Pi, basically making the Pi the Laptops default audio device)
The thing is, on Windows I can't figure out how to tell any application to route its audio through Jack. For example in Audacity on the Pi I can select JACK instead of ALSA and all the Jack connections show up. On Windows I can only select MME, Windows Direct Sound and WASAPI (also tried installing ASIO, but that doesn't show up either.) And for Virtual Audio Cable (the thing I would need to get the audio from to make the Pi essentially my default audio device, since for most simple applications (browser, games etc) you can't even select the device, they just use the standart device (to which I can set the Virtual cable)) I don't even see a setting where I could put Jack.

Best,
Jonas
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
https://lists.linuxaudio.org/listinfo/linux-audio-user

[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux