On January 31, 2010 at 05:46, HCFreak said...
1) So far, these buttons never worked, I will test again this evening. However, I doubt they ever will, because the 2500BT has a different interface: first one has to open the on-screen menu for audio, then one can select an audio track. The same with the subtitles.
2) No it doesn't with the default delays, I still got lock-ups. Now I use 300 general delay and 400 poll delay and that works without problems, except that sometimes I still get the error message above, but without apparent reason, because the module at that moment has done and still does all it should and doesn't lock up.
In this context I should maybe mention that my RFX9600 isn't directly connected to the router via ethernet but via a WLAN bridge, which probably causes delays(?).
3) I really like your homescreen for the 9600. In fact I have made one for the 9400 and for my devices that looks quite similar!
1) Is that only for Bluray or also for DVD? Do you know if it's the same for the other BD players?
2) Every wireless hop causes a delay and will lower the transferspeed. The transferspeed is not an issue because the ammount of traffic from and to a remote is very low, the delay is a bigger issue. Also the ammount of devices using the accessPoint cause bigger delays and lower transferspeed. I'm using extremely quick networkequipment and use a fast (330MHz) router stictly as a accesspoint for the TSU and it doesn't have to do DNS and DHCP. Could you ping your remote and extender? And tell me the longest and average ping time? (Go to the settings on your remote and remember the IP. Go to your pc and open a command box and run ping [remote's ip]) Here's my ping (PC->main switch->ap->remote)
C:\>ping 192.168.1.8Pingen naar 192.168.1.8 met 32 bytes aan gegevens:
Antwoord van 192.168.1.8: bytes=32 tijd=4 ms TTL=64
Antwoord van 192.168.1.8: bytes=32 tijd=3 ms TTL=64
Antwoord van 192.168.1.8: bytes=32 tijd=6 ms TTL=64
Antwoord van 192.168.1.8: bytes=32 tijd=6 ms TTL=64
Ping-statistieken voor 192.168.1.8:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).
De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 3ms, Maximum = 6ms, Gemiddelde = 4ms
And the ping to my extender (PC->Main Switch->Switch2->Extender):
C:\>ping 192.168.1.250
Pingen naar 192.168.1.250 met 32 bytes aan gegevens:
Antwoord van 192.168.1.250: bytes=32 tijd<1 ms TTL=64
Antwoord van 192.168.1.250: bytes=32 tijd<1 ms TTL=64
Antwoord van 192.168.1.250: bytes=32 tijd<1 ms TTL=64
Antwoord van 192.168.1.250: bytes=32 tijd<1 ms TTL=64
Ping-statistieken voor 192.168.1.250:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).
De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms
This roughly means my average time from remote to extender is 4 + 0 = 4ms and my max is at 6 + 0 = 6ms (When doing this longer I see an average of 6 and a max of 7ms) Even better for you would be opening two command prompts and do a ping -t [ip] for both at the sametime. Also you player might be slower then mine. I'll re-enable the logging of the time to send and receive in the next version. Another thing you could check is enabling the errorrate in the parameters, when it's to high (the rednumber on the top >7) this will cause delays aswell.
3) Ok, I'll do the rest of my ideas for the home screen aswell.
And thanks for the feedback, you're one of the few who actually tests and reports.
Last edited by sWORDs on January 31, 2010 07:44.
