Socket disconnects

[mvallevand]

I have found that the last couple of versions from 20 & 22nd march have not performed well neither managed more than about 40 mins at a time

I have uploaded a new dongle which I think gets rid of the conflict between the unsolicited request to play the next song and the unsolicited screen saver update. I based the logic on the GBPVR screen saver update arriving at approx. 10 second intervals, although I couldn't find a config.xml setting for this

The way the logic now works, is at the end of a song, emulation mode will not sent the end of song notice if it is expecting a screen update (ie between 9 and 11 seconds) until after the screen update is received.

On my latest test I've now gone 11 hours with MP2 streaming which is the longest I've ever had. In those 11 hours the conflict happened 20 times so there was a good chance the old dongle would have closed the socket.

I ended up taking out all the gapless code but assuming this new logic works, I should be able to reinstate something.

Martin

[mvallevand]

I've successfully run last night's dongle for thirty hours straight with ML2 , so the prime issue is definitely resolved. With 3.1 GB transfered almost 900,000 packets and I guess this is as close to a kiosk type player as I can expect.

Martin.

[tkgafs]

I've successfully run last night's dongle for thirty hours straight with ML2 , so the prime issue is definitely resolved. With 3.1 GB transfered almost 900,000 packets and I guess this is as close to a kiosk type player as I can expect.

Martin.

Sounds good

I'm afraid I only managed a paltry 8.5 hours the first time but strangely only 20 mins after that restart

I haven't been able to test any more yet but will try a run overnight tonight

tkgafs

[mvallevand]

Sounds good

I'm afraid I only managed a paltry 8.5 hours the first time but strangely only 20 mins after that restart

I haven't been able to test any more yet but will try a run overnight tonight

tkgafs

Did it stop while playing with ML2 or while using the remote? I've been focusing on the playing time, I expect there still could be unavoidable collsions when the remote is clicked between songs. Also when it stopped did it crash or did ML2 just stop playing music?

Martin

[jim08127]

Not sure if this thought is helpful. Is there anyway to test the frequency of the conflicting screen saver data and adjust dynamically in your code?

[tkgafs]

Did it stop while playing with ML2 or while using the remote? I've been focusing on the playing time, I expect there still could be unavoidable collsions when the remote is clicked between songs. Also when it stopped did it crash or did ML2 just stop playing music?

Martin

I dont actually know as I was at work, I just started it in the morning and turned the tv off, when I returned the mvp was back at the mvpmc menu I would imagine it was just playing as its unlikely my wife touched it.

when I restarted it by clicking on emulation mode it ran for about 20 mins and it was simply playing music no one touched the remote

Tkgafs

[mvallevand]

Not sure if this thought is helpful. Is there anyway to test the frequency of the conflicting screen saver data and adjust dynamically in your code?

Because the vnc-like data is hard to distinguish the only way I could think if is to take an average for update interval ignoring those not near a keystroke. As long as it is 10 seconds this won't make too difference, it is not exactly 10 sec. anyway.

Martin

[mvallevand]

I dont actually know as I was at work, I just started it in the morning and turned the tv off, when I returned the mvp was back at the mvpmc menu I would imagine it was just playing as its unlikely my wife touched it.

when I restarted it by clicking on emulation mode it ran for about 20 mins and it was simply playing music no one touched the remote

That's disappointing so I tried again overnight with the actual alpha and it is still running. I'll check after work

Here is the ifconfig output at the start

~ Midnight
RX packets:19135 errors:0 dropped:0 overruns:0 frame:0
TX packets:12044 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:25460368 (24.2 MiB) TX bytes:0 (0.0 B)

7 1/2 hours later

RX packets:579152 errors:0 dropped:0 overruns:0 frame:0
TX packets:379185 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:762145306 (726.8 MiB) TX bytes:0 (0.0 B)

It did crash after 14 hours

RX packets:1103519 errors:0 dropped:0 overruns:0 frame:0
TX packets:722786 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1451916782 (1.3 GiB) TX bytes:0 (0.0 B)

