App to fixed MP3 rips that have "byte order reversed"?

[fitwell]

Now I'm really new at this problem. I dl a trilogy recently and 2 to
3 songs on each of the 3 CDs have a problem where the MP3 plays
perfectly fine but the burned CD has staticky/skippy patches all
throughout. Various items were put forth but the "byte order
reversed", by the very description given, sounds like a very possible
cause.

After a multiple-dl of different versions this still happened; each
burned CD has the same problems with the same files no matter what the
source. Was hoping there was a diagnostic/fix tool somewhere to check
and fix this byte thing, sort of like MP3 Trim. I'm very new to this
problem and don't know if this is, ultimately, the definite cause with
all 7 songs out of the trilogy but thought I'd try to track down a
tool to help. If this is a potential problem, will want to run each
MP3 through it to fix _before_ finding out at the end.

When I don't need to re-sample, I run my MP3s through MP3 Trim. When
I do re-sample, through GoldWave which fixes a lot of problems as a
matter of course. It didn't fix this burned issue though. I burned 4
copies of the trilogy using various source MP3s for the trouble songs
and _all_ were affected. Unfortunately, the suggestion to decode to
WAV and using that format for burn not an optin. The songs already
way too big in MP3; WAV would be more than my hdd can handle right now
and don't want to burn to CD a backup with these MP3s and new WAVs.
Need on hdd.

Thanks guys! Here's hoping someone knows of this problem and how to
resolve.

Cheers!

- did everyone have a good Xmas?? I sure did. Love this time of
year! D

 

[REMbranded]

fitwell <[email protected]> wrote:

Now I'm really new at this problem. I dl a trilogy recently and 2 to
3 songs on each of the 3 CDs have a problem where the MP3 plays
perfectly fine but the burned CD has staticky/skippy patches all
throughout. Various items were put forth but the "byte order
reversed", by the very description given, sounds like a very possible
cause.

I dunno. Intel is little endian and some processors are big endian. If
you can play the mp3 my guess is the problem is other than an "endian"
problem. If the mp3 was produced on a different endian machine than
what you have you would not have been able to play it.

http://artemis.wszib.edu.pl/~mdudek/

Above is a link to a hex editor that simply claims:

"Converts big endian to low endian and vice versa"

I bet that is bytes, rather than files, but you might check it out of
curiousity. 471k.

After a multiple-dl of different versions this still happened; each
burned CD has the same problems with the same files no matter what the
source. Was hoping there was a diagnostic/fix tool somewhere to check
and fix this byte thing, sort of like MP3 Trim. I'm very new to this
problem and don't know if this is, ultimately, the definite cause with
all 7 songs out of the trilogy but thought I'd try to track down a
tool to help. If this is a potential problem, will want to run each
MP3 through it to fix _before_ finding out at the end.

When I don't need to re-sample, I run my MP3s through MP3 Trim. When
I do re-sample, through GoldWave which fixes a lot of problems as a
matter of course. It didn't fix this burned issue though. I burned 4
copies of the trilogy using various source MP3s for the trouble songs
and _all_ were affected. Unfortunately, the suggestion to decode to
WAV and using that format for burn not an optin. The songs already
way too big in MP3; WAV would be more than my hdd can handle right now
and don't want to burn to CD a backup with these MP3s and new WAVs.
Need on hdd.

Thanks guys! Here's hoping someone knows of this problem and how to
resolve.

Maybe someone who knows more about sound files can help.

- did everyone have a good Xmas?? I sure did. Love this time of
year! D

It was a really nice Xmas. And the weather is great here. It is the
time to enjoy and to be thankful!

 

[Lester Horwinkle]

It's not a byte-order problem.

Though some CPUs are big-endian, and some little-endian, that only applies
to data stored in memory.

File formats (including MP3) are defined one way only. Any compliant program
must follow the defined standard.

 

[fitwell]

I dunno. Intel is little endian and some processors are big endian. If
you can play the mp3 my guess is the problem is other than an "endian"
problem. If the mp3 was produced on a different endian machine than
what you have you would not have been able to play it.

http://artemis.wszib.edu.pl/~mdudek/

Above is a link to a hex editor that simply claims:

"Converts big endian to low endian and vice versa"

I bet that is bytes, rather than files, but you might check it out of
curiousity. 471k.

Thanks, I'll check it out!

[snip]

Maybe someone who knows more about sound files can help.


It was a really nice Xmas. And the weather is great here. It is the
time to enjoy and to be thankful!

That's good to hear! It was a lovely Xmas, wasn't it?

D

 

[fitwell]

It's not a byte-order problem.

Though some CPUs are big-endian, and some little-endian, that only applies
to data stored in memory.

File formats (including MP3) are defined one way only. Any compliant program
must follow the defined standard.

Swell. Then I still don't know why I'm having this problem with
specific songs. <sigh> Figures.

Thanks!

[snip]