I have multiple installations of MCEBuddy, and would like to monitor multiple stutus panels on a system… Since you have removed the multiple instance capability, could you please implement a multiple install window, so that one machine’s MCEBuddy would be on one section, and another on another section (allowing more than two would be a fair idea), this could be in a single MCEBuddy Status.
[FEATURE] MCEBuddy Status - create option to monitor multiple MCEBuddy's in one MCEBuddy Status window
Also, being able to “name” the installs on the different systems would be nice, instead of having to remember the network address…
This should be easy, start the MCEBuddy Status application more than once, it will more a new status window for each time you start it.
Click on the
Connection button at the bottom left of the screen. Enter your mcebuddy engine machine name or ip address (assuming you haven’t changed the port).
That Used to be true, but the LATEST update (2.4.8), removed the ability to open multiple instances of the status panel… You now get a “Cannot start duplicate instance” “ MCEBuddy Status application is already running” error box when you try to open a second panel…
Update to today’s 2.4.9 BETA build
The right way to connect to multiple engines would be to use the MCEBuddy Remote Client (since typically you’ll have only one engine per machine, each remote client can connect to a single engine).
This is a zip file, extract the files into a directory and click on the file
MCEBuddy.GUI.exe to start the remote client. The reason it’s a zip file is that windows only allows each setup to be installed once, hence you can’t install MCEBuddy more than once on a single machine. However using a zip file you can extract the files into multiple directories and start each one separately.
Remember you can start each directory install only once, so if you want say 3 dashboards, extract the zip file into 3 separate directories. Start each one separately. The added advantage is that the settings are stored in each directory’s config folder, so each remote client will remember which engine they were connected.
Now you can start multiple remote clients from your startup script to create a dashboard.
So the purpose of running remote client on computer 1 is simply to keep your eye on another machine, computer 2? Specifically, you have to set up Computer 2 to convert its own files, but the remote client allows you to monitor progress from computer 1?
Yes, that’s the idea of remote clients.
However, some of us maintain a full install on computer 1 for other purposes, including offloading some of the workload.
In that case, you could have Computer 1 working on files from a watched folder shared by Computer 2, but you would not want to have Computer 1 working on the same watched folder as Computer 2’s watched folder, i.e. you do not want Computer 1 and Computer 2 working on the same watched folder. Correct?
I have a dvr server, I also have it installed on my main pc.
I have the dvr server running all the time, recording and transcoding, but it’s headless (no monitor), and in a rack.
I have my main pc, that I occasionally try to offload the workload onto, to help get through the backlog, or, want to convert other media (still digitizing my physical collection), so it occasionally has things to do on it’s own. I want to monitor both computer’s mcebuddy’s, and even though I put the remote monitor, and the full version in different folders, it still gives me the only one instance error. I would like to see a “tile” option, in the monitor window, so that multiple computers can be monitored in one window.
And yes, I would also like to have the option to “share workload” added, with the one with the conversion que, in charge of sharing out the workload on a per job basis, flagging those jobs shared out so they can be skipped until A-the job is completed; or B-the system the job was shared with disconnects for x amount of time. This way, I could have some extra systems, sitting around doing nothing, pick up some of the slack…
What build version are you using? It’s working fine here.
setting the full mcebuddy window, also sets the remote mcebuddy window, when opened one at a time, but, I want to have status of both local and remote clients at the same time…
also, another post, I requested que sharing - being able to set-up a master instance on a machine, and set it to share it’s que with other instances on other machines. I often have large backlogs of conversions in the que… (as much as a hundred in que, or more)…
See my post above, we fixed it in 2.4.9 so download the latest BETA and then try it.
Have you checked out the posts on shared queues, distributed encoding and load balancing?
Yes, I saw that, he has a script to toss it back and forth…, looking for activity on specific programs…
Only my dvr server runs 24/7, the main pc, just turns on when I want to use it, but, most of the time, I’m just doing youtube/twitch/other media, but, I do do some gaming and other activities that require the cpu.
It took me weeks, to figure out how to write a script to simply move completed recordings off the dvr, onto the nas automatically in batches (to save hdd wear).
And then there are the permission headaches…
It seems, that if something could be integrated into mcebuddy to do que sharing (with file copying and file transfer of completed, it would go a long way.
What JoshDi did is good, but, I don’t think it would really work for me, I would prefer a share workload on off button on the mcebuddy panel, especially when using the “mcebuddy remote” panel…
I don’t know if I am just asking too much, or not.
I’m also considering hardware upgrades, as I am using repurposed/reconfigured/low power machines (most retired enterprise) to take up the 24/7 workload, but, $… I have my main pc, which can game, but, the rest, just have to do their job…, I just don’t Always need the heavy lifting for the dvr server…, so, low power, with enterprise reliability…
Sorry for the long post, and side rant. Having que sharing integrated into mcebuddy would help considerably, otherwise, it gets more expensive to continue my expansion of use… I am expecting to more than double my recording capability soon, and I already get soo backlogged periodically, it just isn’t funny anymore… I’m trying to figure out solutions… And I like to be able to monitor my hardware…