Contents |
Projects are a way of organizing your content. When you are managing more than one display network, you can split your work into different units. Using projects is also an essential part of sharing the same content over several managers. Each project has its own settings. Using projects you may split up the work between several co-managers - edit the content on one and distribute on another.
There is always a default, local project on your manager. It has the DISEContent folder structure as its base, but you may of course add content located anywhere on your manager. However, we recommend you to keep as much content as possible in the DISEContent\Content folder, as it has these advantages:
To create a shared project, a content repository is required on the network.
Read more: Sharing content
Note: In Bridge, you don't need to care about where the project is locally stored.
The project is now downloaded locally to the workspace folder. You will notice if you look in the project folder that DISE has created a standalone DISEContent folder structure. You can see which project you are working with in the left bottom hand corner.
Note: In Bridge, you don't need to care about where the project is locally stored.
You can switch between projects by selecting a project in the dropdown-list File > Options > Current in Composer or Bridge. The available projects will be presented.
Name
Content directories
Encrypt project settings
Enable exclusive edit mode
Create backup of project files on application close
Check for updates on application startup
Calendar view offset (hours)
Delete
Halt on missing files
Note: Unchecking this may lead to unexpected behaviour.
Read more: Troubleshoot dependencies
Log to file
Max log level
Limit number of lines
Log to remote Syslog server
Read more: Syslog - wikipedia.org
Syslog server IP address
Syslog server port
Log to system debugger
In this tab, fill in the connection details to upload content to DISE Server.
Connect to DISE Server
Server address / port
Settings files for projects are saved in the "DISEContent\System\Projects" folder. The Default project can be found in "C:\DISEContent\System\Projects", and if you create a new local or shared project it will be found in its DISEContent structure (for example, "D:\MySharedContent\System\Projects"). Each file will have a unique ID, such as "0682E980-926E-440F-B858-531C51107DB2.diseproject". The default project is named "00000000-0000-0000-0000-000000000000.diseproject". The project itself is stored as a ".diseproject" file and a ".diseproject.local" file. The .diseproject.local file contains information that is specific for this manager. This is applicable when sharing content - some paths and settings will differ between managers. The project contains a list of destinations, which are themselves stored as separate files.
Destinations, the destinations database, and its playlists are also stored here, as ".destination", ".database" and ".playlist" files, respectively.
In the General tab in the Project properties, you may enter a new name in the Name field. You can also click the Browse icon to select a new location for the project files. Please note that this will only move the project files, not content files - they have to be moved manually. Similarly, deleting a project will not delete any content associated with the project. To delete the project, click the Delete button at the bottom in the Project properties.
Note: Moving a shared project will not automatically check out the content from the content server.
There is an option to backup project settings when Bridge is closed. Find it by selecting File > Project > Project properties, then in the General tab checking the box Create backup of project files on application close.
Main article: Troubleshooting projects