Thanks
While executing "sudo ./mosbuild.sh" the command is asking for an USB drive. Shall I remove my USB mounted HDDs and insert an USB. I already have micro sd inserted and Raspbian booted and logged in.
Regards
Partha
I couldn't find any info, so I'm not sure if this has been asked before, but I was wondering if some more settings could be added to the "auto shuffle" feature. These are settings which I really enjoy in squeezebox:
Random Song (we have this)
Random Album (My favorite)
Random Artist
Random Genre
For me, these would me the feature perfect.
Other then that, I finally upgraded to a Pi3B over my original and holy mackerel is it fast! Got Beta12 installed last night without a hitch.
Random Song (we have this)
Random Album (My favorite)
Random Artist
Random Genre
For me, these would me the feature perfect.
Other then that, I finally upgraded to a Pi3B over my original and holy mackerel is it fast! Got Beta12 installed last night without a hitch.
I picked up a refurb unit recently, trying to figure out what to do with it. The build quality seems good, software is raspbian with Bryston additions. It's functionally similar to Moode or Volumio, but doesn't seem as nice to use. From photos it looks like you could open it up and put in an SD card with a Moose image on it. I may try that at some point.
finally got it installed .... what a long way
phew ... did take a while using HeeBoo's fantastic script. Without it I tried 2 days ago, and then gave up, better said I did go the easy way installing runeaudio, DietPi and Volumio.
They are all nice at some point and if you have a somewhat larger audio collection you run into unforseen limits of the software.
We'll see how this ends up, but it looks much more promissing. Means if it's techically at the same level the configuration section is (Just managed that one) it'll be really nice.
Nevertheless one problem (which I suffer with all the above mentioned software aswell as with Moode). I can't get my cifs shares mounted from within the frontend (didn't work with the above mentioned software, same problems)
But, I can easily mount them from within the shell. Any idea?
And don't repeat the nonense that I must add sec=ntlm. Wonder who ever mentioned that to be a solution. It isn't no matter how many poeple do write this to be the issue. Mounting from commandline using the very same parameters used in the frontend simply works while though frontend fails. That's the problem I'm after since I don't get it at all. Perhaps we have a cifs specialist in here?
phew ... did take a while using HeeBoo's fantastic script. Without it I tried 2 days ago, and then gave up, better said I did go the easy way installing runeaudio, DietPi and Volumio.
They are all nice at some point and if you have a somewhat larger audio collection you run into unforseen limits of the software.
We'll see how this ends up, but it looks much more promissing. Means if it's techically at the same level the configuration section is (Just managed that one) it'll be really nice.
Nevertheless one problem (which I suffer with all the above mentioned software aswell as with Moode). I can't get my cifs shares mounted from within the frontend (didn't work with the above mentioned software, same problems)
But, I can easily mount them from within the shell. Any idea?
And don't repeat the nonense that I must add sec=ntlm. Wonder who ever mentioned that to be a solution. It isn't no matter how many poeple do write this to be the issue. Mounting from commandline using the very same parameters used in the frontend simply works while though frontend fails. That's the problem I'm after since I don't get it at all. Perhaps we have a cifs specialist in here?
the simplest way for installing moOde (this is subjective)
How to install moOde on a RPi
Needed :
- a Raspberry Pi
- a micro SD Card of 4Gb minimum
- a computer to install Raspbian on the microSD (windows, mac, linux, unix,...) with a microSD Card drive
- on windows you have to use a third software to take the control of the RPi with ssh (explanation here)
- a fresh image of the last Raspbian Stretch lite downloadable here
- a software to install the image on the microSD like Etcher
- an internet connection
Steps :
- launch Etcher on your computer, drag the image of raspbian on the first icon, insert your micro SD card in your computer and launch it...
- When it's finished re-insert the microSD card in your computer, if all is good you can see a disk appear named "boot"
- create a blank file called ssh : (use your favorite text editor like notepad, smultron, Atom,... to save an empty file inside the "boot" disk)
- if you use wifi create a wpa_supplicant.conf file like explain here
- Eject the SD card, put it in the Raspberry pi and boot the raspberry (if you don't use wifi plug the ethernet on you RPi !)
- login to it in ssh with this command (the password at this step is: raspberry) :
- And finally, just launch this command :
How to know the installation process status
This is a (very) long process (depend of the connection, the microSD card and version of the RPi) and you must wait the END of the process. For look at the progress you can type this (the password at this step is: moodeaudio):
(yes, this is a different one... I have much more in my basket)
!!!! YOU MUST WAIT FOR THIS !!! :
If this is the case so you can enjoy your new installation of moOde, on your computer launch your web browser and access to http://moode or http://moode.local on a mac.
But Maybe you have this in the last line :
Don't panic and just reboot the RPi with this command:
The shorter version of the installation:
From a fresh installation of Raspbian Stretch lite launch this command:
Finished !
Good Luck
PS: my link of the moosimbu.sh script expire in 14 days... i hope the new mosbuild came it before this date.
How to install moOde on a RPi
Needed :
- a Raspberry Pi
- a micro SD Card of 4Gb minimum
- a computer to install Raspbian on the microSD (windows, mac, linux, unix,...) with a microSD Card drive
- on windows you have to use a third software to take the control of the RPi with ssh (explanation here)
- a fresh image of the last Raspbian Stretch lite downloadable here
- a software to install the image on the microSD like Etcher
- an internet connection
Steps :
- launch Etcher on your computer, drag the image of raspbian on the first icon, insert your micro SD card in your computer and launch it...
- When it's finished re-insert the microSD card in your computer, if all is good you can see a disk appear named "boot"
- create a blank file called ssh : (use your favorite text editor like notepad, smultron, Atom,... to save an empty file inside the "boot" disk)
- if you use wifi create a wpa_supplicant.conf file like explain here
- Eject the SD card, put it in the Raspberry pi and boot the raspberry (if you don't use wifi plug the ethernet on you RPi !)
- login to it in ssh with this command (the password at this step is: raspberry) :
Code:
ssh pi@raspberrypi
[I][COLOR="SeaGreen"]#on Mac OS :[/COLOR][/I]
ssh pi@raspberrypi.local
Code:
wget https://transfer.sh/TWE3G/moosimbu.sh && chmod +x ./moosimbu.sh; sudo ./moosimbu.sh -uHow to know the installation process status
This is a (very) long process (depend of the connection, the microSD card and version of the RPi) and you must wait the END of the process. For look at the progress you can type this (the password at this step is: moodeaudio):
Code:
ssh pi@moode "cat ./mosbuild.log | grep '^// \|^\*\* '"
[I][COLOR="SeaGreen"]#on Mac OS :[/COLOR][/I]
ssh pi@moode.local "cat ./mosbuild.log | grep '^// \|^\*\* '"
[I][COLOR="SeaGreen"]#if you are already logged to the raspberry, just enter:[/COLOR][/I]
cat ./mosbuild.log | grep "^// \|^\*\* "!!!! YOU MUST WAIT FOR THIS !!! :
Code:
// END
** Final rebootBut Maybe you have this in the last line :
Code:
** error: ......
Code:
ssh pi@moode "sudo reboot"
[I][COLOR="SeaGreen"]#on Mac OS :[/COLOR][/I]
ssh pi@moode.local "sudo reboot"
[I][COLOR="SeaGreen"]#if you are already logged to the raspberry, just enter:[/COLOR][/I]
sudo rebootThe shorter version of the installation:
From a fresh installation of Raspbian Stretch lite launch this command:
Code:
wget https://transfer.sh/TWE3G/moosimbu.sh && chmod +x ./moosimbu.sh; sudo ./moosimbu.sh -uGood Luck
PS: my link of the moosimbu.sh script expire in 14 days... i hope the new mosbuild came it before this date.
Last edited:
They have a nice case (could be worth 150$ of work) and their own software on top pf some linux distro. For such a product they must ensure that even switching it off does not consume any state so that upon switching it on again the device boots properly (something moode, volumio, etc cannot giarantee).
They can easily end up with a BOM of 300-350$ and for a commercial product this justifies 1250.
Roberto
Last edited:
hmm .... 2 hrs later ... Moode on a Pi3 performs as if one ripped the ARM chip and replaced it by an old Zilog Z80 if ever.
.... waiting for pi-ip the browser says since an hour.
Config modals aren't available any more.
var/www is at 100%
since not being a linux geek I wonder what's going on.
radiostation do play .. adding more fails
cifs mounts do fail as expected
nice enough album artists do work against artists
what I heavily do miss is the ability O!MPD offers, to handle multiple genres split upon "; "
mixed feelings after 2 hrs ... nice one for sure but nothing for a massiv audio collection. if it performs like this with next to 2% of my collection I wonder if it'll catch up after a months if being fed with the complete collection.
any idea if a larger SD card (16 gb now) would make a difference?
Perhaps I'll have a try with the new link HeeBoo just posted to see if that makes a difference using a 64gb sd card.
On the other hand it might be similar to my NAS which took more but a week until the audio station finished indexing and filling the psql database with all the metadata. Who knows ....
.... waiting for pi-ip the browser says since an hour.
Config modals aren't available any more.
var/www is at 100%
since not being a linux geek I wonder what's going on.
radiostation do play .. adding more fails
cifs mounts do fail as expected
nice enough album artists do work against artists
what I heavily do miss is the ability O!MPD offers, to handle multiple genres split upon "; "
mixed feelings after 2 hrs ... nice one for sure but nothing for a massiv audio collection. if it performs like this with next to 2% of my collection I wonder if it'll catch up after a months if being fed with the complete collection.
any idea if a larger SD card (16 gb now) would make a difference?
Perhaps I'll have a try with the new link HeeBoo just posted to see if that makes a difference using a 64gb sd card.
On the other hand it might be similar to my NAS which took more but a week until the audio station finished indexing and filling the psql database with all the metadata. Who knows ....
Hi,
Nice to hear that
Re Ashuffle, it can operate in several ways:
GitHub - joshkunz/ashuffle: Automatic library-wide shuffle for mpd.
1. Entire collection (default)
2. Specific list of song files fed via stdin
3. Excluded tag matches i.e. -e genre Rock -e genre Pop would exclude all song files whose genre tag matched Rock or Pop
4. #2 and #3 together
To experiment, first turn auto-shuffle off in moOde
Then run it from cmd line. Ctrl-c to terminate
ashuffle -e tag value -e tag value ...
-or-
mpc search tag value | ashuffle -f -
mpc search tag value | ashuffle -e tag value -e tag value ... -f -
You can also use mpc find instead of search. Find requires an exact match for value.
-Tim
Hi,
Very odd.
Symptoms suggest a broken build or bad SD card but in either case you need to post more information in order to troubleshoot.
1. Post contents of moode.log
a. Reboot
b. cat /var/log/moode.log
2. Post last 20 lines of MPD log
tail -n 20 /var/log/mpd/log
3. Post the mount string that you entered from cmd line
4. Post output from mount <no args>
5. Number of tracks in collection
6. General network config: WiFi, Ethernet, HomePlug
-Tim
Correct. Ok, had some sleep, things do work best in the morning after a cup'o'coffee.
What I found out when entering my workplace ... it was still unresponsive in many things. For example I could do sys-info but all config option still failed.
before the RESET I had a quick look into the logs and also compared them as suggested after a fresh reboot. (Should I mention here that shutdown and reboot didn't work at all from the GUI? Worked through the shell, and .. I did a complete powercut aswell to be on the safer side.)
ok before reset the following line did raise my attention:
watchdog: PHP restarted (fpm child limit 40 exceeded)
all the rest was pretty normal I'd say. Same for the mpd log.
you asked for the mount command & result and I think I nailed down the problem (perhaps.)
Since
name: music
ip: 192.168.1.5
share: /music
user: admin
pw: <my password>
args: domain=soho,ro
completely fails whereas
sudo mkdir /mnt/NAS/music
sudo mount -t cifs //192.168.1.5/music /mnt/NAS/music -ouser=admin,password='<password>',domain=soho,ro
works so that a sole mount command shows:
//192.168.1.5/music on /mnt/NAS/music type cifs (ro,relatime,vers=1.0,cache=strict,username=admin,domain=soho,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.5,unix,posixpaths,serverino,mapposix,acl,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,user=admin)
I do assume that you build the mount commend from the GUI entries without encapsulating the passwordstring within single-quotes, which, in case of using a passwordstring against a the name of your cat it'll fail due to special chars within the complete mount command, correct?
Since if I use the above command without the single quote I do run into the mount.cifs error. You could try yourself using some $ or # chars within the password.
Collectionsize. more but 100K flac tracks slowly growing.
(K=1024 not 1000
)Network, nothing special. cablemodem acting as access point + wlan access point. switch, and more but 2 handfull of devices, a complete mixture, windows, linux, android, goodies for the family like weatherstation, xbox, firetv and such like. dhcp and dnsmask by a pi running pihole.
Having restarted moode (nor reboot but with a real powercut) seems to work now. Perhaps it was me rushing through all the options yesterday while it was still scanning my share mounted from the commandline.
while writing these lines I had a quick look @ the mpd log ... it's still busy on artists starting with 'A'.
perhaps I should do a df -k from time to time to see if something fills up.
If it slows down again I'll then save the logs and try to remember at which point this started.
Would be nice to let me know if I'm right or wrong with the mount thingy.
-Stefan
Airplay receiver problem
Hi, i found out that airplay reciver doesn't work with the last beta and my usb-dac-amplifier (alientek d8).
searching on internet i found out that you have to change this line:
output_device = "hw:1"
to
output_device = "plughw:1"
in the "/usr/local/etc/shairport-sync.conf"
starting shairport-sync from command line infact work flawlessly, but this change in the config file doesn't effect moode, as i can see on the moode.log there is a script wich pass this command:
(/usr/local/bin/shairport-sync -a "Moode Airplay" -S soxr -w -B /var/local/www/commandw/spspre.sh -E /var/local/www/commandw/spspost.sh --metadata-pipename=/tmp/shamp/shairport-sync-metadata --get-coverart -- -d hw:1 -c "Mic" > /dev/null 2>&1 &)
how i can edit this script? i think i've to change hw:1 to plughw:1
can you help me?
Hi, i found out that airplay reciver doesn't work with the last beta and my usb-dac-amplifier (alientek d8).
searching on internet i found out that you have to change this line:
output_device = "hw:1"
to
output_device = "plughw:1"
in the "/usr/local/etc/shairport-sync.conf"
starting shairport-sync from command line infact work flawlessly, but this change in the config file doesn't effect moode, as i can see on the moode.log there is a script wich pass this command:
(/usr/local/bin/shairport-sync -a "Moode Airplay" -S soxr -w -B /var/local/www/commandw/spspre.sh -E /var/local/www/commandw/spspost.sh --metadata-pipename=/tmp/shamp/shairport-sync-metadata --get-coverart -- -d hw:1 -c "Mic" > /dev/null 2>&1 &)
how i can edit this script? i think i've to change hw:1 to plughw:1
can you help me?
See HeeBoo's post #12727 on the previous page.
Remember to remove anf USB devices from the Pi and preferably use a wired Ethernet connetion, it's quicker and more reliable.
Good Luck
Ian
I have successfully installed Beta 12 RPi3 and everything seems to work as expected.
However, I can no longer reproduce DSD music files. My DAC does not support native DSD neither DSD over PCM (DoP), threfore I am using DSD to PCM on-the-fly conversion. I have set the appropriate moode setting DoP to 'no'.
In order to reproduce DSD music files (.DFF) with the beta 12, I am forced to use SoX , i.e. 32Bit, *Khz. Without SoX there is no audio output.
With SoX however and due to extra cpu load I am experiencing some clicks and pops especially with DSD 128 files.
With older Moode releases (e.g 3.x images) using my RPi3 and the advanced Kernel settings option all DSD files were reproduced without any issues even with SoX disabled.
However, I can no longer reproduce DSD music files. My DAC does not support native DSD neither DSD over PCM (DoP), threfore I am using DSD to PCM on-the-fly conversion. I have set the appropriate moode setting DoP to 'no'.
In order to reproduce DSD music files (.DFF) with the beta 12, I am forced to use SoX , i.e. 32Bit, *Khz. Without SoX there is no audio output.
With SoX however and due to extra cpu load I am experiencing some clicks and pops especially with DSD 128 files.
With older Moode releases (e.g 3.x images) using my RPi3 and the advanced Kernel settings option all DSD files were reproduced without any issues even with SoX disabled.
Last edited: