View Issue Details

IDProjectCategoryView StatusLast Update
0012003MMW v4Codecpublic2014-04-09 09:00
Reporterpeke Assigned To 
PriorityhighSeveritymajorReproducibilityalways
Status assignedResolutionreopened 
Product Version4.1.1 
Fixed in Version4.1.2 
Summary0012003: AAC/M4A: Some Files not handled correctly
DescriptionSome AAC files are not imported correctly

1. Even MMW play the file length is unknown
2. Converting such file do not show progress (Possibly due 1)
3. File originally came with M4A extension and when D&D to Now Playing then title is shown Garbled instead of returning NOT M4A

Sample file is on FTP.
TagsNo tags attached.
Fixed in build1704

Activities

michal

2014-04-07 09:07

developer   ~0040056

Last edited: 2014-04-07 09:59

3) is fixed in build 1704.

1) and 2) are not correctly fixable - the song length is really unknown. The file does not have any header, the basics for decoding are only guessed by the decoder. Note, that e.g. VLC or Winamp with in_mp4 plugin are not able to play this file at all (because of missing header).

peke

2014-04-07 12:38

developer   ~0040060

1. You are right about Winamp and VLC, but AIMP read length. It could be useful that MMW read first Data Chunk and Calculate estimated length based on File size (Assuming that file is in CBR) or at least Show 00:00 so that user know file is playable.

2. Currently progress shows that MMW is Converting at 0% it would be better if it shows 100% so that there is some feedback on converting, as in case of Multiple file conversion it will look better and there will be at least some sort of progress bar.

What do you think?

jiri

2014-04-08 08:25

administrator   ~0040074

Since 1&2 isn't too important, leaving to Michal to resolve sometimes.

michal

2014-04-08 08:28

developer   ~0040075

Last edited: 2014-04-08 08:29

1) frames in AAC have variable size, the only way to detect song length is to parse whole file and count audio frames.

2) will be automatically resolved after implementing parser in 1)