Share your knowledge at the LQ Wiki. Welcome to LinuxQuestions. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features.
Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant.
They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Make sure you have alsa-lib, alsa-utils, and alsa-driver unless you compile your own kernel and use the ALSA modules included in the kernel and opsional is alsa-oss. Find More Posts by willysr. What's the output of "lsmod" Also, did you run "alsaconf" as root before?
I think you need to. Find More Posts by liquidtenmilion. Thread Tools.Please ask your friend to create a new invitation for you. Our company is one that provides a public service, wherefore we are even more obligated to maintain a good image and reputation with respect to customers, shareholders and public administrations.
As workers of ALSA, we have the duty to act with integrity and responsibly in the entire company, the duty to be the example of ethical behaviour and the duty to continue promoting the Group's Values. At ALSA Management, we are committed to combating fraud, not only to create a climate of transparency in management, but also to protect the Group's assets and avoid financial losses.
It has been designed to help us maintain our commitment to integrity in our daily work. The purpose of this Code of Ethics and Best Practices is to regulate the behaviours, actions or events that could constitute violations of both the company's internal standards and the ethical rules or codes that govern its business activity, as well as to prevent situations that could in any way damage ALSA's reputation.
This Code of Ethics does not cover all possible situations that could potentially arise. However, it does cover the principles that should always guide the behaviour of all persons working for ALSA. Accordingly, all employees are required to be conversant with the terms of this Code of Ethics and to comply with it and respect its principles while performing their duties.
The terms of this Code are subordinate to any special internal rules and, obviously, current legislation, both of which will prevail in the event of any conflict or contradiction with this Code.
This Code of Ethics is applicable to all companies, executives and employees of the ALSA Division, regardless of the geographical scope where their business activity is developed. We must also remember our responsibilities to others and to our communities, customers, shareholders, suppliers and all other partners. It is the obligation and responsibility of all Employees to know the Code of Ethics. It was updated, the new terms being approved on 21 December and coming into force on 1 January It was updated once again current document in Decembercoming into force in January The Code of Ethics Compliance Committee is created as the body in charge of promoting the dissemination of, knowledge of and compliance with the Code.
Complying with the rule of law is a principle mandate for ALSA in all countries where it is present. All workers must comply with the regulations of the legal system within which they work, in addition to the applicable internal policies of NEG and ALSA.
A violation of the law must be avoided under any circumstance. Regardless of the sanctions that could be imposed by law, any worker who is liable for a breach will be subject to disciplinary consequences as a result of violating their obligations as an employee. It is therefore expected that, when dealing with customers, public administrations, suppliers and all other partners, we will act in ALSA's interest and in accordance with the applicable laws and regulations.
ALSA promotes integrity and professionalism as guiding elements in business relations at the company. Illegal or inappropriate behaviour by just one of our workers can cause considerable harm to the company. Conflicts of interest arise when personnel become involved in activities outside the scope of their competencies at the company or when they give preference to their own personal interest.
Workers must therefore inform their hierarchical superiors about any personal interest that could exist in relation to carrying out their professional obligations. Therefore, when entering into personal contracts or orders, they must not use companies with which they may have commercial dealings as a part of their activities at ALSA if any advantage for the personal contract or order could be derived from such dealings.
A business relationship with or an equity holding in a competitor or customer of ALSA, or participation in additional activities, could give rise to a conflict that prevents workers from complying with their responsibilities at ALSA. It is important that we all, in the performance of our professional activities, recognise and avoid conflicts of interest or even the appearance of a conflict of interest. ALSA has adapted its supplier selection and contracting processes to the criteria of objectivity, impartiality and transparency.Welcome to LinuxQuestions.
You are currently viewing LQ as a guest.
By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
HTH then because it seems to be all those codes listed as well as a whole load of handy stuff, so I thought I would pass it on. Find More Posts by mykaitch.
Tags alsacodeserrorlist Thread Tools. BB code is On. Smilies are On.
All times are GMT The time now is AM. Open Source Consulting Domain Registration. Visit Jeremy's Blog. Search Blogs.Redirected from Troubleshooting. This troubleshooting is for ALSA problems. Many other software layers can be involved in Linux audio. Enter the aplay command in a terminal with -vv extra-verbose options to play a.
If aplay doesn't produce sound, then use aplay -L to list all soundcards and digital audio devices. An important first step: compile the relevant information using aadebug. AlsaTips might have useful stuff too. Make sure you have installed ALSA as modules, and not compiled into the kernel.
ALSA fails for all sorts of reasons when compiled into the kernel this may no longer be true for kernels after v2. Anything that mentions sound in the kernel config, even if it is not directly to do with ALSA, set its option to M if you can. If it is not, download and compile newer drivers for kernel v2. Check the Quick Install instructions or the other installation instructions on the main page of this Wiki for additional information.
How to check your ALSA library version is distribution dependent. Usually, you can use the package e. APT, aptitudesynapticyumup2dateYAST2 used by your distribution to check the versions of installed packages. You can also try something like. First check that the ALSA drivers are installed and have recognized your card.
If not, make sure that the appropriate driver module is loaded. To figure out which modules you need, use the lspci egrep -i audio command. This usually will list the name and type of your sound chipset.
The main ALSA website then contains a list of those chipsets and the required drivers. As a wild guess, for most recent low-cost AC97 based motherboards and laptops, try the snd-intel8x0 driver. To make sure your card is recognized and the right driver is selected you can also try the alsaconf command, and use it to configure your sound card.
Unload it and load the ALSA driver. If you have multiple sound cards, see the MultipleCards and. If the directory does not exist, or it is empty, use the ALSA snddevices script or similar to create it and the device special files in it.
Run alsamixer both as root and as a non- root ordinary user. If the latter fails, the permissions on the device special files don't allow access by ordinary users. There are several options to fix this, depending on security requirements, your distribution and how your PC is set up:. Note that ALSA sort of misnames the channels of the mixers of many cards.
Use alsamixer to play around with the settings of the most obvious sounding channels. ALSA modules and Sound cards may describe what the channels for a specific sound card.
Since the audio is recording fine for me, should I try to simply suppress its error messages? Or would there be a way of resolving them? Once you comment out these lines, those error message will be gone.
That's said, some of those messages are telling something is wrong in your configuration, though they do not cause any real problem. I do not recommend you clean up the alsa. Those messages are printed out by alsa-lib, not PyAudio or PortAudio.
All of the above is true and a good solution. I just came here to suggest a nicer way of re-using the error handler code:. Those look like normal debug messages as it figures out how to run on your system.
I don't see any reason you shouldn't suppress them. You can probably turn off detection of jack servers, bluetooth devices, surround sound etc. Don't mess with things that are working! If your default audio subsystem is Pulseaudio common for Fedora, Ubuntu, Debianit is better to properly recompile PyAudio and underlying C library Portaudio with Pulseaudio support only without Jack and other subsystems.
Learn more. PyAudio working, but spits out error messages each time Ask Question. Asked 8 years, 11 months ago. Active 1 year, 2 months ago.
Viewed 44k times. I'm using PyAudio to record input from the microphone. ALSA lib pcm. Active Oldest Votes. There is a way to suppress the message in Python, here is a sample code:! LoadLibrary 'libasound. PyAudio p. This doesn't get rid of the messages from JACK, right? Nils Werner Nils Werner 25k 5 5 gold badges 54 54 silver badges 78 78 bronze badges.
That's definitely an elegant solution. Thanks for the advice! My problem is, the script displays the text needed to record. As soon as you hit record, that text basically gets bumped out of the way by these debug messages.
If your question is how to suppress them, try redirecting the stderr to a file. Let me know if it works. That seems to make sense, but has no effect. Is it possible the messages are coming through another output stream, for example? Matthias Matthias 3, 1 1 gold badge 22 22 silver badges 39 39 bronze badges. I've given a slightly more verbose answer there: stackoverflow.Please be bold an merge the two pages! Please consider using safer ways on your programs like polling if you are going to use Pulse Audio.
Since none of the existing documentation was thorough enough for me to understand what was really going on in ALSA at times, I'm going to write up this partial document on how I got ALSA output to work in my application, and what I think is going on, describing it to my best abilities.
Hopefully, some Developer With A Clue will extend or fix this document. Comments by me in this file are italicand probably means something wasn't and still isn't quite obvious to me.
Fore-mentioned developers are welcome to enlighten me. This document describes just one of the methods for using ALSA.
Specifically, I'm going to use regular writes here, and use asynchronous notification to find out when I can write to the ALSA buffer.
Besides asynchronous notification, you can also simply poll like you would with any other file descriptor. And besides regular writes, you can also mmap the buffer and write directly to memory. This should look fairly straight-forward. We need a handle, a variable holding the return value of our calls and a device name to tell ALSA which device to open for us. The device name is a standard ALSA device identifier you've probably encountered already, such as "hw:0,0" to indicate the first device.
The value "default" we use here opens up either the first available device or whatever the default is, probably set in the system or user's asoundrc file.
Most functions in alsa-lib return a negative error code if the operation failed, like most regular system calls. Can this be OR'd? The asynchronous notification worked without this flag, in fact, it broke when I tried to set it. In code examples beyond this section, I will leave out error checking for brevity, and simply tell you how to clean up instead.
If your application is simple player or whatever, you'd probably exit at that point. To kick off the lame excuse I have for my lazyness, after we're finished with the device, we simply close it:.
Before we can actually feed something to this device handle we just created, we have to tell it what we're feeding. First, we allocate this structure, and then we fill it with information from our device's current state:.
If this all goes well, we can now set hardware parameters! Setting a subset of hardware parameters is almost mandatory:. There are two types of transfer modes:. Besides this, there are also two ways to represent the data transfered, interleaved and non-interleaved.
If the stream you're playing is mono, this won't make a difference. In all other cases, interleaved means the data is transfered in individual frames, where each frame is composed of a single sample from each channel. Non-interleaved means data is transfered in periods, where each period is composed of a chunk of samples from each channel.Good day!
I have been looking for a bitperfect, hifi and multichannel audio player for a long time. I am hoping that Volumio will be the player for me. The video and audio portions of this card are specifically passed through.
Subscribe to RSS
This configuration installs and boots up fine logs. The web interface works great. Every playback attempt shows the attached Alsa Error. I made some attempts to poke around via SSH. I then execute the reboot command. My desired mixer type is None and it is set as such. If I SSH and check, those changes are temporarily persistent. The player then populates properly, the timer begins to count and the file encoding details display.
Unfortunately there is still no audio. The volume is set at and not adjustable. The mixer is now set to hardware. The volume is is adjustable to and not muted. There is no output. This is the log file for that last status - logs. Thank you for the support! Just a thought, could you check alsamixer and verify the default on that device is not muted?
Sometimes that happens, in case you can change it with alsamixer and you reboot, it should have been be persisted. I assure you I will continue this. I hope Friday night or Saturday next weekend I will have your tests complete and some data for a response. I look forward to relaxing and truly enjoying some hifi fruits of our efforts. Thank you. I currently have the mpd. This is the configuration where it will appear to play a file with volume fixed at and no audio output.
When I logged in this was the default view. It shows two outputs, correct? I pressed right arrow, M and it changed to. I edited the mpd. HDMI output is functional this whole time. There is a large reply posted before these two recent picture posts.
It has config dumps and some more details…. These are now slightly out of order - sorry. I have no idea what the criteria for such an action is, there was nothing wrong with your posts.