DEV TESTING

[TT-ReBORN]

Important Update: As of 02 September 2025,

Georgia-ReBORN is transitioning to focus on 64-bit support for foobar2000.
The versions currently available on the Releases page
are compatible only with foobar2000 32-bit.
For the latest Georgia-ReBORN x64, download from the master branch.

---

For foobar2000 32-Bit ONLY:

All versions on the "Releases page" here:
https://github.com/TT-ReBORN/Georgia-ReBORN/releases
Are for foobar2000 32-Bit ONLY!

CURRENT VERSION: Third Release Candidate - Georgia-ReBORN v3.0-RC3: DOWNLOAD FROM HERE.

For foobar2000 64-Bit ONLY:

P.S Just a reminder for anyone who did not know, you can always download the master as you like.
If you go to the main page here and at the top click on the green <> Code button > Download ZIP.

---

Developers might be interested to take a look at the DEV CORNER thread here: #171

---

Posted issues that have been fixed, will be deleted to have a better overview of messages, thank you for the bug report!

Cheers

-TT

[erusapien]

[TT-ReBORN]

The Wizardium and its Wizards, Pure Dynamics & Georgia-ReBORN 64-bit: An Epic Unveiling After Eight Months of Arcane Craft

After eight months of relentless dedication, I proudly unveil The Wizardium — a legendary collection of standalone plugins forged to elevate the sacred realm of foobar2000—alongside the triumphant 64-bit rebirth of Georgia-ReBORN. This is no mere update; it is a monumental resurrection of tools designed to empower every foobar2000 user. Every line of code, every graphic, logo, and branding element is my own creation, weaving a cohesive, immersive universe under the banner of The Wizardium (The-Wizardium.org). Below lies the grimoire of this release, detailing each sacred chapter. Break the seals and claim your power.

The Wizardium: Anointed Of The Veiled Arcana

The Wizardium is the beating heart of this suite — a bespoke website and brand I crafted to unite these plugins in a visually stunning portal (The-Wizardium.org). Every logo, icon, and animated rune is my original design, conjured to evoke the mystique of the Holy Foobar Land. With intuitive navigation and a unified aesthetic, The Wizardium invites novices and adepts alike to explore, download, and master these arcane tools.

API Wizard: The Topaz Spell Of Automation Rituals

Sealed within the Topazurum Sanctum, API Wizard is a standalone plugin that unlocks foobar2000’s automation potential through a robust COM/ActiveX interface. It empowers JavaScript-driven control over playback, playlists, and settings, supporting both foo_uie_jsplitter and Spider Monkey Panel. As the backbone of Audio Wizard and UI Wizard, it offers comprehensive documentation for seamless scripting, from resizing windows to managing playlists. Released under the MIT License, API Wizard is a universal tool for any foobar2000 user to weave automation rituals.

• Key Features:
  • COM/ActiveX interface for JavaScript automation.
  • Supports registration-free COM via MinHook or traditional registry-based COM.
  • Extensive API documentation for scripting mastery.

Audio Wizard: The Ruby Spell Of Sonic Mastery

Blazing within the Rubynar Sanctum, Audio Wizard is a standalone plugin that conjures unparalleled audio analysis for foobar2000. Compliant with ITU-R BS.1770-5 and EBU TECH 3341–3343, it measures loudness (LUFS), peaks, and dynamics across 24 channels, with waveform visualization and real-time monitoring. Integrated with API Wizard for scripting, it introduces my novel Pure Dynamics metric—a psychoacoustic breakthrough that captures audio as humans perceive it. Released under AGPLv3, Audio Wizard is a universal tool for audiophiles and professionals, whether used with Georgia-ReBORN or standalone.

• Key Features:
  • Full-track and real-time audio analysis with customizable displays.
  • Waveform visualization and raw PCM audio access.
  • COM/ActiveX scripting via API Wizard.
  • Implements Pure Dynamics for perceptually accurate dynamic range.

UI Wizard: The Sapphire Spell Of Interface Enchantment

Glowing within the Sapphiraz Sanctum, UI Wizard is the official successor to foo_ui_hacks, a standalone plugin that transforms foobar2000’s interface with Aero glass effects, borderless designs, transparency, and snap-to-edge functionality. Built on API Wizard’s scripting capabilities, it offers dynamic control through a user-friendly preferences menu I designed. While crafted to support Georgia-ReBORN’s 64-bit transition, UI Wizard is a universal tool for any foobar2000 user to reshape their interface with elegance. Released under the MIT License.

• Key Features:
  • Customizable window styles, Aero effects, and transparency.
  • Snap-to-edge and window state management (Normal, Maximized, Fullscreen).
  • COM/ActiveX scripting for dynamic UI control.
  • Replaces foo_ui_hacks with enhanced functionality.

