Hello Greg Thanks for a rapid response.
Greg Erskine wrote: > > The asound.state should be restored after a reboot. When you did a 'sudo > alsactl store' did you also do a 'sudo filetool.sh -b'. This saves your > new asound.state into mydata.tcz that is restored after a reboot. I didn't do this. Greg Erskine wrote: > > Oh, I just remembered, on the 'Tweaks page' > 'ALSA output level' needs > to be set to custom to run a 'sudo alsactl restore' at startup. > I did set it to customer and it didn't help. Is it intended to just run the restore command? Would it be affected by not running 'sudo filetool.sh -b'. I thought a backup was done anyway. Greg Erskine wrote: > > I don't believe /usr/local/etc/init.d/alsasound is ever run, but there > are other 'generic' alsa startup files with similar issues that I think > are run. > It wouldn't suprise me. It is quite difficult for me to work out what is run, and in what order, because I am not really sure of the starting point. 1xSB, 1xSB2, 1xSB3, 2xDuet, 1xBoom, 3xRadio, 2xTouch, 2xpiCorePlayer with IQAudio DAC (RPi2) iPeng/Orange Squeeze, LMS 7.8 on Max2Play/Squeezeplug RPi2 ------------------------------------------------------------------------ rectorydp's Profile: http://forums.slimdevices.com/member.php?userid=2131 View this thread: http://forums.slimdevices.com/showthread.php?t=97803 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
