Re: [orca-list] Monitoring my line-in? Can it be done?

["B. Henry" <burt1iband gmail com>]

I always recommend making a copy of your whole ~/.config/pulse directory and your asound.state file before 
making any significant or experimental 
changes, always good to have a copy of your optimised sound configuration anyway in case of corruption which 
I've seen happen repeatedly on some 
hardware, most notably a sony netbook. 
I'd do something like 
open a terminal with control alt t in most distros/desktops, or logging in to a tty console by pressing 
control alt plus some function key, f1-6 in 
Ubuntu and friends, f2 to 7 last time I used F123 and or manjaro, maybe fedora as well, and writing your 
username, press enter and then your pw and 
enter.
Then run 
mkdir Backups
cp -rf .config/pulse Backups/
now you can get known to be working sound settings back by copying that pulse directory back in to place and 
restarting pulseaudio or rebooting.
Best to get rid of any and all pulse config files  like Peter writes, just in case something extra has been 
added and thus won't be overwritten when you 
restore your backup.
 rm -rf .config/pulse
cp -rf Backups/pulse .config/ 
Depending on your configuration on some hardware you can enable loopback with alsamixer even if you are using 
pulse.
Put speakup in cursoring off mode to read alsamixer, and to cut through confusion , at least in the beginning 
use review keys  to read levels and what 
is what while you count how many sliders you have moved with the left and right arrow keys.
On the machine where I can enable loopback mixing via alsamixer I think it was the laaast control to the 
right in the default alsamixer view, i.e. how 
it opens. 
Some machines can do almost notahing with alsamixer if they are using pulse.
Oh, also to backup the asound.state file I mentioned above you can use cp like we did with the pulse config 
folder above, e.g.,
cp /var/lib/alsa/asound.state ~/.Backups
If you have not already learned the tilda, "~" character is Xnix shorthand for the active user's home 
directory. I did not use it in the first commands 
as we had just opened a terminal emulator window, or a VT-console which has you in your home folder by 
default.
I see that Peter wroote more than I noticed on first read, i.e. removing the pulse directory is always an 
alternative  if you do not have backups,but 
some machines may require quite a bit of fine tuning to sound their best so having a known to be good backup 
can save quite a bit of time comopared to 
starting over from pulse defaults. Other systems are just fine out of the box running default configurations 
and other than raisinig or lowering master 
volume need little or no adjustment.  

Got to run, but that should give you the basics along with the other posts in this conversation. Remember 
that google is your friend. Most questions I 
need ato answer if not very specific to accessiblity get answered somewhere or in multriple places on the 
first page of google search results. I do set 
things up to get 30 results per page usually, so if you only get ten you might need the 2nd page from time to 
time, but between sites found on 
cybercity.biz, howtogeek etc, the Ubuntu and Arch wikis, and some of the forums like stackoverflow, askubuntu 
and stackexchange there's a ton of help 
around for beginners to experts. 
In the beginning more man pages are confusing compared with those that are easy to understand and helpful, 
but many are so well written that l a lot of 
people will be able to easily follow even in their first Linux sessions. It is a good idea to at least take a 
quick look at the manpage for any software 
you are using for the first time and/or not knowledgable about. More and more of them will start to make 
sense, but like anything else one must start 
out crawling, then try to walk, and eventually run. 
A big help when looking for all kinds of info, but especially answers to computer related questions is 
surfraw. 
Google it, install it, and give it a try. I mosgtly use textbased browsers for those computer questions. I 
Prefer elinks, but lynx is faster to get 
configured for best accessiblity as it comes with a configuration file you can just copy in to place. 
I  can send you an optimised elinks configuration file if you want to go that route, and although it's 
usually less efficient for the kind of searches 
I'm talking aobut you can certainly use firefox or any browser you like with sr. 
Oh, make aliases to call surfraw wit less typing, e.g. 
alias srg='sr google'
If you have a ~/.bash_aliases file then put this somewhere in there, and if you don't have such a beast hyet 
you can put some aliases in ~/.bashrc. 
Note the leading period "."  i.e. yo will not see these files in your filemanagers unless you enable the 
display of "hiddewn" files in your view menu or 
prefferences or both depending on filemanager and version. 
With that alias I just type something like 
srg What is new in firefox56?
If you use much oof any punctuation other than . ? and ,  you want to put yhour question in quotes.

