DSM-G600, DNS-3xx and NSA-220 Hack Forum

Unfortunately no one can be told what fun_plug is - you have to see it for yourself.

You are not logged in.

Announcement

#1 2009-01-04 20:37:56

nemo
Member
Registered: 2008-11-24
Posts: 5

uPnP AV server refresh has become sloooooow! (like, 2 hours slow)

hi all,

i'm wondering if anyone else has experienced this. recently, refreshing the content on the 323 has become SLOOOW! like, two hours+ slow to reach 100%. not sure what's going on, if its hanging on some corrupted files or something, but is it something i should be worried about? it wasn't like this initially.

i'm also wondering if this would be harmful to the drive/data i have in the 323 in the long run, as i upgraded the firmware to 1.06 and the 'auto-refresh' option has been removed (i assume that means that the 323 auto-refreshes on its own?) - hours of endless grinding on the drive plates can't be good...

can someone tell me what's going on? should i be worried?

Offline

 

#2 2009-01-05 19:38:30

corky
Member
Registered: 2008-01-07
Posts: 17

Re: uPnP AV server refresh has become sloooooow! (like, 2 hours slow)

I might be also suffering from this as well. I noticed this over the weekend, i renamed an album, then copied over another album, turned on my ps3 and both don't exist at all. Even if i click on refresh in settings, then wait till finished, restart ps3, still not there.

Even tried twonky set to -1 for auto refresh, still not refreshing ?

downgraded the firmware to 1.05, reset defaults, back to 1.06, nope, still can't see the renamed and new albums.

But i see them fine via smb using xbox or pc.

Totaly stumped ??

Offline

 

#3 2009-01-05 21:07:15

jeff777
Member
Registered: 2007-05-25
Posts: 15

Re: uPnP AV server refresh has become sloooooow! (like, 2 hours slow)

I've also noticed that the refresh of the native UPNP AV support on the DNS-323 with firmware rev 1.06 is very slow.  I have a media library that consists of over 20000 audio files and almost 400 video files on one of the hard drives in the DNS-323, and the time it takes for the native UPNP AV support to recognize that library requires an extremely long, long time.  Whereas if I'm running TwonkyMedia on my DNS-323 (I'm running revision 4.4.6), that entire audio and video libary is detected after Twonky's refresh in less than 10 minutes.

I also noticed in the DNS-323's native UPNP AV support that it's supposed to automatically detect immediately any added audio and video included within the area of a hard drive assigned for UPNP AV.  I've seen this work with audio files, but I haven't seen it do this with video files.  On my PS3, if I bring up any audio, the DNS-323 will immediately start accessing the hard drive within each folder I navigate through on the PS3.  But if I bring up any video, it will only display any video files that were detected from the previous UPNP-AV refresh on the DNS-323 and nothing added afterward (until I do another refresh).



Jeff

Offline

 

#4 2009-01-05 22:59:03

corky
Member
Registered: 2008-01-07
Posts: 17

Re: uPnP AV server refresh has become sloooooow! (like, 2 hours slow)

Also using the built in av server it's gone really slow for me, when navigating over to photos on my ps3 it takes far too long to display "volume_1", then photos again, then list all my photos in folders. It's all a struggle. It's a bit quicker with music, but still slow, and it's fine when i navigate to films which has about 200 avi films on it ?

I tried my other nas drive buffalo linkstation pro with twonymedia and on my ps3 it's all pretty much fast and instant.

Maybe i'll try twonky again on the dns-323, but when i tried it on saturday there was no refresh either, saying that i was assuming it would be instant, maybe not, maybe i need to wait 10 mins ir so, then see if it's updated ?

Offline

 

#5 2009-01-06 07:21:05

nemo
Member
Registered: 2008-11-24
Posts: 5

Re: uPnP AV server refresh has become sloooooow! (like, 2 hours slow)

hmm i actually started to get this slow refresh one day while using 1.05, which was when i upgraded to 1.06 to see if it would fix anything. so doesn't seem to be a firmware issue, at least for now. no one seems to have a solution/reason for this. perhaps it's a new issue that has arisen?

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB