Frank Blendinger | 5 May 2008 16:09
Gravatar

Year field gets automatically "fixed", loosing month and day

Hi,

I recently discovered the following behaviour:

When selecting files (only tried with MP3 files) that have their
``year'' field set to something not-so-standard, i.e. ``2008-01-28'',
Easytag automatically "fixes" this to ``2008'' (it probably gets that
value from the id3v1 tag). How can I stop it from doing so?

I guess such a value is not really standard conformant, but I must say
that I really began to like those. I began using the Picard tagger to
automatically tag my music with MusicBrainz information, and for many
releases there is a full release data available and Picard sets the
``year'' (or is it actually ``date''?) field to this. The client of my
choice also displays those values just fine (which makes sorting by date
more accurate when you have more than one release by an artist from the
same year). The id3/id3v2 command line tools display just the year for
those files.

I still use EasyTag for all my manuall tagging and it is really annoying
that it tries to "fix" the dates. Most of the time I just want to fix
some errors in other fields, but keep the date value like it is. There
is no way to do so currently, at least I haven't found one. I think this
behaviour should be at least optional.

Greetings,
Frank

--

-- 
Frank Blendinger | fb(at)intoxicatedmind.net | GPG: 0x0BF2FE7A
(Continue reading)

Marcin Zajączkowski | 6 May 2008 22:13
Picon
Favicon

Re: Tags caching

On 2008-04-24 18:17, Jérôme COUDERC wrote:
> The file was read only when loading the file (when browsing 
> directories). Then, tag data were stored in memory. The problem of 
> performance was due to the managing of the main list.
> But when version are you using, because perfomance enhancements were 
> made in the last versions...

If the list is already kept in a memory, my proposition isn't very 
attractive. I've updated from 2.1.4 to 2.1.5 (it was a long time ago 
when I was using 2.0 branch, but you are probably right that EasyTag is 
now faster) and there is still some delay. Its length depends on number 
of songs in the current directory. It's about 0,6-0,8s for ~300 mp3 
files. I noticed that even for directory with only 3 files there is a 
small and completely acceptable (but still visible) delay, so maybe it's 
time requires to refresh/update widgets in GUI?
Another reason could be that my computer isn't very fast - Athlon XP 
1,8+ (~1,5GHz). I will try to test on Intel Core 2 Duo 2,2GHz for 
comparison.

Regards
Marcin

> Marcin Zajączkowski wrote, the 09/04/2008 19:34 :
>> Hi,
>>
>>
>> Recently I review my mp3/ogg library and add/fix tags. Usually
>> everything is ok and I only have a look on it. Because reading of
>> mp3/ogg file takes awhile there is a visible delay after pressing DOWN
>> key. It's quite unpleasant when you have a lot of files.
(Continue reading)

Jérôme COUDERC | 7 May 2008 23:35
Picon

Re: can't load images with JPG/PNG extension (uppercase)

Hi,

    Indeed, the problem is due to the case of the extension.

Will be fixed in the next version

Regards,
Jerome

Michał Smoczyk wrote, the 29.04.2008 22:57 :
> Jérôme COUDERC napisał(a):
>   
>> Hi,
>> Strange, as I haven't this problem with the version 2.1.4, as you can see in the 
>> screenshot. The version used is 2.1.4 on Windows XP
>>     
>
> Maybe Windows system don't bother about uppercase/lowercase, but Linux
> does?
>
>   

--

-- 
EasyTAG - Tag editor for MP3 and Ogg Vorbis files
http://easytag.sourceforge.net
--
Jerome COUDERC <easytag <at> gmail.com>

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
(Continue reading)

Peter Wurmsdobler | 12 May 2008 16:54

tagging classical music flac files

Hello,

First of all many thanks for all developers for this excellent piece of 
software. I have tried out other, "commercial" software and find that 
easytag does an excellent job.

I am about to rip all my classical, jazz and rock CDs onto a server as 
flac files using EAC into a simple directory structure. This target 
structure reflects mostly the CDs in three levels: genre, composer (or 
artist), and CD, with optional sub directories for multiple CDs, e.g. 
Classical / Beethoven / Piano-Sonatas-Brendel / CD* / *.flac, or Jazz / 
Keith Jarrett / Koeln Concert/ *.flac

To start with, I have ripped and tagged a 50+ CDs in order to get an 
idea of the requirements. What I would like to get at, is that a music 
player can then create a view depending on meaningful tags. In 
particular, I would like to use two additional tags: WORK for the work, 
the oeuvre, and TYPE for the work type such as string quartets. So I 
would like to see a hierarchy:

GENRE	COMP.	TYPE	WORK	TITLE
Classical
	Beethoven
		String Quartets
			Quartet No.132
				Allegro ...
				:
			:

		Piano Sonatas
(Continue reading)

Peter Wurmsdobler | 12 May 2008 17:35

Re: tagging classical music flac files

Hello Daniel,

> and what you would do about it.  It seems as if the predefined tags 
> don't ever consider classical music.

It appears that you are right in that most tagging software and music 
players are geared towards pop music and the existing tags do not lend 
themselves to classical music. Some people try to bend to the pop-world 
rules an say you have to re-use this tag as that etc, but I do not want 
to do that. Technology should bend to our needs, not the other way round.

In essence I see three aspects: First, ripping of CDs into flac files. 
Second, define sensible views. And third define a tag model that allows 
for various meaningful representations. The first bit is easy. The 
second bit contains perhaps some input for the third.

As I mentioned before, for very "buzy" composers, like Bach, it would be 
nice to have a view that allows three-four levels. Other composers can 
do with fewer levels.

And then there is the aspect of multiple performers. I have Milhaud's Le 
boeuf sur le toit once with Karajan, and another one with Guidon Kremer. 
I have all Beethoven sonatas with Brendel, and a few with Giles. It 
should then be possible to have two views:

Performer view:

PERF.	COMP.	TYPE	WORK	TITLE
Giles
	Beethoven
(Continue reading)

Peter Wurmsdobler | 12 May 2008 19:10

Re: tagging classical music flac files

Hello,

To partially answer myself, I have looked through the code, in 
particular through flac_tags.c. I can see that only a minimum set of 
tags is implemented. ogg_tags.c list all potential tags, but only 
implements a minimum set, too.

 From what I know flac allows several metadata sections. How difficult 
is it to add more tags to flac_tags.c, perhaps in an additional section? 
Would they automatically appear in the tag view? Would it be necessary 
to tag these tags as extra?

Regards,
peter

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
Trond Husø | 12 May 2008 20:51
Picon
Picon

Re: Edit custom tags


