12-29-2020, 03:40 AM
@TheOldPresbyope
It's a Pixel 4a, non-5G, via the Chrome browser. Everything up to date, but very very slow.
It's a Pixel 4a, non-5G, via the Chrome browser. Everything up to date, but very very slow.
Thank you for your donation!
Cloudsmith graciously provides open-source package management and distribution for our project.
|
Official moOde 7.0.1 support thread
|
12-29-2020, 01:53 PM
(12-29-2020, 03:05 AM)TheOldPresbyope Wrote: @oculto Both Digi+ (RPi 3A+) and Digi+ Pro (RPi 3B+) work for me running 7.0.1 Marc
12-29-2020, 01:54 PM
(12-29-2020, 03:40 AM)Evil_Underlord Wrote: @TheOldPresbyope This reminds me that there have been ongoing differences in behavior between Chrome and Firefox browsers on Android phones. I expect it's down to their Javascript engines but no smoking guns have appeared using the browsers' dev tools. (Pure conjecture since I have nothing to do with frontend development.) What happens if you try Firefox on your Pixel 4a? In truth I rarely use my phone these days for anything but phone calls and texts now that I have my iPad. It's so much more comfortable to use for reading and for dealing with multimedia. Also, out of curiosity, how many tracks are in your library? There's not hard and fast rule but big (multiples of 10K) libraries seem to bog down the interface, at least for some devices. Regards, Kent 
12-29-2020, 03:17 PM
(12-29-2020, 01:53 PM)jmarcusg Wrote:(12-29-2020, 03:05 AM)TheOldPresbyope Wrote: @oculto Here also no issues with a clean 7.0.1 on Pi2b with a Hifiberry Digi+ Pro. You can check if the modules are loaded with the following command: Code: lsmod | grep wm8804Should return something like: Code: pi@moodedev:~ $ lsmod | grep wm8804Notice the wm8004 drivers; the driver for HB Digi+ Pro are loaded. Else look in the output of the command dmesg for drivers issues.
12-29-2020, 11:10 PM
Guy’s, thank you for the attention with this case. I will try again son and post here more details.
BTW, the board i use is a generic chinese hat, with uses dtoverlay=hifiberrydigipro (i spell wrongly because i don’t have it with me now, but i will check the correct dtoverlay on raspbian) And with this dtoverlay it works flawlessly. The last time i try, the problem occurred after i set the driver and reboot. But before that, i also set the mpd parameters. I will check it latter. Please inform what logs have the information needed to be properly addressed here. I will post it.
12-29-2020, 11:50 PM
(This post was last modified: 12-30-2020, 12:06 AM by oculto.
Edit Reason: mistake
)
* * * update: i post a mistake here - the log bellow is using HIFI Digi+ but I already set the correct driver dtoverlay=hifiberry-digi-pro * * *
I few this i found on log... Code: 20201228 132002 worker: -- Devicecomplete log.... Code: pi@moode:~ $ moodeutl -l
I think I found the problem.
pi@moode:~ $ aplay -l aplay: device_list:272: no soundcards found... for some reason, the card is not recognized, but it work with raspbian and dtoverlay=hifiberry-digi-pro (but not work on moode) ![[Image: HTB1Cu0ERVXXXXbLapXXq6xXFXXXP.jpg?size=2...8412a8485d]](https://ae01.alicdn.com/kf/HTB1Cu0ERVXXXXbLapXXq6xXFXXXP.jpg?size=219844&height=533&width=800&hash=fed4981a7971718c89d5e48412a8485d) Code: dmesg | grep wm8804
12-30-2020, 01:21 AM
no luck for me. Try to install the AOIDE driver, update moode sqllite db to offer AOIDE driver, it works fine but the card still not recognized. I tomorrow will try to rollback to 6.7.1 to see if it works
 (12-24-2020, 05:39 PM)Tim Curtis Wrote: The code now handles multiple occurrences of Genre, Artist, Performer and Conductor tags and considers Artist, Performer and Conductor as all being "artists" which they are. This approach supports Classical collections which are often tagged with multiples, and it still supports Pop collections which normally only have a single Genre, Artist, AlbumArtist tag. Hi Tim, Took a while to get back to you having to find time after Christmas and work duties to look into this a bit further. These albums will likely have been at some point EAC rips with cue sheets and I decided some years ago to split them all into tracks and ditch the cue sheets, the metadata in those cue sheets probably came from CDDB and the tools/scripts I used to split and tag the files en masse would have populated whatever was in the cue files, including the performer tags. I've sorted the problem at my end, using metaflac I identified all the tracks with matching artist and performer tags (21195 of them!) and removed the performer tags without altering the file modification dates, turns out they were the only files I had that had performer tags so all is well. Still I will put it out there that I don't think that's really the right way to handle album artists, I can see what you mean by looking in playerlib.php that the code is creating an array of artists tags if there are multiple artists under the same album and if the array contains more than one value then set album artist to Unknown AlbumArtist if there's no Album Artist tag and that's fine. But as it's now adding the values of the performer and composer tags to the artist array, if a composer or performer tag exists at all (even if they're the same as artist) the artist tag is no longer used as the album artist in the absence of an album artist tag and I think that's having an effect that was not intended. Code: 455 for ($i = 0; $i < $linecount; $i++) {The performer tag is a valid tag as is conductor, and in the context of classical music or audio books these are more likely to exist and be different to the artist tag and the same is likely to occur. Shouldn't have to add an Album Artist tag if the Artist string is the same on all tracks regardless of any other tags. In the case of audio books it's less likely to be an album at all, often a book or other spoken word audio file is a single file so overriding artist for Unknown AlbumArtist if performer exists doesn't make sense. Whilst Album Artist is useful and required if an album contains tracks from multiple artists it isn't mentioned as one of the minimal proposed tags in the Vorbis specs, yet artist and perfomer is and the different contexts described. https://www.xiph.org/vorbis/doc/Vorbis_I...860005.2.2 Anyway thought I'd put it out there in case this bites anyone else. By removing the performer tags in my collection and regenerating the database I no longer have 1600+ albums showing up as artist unknown and they're again listed against their artist tags.
12-30-2020, 12:51 PM
(12-30-2020, 10:02 AM)Pjotr Wrote: Thank You the new version. The UI is very nice and I love the cover art in folderview. With 7 we switch to the more common Q factor. Where Qneweqp = 0.5 / BWoldepq. |
|
« Next Oldest | Next Newest »
|
