Moode Audio Player for Raspberry Pi

Jump to Latest
#12,282
franz159 said:
What dac are you using?
Certain dacs require a specific bit length to be configured in Airplay settings.
For example with my Chord MoJo I have to set 32 bits for Airplay to work.
Click to expand...

It's cool, I basically hadn't done the full install of additional components. I had opened the build text file in Text Edit on the mac, and it hadn't actually loaded the full instructions. I opened the build txt file in TextWrangler (BBEdit), and I saw a bunch of additional steps.

I have to say, even though I'm a newbie, this install is actually basic. You just follow the instructions in the build.txt file, cut and paste and wait. I logged into my device on pi@<IP ADRESS>, if things didn't look right in a particular section I just did a sudo reboot, and logged back in and started the section I was on again.

If I can do it, anyone can do it. Now back to Christmas Day... and my speaker build.
 
#12,284
Hello.
I have a problem with mounting / defining the Samba resource. I am using version 4b12 of Moode.
The NAS resource is located on the sat tuner disk with the linux OS. The disk (1TB and many files) is available via SMB and identified by the name Harddisk.
Sharing is as a guest but you can also use the root account with the password of dreambox. I configure the NAS source in Moode:

Source name: Dreambox
Fileshare protocol: SMB/CIFS
Host or IP address: 192.168.1.103
Remote directory: Harddisk
User id: <blank>
Password: <blank>
Charset: UTF8 (default)
Rsize: 61440
Wsize: 65536
Mount flags: ro,dir_mode=0777,file_mode=0777


Once the SAVE is executed, the page remains, the busy cursor appears in the browser window. The NAS resource is not visible, you can not run any Configure subwindows.
From the command line (SSH) after executing df -k it follows that the SMB resource is not mounted. The following command is completed successfully, the resource is mounted correctly:

sudo mount -t cifs -o user=guest,password=,ro,dir_mode=0777,file_mode=0777 //192.168.1.103/Harddisk /mnt/NAS

(note: file_mode=0777 .... I do not know why the forum software inserts a space.)


I tried to use userid=root and password=dreambox. The result is identical. Not working any Configure subwindows, unmounted resource, but correctly executing mount from the command line. Adding sec = ntlm does not help. What am I doing wrong?.
 
Last edited:
#12,285
STUDI said:
Hello.
I have a problem with mounting / defining the Samba resource. I am using version 4b12 of Moode.
The NAS resource is located on the sat tuner disk with the linux OS. The disk (1TB and many files) is available via SMB and identified by the name Harddisk.
Sharing is as a guest but you can also use the root account with the password of dreambox. I configure the NAS source in Moode:

Source name: Dreambox
Fileshare protocol: SMB/CIFS
Host or IP address: 192.168.1.103
Remote directory: Harddisk
User id: <blank>
Password: <blank>
Charset: UTF8 (default)
Rsize: 61440
Wsize: 65536
Mount flags: ro,dir_mode=0777,file_mode=0777


Once the SAVE is executed, the page remains, the busy cursor appears in the browser window. The NAS resource is not visible, you can not run any Configure subwindows.
From the command line (SSH) after executing df -k it follows that the SMB resource is not mounted. The following command is completed successfully, the resource is mounted correctly:

sudo mount -t cifs -o user=guest,password=,ro,dir_mode=0777,file_mode=0777 //192.168.1.103/Harddisk /mnt/NAS

(note: file_mode=0777 .... I do not know why the forum software inserts a space.)


I tried to use userid=root and password=dreambox. The result is identical. Not working any Configure subwindows, unmounted resource, but correctly executing mount from the command line. Adding sec = ntlm does not help. What am I doing wrong?.
Click to expand...

Hi,

Very odd that it works via cmd line and not via NAS config using the exact same params.

To troubleshoot try the following:

1. Use NAS config to remove the NAS source
2. Verify that /mnt/NAS/Harddisk directory was removed
3. Use System config to turn on Debug logging
4. Create the MAS config again but use a bogus userid and password for example admin/admin
4. Examine moode.log and look for the mount string and any mount errors

cat /var/log/moode.log

-Tim
 
#12,286
TimCurtis said:
Hi,

Very odd that it works via cmd line and not via NAS config using the exact same params.

To troubleshoot try the following:

1. Use NAS config to remove the NAS source
2. Verify that /mnt/NAS/Harddisk directory was removed
3. Use System config to turn on Debug logging
4. Create the MAS config again but use a bogus userid and password for example admin/admin
4. Examine moode.log and look for the mount string and any mount errors

cat /var/log/moode.log

-Tim
Click to expand...


In addition to my previous post.
After the system reboots, the mpd daemon does not start. It can be run from the command line (/etc/init.d/mpd/start). However, the previously described problems with music sources still exist.

Returning to Your procedure.
Point 1 can not be executed because the Sources window can not be executed. It remains to start a new installation of Moode. This means that point 2 loses meaning.

New fresh Moode installation. I turned on Debug logging. Unfortunately, the execution of Set already causes the same symptom. The page is still busy. Any Configure windows are not opened. Restart - the effect of inactive Configure windows still exists.

Re-installing Moode on the SD card. I turned on Debug logging. I defined the source of the NAS with userid root and the password of dreambox. Below is what goes into the moode.


