(05-01-2020, 01:37 PM)TookaFace Wrote: For the second issue i can't repro when playing a radio, only title with artist and album taking 2 lines.
For the first issue, maybe an Android thing, i can repro everytime in my case, will try different mobile when i could.
I thought I had reported seeing both issues on my Android Pixel 3A phone during testing, but maybe I was just muttering to myself again.
I paused play of Sonic Universe while on a track with a long title split into three lines.
Android Pixel 3A/Chrome (393px X 736px) - the top of the prev/pause/next button bar overlaps the bottom of the 3rd title line
Android Pixel 3A/Firefox (396px X 685px) - the top of the button bar is separated from the bottom of the 3rd title line by approximately the same amount as the top of the 3rd line is from the bottom of the 2nd.
iPhone 11/Safari (414px X 719px) - same, bar does not overlap
iPhone 11/Chrome (414px X 722px) - same, bar does not overlap
IIRC sometimes I saw an overlap in Android/Firefox but not this time.
The viewport dimensions are as reported by whatismyviewport.com.
It's a wonder to me you CSS jockeys can manage all the screen sizes and aspect ratios as well as you do. Glad I'm not a frontend designer!!!
(05-01-2020, 07:45 AM)fdealexa Wrote: Good morning to everybody,
I would like share with you some issue that could be not a problem but I think not normal:
1. during reboot I see an error on the screen (see Errore reboot): this is the LOG:
Raspbian 10.3 | 4.19.115-v7+ #1305 | armv7l (32-bit)
moOde audio player
Release 6.5.1 2020-04-27
(C) 2014 Tim Curtis
The programs included with Moode are free software; the
exact distribution terms for each program are described
in the individual files in /usr/share/doc/*/copyright.
Moode comes with absolutely no warranties expressed or
implied, or any other guarantees.
2. after several regenerate of the MPD i cannot see anything in TAG view or in ALBUM view (see Attachments)
3. Normali the MENU on top right is composed of 9 items and the configuration submenu is complete. After a configuration (for example library) the MENU on top right is composed of 6 items and the configuration submenu is not complete (see attachment)
I assume that you are so busy on other bigger problems, but I would like understand if I am in trouble on something.
Thank you very much and best regards,
Francesco
The log shows what appears to be invalid primary DNS entry and domain. Also, home Routers typically don't use a 172.21.200 address space. That seems odd.
Code:
20200501 083554 worker: IP addr (172.21.200.223)
20200501 083554 worker: Netmask (255.255.255.0)
20200501 083554 worker: Gateway (172.21.200.1)
20200501 083555 worker: Pri DNS (8.8.8.8)
20200501 083555 worker: Domain (85.37.17.51)
Typically primary DNS address should be same as Gateway address and point to the LAN interface of home Router. The Router then proxies all DNS requests.
Configure your Router DHCP service to hand out addresses where primary DNS is set to 172.21.200.1
Tim, thanks for the reply but I am sure about the network configuration: it is a LAN created under a firewall (.1) if I use the DHCP the result is the same (.38 instead of .223). I never had problem with (for example) upgrade, NAS connection, etc. The main difficult is that I can see (and listen) all the content of my library, only browsing the NAS: Directories, Files, or through search (not album, not tag views).
(05-01-2020, 04:45 AM)TheOldPresbyope Wrote: I'm still not sure I get it. What would be the expected screen display for a podcast?
When I feed duracell80's sample .m3u file to VLC, it starts playing the first "song" and displays the duration and title it grabs from the corresponding #EXTINF line. Isn't that what moOde is trying to do, putting aside the known seekbar issue? The only thing extra I see is the "Streaming Source" label which is kinda true.
The bottom line for me is that these podcasts are neither fish nor fowl when streaming so it's not surprising they are an edge case.
I wonder what happens if the URL in the .m3u file resolves to a file on a real file server?
Regards,
Kent
Probably a debate for a different thread for how to display a podcast, I was providing a playlist of MP3's that have known duration's that works with the current Moode player without having to modify it (it's just a playlist file that points to a number of files, a "radio station" has one file, a podcast has several "station urls" that are known as "episodes", it's still radio just on demand). But yeah -1 is very common as a duration to indicate radio streaming or "live" online radio. It would be awesome if the pause button in radio was actually pause not stop, so that the station carried on streaming, say if you take a phone call, you can resume from a buffer or skip backwards to listen to the song again.
But anyways there's merit in providing a Podcast folder for "streaming MP3's", even if there's no music involved. We have talk radio without music?
I was noting that 6.4 handles a playlist item with a duration fine and 6.5 doesn't.
I use podget to download podcasts to my NAS and manage them. Easy enough to do. A GUI to manage podget would be great, but I haven't the time to do one, alas.
(05-01-2020, 03:37 PM)Tim Curtis Wrote: Open Library Config and clear the library tag cache.
Thanks Tim, I have already done it several times and I have done it again for your information: see attachments.
Could it be a too large library (more than 30,000 albums)?
Thanks again for your patience.
Regards,
Francesco
(05-01-2020, 05:00 PM)Tim Curtis Wrote: Probably the size of the collection is causing a memory or buffer limit to be exceeded.
You could try doubling the MPD output buffer.
Code:
1. sudo nano /etc/mpd.conf
2. Change the output buffer limit
Change
max_output_buffer_size "131072"
To
max_output_buffer_size "262144"
3. Ctrl-x y return
4. sudo systemctl restart mpd
Then monitor the mpd log for errors after submitting a database update
Code:
1. mpc update
2. tail -f /var/log/mpd/log
I have tried but no good results. now i have deleted 3 of the 4 shares and it works fine. The problem is the large amount of material.
Do you think we can try to solve all the actions? Another thing (sorry) where is the buffer located? I see how much it increases and therefore we can try to optimize the correct size.
The TAG view is wonderful: my compliments.
