Skip to main content
Topic: foobar2000 1.5 beta 1 properties bug (Read 4067 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foobar2000 1.5 beta 1 properties bug

There's a mess with properties subcategories Selection Properties -> Metadata alone displays nothing, must be combined with other subcategory

I can't somehow get used to new properties dialogue. Could be the old box available?

Re: foobar2000 1.5 beta 1 properties bug

Reply #1
Thanks for the bug report.

I understand that the new dialog breaks some people's habits; the old one will be made available as a standalone component later.

Re: foobar2000 1.5 beta 1 properties bug

Reply #2
Thanks for the bug report.

I understand that the new dialog breaks some people's habits; the old one will be made available as a standalone component later.

When we add pictures for cover and artwork please set to search in it's music/album folder automatically. I love your Foobar2000, Good job sir.

Re: foobar2000 1.5 beta 1 properties bug

Reply #3
Also, when exporting images, it should default to the current directory, IE foobar2000 automatically selects the folder in question.

Nevermind, I made a mstake

Re: foobar2000 1.5 beta 1 properties bug

Reply #4
Some feedback to new properties dialog:
1. Artwork.
- I wish the first letter on column Name uses big letter, similar to context menu.
- Previous version shows format of attached picture. I wonder if you will add it later.
- Right-click on free space, 'Remove' context menu is enabled but nothing to be removed.
2. ReplayGain
- By using Tools -> ReplayGain -> (scan menu), I wish it will be redirected to ReplayGain tab, if that makes sense.

Re: foobar2000 1.5 beta 1 properties bug

Reply #5
I’ve also noticed that the width of the “Name” column on the “Metadata” tab resets itself to much narrower than I would like whenever I re-open the Properties dialog. (I have some long-ish field names!)

Currently, foobar2000 1.4.* remembers the width I set for the “Name” column.

Re: foobar2000 1.5 beta 1 properties bug

Reply #6
Some feedback on new properties dialog: IMO, there should be a separator between columns, since it makes harder to distinguish visually the end of data in one column and the start of the data in the next column (especially if these column contain long space separated strings).

Re: foobar2000 1.5 beta 1 properties bug

Reply #7
Thanks for all the feedback.
Beta 2 posted, most of the reported issues have been addressed.

Some feedback on new properties dialog: IMO, there should be a separator between columns, since it makes harder to distinguish visually the end of data in one column and the start of the data in the next column (especially if these column contain long space separated strings).
Post a screenshot please so I can get a better idea what it looks like for you.

Re: foobar2000 1.5 beta 1 properties bug

Reply #8
Thanks for the bug report.

I understand that the new dialog breaks some people's habits; the old one will be made available as a standalone component later.

When we add pictures for cover and artwork please set to search in it's music/album folder automatically. I love your Foobar2000, Good job sir.

Thank you for anwer my prayer immediately in 1.5 beta 2 :) I don't need mp3tag now.


Re: foobar2000 1.5 beta 1 properties bug

Reply #10
Peter,

Would it be possible to make the Properties dialog use the current color scheme for background / text / highlight as set in Preferences? (Maybe an option in Advanced?) I use a dark grey background and light text which pops a bit more making it easier on the eyes.

I'm also crossing my fingers you could maybe expand the Selection Properties element to include specific headings for the "Other" components, which could solve Spider Monkey Panels theft of the %rating% display from Playback Statistics. >:(  ;)

(And, speaking of Preferences, Advanced > Display > Album List, there is a typo)

Cheers


Re: foobar2000 1.5 beta 1 properties bug

Reply #11
The properties dialog crashes on Windows XP/2003 often, about a quarter of the time as soon as it appears, and more often on a slower computer. Also crashes at the end of a ReplayGain scan started from the dialog. If you don't want to look at the problem, it is not a big deal.

The tabular overview of ReplayGain is nice. I'd like to see an option to manipulate a selection/column of values, in order to delete all album gains if I discover that the set has uneven loudness (for example).

The column headers in the properties dialog look a bit ugly, they don't line up with the top of the dialog,extend past the tabs on either side, and are set in the Microsoft Sans Serif font, unlike the rest of the dialog.

An old issue still exists, where the default "Edit" option is not available after clicking on multiple fields on first startup of Foobar. The first menu option is "Remove".

Re: foobar2000 1.5 beta 1 properties bug

Reply #12
Hi Peter,

I love the new ease of accessibility of the file properties using the keyboard shortcuts, it's very much appreciated. There's just one little cosmetic issue that I would like you to address, if possible. Currently, except for the details tab, the width of the columns aren't remembered. Both v1.5 beta 1 and beta 2 are affected.
Best regards
deus-ex

Re: foobar2000 1.5 beta 1 properties bug

Reply #13
When trying to add a new metadata field that already exists in other files, pre 1.5, the field name would autocomplete (such as when typing "CA", you'd get "CATALOG #"). Now, the autocomplete is gone and you lose the ability to autocomplete the field name, which leads to a greater chance of typing errors and improper tags.

Re: foobar2000 1.5 beta 1 properties bug

Reply #14
The properties dialog crashes on Windows XP/2003 often, about a quarter of the time as soon as it appears, and more often on a slower computer. Also crashes at the end of a ReplayGain scan started from the dialog. If you don't want to look at the problem, it is not a big deal.
I see nothing on the crash report tracker. Please autosend reports, or send me the .txt/.dmp files if sending automatically is impossible.

EDIT
Problem recreated in a virtual machine, I see crash log writing doesn't work at all in this case, investigating.

EDIT 2
Neat bug, fixed for the next update... affects 1.4 series too but harder to trigger.
Also improved crash report writing so stack overflows produce valid reports that can be submitted automatically.

 

Re: foobar2000 1.5 beta 1 properties bug

Reply #15
I've noticed that the return key now has the same effect as double click, in that it opens whichever field is currently highlighted. Previously, return had the same effect as clicking the 'OK' button to save/close the properties window or any field editing pop-up.

If this is intentional, is it possible for return key behaviour to be toggled, perhaps in Advanced Settings? The muscle memory is strong after tagging through these menus for the past decade...!  ;) :D

