Hydrogenaudio Forums

Lossy Audio Compression => AAC => AAC - General => Topic started by: reardon on 2005-11-17 19:32:22

Title: AAC/M4A command line tagger
Post by: reardon on 2005-11-17 19:32:22
I saw tg.exe but it seems like it has int'l problems, and doesn't support binary fields (COMPILATION, etc)

Does anyone know if this exists somewhere?

+Reardon
Title: AAC/M4A command line tagger
Post by: Lego on 2005-11-17 19:35:53
Foobar2000 (http://www.hydrogenaudio.org/forums/index.php?showtopic=28700)
Title: AAC/M4A command line tagger
Post by: reardon on 2005-11-17 19:52:55
Quote
Foobar2000 (http://www.hydrogenaudio.org/forums/index.php?showtopic=28700)
[a href="index.php?act=findpost&pid=342623"][{POST_SNAPBACK}][/a]


You're kidding, right? 

One, it's hilariously overkill.  Two, commandline TAGGER??  Three, foobar screws any tag it doesn't understand... compilation, cover art, etc.  Very frustrating, and it appears like 0.9 won't address, despite many requests from many users for foobar to at least leave other tags (notably those *standard* tags used by iTunes).
Title: AAC/M4A command line tagger
Post by: torok on 2006-05-09 23:05:25
I found this thread on Google and have the same question.  I know about atomic parsley, but just wondering if there are any others.
Title: AAC/M4A command line tagger
Post by: reardon on 2006-05-11 00:43:59
I found this thread on Google and have the same question.  I know about atomic parsley, but just wondering if there are any others.


I disagree strongly with the approach AP uses...it squashes free space, so tag writing is painfully slow.  If these people knew how much more space was being wasted at the filesystem level due to overhead and cluster glut, they'd probably try to rewrite the filesystem to save another 0.5%.  Sigh.

I am taking to use the tool in the MP4Tools package at Rarewares.

+Reardon
Title: AAC/M4A command line tagger
Post by: sh1leshk4 on 2006-05-11 09:55:54
AP is 'painfully slow'?
Have you actually tried using it?
Title: AAC/M4A command line tagger
Post by: reardon on 2006-05-11 22:06:19
AP is 'painfully slow'?
Have you actually tried using it?


Um, well, yes, rewriting every file from scratach just to create a tag is painfully slow.  I don't buy into the strategy.

Also, unfortunately, I can't get it working with UTF8 tags.  I have used both the Win32 version and the two Cygwin versions.  I can't get the Cygwin-UTF8 version to write non-ASCII (7bit) tags properly.  iTunes and other apps do not recognize any characters beyond ASCII.

I personally don't have much need of UTF8, probably only about 3-5% of my music needs, it's mostly just the classical stuff.  But it's important enough.

It hasn't been updated since early Feb.  Anyone know if there is active development.  I may be able to descend into it and get the Win32 version properly supporting UTF8.

+Reardon
Title: AAC/M4A command line tagger
Post by: anaxamander on 2006-05-12 01:05:00
Anyone know if there is active development.  I may be able to descend into it and get the Win32 version properly supporting UTF8.

http://sourceforge.net/forum/forum.php?thr...forum_id=514419 (http://sourceforge.net/forum/forum.php?thread_id=1454986&forum_id=514419)

utf8 support.

http://svn.sourceforge.net/viewcvs.cgi/ato.../atomicparsley/ (http://svn.sourceforge.net/viewcvs.cgi/atomicparsley/trunk/atomicparsley/)

should show you that there has been activity since Feb.
Title: AAC/M4A command line tagger
Post by: reardon on 2006-05-12 23:19:12
http://sourceforge.net/forum/forum.php?thr...forum_id=514419 (http://sourceforge.net/forum/forum.php?thread_id=1454986&forum_id=514419)

utf8 support.

http://svn.sourceforge.net/viewcvs.cgi/ato.../atomicparsley/ (http://svn.sourceforge.net/viewcvs.cgi/atomicparsley/trunk/atomicparsley/)

should show you that there has been activity since Feb.


Ok, I just played with it.  It's broken for UTF8, look at my post on that forum.  Also, requiring codepage 65000 is wrong, he should just accept the chars as they come in.  It's up to the script writer or user to switch to 1252 or 65001 or whatever if they need to enter those characters.  But that doesn't effect display, and further should not affect input if characters are available in the chosen codepage.  That said, staying in 65001 is the safest.  In any case the app itself shouldn't care, rather it just affects the way CMD.EXE interacts (for passing in params and redirection).

+Reardon
Title: AAC/M4A command line tagger
Post by: reardon on 2006-05-26 23:34:59
Ok, I just played with it.  It's broken for UTF8, look at my post on that forum.  Also, requiring codepage 65000 is wrong, he should just accept the chars as they come in.  It's up to the script writer or user to switch to 1252 or 65001 or whatever if they need to enter those characters.  But that doesn't effect display, and further should not affect input if characters are available in the chosen codepage.  That said, staying in 65001 is the safest.  In any case the app itself shouldn't care, rather it just affects the way CMD.EXE interacts (for passing in params and redirection).

+Reardon


For anyone following, this tool has been updated for Win32, see the links above.
Title: AAC/M4A command line tagger
Post by: kwanbis on 2006-05-27 04:27:24
For anyone following, this tool has been updated for Win32, see the links above.

haven't checked, but latest version allways errorlevels to 1, instead of 0.
Title: AAC/M4A command line tagger
Post by: PiezoTransducer on 2006-06-05 09:47:23
I just grabbed the Nero Digital Audio (http://www.nero.com/nerodigital/eng/Nero_Digital_Audio.html) pack again, and found neroAacTag.exe inside. Perhaps this may be of some help.
SimplePortal 1.0.0 RC1 © 2008-2020