VALT 6.4.5 - Revision history

IVSWikiBlue at 15:00, 14 April 2025

2025-04-14T15:00:26Z

IVSWikiBlue at 14:17, 11 April 2025

2025-04-11T14:17:34Z

IVSWikiBlue: Created page with "April 11th, 2025 '''Application Fixes''' * Fixed issue where editing a Schedule after its first instance but on the same day of its next instance caused the Schedule to skip..."

2025-04-11T13:51:23Z

Created page with "April 11th, 2025 '''Application Fixes''' * Fixed issue where editing a Schedule after its first instance but on the same day of its next instance caused the Schedule to skip..."

New page

April 11th, 2025

'''Application Fixes'''
* Fixed issue where editing a Schedule after its first instance but on the same day of its next instance caused the Schedule to skip to the next instance
* Fixed issue where creating/editing a recurring Schedule using the "End at" field without specifying an "End at" date now shows a relevant error message
* Fixed issue where the CUE App started recordings authored by the user who created the track instead of the user who is beginning the track

← Older revision		Revision as of 15:00, 14 April 2025
Line 4:		Line 4:
	* Fixed issue where editing a Schedule after its first instance but on the same day of its next instance caused the Schedule to skip to the next instance		* Fixed issue where editing a Schedule after its first instance but on the same day of its next instance caused the Schedule to skip to the next instance
	* Fixed issue where creating/editing a recurring Schedule using the "End at" field without specifying an "End at" date now shows a relevant error message		* Fixed issue where creating/editing a recurring Schedule using the "End at" field without specifying an "End at" date now shows a relevant error message
		+
		+	'''Technical Feature'''
		+	* VALT is now compatible to handle CUE recordings being authored by users who begin the track instead of the user who created the track

← Older revision		Revision as of 14:17, 11 April 2025
Line 4:		Line 4:
	* Fixed issue where editing a Schedule after its first instance but on the same day of its next instance caused the Schedule to skip to the next instance		* Fixed issue where editing a Schedule after its first instance but on the same day of its next instance caused the Schedule to skip to the next instance
	* Fixed issue where creating/editing a recurring Schedule using the "End at" field without specifying an "End at" date now shows a relevant error message		* Fixed issue where creating/editing a recurring Schedule using the "End at" field without specifying an "End at" date now shows a relevant error message
−	* Fixed issue where the CUE App started recordings authored by the user who created the track instead of the user who is beginning the track