View Issue Details

IDProjectCategoryView StatusLast Update
0005144MMW v4Framework: Taggingpublic2010-02-12 14:49
Reporterrusty Assigned To 
PriorityimmediateSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version3.1 
Fixed in Version3.1 
Summary0005144: Problems reading wav tags from SoundMiner
DescriptionPlease have a look at this. A customer is having problems with this issue, and I'm not sure whether this is easily fixable or not.

Tags appear like this when scanned by MM:
ÿþG:o:o:d: :K:i:n:g: :P:o:p: :R:o:c:k:

They should appear as:
Good King Pop Rock

To read the tags properly, you can use dbpoweramp.
Additional InformationOriginal report at:
http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=3258

Tracks are posted to the ftp server.
TagsNo tags attached.
Fixed in build1221

Relationships

related to 0005260 assignedmichal Support for Broadcast Wave Format 
related to 0004902 closedjiri WMP11 x64 and CD rip to WAVE Format incomapatibility. 
related to 0005414 closedjiri Replay gain information isn't saved to .wav tracks 

Activities

peke

2009-01-07 05:54

developer   ~0016039

After brief look WAVE files saved in soundminer contain additional extended tag format http://hul.harvard.edu/jhove/wave-hul.html Broadcast Wave Format and file native extension should be .BWF to clearly state that Audio Data is preserved in WAVE format Tag Data and its handling should be handled according to Broadcast Wave Format (BWF)

rusty

2009-01-08 02:17

administrator   ~0016071

In order of priority:
1) Be able to read standard riff data correctly from SoundMiner
2) Be able to read custom tags from Soundminer
3) Be able to write custom tags for Soundminer

Items 2 and 3 are clearly out of scope for MM 3.1. Item 1 would be nice to have if it's an easy/low risk fix.

peke

2009-01-08 23:15

developer   ~0016091

1) Currently MMs TNT components can't read/translate Unicode Written Tags in SoundMiner, but instead of trying to translate/read Unicode it should use second set of RIFF Tags that are normally written in ASCII

2), 3) we would need to get exact spec of field relations used in SoundMiner for better implementation

jiri

2009-01-27 23:45

administrator   ~0016417

Fixed in build 1219.
 - I simply fixed reading of ID3 tag that's present in WAV file and now it's ok.

peke

2009-01-28 08:33

developer   ~0016427

Confirmed 1219 that ID3 Tags written in UTF-16 are now read correctly

peke

2009-01-28 08:35

developer   ~0016428

Last edited: 2009-01-28 08:35

Internal Soundminer .BWF format is still not read should we add it?

jiri

2009-01-28 08:51

administrator   ~0016429

I don't think that we need to support any application specific format.

rusty

2009-01-30 06:15

administrator   ~0016469

I have a batch of wav tracks of which many are not being read correctly. Will upload to ftp.

jiri

2009-01-30 16:16

administrator   ~0016473

Last edited: 2009-01-30 16:18

There doesn't seem to be any problem on MM side. On the tracks I have checked, there was one chunk 1 byte shorter than it should be, which caused that further chunks aren't scanned by MM (they simply can't be) and so correct metadata present in the tracks can't be read.

rusty

2009-01-30 17:08

administrator   ~0016474

Assigned to Rusty to verify the source of the corruption / what kind of similar corruptions we can expect and determine whether MM should add some heuristics to get around the problem that the tags are inaccessible since chunk link is corrupted before MM reaches them.

peke

2009-01-30 17:58

developer   ~0016475

Last edited: 2009-01-30 18:04

When you check this please note that due the fact that RIFF tag chunks are not standardized like for example in FLAC where Author said that usage of ID3v2 is possible but highly disapproved and should be either ignored/cleaned and not supported. Currently each chunk is checked for valid format and assumed read info is correct. It is one of the oldest plugins made for MM it should be revised especially as .AVI uses same tag/chunk format.

Additionally WAV now support Multi Channels (5.1, 7.1 and 24, 32 and 64 Bit audio data along with 192Khz bitrate)

In last few revisions Jiri corrected JUNK chunk Correction (It posed high risk especially on network environment due the high number of access and brute force changes to speed processing on large files). Your non subjective revision is highly recommended.

rusty

2009-01-30 17:58

administrator   ~0016476

Re-assigning to Jiri. Further testing shows that the tracks are correctly read by Windows Media Player as well as a couple of other apps?!

jiri

2009-02-02 16:51

administrator   ~0016488

Fixed in build 1221.
 - There was some old thing in the plug-in that wasn't according to the spec.

peke

2009-04-07 20:38

developer   ~0017447

Verified 1233