Best practices for Studio
Applies to:
- Revu 21
- Revu 20
The topics and guidelines presented below are designed to prevent potential storage and performance issues caused by extremely large file collections in Studio Projects or Sessions and to ensure the best possible collaborative experience. This information is based on the experience of our customer-facing teams that regularly assist hundreds of thousands of Studio users.
What is a Large Project?
The size of a collection of project documents is determined by following criteria:
- The number of files or sheets
- The combined file size of the documents, markups, or both
The following are examples of large document sets in Studio:
- A complete construction drawing or as-built set of 1,000 sheets
- A Studio Session hosting more than 100 drawing sheets comprised of any combination of single or multi-page PDFs
- A Studio Session hosting more than 250 MB of PDF files
- A Studio Session where more than 20 attendees are likely to markup the files
- A Studio Project where the total file size of the documents exceeds 10 GB
- A Studio Project where batch processes are likely to be used on PDF files with a combined file size of more than 100 MB or more, or a page count of at least 250 pages
Best practices
Design Reviews in Studio Sessions
Although the real-time collaborative capability of Studio Sessions greatly speeds up the design review process, the project becomes larger and more complex as the number of sheets increases. Here are a few steps you can take to ensure the quickest possible performance:
- Use the fastest and most stable internet connection possible.
While working with a large collection of documents or drawings, it is possible for a Studio Project to contain upwards of 25 GB of data. Downloading and uploading this amount of data to and from the Session and each attendee requires the fastest and most stable internet connection possible. - Minimize the file size of your PDFs as much as possible.
Before uploading your files, remove any unnecessary or unwanted content, such as layers, file attachments, and unnecessary markups (such as SHX file markups) included in PDFs exported from Autodesk AutoCAD.
Consider using the Reduce File Size feature in Revu.
- Be careful when using data-heavy markups. For example:
- Grouped Markups – If you are going to combine markups together, you should ideally minimize the number of individual items within each Group. It is best to avoid using this functionality unless it's necessary.
-
Snapshots – We recommend using the “leanest” Snapshots possible, which do not include background content or data from the original document. To do this, capture the part of the original page you want to add to your document, but before pasting it onto the destination file, you should first paste it into a new, blank PDF, and retake the snapshot from there. This second version of the Snapshot will be free from any unnecessary data.
-
Images & Videos – Whether you are using the Image tool or the Capture feature to add photographs or videos to a PDF in a Studio Session, it is important to remember that Studio transmits document and markup changes back and forth between the Session and each attendee. This being the case, it is important to consider that the large file size of high- resolution files may have an adverse effect on overall performance.
- Upload your drawings to a Studio Project first.
Storing large numbers of drawing sheets covering various disciplines in a Studio Project ensures your documents and folders remain organized and intact. When you decide to collaborate on any of those files in real time, add copies of selected Project files to a new or existing Studio Session. Once the Session attendees finish working on the drawings, use the Update Project Copy function to update the original version in the corresponding Studio Project.
This has the added benefit of building a Revision History for any drawing that your colleagues work on in the Session.
Working with Large Quantities of Markups
Session attendees simultaneously applying or editing large quantities of markups across multiple sheets could also impact performance. As the number of attendees in a Session increases, the amount of data transmitted between the Session and each attendee increases rapidly.
Document Preparation
Before uploading your drawings or documents to Bluebeam Studio, we strongly recommend taking care of the following tasks so that you will not have to remove, correct, and re-upload them:
- Prepare your Custom Markup Statuses ahead of time. Although Studio Sessions allows you to select different options in the Status column of the Markup List, you must create and apply all Custom Statuses to your drawings before uploading them.In Revu 21, only Core and Complete subscribers can created custom statuses.
- To ensure accurate calibrations and measurements, go to the Measurements Panel and delete all untitled or unwanted Viewports.
- All sheets and documents must be oriented correctly. You will not be able to change orientation after you upload them.Further information about rotating PDF documents can be found in this article as well as the Revu Help Guide.
Drawing Management for Studio Projects
Studio Projects is a document management system (DMS) for sharing information and files with collaborators while maintaining file integrity and with revision history that tracks activity and updates. For the best end-user experience, consider the following factors before uploading files to your Studio Project:
- Network Speed – While working with a large collection of documents or drawings, it is possible for a Project to contain upwards of 25 GB of data. Downloading and uploading this amount of data to and from the Session and each attendee requires the fastest and most stable internet connection possible.
- Using the Sets or Batch Processing – If the total file size or your PDFs is greater than 100 MB or has a page count of at least 250 pages, we strongly recommend running these CPU or time intensive functions before uploading them to the Studio Project.
Editing documents in Studio Projects requires extra time, bandwidth, and processing to support proper file access, document management, and version control. Additionally, new files which have yet to be cached locally require additional processing time during an initial upload and download.
How-To
Revu 21
Revu 20
Studio