Thank you for your donation!


Sound Tweaks Now on GitHub
#1
To 'hopefully' make things easy and to have a central access point I put everything needed in github.

Note: you will need some basic knowledge of Linux ssh, copying, moving etc. nothing major.

https://github.com/dynobot/Linux-Audio-Adjustments


Have fun and leave a comment.
Reply
#2
(01-13-2019, 04:15 PM)Edward Wrote: To 'hopefully' make things easy and to have a central access point I put everything needed in github.

Note: you will need some basic knowledge of Linux ssh, copying, moving etc. nothing major.

https://github.com/dynobot/Linux-Audio-Adjustments


Have fun and leave a comment.

Was this developed and tested with Moode? It looks fairly generic, but I'll give it a go if it has worked with Moode. I'm using 4.4 with the update and newer MPD version on an RPi 3B+ and an Allo Boss.  Thanks for your your effort here.

Skip
Reply
#3
(01-13-2019, 07:51 PM)Skip Pack Wrote:
(01-13-2019, 04:15 PM)Edward Wrote: To 'hopefully' make things easy and to have a central access point I put everything needed in github.

Note: you will need some basic knowledge of Linux ssh, copying, moving etc. nothing major.

https://github.com/dynobot/Linux-Audio-Adjustments


Have fun and leave a comment.

Was this developed and tested with Moode? It looks fairly generic, but I'll give it a go if it has worked with Moode. I'm using 4.4 with the update and newer MPD version on an RPi 3B+ and an Allo Boss.  Thanks for your your effort here.

Skip

http://moodeaudio.org/forum/showthread.php?tid=749
Reply
#4
Error in the line "start the service; systemctl start some.service". They should be sound.service.
Reply
#5
Now with Automated Install and Removal...see GitHub for details.

Enjoy and don't forget to leave feedback.

Big Grin
Reply
#6
(01-18-2019, 04:06 PM)Edward Wrote: Now with Automated Install and Removal...see GitHub for details.

Enjoy and don't forget to leave feedback.

Big Grin

I'm getting the following failure on the automated install using putty to my RPi 3B+:

pi@moode:/etc/systemd/system $ curl -sSL https://github.com/dynobot/Linux-Audio-A...asic-insta       ll.sh | bash
--------------------------
| Downloading Sound File |
--------------------------
--2019-01-18 13:46:43--  https://github.com/dynobot/Linux-Audio-A...r/Sound.sh
Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112
Connecting to github.com (github.com)|192.30.253.113|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://raw.githubusercontent.com/dynobo...r/Sound.sh [following]
--2019-01-18 13:46:47--  https://raw.githubusercontent.com/dynobo...r/Sound.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.52.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.52.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 753 [text/plain]
Sound.sh: Permission denied

Cannot write to ‘Sound.sh’ (Permission denied).
mv: cannot stat 'Sound.sh': No such file or directory
chmod: changing permissions of '/usr/bin/Sound.sh': Operation not permitted
-----------------------------------
| Increasing Sound Group Priority |
-----------------------------------
mv: cannot move '/etc/security/limits.conf' to '/etc/security/limits.conf.bak': Permission denied
bash: line 31: /etc/security/limits.conf: Permission denied
bash: line 32: /etc/security/limits.conf: Permission denied
bash: line 33: /etc/security/limits.conf: Permission denied
bash: line 34: /etc/security/limits.conf: Permission denied
-----------------------------
| Improving Network Latency |
-----------------------------
mv: cannot move '/etc/sysctl.conf' to '/etc/sysctl.conf.bak': Permission denied
bash: line 50: /etc/sysctl.conf: Permission denied
bash: line 51: /etc/sysctl.conf: Permission denied
bash: line 52: /etc/sysctl.conf: Permission denied
---------------------------
| Creating System Service |
---------------------------
sed: couldn't open temporary file /etc/seduutFrU: Permission denied
--------------------
| Rebooting System |
--------------------
Failed to set wall message, ignoring: Interactive authentication required.
Failed to reboot system via logind: Interactive authentication required.
Failed to open /dev/initctl: Permission denied
Failed to talk to init daemon.
_______________________________________________________________________

