Moode Audio Player for Raspberry Pi

Jump to Latest
koda59

koda59

Member
Joined 2017
You can force the default date/time in /etc/fake-hwclock.data.
Look at this file, modify it and after reboot it must start with this one.

Best way to solve your problem is to reboot, let the script failed.
Modify /etc/fake-hwclock.data ... and reboot.

The building must resume and if your date's modification is ok ... it must continue without error.

Regards

-Eric

PS : @Tim, i thought to have anticipate this problem (line 499 mosbuild) but only for SD Card install not direct one.
Maybe something to modify around this to take the clock on the net and save it in /etc/fake-hwclock.data for all case.

sinski said:
Hi,
i am trying to compile 4.0 on Pi 3. I am installing Raspbian Stretch Lite release 2017-11-29, than login with ssh and starting mosbuild.sh. After long, long time installation is exited. I repeated it few times, it is always the same error:



i can reboot and it is happening again. Tried few different sd cards and also newer Rasbian.

This is the mosbrief output:



i noticed, that the time on pi is wrong:



and in mosbuild.log they are tausends warnings like this:





any hints ?
Click to expand...
 
Last edited:
sinski

sinski

Member
Joined 2004
koda59 said:
You can force the default date/time in /etc/fake-hwclock.data.
Look at this file, modify it and after reboot it must start with this one.

Best way to solve your problem is to reboot, let the script failed.
Modify /etc/fake-hwclock.data ... and reboot.

The building must resume and if your date's modification is ok ... it must continue without error.

Regards

-Eric

Thanks Eric. I edited /etc/fake-hwclock.data, but after each reboot the file i written new by some starts scripts and pi time is again "Wed 29 Nov 03:27:53 UTC 2017" ...
Click to expand...
 
TimCurtis

TimCurtis

Member
Joined 2012
moodeaudio.org
sinski said:
Hi,
i am trying to compile 4.0 on Pi 3. I am installing Raspbian Stretch Lite release 2017-11-29, than login with ssh and starting mosbuild.sh. After long, long time installation is exited. I repeated it few times, it is always the same error:



i can reboot and it is happening again. Tried few different sd cards and also newer Rasbian.

This is the mosbrief output:



i noticed, that the time on pi is wrong:



and in mosbuild.log they are tausends warnings like this:





any hints ?
Click to expand...

To troubleshoot:

1. Boot up fresh Stretch Lite
2. Use raspy-config to set date, time and timezone
3. Reboot

Post output from cmds below:

timedatectl
cat /etc/fake-hwclock.data

Then verify that the git clone that was bombing works ok. There was an issue with this particular repo a while back and so in the next ver of the Builder I've included it as a local repo.
Code: 
sudo git clone [url]https://@opensourceprojects.eu/git/p/libupnppsamples/code[/url] libupnppsamples-code

It may be that the direct build method needs an additional manual step to use raspy-config to set current time. I've not had to do this in my tests but it may be a corner case that has to be handled.

Here is how fake-hwclock is supposed to work
fake-hwclock(8) — fake-hwclock — Debian jessie — Debian Manpages
 
Last edited:
sinski

sinski

Member
Joined 2004
Hi Tim,

1. I can't find the option to set the current time with raspy-config, i can only change the timezone.

2. I tried this on fresh Stretch Lite (after i installed git) :

pi@raspberrypi:~ $ sudo git clone 403 Forbidden libupnppsamples-code
Cloning into 'libupnppsamples-code'...
fatal: unable to access 'https://@opensourceprojects.eu/git//libupnppsamples/code/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Click to expand...

:confused:
 
T

TheOldPresbyope

Member
Joined 2015
sinski said:
Hi Tim,

1. I can't find the option to set the current time with raspy-config, i can only change the timezone.

2. I tried this on fresh Stretch Lite (after i installed git) :



:confused:
Click to expand...

@sinski

Check out this server-certificate-verification-failed discussion on StackOverflow.

I don't know why this is happening to you. The same steps you took succeed for me here. If you're feeling über-gutsy, you can disable SSL checking ala
Code: 
export GIT_SSL_NO_VERIFY=1
. Have to run now but if you need help let us know.

Regards,
Kent
 
TimCurtis

TimCurtis

Member
Joined 2012
moodeaudio.org
Works ok here on my end.

pi@rp3:~ $ sudo git clone https://@opensourceprojects.eu/git/p/libupnppsamples/code libupnppsamples-code
Cloning into 'libupnppsamples-code'...
remote: Counting objects: 62, done.
remote: Compressing objects: 100% (62/62), done.
remote: Total 62 (delta 19), reused 0 (delta 0)
Unpacking objects: 100% (62/62), done.
pi@rp3:~ $

