Release Notes
2025.7.2
Release date 17 July 2025
Added
- Added support of MPEG2 AAC LC audio profile
Fixed
- More accurate DVB susbtitles rendering
2025.7.1
Release date 03 July 2025
Added
- Users can subscribe to release notes and announcements on Account page
2025.6.2
Release date 23 June 2025
Added
- Qualify 2025.4.1.1. Minor fix for Qualify’s dolby_atmos_loudness test.
- DAMF packages (.atmos files) are now supported as QC sources.
Fixed
- Handling webvtt with short timestamps.
2025.6.1
Release date 05 June 2025
Added
- New Qualify version 2025.4.1
Fixed
- Improved handling some specific Dolby E audio inputs
- SCC to WebVTT conversion missing character before Background Attribute Code with Backspace
2025.5.2
Release date 22 May 2025
Added
- Display remaining plan commitment in usage statistics in UI
Fixed
- Embedding VTT file as CEA 608/708 closed captions
- Incorrect formatting of teletext subtitles from STL source (styling issues)
2025.5.1
Release date 08 May 2025
Fixed
- Minor UI issues
2025.4.2
Release date 24 April 2025
Added
- New option to strip certain cue settings for WebVTT subtitles
- Display user status on account page in UI
Fixed
- Minor UI fixes
Check the latest API changes here.
2025.4.1
Release date 10 April 2025
Changed
- Improved SCC-to-VTT conversion error messages provide better clarity
- Improved CPIX error messages provide better clarity
Fixed
- Issue with STL subtitle source with 00:00:00:00 item and no add_source_offset
2025.3.2.1
Release date 02 April 2025
Added
- Retries for determining the source file size.
Check the latest API changes here.
2025.3.2
Release date 27 March 2025
Added
- A new API parameter ensures that the initial PTS delay is not added to MPEG-TS
Changed
- Improved accuracy for job progress reporting
Fixed
- Wrong behavior in case of using set_video_duration along with clipping parameters
Check the latest API changes here.
2025.3.1
Release date 13 March 2025
Versioning Convention Update
To provide clarity and transparency in our updates, starting this release Vantage Gateway will follow a structured versioning format:
YYYY.M.Version.Hotfix
- YYYY = Year of release (e.g., 2025)
- M = Month of release (e.g., 3 for March)
- Version = Main release number within the month
- Hotfix (optional) = A minor fix or patch for urgent issues
Examples:
- 2025.3.1 → First main release in March 2025
- 2025.3.2 → Second main release in March 2025
- 2025.3.2.1 → A hotfix for version 2025.3.2
This versioning system ensures clear tracking of major updates while allowing for rapid fixes when needed.
Release Changes
Added
- Formatting support for burned-in STL subtitles
Changed
- Minor UI improvements
Fixed
- Incorrect timecode handling for external STL
- Dolby Atmos transcoding in case of non-ABR outputs
- Subtitle conversion issues for mp4-ttml and ismt formats
8.34
Release date 27 February 2025
Added
- Improved HTML entity conversion in WebVTT subtitle input
Changed
- cea-608 captions mapping in case of specifying more that 2 subtitle sources
Fixed
- Failure with low-bitrate AAC audio output
- Closed captions from source are cut correctly with start/finish options
- Prevent encoding fail in case of using set_video_duration and audio_codec copy
- Minor UI issues
Check the latest API changes here.
8.33
Release date 23 January 2025
Added
- Fallback to retrieve the AWS S3 bucket’s region from the HTTP header
- A new API parameter to change the timecode track mode.
- Added qualify version to About page
- Default Qualify templates
- New API call ListDefaultQualifyTemplates to list pre-populated Qualify templates.
- New Qualify version 2025.1.1
- Ability to set AAC SBR/PS signaling for fMP4 intermediate repackage outputs
- Support for CEA-608/708 track in apple_prores output
- UI Usage report pages updated to support per-minute resources
Fixed
- Copy of the DNxHD video codec to the MXF OP1a format
- IPCM audio decode
- Packing of DV intermediate files into MP4 when Ludicrous Mode was used
- Unexpected job failures with error like: [Download S3] Process follower: master process hung or died: status files are not updated for too long
Check the latest API changes here.