... some questions for dummies

[Venerdi]

Hi Guys,

I went from version 7.61 to version 8.02.
I have seen that in the System Config there is no longer the option to expand the File System. Why?
The choice of 32bit / 64bit Kernel architecture is no longer there. Why?
I also have another question for a long time...
Are there any real advantages to using a larger microSD card or not? I use moOde Audio with a Synology NAS where I have about 10,000 cds, with about 85,000 FLAC files and about 10,000 JPG (covers). This question is related to the first. What was the purpose of expanding the File System?
Thanks 
V.

[Tim Curtis]

In moOde 8 series the file system is auto-expanded at first boot as is done in stock RaspiOS.
The 64 bit kernel option was dripped because it caused MPD database update to sometimes crash.
Size of SDCard does not matter as long as its > size of image which 4.7GB + .5GB ~= 5.25GB

[Venerdi]

In moOde 8 series the file system is auto-expanded at first boot as is done in stock RaspiOS.
The 64 bit kernel option was dripped because it caused MPD database update to sometimes crash.
Size of SDCard does not matter as long as its > size of image which 4.7GB + .5GB ~= 5.25GB

Thanks Tim,
I thought that the dbase of the library and the thumbnails cover of the cd took up space on the microSD...

[Tim Curtis]

They do but practically speaking most SD Cards today are minimum 32GB which should be big enough for tag database, library cache and thumbnails.

[TheOldPresbyope]

@Venerdi

Since you've already been running moOde 7.6.1 and 8.0.2 you can gather the info yourself but it you want an estimate I just looked at my modest collection.

moOde 8.0.2
NAS - 519 albums, 5879 tracks

Some key files and the thumbnails directory
/var/local/www/libcache_all.json = ~260K 
/var/lib/mpd/database = ~284K
/var/local/www/imagesw/thmcache = ~4.5M

If I scale these sizes by a factor of 20 to approximate your collection, I get ~100M total. That's a pittance compared to the sizes of uSD cards these days.

What I wonder about is the speed of the moOdeUI in a typical browser/OS, especially on handheld devices, dealing with a ~5M json file and all the thumbnails...but you can test that too.

Regards,
Kent

[Venerdi]

@TheOldPresbyope

Very interesting what you wrote ... Thanks Kent!
Unfortunately I don't know how to go to see the size of the folders on the raspberry... I am one of the dummies
Regarding the speed of the browser (in MoOde Audio), at first it was disastrous...
Then I created folders with the letters of the alphabet, with a folder inside for each artist. Still inside a folder for each cd.
This solved the speed problem. The songs starts in real time; the cover image arrives 2 to 5 seconds later.
Another thing I don't know is whether the size of each thumbnail is the same.
In the NAS, the covers are obviously all different, but in general all very large and in high resolution.

Regards
v

[Tim Curtis]

There is a setting for Thumbnail resolution in Preferences. If or example it's set to 600px then each thumbnail jpeg image will be a max 600px at jpeg quality 60. If the original cover image is <= 600px then no conversion will occur.

[Venerdi]

There is a setting for Thumbnail resolution in Preferences. If or example it's set to 600px then each thumbnail jpeg image will be a max 600px at jpeg quality 60. If the original cover image is <= 600px then no conversion will occur.

Yes, I had seen the choice. The option I entered is "AUTO".
The covers contained in the NAS are all > 1000px X 1000px, and I don't know with "AUTO" how they become...
I have read the description; it says "Uses the device Pixel Ratio to set an optimum resolution and quality", but what happens? 400px? 500px? 600px?
If I set the value to 600px, should I do the Thumbnail regeneration?

[Tim Curtis]

Yes, the thumbnails need to be regenerated when changing the resolution.

The Auto setting does the following, from the source code.

Code:

// Auto: Uses the device Pixel Ratio to set an optimum resolution and quality while maintaining the smallest file size (fastest image load time).
// NOTE: Manual should be used for Desktops
/*
Device        Physical    Pixel    Logical
            Res (px)     Ratio    Res (px)
---------------------------------------------------
iPhone 3g    320×480        1        320×480
iPhone 4s    640×960        2        320×480
iPhone 5    640×1136    2        320×568
iPhone 6    750×1334    2        375×667
iPad 2        768×1024    1        768×1024
iPad 3        1536×2048    2        768×1024
Samsung GS3    720×1280    2        360×640
Samsung GS4    1080×1920    3        360×640
iMac 27"    2560x1440    1        2560x1440
iMac 27" R    5120x2880     2        2560x1440
*/

if ($hires_thm == 'Auto') {
    if ($pixel_ratio == 2) {
        $thm_w = 200;
        $thm_q = 75;
    }
    elseif ($pixel_ratio >= 3) {
        $thm_w = 400;
        $thm_q = 50;
    }
    else {
        $thm_w = 100;
        $thm_q = 75;
    }
}
// Manual: Use the specified resolution and quality factor.
else {
    $hires_thm_wq = explode(',', $hires_thm);
    $thm_w = substr($hires_thm_wq[0], 0, 3); // The numeric part ex: "400" from "400px"
    $thm_q = $hires_thm_wq[1];
}

[Venerdi]

I am not able to understand the code well, but I understand that since I use a desktop, it is better not to use "Auto".

Thanks Tim