Isn’t It TIME for some information about the New Firmware we are in final of MAY How hard can it be to give a date people are getting frustrated
Thats not the official, does it? The official is here: https://www.mcbluna.net/wp/eversolo/eversolo-model-overview/eversolo-dmp-a6-firmware-download/
Well, closer to four months if I can count, as the last official firmware was released at the end of January. No one is suggesting that the world is ending (well, not due to the lack of A6 firmware updates anyway ), but if one of the various bugs affects you then it is mildly annoying.
McBluna is not official but yes a highly valued enthusiast who only includes original images from the official source. He also provides tons of additional info not done by Zidoo/Eversolo themselves. Only can recommend the site as a reliable source.
Yes mate, I'm perfectly aware of that and that his links are to the official ones, it was just a matter of clarification and not intended against him in any way or form. In fact, I downloaded my first FW update from his site
Well, today a new version of the iOS app was released on AppStore -- still not a word on the impatiently awaited firmware update from the developers. This non-communication is really not acceptable!
Not a very long list of ‘changes’ but I’m glad to see that they might have done some work on the internal player…
Hi, It seems there is an issue in the now firmware. it says "Composer", but in the same list, I find the "Conductor" too for my classical music files. For exemple, in the composer list, I find Ludwig Van Beethoven, and Herbert von Karajan ...
It could be an error, of course. But are you sure none of the involved files have the CONDUCTOR name set in the COMPOSER metadata tag (that is: are your files correctly tagged? keep in mind that different tag systems - like id3v2 / APE / VorvisComment - use different tag IDs)
Are the files with the "error" of the same type / with the same TAG system? (all FLACS + VORBIS, or all MP3s + id3v2 I mean), because as I mentioned the different tag IDs for the conductor / composer / etc. could have mislead the devs; if we can find a pattern, we can also make life easier to the devs to correct the error...