Software :: Get The Sound Peak Level In A Terminal ?
Oct 31, 2010
I'm wondering if I could get the sound peak level value at a certain time in decibels or percentage using the terminal through a command line ? Is there a feature for ALSA that could allow me to do that ? or is there a piece of software that runs in a terminal that could do that ?
I was just using the mic and watched it stop working suddenly. I was in the middle of a skype test call when the graphical mixer level died down to zero in the middle of the call. When the test call was played back, the first part sounded fine then the sound got lower until it became inaudible. Since then I can't get any sound from my mic in skype.
Also, the audio input level graphically shown in Sound Preferences shows no fluctuations in sound as it used to before. The input device is enabled. I tried using Sound Recorder to record some sound clips and that worked fine. So the mic is working but Sound Preferences and Skype seem to have the mic level really low. I'm not sure what else to think considering it was working perfectly a few minutes ago. I've tried restarting, but that didn't fix it either.
If this is documented (I'm sure it is) I can't find it.Being a really OLD UNIX user (35-tty days) I don't like GUI and leave it at RL 3. The background is wallpapered with an undesired image. can't remember where to get rid of it. I have done it B4 but I've slept since then
I want that when ever my Red Hat Linux machine use run level 5 it automatically open terminal. Is there anyway to do it? Normally I see the desktop, Right click on anywhere and click for terminal then it can see terminal.
is there a way to set level of sound parameters (those you can set by running "alsamixer") at boot?Sound on my netbook is low. I fix that by running "alsamixer" and bringing PCM level to the max. However, as soon as I restart the system, low sound is there again, and I have to run "alsamixer" again. Any definitive solution?
Ubuntu 10.4 recognized a Samson C01U usb microphone when plugged in the very first time and the mic could be selected in Sound Preferences on the Input tab.gnome-alsamixer also showed the device from the beginning with a single volume control.After many hours of work backports-modules were removed and alsa-driver-modules reinstalled.There is now, finally, at least a signal that Applications|Sound & Video|Sound Recorder can record. The recording is very faint, but its there, along with an industrial amount of noise.
alsamixer gives 2 warnings about 'no idea what to do with line-in mode and Mic-in mode'. Forum posts have alerted there can be problems if both of these are on at the same time. One or the other should be muted to avoid a conflict. Muting line-in or Mic-in has no effect on the error messages. Maybe these warnings are unrelated to the core issue and can be ignored? The machine here is a desktop with 2 soundcards and playback works without any problem. Both JACK and Ardour seem to be working fine. Just no recording capability thru the USB Mic.Can someone shed some light on the signal strength issue and what may be needed to get the mic to work.
If I set the level for headphone via Yast/Sound at 50% it is back to 100% after a reboot what gives Pulse-Audio vs. alsa ?I'm running a Dell latitude D830 and the card is 82801 H (ICH8 family) and the driver is snd-hda-intel.
I have just installed OS 11.3 onto a lenovo desktop / Thinkcentre that previously had vista installed on it. With Opensuse I am having trouble getting much sound volume. With Vista the volume was fine but with Opensuse I have PCM, Master running pretty much on full. This gives me a respectable volume but I think there should really be more left in the tank from what I have it at. Is there any way to increase the gain in Alsa? The sound device shows in KDE as HDA Intel (AD198x) using xine backend.
I'm using OpenSuse 11.4 64 bits with KDE 4.6.00 (4.6.0) "release 6". Since several days, the sound level setting via the sound icon at the right of the task bar is very slow, ie it takes several seconds (not to say one minut or more) between the action of increase / decrease the sound level and the effect on the sound level.Same behaviour when I select this sound level icon at the right of the task bar, the cursor appears one minut later.
so, i just recently installed ubuntu and i tried to go watch a videos video and i noticed my speakers weren't working. then i raised the volume from mute to "1", no sound, then to "2", again no sound. then i went to "3" and the sound came on but it was ridiculously loud. it does this with all sounds from my computer, the first 2 notches don't emit any sound but the third and above emit sound at a very high level. running a dell precision m90 notebook. never had a problem when running my windows 7 boot, only my ubuntu boot.
Can someone recommend a good app to monitor the OUTPUT of my soundcard? I don't just want to look at the VU meter of my music player - i actually want to see what the soundcard is outputting. Windows drivers for my soundcard (Audiophile 192) had this ability, but I'm not sure what software to use in Linux.
In playback application i guess "snd_pcm_lib_write1" is the function call used to write the audio data to sound card at kernel level.If that is true. how can i send the same audio data at kernel level to other system connected over LAN.
I've been able to kludge a kill script which finds the correct pid for the kdeserver (or gnome server) after my system comes up in run level 5 so I can drop back to run level 3 mode. Lots of experimentation showed me that using telinit 3 and telinit 5 would occasionally leave the video memory in a mess and I would have the black screen of death.
I set the security parameter setting to autologin for me since I am the only user of my machine, but I still have to kludge the default setting under sysconfig (the DEFAULT_WM) under Window Manager to pick a certain window manager, so it takes time to manually switch the desktop.
Right now I can leave the gui and drop back to cli, but painful experimenting showed me that killing the X server is a no no. Right now I kill the kde server, which sends the SIGTERM to the X windows manager, which then figures out that it has to shut down.
Questions: Is there a better way of doing this? Apparently openSUSE figures that we have multiple users logging into the gui desktop, so the gui is always kept running and a login window with the desktop manager option forces the user to login in. With autologin, this never happens, but no choice of desktop is possible on the fly.
Can some type of script be set up to painlessly enable this to happen? And what is the best way of bringing either the Gnome or KDE desktop manager down gracefully? I do get lots of error messages as the system attempts to recover and X shuts down. It appears that apparently the single user with autologin is left out in the cold.
I want to install a software called TinyOS which is an operating system designed for wireless sensor embedded networks in my account. The problem is it has instructions to install the software as an administrator since i'm not an admin of the department network i can not able to install. Is there any method to install this software as an user level rather than admin level.
How can I adjust the levels at which the battery is considered to be critically low?ight now it seems this is set at 5 or 10%. I want to make it 20 or 25%This is for Gnome. I am using Lucid x86
I have a server in a data centre, which is supposed to have a 100Mbit line. Peak rates at the moment on my server are in the region of 20Mb, which should be easily handled. Is there anyway I can trace how much more bandwidth is available at any one time or if things are becoming sluggish on the server?
hello everyone, im having a problem when my computer enters in the run level 4 as the default when i start slackware. The strange thing is that it not seems that is a X window problem, it looks like more like a configuration problem in some part of the kde script to initialize the log in, because if i manually start the X service it works fine, i dont know what is the source. Thank you in advance for the help.
I want to know what are the advantages and disadvantages for accessing spi(serial peripheral inerface )from kernel level and user level. like methods of doing it, speed ,memeory utilization etc
My server crashed last week and I'm trying to diagnose why. /var/log/messages contains the following error messages, which indicate that the server's memory peaked. I would like to discover what process caused the memory peak. Being that "httpd invoked oom-killer", can I conclude that httpd was the cause of the memory peak?
you can find a cutout of an output generated by "iwlist s" command for a cell. Does anybody know what Quality, Signal level and Noise level mean? What is the definition of them? I searched for it and could not find good information on it. What do these Extra:*** fields for? What does it show in the example above? How were those values computed?
I am running F10 x86_64 with Nvidia Quadro FX 3400. I installed the drivers and it worked just fine. No errors generated according to Nvidia log files. However, while in run level 5 when I try to switch to run level 3 by typing "telinit 3" or "init 3" the X server goes down and I get a blank screen. Same thing happens when I try to switch to a different tty session by <ctrl>+<alt>+F2 (or any F key for that matter). I also noticed that when I shut down my system I can't see any more the screen where services are shutting down and their status ([OK] or [failed]).
Hey Guys, I'am new here and request your help on this: After installing emacs and a few dependencies on my RHEL 5, on restarting the system, the keyboard was not able to work. I restarted several times in vein.
However, when I start in single mode, it works perfectly. I have tried looking for a solution from google, but in vein.
I have a directory that has a another directory inside it. The top directory is rather redundant since it only contains the one other one. Is there a way to delete the top level directory and have the contents simply "move up a level"?
Last week my server crashed. I'm trying to diagnose the cause.
This is the relevant error message in /var/log/messages:
Code:
I'm assuming that I can conclude, then, that apache/httpd was the cause of the memory leak?
Next, I've been tracking my memory usage. Using top, this is an average memory load level for my server:
Code:
I'd like to confirm if my understanding of this data is correct, because Plesk indicates that my memory usage is only 50% or less. (Though I have read a number of reports indicating that Plesk's measurements are frequently wrong.)
Top says: Of the 2,073,156K total memory, 1,982,572K (95.63%) is being used, 90,584K (4.37%) is free. Of that sum, 421,948K (20.35%) are being used as buffers. Additionally, of the 2,096,472K of Swap, 60K is used, and 887,700K (42.34%) is cached.
My questions: Is my memory actually being 95% used? Or is the buffered quantity (20.35%) not a use of physical/virtual memory? (i.e. is it disk usage?) Does the amount of cached Swap influence the percentage of physical/virtual memory being used?
In other words, who is correct? Plesk says I'm using 40-50% of my memory, whereas top says 85-95%.
In our company, we have one server with kernel, 2.6.18. because of our neads, we had to buy new hard disk,that slax live cd detects that as "Ibex Peak 2 port SATA IDE Controlle".Apparently this kernel does not support this device.Unfortunately according to our policy(definitely some dependency on company's softwares installed on this kernel) we can not upgrade our kernel.
I just upgraded to the 10.04 and everything works just fine as before (except for skype but that really doesn't matters as it has already been 3 years I'm using ubuntu and I managed to get it to work only once, for miracle I believe ^^). The only real issue I have is this: when I start up my laptop, after the log-in, no sound will be heared as the "speaker" volume level in alsamixer is set to 0; if I raise it from the terminal running alsamixer (as I don't know any other alternative) everything plays just fine, but the next time I boot I do have to do it all over again... So, how can I change the default startup level of the "speaker" in alsamixer?
PS: by the way I do have the very same issue with the screen luminosity but the other way round as is always starts at maximum brightness and I can't manage to get it to start at the minimum, as it did before. At least reducing the backlight if far more quick but a couple of times I forget it and the battery lasted something like half an hour