VidiControl Release Notes [VCon RN]
There is now a new tab “Metadata” available in the Booking Dialogue for Booking Components. The metadata set is configurable. For more information, please see Operations Guide [VCon OG] .
All data is stored in VidiCore. When creating new items, the data is sent via VidiControl Backend, when editing, the dialogue communicates directly with VidiCore.
Titles are synced from VidiCore with them being stored in VidiCore’s title metadata field. For faster loading and for failover situations, the title is also cached in VidiControl’s backend. VidiCore titles always overwrite VidiControl’s title. This causes some limitations (see below).
Modal Booking Dialogue
There is a new user setting. The user can decide if he wants the booking dialogue opening in a new tab (for multi display workstations) or in the same tab.
When a VidiCore item is created by VidiControl, it will get a Deletion Lock. This prevents the item from being deleted by VidiCore’s housekeeping. The default holdback time for this lock is recording-end + 48 hours. This value can be adjusted with the configuration value VidiCoreChunkItemLockIntervalHours.
When recordings are updated, the VidiCore deletion lock will be updated as well.
When deleting a recording from VidiControl’s timeline or by using the BookingService API, the recording is deleted in VidiControl’s backend. The deletion lock is removed from VidiCore’s item.
The user is able to cancel a running recording. Cancelling it would result in an immediate stop of the record followed by a delete operation of the recorded asset. A confirmation dialogue warnes the user about the risk of that operation.
Auto Resource Detection
The system is capable of requesting router and recorder ports on initialization. Labels are stored and displayed in the GUI. They can be overridden by custom labels that are configurable in the backend’s database.
In the context menu of a planned item, a new command “Start Now” is now available. It moves the planned recording so, that it starts immediately. See Modify a Booking Component on the Timeline [VCon UG] | Starting-a-Recording-Now.
Lane Header Context Menu
The lane headers now have a context menu to schedule new Bookings or to Crash Record. See Area: Timeline [VCon UG] | Context-Menu:-For-individual-lanes.
Group Header Context Menu
The group headers now have a context menu to sort the items in the group. See Area: Timeline [VCon UG] | Context-Menu:-For-source-groups.
Mouse Zoom & Scroll:
Holding the “Alt” and “Shift” keys while using the mouse wheel can be used to improve timeline navigation. See Area: Timeline [VCon UG] | When-Navigating-the-Timeline.
Clicking on a message title jumps to the corresponding item. See Area: Notifications & Messages [VCon UG] | Using-a-Message-to-Jump-to-a-Recording.
Clicking on an timeline item filters the messages in the message dialogue, so that only messages belonging to the selected item are displayed. See Area: Notifications & Messages [VCon UG] | Using-a-Booking-Component-to-View-Messages.
Finding related Booking Components
When clicking on an item on the timeline while holding the “Alt” key highlights all Booking Components belonging to the same Booking. See Area: Timeline [VCon UG] | Identifying-Booking-Components-Related-to-a-Booking.
The item state is now displayed in different colors. The state is also shown in the Booking Quick Info Dialogue. See Area: Timeline [VCon UG] | When-Viewing-Booking-Components-on-the-Timeline.
The user can drag the timeline at any empty space and drag it in any direction to navigate on the timeline.
Open Booking Details Window (Booking Dialogue)
Due to browser conflicts, the keyboard shortcut for opening the booking dialogue was changed from Ctrl+E to Ctrl+B. In addition, the booking dialog can now also be opened by double-clicking on a timeline item.
Item highlighting has been improved.
Display Current User
The current user is now displayed in the settings dialogue.
Reset Button Functionality Update
The reset button now re-calculates the timeline display to fix a problem where timeline tracks were taking up too much height.
Zoom Handles too hard to grab
Wrong Date/Time in Message Window
Error Icon fixed
Error when updating Booking Components
Specification should not be editable when state is Done
Booking Dialogue: End Date Calculation
Item status does not affect items color
Click on timeline item leads to item move
Booking Dialogue: Booking Component in past
Inports are not set
Booking State Indicator missing
Wrong mapping on RouterOut lanes
Shorten running recordings
Outport entry in chunk table is wrong
VidiCore item id gets deleted sometimes
Preparation status does not switch to running
ThirdPartyRetryCtrl still use appsettings.json for some settings instead of config table
MaxRecordingChunkLength does not work
Add dispose for queue consumer/produced
Timeline view is showing chunk start/end instead of recordingcommand
AutoUpdate of Bookings doesn't read commands
Labels are not consistent
Status is not updated
BookingAPI: Update running recording failes
Wrong UseCaseDefinitionId in Frontend
Performance problems in GetMessages endpoint of ProxyApi
Fix Auth Service
ThirdPartyService: Persisting of failed jobs (for retry) does not contain metadata
"In Preparation" state colour in quick booking info window
Remove source and destination from command
Frontend - Edit Booking Link does not opens up
Auto Token refresh of token does not work
Metadata Tab: Enum list value do not change color when mousepointer over it
Update - Compute End time when duration of recorder is changed
Update - Router duration should not change when booking is in progress status
Update - Recorder execution time is more than end date time
Update - start date and router execution should auto modify once executiontime for recorder is changed - pending status
Update - Pool and Device Id does not match then should not allow to update booking
Update - Modification time does not update in database if update action taken during pending state
User should not be able to create booking with negative durations on the commands
SideEffects fix in config app
Pool Utilization - Color fix and tooltips
Update - InportId of recorder should not update
Context menu styling not applied in production
Update - If router duration changed then execution time should auto update
Fix Overlapping Bookings
Update - recorder execution time should not change during in progress status
Booking Dialogue Start Date Picker
Align datetimepicker style
Fix broken styling in booking dialogue
Invalid handling of "InPreparation" items
Labels are not consistent
Language toggle broken
2 seconds off: Adapt API
Update Chunk with blocking Device + pool
Third-Party-Control Gregorian Calendar Problem
Healthcheck at ChunkUpdate - DateTime Rounding Error
ThirdPartyCtrl - Delete does not work
chunk-delete-msg chunkid ignored by notification handler
Update Chunk returns wrong chunk
Floating Message windows on the right hand hide the config menu
Booking dialogue: table cell backgrounds and border mismatch
CSS rule for popup in incorrect group
Frontend: Timeline item shortening removes item on other lane
If duration from from switch command is null then should be get the duration from capabilities and write it to command
Booking Quick Info Window edit button strange scaling
Extend running chunks does not work
RecorderMock - Multithread Problem
Drag and Drop pending recording on timeline jumps back
Missing title for newly created booking components
Booking Dialogue: Metadata does not load in modal dialogue
Metadata Dialogue: Columns are not displayed
Fix function debounce
Booking Dialogue: Switching between tabs effects timeline tabs
Missing translations in actions snackbars
Select Specification tab initially
Booking Dialogue: Timeline tab changed after close
Redirect to vidicontrol/ to vidicontrol with https
Slash in URI
No Device available error
Scheduler doesn't fill up the pool completely
Opening both popup menus doesn't close the one that opened first
Not possible to extend/shorten crash record booking via booking dialogue
Timeline: utilization hidden for last collapsed pool group
Messages: It should also be possible to delete Messages for all recording states
Fix React state update during render
Crash Record parallel access to chunk causes problems randomly
Maxrecordinglength should only refer to recording commands
Messages are not shown for recordings which are located in the past
State is missing in /PUT/ComponentDescription Endpoint response
Booking Dialogue: Device changed saved successfully but data is reset
Booking Dialogue: Destination missing in table
OutportId is null of ComponentDescription
Messages and Statusupdates are not processed in Production mode
Minimum required Vidi* version is 22.4
Only item metadata is synched right now. There is no handling or inheritance of collection metadata to item metadata on creation.
VidiControl caches the title for failover and faster access. VidiCore title metadata will always overwrite VidiControl's cached title. To change the title of a recording, you have to update VidiCore’s title metadata. There are several ways to do this:
Use VidiCore’s API directly.
Change the title in VidiCore’s metadata for the item. Then the new title will be synched to VidiControl and updated there. If there is a problem while saving metadata to VidiCore or if the sync fails, the new title will not be displayed or it will be displayed after saving/syncing was successful.
Use VidiControl’s BookingService API. (Recommended)
Change the title in the chunks metadata field. Also set the chunks title field. Take care that both values are identical. So, the title change is synced to (and from VidiCore) but the title is also updated in VidiControls cache and can immediately be displayed.
Except for the title, no other metadata field will ever be cached by VidiControl.
Although the user/rights/roles concept is already implemented in the frontend, there are still unfinished parts in the backend. Therefore, the admin user must still be used for this release.
In concurring editing scenarios the last save operation wins.
If an item has to appear in MediaPortal, a workflow has to set the MediaType at the item.
When the user modifies a pool booking (dragging on the timeline, extending, shortening, etc.), the booking may "jump" to another device in the pool. This is caused by the scheduler applying its device selection strategy to the updated booking. This is not a bug, but an intended behavior.