1.03.49 headache inducing framerate issue

Has anyone else noticed really bad rubber banding framerate effect on, for example, full screen panning shots? I’ve been trying to watch the latest F1 race and its enough to make my want to rip my eyes out with the speed-up slow-down speed-up panning!

Is this something you guys have also noticed, or is it an isolated issue for me? I will note that downgrading to the previous official firmware fixed the issue for me.

Same here after upgrading to the latest firmware :angry:

I’m surprised by the low number of reports on this issue.

I’m bot sure if it’s the latest firmware but now some of my avi movies are stuttering very bad. The frame rate seems to be out and I don’t know how to check it out.

I have my wdtv live connected to a usb wd portable drive,

Any help appreciated

yap and losing sound also in this problem ! 

Glad to see it wasn’t just me, I’ve been trying every combination of resetting, video output method, file source, etc that I could think of. None of them with any improvement except for rolling back to the old firmware. My issue with rolling back is, the old firmware has all kinds of audio sync issues - a problem the new firmware fixes. Although, the audio fix is a bit marginal because of the hiccups/pops as it seems to be correcting any errors, but still a vast improvement on a +/-2 second variation.

Something I also noticed switching between firmwares is that the problem exists system wide - including menus. Entering a password on the old firmware with an arrow held down: skip-skip-skip-skip; with the new firmware skip-skip—skip-skip-skip—skip-skip. 

I agree though, its kind of hard to believe that there have been so few reports _anywhere _for something I noticed immediately after updating.

Hmmm.   I looked for exactly that, and I’m not seeing it at all.

None of ya mentioned it:   Did you try a therapeutic reboot?    Or try resetting back to factory defaults after upgrade (yeah, I know, it’s a pain, but many people have reported it fixes all kinds of issues.)

Random no audio in some mkvs accompany with slow motion.

To fix:

  1. stop playback, back to folder, select play, resume

  2. rewind a bit, play

When no audio, video framerate is slow, but not stutter.

WD, we need “GO TO” function!!!

RamboKid wrote:

 

WD, we need “GO TO” function!!!

 

The Hub has a GO TO function that works well.  Hopefully they’ll be back-porting that to the Live units.

Tony - Not sure what the definition of a theraputic reset is, but I’ve tried the fw flash a few times (between 1.02 and 1.03), resetting before and after (with the button and the menu item) as well as unplugging for a minute or two to start fresh. None of that made any difference.

Rambo - Audio isn’t an issue any more, and this specific case is an MPEG2 file not a .mkv. Also I’ll add, that solution worked maybe 5% of the time and usually only for a couple minutes when I used to try it in the old firmware.

Off Topic - Yes, a go to/seek slider would be a welcome addition.

EDIT: Here is a clip to demonstrate what mine is doing on panning:  http://www.megaupload.com/?d=56YXDILO .Plays very smoothly on my PCs but on the wdtv its fast-slow-fast-slow-fast-slow.

Woohoo! Well done WD, 1.04 update fixed it for me! No crazy reboot/power down sequence needed or anything.

I’ve been having similar problems with 1.03.49B for Live+.

When playing blu ray rips created with MakeMKV and DVDfab (no compression other than whatever was native to the discs) the video will eventually stutter and/or audio will disappear within about one minute of starting. It happens with both mkv and m2ts files. All are 1080p with 5.1 audio and are large files in the tens of GB range. These problems did not exist with 1.03.29B or 1.03.39B beta. Old tricks like FF and/or stop and replay did not improve playback.

I also noticed DVD rips and compressed  (post-rip) avi files with stereo audio played fine.

I followed standard procedure and after the FW update, did resets using the pinhole button, software reset, and power unplug. Reverting back to 1.03.29B, the problem went away.

The files are being accessed via file shares over hardwire LAN. The files reside on a Windows 7 x64 PC.

I will try the just-released 1.04.10 and see if the problem persists there.