Steinberg can you please allow us direct access to our finder / file explorer, VS. the media tab! This is the slowest thing about Cubase, as well as mediabay.
Studio One is much better in this regard. Yet I prefer Cubase, we really need you guys to focus on faster access to our files, direct access to the file explorer would be so much faster.
What do you mean by “direct access”? As is I can open Explorer and drag stuff back & forth directly between it and Cubase. How much more direct is there?
I mean directly to your finder, or in windows file explorer… Such as Presonus Studio One’s browser…
With Cubase, their Media Tab, is not even close to the speed, of your finder / file explorer… Such as Mediabay, this will never be able to have good speeds, so long as they keep their current code for the browser.
Cubase needs to have free direct access to our actual browsers within Cubase.
Can you NOT NOTICE the slow speeds ?
Do you Not Notice when in the Media tab,when you click on a folder to reveal what’s in it, Cubase has to calculate a results list / similar to Mediabay… They need to bypass Cubase’s layer of code preventing it to just seek,search and find, using your cpu’s own architecture to do so.
OK, lets try again.
Please describe the specific changes you would like to see implemented. When it is behaving the way you want - what does that look like? Once you got that, you should also add a Feature Request tag to your thread.
1 Like
Hi,
The Feature Request would be, for Steinberg to remove the code that prevents Cubase to operate like other DAWS such as Reaper and Studio One, where their browsers have direct access to search,seek functions as the CPU’s OS and architecture supports.
At this point, Cubase does not support direct access to our OS, without a layer of their dated code that is slowing down the Cubase Media Tab / and Mediabay.
In my experience, the Cubase File Browser/Media Bay is no slower than the Windows 10 File Explorer.
Me neither. But I only use Media Bay & not the File Browser like the OP is using.
I was able to figure out how to get mediabay to load much faster now after learning the way a fellow forum member explained how to get it running properly. 
Would you care to share for others’ in the same predicament?
1 Like
With Cubase 13 the MediaBay was switched to a client / server implementation. That was done for HALion 7 in advance. Now there is only one database, and tags are in sync across those apps.
The process that is scanning your content is the Steinberg MediaBay Server, you can see it in the Windows Task Manager / macOS Activity Monitor. Cubase starts the Server so the permissions are passed on.
Regarding performance: The MediaBay supports a concept of Volume Databases: Do a right click on a volume in the MediaBay Tree in Cubase / Nuendo and select “Create Volume Database” - best before scanning!!! That will separate your scanned library content from the all the preset and VST Sound content. If not creating such a Volume Database all media is put into one database and browsing presets can become very slow, depending on how large your libraries are.
Btw. those Volume Databases are shared between products (even between C12 and C13), but they do not immediately communicate updates between the products, as the MediaBay Server does. (e.g. edit a Rating in HALion 7 and see the “real-time” result in Cubase 13).
Note: Volume Databases are created in a “.steinberg” folder in the root of the drives, so write permissions must be granted for the feature to work.
Deactivating Antivirus / creating exclude rules only for your libraries (after manual AV check) is a good idea. Checking the permissions on the volume is another good idea. If trouble persists I can help with activating logging and analysis of logs.
The appearance of hidden files is something we can fix, I’ll talk to our planners for next actions.