Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Diverdown1964]

Hi folks. I'm new to participating here, but I've been lurking for a while. First off, I want to commend the entire team for an amazingly powerful, yet intuitive piece of software, I'm recommending it to anyone that will listen.

I have a fairly large MP3 collection (> 33000), and I use media server extensively. It seems the last few builds (since the TiVO support) have developed a connection bug. Unfortunately, I've been unable to nail it down totally.

Sometimes I can connect, and then about 10-12 songs stream. and the end of the last song, something hangs and it's not possible to reconnect until both servers are rebooted (and sometimes it has trouble even then). Sometimes the client crashes (MEDIA CORE dump) trying to connect to the server, and sometimes it just doesn't find the server at all.

I've tried with both the "find server on network" option, and explicitly entering the connection info. Same results. Everything  is on the same 192.168.x.x subdomain. The only wrinkle is that my cklient is wireless, although my network link is strong and healthy.

Thought you may want to know this as you're preparing to ship.

Again, thanks for such a useful product.

[Diverdown1964]

One more thing, I'm currently experiencing these problems on 9.0.155.

[Diverdown1964]

On the media server in question, when "Stop Sharing is selected, it displays the followiong message:

04/19/03 11:48:26 - bad port <>
04/19/03 11:48:26 - tcp_write failed error=10038
04/19/03 11:48:26 - bad version

[Harry_The_Hipster]

That's a variation on what I'm getting. This was also discussed in the following thread: http://www.musicex.com/cgi-bin/yabb/YaBB.cgi?board=beta;action=display;num=1050500620

It does seem to go back 6-8 builds. Would this have anything to do with changes implemented for TiVo/HMO? The time frame matches up. Maybe John T can comment.

When I started this message, there were no connections to M/S either locally or remotely, yet the log was showing one connection. I then went in to check settings, M/S asked me if I wanted to reconnect, I selected Yes, wound up with the following:

04/19/03 12:52:33 - Current Connections: 1
04/19/03 12:52:33 - ready for another connection
04/19/03 12:52:33 - private sharing thread started
04/19/03 13:07:57 - bad port <>
04/19/03 13:07:57 - tcp_write failed error=10038
04/19/03 13:07:57 - bad version
04/19/03 13:07:58 - Stopped auto response thread.
04/19/03 13:07:58 - sharer starting
04/19/03 13:07:58 - Initializing server.
04/19/03 13:07:58 - Server initialized
04/19/03 13:07:58 - sharer ready to accept connections
04/19/03 13:07:58 - Started auto response thread on port 5556.
04/19/03 13:07:58 - connection closed 3?
04/19/03 13:07:58 - read_http_request failed: -1

Autoport selection is activated.

HTH

[John Gateley]

I found a similar behaviour at home this weekend, but couldn't spend a lot of time checking it. HTH: did you get the "too many connections" problem again?

j

[Harry_The_Hipster]

This is what I got today. Notice the '4 current connections'!

04/21/03 15:46:36 - sharing thread exiting
04/21/03 15:56:14 - connection closed 3?
04/21/03 15:56:14 - read_http_request failed: -1
04/21/03 16:00:49 - connection closed 3?
04/21/03 16:00:49 - read_http_request failed: -1
04/21/03 16:23:52 - received a connection
04/21/03 16:23:53 - Current Connections: 2
04/21/03 16:23:53 - ready for another connection
04/21/03 16:23:53 - private sharing thread started
04/21/03 16:31:10 - received a connection
04/21/03 16:31:10 - Current Connections: 3
04/21/03 16:31:10 - ready for another connection
04/21/03 16:31:10 - private sharing thread started
04/21/03 16:36:12 - received a connection
04/21/03 16:36:12 - Current Connections: 4
04/21/03 16:36:12 - ready for another connection
04/21/03 16:36:12 - private sharing thread started
04/21/03 17:05:53 - connection closed 3?
04/21/03 17:05:53 - read_http_request failed: -1
04/21/03 18:25:39 - connection closed 3?
04/21/03 18:25:39 - read_http_request failed: -1
04/21/03 18:31:12 - connection closed 3?
04/21/03 18:31:12 - read_http_request failed: -1
04/21/03 18:32:11 - received a connection
04/21/03 18:32:11 - Current Connections: 2
04/21/03 18:32:11 - private sharing thread started
04/21/03 18:36:15 - connection closed 3?
04/21/03 18:36:15 - read_http_request failed: -1
04/21/03 18:46:51 - received a connection
04/21/03 18:46:51 - Current Connections: 2
04/21/03 18:46:51 - ready for another connection
04/21/03 18:46:51 - private sharing thread started
04/21/03 18:52:23 - received a connection
04/21/03 18:52:23 - Current Connections: 3
04/21/03 18:52:23 - ready for another connection
04/21/03 18:52:23 - private sharing thread started

