Feature request: add bit-depth to audio properties

Applications
,
1

Currently a number of audio properties and metadata can be inspected in Nautilus, one of them is the sample rate of the audio file, e.g. 44.1Khz.

The sample rate is generally only informative in combination with the bit-depth of the file, together they determine the resolution of the audio. The bit-depth is currently not included as a property, it would be good if it could be added.

image
image926×1066 44.7 KB

1 Like
2

Sure. Please note bit depth might not apply to lossy compressed audio.

So, we should probably display a combination of the following depending upon the audio.

  • Sample Rate
  • Bit Depth
  • Bit Rate
3

Yes, that’s a good nuance.

There are two other issues relating to the audio properties panel that might be good to look into, but i don’t know if they belong in this thread or should be discussed separately:

  • The panel currently has no scrollbar, so if one of the fields has a lot of content (e.g. the Comment field) it will fill the panel and the rest of the properties will be unreachable.

image
image933×1355 124 KB

  • In the case of FLAC and perhaps also other formats, which i think are technically not container formats, the panel adds an extra container field which will be a duplicate of the codec field.

image
image929×1171 51.3 KB

1 Like
4

The rest of the properties can be reached by scrolling, it’s just the scrollbar is not visible here.

Sure.

5

That doesn’t appear to work on my system (Gnome 48.0), i can’t scroll the panel with my touchpad or by walking down the list with the keyboard arrows.

6

Comment might be the last field for that audio file. Can you try with other files or update the comment and check.

Also, you can rule out any CSS custom theming issue.

7

It isn’t the last field, if i remove most of the text in the Comment tag so that it fits on one line, then the properties panel will show the rest of the fields below it. Example:

image
image927×1298 57.6 KB

I’ve only applied custom CSS colors so no other theming that would be of influence:

@define-color accent_color #586e75;
@define-color accent_bg_color #1f444d;
@define-color accent_fg_color #eee8d5;

@define-color window_bg_color #002b36;
@define-color window_fg_color #eee8d5;

@define-color sidebar_bg_color #002b36;
@define-color sidebar_backdrop_color #002b36;

@define-color headerbar_bg_color #07313b;
@define-color headerbar_fg_color #eee8d5;
@define-color headerbar_backdrop_color #002b36;

@define-color popover_bg_color #123a44;
@define-color popover_fg_color #eee8d5;

@define-color dialog_bg_color @popover_bg_color;
@define-color dialog_fg_color @popover_fg_color;

@define-color view_bg_color #073642;
@define-color view_fg_color #eee8d5;

@define-color card_bg_color #123a44;
@define-color card_fg_color #fdf6e3;

@define-color warning_bg_color #CB4B16;
@define-color warning_fg_color #eee8d5;
@define-color warning_color #CB4B16;
@define-color error_bg_color #DC322F;
@define-color error_fg_color #eee8d5;
@define-color error_color #DC322F;
@define-color success_bg_color #859900;
@define-color success_fg_color #eee8d5;
@define-color success_color #859900;
@define-color destructive_bg_color #D33682;
@define-color destructive_fg_color #eee8d5;
@define-color destructive_color #D33682;
8

Can you try resizing the properties window?

9

That will show a little bit more (about 1 line) but not much, here it is resized:

image
image2266×1796 237 KB

10

This is weird. I’d suggest checking in a new environment (new user).

Also which distro was this on?

11

This is on Fedora (42 beta). I’ve also tested in Hyprland and the behaviour appears to be the same there.

12

Works fine in Fedora 42 beta.

It’s related to some customization in your environment.

13

I’m fairly certain this isn’t the case, i will try to illustrate with a screen recording. This is with all extensions and CSS disabled. The scrolling of the popup does work in principle, but the audio properties panel won’t show any items beyond the initial 100% height of the panel:

Screencast

14

Can you open 2 issues for these? Also attach audio files that has the issue as that would greatly help.

15

Do you mean on Gitlab in that case or here on Discourse?

16

Issues are filed on GitLab, yes. Discourse is for discussion.

17

Ok here are two tickets for both issues:

1 Like