Here is the URL. Just remove the space between the https:// and the @ sign
https:// @opensourceprojects.eu/git/p/libupnppsamples/code libupnppsamples-code
 
RafaPolit

RafaPolit

Member
Joined 2016
Http://rafaelpolit.com
T

TomWoB

Member
Joined 2017
Some Answers

Zootalaws wrotes regarding "soldering the Pi":
---------------------------------------------
You don’t need to solder + can just plug onto the GND/5V posts.
Comment: but moOde user have typically an audio board mounted on the Pi, so the "GPIO posts are gone" ... e.g. they are completly covered by my DigiOne board, so soldering is "somehow necessary" ...
I did some solder explanations here: Allo DigiOne board - Raspberry Pi - Roon Labs Community

JonPike asked regarding "USB-Case for SSDs":
---------------------------------------------
Q: do you power your SSD directly from the Pi USB port?
A: yes, no other power needed. I use a 1TB Samsung 840 EVO Basic which has a specified power consumption of only 0.1W! (I was never happy with that SSD on SATA, remember the 15MB/s read speed, because of buggy TLC firmware)

Q: any problems running under the USB 2.0 rather than 3.0?
A: no problems, my DigiOne board supports up to 24-bit, 192kHz. No problem playing such files from SSD. Only the "download speed" from network to SSD is very slow, because of sharing network with USB -> approx 8 BM/s.


 
Last edited:
E

EarsOfAnEagle

Member
Joined 2017
TimCurtis

TimCurtis

Member
Joined 2012
moodeaudio.org
grumbleweed said:
I do Tim but it's something that could be easily managed outside moode, if someone needs it. I did run v1.2.1 on moode beta4 and it seemed to work ok - ReadyMedia - Browse /minidlna at SourceForge.net

Paul
Click to expand...

Hi Paul,

I just tried compiling 1.2.1 and got an error at the end of ./configure. Are there some additional devlibs that have to be installed beyond whats already on moode os?

Code: 
configure: error: libjpeg headers not found or not usable

-Tim

Code: 
pi@rp1:~ $ cd ./minidlna-1.2.1/
pi@rp1:~/minidlna-1.2.1 $ ./configure
checking build system type... armv7l-unknown-linux-gnueabihf
checking host system type... armv7l-unknown-linux-gnueabihf
checking target system type... armv7l-unknown-linux-gnueabihf
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for iconv... yes
checking for working iconv... yes
checking for iconv declaration... 
         extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for gawk... (cached) mawk
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for inline... inline
checking for mode_t... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for uint8_t... yes
checking for int32_t... yes
checking for uint32_t... yes
checking for uint64_t... yes
checking for ssize_t... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for struct dirent.d_type... yes
checking for struct stat.st_blocks... yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking whether byte ordering is bigendian... no
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking whether lstat correctly handles trailing slash... yes
checking for gethostname... yes
checking for getifaddrs... yes
checking for gettimeofday... yes
checking for inet_ntoa... yes
checking for memmove... yes
checking for memset... yes
checking for mkdir... yes
checking for realpath... yes
checking for select... yes
checking for sendfile... yes
checking for setlocale... yes
checking for socket... yes
checking for strcasecmp... yes
checking for strchr... yes
checking for strdup... yes
checking for strerror... yes
checking for strncasecmp... yes
checking for strpbrk... yes
checking for strrchr... yes
checking for strstr... yes
checking for strtol... yes
checking for strtoul... yes
checking for struct ip_mreqn... yes
checking syscall.h usability... yes
checking syscall.h presence... yes
checking for syscall.h... yes
checking sys/syscall.h usability... yes
checking sys/syscall.h presence... yes
checking for sys/syscall.h... yes
checking mach/mach_time.h usability... no
checking mach/mach_time.h presence... no
checking for mach/mach_time.h... no
checking for __NR_clock_gettime syscall... yes
checking for linux/netlink.h... yes
checking libavutil/avutil.h usability... yes
checking libavutil/avutil.h presence... yes
checking for libavutil/avutil.h... yes
checking ffmpeg/libavutil/avutil.h usability... no
checking ffmpeg/libavutil/avutil.h presence... no
checking for ffmpeg/libavutil/avutil.h... no
checking libav/libavutil/avutil.h usability... no
checking libav/libavutil/avutil.h presence... no
checking for libav/libavutil/avutil.h... no
checking avutil.h usability... no
checking avutil.h presence... no
checking for avutil.h... no
checking ffmpeg/avutil.h usability... no
checking ffmpeg/avutil.h presence... no
checking for ffmpeg/avutil.h... no
checking libav/avutil.h usability... no
checking libav/avutil.h presence... no
checking for libav/avutil.h... no
checking libavcodec/avcodec.h usability... yes
checking libavcodec/avcodec.h presence... yes
checking for libavcodec/avcodec.h... yes
checking ffmpeg/libavcodec/avcodec.h usability... no
checking ffmpeg/libavcodec/avcodec.h presence... no
checking for ffmpeg/libavcodec/avcodec.h... no
checking libav/libavcodec/avcodec.h usability... no
checking libav/libavcodec/avcodec.h presence... no
checking for libav/libavcodec/avcodec.h... no
checking avcodec.h usability... no
checking avcodec.h presence... no
checking for avcodec.h... no
checking ffmpeg/avcodec.h usability... no
checking ffmpeg/avcodec.h presence... no
checking for ffmpeg/avcodec.h... no
checking libav/avcodec.h usability... no
checking libav/avcodec.h presence... no
checking for libav/avcodec.h... no
checking libavformat/avformat.h usability... yes
checking libavformat/avformat.h presence... yes
checking for libavformat/avformat.h... yes
checking ffmpeg/libavformat/avformat.h usability... no
checking ffmpeg/libavformat/avformat.h presence... no
checking for ffmpeg/libavformat/avformat.h... no
checking libav/libavformat/avformat.h usability... no
checking libav/libavformat/avformat.h presence... no
checking for libav/libavformat/avformat.h... no
checking avformat.h usability... no
checking avformat.h presence... no
checking for avformat.h... no
checking ffmpeg/avformat.h usability... no
checking ffmpeg/avformat.h presence... no
checking for ffmpeg/avformat.h... no
checking libav/avformat.h usability... no
checking libav/avformat.h presence... no
checking for libav/avformat.h... no
checking jpeglib.h usability... no
checking jpeglib.h presence... no
checking for jpeglib.h... no
checking jpeglib.h usability... no
checking jpeglib.h presence... no
checking for jpeglib.h... no
configure: error: libjpeg headers not found or not usable
pi@rp1:~/minidlna-1.2.1 $
 
