View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001485 | MMW v4 | Properties/Auto-Tools | public | 2004-07-06 15:19 | 2007-09-11 17:05 |
| Reporter | rusty | Assigned To | |||
| Priority | low | Severity | feature | Reproducibility | always |
| Status | feedback | Resolution | reopened | ||
| Summary | 0001485: Add support for Encoded By field | ||||
| Description | It seems that many apps use the 'Encoded By' field rather than the 'Encoder' field. We should consider adding support for this (instead?). | ||||
| Additional Information | Raised at: http://www.songs-db.com/forum/viewtopic.php?t=2015 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
As user mentioned in the forum, MM is right here, it works according to ID3v2 specs while some other apps don't. We could think about it further, but I don't see any correct way how to support both fields, I think the current situation is ok. |
|
|
I'm not saying that our implementation is incorrect--I'm just pointing out that most other apps use "Encoded By:" with the TENC, whereas MM uses "Encoder:" with the TSSE field. So our implementation is correct--the question is whether we should add an "Encoded by:" entry with a TENC field, so that data commonly included by other rippers would be read by MediaMonkey. The second question is whether we should consider replacing "Encoder:" TSSE with "Encoded by:" TENC. Thoughts? |
|
|
I think we could 'Encoded by: TENC' field, but I don't think it's really high priority. |
