3 w amp configure file problems

Hi, I am trying to set up a RPi with the 3w amp. I installed full RasPian and then ran the install script.

Everything is as it should be - up to the instructions to edit the mopidy config file to add the file path for the music files to the [local] section.

There is no [local] section in my config file.

I found an instruction to add various lines to the config file but these various lines (the ones to be added) are in fact all that my config file is made up from, there are no other lines. It is as if the original config file has been overwritten by the new lines - rather than having them added to it.

I have tried to simply add the line to redirect but to no avail.

So, to sum up… The display is working, telling me where to look for Iris. Iris is working but pointing to the wrong place for my files.
(In fact, once up and running, I would like to point it to a usb stick for my files).

Is there a standard config file that I can ‘find’?
Perhaps I’m trying to edit the wrong config file? (/etc/mopidy/mopidy.conf)

Any help for a struggling newbie gratefully received!

not 100% sure ,but you could be trying to edit the wrong file , edit the pi boot config file command ,
sudo nano /boot/config.txt

There are two mopidy.conf files depending upon how you run it. The one given in the documentation is for when you run it as a service.

If you run it manually via console, the location is~/.config/mopidy/mopidy.conf .

The ~ in the file path automatically expands to your home directory . If your username is alice and you are running Linux, the config file will probably be at /home/alice/.config/mopidy/mopidy.conf .

This caught me out big time.

Many thanks for your reply.

Following on from my first post, this morning I have got music playing (display working too) by putting some music files into the var/lib/mopidy/m3u directory.
This makes me feel that the /etc/boot/config.txt file must be ok.

However I would like to ‘add local files’ as described on the ‘Getting started with Pirate Audio’ web page.
This would seem to involve the /etc/mopidy/mopidy.conf file which is where I come unstuck.