From: SourceForge.net <no...@so...> - 2010-07-04 17:31:34
|
Feature Requests item #1985551, was opened at 2008-06-05 15:28 Message generated for change (Comment added) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350290&aid=1985551&group_id=290 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Frontends (lame/mp3x/...) Group: None Status: Open Priority: 1 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: lame --pass-ID3-tags-unscathed Initial Comment: It is terrible that $ lame -V 9 big.mp3 small.mp3 doesn't copy the ID3 tag of big.mp3 into small.mp3. All I wanted to do was to reduce the size of some .mp3s to make more room on my player, and now I have to write a whole script to $ eyeD3 --no-color > tmp big.mp3 $ lame `myscript tmp` -V 9 big.mp3 small.mp3 put the tags back. ---------------------------------------------------------------------- Comment By: http://subharo.myopenid.com/ () Date: 2010-07-04 17:31 Message: There is funding available from a generous donor (D. Pignon) to implement this feature request. Interested developers can apply to me directly (Subharo Bhikkhu, su...@fo...), the technical contact for this bounty. Preference will be given to a developer who has already made substantial contributions to LAME, especially Robert Hegemann. Upon selection of a developer (made on July 25th, 2010, 3 weeks from now, if Robert doesn't respond sooner), $100 will be paid up front, via PayPal, as a gesture that this bounty is legitimate. The remaining $100 will be paid upon completion. Here is a careful definition of what "completion" means, for collecting the full bounty: 1) The final code must be merged into the mainline code (and thereby become part of the official release, so it can be packaged downstream into the next version Ubuntu). Once I can check out (over CVS) and verify the fix in the mainline code, then payment can be released. I'm willing to check out the code to verify and test it before it gets into the mainline branch. 2) After re-encoding/converting an MP3, the existing ID3 tags must be preserved EXACTLY as were are before the encoding. That is to say, these kinds of qualities of the ID3 tags must remain unchanged: -The version of the ID3 tags, be it v2.3, v2.4, etc. Do not convert one version to another. -Any and all "unusual" tags. If there are tags for, say, "Translator," or "Location," etc. preserve them! -Any and all images in the tags (such as JPGs) -The character encoding, even if it seems unusual or improper -A combination of both v2 ID3 tags and v1 should also be preserved 3) This feature must be possible to activate by the option "--pass-ID3-tags-unscathed". This is for users who want to be extra-sure this behavior occurs, who want to specify it explicitly as an option. This is a bit of future-proofing in case new options that cause different ID3-tag-related behavior ever get added in the future. 4) This feature must occur as LAME's default behavior, even if the option "--pass-ID3-tags-unscathed" is not used. After all, it's only common-sensical that an end user would not want their ID3 tags molested. (If the end user did want to convert or change their ID3 tags somehow, plenty of other software already exists to do this, such as Easytag or eyeD3). 5) LAME's "man" page, (and any and all other relevant documentation of LAME's options) must be updated to properly mention this feature. ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2010-06-23 12:01 Message: Sorry, I must have just made up the name 'myscript', as I looked on all my computers and could not find it. ---------------------------------------------------------------------- Comment By: http://subharo.myopenid.com/ () Date: 2010-06-09 19:56 Message: jidanni, would you be willing to reply (with another comment), posting the contents of your "myscript" script? I would really appreciate using your workaround until this bug gets fixed. :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350290&aid=1985551&group_id=290 |