Re: Adding a Conductor field in EasyTAG

[Budge <ajebay errichel co uk>]

Hi David,
Thanks for the information.  Having finally moved over to wide LCD 
display I have no problems with screen real estate.  In fact on the 
right hand side of the EasyTAG screen there is room below "Encoded by:" 
for several additional fields.

As you know I am not a coder and so am not aware of why you suggested 
another tab for less common fields but before going down this path let 
me share my views on the present configuration and what might be termed 
less common.

For example, I seldom use Comments: because they are not displayed on my 
control point or renderer.  Similarly Orig. artist: which for classical 
music would only be of interest to a specialist.  Encoded by: is only of 
interest when trying to sort out and compare encoders etc.  Finally I 
never use Copyright or URL:  If looking for real estate I would 
sacrifice some of these before tabbing.

My preference would be to have an option as to which fields to display 
or turn on rather than a tab.  That would enable me to build my screen 
to suit may needs and obviate the need for tabbing which would be very 
inconvenient during a working session.

With regard to "unknown" fields I assume you mean unrecognised by 
EasyTAG.  There are well over 60 ID3v2.4 frames so it is quite possible 
for a file to have tags such as Conductor (TPE3) which do not coincide 
with those fields which are presently shown on EasyTAG, but how do you 
deal with these now?

Meanwhile how may I add Conductor please?
Regards,
Budge.

On 15/03/17 17:02, David King wrote:
> Hi Budge
>
> On 2017-03-15 14:31, Budge <ajebay errichel co uk> wrote:
> > I see there was some discussion on adding a new field back in 2011 but
> > surely I am not the only person since then to ask this.  For classical
> > music a Conductor tag would be a great improvement.  Is there any chance
> > it can be done?
>
> In principal, adding an extra field for conductors is really easy.
> However, there needs to be some thought about reducing the number of
> fields that are currently shown in the UI by default, and probably some
> way to show all fields, including those that are not currently known to
> EasyTAG. A quick fix would be to add a third tab for "less common"
> fields, but this does not solve the problem of handling the unknown fields.