-- 
B.H.
Registerd Linux User 521886


Peter Vágner wrote:
Sat, Oct 21, 2017 at 10:03:28PM +0200

Hello,

Yes it's doable.

First you do need to load module-loopback into your pulseaudio. I've found
some other ubuntu fellow doing that years ago, so here is his article:
[1]https://thelinuxexperiment.com/pulseaudio-monitoring-your-line-in-interface/

Once your loopback module is loaded you can just go to Settings -> Sound,
or you can open Sound settings from the system menu on the top bar, or you
can use search to find Sound.
Once the sound settings are showing use the tab key to navigate. Once you
land on the output tab, switch to the input tab by pressing right arrow
key. Now tab into a table with the input device selection, choose the
corresponding line in input in there, tab more to the slider where you can
set its volume. Tab more to the toggle button to unmute, shift+tab back to
the volume slider so you can now fine tune the volume.

There is a commandline app called pacmd as a part of the pulseaudio which
can be used from the terminal in case you are not looking for a graphical
way on how to manipulate default source output selection and setting its
volume. With that you can also create a script you might be able to assign
to a simple keyboard shortcut. So if it works fine for you and you need
more try reading pacmd --help or ask for more hints.

Please note as you are switching device selection in one of the tables
either on the Output tab or on the Input tab, Pulseaudio changes the
active device on the fly, setting it as the default also routing all
active streams to the new device being selected. So depending on your
audio setup you may get no sound when changing default device or its
profile on the Output tab. If you are afraid, please do ask sighted help
to assist. Or keep sshd running so you can troubleshoot from another
machine if you inadvertently disable your sound.
Alternatively you might be able to reset your sound configuration by:
killing pulseaudio - running pulseaudio -k in the terminal
removing pulseaudio configuration - running rm -Rf ~/.config/pulse in the
terminal
and starting the pulseaudio -- pulseaudio --start

Greetings

Peter
2017-10-21 19:31 GMT+02:00 Christopher-Mark Gilland
<[2]clgilland07 gmail com>:

OK, so here's the abridged short version of the story.
 
Due to very convoluted reasons which, don't worry, I won't bore you
with, I have to use my line in jack on my desktop machine for monitoring
a certain source which I always have patched to my PC.
 
This is not a matter of guesswork. It's not even a recording audio
thing. I'm basically running a device through line in to provide a
source to hear it through my speakers. We'll just leave it at that.
 
Anyway, In Windows, I obviously can unute the playback on my line in,
and therefore monitor anything coming into that jack.
 
Without physically recording, is there a way that I can monitor my line
in jack on Ubuntu 16.04 much the same way? The main reason I'm really
hesitant to blow Windows off this machine entirely is because I cannot
afford to lose my line in monitoring. If! provided this is possible,
then, I seriously may consider installing on this box. I just need to
make double dog sure!
 
Chris.
_______________________________________________
orca-list mailing list
[3]orca-list gnome org
[4]https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: [5]https://wiki.gnome.org/Projects/Orca
Orca documentation: [6]https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
[7]https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at [8]http://bugzilla.gnome.org

References

Visible links
1. https://thelinuxexperiment.com/pulseaudio-monitoring-your-line-in-interface/
2. mailto:clgilland07 gmail com
3. mailto:orca-list gnome org
4. https://mail.gnome.org/mailman/listinfo/orca-list
5. https://wiki.gnome.org/Projects/Orca
6. https://help.gnome.org/users/orca/stable/
7. https://help.gnome.org/users/gnome-help/stable/a11y.html
8. http://bugzilla.gnome.org/

_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org

End of quoted content


End of quoted content