Difference between revisions of "History:Intuitive Picard Interface"

From MusicBrainz Wiki
(typos. there's an incomplete sentence though :) (Imported from MoinMoin))
(completed sentence and added options (Imported from MoinMoin))
Line 18: Line 18:
 
# do a lucene lookup for each album and load the metadata of the first match into the right pane, if the match is better than n%  
 
# do a lucene lookup for each album and load the metadata of the first match into the right pane, if the match is better than n%  
 
# move the files over to the right, if they match better than m% (> n%)  
 
# move the files over to the right, if they match better than m% (> n%)  
# for the remaining files (ungrouped or  
+
# for the remaining files (ungrouped or no exact enough lucene match)
 
## analyze them and create a PUID  
 
## analyze them and create a PUID  
 
## lookup that PUID   
 
## lookup that PUID   
Line 25: Line 25:
  
 
While doing this Data should comment all his actions in a log window. Ideally each action could be reverted (unless something has been done on top of it). If you want to be really cool, then each file will have an action history, and you could undo steps for each file.   
 
While doing this Data should comment all his actions in a log window. Ideally each action could be reverted (unless something has been done on top of it). If you want to be really cool, then each file will have an action history, and you could undo steps for each file.   
 +
 +
Also the different aspects of the AI should be switchable via options:
 +
* Group files into albums [yes/no] if at least [n] files have the same album tag.
 +
* Lookup albums by tag (Lucene enabled text search) [yes/no]
 +
** Required match to automatically load album data into Picard [n%]
 +
** Required match to automatically assign files to album [m%]
 +
 +
* Lookup files by PIUD (acoustic fingerprint) [yes/no]
  
 
[[Category:To Be Reviewed]] [[Category:Development]]
 
[[Category:To Be Reviewed]] [[Category:Development]]

Revision as of 16:32, 27 March 2006

RobertKaye and DonRedman have started to work an an intuitive user interface for the PicardTagger, because the current one is, well, shitty.

The new interface has two panes that each has a tree-like structure. The left pane represents unmatched stuff, and the right one matched stuff.

This means you load files into the left pane. You can group them by album there, and analyze them so that they get PUIDs, but that is about it.

You can load metadata from MusicBrainz into the left pane, and then you can match files by dragging them (or the whole album group) into the left pane.

PicardMockup2.jpg

Automatization

Of course the cool stuff is that all this should be mostly automatic.

Picard will have an AI called "Data" that will try the following:

  1. read the metadata of new tracks
  2. if at least n files have the same album tag, group them.
  3. do a lucene lookup for each album and load the metadata of the first match into the right pane, if the match is better than n%
  4. move the files over to the right, if they match better than m% (> n%)
  5. for the remaining files (ungrouped or no exact enough lucene match)
    1. analyze them and create a PUID
    2. lookup that PUID
    3. load that track's metadata into the right pane
    4. move the track into the right pane

While doing this Data should comment all his actions in a log window. Ideally each action could be reverted (unless something has been done on top of it). If you want to be really cool, then each file will have an action history, and you could undo steps for each file.

Also the different aspects of the AI should be switchable via options:

  • Group files into albums [yes/no] if at least [n] files have the same album tag.
  • Lookup albums by tag (Lucene enabled text search) [yes/no]
    • Required match to automatically load album data into Picard [n%]
    • Required match to automatically assign files to album [m%]
  • Lookup files by PIUD (acoustic fingerprint) [yes/no]