Uosc customization

[ElvioG]

Hello everyone,
I have been using MPV with the UOSC ui for a while now, I have customized some functions of MPV and wanted to know if it was possible to fix or customize some things.

• When I open an audio file (mp3, wav) I would like to have a smaller window size, and change the window background (is black now)

• I would like to add a background in alpha behind the osc, so that more buttons and elements contrast especially if I have a dark scene.

• When I have a very short video or audio that lasts only a few seconds, on the seekbar I display (e.g. for 10 seconds) 01-10, instead I would like to be able to display in detail, such as h:m:s

• Is possible with MPV have custom icons per file type, like Pot Player?

Thank you

[christoph-heinrich]

* When I open an audio file (mp3, wav) I would like to have a smaller window size, and change the window background (is black now)

You can use conditional auto profiles to change the window size using geometry or autofit.

[audio-only]
profile-cond=vid == false
autofit=500
profile-restore=copy-equal

The black window can be remedied with the visualizer.lua script.

* When I have a very short video or audio that lasts only a few seconds, on the seekbar I display (e.g. for 10 seconds) 01-10, instead I would like to be able to display in detail, such as hms

That's currently not configurable. Do we want it to be? @tomasklaen

* Is possible with MPV have custom icons per file type, like Pot Player?

I don't think that's possible.

[ElvioG]

I understand that maybe you don't like the h : m : s format in short files, but it would be a useful thing to give the option to override it whenever the user feels like customizing their experience to suit their needs and tastes, don't you think?

[tomasklaen]

Since it adds an option that needs to be maintained and increases config file bloat, it needs to be justified. It needs to add value.

And you haven't provided any reason why displaying zeroes that don't convey any information adds value, or addressed the fact that doing so makes parsing the smaller timestamps harder/slower. So in this sense, it'd be an option to make things worse.

Your arguments are still a biased "I like it like that", and "others do it too", which don't count.

This is not just my whim. The way it works now was a requested feature that I agreed with, since it makes sense from any angle I look at it. You're just not used to it. Once you do, you'll be annoyed at pointlessly long timestamps, as I am now. It's similar difference as displaying time as 2023-06-01T10:17:37.533Z instead of 1 second ago.

[ElvioG]

Let me understand something, MPV basic always shows hms format even if the file is short. In UOSC it doesn't, there are only the seconds, so it seems to me that there is your legitimate choice, based on your taste and the way you work, no?
I am involved in audio and video production, and in whatever software I have used in my life that my brain is used to, both visually and in terms of usability, I have always found the hms format, ms, etc., to be the most common.
Now, considering that it is a feature taken out of the basic MPV program, considering that I know how I work and I don't go to others to tell them how their brains work, considering that I am asking for me, and I am certainly not saying that you have to work and implement an option (also because I never asked to implement an option, but rather if it would be possible to show the hms format), where can I restore the feature that was taken out and changed?
Then if you can't give me this information or if it's not possible just say so, you can't and I'll get over it, but if you allow, my habits, my way of working, my tastes are precisely my own, so if it's possible I ask, if it's not it's okay.
Thank you

[christoph-heinrich]

Here is how to change that

diff --git a/scripts/uosc_shared/lib/utils.lua b/scripts/uosc_shared/lib/utils.lua
index 4eecddc..9847664 100644
--- a/scripts/uosc_shared/lib/utils.lua
+++ b/scripts/uosc_shared/lib/utils.lua
@@ -217,14 +217,6 @@ function format_time(seconds, max_seconds)
 		local formatted = string.format('%.' .. options.time_precision .. 'f', math.abs(seconds) % 1)
 		human = human .. '.' .. string.sub(formatted, 3)
 	end
-	if max_seconds then
-		local trim_length = (max_seconds < 60 and 7 or (max_seconds < 3600 and 4 or 0))
-		if trim_length > 0 then
-			local has_minus = seconds < 0
-			human = string.sub(human, trim_length + (has_minus and 1 or 0))
-			if has_minus then human = '-' .. human end
-		end
-	end
 	return human
 end

[ElvioG]

Here is how to change that

Yes, thank you, I was just looking at this function

[bananakid]

@tomasklaen, @christoph-heinrich, it's a quite insignificant question for a separate discussion (and I didn't find a similar issue), maybe you'll find a minute to guide me: how do I change icon and button size for window controls buttons (minimize, maximize and close window) in uosc 5.10.0? When editing TopBar.lua, I have tried this without a favorable result:

--Line 77 data doesn't affect the window controls button glyphs size (I couldn't figure what this line affects at all),
--i.e. self.icon_size = round(self.size * 0.025) has no effect
 self.icon_size = round(self.size * 0.25)

--In line 78, once I change 2 to 6 the controls do get smaller, 
--but the main text font of TopBar gets smaller as well, I'd like to keep the default main text font of TopBar as it is,
--i.e. self.font_size = math.floor((self.size - (math.ceil(self.size * 0.25) * 6)) * options.font_scale)
self.font_size = math.floor((self.size - (math.ceil(self.size * 0.25) * 2)) * options.font_scale)

I succeeded in 5.0.0 fairly easy with that, but the code changed so much since then. Also sorry, I know I can adjust top_bar_size in uosc.conf to make buttons smaller, but it controls the title font size too.

[tomasklaen]

You'll have to modify the "Window controls" section of the TopBar:render() function:

uosc/src/uosc/elements/TopBar.lua

Lines 234 to 271 in 7fbcff4

	-- Window controls
	if options.top_bar_controls then
	local is_left, button_ax = options.top_bar_controls == 'left', 0
	if is_left then
	button_ax = ax
	ax = self.size * #self.buttons
	else
	button_ax = bx - self.size * #self.buttons
	bx = button_ax
	end
	for _, button in ipairs(self.buttons) do
	local rect = {ax = button_ax, ay = ay, bx = button_ax + self.size, by = by}
	local is_hover = get_point_to_rectangle_proximity(cursor, rect) == 0
	local opacity = is_hover and 1 or config.opacity.controls
	local button_fg = is_hover and (button.hover_fg or bg) or fg
	local button_bg = is_hover and (button.hover_bg or fg) or bg
	cursor:zone('primary_down', rect, button.command)
	local bg_size = self.size - margin
	local bg_ax, bg_ay = rect.ax + (is_left and margin or 0), rect.ay + margin
	local bg_bx, bg_by = bg_ax + bg_size, bg_ay + bg_size
	ass:rect(bg_ax, bg_ay, bg_bx, bg_by, {
	color = button_bg, opacity = visibility * opacity, radius = state.radius,
	})
	ass:icon(bg_ax + bg_size / 2, bg_ay + bg_size / 2, bg_size * 0.5, button.icon, {
	color = button_fg,
	border_color = button_bg,
	opacity = visibility,
	border = options.text_border * state.scale,
	})
	button_ax = button_ax + self.size
	end
	end

[bananakid]

Thank you kindly for input, Tomas, it was tricky to get it pixel perfect, but nothing too crazy! Would you kindly also tell what color coordinates does hover_bg of the close window button use and how to assign a "true red" (#FF0000) color to it? Here, if I set it to ff0000 instead of 2311e8, I get blue hover color:
https://github.com/tomasklaen/uosc/blob/7fbcff41c28ac013d0c844053ff0ce90f74a0ed6/src/uosc/elements/TopBar.lua#L33C33-L33C37

[tomasklaen]

ASS color format is BGR instead of RGB for some reason.