View Issue Details

IDProjectCategoryView StatusLast Update
0009672MMW v4Properties/Auto-Toolspublic2012-10-04 19:07
Reporterpeke Assigned To 
PriorityimmediateSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version4.0.6 
Target Version4.1Fixed in Version4.1 
Summary0009672: f_WAVE: Tagging sometimes do not correctly create Junk Chunks
DescriptionTagging File two or three times in a row and MM format plugin add not needed JUNK Chunks at the end of file and do not calculate file format size correctly so DATA chunk size is re calculated including FALSE JUNK chunk.

Note: That first tagging is correct and every other tagging should change only LIST INFONAM CHUNK without adding JUNK CHUNKS and create incorrect Data CHUNK Size.
Additional Informationhttp://www.mediamonkey.com/forum/viewtopic.php?f=7&t=67676
FY-643005
TagsNo tags attached.
Fixed in build1600

Relationships

related to 0008902 closedmichal Certain WAV files can have static pop after edits in MM 
related to 0009198 closedmichal Wrong size of LIST INFO chunk after WAV tagging. 
related to 0005347 closedmichal WAV metadata Track Number 'itrk' not supported on some devices 

Activities

michal

2012-09-09 07:37

developer   ~0031848

Last edited: 2012-09-09 07:44

Seems to be already fixed in 4.1.1600 and later (I can reproduce it with 4.0.6.1501, but cannot with 4.1.1600 and 4.1.1601), please retest it and reopen if needed.

peke

2012-09-09 10:43

developer   ~0031849

My tests were done with 1600, thing I have done is that I opened WAV in HEX editor and watched for changes.

Have you tried to force MM sync tags into file after changes?

I'll UL sample file on FTP under Bug number.

peke

2012-09-09 11:16

developer   ~0031850

I had faulty f_wave.dll Compiled on from SVN and reinstalling 1600 confirmed Michal Fix.

peke

2012-09-09 11:17

developer   ~0031851

Verified 1600

peke

2012-10-03 23:18

developer   ~0032295

It looks like we should think of merging with 4.0.7, can you do estimate of regression risk?

michal

2012-10-04 15:52

developer   ~0032301

Last edited: 2012-10-04 15:52

Resolving, the problem was not in this, but in missing 0008902 fix in 4.0.7 branch. This issue is not related to 4.0.x versions, because it was regression caused by 0005347 and fixed as 0009198, both related only to 4.1 version.

peke

2012-10-04 19:07

developer   ~0032302

closing thx for clarification