Stellar Glossary
Stellar is the user tool for authoring, editing, checking and viewing all types of timed text including subtitles, captions, Audio Description, voice over, and dubbing scripts and recording and transcripts.
Stellar runs on Nebula so you have to have a Nebula account and to be running a Nebula Device on your PC or Mac.
You need to have an active internet connection as the local Nebula Device must be in contact with the Nebula System. However none of your media files are ever stored on our servers, you are always in control of your own media.
Once you are up and running you will only need to access Nebula to view and update your account or possibly occasionally to edit some Stellar configurations. There is a full set of Nebula Help pages available should you need them.
NOTE: Projects in Nebula and Stella are not the same thing! See the Project Overview for more information on Stellar Projects and the Nebula help pages for information on Nebula Projects.
| Term | — | Description |
|---|---|---|
| Device | — | A Device is a mini software server that runs on each machine that is used to run any nebula Processes. Each device is unique and there is a different Device type for PC, Mac or Linux machines. Only one copy of a specific Device (ID Number) can run at the same time. Even on different computers. |
| Project | — | A Stellar project (different from a Nebula Project) is a collection of files and attributes that have been gathered together for a specific job. |
| — | A single Project file references media, subtitle, script and other metadata files into a single collection. | |
| Task | — | A Stellar Task is a Project that has been uploaded to a central Task Server and assigned to a User. |
| — | Tasks can be downloaded by any Stellar user who has been assigned the task. | |
| — | Tasks are stored centrally and all changes are updated automatically. | |
| Files | — | Files are all the parts that make up a Project and include video file, subtitle or script files, shot change and other data files and any associated audio files. |
| — | All files are stored on either your local drive or a specified location. | |
| — | Files may be copied automatically to a Task server if that is how your Stellar is configured. | |
| User | — | A Nebula User who has been added to the Task System. |
| Widget | — | A Stellar Widget is a sub component of the Stellar software and can be enables, disabled and configured to provide a specific function within Stellar. |
| — | Which Widgets are active and how they are configured is set by a Layout. | |
| Profile | — | A Stellar Profile is a set of style and QC Layers (containing Rules) that are applied to a specific subtitle or script file. This may be the number of characters per row, the maximum number of lines and the font style for a subtitle file, or the default fade levels for an Audio Description file. |
| — | Profiles are stored centrally per Company and can be accessed by any user with suitable privileges. | |
| — | There are a set of Read-Only System Profiles that users can use directly or copy to make custom versions. | |
| — | Profile settings can also be overridden on a specific Project or Task to allow for special cases. | |
| Layers | — | Layers define a set of Rules for how text files (Subtitles, Captions, Scripts or Transcripts) should be created. There are Layers for Reading Speed, Timing, Text Style, Editing restrictions, Audio Settings and QC tests. |
| — | Profiles are stored centrally per Company and can be accessed by any user with suitable privileges. | |
| — | Layers are only used as part of Profiles | |
| — | Layers are stored centrally per Company and can be accessed by any user with suitable privileges. | |
| — | There are a set of Read-Only System Layers that users can use directly or copy to make custom versions as Company Layers. | |
| Rules | — | Rules are the individual settings in Layers that control the style, timing and other settings for a text file (Subtitles, Captions, Scripts or Transcripts). |
| — | Rues are only set in Layers | |
| — | Within a Project individual Rules can be overridden just for the specific text file in a single Project. | |
| Settings or Properties | — | The Settings for Stellar are stored in a range of ways depending on the setting. |
| For example: | Rules are only set in Layers | |
| The microphone selected to record Audio Description audio is stored as part of the overall Stellar settings as this is specific to your computer | ||
| The position and size of the widgets on screen, and any of their settings, are stored as part of a Layout. This allows you to swap between different Layouts for different type of work. | ||
| Subtitle style settings, line length, positioning rules, are stored as part of a Profile that sets the rules for a specific file within a Project. | ||
| Hotkeys | — | Hotkeys are shortcut key combinations to access specific function. |
| For example: | Alt+ Up Arrow – Video pause and single step forward | |
| Hotkey Maps | — | Hotkey Maps control what Hotkeys are used for each function within Stellar. |
| — | There is a Default Stellar map – See the Hotkeys Help page | |
| — | Alternative Hotkey maps are provided to simulate other subtitling software products | |
| — | Users can create personal customized Hotkey Maps to set personal preferences. | |
| Import | — | Importing in Stellar is the action of bringing in files that are not in the \Stellar\ file system and making them available in Stellar. Importing may, optionally, include format conversion of video or text files. |
| Export | — | Exporting from Stellar is the action of taking a file in the \Stellar\ file system and saving a copy in an external location. Exporting may, optionally, include format conversion text files or zipping of audio and script file sets. |
| ASR | — | Automatic Speech Recognition. Another term for Speech to Text (STT). This is the process of using AI tools to transcribe the speech from audio to text. |
| Synthetic Voice | — | Another name for Text to Speech (TTS). This is the process of using AI services to turn text into spoken audio. |
Nebula Glossary
- Nebula is a system for automatically manipulating subtitle, audio description, dubbing and other media files located on any local or cloud storage. All Nebula functions are automatic and can run on a machine or server anywhere.
| Term | — | Description |
|---|---|---|
| Nebula Server | — | The Nebula Server is the central server that controls all Nebula and Stellar functions. All Process and Project configurations, all user logins and all metering and billing is done by the Nebula Server. |
| — | — | No media of other user files are stored on the nebula Server. |
| Device | — | A Device is a mini software server that runs on each machine that is used to run any nebula Processes. |
| — | — | Each device is unique and there is a different Device type for PC, Mac or Linux machines. |
| — | — | Only one copy of a specific Device (ID Number) can run at the same time. |
| Device Template | — | A Device Template is a stored configuration for a Device and for any Projects and Processes configured for that Device. Device Templates are used to simplify the deployment of new Devices. |
| Project | — | A Nebula Project (different from a Stellar Project) is a collection of Processes with their configurations and other parameters. A Project is assigned to a specific Device and can have cost codes an support levels assigned to it. |
| Project Template | — | A Project Template is a pre-configured set of Processes and settings that can be quickly reused. Project Templates are used to simplify the deployment of new resources. |
| Process | — | A Process is the key building block in Nebula. All functions provided in Nebula and Stellar are performed by Processes. Only the use of Processes is charged for. |
| User | — | A Nebula User has access to parts of the Nebula system to add, edit or remove Devices, Projects, Processes, Templates, Libraries and Users for the company they are a member of. How much access a user has depends on the access level assigned to them. |
| Company | — | A Company within Nebula has Users, an account and any number of Devices, Projects, Libraries and Processes assigned to it. Users belong to a Company and can only access components associated with that company. |
| Library | — | A Nebula Library is a pre-configured data storage location. Libraries can be local storage on a User’s machine, an area on a company’s server or a cloud storage location. Libraries are configured and used by Users and do not store any data on Yella servers. |