Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: What\'s happening with my track numbers? (Read 2438 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

What\'s happening with my track numbers?

Hello forum.

I do a lot of MPC rips/encodes with EAC and Andree's newest encoder.
Lately I've been noticing something, and I wonder why and how this is happening. I hope one of you might be able to answer.

I use ID3v1.1 for my MPC encodes, and when I rip and encode an album with EAC, there's always one or two tracks for which the track# field is left blank. Everything else (track name, artist, bla-bla) is in, but not the track number.
And only on one or two tracks for each album I rip.
The other tracks come out fine with every ID3v1.1 field filled.

This has happened to me on multiple computers, so I think I can safely conclude that either EAC, the MPC encoder holds this flaw.

Does any of you know which?

What\'s happening with my track numbers?

Reply #1 –
Quote
Originally posted by helstegt
I use ID3v1.1 for my MPC encodes, and when I rip and encode an album with EAC, there's always one or two tracks for which the track# field is left blank. Everything else (track name, artist, bla-bla) is in, but not the track number.
And only on one or two tracks for each album I rip.
The other tracks come out fine with every ID3v1.1 field filled.

This has happened to me on multiple computers, so I think I can safely conclude that either EAC, the MPC encoder holds this flaw.


Is this with Andree's encoder or Frank's?  I don't think I have run across this particular issue before so I can't really offer more help at the moment unfortunately, but you might try using both encoders on a album you have noticed this behavior and see if they both do it.