another day, another strange thing??
In theory I have everything updated, including the media bay, which did not work through SDM…now I receive these random errors???
In theory I have everything updated, including the media bay, which did not work through SDM…now I receive these random errors???
MediaBay is running as a server in a process. This is what it looks like on Windows:
Maybe there is another instance of it hanging, ie. the process needs to be killed? Can this be done through the Activity Monitor?
Oh!! Sorry!!!
This has happened to me since I tried to update mediabay (because when I opened SDM it asked me to, but it had failed and I installed it manually). I don’t remember if this has happened before or after opening an instance of Cubase.
Sorry for my language!!
1 Like
Could not have written it better in Spanish, even if I was able to understand this language.
Sorry
Every now and then I have to restart my Mac because the media server continues to run and grow in the background after quitting Cubase. Hopefully this is something they have acknowledged and will be fixing in the near future.
You can just kill the process in Activity Monitor as indicated 2 replies up in this thread. If you’re more of a CLI-kinda-guy you could use:
kill $(ps aux | grep -i MediaBayServer | grep -v grep | awk '{print $2}')
Which works well if you need to assign a bash/zsh alias to it.
1 Like
I’m always skeptical to force quit processes but that would definitely be quicker than restarting.
Any idea why the media server continues to run?
No, I’ve only heard about it happening a couple of times. I haven’t seen any detailed information on what causes it. If you don’t mind rebooting, then it accomplishes the same thing in the end.
Your report is the first I’ve heard of it “growing,” which I took to mean increasing in RAM/Process time.
Yes, it takes up quite a bit of RAM and increases even with Cubase quit.
Guess I’ll just deal with it until there’s a fix.
I have my MediaBay results set to 65,000 and when running it fluctuates around 95meg of RAM. As I audition different samples that number increases of course, but I don’t experience the MediaBayServer process persisting after a normal app exit. If yours continues to incrementally increase the amount of RAM usage even after Cubase is closed, then I would ensure you’re all patched up. The C14 maintenance update just dropped, so there may be some fixes in there. Up to you if you choose to apply the update, but given what you’re experiencing it may be a good idea.
Yep just updated. See how it goes. Cheers for your feedback.
1 Like
I haven’t seen it in awhile but I’ve had it happen before here. I had some issues in the past where MediaBay would stop responding while auditioning files, and after it ‘recovers’ and starts moving again, the files I was trying to select somehow got corrupted and blown up into useless 4GB files (at least its easy to dig through my samples and figure out which ones were bad at that rate). Had to do Time Machine recoveries a few times to fix it.
After it happened a few times, I checked and noticed in Activity Monitor the server process was still going after Cubase closed. Force Quit every time. Knock on wood, hasn’t happened once in 14 so far. Media Server usually takes a few seconds to shut down after Cubase, but haven’t seen it stuck hanging around for awhile now thankfully.
1 Like
Same here. What I did notice is that if I tweaked my background process settings and did NOT allow the Steinberg com.steinberg.SilentInstallHelper.plist daemon to run, then MediaBay updates wouldn’t apply when I launched SDA, and I had to manually update MediaBay - it seems like MediaBay operates differently than “standard” updates in that it would just automatically update when SDA was launched, and NOT present a separate update in my Updates hive in the left-hand Product pane. But I don’t know that and haven’t been able to “catch it” in between to find out. But I can see what I perceive as “incremental auto updates to Media Bay Server” not being applied as potential issues…