search

lebauce / quodlibet

Automatically exported from code.google.com/p/quodlibet
1 stars 0 forks source link

Ex Falso: Inputting tags is painful #44

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
1. Assume a twenty-track tagless album.

2. Try to input TITLE tags for each of the files.

3. Get wrist injuries.

No, really. There should be a way to add tags sequentially without _too_
much effort. Personally I'd like a simple big text area where I can just
type one tag per line, ie.

Looking for Someone
White Mountain
Visions of Angels
Stagnation
Dusk
The Knife

=> Select "Add as: TITLE"
which would then apply the tags to the files.

The current "most efficient" way I've found is this:

1. Select first file in file selector
2. alt-A (Add tag)
3. type "TITLE" <return>
4. type title of a track
5. down arrow (next file)
6. goto 2

(yes, yes, I know about cddb and musicbrainz but they don't always have my
albums)

Original issue reported on code.google.com by hha...@gmail.com on 3 Nov 2008 at 6:46

GoogleCodeExporter commented 9 years ago 
Perhaps you could make a plugin; see for example the import side of 
importexport.py
for a basis.

Original comment by mur...@gmail.com on 9 Nov 2008 at 7:46

GoogleCodeExporter commented 9 years ago 
I don't know python, but I wrote a simple perl script which asks for tags in
succession and calls metaflac. It's a good stopgap.

Original comment by hha...@gmail.com on 26 Nov 2008 at 2:14

GoogleCodeExporter commented 9 years ago 
Addendum: Editing pre-existing tags is arduous, too. Whatever solution is done 
to fix
this should think of editing, too.

Original comment by hha...@gmail.com on 13 Dec 2008 at 11:34

GoogleCodeExporter commented 9 years ago 
What about option like 'edit next tag on enter'? And (same option, probably), 
'edit
next song's tag on enter'.
Also, set of predefined tags (title/artist/album/date, probably) visible (and
highlighted) even if there's no such tags in file — for faster editing 
(erm… I
remember this problem mentioned somewhere else. Don't remembet the result 
though).
And, hotkeys for jumping to next/previous song in tag editor could be solution 
of op
problem as well, allowing to press 'enter, <hotkey>, enter' to edit first (or 
same as
edited previously, if possible) tag of next song in list.

Original comment by hoverh...@gmail.com on 7 Jan 2009 at 12:59

GoogleCodeExporter commented 9 years ago 
How about an Edit option in the context menu for editing multiple tags, that:

If one tag is selected, display a window like the first attachment.  The tab not
shown has a multiline text edit box. In the tab shown, one can select $n lines 
and
paste $n lines from the clipboard, overwriting the selected lines.

If multiple tags are selected, display a window like the second attachment.  
Copying
and pasting works as above, where you can select $n lines.  The clipboard 
should have
tab-delimited text of the $n lines and $t columns, where $t is the number of 
tags
you're editing.

Original comment by iain.dal...@gmail.com on 8 Jan 2009 at 7:04

Attachments:

GoogleCodeExporter commented 9 years ago 
hoverhell:
> Also, set of predefined tags (title/artist/album/date, probably) visible (and
> highlighted) even if there's no such tags in file — for faster editing 
(erm… I
> remember this problem mentioned somewhere else. Don't remembet the result 
though).

That was bug #60. It was wontfixed, "should be implemented as a plugin"

Original comment by hha...@gmail.com on 8 Jan 2009 at 1:57

GoogleCodeExporter commented 9 years ago

Original comment by steven.strobe.cc@gmail.com on 21 Jun 2009 at 7:45

GoogleCodeExporter commented 9 years ago 
What about a new tab like this one: http://666kb.com/i/bekvtdha2otaycneh.png
Or merge it into Track Numbers, and display extra stuff for tracknumber 
underneath
the selection box.

Original comment by reiter.christoph@gmail.com on 1 Dec 2009 at 11:28

GoogleCodeExporter commented 9 years ago 
What I would like is a multi-line text entry where you can paste a track 
listing taken from the web (e.g. 
amazon.com), or from a text file, and then parse it line-by-line just like you 
can with tag markup in the 
«Tags from Path» Tab. 

It could default to <title> so you can directly enter title tags, one-by-one 
just hitting enter like in a text 
editor, and then there is a preview button to validate what you entered just 
like in the other tab.

Bonus points for line numbers in front of the lines in the edit control. But I 
suppose that would 
necessitate a dependency on gtksourceview, or something.

Original comment by towolf on 1 Dec 2009 at 11:45

GoogleCodeExporter commented 9 years ago 
Issue 73 has been merged into this issue.

Original comment by steven.strobe.cc@gmail.com on 19 Jan 2010 at 12:17

GoogleCodeExporter commented 9 years ago 
To relieve the pain a bit until the feature is added, you can select the 
tracks, go
to "Tags from Path", enter <title> as the pattern, and then change the titles to
whatever you want. You still need to type or copy every title yourself, but 
it's a
lot easier than editing the tracks separately.

Original comment by arume...@gmail.com on 23 Jan 2010 at 9:44

GoogleCodeExporter commented 9 years ago 
Tag parser plugin: Basically what towolf described above. Most parts copied from
tagstopath. (not heavily testet.. could eat your tags)

Original comment by reiter.christoph@gmail.com on 8 Feb 2010 at 2:33

Attachments:

GoogleCodeExporter commented 9 years ago 
Sorgot to set utf8 after adding the copyright..

Original comment by reiter.christoph@gmail.com on 8 Feb 2010 at 2:41

Attachments:

GoogleCodeExporter commented 9 years ago 
Christoph, you jewel! That’s exactly what I had in mind.

But, being an insolent brat, of course I bring nitpicks.

1. Can we make the headers in the treeview resizable?
2. It’s a gtk.Dialog, but the Save button is in the main area, 
   not in the (empty) button strip down low.
3. I’m aware of the space contraints and I find your two tab 
   approach logical. But it somehow seems to belong in the tagging
   window. It feels expatriated like that in the songs menu.
   Perhaps I can whip up a concept for that and we iterate the design.
   Maybe even a patch, but that would take me long, I guess.

But I sure am psyched about this.

Original comment by towolf on 8 Feb 2010 at 10:37

GoogleCodeExporter commented 9 years ago 
Christoph, what do you think about this concept? I know that opening yet 
another 
window isn’t all that attractive.

Is there a way to make part of the string a no-op, by the way?

Original comment by towolf on 10 Feb 2010 at 3:55

Attachments:

GoogleCodeExporter commented 9 years ago 
I have to say that I didn't think of the plugin to be the best solution for this
problem. More like a temporary workaround... 

Like I said before, it's mostly copied from tagstopath and I can't really 
change the
look of it.. because I would have to pull even more of exfalso's code into it.. 
not
an option. Noop is the same btw: <~>. I don't think text parsing is important 
enough
to be a new tab in the main window... but I will try to get it stable and 
commit it.

I will try to come up with a working solution for inputting tags in the next 
days..

Original comment by reiter.christoph@gmail.com on 10 Feb 2010 at 4:36

GoogleCodeExporter commented 9 years ago 
“I don't think text parsing is important enough to be a new tab in the main 
window... 
but I will try to get it stable and commit it.”

That makes sense. You should definitely commit to the plugins repo. Let me 
suggest that 
you change the name, because ›Tag Parser‹ is not very descriptive. Perhaps 
»Tags from 
Track Listing« or similar.

Original comment by towolf on 13 Feb 2010 at 11:30

GoogleCodeExporter commented 9 years ago 
I'm in favor of a new plugin type which adds a new tab to the edit tags window 
to
maximize reuse. As we work out the details of the new plugin API, this can be 
elaborated.

