View Issue Details

IDProjectCategoryView StatusLast Update
0001301OpenMPTFeature Requestpublic2023-04-27 17:15
Reporterharbinger Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionduplicate 
Platformx64OSWindowsOS Version7
Product VersionOpenMPT 1.28.08.00 / libopenmpt 0.4.9 (upgrade first) 
Summary0001301: Sound file properties from tree view
Description

When i'm previewing samples from the tree, i often need to know the properties of the sound file. I have already had to go thru and mark all my stereo samples special (i end them with a $), but now i need to know other properties, like bit rate, file size, etc., before assigning it to a sample slot.

What would be nifty is a message that shows these various file attributes, perhaps as a tooltip or a set of abbreviations in the Status Bar for the file that's selected. This would save me from having to go to a third-party sound previewer just to see what the sample's stats are.

TagsNo tags attached.
Has the bug occurred in previous versions?
Tested code revision (in case you know it)

Relationships

duplicate of 0001389 new "Properties" instruments in the console menu of the tree view file browser. 

Activities

Saga Musix

Saga Musix

2020-03-03 07:36

administrator   ~0004247

While a tooltip might appear handy on first sight, it would be a very bad idea because it could lock the UI for many seconds, depending on how complex the instrument you are hovering really es. OpenMPT needs to load the whole sample or instrument to know its bit rate, if it has one at all.

harbinger

harbinger

2023-04-27 05:42

reporter   ~0005695

Can openMPT be set up to read the file then display the attributes in a new side box in the Sample Editor page?

Saga Musix

Saga Musix

2023-04-27 17:14

administrator   ~0005696

I'll mark this as a duplicate of 0001389 where there is some further discussion and where some initial work was done (file size and modification date are now shown in the status bar). Some sort of dialog that has to be explicitly called by the user is probably the only way to implement this in a way that doesn't degrade application performance for everyone who doesn't need the feature.

Issue History

Date Modified Username Field Change
2020-03-02 21:55 harbinger New Issue
2020-03-03 07:36 Saga Musix Note Added: 0004247
2023-04-27 05:42 harbinger Note Added: 0005695
2023-04-27 17:14 Saga Musix Note Added: 0005696
2023-04-27 17:14 Saga Musix Relationship added duplicate of 0001389
2023-04-27 17:14 Saga Musix Status new => closed
2023-04-27 17:14 Saga Musix Resolution open => duplicate