More > JRiver Media Center 25 for Linux

JRiver MC25 Docker Image with WebUI as VNC

<< < (10/14) > >>

max096:
Automatic music import works for me now too (instantly). Not sure since when. But it sure does, now!  :)

max096:
Just found another bug. I wasn't able to input anything into the textboxes in any of the options. That has been fixed now though. Didn't notice this myself since back when I created the container it worked. But the script that I wrote to force the window to not be minimize-able broke it. Now it works again.

max096:
If anybody had a problem with high cpu usage, because of repeated "screen -l" This now works much better. I didn't notice this running it on my NAS. But I now have set up a VM for some testing for another project with a single fairly low-end vcore (around 10% of my 4790k in that system). It was using around 90% cpu doing nothing. All of which was due to calling "screen -l" A LOT. Now this is down to 2% usage on that same system.

So, I would highly recommend to anybody who is using this container now and cares about cpu usage to update to one of the new builds.

That's about the only change that happened screen is gone. R.I.P. screen. The issue didn't really happen because of screen, but because when calling screen the command effectively is done immediately. x6-overlay then assumes the service is dead and runs the start script again for that service. Then it does that again... and again.. until the end of days. I knew that before, that's why I checked wether the screen is already running in the startscript. But I wasn't aware that this can use up quite a bit of cpu usage.

max096:
I now have done the "version" tagging I said I was gonna do when the docker image is stable.

The tags latest and stable are rebuilt every sunday to the newest version of the base image and jriver of the stable and latest repository.

Whenever a new JRiver version is released it's also gonna create a tag with "25.0.50-stable-1" for example.
The first part being the JRiver version. The second the repository and the third one is the image version (meaning whenever I change something that changes the resulting image the number will go up). The image from 0 to 1 didn't really change. All that changed was I included a VERSION file within the image that contains the image version. Before there was no version. So the two images that existed before are now "25.0.50-stable-0" and "25.0.80-latest-0".

Old versions won't be built. But if in the future a new base image or new jriver version ends up causing problems, you can easiely revert to an older version, by changing the tag.

max096:

--- Quote from: shortie on July 10, 2019, 05:20:16 pm ---I found nothing definitive when comparing the directories but I think I may have an idea now just from using it. I think it may have to do with either moving the window or resizing it. Those are the only two things I've done since clearing my config directory and installing from scratch.

UPDATE: It doesn't seem to have anything to do with moving the window. I haven't been able to figure out how I resized it before.

--- End quote ---

Do you still have that directory that bailed? If so Im curious if the current container would fix that. Any of them. I think with the current container even if a window where to pop up behind something it should be pulled in front right after the window changed.

Otherwise, could you send me said directory confidentially? Just send me a private message then, not a good idea to post folders that potentially contain license information on a public forum.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version