d10ygs.netlify.com

1. Pulseaudio Download
2. Install Pulseaudio On Windows 10
3. Pulseaudio For Linux
4. Install Pulseaudio Windows 7

1. Streaming audio from Windows to Linux using PulseAudio. Ask Question 11. I have Linux box with Ubuntu + PulseAudio network server installed. I can stream audio from my laptop (with Linux installed too) to the box over local network. Install JACK and ASIO Bridge on the Windows box.
2. Apr 19, 2017  I can't check 'pacmd' because PulseAudio insists on shutting down if it can't find anything, and 'pacmd' requires PulseAudio as a service to run, so I can't even figure out what PulseAudio is seeing on my box. It's not logging any specific errors, either. It doesn't help that I have.counts six 'sound cards' according to Windows.

Can a Windows computer access Pulse sound server on an Ubuntu computer? Using Pulse Audio Preferences. I have some Windows computers as well. I was wondering if.

This question is inspired by Can you run GUI apps in a docker container?.

The basic idea is to run apps with audio and ui (vlc, firefox, skype, ..)

I was searching for docker containers using pulseaudio but all containers I found where using pulseaudio streaming over tcp.(security sandboxing of the applications) Direct folders 3.5 serial.

In my case I would prefere playing audio from an app inside the container directly to my host pulseaudio. (without ssh tunneling and bloated docker images)

Pulseaudio because my qt app is using it ;)

A. BinzxxxxxxA. Binzxxxxxx

4 Answers

it took me some time until i found out what is needed. (Ubuntu)

we start with the docker run command docker run -ti --rm myContainer sh -c 'echo run something'

ALSA:
we need /dev/snd and some hardware access as it looks like.when we put this together we have

In new docker versions without lxc flags you shoud use this:

PULSEAUDIO:
Here we need basically /dev/shm, /etc/machine-id and /run/user/$uid/pulse. But that is not all (maybe because of Ubuntu and how they did it in the past). The envirorment variable XDG_RUNTIME_DIR has to be the same in the host system and in your docker container. You may also need /var/lib/dbus because some apps are accessing the machine id from here (may only containing a symbolic link to the 'real' machine id). And at least you may need the hidden home folder ~/.pulse for some temp data (i am not sure about this).

In new docker versions you might need to add --privileged.
Of course you can combine both together and use it together with xServer ui forwarding like here: https://stackoverflow.com/a/28971413/2835523

Just to mention:

• you can handle most of this (all without the used id) in the dockerfile
• using uid=$(id -u) to get the user id and gid with id -g
• creating a docker user with this id

create user script:

Pulseaudio Download

A. BinzxxxxxxA. Binzxxxxxx

Inspired by the links you've posted, I was able to create the following solution. It is as lightweight as I could get it. However, I'm not sure if it is (1) secure, and (2) entirely fits your use-case (as it still uses the network).

1. Install paprefson your host system, e.g. using sudo apt-get install paprefs on an Ubuntu machine.
2. Launch PulseAudio Preferences, go to the 'Network Server' tab, and check the 'Enable network access to local sound devices' checkbox [1]
3. Restart your computer. (Only restarting Pulseaudio didn't work for me on Ubuntu 14.10)
4. Install Pulseaudio in your container, e.g. sudo apt-get install -y pulseaudio
5. In your container, run export 'PULSE_SERVER=tcp:<host IP address>:<host Pulseaudio port>'. For example, export 'PULSE_SERVER=tcp:172.16.86.13:4713' [2]. You can find out your IP address using ifconfig and the Pulseaudio port using pax11publish [1].
6. That's it. Step 5 should probably be automated if the IP address and Pulseaudio port are subject to change. Additionally, I'm not sure if Docker permanently stores environment variables like PULSE_SERVER: If it doesn't then you have to initialize it after each container start.

Install Pulseaudio On Windows 10

Suggestions to make my approach even better would be greatly appreciated, since I'm currently working on a similar problem as the OP.

References:
[1] https://github.com/jlund/docker-chrome-pulseaudio
[2] https://github.com/jlund/docker-chrome-pulseaudio/blob/master/Dockerfile

UPDATE (and probably the better solution):
This also works using a Unix socket instead of a TCP socket:

1. Start the container with -v /run/user/$UID/pulse/native:/path/to/pulseaudio/socket
2. In the container, run export 'PULSE_SERVER=unix:/path/to/pulseaudio/socket'

The /path/to/pulseaudio/socket can be anything, for testing purposes I used /home/user/pulse.
Maybe it will even work with the same path as on the host (taking care of the $UID part) as the default socket, this way the ultimate solution would be -v /run/user/$UID/pulse/native:/run/user/<UID in container>/pulse; I haven't tested this however.

ctitzectitze

After trying most of the solutions described here I found only PulseAudio over network to be really working. However you can make it safe by keeping the authentication.

1. Install paprefs (on host machine):

2. Launch paprefs (PulseAudio Preferences) > Network Server > [X] Enable network access to local sound devices.

3. Restart PulseAudio:

4. Check it worked or restart machine:

   New Excel formulas are also available - for calculating molecular descriptors, molecular weight or molecular formula and for determining whether one Smiles string is a substructure of, or is similar to, another Smiles string (within a defined threshold). Molecular descriptors for cheminformatics pdf to excel.

Now use that socket:

Check that the user running inside the container has access to the cookie file ~/.config/pulse/cookie.

To test it works:

For more info may check Docker Mopidy project.

WernightWernight

Assuming pulseaudio is installed on host and in image, one can provide pulseaudio sound over tcp with only a few steps. pulseaudio does not need to be restarted, and no configuration has to be done on host or in image either. This way it is included in x11docker, without the need of VNC or SSH:

First, find a free tcp port:

Get ip adress of docker daemon. I always find it being 172.17.42.1/16

Pulseaudio For Linux

Load pulseaudio tcp module, authenticate connection to docker ip:

On docker run, create environment variable PULSE_SERVER

Afterwards, unload tcp module. (Note: for unknown reasons, unloading this module can stop pulseaudio daemon on host):

Edit: How-To for ALSA and Pulseaudio in container

mviereckmviereck

Not the answer you're looking for? Browse other questions tagged qtaudiodockeralsapulseaudio or ask your own question.

Using this script to install PulseAudio on Windows, this happens on startup:

I don't think this is your fault.

I'm using a combo PCI VGA card/Sound card with an HDMI output. I can't really change this configuration physically, it's just what it is. Looking on Google, I'm in the same RMS Titanic as these unfortunate folks.

I can't check 'pacmd' because PulseAudio insists on shutting down if it can't find anything, and 'pacmd' requires PulseAudio as a service to run, so I can't even figure out what PulseAudio is seeing on my box. It's not logging any specific errors, either.

It doesn't help that I have..countssix 'sound cards' according to Windows. All of them serve different functions and cannot be readily disabled.

If it helps, the IRQ is 16 and the Port address ranges are as follows:

Install Pulseaudio Windows 7

All of these are set up by the BIOS and I'm hesitant to change them.

For completeness, here are the errors on the 'other side':

It doesn't help that a lot of older software products I have don't understand this configuration very well either. I ran into a similar issue using a Piggyback videocard configuration - the sound card kept switching contexts from application to application - a total mess.