P

pinkdot

Member
Joined 2016
Jempie said:
My info is correct i use public

on mij PC / network / sonos / public

it work for sonos but not for moodeaudio

thx
Click to expand...
If I understood you correctly in your first post:
SMB/CIFS
Host or IP address
192.168.1.157
Remote directory
sonos/public

Meaning you have a folder 'sonos' as a samba share folder on the Synology. Just like your ' photo, music,video and home folder?
In this 'sonos' folder you have a sub folder 'public'? If this is the case: first check if you can add the 'music' folder instead. Place a few files inside the music share and add it to moode. Does this work? Check if the music folder has the same permissions as the sonos'/public folder.
 
R

RincewindGER

Member
Joined 2014
Where is Moode Audio Player for beginners?

Hi!

It is some time ago, that I wrote a guide for newbies in Germany, a how to install and configure your networkplayer using Moode (check it here Google Translate )
The main reason for this kind of user manual was, that the most people don't think like a computer enthusiast. They need very simple and easy to adapt steps to do use something.

The current moode software can't be used by people with small knowledge how a computer is working. The most of them could be proud, if they have managed to type a URL in their browser without any errors.

@Tim Curtis: You have created a really good Raspberry Pi music player! But this Version is usable by very experienced computer users. It is now your focus? Or do you have plans to offer in the next future a MoodePlayer image?

Thank you Tim for your best audio player for RaspberryPI!

Rincewind (from Germany)

P.S.
Did you have ever think about, why Sesam Street is one of the most viewed channels?
 
rhizomusicosmos

rhizomusicosmos

Member
Joined 2011
TimCurtis said:
Have a look at Forums

Its a significant decision for me to step away from diyAudio so I'll need some feedback from people on whether they truly want a dedicated Forum. I'll also need help administering and moderating it.

-Tim
Click to expand...

A forum could offer some great benefits:

  • Stickies and FAQs will help reduce the amount of repetition in questions and answers (e.g. Why isn't moOde available as a pre-compiled image?)
  • Browsing for information should be easier
  • Users can contribute their own experiences, workarounds, etc., to the knowledge base
  • Fostering community through a variety of topics related to moOde
However, the first two points could be addressed by a Wiki and consideration of benefits has to be balanced with the extra overhead of moderating and running a forum.


-Richard
 
You must log in or register to reply here.
Top Bottom