D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: 12au7 on January 12, 2009, 08:38:19 AM
-
DNS323 streaming video file to DSM520 Media Player on local network with Actiontec router (FIOS supplied).
At 1.05 firmware: video file played with very good quality on HDTV through DSM520 Media Player. But, files over 1 or 2 GBytes would play about 10 minutes and end (known problem to be fixed in 1.06 firmware). I have been waiting for this fix, (UPnP AV support large file over 4GB).
After upgrade to 1.06 firmware: Using same video file. Length appears to calculate correctly. However, playback of video (same setup) stutters. Video freezes for 1 to 4 seconds every 1 to seven seconds. During the freeze no data is lost it just starts playing again.
The mpeg video file was created by Sage TV. A captured ATSC HDTV program.
The size of the file, small or large, does not change the symptom. I have reformatted, reset, changed settings, back and forth between 1.06 and 1.05. Now back at 1.05.
Any suggestions??
-
I have exactly the same problem. Post upgrade, video stutters badly regardless of what player I use or what buffering level I select. Connection to DNS is wireless.
Mike
-
+1.
I'm streaming from the DNS323 to my PS3. On 1.05 (and prior versions) I could stream fine. I now get stuttering throughout video playback on 1.06. The two are connected via a wireless bridge.
-
I have PS3 and DNS-323 with wired network. I don't have problem after upgarde to 1.06.
-
See my thread here: http://forums.dlink.com/index.php?topic=3533.0
I think that our problems might be related, but to different degrees. Does your DNS-323 have a static IP or is it using DHCP?
It seems the connection is lost temporarily in my situation and I get a message when trying to batches of files after a minute or so that says the path is no longer found. I suspect this is also why my video freezes when streaming data from the 323 as well.
-
I'm running with a static IP. I noticed a few dropped connections with the DNS, but assumed that it was a hiccup in my wireless network - I'll pay more attention to that and see if it is somehow dropping the network connection to the DNS.
mike