Pure Dynamics: The Psychoacoustic Flame

Embedded within Audio Wizard, Pure Dynamics (PD) is my revolutionary psychoacoustic metric, released under GPLv3. Unlike traditional metrics like DR or LRA, PD measures dynamic range through 12 principles—Zwicker loudness, binaural perception, transient salience, and more—delivering a single, perceptually accurate value in just 17ms at 60fps. Ideal for music production, live sound, and audiophile analysis, PD hears music as mortals do, making it a universal tool for audio enthusiasts. Its open-source nature invites the community to refine its arcane algorithm.

• Key Features:
  • Perceptually driven dynamic range measurement.
  • Real-time processing with 17ms latency at 60fps.
  • Adapts to genres and enhances stereo depth and transients.
  • Open-source for community-driven evolution.

Georgia-ReBORN: The Titan Reforged

Georgia-ReBORN 64-bit marks the triumphant evolution of a beloved foobar2000 theme, now fully compatible with 64-bit systems. This conversion replaces outdated components with the power of The Wizardium:

• foo_spider_monkey_panel replaced by foo_uie_jsplitter.
• foo_ui_hacks replaced by UI Wizard.
• foo_vis_vumeter and waveform tools replaced by Audio Wizard.

The result is flawless 64-bit compatibility, enhanced display detection, seamless maximize/fullscreen behavior, and faster waveform analysis. While Georgia-ReBORN harnesses The Wizardium plugins, each remains standalone, ensuring versatility for all foobar2000 users.

• Key Enhancements:
  • Improved display detection and UI behavior via UI Wizard.
  • Faster waveform analysis via Audio Wizard.
  • Eliminated outdated workarounds for a streamlined experience.

A Personal Odyssey of Art and Code

This release is the fruit of eight months of solitary focus—a fusion of complex C++ code and intricate graphic design. Every logo, icon, and visual element across The Wizardium and its portal is my original creation, crafted to form a unified, enchanting identity. From the animated runes of The Wizardium website to the bespoke logos for each plugin, my passion for art and code shines through every pixel and line.

Join the Fellowship

The Wizardium is open for all to use, customize, and enhance under MIT, AGPLv3, and GPLv3 licenses. The source code awaits your contributions on The-Wizardium.org. Join the fellowship and share your arcane insights, report mystical anomalies, or forge new spells. Break the runic seals, claim the spells, and etch your name in the annals of The Wizardium!

• Visit the Portal: The-Wizardium.org
• Commune with Scholars: hydrogenaud.io

The path is open. The sanctums await. Wield the power of The Wizardium!

[madindehead]

I'll give that a go and see how I get on.

Otherwise, I assume that georgia-reborn-config.jsonc contains all the relevant settings?

[silverwings15]

@TT-ReBORN please consider my previous feature request to have a way to pin the options menu so users can try out various settings without having to navigate back to them each time!

[TT-ReBORN]

@madindehead,
georgia-reborn-config.jsonc saves only the Georgia-ReBORN theme settings, but not your Playlists, Library, and Playcounts...
The Theme Backup feature does save everything for you.

[TT-ReBORN]

@silverwings15,
yes I know.

This is not possible with the menu framework, you would need to somehow hack it and it would look ugly, meaning save position of the mouse and then reopen the menu to the setting. Maybe it is possible, but maybe not. The cleanest way would be to make a new menu frame work, similar how the custom theme menu works...

But you can use the quick navigation in the right-click context menu for each panel and select the first panel options for panel options.

[silverwings15]

ah my bad i didn't know (or forgot) that it isn't possible

[Fizbin99]

This should probably be in github's Wizardium but I've never started a new discussion before, so I'll post it here...

1. CTRL-P (preferences) rarely works on bootup. UI Wizard is somehow blocking it. If you click on a panel and then hit CTRL-P it will work.

2. Windows 10 Auto Hide taskbar doesn't work. It stays hidden and never shows. (This isn't an issue with Reborn because it's always in fullscreen)

3. When the frame is set to Default and the window is maximized... What happens is if you minimize the window with "-" and then you click on the icon on the taskbar to bring the window back, it's minimized instead of maximized.

4. When toggling fullscreen via UIWizard.ToggleFullscreen(), and you exit fb2k while in fullscreen and reboot, it's no longer in fullscreen and it's also minimized.

[TT-ReBORN]

You are now in the annals of The Wizardium and in the Hall Of Honorable Scholars:
https://github.com/The-Wizardium/UI-Wizard?tab=readme-ov-file#hall-of-honorable-scholars

Official Release is here:
https://github.com/The-Wizardium/UI-Wizard/releases/tag/0.2.0

Need to keep The Wizardium branding alive, maybe I should write a fantasy novel LOL =)