It looks like a lack of 'sudo's or a similar permissions issues. Any thoughts?


thanks,   Skip
Reply
#7
(01-18-2019, 11:06 PM)Skip Pack Wrote:
(01-18-2019, 04:06 PM)Edward Wrote: Now with Automated Install and Removal...see GitHub for details.

Enjoy and don't forget to leave feedback.

Big Grin

I'm getting the following failure on the automated install using putty to my RPi 3B+:

pi@moode:/etc/systemd/system $ curl -sSL https://github.com/dynobot/Linux-Audio-A...asic-insta       ll.sh | bash
--------------------------
| Downloading Sound File |
--------------------------
--2019-01-18 13:46:43--  https://github.com/dynobot/Linux-Audio-A...r/Sound.sh
Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112
Connecting to github.com (github.com)|192.30.253.113|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://raw.githubusercontent.com/dynobo...r/Sound.sh [following]
--2019-01-18 13:46:47--  https://raw.githubusercontent.com/dynobo...r/Sound.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.52.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.52.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 753 [text/plain]
Sound.sh: Permission denied

Cannot write to ‘Sound.sh’ (Permission denied).
mv: cannot stat 'Sound.sh': No such file or directory
chmod: changing permissions of '/usr/bin/Sound.sh': Operation not permitted
-----------------------------------
| Increasing Sound Group Priority |
-----------------------------------
mv: cannot move '/etc/security/limits.conf' to '/etc/security/limits.conf.bak': Permission denied
bash: line 31: /etc/security/limits.conf: Permission denied
bash: line 32: /etc/security/limits.conf: Permission denied
bash: line 33: /etc/security/limits.conf: Permission denied
bash: line 34: /etc/security/limits.conf: Permission denied
-----------------------------
| Improving Network Latency |
-----------------------------
mv: cannot move '/etc/sysctl.conf' to '/etc/sysctl.conf.bak': Permission denied
bash: line 50: /etc/sysctl.conf: Permission denied
bash: line 51: /etc/sysctl.conf: Permission denied
bash: line 52: /etc/sysctl.conf: Permission denied
---------------------------
| Creating System Service |
---------------------------
sed: couldn't open temporary file /etc/seduutFrU: Permission denied
--------------------
| Rebooting System |
--------------------
Failed to set wall message, ignoring: Interactive authentication required.
Failed to reboot system via logind: Interactive authentication required.
Failed to open /dev/initctl: Permission denied
Failed to talk to init daemon.
_______________________________________________________________________

It looks like a lack of 'sudo's or a similar permissions issues. Any thoughts?


thanks,   Skip

Since it downloaded the file you should be able to just do this....

sudo ./basic-install.sh
Reply
#8
Smile 
Tried this (alternative install) and it worked fine.....
Immediate difference on an old Pi (1) B..... Wink  (MoOde 4.1 as less overhead...)
But clicking when changing tracks....Sad
Reply
#9
This is what i'm getting. Any Ideas?

Thanks,

-----------------------------------
| Increasing Sound Group Priority |
-----------------------------------
-----------------------------
| Improving Network Latency |
-----------------------------
---------------------------
| Creating System Service |
---------------------------
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.
--------------------
| Rebooting System |
--------------------
Reply
#10
(01-21-2019, 03:03 PM)Botte Wrote: This is what i'm getting. Any Ideas?

Thanks,

-----------------------------------
| Increasing Sound Group Priority |
-----------------------------------
-----------------------------
| Improving Network Latency |
-----------------------------
---------------------------
| Creating System Service |
---------------------------
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.
--------------------
| Rebooting System |
--------------------

It tried to add the script as a system service but the system didn't like it.
Try the optional method which includes chmod 755 etc.
Reply


Forum Jump: