Changes Made to TAG.EXE, Tags from text file & OptimFrog support Options

[Synthetic Soul]

2006-02-08 11:53 :
2.0.45 released. As well as --tocue, --tocuen and --tocuea, I have now added the --paranoid switch which will cause warnings and non-critical errors to return a non-zero return code, so that this can be picked up in a script. Thanks to R Hannes Beinert for the suggestion and patch.

2005-12-08 13:24 :
2.0.45b9: Added code to fix memory leak. Report and code kindly provided by Steve Vibert.

2005-12-08 13:24 :
2.0.45b8: Added --tocue, --tocuen and --tocuea. libVorbis 1.1.2 & libOgg 1.1.3.

2005-04-21 22:00 BST:
If you downloaded Tag 2.0.43 before 19:30 BST you may want to download it again.

See this post for more info.

2005-04-21:

a small bug report for 2.0.42. View APE 3.98 and higher files' tags and the details field is incorrect, for example: "Details: 24 Hz, playtime 42274:53:30". The 24 Hz part is always constant.

Version 2.0.43 has been uploaded.

v3.98+ APE files are now detailed correctly. Also, the 10KB limit when using the -f switch has been removed.

Update: wapet has also been updated now, so that the 10KB limit no longer applies. wapet 0.5 available here.

2005-02-07:
I thought I may as well record on forum that I have updated Case's Tag with libFLAC 1.1.2. You can get it here.

It now uses libFLAC 1.1.2, libOgg 1.1.2 and libVorbis 1.1.0 - all the most recent releases.

I see from the FLAC changelog that there have been some changes relevant to VORBIS tagging, so I thought I may as well.

Original Post:
This topic explains the history of this amendment

EAC+MAC+TAG+PAR2

There is a little information, and all the downloads here:

http://synthetic-soul.co.uk/tag/

I hope someone else finds this useful as well.

wapet is also now available, with the additional -f switch.

This post has been edited by Synthetic Soul: Feb 8 2006, 12:59

[Synthetic Soul]

Thinking about it, I think this will be because Tag understands MP3 files, but has no idea how to decypher TAK files (or OptimFrog, WavPack, and maybe more). Part of the extended information involves writing the duration of the track, and Tag can't retrieve that as it doesn't know how to read the header.

That said, I believe using -1 for the duration is valid (certainly for streaming files), so I may see if I can get Tag to use -1 for the duration if it can't decypher the format, and use the meta data info that it should surely know about.

I'll add it to my list of crap to stop me from doing proper work...

Edit: FYI I have confirmed this. If Tag cannot obtain a duration it does not write the line at all. I'll report back here if I can make the change.

This post has been edited by Synthetic Soul: May 2 2007, 10:16