Recent Posts Total Posts: 143800

Pages: 12 3 ... 10
1
Questions / Re: Japanese characters show up as empty boxes
Last post by Comexs on Today at 06:24:32 AM   |  Started by mysterioustrumpet
Quote
Ah, it turns out the Tahoma font doesn't support Japanese characters for larger text/headers?
switched to Yu Gothic and now it feels like I'm back on windows, finally

I tried to switch to Yu Gothic but every time I switch to it a get a error
Code
The selected font is not a valid font for MusicBee (the selected font needs to be a TrueType font)
2
Visualizers / Re: Milkdrop Visualiser Support
Last post by musicbee4dwd on Today at 03:16:39 AM   |  Started by Steven
I just did my version with screenshots and works with very old winamp versions: https://getmusicbee.com/addons/visualizer/386/milkdrop-2/

Beautiful. I was still using the other update. Your update is gorgeous. A couple quesitons:

(1) How can we access individual visualizations?
In MB, it just shows the Milkdrop2 folder, not the individual visualizations.

(2) Where are the settings located, such as time to move to next visualization, speed, etc.?
3
MusicBee Wishlist / Re: Improved Search Box search syntax
Last post by Tybot on Today at 12:29:12 AM   |  Started by Beezmann
I wouldn't mind seeing this suggestion implemented in some shape or form, mainly due to the fact that my search preferences vary greatly depending on whether I'm managing music or just listening to it. I see this as a way to bring the power of a custom search into the convenience of using the regular search box.

+1
4
Visualizers / Re: Milkdrop Visualiser Support
Last post by raul on May 20, 2022, 09:58:09 PM   |  Started by Steven
I just did my version with screenshots and works with very old winamp versions: https://getmusicbee.com/addons/visualizer/386/milkdrop-2/
5
Bug Reports / Re: Year field stops being directly editable in Playlist view.
Last post by Beezmann on May 20, 2022, 09:28:46 PM   |  Started by Beezmann
Pretty sure this is not a bug as it's working fine for me both in the main collection and in a playlist.
Have you enabled Preferences > Tags (2) > tag handling > enable direct editing of tags in the main panel?

Thanks for the quick reply and test. I knew that it might have been an issue with my skin, plugins, and so on, so I downloaded the latest version from the website and ran in through a sandbox before posting. After your "this is weird!" post, I did some additional digging and realized the source of the problem. There are two separate fields, "Year (xxxx)" and "Year". You most likely tested the Year one, since I just checked and it's editable everywhere. I was using using Year in my regular views and Year (xxxx) in the playlist view, and since the fild was sized too small to see the "(xxxx)" part of its description, I didn't realize that I was using two different fields...

Anyway, it appears that "Year (xxxx)" isn't editable at all, most likely by design. I'd still prefer it to be editable since I like to just use years and disregard the days and months, but that's obviously not true for everyone and the editing was likely disabled to prevent accidents. The solution for people like me is to change the non-editable field to the editable one, which I just did.

Thanks again for helping me figure it out as it was driving me nuts. You can just lock the thread and sorry about the confusion.
6
Bug Reports / Re: Year field stops being directly editable in Playlist view.
Last post by phred on May 20, 2022, 08:41:44 PM   |  Started by Beezmann
Pretty sure this is not a bug as it's working fine for me both in the main collection and in a playlist.
Have you enabled Preferences > Tags (2) > tag handling > enable direct editing of tags in the main panel?
7
Bug Reports / Year field stops being directly editable in Playlist view.
Last post by Beezmann on May 20, 2022, 07:56:38 PM   |  Started by Beezmann
The "Year (yyyy)" field stops being directly editable in the Playlist view.

Severity: very low.

Steps to recreate:
1) create a playlist
2) try editing any "Year (yyyy)" field value (at least non-empty one) by either clicking on the value twice or clicking it once and pressing F2. It won't become editable like it usually does.

The reasons why it's likely a bug:
1) The Year field is perfectly editable in other views like Music or Folders.
2) Other editable fields are still editable in the Playlist view, at least the ones I use.
(From what I use, only Title, Artist, and Album are always editable. Other, less common fields may be affected by the same issue as well.)

Tested in 3.5b (3.4.8033 P) and freshly installed 3.4.8033. My apologies if this has already been reported–I haven't found it in my search.

P.S. If you ever decide to address this, please consider making currently uneditable Track Gain and Album Gain fields editable as well while you're at it.
8
General Discussions / Re: Default Hotkeys
Last post by phred on May 20, 2022, 07:43:18 PM   |  Started by phred
Thanks psycho. It's up-to-date with version 3.0.5903, which was issued around May of 2016.

I have copied it into Notepad++ for future (offline) reference. It would be great if Steven could comment on any that have been added since that point.
9
General Discussions / Re: Default Hotkeys
Last post by psychoadept on May 20, 2022, 06:44:02 PM   |  Started by phred
I haven't checked recently to make sure it's still accurate, but I know I put one on the wiki when I made that page.
10
MusicBee Wishlist / Re: Improved Search Box search syntax
Last post by psychoadept on May 20, 2022, 06:42:46 PM   |  Started by Beezmann
introduce users to the shortcuts (that also applies to the existing ones–I'm sure many users don't know about them) would be in the Set Search Fields popup, via either tooltips (preferable but more work) or a simple field name text edit

+1 to this
Pages: 12 3 ... 10