Page 1 of Scream(R2), plays with massive picture distortian and sound loss on my Scan SC-2000 :(

Hiya

Just got Scream on DVD (R2) and played it in my Scan SC-2000 (recent player with 2.04s firmware) and it simply wont play

from begining to 24:00 the screen is simply a mass of colours and weird patterns plus the occasional burst of sound, then suddenly it plays fine for about 15 mins and then it goes back to the corrupted display.

Im not having problems with any other DVD and I lent it to my friend with a Sony 725d DVD player and he said it played just fine.

What could be wrong ?!, all helpful and non sarcastic answers appreciated.

Thanks

Chris

Sounds has if the scan is performing perfectly normal to me! Pheraps one day all discs will play on all machines, woudn`t that be nice!

But you could give the disc and the player a good clean with a proper cd/lens cleaning kit,
And the Sony 750 plays just about anything.

Then take the disc back and exchange it and try again!

If anyone advises you to upgrade firmware be carefull you could break your player or make it a lot worse!

This item was edited on Wednesday, 4th April 2001, 12:38

Thanks

I am well aware of your opinions about the Scan but Its not fair to say this is normal operation because it isnt, and it plays my other DVD`s both bought and rented just fine.

The surface of DVD is crystal clear with no scratches (its a new disc) so I dont think its that. Maybe the disc is just poorly made and trips up a weaker player like the scan ?.

If anyone else knows anything about this I would appreciate some help, how about a new firmware update?. Ive added myself as a member of the scan yahoo group so hopefully ill be able to access the most recent firmware soon.
Are there any issues or stuff I should know about with these latest firmwares ?

Thanks

Chris

Ah this is one Scan story that has a happy ending.

I joined the Scan Yahoo group and downloaded the latest 2.33 firmware. After installing it Scream plays fine with no issues whatsoever.

Strange though that a firmware as late as 2.04 could have such an issue

Chris