Red Hat Bugzilla – Bug 426558
abcde aac/m3a tagging post encoding (With Patch)
Last modified: 2008-01-23 11:33:46 EST
Description of problem:
abcde is not capable of post-tagging aac/m3a tracks. Attached is a patch to use
AtomicParsley to post-tag m4a tracks. I suppose an AtomicParsley RPM will need
to be generated to -- although the patch checks for AtomicParsley and falls back
to the previous method when it is not available.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. abcde -o m3a
Please apply to FC7 and FC8.
Created attachment 290282 [details]
Patch to use AtomicParsley to Post-Tag Tracks
Created attachment 290283 [details]
Patch to the abcde Spec File
Bump the version, apply the patch, added a changelog entry.
Have you tried sending this patch upstream (email@example.com)?
It seems that abcde already contains aac/m4a tagging code using faac, it's just
disabled currently. I'd feel much more comfortable with enabling that than
adding a patch that upstream really should look into first. More info:
Could you test if that patch works for you?
A couple of quick comments about your patch:
+ # case core dumps with AtomicParsely 0.9.0
+ echo "WARING: $METAAAC Not Found Not Post-Tagging!"
s/Not Found Not Post-Tagging/not found, not post-tagging/
The METAAAC variable name sounds odd to me, I think a better choice would be
Created attachment 290313 [details]
New Patch for Post-Tagging M4A Files
o Fixed the spelling errors.
o Changed METAAAC (I was going off off METAFLAC) to ATOMICPARSLEY.
I added post-encoding tagging because of the text in the code "Quick hack
to...." I figured that post-tagging was preferred. If AtomicParsley is not
present, it falls back to inline tagging.
I'll send the patch to the supplied email address and see if it gets accepted.
Thanks for your feedback.
FYI: I sent an email on Dec. 23 to jesus.climent at hispalinux.es and have still
heard no response. I just sent another email trying to get a response to if he
will apply the patch to the main branch or not.
- If AtomicParsley is not available, an ugly error message is printed; I think
that's undesirable: which: no AtomicParsley in ($PATH goes here...)
- If it's not found, another "WARNING: AtomicParsley Not Found Not
Post-Tagging!" message is printed. Why is this worth a warning in the first
place? AFAICT faac does the job just fine. If you want to keep it, I think
some rephrasing would be in order, eg. "WARNING: AtomicParsley not found,
falling back to inline tagging."
- After applying your patch to my work in progress package by hand, if
AtomicParsley was not available, abcde did not fall back to inline faac tagging
(it did not tag at all), and failed to create the real target "Author-Albumname"
directory, leaving just the abcde.xxxxxxxx dir and all the cruft in it behind.
- The core dump commentary in the patch does not give me a warm fuzzy feeling
Having played around with m4a tagging for a while now and seeing that faac is
the only supported m4a encoder in abcde, I must say that I fail to see the
reason to introduce AtomicParsley support. faac appears to do the job just
fine, whereas AtomicParsley is another dependency, adds more code, and the
implementation seems slightly broken at the moment.
If you wish to continue improving the patch, please rebase it with abcde
184.108.40.206-5 which will soon hit F8 testing updates and the devel repository. In
the meantime, you can grab it from CVS or
Thanks for the feedback. All good points.
Let's drop this patch/bug in favor of enabling/using faac tagging.
Ok, let's do that, thanks for the quick reply.