More > JRiver Media Center 30 for Linux
JRiver Media Center 30.0.55 BETA for Debian Buster (amd64, i386, arm64 and armhf
bob:
--- Quote from: mwillems on January 27, 2023, 09:22:53 am ---bob is it useful to test this with mixed versions? That is to say, should I ensure that the server and all clients are updated to 55 to test, or is it ok to do piecemeal updates for testing? It looks like the main changes are client side, so I'm tempted to test on clients before updating the server, but if that won't expose the new functionality I'll move everything up together.
--- End quote ---
All of the changes are client side so you shouldn't have to do anything with the server.
mwillems:
--- Quote from: bob on January 27, 2023, 10:46:13 am ---All of the changes are client side so you shouldn't have to do anything with the server.
--- End quote ---
Good to know, I'm testing on a client and will report back.
mwillems:
After two-ish hours of playback, I'm seeing normal behavior and good performance. For the past several builds I had been getting frequent but brief UI freezes on clients (five seconds freeze every five or ten minutes or so). They mostly didn't interfere with playback, and I couldn't figure out how to repro them so I hadn't reported a bug. I also was getting an intermittent playback hang on clients after an hour or so of continuous playback where the track would seem to advance on the UI but sound playback would halt and not recover until I stopped and restarted playback (I wasn't sure if that was a new issue as I'm mostly an album listener, so I mostly run into the issue when putting on a playlist once in a while).
I have seen neither of those issues with the new build after well more than an hour of continuous playback, so I suspect the changes are working. I also greatly appreciate the new window drawing method. Much nicer!
The only "downside" is that MC's memory usage seems noticeably higher than usual (about 50-60% more memory five minutes after launch), but I suspect that's an unavoidable side effect of keeping another copy of the library in memory? Not a big deal in any case, just reporting in case it's unexpected.
I'll report back if I see any actual issues.
bob:
--- Quote from: mwillems on January 27, 2023, 12:32:35 pm ---After two-ish hours of playback, I'm seeing normal behavior and good performance. For the past several builds I had been getting frequent but brief UI freezes on clients (five seconds freeze every five or ten minutes or so). They mostly didn't interfere with playback, and I couldn't figure out how to repro them so I hadn't reported a bug. I also was getting an intermittent playback hang on clients after an hour or so of continuous playback where the track would seem to advance on the UI but sound playback would halt and not recover until I stopped and restarted playback (I wasn't sure if that was a new issue as I'm mostly an album listener, so I mostly run into the issue when putting on a playlist once in a while).
I have seen neither of those issues with the new build after well more than an hour of continuous playback, so I suspect the changes are working. I also greatly appreciate the new window drawing method. Much nicer!
The only "downside" is that MC's memory usage seems noticeably higher than usual (about 50-60% more memory five minutes after launch), but I suspect that's an unavoidable side effect of keeping another copy of the library in memory? Not a big deal in any case, just reporting in case it's unexpected.
I'll report back if I see any actual issues.
--- End quote ---
Thanks for the report. I'll ask about the memory usage.
How large is your server library (# of media files)?
mwillems:
--- Quote from: bob on January 27, 2023, 12:34:44 pm ---Thanks for the report. I'll ask about the memory usage.
How large is your server library (# of media files)?
--- End quote ---
I've got about ~135k files (75k audio, 50k images, and 9k video). A zipped library backup sans-thumbnails is about 20MB.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version