The main settings of the project. Its sub-page is Additional parameters.
Disc type - the type of the output medium: Blu-ray or Ultra HD (4K). Ultra HD is available in the UHD version only. For Ultra HD you also have to select the media encoding parameters from the list next to it: Group (HTR/DTR/LTR), Disc size (50/66/100 GB), Data rate from the drive, Maximum TS recording rate. HTR means High Transfer Rate, DTR Default Transfer Rate and LTR Low Transfer Rate. Choose the value that matches your encoding bitrate. An Ultra HD disc uses BD-J profile 6, so the BD-J profile version is shown as "6" and the disc profile version is always "same as BD-J profile". The HDR settings are available only for Ultra HD.
3D project (available only for Blu-ray) - makes this a 3D project. Described here. The 3D settings are on the Additional parameters page.
Project type - lets you choose one of the four project types:
- Standard - the original default mode, in which you can use one or several JARs. Some features only work in this mode, and it is the only mode available without JAR signing. In this mode, pressing the Top Menu button on the remote control reloads the JAR.
- Quick Top menu - unbinds the JAR from the main title, which prevents the JAR from being reloaded when the Top Menu button is pressed. Only one JAR is available.
- Two Titles - uses the "Quick Top menu" approach, but lets you switch between the Top Menu title and the Main JAR title with the "Select JAR title" → "Select Menu title" / "Select Movie title" actions. In this mode you can run the main menu in the Top Menu title (where calling the Top Menu is prohibited) and switch to the Main JAR title when the movie starts. Only one JAR is available.
- Three Titles - the same as "Two Titles", but the Top Menu button can be used in the Menu title. In this mode the Menu title is not the same as the Top Menu title.
To make sure no required action is missing, there is the setting Add missed "Select ... title" ....
The basic idea of the Two Titles mode is:
- the Top Menu button is disabled in the Top Menu title and allowed in the Main JAR title;
- use "Select Menu title" before going to the main menu;
- use "Select Movie title" before going to the movie;
- choose the title the disc starts from with "Start disc from" in the JARs window (this is usually the Top Menu title).
If you do not use an animation, we recommend using the Hide menu animation, at least in the Two Titles/Three Titles modes. The way the title is switched in these modes is set on the Advanced page.
Default language code - the language code used by default in the current project. The "..." button opens the list of languages.
BD-J profile version - the version of the BD-J profile. The BD-J profile limits the size of the menu graphics, i.e. the width times the height of the resulting image (the combination of all project images if you use "Mosaic" = "In a single image"). It must not exceed 5.9 million pixels for version 1 or 8.0 million pixels for version 2. Old players may not support the second profile. If you get an "Image buffer overflow" error, you have to reduce the amount of graphics used (see here) or change the method used to combine the images (see below).
Disc profile version - lets you specify the BD-J profile of the disc title. This option controls whether a disc that uses BD-J profile 2 can be started on players that only support profile 1 or 1.1. In theory it should match the BD-J profile, but in practice this is not required, and we recommend setting "force version 1".
Sign JAR(s) (on by default) - enables JAR signing during compilation. A signed JAR lets you store data in the storage, use text (fonts) and switch titles. You have to specify the correct application ID and the corresponding signature settings. Without JAR signing the project type is always Standard, and the other settings that need a signed JAR (application ID, signature settings, placing the mosaic outside the JAR, disc settings and the storage file name) are disabled.
Signature settings - opens the signature settings window.
Application ID - the ID of the signed JAR: four hexadecimal digits between 4000 and 7ffd.
Mosaic - defines how the images are combined (the graphic mosaic):
- In a single image - combines all images into one image. It must not exceed 5.9 megapixels for profile 1 or 8.0 megapixels for profile 2.
- Split into separate files - splits the graphics into separate files so that the limit per file is not exceeded. In this mode all images and graphic objects together must not exceed 11.8 megapixels for profile 1 or 16 megapixels for profile 2. The number of graphic objects cannot be predicted, so we recommend not exceeding 8.8 megapixels for profile 1 and 12 megapixels for profile 2. Note also that the images are not packed perfectly: if all the images fit into 7 megapixels in one file, they may take more than 9 megapixels in "separate files" mode. The size of each file is limited by the memory limit on the Engine page.
- Dynamic load (not safe) - loads the graphics dynamically. This mode needs additional memory to load the graphics before you jump to another menu or play an animation. You therefore have to adjust the script (Java) accordingly if you use one in the project (note that the scripts generated with and without "Dynamic load" are different). For this reason, do not use this mode unless you really need it.
Place mosaic outside JAR (on by default) - stores the resulting graphic mosaic outside the JAR, next to it in the JAR folder of the disc (recommended). Without JAR signing the mosaic is always placed inside the JAR.
Disc settings - defines how data is stored in and restored from the storage.
- Do not store (the default) - do not store or restore any data.
- Restore by command - restores resume time for movies/playlists, selected audio/subtitle tracks, and the disc resume point from the internal storage on the "Resume disc" or "Restore data from storage" actions.
- Restore on disc load - restores the data above when a disc is loaded, without any additional commands.
The "Resume disc" and "Restore data from storage" actions are only offered if this is not set to "Do not store". User-defined parameters and GPRs can be saved in the storage as well, see Parameters & Functions. Bookmarks are kept in files of their own and need only JAR signing.
Storage file name - the name of the file used to save the data in the storage (def: BDS.properties). More details can be found here.
The folder the built-in muxer and tsMuxeR multiplex the project into. If it is empty, the Output subfolder of the project folder is used. Two variables can be used here: %volume% is the volume label from Scenarist → "Volume label", and %project% is the source project folder.
Add project folder name - adds the name of the project folder to the output path (together with the two other options it forms a subfolder name).
Add project file name - adds the name of the project file to the output path (together with the two other options it forms a subfolder name).
Add current date/time - adds the current date and time to the output path (together with the two other options it forms a subfolder name).
If any of these three options is on, the project is muxed into a subfolder of the output folder (or of the project folder, if the output folder is empty) named folder_file_yyyy-mm-dd_hhnnss, with only the enabled parts. With the date/time, every mux creates a new folder, and Build CMF image and the ISO image creation start from the folder of the last mux.
Warn if output folder is not empty - before a full mux with the built-in muxer or tsMuxeR, asks whether to continue if the output folder already contains files. A partial mux does not ask.