Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - garretwilson

Pages: 1
1
Questions / Re: search should be insensitive to marks
« on: July 22, 2018, 06:15:27 PM »
I apologize for posting a bug report in the wrong forum. It wasn't immediately obvious to me that there were separate sections for questions and bug reports. Frankly most projects nowadays don't even use forum software for bug reports; everyone has pretty must standardized on GitHub or JIRA, which is why I wasn't familiar with the particular process here. Anyway, that's just a suggestion. In the future I'll try to be careful to see which subsection I'm posting to.

I see that this feature has been enabled in MusicBee 3.2, and it is really great!! This means I can finally start using MusicBee as my primary music player. Thank you very much and good luck with the program.

2
Questions / Re: hotkey to focus on search filter
« on: July 22, 2018, 06:07:46 PM »
That is so great!!! Thank you very much for letting me know. This actually makes a huge difference in usability.

3
Questions / search should be insensitive to marks
« on: July 14, 2018, 05:01:23 PM »
The search field should find titles and such without regard to marks. For non-English words it makes MusicBee hard to use.

For example, let's say I want to find all songs by "Maria Bethânia" (an all-time popular singer of Brazilian roots samba). If I type "maria bethania", nothing comes up; I have to make sure I type "maria bethânia", with the accent (which of course would miss any songs if someone accidentally left the accent off on a song's metadata).

Similarly if I want to find all songs in the genre forró (a popular style of music from the Brazil Northeast), I can't type "forro", I have to type "forró".

MusicBee already searches without regard to case. It should search without regard to marks as well. (MediaMonkey does this correctly, for example.) Doing so is no mystery; it is completely laid out in the Unicode specs; see UTS #10 § 1.1.

Another more efficient approach is to store special search fields in the database already normalized to NFD for example, with the separate mark characters removed. Perform the same normalization on the search text, and then you can efficiently compare the characters without worrying about case or marks. See UAX #15 § 1.2.

However you do this, it needs to be fixed. MusicBee shouldn't assume everyone using it is am American listening to music with only ASCII characters in the metadata.

4
Questions / hotkey to focus on search filter
« on: July 14, 2018, 04:49:20 PM »
I want to map a hotkey such as `Ctrl+K` (a common search/filter key combination) to focus on the "search" box in the top right-hand corner so I don't have to click on it with a mouse. (I don't want to bring up the "find" dialog".) How can I do that? I don't see anything in the hotkeys that looks like "focus on the search box".

5
Unfortunately the workaround doesn't fully work. It turns out that if I disable the play/pause key for just the MusicBee app, then play/pause works when MusicBee has the focus, but I get the double recognition (play then stop or stop then play, as described above) if another windows has the focus.

But if I disable the media play/pause key for all applications, then I can no longer use the key for other applications, such as VLC media player.

I tried going into MusicBee and setting play/pause to not be global. Then I disabled the play/pause key in the Microsoft Mouse and Keyboard Center, just for the MusicBee app. Now the same thing happens: I can use play/pause within MusicBee, but when another has the focus, I get the double-input problem.

I don't understand why MusicBee can't fix this, if other applications such as MediaMonkey don't have this problem.

6
I can confirm that with the Natural Ergonomic Keyboard 4000, the workaround of disabling the Play/Pause button fixes this problem. Moreover Microsoft Mouse and Keyboard Center seems to allow me to disable the key just for the MusicBee application.

But I wish this could be fixed in MusicBee itself. MediaMonkey doesn't seem to have this problem, for example. Is this a MusicBee bug?

Pages: 1