> Marco Jackel wrote:
> >> I would go one step further. I would be great to edit every tag you want
> >> and define your own tags. For example this is possible in mp3tag
> >> (http://www.mp3tag.de).
> > 
> > Are there any plans to implement this feature? I'm using a few custom tags,
> > that I cannot edit with easytag (track-replaygain, album-replaygain,
> > musicmaic-data, musicmagic-fingerprint, Album-Artist (tpe2),
> > itunes-compilation).
> > 
> This has been brought up before.
> 
> Quick answers for you:
> Supported tags are hardcoded so it would take a *major* rework of the
> code to support ad-hoc tag editing
> 
> I don't believe there are plans to do it.
> 
> When, occasionally, I've wanted to edit custom tags I've used Ex Falso
> (Quod Libet's tag editor).
> 
> ciao
>    Mark
> 
Hi Mark and Marco,

I think Marcos suggestion is a good one, so I wonder one thing: Would it
be easier for the program if the supported tags where "hardcoded" in an
XML-file, and so users could add other tags by adding XML-files, or
(Continue reading)

Frode Slettum | 17 May 2008 12:16

4 suggestions for easytag

Hope this is a good place to come up with a few suggestions of new features for Easytag. 

First, Easytag is in my experience the best mp3 tagging software out there, including commercial
programs. 

However, it can allways get better ☺ Foursuggestions from me: 

1. I spend a lot of time waiting for an album to be saved before I can work on the next one. I think it would be
great if the saving process would stay in a queue that saved files in the background while I was tagging new
albums. Many people tag files over the network and I can’t believe I’m the only one that would love this
feature. 

2. I just figured that sometimes, it’s better to fill out i.e tracknames manually, and not use the ”fill
tag” – feature. Let’s say that this is a mp3 file in an album: 01 – Prodigy - Their Law.mp3, and it
misses the TITLE. When I start to type ”Their Law” in the TITLE field it would suggest it based on parts
of the filename. The same if I manually start typing ”Prodigy” in the ARTIST field, it would suggest
that. Just like moderen browsers do. Not a big deal, but maybe a thought?

3. ”Pictures” is now placed in a separate tab together with ”Common”. For most
people/resolutions there are plenty of space below the Common area. At least for me, it would be much
better to have the picture area below ”common” so I can see both at the same time. If an album is missing a
picture, I’ll see it right away without clicking the ”Picture” tab. At least it should be possible
to configure it that way. 

4. I have a 1920x1200 resolution screen, and even then I get to little width-space. After the middle part of
the screen now displays id3 information instead of just filenames (a nice new feature btw) I have to scroll
a lot to see it all. It’s not necessarely a better thing to the file structure area (Tree) below/over the
middle area, but it should maybe be possible to align it that way. 

Best regards
(Continue reading)

Doruk Fisek | 21 May 2008 22:01
Picon
Gravatar

Re: 4 suggestions for easytag

Sat, 17 May 2008 12:16:49 +0200, "Frode Slettum" <frode <at> slettum.com> :

> 1. I spend a lot of time waiting for an album to be saved before I
> can work on the next one. I think it would be great if the saving
> process would stay in a queue that saved files in the background
> while I was tagging new albums. Many people tag files over the
> network and I can’t believe I’m the only one that would love this
> feature.

Not that I'm against this suggestion but why don't you just run two
instances of Easytag at the same time?

                   Doruk

--
FISEK INSTITUTE - http://www.fisek.org.tr

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Easytag-mailing mailing list
Easytag-mailing <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/easytag-mailing
solsTiCe d'Hiver | 22 May 2008 12:51
X-Face
Picon
Gravatar

[easytag 2.1.5] does not compile (iwht gcc 4.3)

hi.

when i try to compile easytag 2.1.5 i got that error:

g++ -DHAVE_CONFIG_H -I. -I../.. -DLOCALE=\"/usr/share/locale\"    -march=i686 -mtune=native -O2 -pipe
-MT 
c_wrapper.o -MD -MP -MF .deps/c_wrapper.Tpo -c -o c_wrapper.o c_wrapper.cpp
In file included from /usr/include/id3/utils.h:38,
                 from /usr/include/id3/tag.h:35,
                 from c_wrapper.cpp:34:
/usr/include/id3/id3lib_strings.h: In static member function 'static unsigned 
char* std::char_traits<unsigned char>::move(unsigned char*, const unsigned 
char*, size_t)':
/usr/include/id3/id3lib_strings.h:87: error: 'memmove' was not declared in 
this scope
/usr/include/id3/id3lib_strings.h: In static member function 'static unsigned 
char* std::char_traits<unsigned char>::copy(unsigned char*, const unsigned 
char*, size_t)':
/usr/include/id3/id3lib_strings.h:91: error: 'memcpy' was not declared in this 
scope
make[3]: *** [c_wrapper.o] Error 1
make[3]: Leaving directory 
`/home/solstice/abs/easytag/src/easytag-2.1.5/src/id3lib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/solstice/abs/easytag/src/easytag-2.1.5/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/solstice/abs/easytag/src/easytag-2.1.5'
make: *** [all] Error 2

i guess it's because of g++ 4.3 that's more strict for header declaration. i 
(Continue reading)


Gmane