Tags from text is useful, but it doesn't solve all of the problems mentioned 
above.
Here's my take, which could either replace or augment the existing 'Edit Tags' 
tab,
and would be in addition to tags from text. Each blank line represents a new 
list item.

=========

- Title                             [Different across 10 songs]

|   01 - Turnin' on the Screw.flac  Turnin' on the Screw

|   02 - Sick, Sick, Sick.flac      Sick, Sick, Sick

|   03 - I'm Designer.flac          I'm Designer

+ Artist                            Queens of the Stone Age

+ Album                             Era Vulgaris

- Writer                            [Different across 10 songs]

|   01 - Turnin' on the Screw.flac  Joshua Homme
                                    Troy Van Leeuwen
                                    Joey Castillo

|   02 - Sick, Sick, Sick.flac      Joshua Homme
                                    Troy Van Leeuwen
                                    Joey Castillo
                                    Chris Goss

|   03 - I'm Designer.flac          Joshua Homme
                                    Troy Van Leeuwen
                                    Joey Castillo

- Genre                             Hard Rock
                                    Stoner Rock

|   01 - Turnin' on the Screw.flac  Hard Rock
                                    Stoner Rock

|   02 - Sick, Sick, Sick.flac      Hard Rock
                                    Stoner Rock

|   03 - I'm Designer.flac          Hard Rock
                                    Stoner Rock

=========

Pressing [Enter] moves you to the next tag; [Ctrl]-[Enter] brings up the tag 
edit
box. The standalone edit box will default to a single-line entry, but clicking 
on a
button with text like "Use multiple tags" or something more intuitive will 
switch to
a multi-line entry to use multiple values for a single tag. (Blank lines will be
stripped, and if a tag already has multiple values the multi-line entry will of
course be used.) Attention would be paid to keyboard usage to make it efficient.

Thoughts?

Original comment by steven.strobe.cc@gmail.com on 20 Feb 2010 at 5:16

GoogleCodeExporter commented 9 years ago 
The above sounds quite good and useful

Original comment by the.sub....@gmail.com on 27 Feb 2010 at 10:46

GoogleCodeExporter commented 9 years ago 
I concur. I like using ex falso because it's very stable, but editing tags 
manually is a pain and it's slow. There not even a Ctrl+S shortcut to speed up 
the fields editing (clicking on the save icon get annoying after a couple of 
times). I could maybe set an accelerator maybe - I don't know?

I don't try the plug-in above. When I need to edit tags manually, I use 
puddletag. It is super fast. I really like both ex falso, and puddletag. And, 
in my opinion, this request should not be an external plug-in. It should be in 
the core.

Original comment by nom...@gmail.com on 19 Jul 2011 at 2:32

GoogleCodeExporter commented 9 years ago 
Plugin update to make it work with QL 2.4/trunk..

Original comment by reiter.christoph@gmail.com on 16 Apr 2012 at 11:02

Attachments:

GoogleCodeExporter commented 9 years ago 
Slightly relevant to this thread: in revision 08eb995bca10 added a preferences 
checkbox to auto-save changes when moving between files during editing of 
multiple files. Use at your own risk, etc etc.

Original comment by nick.bou...@gmail.com on 10 Jun 2012 at 6:35

GoogleCodeExporter commented 9 years ago 
Resync with trunk..

Original comment by reiter.christoph@gmail.com on 16 Sep 2012 at 6:08

Attachments:

GoogleCodeExporter commented 9 years ago 
Because Google Code is going away [0] we've moved this bug tracker to GitHub.

This issue is now available at

https://github.com/quod-libet/quodlibet/issues/44

In case you are still interested in this issue and have a GitHub account, you
can subscribe to the new issue using the "Subscribe" button on the right hand
side of the page.

[0] http://google-opensource.blogspot.co.at/2015/03/farewell-to-google-code.html

Original comment by reiter.christoph@gmail.com on 16 Mar 2015 at 11:17