20171225 010058 engine-mpd: Connect
20171225 010058 engine-mpd: Session loaded
20171225 010058 engine-mpd: Open socket
20171225 010058 readMpdResponse(): reading response
20171225 010058 readMpdResponse(): success $str=(OK MPD 0.20.0)
20171225 010058 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
20171225 010058 engine-mpd: Get initial status
20171225 010058 readMpdResponse(): reading response
20171225 010058 readMpdResponse(): success $str=(OK)
20171225 010058 readMpdResponse(): success $resp[0]=(volume: 100)
20171225 010058 engine-mpd: UI state=(stop), MPD state=(stop)
20171225 010058 engine-mpd: Idle
20171225 010058 engine-mpd: Wait for idle timeout
20171225 010058 readMpdResponse(): reading response
20171225 010058 readMpdResponse(): reading response
20171225 010058 readMpdResponse(): success $str=(OK)
20171225 010058 readMpdResponse(): success $resp[0]=(file: SDCARD/Stereo Test/LRMonoPhase4.flac)
20171225 010128 waitWorker(): Start (src-config, w_active=1)
20171225 010129 waitWorker(): Wait (1)
20171225 010130 waitWorker(): Wait (2)
20171225 010131 waitWorker(): Wait (3)
20171225 010132 waitWorker(): Wait (4)
20171225 010133 waitWorker(): Wait (5)
20171225 010134 waitWorker(): Wait (6)


I think the problem lies somewhere else (because the inclusion of Debug log causes a similar problem after reboot). Probably something is badly written to files describing Moode confoguration. My question where are all parameters saved from the Web UI level saved?
 
#12,289
Alarm canceled. 🙂
The reason was that during the yesterday's construction of Moode, one of the network resources was not available. The structure of the nei files was therefore complete, there was only partial functionality, and the described effect depended on the details of the defined configuration. It expires that it is OK.
 
#12,290
meilenstein said:
Hi
I have to report the following : None of the Radiostations in the Browser-window are
klickable ( despite the Hand-coursor ), only via the 'Actions' Tab (..the three dots..) I can start playing a Station..
Is there already a solution ?
Thanks in advance
Click to expand...

Hi,

Its always been that way. Are you asking for the capability to click anywhere on the line and have the station start playing?

-Tim
 
#12,292
Local display

Hello and merry Xmas

I have succeed to install moode4 with the OS image builder. It works, with a Pi3, brand new sd Cards (Sandisk 16GB Ultra), a tiny USB card reader and a Pifi DAC+ found on ali....

I have tried to active local display (official rasp touch screen). It works.... half the way.
The 180 rotation works.... (i can see the the raspberry screen).
The UI does not appear, ( so do i need to install chromium like i did before?)

Thanks Tim and everybody for sharing experience
Pierem
 
#12,293
Sorry if i'm being thick...

I have just built moode on a raspi3b using 4 beta 12 and the Moosimbu script (got it working on 3rd attempt - 1st time around I was probably too impatient and started config'ing too soon, 2nd time around the local.rc failed to run correctly).

I think i'm all up and running now but have not yet connected the IQaudio Digi+ to my DAC and heard any music out of it yet.

I believe that you can add radio stations - I have found all the stream feed details but I don't see where I should enter them - how do I get to the radio station maintenance screen?
 
#12,297
Local UI

pierem said:
Hello and merry Xmas

I have tried to active local display (official rasp touch screen). It works.... half the way.
The 180 rotation works.... (i can see the the raspberry screen).
The UI does not appear, ( so do i need to install chromium like i did before?)
Click to expand...

Hi,
Have you installed the "additional components" ?
If yes, have you a touch screen and option "touch" is activated in the "configuration system"?
if yes, touch the screen for turn off the "screensaver"
if not, change the blank screen option to never & reboot...

If you haven't installed the additional components, you can make it with the instructions of the moode build recipe (COMPONENT 8) downloadable here : http://moodeaudio.org/docs/SOURCES.html

Here the part :
Code: 
////////////////////////////////////////////////////////////////
//
// COMPONENT 8 - Local UI display 
//
////////////////////////////////////////////////////////////////

1. Install xserver. Perform this step separately from the rest.

sudo apt-get -y install xinit xorg lsb-release xserver-xorg-legacy chromium-browser libgtk-3-0

2. Permissions, clean up and service config

sudo sed -i "s/allowed_users=console/allowed_users=anybody/" /etc/X11/Xwrapper.config
sudo apt-get clean
sudo systemctl daemon-reload
sudo systemctl disable localui

4. Configure Chrome Browser

NOTE: These steps are performed AFTER actually starting local display via System config,
rebooting and then accessing moOde on the local display.

a. Connect a keyboard.
b. Press Ctrl-t to open a separate instance of Chrome Browser.
c. For Raspberry Pi 7" Touch Display open Chrome settings and set the zoom to 75%.
d. Optionally, enter url chome://extensions and install the xontab virtual keyboard extension.
e. Enter url chrome://flags and scroll down to Overlay Scrollbars and enable the setting.

Good luck.
 
Last edited:
#12,299
Build with only one microSD

blach said:
Can anyone tell me how to install the sources? I'm not sure how to generate an .img file.
I have only one SD card so I cannot use the builder - theoretically would it work from a linux laptop as well?
Click to expand...

Hello,
You can maybe use this script, is made for this case :
Round 3 - One Script To Rule Them All...

If you use a laptop on Linux for made the Raspbian image you can copy directly the file to /home/pi (in original process it's copied in /boot drive) of the SDCard else it's the same process.

Good Luck !
 
Last edited:
You must log in or register to reply here.
Top Bottom