Workspaces
Last updated
Last updated
Mimiq's Workspaces feature allows you to use non-NAS-type storage with Media Composer. It lets you remount any folder in a Media Composer-compatible way, akin to how NEXIS makes folders on shared storage available. This allows you to use any type of storage for bin locking. This is particularly useful for utilizing non-NAS storage like RAID, SAN (e.g., Quantum StorNext), and local folders as independent NEXIS shares.
Workspaces are only needed when your shared storage is not a NAS or macFUSE volume. Do not use Workspaces to create shares for your NAS, but use your NAS's software instead.
Click the Mimiq icon in the menu bar (macOS) or System Tray (Windows), then + Add Workspace.
Select a folder to create a Workspace, then click Select (macOS) or Select Folder (Windows).
Your Workspace will appear in Mimiq with a green 🟢 status, then mount in Finder (macOS) or File Explorer (Windows).
You can access your Workspace through Finder (macOS) or File Explorer (Windows) or double-click a Workspace listed in Mimiq to open it in a new window.
Ideally, you don't have Media Composer open while creating Workspaces, as it will detect your new Workspaces only after a restart of Media Composer.
Workspaces do not scale indefinitely, it's always best to use as little as possible as each Workspace will add overhead to your overall bandwidth.
On macOS, the usable amount of simultaneously active Workspaces depends on your system resources.
As Workspaces on macOS rely on macFUSE, there's a limitation on how many Workspaces can be used simultaneously. Our tests have shown that a maximum of eight Workspaces is practical. However, as this number correlates with your hardware and system load, it's possible to increase or decrease this amount.
Using Terminal.app, set the maximum number of Workspaces that can be enabled simultaneously:
Then, commit the new setting by starting Mimiq. If Mimiq is already active (i.e. its icon shows in the menu bar), quit and restart Mimiq.
If needed, you can use this command to check the current Workspaces limit:
It's just as easy to reset the amount back to the default value of 8:
On Windows, Workspaces utilize available drive letters for mounting. Due to the limited number of drive letters in Windows, there's a constraint on how many Workspaces can be mounted simultaneously.
By default, Mimiq attempts to mount the first Workspace using the drive letter M:. Subsequent Workspaces are assigned the next available letters in alphabetical order.
If M: is already in use on your system, you can modify the starting drive letter. This can be useful if you want to reserve certain drive letters for other purposes or if you prefer a different range of letters for your Workspace(s).
Using PowerShell, define a different starting drive letter:
Change the starting drive letter
Then, commit the new setting by starting Mimiq. If Mimiq is already active (i.e. its icon shows in the menu bar), quit and restart Mimiq.
Resetting the default drive letter is just as straightforward:
Click the Mimiq icon in the menu bar (macOS) or System Tray (Windows), mouse over the Workspace you wish to disable, then click (⋯) > Disable.
Your Workspace will appear in Mimiq with a grey ⚪️ status.
Disabling a Workspace renders it temporarily unavailable to Media Composer without removing it. You may want to disable a Workspace to simplify media management by reducing the number of volumes Media Composer can read from / write to.
Click the Mimiq icon in the menu bar (macOS) or System Tray (Windows), mouse over the Workspace you wish to remove, then click (⋯) > Remove Workspace.
Once you remove a Workspace, it's ejected from your computer and no longer available in Media Composer until you add it again.
Media Composer cannot cope with volumes mounting/ejecting (or connecting/disconnecting) while it’s open.
If you need to add/remove/disable a Workspace, quit/exit Media Composer first.
Unreachable?Either your shared storage is unavailable (e.g. disconnected from the network, powered off), or someone renamed the source folder you selected.
Take the appropriate action to make that source folder available again, then quit-then-relaunch Mimiq.
If Mimiq still says the Workspace is Unreachable, you may have to remove the Workspace and then re-add it.
No lockable volumes found? Unlike other eligible volumes, Mimiq will not show the mount point of your SAN share as a lockable volume.
Yes. Mimiq saves paths to Workspaces in a JSON file:
~/Library/Application Support/Mimiq/Workspaces/MimiqWorkspaces.json
You could even sync this JSON file among your local and remote team members using something like Resilio Sync, as long as you sync it among Mimiq users with a matching operating system.
System Extension Blocked. What can I do?If your Mac is managed through MDM, stop now and contact your System Administrator.
Starting in macOS Big Sur, the local kernel extension (i.e. kext) database in macOS may not retain your decisions on approving third-party system or kernel extensions to load in macOS. If macOS doesn't load macFUSE despite multiple approvals from you, you can safely reset macOS' kext database, which revokes approval for all third-party kexts installed on your system volume.
Once you reset the local kext database, you can log back into macOS and approve any/all system or kernel extensions installed on your Mac.
Save any open work, then power down your Mac.
Choose your system volume, log in with a macOS Administrator account, then launch Terminal.
Use this command to reset your Mac's Kernel Extension database:
kmutil trigger-panic-medic --volume-root /Volumes/(SYSTEM VOLUME)
If your system volume has a space in its name (e.g. Macintosh HD), enclose the volume name in quotation marks (e.g. "/Volumes/Macintosh HD").
Press the (Return) key.
If you entered this command correctly, you'll see this response, All third party kexts have been unapproved and uninstalled from /Volumes/(SYSTEM VOLUME).
Restart your Mac.
Once you log into macOS, you'll likely be greeted with multiple dialog boxes saying...
System Extension Updated
System Extension Blocked
...along with confirmation that you triggered the Panic Medic Boot.
You've successfully reset your local kext database in macOS.
When you create a Workspace from a local drive, and that drive already has a label in File Explorer, the label of the parent drive takes precedence over the Workspace label assigned by Mimiq. In other words, File Explorer will display the existing label of the parent local drive instead of the Workspace label.
To make the Workspace's label visible in File Explorer, you can remove the label for the parent drive.
To display the Workspace label assigned through Mimiq, follow these steps to remove the label from the parent drive:
In File Explorer, create a new window, then locate the parent drive.
Right-click on the parent drive and select Properties.
In the Properties window, locate the General tab.
In the Label field, delete the existing label text.
Click Apply and then OK to save the changes.
For a LucidLink Filespace, use PowerShell to remove the drive label:
Open PowerShell.
Run the following command:
lucid config --set --local --FileSystem.MountPointWindowsLabel ""
Remount the Filespace.
As long as you have read and write permissions to that share, once you , Mimiq will activate Bin Locking on that folder.
Once your Mac is fully powered down, .
, and any other existing system or kernel extensions, to load in macOS.
