Thank you for your donation!


Sound Tweaks Now on GitHub
#11
(01-21-2019, 08:38 PM)Edward Wrote:
(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.

Looks like the same thing.

?


pi@moode:~ $ chmod 755 basic-install.sh
pi@moode:~ $ sudo ./basic-install.sh
--------------------------
| Downloading Sound File |
--------------------------
--2019-01-22 17:35:46--  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-22 17:35:47--  https://raw.githubusercontent.com/dynobo...r/Sound.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.184.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.184.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 753 [text/plain]
Saving to: ‘/usr/bin/Sound.sh’

/usr/bin/Sound.sh   100%[===================>]     753  --.-KB/s    in 0s

2019-01-22 17:35:47 (6.29 MB/s) - ‘/usr/bin/Sound.sh’ saved [753/753]

-----------------------------------
| 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 |
--------------------


Let me know,

Thanks,
Reply
#12
You need to delete that old basic-install.sh file, it still has the command in it that's causing problems.i removed it in the new file.
Reply
#13
(01-23-2019, 08:31 PM)Edward Wrote: You need to delete that old basic-install.sh file, it still has the command in it that's causing problems.i removed it in the new file.

Thanks, that seems to have worked.
Reply
#14
Great, now are you willing to spend a minute or so and give your opinion?
Reply
#15
(01-23-2019, 09:45 PM)Edward Wrote: Great, now are you willing to spend a minute or so and give your opinion?

Thanks again for your help,

Yes this makes a significant change, the sound stage gets bigger with more separation.

It’s a bigger change than slowing down the pi clock, in my system.

I will work on a better write up comparing the differences once I have a chance to give it a better listen.
Reply
#16
Hi Edward,

how can I remove old basic-install.sh . I need the command .

regards

Wikko 13 Sad
Reply
#17
(01-20-2019, 04:14 AM)DRONE7 Wrote: 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

(02-02-2019, 08:30 PM)wikko13 Wrote: Hi Edward,

how can I remove old basic-install.sh . I need the command .

regards

Wikko 13 Sad

To remove the file itself 

sudo rm basic-install.sh

Otherwise the remove.sh script will remove the parameters from your system.

I was just thinking of making a self destructing file for these....ie once they are used the main file deletes itself or something of that effect
Reply
#18
(02-03-2019, 02:40 AM)Edward Wrote:
(01-20-2019, 04:14 AM)DRONE7 Wrote: 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

(02-02-2019, 08:30 PM)wikko13 Wrote: Hi Edward,

how can I remove old basic-install.sh . I need the command .

regards

Wikko 13 Sad

To remove the file itself 

sudo rm basic-install.sh

Otherwise the remove.sh script will remove the parameters from your system.

I was just thinking of making a self destructing file for these....ie once they are used the main file deletes itself or something of that effect

many thanks

my moodeaudio system still works..  Smile
Reply
#19
(02-03-2019, 03:19 AM)wikko13 Wrote:
(02-03-2019, 02:40 AM)Edward Wrote:
(01-20-2019, 04:14 AM)DRONE7 Wrote: 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

(02-02-2019, 08:30 PM)wikko13 Wrote: Hi Edward,

how can I remove old basic-install.sh . I need the command .

regards

Wikko 13 Sad

To remove the file itself 

sudo rm basic-install.sh

Otherwise the remove.sh script will remove the parameters from your system.

I was just thinking of making a self destructing file for these....ie once they are used the main file deletes itself or something of that effect

many thanks

my moodeaudio system still works..  Smile

Can you describe the problem you were having? Did this cause any problem with your moodeaudio system working?
Reply
#20
(02-03-2019, 04:20 AM)Edward Wrote:
(02-03-2019, 03:19 AM)wikko13 Wrote:
(02-03-2019, 02:40 AM)Edward Wrote:
(01-20-2019, 04:14 AM)DRONE7 Wrote: 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

(02-02-2019, 08:30 PM)wikko13 Wrote: Hi Edward,

how can I remove old basic-install.sh . I need the command .

regards

Wikko 13 Sad

To remove the file itself 

sudo rm basic-install.sh

Otherwise the remove.sh script will remove the parameters from your system.

I was just thinking of making a self destructing file for these....ie once they are used the main file deletes itself or something of that effect

many thanks

my moodeaudio system still works..  Smile

Can you describe the problem you were having? Did this cause any problem with your moodeaudio system working?

Hi Edward, 

My moodeaudio.org is ok   Smile
I wanted only try to tune the Sound 

Regards
Reply


Forum Jump: