The session browser has undergone a significant update, this document outlines the improvements and how to use them.
Data Sources
Data sources allow you to aggregate multiple SQLRace and Folder locations. All session types will then be displayed in the session pane.
The “Sources” section at the top left hand side allows users to add many
- Folders containing saved session files
- SQL Race databases
When you add a file location you have the option to recursively look through all the folders.
Once a file location is added, an indexer will work in the background and store a reference to the file along with its session data in a database. This information can then be used to filter the sessions.
Please note, at the moment, if you move the files once indexed, the previous data will remain and cannot be easily removed.
Filters
The “Filters” section is automatically populated based on the selected sources. The default filter categories are ‘Circuit’, ‘Driver’, ‘Run Type’ and ‘Year’ but users can select any other session property as their filter category. The list of filter categories can be accessed by right-clicking on the “Filters”. A filter selection can be saved using the “Save” button, which then appears under the “Favourites” section.
Loading Sessions into Sets
Sessions can be loaded into a Set by one of the following operations:
- Double click a single session
- Select and drag single or multiple sessions (ctrl pressed while dragging)
Recorders
The “Recorders” section at the bottom left hand side allows users to setup different types of recorders.
Double click a recorder to edit its details once created. When you edit a recorder, its new information is automatically saved.
Recorder behaviours
When a recorder is dragged into a layer (composite session), it creates a ‘recording behaviour’ – this is a definition of how the recorder interacts with that composite session and is layer specific. It is possible to associate the same recorder with multiple layers, each with different behaviours.
Note: When you start a recording, it is not automatically added to a set and your session is not automatically loaded. The user must either:
- Add the live session to a set/layer from the sessions list – this will only load the current live session, and not trigger from any future recording
- Drag a recorder to the layer to create a recorder behaviour – this will bring the live session with it if the recorder is active.
When a recorder is recording without being attached to a set(s) then it will still record to its destination.
After a recorder is added to the Set, one can define its behaviour: Create, Replace or Append.
Create: Every new recording creates a new session; previously recorded session remains in the Set as a historic session.
Replace: Every new recording replaces the previously recorded session.
Append: As the recorders now can be dropped onto an existing historic session, every new recording will be appended to the existing sessions in that slot.
Comments
0 comments
Please sign in to leave a comment.