+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Official moOde 6.5.0 support thread (/showthread.php?tid=2417)
RE: Official moOde 6.5.0 support thread - Tim Curtis - 04-26-2020
You haven't posted the requested error messages from MPD log so how do we know what's really happening?
http://moodeaudio.org/forum/showthread.php?tid=2417&pid=19119#pid19119
RE: Official moOde 6.5.0 support thread - Dradder - 04-26-2020
(04-26-2020, 03:48 AM)Tim Curtis Wrote: You haven't posted the requested error messages from MPD log so how do we know what's really happening?
http://moodeaudio.org/forum/showthread.php?tid=2417&pid=19119#pid19119
At this point in the discussion, I don't really care whether you know what's really happening or not. I haven't posted those requested error messages because I'm not proficient with Linux -- I never use it, and have no experience with it -- so your instructions in that regard were pretty unhelpful to me. So all I've done in this thread is report what my experience with the latest Moode 6.5.0 has been, which I had thought was the purpose of this thread. And that experience is that MPD crashes in post-6.2.0 Moode versions rather than correctly databasing a large multi-terabyte collection of music files, the way previous Moode versions such as 6.2.0 were capable of doing -- which of course is why I'll continue to use Moode 6.2.0 rather than trying to migrate to a later version such as the new Moode 6.5.0. If that information I've provided is helpful in your further development of Moode, then great; if it isn't -- well, sorry, that's all I've got.
IMO, Moode is a great program -- really the best of several that I've tried on a Digione Signature Player -- and I'll continue to use the 6.2.0 version of it, as it works very well for me. And I'll download and install and test out subsequent Moode versions, to see if the problem I've had with previous post-6.2.0 versions has been resolved. If it has been resolved, then great, I'll likely migrate to that new, improved version; if not, I'll continue with Moode 6.2.0, which works for me. But frankly, this discussion has taken on an unfortunate combative tone, which I find unpleasant. So I think I'll just sign off for now -- best of luck & more power to you.
RE: Official moOde 6.5.0 support thread - DRONE7 - 04-26-2020
(04-26-2020, 04:23 AM)Dradder Wrote:(04-26-2020, 03:48 AM)Tim Curtis Wrote: You haven't posted the requested error messages from MPD log so how do we know what's really happening?
http://moodeaudio.org/forum/showthread.php?tid=2417&pid=19119#pid19119
At this point in the discussion, I don't really care whether you know what's really happening or not. I haven't posted those requested error messages because I'm not proficient with Linux -- I never use it, and have no experience with it -- so your instructions in that regard were pretty unhelpful to me. So all I've done in this thread is report what my experience with the latest Moode 6.5.0 has been, which I had thought was the purpose of this thread. And that experience is that MPD crashes in post-6.2.0 Moode versions rather than correctly databasing a large multi-terabyte collection of music files, the way previous Moode versions such as 6.2.0 were capable of doing -- which of course is why I'll continue to use Moode 6.2.0 rather than trying to migrate to a later version such as the new Moode 6.5.0. If that information I've provided is helpful in your further development of Moode, then great; if it isn't -- well, sorry, that's all I've got.
IMO, Moode is a great program -- really the best of several that I've tried on a Digione Signature Player -- and I'll continue to use the 6.2.0 version of it, as it works very well for me. And I'll download and install and test out subsequent Moode versions, to see if the problem I've had with previous post-6.2.0 versions has been resolved. If it has been resolved, then great, I'll likely migrate to that new, improved version; if not, I'll continue with Moode 6.2.0, which works for me. But frankly, this discussion has taken on an unfortunate combative tone, which I find unpleasant. So I think I'll just sign off for now -- best of luck & more power to you.
Dradder... I'm sure had the user community known earlier you were not proficient in computing and especially unfamiliar with Linux then any one of us would have been happy to walk you through with baby steps....and still would be
I have read back through the thread and see nothing 'combative'.... I understand you are frustrated and feel helpless.. We all are going through tough times with the worldwide lock-down and I find myself obsessing over little things I would otherwise be more accommodating about.
The devs have asked for information to help assess the difficulties you are experiencing and it seems they are eager to help once given that info and being able to repro it.
I'm happy to help with the linux commands you need to run...pm me if this would be useful for you. (note they can be run easily from within moOde...you do not need any other Linux
)Best,
Bob.
RE: Official moOde 6.5.0 support thread - vinnn - 04-26-2020
So to pull back the thread from the change averse types... loving the UI update, better overlays, seems cleaner and more fat-finger friendly with the migration of the smallest buttons (which could be fiddly on small screens) to the new nav menu. Well done guys, there's clearly a lot of thought and effort that has gone into 6.5.0 and it works very well.
Special thanks for the new Show Tagview covers appearance option, when set to No the Tag view render time is further improved, faster than the UI.tagViewCovers hack on 6.4.x with my ~9000 album library.
One minor thing I should point out is that when this option is selected the album column spacing is different to the other columns.
[attachment=1187]
Thanks again.
RE: Official moOde 6.5.0 support thread - TookaFace - 04-26-2020
The new update library feature works very well aswell, very straightforward
RE: Official moOde 6.5.0 support thread - jonners - 04-26-2020
If I mute and then unmute, the volume goes to 100!
Pi3b+, Terraberry DAC.
Edit: Same issue on my other system, Allo USBridge Sig, Katana DAC.
RE: Official moOde 6.5.0 support thread - vinnn - 04-26-2020
(04-26-2020, 08:49 AM)petfr Wrote: I'm back at Moode 6.4.2
First of all I would like to apologize for my bad (google) english! I use the official 7 "touch display. The installation of the new version went so far smoothly. The reason is change or reduction of the volume ring in the main window (see attachments). In particular the position of + and - is for me a significant deterioration compared to previous version. It happened to me several times now that I ended up at 100% when changing the volume. This is not healthy for my speakers! Is there a way to enlarge the adjustment ring again?
Greetings from the south of Germany
Peter
Hi Peter,
Seems as if the font has changed in 6.5.0 for the numbers in that view and your tablet is rendering it differently to the other font.
This actually seems to be caused by the Android settings on your tablet, I've been able to replicate your issue on my tablet by changing Android's View Mode in [Settings] > [Display] from the default to Large (probably different name/location on different versions of Android).
This setting magnifies all the icons and fonts in the home screen and supported apps and makes moOde look like what you've posted there.
Try putting your tablet's display settings back to the default View Mode and font size and see if that fixes your issue.
RE: Official moOde 6.5.0 support thread - TookaFace - 04-26-2020
(04-26-2020, 09:07 AM)jonners Wrote: If I mute and then unmute, the volume goes to 100!
Pi3b+, Terraberry DAC.
Edit: Same issue on my other system, Allo USBridge Sig, Katana DAC.
Yes for me too
RE: Official moOde 6.5.0 support thread - moodenigo - 04-26-2020
(04-25-2020, 08:57 PM)swizzle Wrote:(04-25-2020, 12:37 PM)The moodenigo Wrote: Second, the not-so-good-news: Now the option so update the thumbnail cache is gone. I can only regenerate? Why?
The thumbnail cache now updates automatically when you update the mpd library.
I see. I am not 100% sure this is optimal but I understand the rationale for removing the option. It actually reduces the steps I have to do, so even according to my principles it is better ;-) I did not say one should not update the thumbnail cache when the mid library is updated. I just said that the option for refreshing the thumbnail cache should be there, if nothing for the cases where it somehow gets corrupted (it happened to me with my large library).
Quote:Quote:Introducing the "adaptive UI" with the playlist "rising up" from the reduced version at the bottom has been difficult to digest, because it increases the number of steps to go from playlist to file browser or library browser from one to two: first collapse the view, then choose the type of library view. This was bad and until 6.4 I found it painful.
The file browser is a library view and how often do you actually switch between them? Most people stick to one (with the exception of maybe the radio browser). Moode since 6.x remembers where you last left off so you can toggle between the full screen playback and the library view you use with one click without wasting space on a navbar a la moode 3.x.
Some users switch between various views frequently. I am sure I am not the only one. I guess I can live with this as well.
Quote:Quote:Now there is no visual cue. I have to guess that clicking on the cover art will lead me to library view – this absolutely makes not sense, it is not intuitive
There was some debate about this but this is the kind of thing you learn once and then you know it. It’s like the little text on your side mirrors about objects being closer than they appear, useful the first time but forever after just in the way.
No, the is completely illogical and makes no sense. If there is one thing to change is this one. Repeat after me: You have to click on the cover art to go to library view. You have to click on the cover art to go to library view. You have to click on the cover art to go to library view.
This is one of the things it is actually worth "wasting" screen real estate for.
Quote:Quote:AND, to add more lack of intuitiveness, one must choose the view from a button.
It’s a menu actually.
A drop down menu is always attacked to another UI element, in this case a button. I have done UI design in the past.
Quote:Quote:The approach that was there in 3.x (4.x as well IIRC) was: there is a series of "tabs" and one chooses the right one. File browser / library browser / cover view / playlist. Like it is now for the configuration mode. This is the right way to do it.
It may be the right way for you, but this isn’t moodenigo 6.5.
Haha. I know.
Quote:As Tim said the move to the menu was needed because 1) screen space is precious and there isn’t enough room to do it like before if we add any new views ), 2) this lets us declutter the ui by moving some things to the menu (e.g. recently added).
I understand this as well. There should be a different solution though. Putting options on the side in the desktop view perhaps? A button on the left of the search field or of the "m" menu?
Quote:Quote:At the moment I am sticking with moOde only because I do not have to pay for an equaliser (and the parametric one should really have more than 4 bands, since this makes the use with, say, REW, impossible).
Moode is a passion project for Tim and we’re lucky that he’s demented enough to put as much time into it as he does, but reminding him that the only reason you use it is because you don’t have to contribute anything back to the project probably isn’t the right way to win him over with regard to any requests you may have.
I understand, but I want you to understand that there are small issues (and that can probably be easily mitigated) that affect UX significantly. The thing that really sticks out is "click on the cover art to go to cover view" which is a "SRSLY?" thing each time I have to do that.
Quote:Quote:Please reconsider very seriously the insertion of a navigation bar, and restore the ability to go to a "large cover" view of the playlist by clicking on the cover art.
We got rid of the navigation bar on purpose. Most modern music software (e.g. Spotify, Tidal, Roon, etc.) has adopted a similar interface design language and that makes interoperability easier. You’d have to explain what a “large cover” view of the playlist is.
These pieces of software also go to the library upon clicking on the cover view? This is counterintuitive, and there is no reason for following them if they do stupid things.
Quote:Quote:UX is not about changing the UI to make it "cleaner" and new fonts. It is about the actual useability of the UI.
The only font difference is the use of monospace in the dials now iirc. A less cluttered UI is inherently easier to use though it isn’t necessarily easier to do what you want if you get the distinction. You could say moode lacks discoverability in some areas and I’d agree with you but any software has a learning curve and after the first time insisting on having a separate button to press instead of using the much larger cover seems pedantic.
Come on, the fonts comments was just an example.
Yes, I claim lacks moode lacks discoverability in some areas. Discoverability is fundamental in modern UI design. Otherwise we would have only extremely uncluttered views with random operations to go from one mode to the next. This should be improved a bit.
All software has a learning curve but we should not increase it artificially. Otherwise we could just say a CLI is ok for all users, they just have to learn.
I know I sound pedantic, but fact is, I do not really see the logical connection between the cover art and the library. One could indeed claim that the library is where one "browses" the albums looking at their covers, as in an old fashioned record collection. But with ally good will I cannot persuade myself that this makes sense.
I agree that moOde looks beautiful and that aspect has improved with each release. But this should not be the only rationale or a UI choice.
Quote:Quote:(also configuration should NOT need an extra click either, you just go to the last used higher level pane, without the intermediate selection of Audio/Library/Network/System).
The problem with that are the quick link buttons to e.g. mpd configuration or eq settings. While I personally don’t use them and have contemplated removing the dialog as well but ultimately this isn’t swizzle 6.5 either.
I understand. I suggest to reconsider removing that. It is, to be pedantic, repeating myself, an inconsistency. Different part of an application should behave similarly, unless there is a very strong reason to do otherwise. Which I think is missing in this case. The Library does not have such a dialog (and it is obvious, I believe, that it would be wrong to have one) – hence Configuration should also not have one.
Quote:As an aside: elements overlaying the album cover on the playbar was a mobile only thing at first because there I wanted to improve the spacing of the playbar and make the text bigger and there isn’t enough room otherwise (so this is unlikely to change there unless we just get rid of the cover) but it migrated to the larger screen version (and the controls flip-flopped) because around the same time Tim got into Amazon HD and liked how the setup worked there (though iirc they use hover to show the controls which we can’t really do because of touch devices).
I understand, but one should not have a overlaying element for the search. It is done in forums because this leads to a different page, but not here.
I slept over this and I have come to the conclusion that
- Adding a little button to go to library view near the search field or the "m";
- Removing the dialog to enter configuration; and
- Removing the search from the Library menu in tag view and putting it next to the library drop down menu
I think the moOde concept is the best one among linux audiophile distros that run on the Raspberry Pi. I understand the need to rationalise the use of screen real estate. I am myself a person that likes to bring concepts to their extreme consequences - but not only for consistency - also to see where they can fail. In this case, I believe that pushing things to the extreme has failures.
BTW: where is the "large cover art" view now?
RE: Official moOde 6.5.0 support thread - moodenigo - 04-26-2020
(04-26-2020, 08:42 AM)vinnn Wrote: So to pull back the thread from the change averse types... [...]
Special thanks for the new Show Tagview covers appearance option, when set to No the Tag view render time is further improved, faster than the UI.tagViewCovers hack on 6.4.x with my ~9000 album library.
I guess I am the change averse type. I hope that my last reply shows I am not completely change averse – it is more about how the changes are done.
This said the Show Tagview covers option is a GODSEND for me. I have about 15000 albums and setting that option to "NO" makes the UI very very snappy. For this I am very grateful.
Roberto