Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_infobox (Read 166625 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_infobox

Reply #175 –
Many thanks to Nirana and bluenet~

Few Suggestions:
  • Return the CAPS for tag names; it looks odd when there are a few lowercase fields when most of your tags are uppercase (the lowercase may not even be user-intentional, such as 'totaltracks').
  • Multiple-field merging in the dialog is very nice (one of the reasons the original foo_playcount opted for merging the PLAY_STAMP tag was because how ugly it looked in the existing tag editors). However, if you edit that field, it will actually write it as a single entry (i.e. 2 tags ARTIST="foo," "bar" => ARTIST="foo/bar"). Also suggest using the backslash '\' in place of the slash '/', since fb2k already uses it (in the multiple properties dialog) to separate multiple values.
  • Moving the 'Length' and 'Subsong index' boxes from the lower right to the upper left reduces the viewing area for tags while leaving a large gap in the 'Technical info' box. I think the previous scheme made a more efficient use of space; even resized as small as it can, I have a hard time finding a file which can fill up the entire Tech info box while the left half of the dialog is as scrunched as ever. Edit: I see that was to make it match the height of the new 'ReplayGain' area (which has slightly strange sunken-looking fields). Perhaps this could be a compromise?
  • Both the Title and Genre fields are selected when you open the dialog.
  • Editing the Genre field does not activate the 'Update' and 'Save & Close' buttons.
  • Changing 'Cancel' to 'Close' and adding a prompt seems more appropriate; if you update the tags, Cancel wouldn't do what it implies.
  • Customizable font? Appreciate the effort to remove config clutter, but Tahoma 8 is a little hard to read on this screen. It was also nice to hide the features I hardly used from the dialog (codepage, follow cursor, change focus). I'd figure other people would have their own reasons too.
Kudos for picking up the development.
f to c to f to c

foo_infobox

Reply #177 –
Anyone else not being able to download it?

EDIT: Nervermind! Works Now.

foo_infobox

Reply #178 –
bug in genre box. shows "progressive" as "progressive rock" on 0.9

foo_infobox

Reply #179 –
Bug list :

*  non-ID3v1 Genres not supported (Would like to add "Chanson Française" as a genre, and many custom others.)
*  Save and close feature not yet implemented (?) or not working in it's implementation.  IMO, this is a very important feature, as it allows you to go directly to the next song in a single click instead of two.

Also, TOTALTRACKS is now a standard tag in foobar2000 0.9 : as such, it should be located right beside the tracknumber, after a slash, maybe (# 01/15 )

I also think Performer and Composer should have dedicated text boxes.

foo_infobox

Reply #180 –
Quote
I love this new inline editing and it almost makes up for the info tool but I don't like how it doesn't display the existing tag content for editing, when you edit within the columns ui playlist.  When the field becomes editable, it also becomes blank.  I think it would be really easy to copy the text out of the field and start the new field that way, so why don't they, and if they have, how do you switch to that or do that?
[a href="index.php?act=findpost&pid=376374"][{POST_SNAPBACK}][/a]


It does for me... are you sure that you have the correct tag set in the "metafield to edit" box?

foo_infobox

Reply #181 –
Thanks for this, it works great but has some speed problems here.. It's kinda slow compared to the old one, I hope you can improve that (if you experience it too..).

foo_infobox

Reply #182 –
BUG: if we switch between playlists and have infobox open it work well after changing focus, but it wont work if there is only one track on playlist (have to right click > "file info" because reload info dont work in that specific case)

100% agree with Silverbolt

foo_infobox

Reply #183 –
Thanks very much for this great plugin!

Great work!
Keep it up!

foo_infobox

Reply #184 –
Thanks for reported. 2.0.1 was release, for bug fixed.
Accept more suggest as Silverbolt said.

2.0.1 Change Log:
   Speed up
   Option to keep field name upper.
   Multiple-field separator changed to '\' as FB2K used.
   Fixed editing the Genre field does not activate the 'Update' and 'Save & Close' buttons.
   Prompt when close dialog if value changed.
   Reload info while activate playlist or item changed.

to Shinsou: Where can I find the standard Genre list?

foo_infobox

Reply #186 –
Quote from: bluenet on
Multiple-field separator changed to '\' as FB2K used.


Please:

- check the '\' because I can see in your panel that multi values info are shown with the '/' separator and not the '\'.

- state again which is the char we have to use for multi values fields (to avoid confusion).


Do you think you can do something to solve the old inconsistency issue about '/' separator working with a multi files selection and not working with a single file selection?

thanks.

foo_infobox

Reply #187 –
Hi Bluenet,

Thanks for the update! I was wondering if you had plans to to fix or upgrade the "File Info / details" box? The "Field name:" box does not produce any fields when you click on the "arrow down" button.

Also, any chance to get the 'Save Previous" and "Save Next" buttons back?

Again, many thanks for making this plug-in available for v0.9.
Surf's Up!
"Columnated Ruins Domino"

foo_infobox

Reply #188 –
bluenet, thank you very much for updating this component.
Although I would prefer to have all the file infos in the lower right (like length and subsong index) + to have the filesize silhouetted against the technical infos as it is done in /\/iranas screenshot above.
And a 'displaying' option in preferences with checkboxes for e.g. "display change focus and follow cursor", "display override codepage" as it is in 0.8.3.
.....well, reflecting everything, the appearance of /\/iranas version is perfect....
Sorry, no offense, these are just my suggestions, but I still greatly appreciate your efforts, don't get me wrong here

foo_infobox

Reply #189 –
- if we edit tags in external program Reload Info button doesnt work. It has to be done through tagging>reload info from files.
- as said, "Save Previous" and "Save Next" would be very nice
- add new > and no tag list to choose from ("field name:")

foo_infobox

Reply #190 –
I have reproducable crashes with foo_infobox 2.0.1 with latest foobar2000.  It wasn't very easy to track down. 

Minimal test case known to work every time (verified with fb2k 0.9.2b2, infobox 2.0.1):

1. Add a corrupted wavpack file (dd if=/dev/random of=breakme.wv bs=8192 count=32 or whatever, any garbage named .wv would probably work) to the playlist.  Dismiss the error dialog box.  Add the corrupted file to the playlist again, and dismiss the dialog box again.

2. Use Context Menu -> "File Info" on the first playlist entry (the first `bad` file).  Close the File Info dialog, answer "No" if it asks you to save tags.

3. Add a good wavpack file to the playlist.  foobar2000 will either hang forever at this point ("Abort" box is non-functional) or crash. 

This has been tested on 3 different configurations.  This plug-in is really only somewhat useful for viewing tags, but not much for actually modifying tags when using the keyboard, requiring lots of user visual concentration from the user, such as when tabbing around the fields.  Once you get used to it, the default editor is much faster and inherently more extensible.  If you limit yourself to only using the mouse, you are really missing out on how great the built-in "Properties" functionality is.

The one thing this plug-in does better than the built-in functionality is that it it provides a quick way to scroll through a playlist to examine ReplayGain data (avoiding additional title-formatting).  It would be unfortunate to lose this functionality, and I hope this bug can be fixed. 

Another obvious problem is attempting to reload the tag data using the "Reload Info" button does not work, but this seems to be mentioned before in this thread.

Edit: Spelling.

foo_infobox

Reply #191 –
This is a suggestion I'd like to throw out there, if you dont like it fire away. I would like to see the option to "lock" a field from one song to the next.

This way I can load up File Info on SongA, type in the tag information, then if I could "lock" (click on the tag name as a toggle perhaps) fields my songs have in common such as artist, album title, etc.. I would then be able to save the tag, click on next, and those "locked" fields would automatically populate when I load SongB and I'd only need to enter the song title and track number.

I used to use a program called MediaTagger which allowed me to do this but I have since moved completely to foobar and miss this functionality.

foo_infobox

Reply #192 –
Quote from: Yotsuya on
This is a suggestion I'd like to throw out there, if you dont like it fire away. I would like to see the option to "lock" a field from one song to the next.

This way I can load up File Info on SongA, type in the tag information, then if I could "lock" (click on the tag name as a toggle perhaps) fields my songs have in common such as artist, album title, etc.. I would then be able to save the tag, click on next, and those "locked" fields would automatically populate when I load SongB and I'd only need to enter the song title and track number.

I used to use a program called MediaTagger which allowed me to do this but I have since moved completely to foobar and miss this functionality.

Correct me if i'm wrong but that sounds like unnecessary options-bloat to me, because the same can be done more intuitively by selecting multiple songs, and then editing the common fields of them. Thats where the standard-dialog is better suited than foo_infobox.
I am arrogant and I can afford it because I deliver.

foo_infobox

Reply #193 –
That is the method I currently use, however that method requires a user to work with the raw tag list instead of the convenient infobox fields.  If what I asked for is too much "bloat" then could someone perhaps suggest a better approach to manipulating multiple songs with the benefit of the infobox formatting? I'm not talking about big massive collection tagging, but just one album at a time as you rip or leech them.

foo_infobox

Reply #194 –
Don't know if it has been suggested before, but the plugin is lacking a feature which 0.83 box had:

"save and next" "save and prev."

Very often I have albums where I have to edit the title tags of all tracks. What I did was edit the title, then "save and next"... Now I have to click "update", then "next".

I see, this has been asked before. I want to emphasize it's importance.

foo_infobox

Reply #195 –
I also would like the save next/save previous things, please. :/


Regarding Yotsuya's problem, maybe that's something that could better be addressed in the 'default' tagger dialogue? Like instead of



maybe a more efficient way of doing it would be



blah blah something like that you get the idea


:shrug:
~

foo_infobox

Reply #196 –
Your second solution wouldn't be effective, because all tags are not on all files, and some people use different types of tags / non-standard ones.

foo_infobox

Reply #197 –
Quote from: Squeller on
Don't know if it has been suggested before, but the plugin is lacking a feature which 0.83 box had:

"save and next" "save and prev."

Very often I have albums where I have to edit the title tags of all tracks. What I did was edit the title, then "save and next"... Now I have to click "update", then "next".

I see, this has been asked before. I want to emphasize it's importance.

I would also like to add myself to the army of people who needs this plugin with those features from 0.8.3 couse often i get some bootlegs which i cannot tag with cddb-freedb couse simply they are not there in db.
So those features would be a really nice addon to newer builds of Foobar
 

foo_infobox

Reply #198 –
What happened to the "MOD"?  Like ..... 4211256 samples @ 44100Hz and under it is MOD [some number] = 0.  This is how you can tell a song came from a transcode...  if !=0, then transcode.

foo_infobox

Reply #199 –
Quote from: Crissaegrim on
What happened to the "MOD"?  Like ..... 4211256 samples @ 44100Hz and under it is MOD [some number] = 0.  This is how you can tell a song came from a transcode...  if !=0, then transcode.

Are you sure that you are correct..Couse on all encodings i checked now which were done from original cds with eac and lame3.90.3 aps i have that in my infobox;

12276264 samples @ 44100Hz
(mod 588 = 0)
It cant be that they are transcodings-it must be some explanation