Hi everybody. I’ll try to be as clear as I can …. And sorry for the wall of text but I thought more detail the better.
Basically I have JRiver commiting lots RAM -- actually using between 1go and 1.6go of memory on my main Win7 pc (server) and between 500k and 1.5go in memory on an older XP machine (client). The more zapping, the more resources – if I just listen to a full album it settles down to about 500 to 750k after about 15 minutes. Thought it was a problem with the XP client, but it seems to me its on the server PC – the Win7 PC which uses a similar amount of memory when not on the network (500K when not playing anything)
Win7 Memory
Win7 Network
Can
anybody help me figure this out?
I’ve tried for over a week just about everything, basically making client and network unusable
Setup:
JRiver version 18.0.193
Client (“Upstairs”) Win XP/4go RAM/CPU dual core 3.0khz – (crappy PC speakers only)
Connected by CPL (85 Mbps^^ -- I know that's slow, but it worked fine before
Server (Downstairs) Win7 Pro 64bit/i5 2400/8go Ram (has nothing to do with it I’m sure but …optical connection to external DAC=> preamp=>active cards=>amps=>speakers w/passive crossovers by-passed)
PCs with 1go Ethernet cards (client connected direct to router, btw)
I have a medium to large size collection I guess? (2.2 tb about 5700albums/82K flac tracks located on the server PC, including a small quantity of videos which I never watch from the client). In the past I had library servers running on both machines, I’m using it only from the server now.
The “Downstairs” library (36.1mb indicated in pop-up) takes almost 5 minutes to load on the client! – 6 months ago it took maybe 30seconds, and I have only added about 20 cds since then. It virtually floods the network too. I have to explain a little bit though because I haven’t been using the client for a number of months. I noticed a big lag on my network reusing the xp machine and JRiver -- first I noticed it was on version 17 because it was updating itself to the last build. The server was already on 18. So of course I put MC18 on the client machine. At first I was convinced it had nothing to do with MC because playback was always flawless on my stereo. And there haven’t been any posts here of a similar problem for years. So, I started checking everything … a couple of days ago, with no computers connected to the network except the server pc, and listening to music with no problems, I decided to check what processes were running and I noted that jriver was taking so much RAM without even being solicited from the network at all. I just never noticed it before, probably because my i5 and 8gbRam are a little overkill just for listening to audio and internet usage (basically the only programs I have running are JRiver and Chrome and an av)
What I’ve already checked:
- router settings/firewal
- antivirus and firewall settings that might interfere (Bitdefender 2011/2013 – haven’t uninstalled however)
- client and server settings in JRiver (I messed with those so much I’m not sure if its the right config anymore) – because I use the client to tag to the server I have deactivated the automatic library sync, too no change either way. Of course, I played with the buffer setting, but there are so many new server options that I don’t know what is right anymore (looked everywhere here for an explanation btw not in wiki either. Also I noticed in DLNA Audio=>Advanced I can’t un-check volume levelling or stereo downmix to see if that would make a difference. (never even saw these options before)
- I reverted both PCs back to version 17 – no real difference; but loading version 16 there was a significant one – was only using 136kb, compared to 1.2-1.6 gb that’s a big difference.
- Ran deep av and malware scans on both machines just to be sure
I’m attaching system logs; for more exact details … one thing strange with those is that I upgraded both machines to 18.0.193 yesterday but it still indicates I’m using 18.0.189 in the log?!
Thanks to everybody in advance who actually took the time to read all this. Pulling my hair out, it’s probably just something stupid on my part. ?
best,
Steve