You are correct. The Squash and Unsquash instructions are in the Appendix. Here is what I do rebooting between each step:
1: Backup
2: Unsquash (only if you followed Step 10)
3: Update
4: Squash (optional)
5: Backup
6: Enjoy
You can just backup /var/www, or like me and don't know all what I am doing, just backup my whole image.
@zgtc
\2605 is the unicode representation of the "black star", see e.g. ★ | black star (U+2605) @ Graphemica
Not sure what has to be done to make this part of the moOde code base unicode-compliant. Tim likely can shed some light on it.
Regards,
Kent
Hi Kent,
Could be a mediainfo bug. moOde 4 uses avprobe instead of mediainfo so maybe this would work in 4.
-Tim
Could be a mediainfo bug. moOde 4 uses avprobe instead of mediainfo so maybe this would work in 4.
-Tim
Correct, I said weird but it's Unicode. The problem it's those chars are written in the folder/file names.
Makes sense. I'm still using 3.1. Will investigate if using unidecode I can manage to solve this. Last resort would be moving to 4 so I can use avprobe.
Thank you
Squash causes no-display issue?
Hi Tim,
Thanks for release beta11.
However, it seems that the Squash process causes the cover art issue again on my moOde 4b11.
I could solve this problem with re-Unsquash.
Is there anyone who has the same issue on cover art display?
kitamura_design
Hi Tim,
Thanks for release beta11.
However, it seems that the Squash process causes the cover art issue again on my moOde 4b11.
I could solve this problem with re-Unsquash.
Is there anyone who has the same issue on cover art display?
kitamura_design
Bluetooth speaker
Hi, Tim.
How about making it possible to override the default Bluetooth speaker name with an entry in the [names] section of the optional /boot/moodecfg.txt file?
That would put it on a par with the other renderer services.
Just my 2-cents worth. I'm enjoying the music.
Regards,
Kent
PS - @SanderG, since about beta10, the Bluetooth speaker name is "Moode Bluetooth" in the new moode-sqlite3.db(.default). In beta 9 the name was blank which would cause the issue you reported if you have been updating moOde but keeping the existing database. I ran into this one too.
Hi, Tim.
How about making it possible to override the default Bluetooth speaker name with an entry in the [names] section of the optional /boot/moodecfg.txt file?
That would put it on a par with the other renderer services.
Just my 2-cents worth. I'm enjoying the music.
Regards,
Kent
PS - @SanderG, since about beta10, the Bluetooth speaker name is "Moode Bluetooth" in the new moode-sqlite3.db(.default). In beta 9 the name was blank which would cause the issue you reported if you have been updating moOde but keeping the existing database. I ran into this one too.
I have updated to MoOde 4 beta 11 and running unsquash as that has caused me much grief ( mostly like due to my own errors(s). Interested in making a backup image so I can try to squash as it is recommended. I am very a Linux beginner. Any help with backup procedure would be most helpful.
I have updated to MoOde 4 beta 11 and running unsquash as that has caused me much grief ( mostly like due to my own errors(s). Interested in making a backup image so I can try to squash as it is recommended. I am very a Linux beginner. Any help with backup procedure would be most helpful.
Windows..? this...
How To Clone Your Raspberry Pi SD Card For Super-Easy Reinstallations | Lifehacker Australia
Linux/Mac..? This..
Backups - Raspberry Pi Documentation
Hi Tim, found on there homepage the following plugin for Volumio
http://forum.audiophonics.fr/download/file.php?id=561
can it also used for moode player ?
Thanks
Kai
@onionhead
If you scroll to the bottom of the build recipe there instructions on how to do this.
If you use Win32Disk make sure the file that you copy has .img on the end as Windows often leaves it off. Also make sure that you put a tick in "Read only allocated partitions"
Ronnie
Hi Kai,
Kernel drivers are tied to a specific kernel release. The maker of the driver must either get it accepted into mainline Linux kernel in which case it will automatically be available with every kernel release, or they must manually make a compiled binary for each Linux kernel thats released. Current mainline kernel is 4.9.65 and the driver you pointed to was made for 4.9.51
-Tim
Ronnie,
I am on MAC and used tried SD card procedures. First a file was created in Document folder see screenshot. Am I on the right pathway?
Can you see anything incorrect on the second screen shot?
Attachments
Since my posting a tried the SD CARD procedure at the end of the build recipe. Everything seemed to go as planned but the sdcard with MoOde refused to boot. As it was getting late I called it a day. Will give it another go today and see how it flies.
🙂
Newbie question: I've just got MoOde running on a Pi3, and have activated the Squeezelite renderer. Should the Pi now appear on the network as a squeezebox, in LMS and my control apps, as it hasn't?
If it should, how do I make it do this? Not tried a reboot yet, as playing with other bits.
If it should, how do I make it do this? Not tried a reboot yet, as playing with other bits.
Hi,
Yes it should. Verify that Squeezelite is installed and running using the cmds below.
which squeezelite-armv7l
pgrep -l squeezelite-arm
-Tim
My bad. I just read the setup.txt file. Gotta stop running on autopilot!
Regards,
Kent
I have updated to MoOde 4 beta 11 and running unsquash as that has caused me much grief ( mostly like due to my own errors(s). Interested in making a backup image so I can try to squash as it is recommended. I am very a Linux beginner. Any help with backup procedure would be most helpful.
I use Windows, so I use Win32DiskImager. Just put your micro SD card in, then open the folder icon, name a file you want the .img to be, make sure the drive letter is your SD card, check the box for Read Only Allocated Partitions,and click Read. Yes, Read. It makes no sense to click Read and create an image, but that's how it works. Write I think writes the image to the SD card.