Moode Audio Player for Raspberry Pi

Aha ok if I want to run alls the raspberry with moode in the car, regardless of a network, I presumably give a fixed ip in the config so I can access with smartphone.

OK thanks

Hi,

AP mode starts automatically if the SSID for Wifi (wlan0) is blank. The IP address of the AP is 172.24.1.1 per the Setup Guide.

From Android, http: //172.24.1.1 will connect to Moode.

-Tim
 
I need help transferring FLAC folders/files to a USB hard drive under Moode Audio. I can only transfer about 1.3Gbytes at a time, or it says the hard drive is full. But it isn't. Is there some limit under Linux, or any other setting that can get large files sets transferred?

Thanks.

energyman

Hi,

How do you connect to the USB drive?
What method are u using to copy the files?

-Tim
 
Hi,

What is output of cmds below?

df -h
sudo blkid

-Tim

Thanks Tim, here is requested outputs.

pi@moode:~ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 15G 13G 1.4G 91% /
devtmpfs 459M 0 459M 0% /dev
tmpfs 464M 0 464M 0% /dev/shmtmpfs 464M 13M 451M 3% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblk0p1 60M 17M 44M 29% /boot
/dev/sdb1 299G 38G 261G 13% /media/553556037FA6279F_
tmpfs 93M 0 93M 0% /run/user/1000

pi@moode:~ $ sudo blkid
/dev/mmcblk0: PTUUID="6f92008e" PTTYPE="dos"
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="MOODE" UUID="947B-B89A" TYPE="vfat" PARTUUID="6f92008e-01"
/dev/mmcblk0p2: UUID="eda95d8a-9cdd-4224-96d0-890b4791600c" TYPE="ext4" PARTUUID="6f92008e-02"
/dev/sdb1: UUID="553556037FA6279F" TYPE="ntfs" PARTUUID="2527a2c7-01"
pi@moode:~ $

energyman
 
Thanks Tim, here is requested outputs.

pi@moode:~ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 15G 13G 1.4G 91% /
devtmpfs 459M 0 459M 0% /dev
tmpfs 464M 0 464M 0% /dev/shmtmpfs 464M 13M 451M 3% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblk0p1 60M 17M 44M 29% /boot
/dev/sdb1 299G 38G 261G 13% /media/553556037FA6279F_
tmpfs 93M 0 93M 0% /run/user/1000

pi@moode:~ $ sudo blkid
/dev/mmcblk0: PTUUID="6f92008e" PTTYPE="dos"
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="MOODE" UUID="947B-B89A" TYPE="vfat" PARTUUID="6f92008e-01"
/dev/mmcblk0p2: UUID="eda95d8a-9cdd-4224-96d0-890b4791600c" TYPE="ext4" PARTUUID="6f92008e-02"
/dev/sdb1: UUID="553556037FA6279F" TYPE="ntfs" PARTUUID="2527a2c7-01"
pi@moode:~ $

energyman

Hi,

I don't see anything suspicious in the command output other than /dev/root has 1.4G available and you indicate that you can't copy more than 1.3G.

Below is DF output from a MoOde reference system that I also use as a music NAS. A while back I copied a music collection to the attached USB disk and did not have any issues.

pi@moode:~ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 1.8G 1.4G 369M 79% /
devtmpfs 459M 0 459M 0% /dev
tmpfs 463M 0 463M 0% /dev/shm
tmpfs 463M 6.7M 457M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 463M 0 463M 0% /sys/fs/cgroup
/dev/loop0 186M 186M 0 100% /var/www
/dev/mmcblk0p1 60M 21M 39M 36% /boot
/dev/sda1 233G 190G 44G 82% /media/EXFAT-256GB
tmpfs 93M 0 93M 0% /run/user/1000


I'm not sure whats happening in your particular situation. I've used NTFS formatted disks in the past and no probs.

Maybe there is a huge hidden .Trash or .$RECYCLEBIN folder on the disk. You may also want to map a local drive directly to the Samba share and then examine what Windows reports as free space on the share.

z: --> \\moode\USB\553556037FA6279F_

Also cat /var/syslog and see if there are any errors related to "not enough space" condition.

-Tim
 
Another happy Mooder here...

But, this evening I was adding another source folder in 'configuration' and the configuration page froze.

I rebooted and now if I enter configuration and select any option my browser just endlessly waits and I can not get into any configuration page. I can 'customise' but I can not use any setting under configure...

anyone with any ideas? Could a file have become corrupt? Is there any workaround I can try to fix this?

cheers

Stuart
 
Tim:

Thanks for your suggestions. It is a mystery, which is why I was checking in with the knowledge base of the diyaudio usergroup. Thanks again.

energyman

Given that there is a (small) correlation between the spare space on root and the size at which you stop transferring, is it possible you are copying to the wrong drive?

Are the files that copied before the error on the target drive you expected?

With the x800 sata interface and ssd, your copy speed should be pretty high, yes? Is it?

I tend to 'sneakernet' big file copies by attaching the drive to the source, but haven't hit a wall at 1.3G on any machine, mac, win or Linux.

Can you tell us the exact cp command string you used?

Edit: sorry, I see you are using USB not sata.

Have you tried using the native USB adapter?

Reading further... check the log, see if any processes are crashing and killing your copy - something like smbs or out of memory errors
 
Last edited:
Copy problem

This is a long shot but it's happened to me when trying to copy files from my desktop to a new Android phone.

Copying to the Androids internal memory worked flawlessly. Copying to the SD card would fail at the same point every try. It wasn't a size limitation, it was a problem with the file names.

My music library was created and is stored on a Linux computer. Androids internal memory is fine with the Linux ext4 file system but the add on card gets formatted with a Windows file system. The Windows file system won't recognise all the odd characters that are OK on Linux. As soon as the copy hit the odd file characters the copy program would freeze. When the file names got changed to characters that Windows likes everything copied to the Android SD card perfectly.

I copy the files to a temp directory then run a utility to change the file names. Then the files get moved to the Android SD card. That prevents mucking up the file names on the desktop and makes things work nicely on the phone.

May or may not be your issue but it was an interesting problem to solve.
 
I've just purchased a rotary encoder (KY-040) and I've realised it has an integrated momentary push switch.

Tim's guidance from a previous post suggests only three pins are connected to the Pi, but is that enough to enable the push switch as well? If not, the push switch would be great to pause/play the music.

Connect a typical 3-pin rotary encoder to Raspberry Pi GPIO 23, 24 and GND then turn on the Rotary encoder in Audio config. This loads the driver.

GPIO 23, 24 and GND correspond to pins 16, 18 and 20 on the 40-pin header.

Here's what my rotary encoder looks like:

Do the CLK and DT pins need to be specifically connected to GPIO 23 or 24, or does it not matter?

An externally hosted image should be here but it was not working when we last tested it.
 
Last edited: