Moode Audio Player for Raspberry Pi

[Man in a van]

Back-up with Windows

Here is a link for simple instructions using windows

How To: Backup & Restore your Raspberry Pi | Raspberry Pi HQ

and the same principle works with this software (also to a zip image)

alex's coding playground >> USB Image Tool

They do however back up the full size of the card, eg. 4gb or 8gb and the fresh burn will likely need a new card of the next size.

Rasberry pi stretch full has a backup feature but I not sure if that gives a smaller image (I think not).

Here is a link for reduce the image size for people hwho want to have a go

Shrinking Raspberry Pi SD Card Images - Andrew Oakley

and I have seen a link to someone who has written a script that can be used on a linux computer that does reduce the blocksize and gives a smaller image.

I mean to try it one day but can't remember where I saved the link

 

[TimCurtis]

Hi Tim
Just done as your instructions and in alsamixer everything is set to 100% already.

Nick

Hi Nick,

In alsamixer, what is displayed for dB gain in upper left when slider is at 100?

-Tim

 

[perryni]

Hi Nick,

In alsamixer, what is displayed for dB gain in upper left when slider is at 100?

-Tim

Hi Tim

I have 0.00 dB gain

Nick

 

[TimCurtis]

Hi Nick,

Ok, that result suggests ALSA config is ok.

What is your audio chain again?

-Tim

 

[perryni]

Hi Nick,

Ok, that result suggests ALSA config is ok.

What is your audio chain again?

-Tim

NAS —> homeplugs —> RPI3 + Piano 2.1 —> Ruark r4

 

[perryni]

Hi Tim
I have a feeling it might be due to the loudness on some of my flacs. Some music is fine whereas some gets a bit crackly. Surely that’s a flac issue rather than a moode/RPI issue?

I will do further testing on different systems.

Many thanks for your help (and excellent software)

 

[DRONE7]

I have a feeling it might be due to the loudness on some of my flacs. Some music is fine whereas some gets a bit crackly. Surely that’s a flac issue rather than a moode/RPI issue?

Try connecting the NAS direct to your Pi and playing the problem tracks....I gave up on homeplug type devices due to a similar issue.

Their throughput is generally much less than advertised and mine caused interference with other devices on the mains and were impacted themselves by other appliances... especially towards the end before one expired in a puff of foul smoke.

 

[NoCompulsoryRegistr]

I also had a prpblem with FLAC files playing from my NAS (freenas). I got stuttering every few seconds and also glitches in the sound. Everything worked perfectly fine with MP3s. But FLACs worked in moode 3.2 (I guess),too. And I did not changed options in my NAS or the like. So in the end after fumbling around for hours, I noticed the mount options in moode changed. Default in moode 4:

 rsize=1048576

Default in moode 3.2:

 rsize=61440

wsize is 65536 for both versions. As soon as I changed the rsize option and remounted the source, the stutter and glitches were gone. Thought I share this with you.

 

[TimCurtis]

NAS —> homeplugs —> RPI3 + Piano 2.1 —> Ruark r4

Try connecting the NAS direct to your Pi and playing the problem tracks....I gave up on homeplug type devices due to a similar issue.

Their throughput is generally much less than advertised and mine caused interference with other devices on the mains and were impacted themselves by other appliances... especially towards the end before one expired in a puff of foul smoke.

Hi Tim
I have a feeling it might be due to the loudness on some of my flacs. Some music is fine whereas some gets a bit crackly. Surely that’s a flac issue rather than a moode/RPI issue?

I will do further testing on different systems.

Many thanks for your help (and excellent software)

I also had a prpblem with FLAC files playing from my NAS (freenas). I got stuttering every few seconds and also glitches in the sound. Everything worked perfectly fine with MP3s. But FLACs worked in moode 3.2 (I guess),too. And I did not changed options in my NAS or the like. So in the end after fumbling around for hours, I noticed the mount options in moode changed. Default in moode 4:

 rsize=1048576

Default in moode 3.2:

 rsize=61440

wsize is 65536 for both versions. As soon as I changed the rsize option and remounted the source, the stutter and glitches were gone. Thought I share this with you.

Hi,

Interesting.

1048576 is the default Stretch rsize reported for a mount w/o any rsize options specified. 61440 was default for Jessie.

Mount is supposed to "negotiate" an optimum rsize but perhaps its not able to in certain scenarios.

@perryni, can you test 61440? If it eliminates the glitches I'll figure something out for Beta9. Powerline networking though is very suspect :-0

-Tim

 

[Mars67]

@Mars67

A server status code 404 means the server site is up but can't locate the file requested.

Did you run apt-get update as the error message suggests? That has usually fixed the problem when I've encountered it. Package information changes from time to time.

Regards,
Kent

Hi Kent

Thanks for the input. Earlier in the build process one does an update/upgrade so I was wondering what could cause this but then I realised that the process took quite long when I did it. So I ran and update/upgrade again and that fixed the issue.

 

[Mars67]

Right. The big advantage of dd is that the the block count can be specified which results in only the partition data being copied and not the entire SD Card.

But dd is DANGEROUS. U can wipe your host computers OS partition if you mistakenly specify the wrong of=<> param :-0

-Tim

The latest version of Win32diskImager now has a setting where you can select to read only allocated partitions. It is a free download from Sourceforge.

 

[philrandal]

I also had a prpblem with FLAC files playing from my NAS (freenas). I got stuttering every few seconds and also glitches in the sound. Everything worked perfectly fine with MP3s. But FLACs worked in moode 3.2 (I guess),too. And I did not changed options in my NAS or the like. So in the end after fumbling around for hours, I noticed the mount options in moode changed. Default in moode 4:

 rsize=1048576

Default in moode 3.2:

 rsize=61440

wsize is 65536 for both versions. As soon as I changed the rsize option and remounted the source, the stutter and glitches were gone. Thought I share this with you.

You may be onto something here. I'm pretty sure I played with rsize when trying to debug my FLAC over NAS problems without much success. I'll resurrect my old Moode 4 beta tomorrow and check it out.

Phil

 

[Morias]

I'm busy building another image but am constantly getting the following error where some of the packages cannot be found. Some of the packages do install however.

"E: Failed to fetch 404 Not Found 404 Not Found [IP: 93.93.128.193 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?"

Can anyone explain why this would be happening? I get the impression that some of the mirror sites may be down but am guessing here.

How does one resolve this?

Thanks

I got the same. I changed my sources file to a local repository to do the install. Worked fine (and faster) after that.

 

[TheOldPresbyope]

Hi,

Interesting.

1048576 is the default Stretch rsize reported for a mount w/o any rsize options specified. 61440 was default for Jessie.

Mount is supposed to "negotiate" an optimum rsize but perhaps its not able to in certain scenarios.

@perryni, can you test 61440? If it eliminates the glitches I'll figure something out for Beta9. Powerline networking though is very suspect :-0

-Tim

Are we talking NFS here?

From the nfs(5) man page,

The maximum number of bytes in each network READ request that the NFS client can receive when reading data from a file on an NFS server. The actual data payload size of each NFS READ request is equal to or smaller than the rsize setting. The largest read payload supported by the Linux NFS client is 1,048,576 bytes (one megabyte).
...
If an rsize value is not specified, or if the specified rsize value is larger than the maximum that either client or server can support, the client and server negotiate the largest rsize value that they can both support.
...
The rsize mount option as specified on the mount(8) command line appears in the /etc/mtab file. However, the effective rsize value negotiated by the client and server is reported in the /proc/mounts file.

Based on what I found in a quick web search, I believe the new limit in Stretch was chosen based on file-transfer speed tests, e.g., maximizing average throughput.

Keep in mind that the NFS read request gets broken up into packets and segments and frames, oh my, as it moves through the Transport, Internet, and Network interface layers. At those levels I wouldn't think it matters what rsize is.

I'd think the most important effect of a large resize on the client is the need for larger buffers in memory.

Like @DRONE7, I'm more suspicious of the behavior of the intermediary network equipment such as the powerline adapters (and the home router).

Regards,
Kent

 

[TheOldPresbyope]

I got the same. I changed my sources file to a local repository to do the install. Worked fine (and faster) after that.

Hi, Morias.

How did you implement your local repo? I'm running apt-cache-ng on a local machine and point to it from every debian-based host I am working with. Over time the speed up of apt-get install steps is quite noticeable, although I've never tried benchmarking it.

Regards,
Kent

 

[TimCurtis]

Are we talking NFS here?

From the nfs(5) man page,

Based on what I found in a quick web search, I believe the new limit in Stretch was chosen based on file-transfer speed tests, e.g., maximizing average throughput.

Keep in mind that the NFS read request gets broken up into packets and segments and frames, oh my, as it moves through the Transport, Internet, and Network interface layers. At those levels I wouldn't think it matters what rsize is.

I'd think the most important effect of a large resize on the client is the need for larger buffers in memory.

Like @DRONE7, I'm more suspicious of the behavior of the intermediary network equipment such as the powerline adapters (and the home router).

Regards,
Kent

Hi Kent,

I thought the earlier post was about a CIFS mount but either way rsize applies to both CIFS and NFS and I'm thinking that the param needs another look.

-Tim

 

[rhizomusicosmos]

Hi @perryni,

I have a feeling it might be due to the loudness on some of my flacs. Some music is fine whereas some gets a bit crackly. Surely that’s a flac issue rather than a moode/RPI issue?

Is it possible that the FLAC files with the crackling have a lot of signal maxed at 0 dB FS and the Piano DAC is not coping well with intersample peaks? Any resulting distortion might be exacerbated by gain stages in the Ruark unit.

I know this is a contentious issue, but I did find someone who had done measurements for intersample overload distortion:
http://cdn-downloads.tcelectronic.com/media/1018176/nielsen_lund_2003_overload.pdf

Some people don't believe intersample peaks are audible but I have heard issues myself with heavily limited music (such as Adele's last album) on some equipment.

Cheers,
Richard

 

[onionhead]

Raspbian Stretch Lite and moOde are headless.

Unplug locally attached monitor and keyboard. Reboot and then from another computer on your network begin with STEP 3

ssh pi@raspberrypi (pwd=raspberry)

EDIT to add:

Pi will need access to Internet.

-Tim

Tim

I am getting somewhere. Connected pi device to my wifi router.

When I used pi@raspberrypi and got " ssh: Could not resolve hostname raspberry: nodename nor servname provided, or not known. When I use pi@10.0.0.20 I got "The authenticity of host '10.0.0.20 (10.0.0.20)' can't be established. ECDSA key fingerprint is :gj2dJ57Gj/eyJyWidIhKz+bFdnHrKTgKu8Z965lzFK8." I typed yes and I was in.

Now I have made to the expand the root partition. Typed in sudo cp ./rel-stretch/www/command/resizefs.sh ./ and got " sudo: unable to resolve host raspberrypi

My guess is because I was not able to access pi with pi@raspberrypi i need to change the references to raspberrypi to 10.0.0.20.

 

[DRONE7]

DSD or not DSD that is the question..?

Not particularly interested in Dsd....there isn't much available .
However, I am a little confused about how moode renders it..

I have a dac that will play native dsd 256 and it has both a lock indicator and one for dsd.

In moode mpd settings DoP is set to 'yes' when Native is not available.

If I play a dsd file both the lock and dsd lights come on for the dac.

Moode playback panel shows DSD as the file type being played but the 'audio info' window shows it being decoded at 24/352.8 and output as 32/352.8 ...

If I play pcm and upsample to 32/352.8 the dac lock lights but not the dsd light.

output is via usb to i2s xmos, not direct i2s from the pi.

any enlightenment appreciated

Hmmmm is the dsd light showing because .....

A specific marker code in the top 8 bits identifies the data stream as DoP, rather than PCM.

 

[rhizomusicosmos]

Not particularly interested in Dsd....there isn't much available .
However, I am a little confused about how moode renders it..

I have a dac that will play native dsd 256 and it has both a lock indicator and one for dsd.

In moode mpd settings DoP is set to 'yes' when Native is not available.

If I play a dsd file both the lock and dsd lights come on for the dac.

Moode playback panel shows DSD as the file type being played but the 'audio info' window shows it being decoded at 24/352.8 and output as 32/352.8 ...

If I play pcm and upsample to 32/352.8 the dac lock lights but not the dsd light.

output is via usb to i2s xmos, not direct i2s from the pi.

any enlightenment appreciated.

I'm not sure why the output of moOde is detailed as 32/352.8 but 24/352.8 is what is necessary for DSD128 data to be packed into a PCM stream (this is not to be confused with conversion of DSD to PCM). The following site has more info:
DoP open Standard | DSD-Guide.com

Richard