But the error did happen where I think there is a problem in gbpvr (the 20 comes from me)

02:31:14.062 VERBOSE [8] Responding to ping
02:31:14.062 VERBOSE [8] getValue cached value: /settings/DisableHauppaugeMVPScreenSaver : true
02:31:14.062 VERBOSE [8] MVP request processed
02:31:14.082 VERBOSE [10] Y/Y2 buffer: 2711 bytes
02:31:14.092 VERBOSE [8] MVP data read: 1 (4)
02:31:14.092 VERBOSE [8] User pressed: 20
02:31:14.092 VERBOSE [8] MVP request processed
02:31:14.122 VERBOSE [10] U/V buffer: 1088 bytes
02:31:14.122 VERBOSE [10] incremental frame sent
02:31:14.122 VERBOSE [10] MVP async queue items: 1
02:31:14.122 VERBOSE [10] MVP async queue handling key: 20
02:31:24.067 ERROR [10] MVP Timer Refresh error: An established connection was aborted by the software in your host machine
02:31:24.087 ERROR [10] at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.Socket.Send(Byte[] buffer)
at GBPVR.xbb1566157f5f8b1f.xcca58d4608994dd8(Point x557cda7ca079f710, Rectangle x19534874af95b268, Bitmap x84901bd355736ef6, Boolean x484012b92f24af4e)
at GBPVR.xbb1566157f5f8b1f.xe75b6be209ce111f(Image x84901bd355736ef6)
at GBPVR.xbb1566157f5f8b1f.xb1cbc922a07ef39b(Object xdf2e3583f942db7b, EventArgs xc4f45905cb1fc7ba)
2007-03-29 02:32:24.094 VERBOSE [8] MVP data taking too long, connection must have been dropped!


Martin

[tkgafs]

Hi Martin,

I'm still getting the disconnects the following one is after about 5 hours

2007-03-29 11:18:52.093 WARNING [23] Received unknown request of type: 133
2007-03-29 11:18:52.093 WARNING [23] Received unknown request of type: 224
2007-03-29 11:18:52.093 WARNING [23] Received unknown request of type: 0
2007-03-29 11:18:52.093 WARNING [23] Received unknown request of type: 0
2007-03-29 11:19:43.203 ERROR [25] MVP Timer Refresh error: An established connection was aborted by the software in your host machine
2007-03-29 11:19:44.078 ERROR [25] at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.Socket.Send(Byte[] buffer)
at GBPVR.xbb1566157f5f8b1f.xcca58d4608994dd8(Point x557cda7ca079f710, Rectangle x19534874af95b268, Bitmap x84901bd355736ef6, Boolean x484012b92f24af4e)
at GBPVR.xbb1566157f5f8b1f.xe75b6be209ce111f(Image x84901bd355736ef6)
at GBPVR.xbb1566157f5f8b1f.xb1cbc922a07ef39b(Object xdf2e3583f942db7b, EventArgs xc4f45905cb1fc7ba)
2007-03-29 11:20:46.359 INFO [2] UbuRadio destructor called


do you get lots of messages similar to

WARNING [23] Received unknown request of type: XXX

where XXX is a number

in the gbpvr logs, I have no idea what the messages are or what generates them but they are always there

I have attached the relevant logfile although I dont think it is of much interest

Tkgafs

[mvallevand]

Hi Martin,

I'm still getting the disconnects the following one is after about 5 hours

I will keep plugging away at this and getting dumps. It is tougher testing for me since it typically will take more than 8 hours. My older gbpvr machine is having trouble saving BIOS setting so this is saving me re-entering it anyway.

do you get lots of messages similar to

WARNING [23] Received unknown request of type: XXX

where XXX is a number

in the gbpvr logs, I have no idea what the messages are or what generates them but they are always there

Im prettty sure this error is a collision between the heart beat signal and the gui meesage indicating the progress within a song. I see these with the Hauppauge dongle too and its sort the of reverse to what I think is crashing emulation mode. I don't know how to avoid them or if this causes a problem for gbpvr.

Thanks,

Martin