Been happily using my WD player for a year now. Yesterday it started running super slow. I have unplugged it, reset it etc. to no avail. Any suggestions?
WHAAATTTT ISSSSSSS SLOOOOWWWW? 
What do you mean?
Yes, for me too. I just experinced it in last 3 days. and everything going to slow. media player function is working slow now. when u play a video media it takes more than 30 sec to play. when u pause the video and play it again it takes more than 30 sec to resume again. every function has this probelm. no matter what’s ur video source. HD quality or DVD quality. mkv or avi or mp4.
I think this bug related to the hard disc when it’s getting full.
Because I copied a media from my old HDD to a new HDD for test and media player act normal. but when i want to play the same media from the old full HDD it takes to long to play. and i have to say both HDD are in the healthy situation. because i connectd them to my computer and both are diagnosing as well as the other. they are both same model and same size. but the old one has about 20 GB free space now and i think this is the media player bug.
P.S. sorry if my english skills are not good enough.
did I mention the hard discs size?
they are both seagate 500 GB
the old one is freeagent go
the new one is expantion protable drive (This is exactly the model)
Your problem may not be the same as the original poster, but you ought to try resetting your Live AND unplugging from power for at least 10 minutes.
As with the other post it’s all the functions that are slow. I will try to unplug for 10 min. My hard drive is only 25% full
@austin: Yes, all functions while playing the video file are slow too.
@kelly: I did it before. I even reset device factory setting. But nothing changed. And as I said before, it works perfectly fine with one of those HDD and work worse with the other one.
Guys Maybe it’s a bug.
Guys I found the reason.
This is a bug
Check your HDD
WD Live TV make a folder called (.wd_tv) which used for its images thumbnail cache and other info.
Delete this directory and everything will be fine again.
I think an Honored Contributor must report it as a bug to WD.
Have Fun guys.
Hooman wrote:
…WD Live TV make a folder called (.wd_tv) which used for its images thumbnail cache and other info.
Delete this directory and everything will be fine again…
Hi board, remember that the folder .wd_tv is an hide and protected system folder, so you need to go in explorer and uncheck the relate boxes to show it
regards
@master: tnx master. mine was not hidden folder. but maybe there is a possibility. anyway, guys check if the folder is hidden
Hooman wrote:
Guys I found the reason.
This is a bug
Check your HDD
WD Live TV make a folder called (.wd_tv) which used for its images thumbnail cache and other info.
Delete this directory and everything will be fine again.
I think an Honored Contributor must report it as a bug to WD.
Well, it’s only a “bug” if the problem is that the file has gotten corrupted in some way (which it might if it’s trying to build it while you turn off the Live or unplug it from power). It takes a while to build that file when you have lots of files on your hard drive, so you should NEVER turn off the Live when that light is flashing unless you first eject the USB drive from the menu.
So it’s probably more a matter of bad behavior on your part – make sure you’re careful with the drive and you shouldn’t get into trouble.
Hooman wrote:
Guys I found the reason.
This is a bug
Check your HDD
WD Live TV make a folder called (.wd_tv) which used for its images thumbnail cache and other info.
Delete this directory and everything will be fine again.
I think an Honored Contributor must report it as a bug to WD.
Have Fun guys.
Have another look after you use the hard disc. I bet you it has come back again. Its automatically made by the WDTV and yours was probably corrupted.
@Mike: Yes, mabye.
@ Rick: Yes rick. another .wd_tv directory will made and device start to cache things again. the matter is after cache a bunch of info and needs device start work slower and slower till its become worse.
I think it’s a bug depend on how and when device access to those cache data.
