Moderator: Forum moderators
Hello,
after I tried the Simple Alsa Audio Recorder yesterday, the sound is completely gone in tahrpup64. Apparently the asoundrc was changed yesterday. Today I deleted it and created a new one. This has only made things worse. Can someone please help me?
@MPXY Is this the program you are using? -> viewtopic.php?p=101448#p101448
I will take a look when I return from an errand. Meanwhile perhaps @fredx181 and / or @mikewalsh will know some more details on what could go wrong.
Thank you, that's really frustrating.
@MPXY :-
Well, since I'm the offending individual who put this one together(!), I suppose I ought to try and help troubleshoot your problem. Having said as much, however, all I did was to construct an easy-to-use GUI 'wrapper' around a core script that was long since developed by others that do actually know what they're doing.... 
As it comes, OOTB, Tahr64 - like many other Pups - doesn't have an .asoundrc in /root. Once you've run the Simple Alsa Audio Recorder for the first time, you get a /root/.asoundrc file 'left over' (this is a 'generic' one that shouldn't interfere with anything).
Am I right in thinking that your current /root/.asoundrc is the one as posted above?
Code: Select all
pcm.!default pcm.Capture
pcm.Capture {
type plug
slave.pcm "Loop"
}
# duplex plug device
pcm.Loop {
type plug
slave {
pcm {
type asym
playback.pcm "loopout"
capture.pcm "loopin"
}
}
}
# output device
pcm.loopout {
type dmix
ipc_key 328211
slave {
pcm "hw:Loopback,0,0"
#period_size 256
#buffer_size 8192
}
}
# input device
pcm.loopin {
type dsnoop
ipc_key 686592
slave.pcm "hw:Loopback,1,0"
}If that's the case, my guess is a simple one; you didn't shut things down in the correct order, so the "capture" .asoundrc never got reset back to the "base" .asoundrc.....and this is why you have no sound now. Because since /root/.asoundrc 'over-rides' /etc/asound.conf, your Puppy currently thinks it's trying to permanently record from the snd_aloop module....
(I'll be the first to admit; initially, the order of operation IS a wee bit 'fiddly'.....but once you've done this a few times, it becomes second nature, and you get used to the order in which things need to be done).
The 'HELP' file does explain the order:-
Fire up the utility
Click 'RECORD'. Wait for the terminal to appear
Now launch your audio source
Make sure the terminal is 'in focus', and hit 'Enter'
When recording has finished, enter Ctrl + 'c'. Now CLOSE the audio source
You can now use the other buttons on the GUI to listen to your recording, stop playback, save it, etc...
IF things are done in the correct order, the "capture" .asoundrc will be replaced by the "base" .asoundrc again. A re-written/over-written/replaced .asoundrc is perfectly normal for this app, and is to be expected; it's how the app works, after all!
(IF you get 'stuck' like this, just click the button in the bottom row marked "Reset cfg..."; this will 'reset' the .asoundrc file back to the 'base' copy. I cocked-up a couple of times myself when I was first messing around with this, so I thought a simple reset button might JUST come in handy for others, too..! 
)
Hopefully, use of the 'Reset' button can put things back to 'functional' again. A re-start of any audio source app will be necessary, of course, so that it then reads things correctly once more.
Let us know if that helps, please.
Mike. 
Puppy "stuff" ~ MORE Puppy "stuff" ~ ....and MORE!
_______________________________________________________
Hello,
many thanks for your offer of help.
I have followed your instructions but unfortunately without success. The reset button did not solve the problem either. I then booted up my laptop on which FocalFossa64 is installed. There is no asound.conf. in /etc and also no asoundrc in my home folder. I deleted these two files on my PC and then rebooted the system. That solved my problem.
Best regards
Marc
.