Very peculiar thing, first time I've experienced it: I have a BBC Music classical recording, from the libary - and about 5 minutes into the first track after running totally cleanly on the PC there's a recorded pause, and the next section, fairly loud, goes into a complete speaker shredding meltdown, roughly equivalent to digital TV picture breakup with poor reception. At first I thought that the PC monitor speakers were overloading, so I turned the volume right to a minimum - no, exactly the same thing happened. If I skipped to the next track, etc, everything was fine.
You can still hear the music a bit through the chaotic overload, but it sounds like the speaker is trying to tear itself apart.
Anyone come across this happening, any ideas - peculiar CD, faulty decoding in the DAC, what ... ???
Update: OK, mystery solved ...?? This appears to be a media player misbehaviour, the first time I've come across or heard of such a thing - the player is Nero Showtime Essentials, and it blew its stack when in the normal progression of playing it went from Tk1 to Tk2, only on this particular disk. If I skipped from Stop straight to Tk2 it works perfectly with the playback - so it's not having problems reading the disk. I suspect it managed to fool itself itself into thinking that the coding of the next track was different, somehow - and triggered different, wrong, processing.
So, there was something at the end of Tk1, some code possibly misinterpreted as a flag, that confused the player software and triggered a software bug - for the rest of the disk it had no trouble going from one track to the next. And this behaviour was hardwired, it happened every single time I tried.
Interesting ... 🙂
You can still hear the music a bit through the chaotic overload, but it sounds like the speaker is trying to tear itself apart.
Anyone come across this happening, any ideas - peculiar CD, faulty decoding in the DAC, what ... ???
Update: OK, mystery solved ...?? This appears to be a media player misbehaviour, the first time I've come across or heard of such a thing - the player is Nero Showtime Essentials, and it blew its stack when in the normal progression of playing it went from Tk1 to Tk2, only on this particular disk. If I skipped from Stop straight to Tk2 it works perfectly with the playback - so it's not having problems reading the disk. I suspect it managed to fool itself itself into thinking that the coding of the next track was different, somehow - and triggered different, wrong, processing.
So, there was something at the end of Tk1, some code possibly misinterpreted as a flag, that confused the player software and triggered a software bug - for the rest of the disk it had no trouble going from one track to the next. And this behaviour was hardwired, it happened every single time I tried.
Interesting ... 🙂
Last edited:
King Crimson Playback Problems
I have a CD player which repeats portions of King Crimson CD's.
Certain passages, always at the same location on a track, will begin to "resonate" tones and then repeat the same tone infinitely.
Quite bizarre and reproducible.
I have a CD player which repeats portions of King Crimson CD's.
Certain passages, always at the same location on a track, will begin to "resonate" tones and then repeat the same tone infinitely.
Quite bizarre and reproducible.
I have a CD that does something strange, too, when I play it. Ripped, it's fine. I don't play CDs much anymore....
Hi
Which king crimson CD's and which track(s) ? and what model/brand of CD player ?
Would be interesting to see if it occurs on the CD's I have here.
Cheers / Chris
That sounds like a normal disk mistracking to me, what happens then is dependent on how the error correction mechanism of the player copes with it. I get CDs from the local library, and some of them are unbelievably filthy, and scratched - if one of my players gets stuck on a bad bit then what you describe is exactly how it can sound. What I do then is carefully wash the CD with a bit of normal handwash and water, and polish off the scratches with fine auto polish. This has worked in every case, can recover perfect playback if I do it enough ...
The PC weirdo behaviour can only be a software glitch, nothing else makes sense ...
- Status
- Not open for further replies.