At the client end, created a playlist of `15-20 files, around the 6th or 7th file, buffering, then stopped, followed by the message re checking the file path. All mp3s at 128. No wma or ape, no higher bitrates.

M/S not very useful in its present state. Again, seemed to go downhill @ the time the TiVo/HMO features were added.

Hope this helps.

HTH

[JimH]

Have faith.  We'll get it.  Life deals some cruel blows sometimes.  This isn't one.

[Harry_The_Hipster]

Life deals some cruel blows sometimes.

Like my last 401k statement.

HTH

[John Gateley]

Like my last 401k statement.

Ouch! That hurt.

This helps a little: connections are not being closed on time.

Do you have any internet radio stations or anything in your playing now? I'm guessing no, but...

j

[Harry_The_Hipster]

No radio stations. When I initiate playback on the selected files, they would all appear in Playing Now, if that's what you mean.

One of my busines partners refers to his '201k account'. I think he's being over-optimistic.

HTH

[Diverdown1964]

No radio stations for me either...

[John Gateley]

Hi funnyguy, HTH,

I had no luck reproducing problems today. Can you try the version coming out soon and then mail your entire log to me (gateley @ jriver.com)? I cleaned up the logging messages, so hopefully I'll be able to get a clue.

I'm going to do more testing tonight as well (from home to work).

j

[Diverdown1964]

Hi John.... I'm John too.

Would you like me to try 157, or wait for 158?

[KingSparta]

Hi John.... I'm John too.

Would you like me to try 157, or wait for 158?

I just tested 9.0.157 and it works good

04/22/03 19:09:48 - TiVo streaming http://64.236.34.141:80/stream/1004/~~~stream~~~.mp3
04/22/03 19:10:13 - TiVo streaming http://64.236.34.141:80/stream/1015/~~~stream~~~.mp3
04/22/03 19:10:26 - TiVo streaming http://64.236.34.141:80/stream/1019/~~~stream~~~.mp3
04/22/03 19:10:42 - TiVo streaming http://64.236.34.141:80/stream/1024/~~~stream~~~.mp3
04/22/03 19:11:28 - TiVo streaming http://205.188.234.66:8010/~~~stream~~~.mp3
04/22/03 19:12:25 - TiVo streaming http://scastsrv2.shoutcast.com:8048/~~~stream~~~.mp3

[Diverdown1964]

Trying 157 Right now. So far, so good, although the server didn't respond to the autodetect request.

I'm also noticing that the cover art doesn't appear on the client machine, while it does on the host system.

I'm going to let it run for a while and send in thye log file.

[Diverdown1964]

OOps... spoke too soon. It just died. I'll send in the log shortly.

[Diverdown1964]

Still seeing the problem with build 162. Does this line from the server line mean anything?

04/28/03 19:03:13 - tcp_write failed error=10054

[John Gateley]

Hi, I'm still thinking about this. Do you still get the "continuous play" problem (where the client thinks it's playing a radio station instead of a file)?

The error just means the client closed the connection and the server noticed this while trying to write data. It's normal when the client stops playing.

j

[Diverdown1964]

I get the continuous play problem occasionally, but not always. More reproducable is that it plays for about 10-11 songs, and then simply stops responding. The screen says buffering - but it's not responsive at all. MC needs to be hard stopped (through task manager).

I very much doubt that it's related, but I have cover art stored in most of my mp3s, and they don't display on the client machine.