Thanks for your responses guys. Let’s me know I wasn’t imagining things. If you use the uninstaller and revert to 5.1.20 it seems to be ok, but I am still confused as to how this content even appeared. I liked the idea of the media bay update in line with the other units, but what’s all of this about?
Please can somebody from Steinberg resolve this (i.e provide a new fix) and identify exactly what extra content has been added so I can delete those files.
I couldn’t tell you , i don’t know if it’s kits missing or Filters not working to stop the other UNPAID for libraries from being seen .
It’s not a biggy to me BUT im more concerned about the Download Assistant forcing people that are on C12 to install the latest Mediabay which may F’up their systems , it just makes the DLA to damn volatile to even visit , say you are on C12 and the latest version of Cubase is 14/15 and you buy a loops kit or preset’s or something , you are forced to install the latest mediabay as far as i can tell , there’s been no clarification on this situation which really does put a halt on my purchases
Yeah, can’t say medially has changed much as far as I can see apart from a few refinements. I could be wrong of course, but I see your point and agree that we should get a heads up if this is likely to compromise previous installs. I will certainly be hesitant after the GA update. I would understand if it was v6 or something, but the same iteration should not be giving me these kind of issues. If they wanna throw me some free expansions maybe, but don’t wreck my library with useless entries I cannot access.
Close down Groove Agent, delete the Groove Agent preferences folders and your MediaBay prefs and start over. All mine are gone. Basic troubleshooting folks, come on now.
Errrmmmmmm having to delete preferences every single update is NOT ideal , what about if Backbone has an update next week ? delete Prefs , Halion the week after ,delete prefs ? get where im coming from ?
1 Like
Well , i was just about typing a lovely solved praise in a thread i started but the Powers that be with the chip on the shoulder with me still continues and deletes the thread even thou it was a VALID ISSUE ! . sooooooo
Just six more preferences To delete now Steinberg . And sort the forum out !
So two people have had this issue? Or is it three? Or, have only two or three people updated?
I just to had refresh my Steinberg license and all red warning was gone
1 Like
I think you spoke too soon , just wait till the weekends over Bud then you see it’s not just OUR two or three machines as your trying to insinuate 
Ahh I didn’t think to try that. Figured GA was working fine, must have been a MediaBay issue so I just deleted those prefs haha. I’ve had to do that a lot lately trying to get all my crap imported into Halion so it was no thing to delete it yet again.
Was it exactly the same issue with the same Kits in red ?
So try deleting the Mediabay preferences… As mentioned, we shouldn’t HAVE to do this after every update, but this was integrating the new Mediabay to Groove Agent. Halion already got this one awhile back when 7 was released. There’s bound to be some hiccups and changes that need a little kick to get going.
It’s somewhat of a ‘big’ change, and once in awhile you have to just wipe those out to make the new version start working smoothly. Seen it happen plenty of times going from firmware to firmware on my MPC even (it’s worse with betas). Deleting them on the MPC means, I have to go back in and setup the entire thing again. All my MIDI ports, my sampler settings, sequencer settings, etc. Mediabay is one of the least problematic bits of software to troubleshoot in that respect hah. Deleting Mediabay’s preferences, do nothing whatsoever, but force it to rebuild the database. All your tags and content is still there. I have to do it every now and then in Halion after importing an old AKAI cd or converting some Halion 3 presets. Sometimes it just gets ‘stuck’ and you’ve got to give it a smack to make it update.
1 Like
Due to the fact that the new Cubase media bay does not see user exported midi files. Quite a biggy for a media bay especially within a drum vst that uses midi files for its pad patterns, I would recommend that you don’t install this update.
Indeed. My first instinct in this scenario would not be to start modifying files. The software should be integrated from the jump. I want also to know the next revision is fully compatible before migrating. Are these new library entries included in Cubase 13? I seem to have 300mb or so of sound content that I don’t own and must have been included in the DLA install. I run Cubase 12 Pro currently. Maybe in line with your point you could choose to simply turn off the automatic updates for media bay or whatever is creating this conflict.
The groove bay update has broken my Cubase mediabay’s ability to see new user midi. It’s system wide not just groove agent…
Hello guys.
For my surprise all these files are missing in my Groove Agent and I cannot see from which content set it belongs to.
I’ve tried to refresh my Steinberg license but not success this time.
Help me pls
1 Like
The same with midi in groove agent 5. Where I can find these preference files to delete them?
After the update 5.2 the part of the UI where you can tweak MIDI Drum Patterns is a mess - collumns mixed up, no sound on click etc…went back to 5.1…Cheers!
Allen Morgan Signature drums not working in 5.2.0 update. Error dialogue on loading kits, which is not present 5.1.20.