Hello.
Thank you, to Tim and to Koda59, for patience and help.
I'm using the verse Moode Audio 4.0, Beta 12, everything went smoothly or almost, everything seems to work very well.
Some questions.
I would like to understand why in System Modifications, Linux kernel is only Standard, perhaps because it is the best of the three old versions of Kernel, or are there any special Kernels to improve performance?
The CPU governor, allows you to choose between: Performance or On-Demand, with which of the two can you give more in terms of quality?
Also in System Config we have "Download image builder" I downloaded the image generator that will be really useful to make copies of the program in a simple way, great idea.
Greetings
Jon
libtool: link: `../threadutil/libthreadutil.la' is not a valid libtool archive
Makefile:963: recipe for target 'libupnp.la' failed
make[3]: *** [libupnp.la] Error 1
make[3]: Leaving directory '/home/pi/mosbuild/libupnp-1.6.20.jfd5/upnp'
Makefile:1379: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/pi/mosbuild/libupnp-1.6.20.jfd5/upnp'
Makefile:512: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/pi/mosbuild/libupnp-1.6.20.jfd5'
Makefile:412: recipe for target 'all' failed
make: *** [all] Error 2
** Error: Make failed
** Image build cancelled
Who is ?
Makefile:963: recipe for target 'libupnp.la' failed
make[3]: *** [libupnp.la] Error 1
make[3]: Leaving directory '/home/pi/mosbuild/libupnp-1.6.20.jfd5/upnp'
Makefile:1379: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/pi/mosbuild/libupnp-1.6.20.jfd5/upnp'
Makefile:512: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/pi/mosbuild/libupnp-1.6.20.jfd5'
Makefile:412: recipe for target 'all' failed
make: *** [all] Error 2
** Error: Make failed
** Image build cancelled
Who is ?
Thanks Serverbaboon. I think I had everything installed and had configured my password in Moode. Just to be sure I reinstalled Upmpdcli which is item 4 of Component 6 and the gmusicapi (which said it was already installed). I then rebooted my raspberry pi.
That didn't make any difference and it still wouldn't play.
Using BubbleDs I then changed my library from "Moode UPNP-mediaserver" to "Local and Cloud" and configured Google Music in my phone.
It will now play music but I thought I was meant to use the library from Moode not local and cloud.
@ms2204
Haven't seen anyone answer yet so here's my take:
- RPi2B? yes, I'm running r40b12 on both RPi2B and RPi3B just now, with HiFiBerry DAC+ and DAC+ Pro (sorry @Zootalaws, I was young and foolish last year, metaphorically speaking
).
- Imagebuilder on an existing Moode Installation? Yes...but. I've done it from the command line. Just this morning I tried it by downloading the builder via the moOde GUI (System config/Download image builder) and running it via the moOde SSH term server. The script started fine but came to a full stop after successfully downloading raspbian-stretch-lite.zip. No time to diagnose this until tonight.
The old installation won't be overwritten unless you try something like @HeeBoo's direct installation procedure.- Chromecast audio? Not now, AFAIK. Only Tim can predict the future.
- Bluetooth source (which means streaming from moOde to some Bluetooth sink, like a Bluetooth speaker)? Not now. Again, only Tim can predict the future.
Regards,
Kent
Bluetooth out requires Blueman (Bluetooth manager)
sudo apt-get install pi-bluetooth blueman
Different kind of radiation - WiFi is ‘non-ionizing’ and presents no health risk for any humans, even little ones, even at 500-1000x the maximum power allowed by regulations.
Bang as much WiFi as you like around the house, you have more to worry about by taking them outside in the hot Greek sun
Pi64 is not yet mature as an OS, let alone the apps you might run on it. And like Kent, I would have to ask ‘why?’
The payback for 64bit OS’ are all in areas that the Pi doesn’t address, specifically OS RAM > 4GB. It isn’t ‘faster’ - it can be slower, with bigger tables, bigger address registers, etc.
Where 64bit gives significant boosts is with big RAM, and with crunching big numbers, which it can do in half the number of register calls as a 32bit OS.
When there is a mature 64bit OS for the Pi, no doubt most of the app developers that need bignumber support will produce a 64bit version, but unless they have coded their app with 64bit integer support, compiling it to run on Pi64 wont make any difference.
Given the vast number of 32bit Pi out there, I wouldn’t hold my breath, and there’s no need to - 32bit Pi is not holding you back, in any way.
IMO not wronger one can be.Different kind of radiation - WiFi is ‘non-ionizing’ and presents no health risk for any humans, even little ones, even at 500-1000x the maximum power allowed by regulations.
Bang as much WiFi as you like around the house, you have more to worry about by taking them outside in the hot Greek sun
Just fooling around. Compiled an rt kernel and used the script to build moOde on top of it. This is what happens when I am spoiled by the wonderful build scripts by @koda59 and @HeBoo, I have extra time on my hands Excellent work guys!
Now if I could just figure out how to enable max 384k PCM output via I2S, I'll be very happy. I wonder how one does that?
Excellent work guys!An externally hosted image should be here but it was not working when we last tested it.
Now if I could just figure out how to enable max 384k PCM output via I2S, I'll be very happy. I wonder how one does that?
Hi,
Good question.
"...but I thought I was meant to use the library from Moode not local and cloud..."
Here is the link from JFD's site that provides some info on Music Services. I don't have Google Music, Tidal or Qobuz subscriptions so not able to test.
Upmpdcli
-Tim
Just fooling around. Compiled an rt kernel and used the script to build moOde on top of it. This is what happens when I am spoiled by the wonderful build scripts by @koda59 and @HeBoo, I have extra time on my hands
An externally hosted image should be here but it was not working when we last tested it.
Now if I could just figure out how to enable max 384k PCM output via I2S, I'll be very happy. I wonder how one does that?
Good work! Would you be willing/able to provide an idiot-proof guide on how to do that?
I had reverted just now to listening via the LL Kernel on an earlier release of Moode when I saw your post.
/var/www/command/worker.php
$lock = fopen('/run/worker.pid', 'c+');
It can't create the file, exit with error. Modify it to '/tmp/worker.pid', doesn't work in the same way.
So nice! Thanks a lot. I just want to see wether the sound on the 64bit os is better.
Thanks, Mike.
I have some cheap Bluetooth speakers I wouldn't want to listen to for long stretches, but I'd like to be able to use them while I'm testing at my desk.
When I tried to cobble together a working setup out of the core packages earlier this year I couldn't get all the gears to mesh with moOde. Blueman is written in GTK+ so I ignored it. I should look into what it does---maybe I missed something---and try again.
If moOde can be made to work as a Bluetooth media source, I'm sure Tim can cobble up the additional configuration option before the coffee break
Regards,
Kent
Tidal works fine in my setup whether moOde or BubbleUPnP is the proxy media-server. I'll stand up a trial Google Play Music subscription and try using it with moOde today.
[off topic] Based on the financial reports I've been seeing on news-aggregator sites recently, Tidal will run out of money within a year. I only discovered it because moOde. I'm bummed.
Regards,
Kent
Unfortunately there is no easy way to this, unless we can somehow get the precompiled advanced kernels.
This is what I did, and mind you, this still needs a lot of work as I haven't figured out a number of things yet.
Basically I followed the following steps from the official Raspi how-to on compiling kernels.
Kernel building - Raspberry Pi Documentation
The difference between the above steps when compiling the rt kernel is you need to get the rt patch for the standard kernel source you have downloaded.
So let's assume you are in your home directory:
Download kernel source:
git clone --depth=1 GitHub - raspberrypi/linux: Kernel source tree for Raspberry Pi Foundation-provided kernel builds. Issues unrelated to the linux kernel should be posted on the community forum at https://www.raspberrypi.org/forum
cd linux
wget 404 Not Found
sudo xzcat ../patch-4.9.65-rt57-rc2.patch.xz | patch -p1
I used this particular patch because you will get a 4.9.X version of the standard kernel from the git repository.
There are a lot of versions so get what works for you.
The other thing to do before starting to compile is after you have created the default .config file as per the Raspi guide, you'll have to edit the following areas in this file so they look like this:
##General Setup
CONFIG_LOCALVERSION_AUTO=y
##Kernel Features
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT_RT_FULL=y
##CPU Frequency scaling
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
#CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
There are a lot of configs in this file, and I feel I have just scratched the surface
Compiling on the Raspi itself is less complicated, but it took me 2 hours or more to finish.
Cross compiling on a Linux installed via virtualbox on a Mac took 40 minutes or so, but the steps are more complicated (also indicated in the Raspi compilation guide).
After that you simply apply the moOde build scripts aforementioned.
Hope this helps.
Hi,
Give me an idea of how you want this to operate
-Tim
Just like Spotify: while playing a song, click on the right side (now only options for moving items or set clock radio) and choose 'Add to playlist'. Next screen must be a list of already existing playlists.
Technicly it won't be as easy as I describe