I also echo earlier points regarding the visual pattern of the rows. It would be helpful if the old Excel-style light grey lines between fields could be toggled, or else, for the shading to be more distinct for those of us with poor eyesight or poor screens.

As always, thanks so much for your hard work!

Re: foobar2000 1.5 beta 1 properties bug

Reply #16
Thank you for the fix. I did not get a crash report or even the dialog from windows. It just closed.

These faint alternating shaded rows do exist in some other traditional, non-flat software. And they are quite helpful in following lines due to their halved frequency. Maybe their intensity could be increased a notch? I see one other example with 247. The read only columns to the left could be shaded further, to indicate that they cannot be edited. For example, if I open a multi-field tagging dialog, and see the same string under Item and Title, a different background color would make the dialog more organized. In other software this happens with line number column or sorted columns (e.g. Xyplorer).

Re: foobar2000 1.5 beta 1 properties bug

Reply #17
I've noticed that the return key now has the same effect as double click, in that it opens whichever field is currently highlighted. Previously, return had the same effect as clicking the 'OK' button to save/close the properties window or any field editing pop-up.

If this is intentional, is it possible for return key behaviour to be toggled, perhaps in Advanced Settings? The muscle memory is strong after tagging through these menus for the past decade...!  ;) :D

I also echo earlier points regarding the visual pattern of the rows. It would be helpful if the old Excel-style light grey lines between fields could be toggled, or else, for the shading to be more distinct for those of us with poor eyesight or poor screens.

As always, thanks so much for your hard work!

I posted something similar here about the enter key now is the same as double click.

I also would like to see a change in this behavior. :)

Re: foobar2000 1.5 beta 1 properties bug

Reply #18
When trying to add a new metadata field that already exists in other files, pre 1.5, the field name would autocomplete (such as when typing "CA", you'd get "CATALOG #"). Now, the autocomplete is gone and you lose the ability to autocomplete the field name, which leads to a greater chance of typing errors and improper tags.

Yup, I have to concurr - without autocomplete my acceptance factor tends towards zero...
In the old dialogue we were able to choose from already used tag names when adding new fields so writing wasn't necessary. This is a big step backwards now.

Re: foobar2000 1.5 beta 1 properties bug

Reply #19
When trying to add a new metadata field that already exists in other files, pre 1.5, the field name would autocomplete (such as when typing "CA", you'd get "CATALOG #"). Now, the autocomplete is gone and you lose the ability to autocomplete the field name, which leads to a greater chance of typing errors and improper tags.
Autocomplete is not gone. It is adjustable now. File->Preferences->Advanced->Display->Properties dialog->Field name suggestions
And, after you typed some name manually in Properies dialog, it becomes automatically remembered in "Field name suggestions". So you need to type it manually only first time.

Re: foobar2000 1.5 beta 1 properties bug

Reply #20
Regarding autocomplete of field names, it works.... it *logically* does the right thing, suggests known field names that are not yet listed in the table.
I have to admit that at some point I myself thought it was not working properly, not listing the field names I expected, because they were already listed above.
I'm changing it to list all fields, because the way it is now confuses too many people.
I guess some of you also expect a dropdown list instead of edit+autocomplete... I don't currently have the technology to embed such in a table instead of the editbox, but I'll investigate it at some point.

Re: foobar2000 1.5 beta 1 properties bug

Reply #21
Peter, I sent you a private message if you could give it a read.

Re: foobar2000 1.5 beta 1 properties bug

Reply #22
So you need to type it manually only first time.

Ah.. I thought it would use tags that already exist in my library.

Regarding autocomplete of field names, it works.... it *logically* does the right thing, suggests known field names that are not yet listed in the table.
I have to admit that at some point I myself thought it was not working properly, not listing the field names I expected, because they were already listed above.
I'm changing it to list all fields, because the way it is now confuses too many people.
I guess some of you also expect a dropdown list instead of edit+autocomplete... I don't currently have the technology to embed such in a table instead of the editbox, but I'll investigate it at some point.

If any change could be made to improve usability, I would suggest keeping the old behavior where if you typed "CA", "CATALOG #" (or whatever) would be automatically filled into the box. That way, if you type "CA" and tab to the value field, the "CATALOG #" tag is kept and you can immediately type its value.

Currently if you type "CA", you have to hit down, then tab. I've already accidentally added several incomplete tag names (like "CA" for "CATALOG #" or "PU" for "PUBLISHER") and each time have to go deep into the advanced preferences to remove those entries.

Re: foobar2000 1.5 beta 1 properties bug

Reply #23
Add commonly used fields like Label / Catalog number to the standard fields in Advanced -> Display so you don't have to type the name at all.

Re: foobar2000 1.5 beta 1 properties bug

Reply #24
Beta 3 posted.

Properties crash has been fixed.
Some changes in visual appearance have been introduced.
Enter key behavior should now make sense. If it's still mishandled in some dialog/page, please post about it and it will be fixed.
Various accessibility issues have been fixed, checkboxes should be presented to screen readers properly.
Add new field autocomplete no longer hides fields already present.

The next update will bring more autocomplete behavior changes.

 
SimplePortal 1.0.0 RC1 © 2008-2019