@MusicHound,

yea just saw in fontforge that the glyph for the font does not exist, but you can change 'Segoe UI' to 'Segoe UI Symbol'.
First open your config file "foobar2000\profile\georgia-reborn\configs\georgia-reborn-config.jsonc" and go to the ( bottom of file )
"settings": { section. Look for "playlistCustomTitle": and "playlistCustomTitleNoHeader": change the pattern to something like this:
"%title%[ '('%original artist%' cover)'] $ifequal(%ITUNESADVISORY%,1,🅴,)"
Save the file.

Open your "foobar2000\profile\georgia-reborn\scripts\Playlist\main.js" file and change in line ~104:

Code: [Select]

const titleNormalFont   = pref.customThemeFonts ? customFont.playlistTitleNormal   : 'Segoe UI';
const titleSelectedFont = pref.customThemeFonts ? customFont.playlistTitleSelected : 'Segoe UI';
const titlePlayingFont  = pref.customThemeFonts ? customFont.playlistTitlePlaying  : 'Segoe UI';

to

Code: [Select]

const titleNormalFont   = pref.customThemeFonts ? customFont.playlistTitleNormal   : 'Segoe UI Symbol';
const titleSelectedFont = pref.customThemeFonts ? customFont.playlistTitleSelected : 'Segoe UI Symbol';
const titlePlayingFont  = pref.customThemeFonts ? customFont.playlistTitlePlaying  : 'Segoe UI Symbol';

If you use the default playlist font size, you need to also change it because the upper of the 🅴 is cut off:
Still in the same file ( main.js ), just some lines under your first change, i.e in function createPlaylistFonts() { line ~130:

Code: [Select]

title_normal:   font(titleNormalFont, rowFontSize),
title_selected: font(titleSelectedFont, rowFontSize),
title_playing:  font(titlePlayingFont, rowFontSize),

to

Code: [Select]

title_normal:   font(titleNormalFont, rowFontSize + 1),
title_selected: font(titleSelectedFont, rowFontSize + 1),
title_playing:  font(titlePlayingFont, rowFontSize + 1),

Restart foobar. If you've done everything correctly, it will display now the 🅴 in your track rows correctly,
when your tracks have a value of "1" with the %ITUNESADVISORY% tag.

-TT

Quote from: Irama on 2023-05-13 17:32:54

Using v. 2.0 (stable) or 2.1 beta (64 bits), interface is temporarily freezing on my side when I update tags, while music is still playing flawlessly. It can last from a few seconds (if I update tags of a single album) to a few minutes (for a bunch of albums using masstager) and everything will be fine again after all operations are completed. Meanwhile CPU usage is somewhere between 20 and 50 %. Same thing happens while new music is being downloaded and automatically scanned for being added in media library. My computer is "a bit" old (see specs below) and music library quite big.

This didn't happen with previous versions. I don't know anything about computing, but I guess this has something to do with foobar now being unable to forget new tag updates after crash (which is nice) and that this is not a bug but a consequence of choices made. Hence I'd like to know if there were ways to shorten this temporary freeze for old computers ran by old people like me... Any help appreciated!

Of course I use some components, mostly JScript Panel samples, but I guess they affect RAM more than CPU, and problems were similar without them installed.

Here's my configuration:

CPU   Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz   3.60 GHz
RAM   16,0 Go
Foobar on SDD
Music library (over 18,000 albums; 8 TB data) on 3 different supposedly healthy HDD
Windows 10

Coming back on this... It seems that foobar is rebuilding the entire library each time I make any change on the metadatas or doing anything else that could affect the library (adding an album for instance). It is pretty annoying since heavy changes can freeze the program for tenth of minutes. Tasks manager tells me that foobar uses up to 40 % of CPU ressources (usually 25-30 % and less than 1 % in normal use). I tried everything I could with Windows, such as giving foobar "real time access" with no results. I'm a bit desperate about this...

There's no way to edit it in the mobile and assuming that it is quite uncomfortable to edit things on a mobile phone, I don't think this is on Peter's top of his to-do-list.

There are fields for composer and the performer (=conductor) plus album artists.
If you have more than one, you can enter them comma-separated - that's at least what I do.

These fields are more or less commonly used by players, but you can also add your own, which won't get displayed in typical players.