Repository navigation
v1.1.5
Version - [1.1.5]
Synchronises the SDK with the current fastpix-openai.yaml. The four new
In-video AI operations (/ai/{mediaId}/advanced-summary,
/ai/{mediaId}/attributed-transcript) are not included in this entry.
Breaking
Models.Components.GetMediaResponserenamed to
Models.Components.GetMediaDetailResponse, following the schema rename on
GET /on-demand/{mediaId}. Its generated companion types were renamed to
match:GetMediaResponseMaxResolution,…MediaQuality,…Mp4Support,
…SourceResolution,…Statusand…Trackare now
GetMediaDetailResponse*. The HTTP wrapperModels.Requests.GetMediaResponse
is unchanged.UpdateTrackRequest.Urlremoved. The API does not allow a track's file to
be changed — only its language and title. Callers settingUrlmust drop it.UpdateMediaMaxResolution.ThreeHundredAndSixtyp(360p) removed, matching
theUpdate-Media.maxResolutionenum. No othermaxResolutionenum offered
360p, and no request enum accepts it, so the API cannot return it.Mp4Supporton media responses is now a list, not a scalar enum. The
schema has long declaredmp4Supportas an array of rendition objects, but
the SDK modelled it as a single string enum, so any response with MP4
renditions present failed to deserialize. OnMedia,GetAllMediaResponse,
GetMediaDetailResponse,LiveMediaClips,SourceAccessMediaand
UpdateMediathe property is nowList<Mp4SupportEntry>?, and the six
per-model enums (MediaMp4Support,GetAllMediaResponseMp4Support,
GetMediaDetailResponseMp4Support,LiveMediaClipsMp4Support,
SourceAccessMediaMp4Support,UpdateMediaMp4Support) were removed.
Read the requested setting from the request models —CreateMediaRequestMp4Support,
DirectUploadVideoMediaMp4SupportandUpdatedMp4SupportMp4Supportare
unchanged and remain string enums.
Added
Titleon ten track models:AddTrackRequest,AddTrackResponse,
UpdateTrackRequest,UpdateTrackResponse,GenerateTrackResponse,
TrackSubtitlesGenerateRequest,AudioTrack,SubtitleTrack,VideoTrack
andVideoTrackForGetAll.OptimizeAudio(bool?) onMedia,GetAllMediaResponse,
LiveMediaClips,SourceAccessMedia,GetMediaDetailResponseand
UpdateMedia.Mp4SupportEntrycomponent, describing one downloadable MP4 rendition
(Type,Status,Height,Width,Ext), together with the
Mp4SupportType(capped_4k,audioOnly),Mp4SupportStatus(preparing,
ready,failed) andMp4SupportExt(mp4,m4a) enums.360pand360added to thesourceResolutionenums for
GetAllMediaResponse,GetMediaDetailResponse,LiveMediaClips,Mediaand
SourceAccessMedia.UpdateMediaSourceResolutionalready carried both.
Fixed
- Documentation links updated for the FastPix docs reorganisation — webhook
events now under/docs/webhooks/, track and playback guides under
/docs/video-on-demand/, AI guides under/docs/in-video-ai/, live-stream
guides under/docs/live-streaming/, analytics guides under
/docs/video-data/, and/docs/error-codes→/docs/error-codes/error-codes.
Live-stream "Manage streams" links now carry their per-operation anchors. - Webhook event renamed in prose:
video.media.subtitle.generated.ready→
video.media.subtitle.generated. - The
GET /on-demand/{mediaId}andPATCH /on-demand/{mediaId}/update-mp4Support
response examples now showmp4Supportas the array of rendition objects the
schema declares, rather than the scalar"capped_4k".
Compatibility
maxDuration.minimummoved from0to60on the live-stream response
models. The SDK does not emit range validation, so there is no code change.