Moode Audio Player for Raspberry Pi

make command: number of jobs option

Hi, Tim.

Some time ago, you and Mike (@Zootalaws) had an exchange about the number of jobs option. As I read it, you asserted that simply invoking make was sufficient to build on as many cores as possible.

I don't see this behavior during my current build of r40b8 on an RPi3B.
I've tried three options while observing top in another terminal:

  • make <- spawns one job on one core
  • make -j4 <- spawns four jobs on four cores
  • make -j <- keeps spawning jobs until the system becomes unresponsive

Regards,
Kent
 
try "http://moode.local" or if you know the ip address of your RPi then try "http://xxx.xxx.xxx.xxx" (your device's ip address)

Thanks for suggestions. Still have the issue. I can see the Pi IP in my router management software and can ssh to the device, it just is not accessible as mentioned in the recipe. The recipe is NOT incorrect something I have done along the way is. Will keep a trying!!!
 
Hi, Tim.

Some time ago, you and Mike (@Zootalaws) had an exchange about the number of jobs option. As I read it, you asserted that simply invoking make was sufficient to build on as many cores as possible.

I don't see this behavior during my current build of r40b8 on an RPi3B.
I've tried three options while observing top in another terminal:

  • make <- spawns one job on one core
  • make -j4 <- spawns four jobs on four cores
  • make -j <- keeps spawning jobs until the system becomes unresponsive

Regards,
Kent

Hi Kent,

Interesting. Maybe I should update the Recipe for Beta9.

Try the variation below. It should return 4 on Pi2/3, CM3 and 1 on all the rest

make -j $(nproc --all)

-Tim
 
Tim, a quick question. In Step 8 the line;

Code:
sudo cp ./rel-stretch/network/wpa_supplicant.conf.default /etc/wpa_supplicant/wpa_supplicant.conf
does this clear out the wi-fi settings that may be applied in Step 1 or 2?

It seems that after the reboot in Step 9 wi-fi gets messed up, I had to plug in an ethernet cable to finish the build.

Paul.
 
Tim, a quick question. In Step 8 the line;

Code:
sudo cp ./rel-stretch/network/wpa_supplicant.conf.default /etc/wpa_supplicant/wpa_supplicant.conf
does this clear out the wi-fi settings that may be applied in Step 1 or 2?

It seems that after the reboot in Step 9 wi-fi gets messed up, I had to plug in an ethernet cable to finish the build.

Paul.

Hi Paul,

Yes, you can either perform the copy or open the Network config page and APPLY the settings. That will rewrite the wpa_supplicant.conf file.

-Tim
 
Folks,

I was building a fresh copy of r40b8 specifically to save as a .img file so I was scrupulously following Tim's recipe instead of "interpreting" it.

This on an RPi3B.

When I got to "// COMPONENT 6 - Upmpdcli" I actually sat and watched instead of going off to do household chores.

I was struck that sudo pip install gmusicapi was taking forever at
Code:
Building wheels for collected packages: lxml
  Running setup.py bdist_wheel for lxml ... |
One CPU was pegged at 100% for more than 5 minutes by the time I got impatient and ctrl-C'ed out of the install.

I went straight to the apt repo.
Code:
sudo apt-get install python-lxml
That took a little time because of dependencies but was still reasonably quick.

Once that was done, I ran sudo pip install gmusicapi without issue.

I'm curious if others have run into the same slowdown? If so, did you just stick it out how long did it take to complete? (I installed gmusicapi in an earlier build but I must have been away from the console for a long time).

Regards,
Kent

Hi Kent. I had the exact same experience with the last build
 
Hi Kent,

Interesting. Maybe I should update the Recipe for Beta9.

Try the variation below. It should return 4 on Pi2/3, CM3 and 1 on all the rest

make -j $(nproc --all)

-Tim

All I have online at the moment are an RPi0W and an RPi3B. Randomly chose squeezelite to rebuild on both. Worked as advertised. 1 job on the zero and 4 jobs on the RPi3B.

Regards,
Kent
 
Yes I had the same issue, gave up waiting and continued without it. It's just for Google Music isn't it?

Yes.

If I get time tonight, I'll do a little benchmarking to see how much time it takes to run pip installs vs apt installs of some of the gmusicapi dependencies. At a glance, installing lxml appears to be the big time sink.

I like Mike's approach. Not only does a movie help the time pass, but all my projects would be more attractive to my significant other if they included a movie date!

Regards,
Kent
 
Yes.

If I get time tonight, I'll do a little benchmarking to see how much time it takes to run pip installs vs apt installs of some of the gmusicapi dependencies. At a glance, installing lxml appears to be the big time sink.

I like Mike's approach. Not only does a movie help the time pass, but all my projects would be more attractive to my significant other if they included a movie date!

Regards,
Kent

The advantage of using apt-get for the dependencies is that they get updated if needed by apt-get upgrade in the future.

Clever way would be to switch to python 3, and use pip3 install. See the Raspberry Pi blog for details.

No idea what would break with python 3, though.


Cheers,

Phil
 
I can't reproduce the dropout problem on beta 8, whatever my rsize setting was (default or 61440).

On beta 5, the problem would always occur on RT kernel when playing a certain FLAC-encoded track, whatever the rsize setting, but was OK with the standard kernel.

To my ears, moode beta 8 with standard sounds better than beta 5 with RT kernel.

Wonder if others feel the same.

Cheers,

Phil
 
Hi all,
i really (really :p) enjoy Moode Audio ... so i spent some time to completely batch the build process with a raspberry PI running another OS (in my case, volumio :D).

If someone want to try it ... i have uploaded a zip file with instructions and 2 install files.
In the zip you will also find 2 logs files with my last test of the process (theses are useless for the process ... it is just to show it was OK on my PI3)

Zip file is here : Uploadfiles.io - MoOde Automatic Install.zip

Tim feel free to use it ... i cannot mp you before posting ... your box is full :D
If you not agree with that, let me know i will delete this post.

Regards.
 
Hi all,
i really (really :p) enjoy Moode Audio ... so i spent some time to completely batch the build process with a raspberry PI running another OS (in my case, volumio :D).

If someone want to try it ... i have uploaded a zip file with instructions and 2 install files.
In the zip you will also find 2 logs files with my last test of the process (theses are useless for the process ... it is just to show it was OK on my PI3)

Zip file is here : Uploadfiles.io - MoOde Automatic Install.zip

Tim feel free to use it ... i cannot mp you before posting ... your box is full :D
If you not agree with that, let me know i will delete this post.

Regards.

Hi,

Downloaded :)

I'll have try later today. Feel free to email me. tim at moodeaudio dot org

Script coding looks awesome! lol, I didn't realize there were 8 boots :-0 maybe that can be reduced?

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

I tested it this evening and when you read an image from the SD card with the "read only allocated partitions" checkbox selected it creates an image file that is 3 Gigs big in stead of the almost 16 Gigs which is the size of the memory card I am using.

This is for the full Moode 4b8 with all the optional features installed.

If you compress that file you end up with a zip file that is 1Gig.
 
I tested it this evening and when you read an image from the SD card with the "read only allocated partitions" checkbox selected it creates an image file that is 3 Gigs big in stead of the almost 16 Gigs which is the size of the memory card I am using.

This is for the full Moode 4b8 with all the optional features installed.

If you compress that file you end up with a zip file that is 1Gig.

Thats cool. I'll make a note of this in the recipe.