[Fizbin99]

Congrats! Your hard work finally paid off.

[TT-ReBORN]

@Fizbin99,
bug reported here:
#74 (comment)

try this new version:

• Fixed window restore in maximized state for "NoBorder" frame style
• Fixed window maximize cosmetic fullscreen glitch in "NoBorder" frame style

foo_ui_wizard-0.2.1.zip

Please tell me it didn't break anything LOL!
Let's pray to God =)

[Fizbin99]

I just noticed this tonight. Is there any way this can be fixed in a future update? It's not imperative. IE: No rush.

https://youtu.be/0KjF8uA1IYg

[TT-ReBORN]

foo_ui_wizard-0.2.1.zip

Thanks, got that fix also in 0.2.1, I'll release it later officially on the repo =)

[LuigiGame3]

Prefixes to strip or swap is not working for me, any way to fix?

[TT-ReBORN]

I'll take a look!

[TT-ReBORN]

@LuigiGame3, this was actually already answered, take a look here:
https://hydrogenaudio.org/index.php/topic,121047.msg1018898.html#msg1018898

[TT-ReBORN]

@regorxxx,

just saw your posted issues on the Audio Wizard repo, did not get any notifications.
This entire Github notification system is bugged :/
I'll get to you when I have fixed the issues here and have more free time for the API stuff.
It will take some time because I am fixing bugs and at the same time designing the Pure Dynamics website =)
And yes I am not using points per second anymore but samples per second as it is better to handle internally in the audio processor...
And you are right it is clamped to 10-1000ms, did I forget to mention it in the docs?

-Tom

[regorxxx]

Replying to the issue about resolution there. The-Wizardium/Audio-Wizard#8

There is zero hurry, I was just trying to implement the component into the waveform script, so whenever it's done I will finish it :)

I had a few other bugs with the ui_hacks replacement, but I have seen it has been updated a few times... so I will wait some days and check again. Great work you did here heh!

[TT-ReBORN]

Yeah, I think this part of all docs is unclear, forgot to update it and make it clear, happens if you do 5 projects at the same time =)
Check:

Georgia-ReBORN/profile/georgia-reborn/scripts/Base/gr-main-components.js

Line 4590 in 9dcf37a

* @property {number} resolution - The temporal resolution in samples per second from 1-1000, recommended preset ranges are:

The entire waveform class has the implementation with the Audio Wizard, so you can check it entirely out.

Actually from what I remember ( did the waveform analysis implementation logic 3 months ago or so ) ffmpeg has default
20 samples/sec converts to 0.05 sec x 1000ms/second = 50ms, the rate at which analysis or visualization data is sampled.
I saw this on their source code on Github. This is easier and more intuitive for audio processing in general and also for me internally than using points/pixel per second.

Anyways, I need to concentrate on fixing user-reports here for now and finish Pure Dynamics website...
Later, we implement the playlist track batch processing without track selection etc...

[regorxxx]

It may be more intuitive for audio analysis, but for me its not useful when I'm trying to fit a waveform into a specific size.

I don't care about how many seconds/sample rate a track has, I just want X points (not px!) per second for any track. So I always know I have exactly X points of data for every second, no matter the duration or sample rate of the audio... and then I can easily draw a waveform into a specific width, knowing I'm just losing time precision since points need to be discarded. And the amount of points to be discarded is constant for any track and sample rate given a width and duration.

Note drawing a waveform for seeking is just UI candy, there is zero intention to analyze audio or have any precision on data for further analysis. I mean, even for most UI resolutions I'm already discarding data points because there is not enough player width to draw them all. Furthermore, it makes zero sense to have more than 4 (?) point of data for every second for this purpose. How are you going to paint that data in a waveform? Using less than 1 px for any standard track? I mean, a 2 min track is already around 500 points! Do you need more?

Anyway, my point was the current implementation doesn't allow to specifically get X points of data per second. I don't care which unit I has to input, that's fine, but nothing I did outputs the desired data despite your suggestions. It's supposed that if I set a 1000ms resolution, I would get exactly 1 point of data per second, but that's not true unless I'm missing something. If I set it to lower values, I get less points of data (not more!), so whatever you think you did there, it's not working as you say.

[regorxxx]

Georgia-ReBORN/profile/georgia-reborn/scripts/Base/gr-main-components.js

Line 4597 in 9dcf37a

* - 1 sample/sec: Minimum Details (1000ms, for ultra-minimal previews on very slow devices).

Also you say the minimum resolution is clamped to 10, but then your docs for the waveform you linked say otherwise. Which I presume is part of the problem here...

And... the argument is not really respected. Something internally changes the resolution for specific values:

So 20 is the same than 15 but then 10 halves the output length (?)

[silverwings15]

