Skip to content
Snippets Groups Projects
Commit 41a62205 authored by David Trattnig's avatar David Trattnig
Browse files

Debuggin device within Docker. #6

parent 894508fd
No related branches found
No related tags found
No related merge requests found
......@@ -6,7 +6,9 @@
- [Frequently Asked Questions](#frequently-asked-questions)
- [Which Audio Interface or Soundcard is compatible with Engine Core?](#which-audio-interface-or-soundcard-is-compatible-with-engine-core)
- [How can I find the audio device IDs, required for settings in engine-core.ini?](#how-can-i-find-the-audio-device-ids-required-for-settings-in-engine-coreini)
- [I have configured an audio device in my `engine-core.ini` but still hear now sound](#i-have-configured-an-audio-device-in-my-engine-coreini-but-still-hear-now-sound)
- [I have configured an audio device in my `engine-core.ini` but still hear no sound](#i-have-configured-an-audio-device-in-my-engine-coreini-but-still-hear-no-sound)
- [I have configured an audio device in my `docker.engine-core.ini` but still hear no sound](#i-have-configured-an-audio-device-in-my-dockerengine-coreini-but-still-hear-no-sound)
- [I'm getting [clock.wallclock_alsa:2] Error when starting output lineout: Failure("Error while setting open_pcm: No such file or directory")!**](#im-getting-clockwallclock_alsa2-error-when-starting-output-lineout-failureerror-while-setting-open_pcm-no-such-file-or-directory)
- [How to solve 'Error when starting output output_lineout_0: Failure("Error while setting open_pcm: Device or resource busy")!'?](#how-to-solve-error-when-starting-output-output_lineout_0-failureerror-while-setting-open_pcm-device-or-resource-busy)
- [How to avoid stutter, hangs, artifacts or in general glitchy sound?](#how-to-avoid-stutter-hangs-artifacts-or-in-general-glitchy-sound)
- [Are there any commands to directly control the playout-server for development, debugging or testing?](#are-there-any-commands-to-directly-control-the-playout-server-for-development-debugging-or-testing)
......@@ -65,11 +67,20 @@ See [alsa-project.org/wiki/FramesPeriods](https://www.alsa-project.org/wiki/Fram
**JACK**: Please check out the [JACK Documentation](https://jackaudio.org/).
## I have configured an audio device in my `engine-core.ini` but still hear now sound
## I have configured an audio device in my `engine-core.ini` but still hear no sound
To test if you device is able to output audio at all, independently from Engine Core, try executing `speaker-test`. If you are running Engine Core using Docker, run the speaker test from within your docker container. Also checkout out the `-D` argument to test specific devices.
To test if you device is able to output audio at all, independently from Engine Core, try executing `speaker-test`. Also checkout out the `-D` argument to test specific devices. If you system doesn't provided `speaker-test` you have to install or use your preferred way of testing also audio.
## I have configured an audio device in my `docker.engine-core.ini` but still hear no sound
**[clock.wallclock_alsa:2] Error when starting output lineout: Failure("Error while setting open_pcm: No such file or directory")!**
If you are running Engine Core using Docker, run the aforementioned `speaker-test` from within your docker container by perform following:
1. Start Engine Core in debug mode using `./run.sh docker:debug`
2. To login to your Docker container you can use the command `docker exec -it aura-engine-core bash`.
3. Now run `speaker-test`. It that's working, you now know that your audio device is at least available from within Docker and you'll need to further check your Liquidsoap device configuration.
4. Next you can run `liquidsoap tests/test_alsa_default.liq`. This is a basic script which tries to play the supplied MP3 using the default ALSA device.
## I'm getting [clock.wallclock_alsa:2] Error when starting output lineout: Failure("Error while setting open_pcm: No such file or directory")!**
Assure you have set the correct device ID. To do so check the aformentioned question. Check the audio interface configuration section in `engine-core.ini`. Verify if the default settings `input_device_0` and `output_device_0` are valid device IDs.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment