possible MAC error with 3.99 ~FTP is up for test~

Topic: possible MAC error with 3.99 ~FTP is up for test~ (Read 8057 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

possible MAC error with 3.99 ~FTP is up for test~

2004-08-13 13:59:15

http://www.monkeysaudio.com/cgi-bin/YaBB/Y...39943;start=0#8

Could use some help diagnosing a possible problem with MAC. Two weeks and still waiting; not surprised by the infamous sloth-like quality of the forum there 323 views 7 responses.

thanks
DC

possible MAC error with 3.99 ~FTP is up for test~

Reply #1 – 2004-08-13 16:51:37

Quote

http://www.monkeysaudio.com/cgi-bin/YaBB/Y...39943;start=0#8

Could use some help diagnosing a possible problem with MAC. Two weeks and still waiting; not surprised by the infamous sloth-like quality of the forum there 323 views 7 responses.

thanks
DC
[a href="index.php?act=findpost&pid=234094"][{POST_SNAPBACK}][/a]

This is no offence to Matt Ashland, but he seems to come and go like the wind. When 3.99 came he regularly posted. There were many reports of corrupt files and CRC errors with 3.99, and there still is. He said he couldn't recreate the problem and then promptly disapeared again. I assume he is busy with the job that actually puts food on his plate, but it would be nice if he gave 3.99 and his user base some attention again.

EDIT:
From another perspective though, Matt has been the sole developer of Monkey's for a long time, it's still a damn good codec, and possibly can't get any better (or only very maginally) Maybe he's just had enough. It's all free in the end

possible MAC error with 3.99 ~FTP is up for test~

Reply #2 – 2004-08-13 21:56:05

I echo all your sentiments Yaz. I highly respect Matt for all his work, but at the same time, when informed to post in the forum since he won't answer email or can't, I have still to see a response to my post where I took the time & initiative 2weeks ago to post a file for testing. Could have just left well enough alone with 3.97....IMHO.

and have you tried this file with 3.97 Yaz; I couldn't really tell from your post there?

I am going to take the file down next week and regardless...sticking with 3.97 HIGH.

DC

Quote

Quote
http://www.monkeysaudio.com/cgi-bin/YaBB/Y...39943;start=0#8

Could use some help diagnosing a possible problem with MAC. Two weeks and still waiting; not surprised by the infamous sloth-like quality of the forum there 323 views 7 responses.

thanks
DC
[a href="index.php?act=findpost&pid=234094"][{POST_SNAPBACK}][/a]

This is no offence to Matt Ashland, but he seems to come and go like the wind. When 3.99 came he regularly posted. There were many reports of corrupt files and CRC errors with 3.99, and there still is. He said he couldn't recreate the problem and then promptly disapeared again. I assume he is busy with the job that actually puts food on his plate, but it would be nice if he gave 3.99 and his user base some attention again.

EDIT:
From another perspective though, Matt has been the sole developer of Monkey's for a long time, it's still a damn good codec, and possibly can't get any better (or only very maginally) Maybe he's just had enough. It's all free in the end
[a href="index.php?act=findpost&pid=234144"][{POST_SNAPBACK}][/a]

possible MAC error with 3.99 ~FTP is up for test~

Reply #3 – 2004-08-14 22:08:35

I verified that the latest foobar plugin (dated June 29, 2004) has trouble with that file, but a previous version (dated April 06, 2004) plays the file fine. So there definitely is a problem.

However, I looked into this a little deeper, and it may not all be Matt's fault. The file has a corrupt APEv2 tag on it, and MAC 3.97 does not write APEv2 tags, so some other program must have been used to append the tag.

I used MAC 3.97 to create the original wav file and then compressed it again and saw that MAC put a funny little corrupt APE tag on there even though I didn't request one. I changed a few bytes in the original file and the resulting funny tag changed, then I changed more original bytes and it completely disappeared. I don't know why this is happening, but neither 3.97 nor the newer versions seem to have any trouble just ignoring it.

However, the program you used to tag the file was confused by this funny tag, and this resulted in a few bytes of the original file being changed and another corrupt tag being added. This still doesn't confuse MAC 3.97 (and foobar reads the tag fine) but it does cause a decoding problem with the new code.

possible MAC error with 3.99 ~FTP is up for test~

Reply #4 – 2004-08-15 23:44:16

Thanks. I have been waiting to finally set up my PC again and check the tag situation because this is seeming to reveal itself as the problem.

I used Abander Tag Control in the past and have been recently using J. River Media Center to do some renaming and tag editing. I think that Abander only used Ape1 tags so that is most likely the culprit.

If you decode the file to wav (the tag is lost?) and simply re-tag it with 3.97 evrything should be okay right? Deleting the problem tag is a fix?

I could then just Verify with 3.99 all my files and re-code with "fresh" tags.

Jon

Quote

I verified that the latest foobar plugin (dated June 29, 2004) has trouble with that file, but a previous version (dated April 06, 2004) plays the file fine. So there definitely is a problem.

However, I looked into this a little deeper, and it may not all be Matt's fault. The file has a corrupt APEv2 tag on it, and MAC 3.97 does not write APEv2 tags, so some other program must have been used to append the tag.

I used MAC 3.97 to create the original wav file and then compressed it again and saw that MAC put a funny little corrupt APE tag on there even though I didn't request one. I changed a few bytes in the original file and the resulting funny tag changed, then I changed more original bytes and it completely disappeared. I don't know why this is happening, but neither 3.97 nor the newer versions seem to have any trouble just ignoring it.

However, the program you used to tag the file was confused by this funny tag, and this resulted in a few bytes of the original file being changed and another corrupt tag being added. This still doesn't confuse MAC 3.97 (and foobar reads the tag fine) but it does cause a decoding problem with the new code.
[a href="index.php?act=findpost&pid=234376"][{POST_SNAPBACK}][/a]

possible MAC error with 3.99 ~FTP is up for test~

Reply #5 – 2004-08-16 04:34:26

Quote

If you decode the file to wav (the tag is lost?) and simply re-tag it with 3.97 evrything should be okay right? Deleting the problem tag is a fix?

If you decode to wav with 3.97 and then re-encode with 3.99 and add tags you should be fine. If you re-encode with 3.97 you will still get that funny corrupt tag that could cause trouble in the future. You don't want to follow the same sequence of events that got you the bad file in the first place! I would not try to just delete the tag from the file because you might make it worse; get your data out of there first.

possible MAC error with 3.99 ~FTP is up for test~

Reply #6 – 2004-08-16 06:51:26

Quote

and have you tried this file with 3.97 Yaz; I couldn't really tell from your post there?

Sorry but there really was not much I could do for you.

You needed someone who could actually look "inside" the file. Glad to see there is now a resolution to your problem.

possible MAC error with 3.99 ~FTP is up for test~

Reply #7 – 2004-08-16 07:57:39

Hi all,

Didn't see your post until after I decoded and re-encoded with 3.97; verifies okay with 3.99 after that.

If I decode with 3.97, the tag is simply erased...no?

Doesn't re-encoding with 3.97 just add a brand new tag....? Or is the data still corrupted by that tag somehow...I don't understand.

I think the error came from editing tags with Abander Tag Control which uses ape1 tags.

DC

Quote

Quote
and have you tried this file with 3.97 Yaz; I couldn't really tell from your post there?

Sorry but there really was not much I could do for you.

You needed someone who could actually look "inside" the file. Glad to see there is now a resolution to your problem.
[a href="index.php?act=findpost&pid=234717"][{POST_SNAPBACK}][/a]

possible MAC error with 3.99 ~FTP is up for test~

Reply #8 – 2004-08-16 18:02:11

Quote

Didn't see your post until after I decoded and re-encoded with 3.97; verifies okay with 3.99 after that.

If I decode with 3.97, the tag is simply erased...no?

Doesn't re-encoding with 3.97 just add a brand new tag....? Or is the data still corrupted by that tag somehow...I don't understand.

I think the error came from editing tags with Abander Tag Control which uses ape1 tags.

I believe that your problem was caused by two things. First, Mac 3.97 put a funny little tag on the file that it shouldn't have. This by itself didn't actually cause any problem, but afterward when you appended a tag with another program, that program was confused by the tag (that wasn't supposed to be there) and made a mess (which 3.99 has a problem with).

If your file decodes correctly with 3.99 now, then you're fine. It would be a good idea to do a verify again if you ever edit the tags in the future.

Notice