i need another sharp pair of eyes to verify this for me please to make sure i'm not imagining things

the 3.0 x64 version has fuzzier, less sharp text rendering and mini album art (in playlist view) compared to 3.0 RC3

[TT-ReBORN]

Seems to be the text rendering of the new JSplitter component, so it should be reported in the JSplitter thread on HydrogenAudio.
32-Bit used the original Spider Monkey panel component which we can not use due to not supporting foobar2000 64-bit.

[silverwings15]

can you forward my post there please? as i do not have a Hydrogen account

[silverwings15]

when the music library is empty, the placeholder text is also extremely pixelated. maybe also an issue with JSplitter?

[Zephyr0ck]

Hello Tom! It's great to see the progress and the level that Georgia-ReBORN has reached with this new x64 version and the incredible components you've developed. As of today, I have installed the latest available version of this new stage of Georgia-ReBORN.

I have a small error, so I'll go ahead and describe it.

• Screen: 1440x900
• Windows 11 Pro (24H2)
• Foobar2000 2.25.0

When the Foobar2000 window with Georgia-ReBORN is "Maximized" as usual, and I minimize it to the taskbar, when I click to show foobar2000 again, it appears in Fullscreen mode. I'm not sure what's happening; I'm attaching a video to show what I mean.

Thank you so much as always. I truly admire and appreciate all the effort you've put in since day one of this project, which has evolved in ways we could never have imagined!

Video_250917173739_Scc.mp4

[TT-ReBORN]

@Zephyr0ck, Hi Jose.

thanks for your kind words, but your timing on posting was bad =)
Actually I released UI Wizard 0.2.0 two days ago and now I see this issue here...
Damn, it is what it is... I am working on the hotfix.

-Tom

[TT-ReBORN]

Ok Jose, try this new version:

• Fixed window restore issue in maximized state for "NoBorder" frame style.
• Fixed cosmetic fullscreen glitch during window maximization with "NoBorder" frame style.
• Fixed position offset issue when dragging a maximized window with "NoBorder" frame style.

Updated:
foo_ui_wizard-0.2.1.zip

[Fizbin99]

0.2.1 seems to have fixed the above issue.

On an unrelated note, how do you normally enter maximized mode? The only way I can do it is by double clicking the title bar. Is that normal behavior?

EDIT...To answer my own question... YES.

[TT-ReBORN]

The only way I can do it is by double clicking the title bar. Is that normal behavior?

Yes, that's right, in general, the caption 🗖 button in the TOP MENU 🗕 🗖 ✖ CAPTION BUTTONS is for maximized state, but in Georgia-ReBORN, it is for fullscreen. Double clicking the titlebar does the maximized state, like in Windows Explorer.

[Zephyr0ck]

Great!🥳 It works perfectly, Tom! Thank you so much, as always, for taking the time to fix these issues. The theme in this new phase is amazing! ❤️

Video_250920081642.mp4

[silverwings15]

on a fresh install with UI Wizard 0.2.1, how do i remove these small gaps on the border of each side when maximizing or fullscreening?

[TT-ReBORN]

Ok @silverwings15,

try this new version UI Wizard 0.2.2 and tell me how it goes, I tested it on my virtual machine Win11 and it seems to be fine now:
foo_ui_wizard-0.2.2.zip

[Fizbin99]

Thanks for fixing the mouse/drag issue.

[silverwings15]

that seems to have done the trick, appreciate it!

[Fizbin99]

How do I go about making the title bar drag/restore function work with windows native title bar? I can get it working with UIWizard.SetCaptionAreaSize(0, 0, ww, "something") but whatever value I enter, the drag area exceeds the bars height and dips into the below panels. Even putting "1" is too much.

I'm really missing the drag/restore function. If I have to I'll make my own title bar.

[Fizbin99]

Actually, I think I have found a bug... With the frame set to Default and the window is in restored down, the title bar can drag beyond its confines. So let's say the title bar is 30 in height, the drag function will go into the 35-ish range.

Upon further review, it's not that big of a deal.

[madindehead]

Seeing this issue but with jsplitter: #38 (comment)

I can't even stop my current album playing. Georgia-Reborn loads, then jsplitter crashes.

Too much artwork? That's annoying.

[TT-ReBORN]

Hi @madindehead,
thank you for this important report! I totally forgot to tune the Garbage Collection settings in JSplitter for the 64-bit :(
But now I have optimized it and you should hopefully not see that issue anymore:

Optimized JSplitter GC config settings

• Increased max heap size to 2560 MB
• Increased heap growth to 256 MB
• Increased GC cycle time to 100 MS
• Increased GC delay to 500 MS
• Increased max allocations to 2000

Download from the master right now and replace your files:
https://github.com/TT-ReBORN/Georgia-ReBORN/archive/refs/heads/master.zip

We could try in the future, after it is stable to increase the max heap size to 4 GB and see how it goes...
But for now let's try and use 2,5 GB, it was only 1 GB at default setting :(

-TT

[TT-ReBORN]

Guys, if you do not want to download the latest master,
you need to immediately optimize your default JSplitter GC settings right now for 64-bits:

Set these optimized JSplitter GC config settings:

• Increased max heap size to 2560 MB
• Increased heap growth to 256 MB
• Increased GC cycle time to 100 MS
• Increased GC delay to 500 MS
• Increased max allocations to 2000

If 2,5 GB max heap size is stable after a couple of months, we can try to increase it to 4GB...
But right now use 2,5 GB.

@regorxxx, mentioned that JSplitter x64 is still capped at 4GB if I remember?
Did you try more than 4GB @regorxxx?

-Tom

[regorxxx]

Nothing has changed as I told u

[TT-ReBORN]

Actually, I tried myself and put 8192 MB and it caps at 4095. What a bummer for foobar2000 64-bit :/

[TT-ReBORN]

Do you remember why that is? Did LUR tried himself and found out the limitation and capped it because of that or what?
Sorry I can not remember the details anymore...

[regorxxx]

Not saying it may not be bypassed somehow, but it was a mozilla limitation on the engine (which also applies to all browsers). The engine is meant to only use max [first 2g and then] 4gb since years.

https://foobar2000.club/forum/viewtopic.php?p=85783#p85783

SpiderMonkey API has a limit for context memory:
// Create a new context (and runtime) for this thread.
extern JS_PUBLIC_API JSContext* JS_NewContext(uint32_t maxbytes, JSRuntime* parentRuntime = nullptr);
But I can increase the limit for the garbage collection threshold (now it is 256MB).

No idea if this recent change applies
https://spidermonkey.dev/blog/2025/01/15/is-memory64-actually-worth-using.html

Maybe you can ask LUR again about it.

[TT-ReBORN]

@Fizbin99,

first of all let's start a new post here, due to the window state management refactoring from UI Wizard 0.1.0 to 0.2.0,
the caption area indicator was not showing. I.e one bug fixed in the Columns UI let to not showing the indicator anymore...

Here the new version 0.2.0b with the caption indicator fixed:
foo_ui_wizard-0.2.2b.zip

Replace it in your Georgia-ReBORN and then open the UI Wizard preferences window,
now change the width or height in the caption area, you will now see the red caption area indicator rectangle.

---

You wrote:

I can get it working with UIWizard.SetCaptionAreaSize(0, 0, ww, "something") but whatever value I enter, the drag area exceeds the bars height and dips into the below panels. Even putting "1" is too much.

I'm really missing the drag/restore function. If I have to I'll make my own title bar.

The custom caption area is meant for the "NoCaption" or "NoBorder" framestyle. You can still use it in "Default" or "NoCaption"
but it was not intended for these framestyles because you have the original window titlebar that is managed by the original Windows behavior. Although it still works in Georgia-ReBORN regardless...

The automatic drag to normal window state works ONLY when the window is in maximized window state, it is disabled for fullscreen window state, because it does not make sense for fullscreen, why would you drag the window in fullscreen anyway? The users can indirectly drag move the window when clicking the top menu and get angry. It stays disabled in fullscreen window state, ditto.
I only did it for maximized window state because how the original Microsoft Windows also behaves, but actually this also does not make sense, why would you want to drag the window when it is maximized? Some questionable, design decisions by Windows, maybe this was only meant for multi-monitor setups to drag to another monitor...

---

Now do yourself a favor and remove that original ugly window titlebar, go pro and do not stay titlebar noob, ok? =)
That was the main point for using UI Hacks and now UI Wizard..., to remove that hideous thing...

I show you, how easy it is done.

First, create the caption buttons 🗕 🗖 ✖

gr-buttons.js:

	/**
	 * Creates the top menu 🗕 🗖 ✖ caption buttons.
	 * @param {number} ww - The window.Width.
	 * @param {number} wh - The window.Height.
	 * @private
	 */
	_createTopMenuCaptionButtons(ww, wh) {
		if (!UIWizard || UIWizard.FrameStyle === FrameStyle.Default ||
			grSet.layout !== 'default' && !grSet.showTopMenuCompact && ww < SCALE(grSet.layout === 'compact' ? 580 : 620)) {
			return;
		}

		const layoutDefault = grSet.layout === 'default';
		const hideClose = UIWizard.FrameStyle === FrameStyle.SmallCaption && UIWizard.WindowState !== WindowState.Fullscreen;
		const btnSize = this.btnImg.Close.Default.Height;
		const btnCount = hideClose ? (layoutDefault ? 2 : 1) : layoutDefault ? 3 : 2;
		const totalWidth = btnSize * btnCount + (btnCount - 1);

		let x = ww - totalWidth - SCALE(10);
		const y = Math.round(grm.ui.topMenuHeight * 0.5 - btnSize * 0.5 - SCALE(1));

		this.btn.Minimize = new Button(x, y, btnSize, btnSize, 'Minimize', this.btnImg.Minimize, 'Minimize');
		x += btnSize;

		if (layoutDefault && !hideClose) {
			this.btn.Maximize = new Button(x, y, btnSize, btnSize, 'Maximize', this.btnImg.Maximize, 'Maximize');
			x += btnSize;
		}

		if (!hideClose) {
			this.btn.Close = new Button(x, y, btnSize, btnSize, 'Close', this.btnImg.Close, 'Close');
		}
	}

Also look at _createButtonImages and _createButtonMap how it is done to set the images with the font glyphs.

Then you need to assign functionality to those caption buttons:

	/**
	 * Handles button action events based on menu, panel and button type.
	 * @param {Button} btn - The instance of the button.
	 * @private
	 */
	_actionHandler(btn) {
		const buttons = {
			// * TOP MENU COMPACT * //
			Menu: () => this.topMenu(),

			// * TOP MENU MAIN - DEFAULT FOOBAR2000 * //
			File: () => grm.topMenu.topMenuMain(btn.x, btn.y + btn.h, btn.id),
			Edit: () => grm.topMenu.topMenuMain(btn.x, btn.y + btn.h, btn.id),
			View: () => grm.topMenu.topMenuMain(btn.x, btn.y + btn.h, btn.id),
			Playback: () => grm.topMenu.topMenuMain(btn.x, btn.y + btn.h, btn.id),
			Media: () => grm.topMenu.topMenuMain(btn.x, btn.y + btn.h, btn.id),
			Help: () => grm.topMenu.topMenuMain(btn.x, btn.y + btn.h, btn.id),
			Playlists: () => grm.topMenu.topMenuPlaylists(btn.x, btn.y + btn.h),

			// * TOP MENU THEME BUTTONS * //
			Options: () => grm.topMenu.topMenuOptions(btn.x, btn.y + btn.h),
			Details: () => this.topDetails(),
			Playlist: () => this.topPlaylistArtwork(),
			Library: () => this.topLibrary(),
			Biography: () => this.topBiography(),
			Lyrics: () => this.topLyrics(),
			Rating: () => this.topRating(btn.x, btn.y + btn.h),

			// * TOP MENU 🗕 🗖 ✖ CAPTION BUTTONS * //
			Minimize: () => this.topMinimize(),
			Maximize: () => this.topMaximize(),
			Close: () => fb.Exit(),

			// * LOWER BAR TRANSPORT BUTTONS * //
			Stop: () => fb.Stop(),
			Previous: () => fb.Prev(),
			PlayPause: () => fb.PlayOrPause(),
			Next: () => fb.Next(),
			PlaybackOrder: () => this.lowerPlaybackOrder(),
			Reload: () => window.Reload(),
			AddTracks: () => this.lowerAddTracks(),
			Volume: () => this.lowerVolume(),
			Mute: () => fb.VolumeMute(),
			ArtistBtn: () => this.lowerArtistBtnAction(),
			TitleBtn: () => this.lowerTitleBtnAction(),
			PlaybackTime: () => this.lowerPlaybackTime(),

			// * PLAYLIST HISTORY BUTTONS * //
			Back: () => pl.history.buttons(btn),
			Forward: () => pl.history.buttons(btn),

			// * LYRICS INFO OVERLAY BUTTON * //
			LyricsInfoOverlay:() => this.lyricsFullLayoutBtnAction()
		};

		const btnAction = buttons[btn.id];
		if (btnAction) btnAction();
	}

You only need these:

	// * TOP MENU 🗕 🗖 ✖ CAPTION BUTTONS * //
	Minimize: () => this.topMinimize(),
	Maximize: () => this.topMaximize(),
	Close: () => fb.Exit(),

These wrappers topMinimize and topMaximize methods call the handleWindowControl method in gr-display.js
that fires the UI Wizard API methods.:

	/**
	 * Handles the minimize button action in the top menu, player goes into minimize window state.
	 */
	topMinimize() {
		grm.display.handleWindowControl('minimize');
	}

	/**
	 * Handles the maximize button action in the top menu, player goes into fullscreen and resumes player size.
	 */
	topMaximize() {
		grm.display.handleWindowControl('maximize');
	}

gr-display.js

In your constructor class, define the UI Wizard settings:

		// * UI WIZARD * //
		/** @public @type {boolean} UI Wizard pseudo caption state, used in setWindowDrag. */
		this.pseudoCaption = false;
		/** @public @type {number} UI Wizard sets pseudo caption width when dragging foobar, used in setWindowDrag. */
		this.pseudoCaptionWidth = 0;
		/** Preferences > Display > UI Wizard > Frame style: No border. */
		UIWizard.FrameStyle = 3;
		/** Preferences > Display > UI Wizard > Move with: Any method. */
		UIWizard.MoveStyle = 3;
		/** Preferences > Display > UI Wizard > Constraints: Disable window maximizing. */
		UIWizard.DisableWindowMaximizing = false;

	/**
	 * Manages and adjusts the window state based on various triggers such as key presses, button clicks, and double-click events on the top menu bar.
	 * This method handles toggling between fullscreen and normal window states, maximizing/restoring the window, and adjusting window state during specific UI interactions.
	 * @param {string} triggeredBy - Specifies the type of trigger that invoked the method. Expected values are 'key', 'minimize', 'maximize', or 'doubleClick'.
	 * The method distinguishes between different types of triggers:
	 * - 'key': Handles key press events, specifically for F11 to toggle fullscreen and ESC to exit fullscreen, respecting certain conditions.
	 * - 'minimize': Handles minimize button click events.
	 * - 'maximize': Handles maximize button click events.
	 * - 'doubleClick': Handles double-click events on the top menu bar, adjusting the window state based on fullscreen mode or specific layout settings.
	 * It also includes condition checks for:
	 * - Disabling specific functionality in certain layouts (e.g., 'Artwork' layout).
	 * - Ensuring fullscreen mode can be toggled or exited appropriately.
	 * - Handling exceptions that may occur during the state adjustment process.
	 */
	handleWindowControl(triggeredBy) {
		const isKeyF10 = triggeredBy === 'key' && utils.IsKeyPressed(VKey.F10);
		const isKeyF11 = triggeredBy === 'key' && utils.IsKeyPressed(VKey.F11);
		const isKeyEscape = triggeredBy === 'key' && utils.IsKeyPressed(VKey.ESCAPE) && !grSet.fullscreenESCDisabled;
		const isMinimize = triggeredBy === 'minimize';
		const isMaximize = triggeredBy === 'maximize';

		try {
			if (isMinimize) {
				UIWizard.WindowMinimize();
			}
			if (isKeyF10) {
				UIWizard.ToggleMaximize();
			}
			else if (grSet.layout === 'default' && (isKeyF11 || (isMaximize && grSet.fullscreenMaximize))) {
				UIWizard.ToggleFullscreen();
			}
			else if (isKeyEscape) {
				UIWizard.ExitFullscreen();
			}
			if (grSet.layout !== 'default' && UIWizard.WindowState === WindowState.Maximized) {
				UIWizard.ExitMaximize();
			}
		}
		catch (e) {}
	}

These control the caption buttons and the F10/F11 key shortcuts.

Finally, you need to handle the window dragging on the invisible custom caption area:

	/**
	 * Sets temporarily top menu caption to be able to drag foobar around.
	 * @param {number} x - The x-coordinate.
	 * @param {number} y - The y-coordinate.
	 */
	setWindowDrag(x, y) {
		// * Disable mouse middle btn (wheel) to be able to use Library & Biography mouse middle actions
		UIWizard.MoveStyle = grm.ui.displayLibrary && mouseInLibrary(x, y) || grm.ui.displayBiography && mouseInBiography(x, y) ? 0 : 3;
		try {
			if (grm.button.mouseInControl || grm.button.downButton) {
				UIWizard.SetCaptionAreaSize(0, 0, 0, 0);
				if (UIWizard.FrameStyle === 3) UIWizard.DisableWindowSizing = true;
				this.pseudoCaption = false;
			}
			else if (!this.pseudoCaption || this.pseudoCaptionWidth !== grm.ui.ww) {
				UIWizard.SetCaptionAreaSize(0, 0, grm.ui.ww, grSet.layout !== 'default' ? grm.ui.topMenuHeight + SCALE(5) : grm.ui.topMenuHeight);
				if (UIWizard.FrameStyle === 3 && !grSet.lockPlayerSize) UIWizard.DisableWindowSizing = false;
				this.pseudoCaption = true;
				this.pseudoCaptionWidth = grm.ui.ww;
			}
		} catch (e) {}
	}

When the mouse is in the custom caption area or clicking the top menu, it needs to disable the caption area temporarily:
UIWizard.SetCaptionAreaSize(0, 0, 0, 0);
Why? Because otherwise the top menu buttons will not work, as the caption area is higher z-level and the click will not go through, i.e register the click action.
After dragging ( this.pseudoCaptionWidth !== grm.ui.ww ) or when the mouse leaves the caption area ( !this.pseudoCaption ), you set the caption area size again:
UIWizard.SetCaptionAreaSize(0, 0, grm.ui.ww, grSet.layout !== 'default' ? grm.ui.topMenuHeight + SCALE(5) : grm.ui.topMenuHeight);

Then you have a perfect "NoBorder" window that works like in Georgia-ReBORN.
That's it.

P.S: Double-clicking in the custom caption area, does call ToggleMaximize() for maximizing and restoring to normal window state.
This is handled internally by UI Wizard.

-Tom

[TT-ReBORN]

I do not understand, I do not have such issues in Georgia-ReBORN or original foobar with Columns UI when using all framestyles.
It needs to calculate new positions and sizes of each panels in the main window, it takes 500ms or faster depending on your CPU power.

So I do not know what the issue really is, because I do not have such issues. But if you can send me your theme, I can see for myself.
Video does not help for such issue. You need to understand me, how should I fix something when I can not understand or reproduce what the issue really is? I don't even know what panel type you are using, maybe you are using old PSS splitters or something, I know nothing about your theme :/ . WinAPI has lot of bugs and quirks, so the best for you and me is to send me your theme!
Upload to Google Drive and send me the link =)

[Fizbin99]

Yes, I know Reborn has no such issue. My theme only has the issue with No Border.

Anyway, I'm using the latest jsplitter and I'm running 64 bit. I'll send a video, anyway just to let you know what to watch for.

[silverwings15]

TT already said a video is of no use to him..

[Fizbin99]

Fine

[Fizbin99]

It seems to be fixed. I first had to figure out a way to make Reborn do the same thing. Surprisingly (for someone who can't program) the first thing I suspected and tried worked.I removed this if statement in callbacks on_size.

if (!grm.display.sizeInitialized) {
	grm.ui.initPanels();
	grm.display.sizeInitialized = true;
} else {
	grm.ui.setMainMetrics();
	grm.ui.setMainComponents('all');
	grm.ui.resizeArtwork(true);
	grm.button.createButtons(grm.ui.ww, grm.ui.wh, false);
	grm.ui.setPlaylistSize();
	grm.ui.setLibrarySize();
	grm.ui.setBiographySize();
}

That made Reborn do the same thing. So I ended up writing something similar and now it worked...no more funky lag. But after I wrote it, Fullscreen wouldn't work. LOL. But in the end everything works now.

silverwings15... Your input here is very valuable and I enjoy your posts but I don't think you should be 'speaking' for TT. Just my opinion.

[silverwings15]

ran into this random crash, haven't been able to reproduce yet

Error: JSplitter v4.0.4 ({D8E5FB80-4F1A-4314-984E-8514B075D843}: Georgia-ReBORN v3.0-x64-DEV by TT)
CreateImage failed:
Failed to create GdiPlus object (0x2): InvalidParameter

File: <main>
Line: 2270, Column: 26
Stack trace:
  FillGradRoundRect@:2270:26
  [email protected]:3235:22
  [email protected]:3204:8
  drawLowerBar@:1023:16
  drawMain@:380:8
  on_paint@:121:9

[TT-ReBORN]

Btw, this also applies to your scripts @Fizbin99 =)

[regorxxx]

I think it would simply be better to just patch the method at the prototype level like I did with JSP3 to SMP wrapper. There are a lot of these cases... And that way it just works globally, no need to keep patching existing code.

I will probably end doing that.

Anyway if you have some kind of list of these things, maybe it can be reported to marc/LUR too.

Thanks for the warning :)

[TT-ReBORN]

Yes of course I fully agree, should be done in the first place.
Over these years, I encountered a lot of these quirks/bugs, but I can not remember every one of them anymore.
I am sure you do too, so how about we make a known list of these? The arc crap etc, was one of the most frustrating ones...
Then there is other stuff with gradient rectangle GDI bugs etc, we did report some here:
TheQwertiest/foo_spider_monkey_panel#206

Btw, I am going to focus in few days on Audio Wizard and take a look with the callbacks, resolution etc...

[TT-ReBORN]

@silverwings15,

this should be now fully fixed in the latest commit:
https://github.com/TT-ReBORN/Georgia-ReBORN/archive/refs/heads/master.zip

You only need to replace the scripts directory from the master.zip with yours.
Now Georgia-ReBORN should be more robust against idiotic GDI graphics behavior that doesn't make sense =)

-Tom

[silverwings15]

updated, will let you know if i run into it again

[urielejh]

waveform bar file cannot be analyzed when using audio wizard

[TT-ReBORN]

Works as expected, just not on ISO image files.
Also it is much faster analyzing than the previous external audiowaveform and ffprobe in Georgia-ReBORN 32-bit...