Karafun Studio 1.10 serial key or number

Packager¶

• Support for CPIX, fully aligned with Origin.
• Create DASH and HLS streams with PlayReady, Widevine and FairPlay protection from a shared set of encrypted CMAF files (CPIX only, see: Multi-DRM protected HLS and DASH from a shared CMAF source).
• Extract CEA embedded captions from a video track and store as TTML or WebVTT.

Origin¶

• Support for cromwellpsi.comt_template to override default logic that defines which 'SegmentTemplate' format is used.
• Support for ingest of Tiled Thumbnails track to add it to its DASH output.

Remix¶

• Support for S3 authorization through command-line options.
• Support for audio silence for AC3, EC3 and DTS.

Packager and Origin¶

• Support for SCTE 35 command to signal splice events.
• Support for DTS:X.

DASH¶

• For all DASH output, calculation of is now compliant with the DASH-IF implementation guidelines.

Origin¶

• cromwellpsi.com doest not start at the Live edge in low latency mode: cromwellpsi.com GitHub issue

• PlayReady protected DASH output for which Origin automatically generates the is incompatible with LG WebOS and devices, because they cannot parse XML that defines a namespace in local scope. To workaround this issue, you can use Apache's with something like the following configuration:

  Substitute"s/xmlns:cenc=\"urn:mpeg:cenc\"/xmlns:cenc=\"urn:mpeg:cenc\" xmlns:mspr=\"urn:microsoft:playready\"/nf"Substitute"s/pssh/cenc:pssh/nf"Substitute"s/IsEncrypted/mspr:IsEncrypted/nf"Substitute"s/IV_Size/mspr:IV_Size/nf"Substitute"s/kid/mspr:kid/nf"Substitute"s/<pro/<mspr:pro/nf"Substitute"s|</pro|</mspr:pro|nf"Substitute"s/xmlns=\"urn:mpeg:cenc\"/xmlns:cenc=\"urn:mpeg:cenc\"/nf"Substitute"s/xmlns=\"urn:microsoft:playready\"/xmlns:mspr=\"urn:microsoft:playready\"/nf"

Capture¶

• Without the option, significant audio or video gaps might occur on clip boundaries, because Capture clips each track on the nearest sync-sample and does not take into account where the position of sync-samples on the video tracks when clipping audio tracks (which is a problem because each audio frame is a sync-sample, whereas this is not true for video and Capture may need to scan further to the left until it finds the start of a GOP).

Packager¶

• # The newly added feature that allows you to create DASH and HLS streams with PlayReady, Widevine and FairPlay protection from a shared set of encrypted CMAF files only works with CPIX, not with the DRM-related command-line options (in the latter case Packager will disregard the Widevine and PlayReady signaling when adding FairPlay).

CPIX¶

• # The implementation of is not fully aligned with version of the CPIX specification. For the optional attribute, as a value is not supported. To get the same behavior, use as a value instead, as defined in version of the CPIX specification.

Fixed¶

• npvr: fixed capture bug when clipping subtitles (#)
  • This fixes a bug that was introduced after GA. The bug caused Capture to add a wrong edit list when capturing a clip for a time range in which the subtitles start significantly later than the video. It mainly impacted Remix nPVR workflows, as the wrong edit list caused Unified Remix to trip up when the captured clip was used as a source to generate a stream from.
  • Impact: none other than as described.

• live: fixed silent failure to create pubpoint database (#)
  • When Origin ingests a new livestream on a publishing points, it creates a SQLite database, amongst others. Previously, when creating this database would fail, Origin would still report successful ingest (by writing to the access logs). This has been fixed and Origin will now return a i error in such cases.
  • Impact: none other than as described.

• live: fixed overflow error in header (#)
  • The header was introduced in the previous release, This fixes an overflow error that caused the header to be populated with the wrong value.
  • Impact: none other than as described.

• dash: remove media segments with zero duration from the SegmentTimeline (#).
  • Since , Origin adds a 'EXT-X-GAP' tag to Media Playlists, alongside empty media segments that should not be loaded by the client. In some cases, this logic impacted Origin's DASH and Smooth output as well, and segments with a zero duration were added to the media timelines for these formats. This has now been fixed.
  • Impact: none other than as described.

Added¶

• packager: added rebuilding of avc1/avc3 and hvc1/hev1 decoder configuration records (e.g. when converting in-band to out-of-band).
  • When repackaging an MP4 in which the out-of-band SPS/PPS headers change throughout the content (which is against the specification), Packager now maintains these changes and properly rebuilds a single out-of-band SPS/PPS header for the repackaged output.
  • Impact: none other than as described.

• live: added header to segments to signal expected (automatic) archive eviction resulting from (#).
  • The header applies to Live streaming scenarios only. It is added to media segments and it signals when a media segment will no longer be available.
  • Documentation: Sunset.
  • Impact: none other than as described.

Fixed¶

• dash: no longer write empty @value attribute for properties and descriptors.
  • Instead of writing an attribute with no actual value, the attribute is now omitted when there is no value to report for a particular property or descriptor in a DASH MPD.
  • Impact: none other than as described.

• libfmp4: fixed " Error writing to bitstream. parsing aborted" for large AVC Decoder Configuration records.
  • In a live streaming scenario, when the encoder posted an init segment with a very large AVC Decoder Configuration record, Origin would report an error and not be able to ingest the stream. This has now been fixed.
  • Impact: none other than as described.

• live: aligned the behavior of http expires / max-age headers for media segments between and (#).
  • Origin used to include and headers for media segments when was set. In that scenario, Origin would set the time of expiry for the segments to the moment at which they would be purged from the archive. Origin did not add such headers to media segments when was set. To ensure consistency, Origin will no longer add these headers when is set either.
  • Impact: if you have configured for your Live streaming setup and rely on the presence of caching headers for media segments, your cache might be affected by this change. However, note that the same type of information is communicated in the header that is added in (see: Sunset).

Added¶

• packager: extract TTML and WebVTT from mp4 (c, stpp, wvtt, dfxp) (#).

• cpix: renamed ContentKey's attribute to , which is the name chosen by DASH-IF (#).

• This update aligns the functionality that was added in with the CPIX specification. The attribute for the element can be used to override the default CENC encryption scheme that Origin uses for its fMP4 HLS ('cbcs') and DASH ('cenc') output. It will leave all other output formats of Origin unaffected (i.e., for these output formats Origin will use its default logic).
• Documentation: CPIX Document Requirements
• Impact: none other than as described.

• packager, origin, remix: use the shortest time interval that overlaps all available media segments to determine the offset and duration of an MPD, following DASH-IF guidelines (#).
  • In prior versions an MPD's was calculated as the difference between the earliest start time and latest end time of all media timelines (taking audio, video and subtitles into consideration). This caused problems when either audio or video started later or ended earlier, as that would result in a gap at the start or end of that media's timeline, compared to the . This is a common scenario when using Virtual subclips or when using Capturing VOD without frame accuracy, if your audio and video segments are not perfectly aligned (which is often the case). The newly implemented behavior no longer takes the subtitles timeline into consideration and calculates the as the difference between the latest start time and earliest end time of the audio and video timelines. This aligns with the requirement specified in DASH-IF implementation guidelines - Necessary segment references in static presentations
  • Impact: Although the newly implemented behavior is according to spec and we have tested it to solve several issues, you may still experience unexpected behavior because of it, as it might be that the player you use does not follow the spec on this point. Case in point is cromwellpsi.com, for which a fix to align it with spec was implemented only recently: cromwellpsi.com GitHub issue Therefore, it is highly recommended to thoroughly test the behavior of the player that you use in your setup, in relation to this change.

Fixed¶

• live: fixed intermittently disappearing and headers for client manifests (#).
  • This fix partially reverts behavior that was introduced in and present in the previous GA. Whereas Origin used to expire content that it expected to be updated (e.g., an MPD or HLS Media Playlist) at least 1 second from when the request was made (i.e., it counted the content's down to 1 and then let it stay at 1 until there was an actual update to the content), the behavior in the previous GA tried to be more 'truthful'. It counted the content's down to 1 and then did not add any expiry information to the content until the content was actually updated and a new expiration could be set. Unfortunately, the intermittently disappearing headers introduced confusion. Therefore, Origin will again expire content that it expects to be updated at least 1 second from when a request was made. As updating content is only relevant within a Live streaming context, this change does not affect VOD scenarios (for which Origin does not add cache headers at all).
  • Documentation: Expires and Cache-Control: max-age="".
  • Impact: if you update from a version prior to the previous GA, please be aware that the previous GA also introduced other, more significant changes to the cache related headers that Origin adds in Live streaming scenarios. However, when you update from the previous GA the impact of this fix should be more reliable caching behavior, although this naturally depends on the exact configuration of your caches.

• live: closing an archive segment always writes an "mfra" box and a "tfra" box for each track (#).
  • When streaming Live, Origin writes a Live archive to disk in archive segments of a user defined length. When the archive segment that Origin is writing to reaches the defined length, Origin closes the archive segment and starts writing to a new one. Prior to this change, when closing an archive segment, Origin would not write a "mfra" and "trfa" box to tracks that did not contain any content for the duration of the archive segment. This is a likely scenario for Timed Metadata tracks, which may not be updated for longer stretches of time. Although it wasn't the cause of any issues, the behavior was changed because the result did not align with how we expect a valid MP4 to be structured.
  • Impact: none other than as described.

• origin, remix, transcode: make web server module RPM packages depend on a specific version of mp4split, to avoid mismatches (#).
  • When installing our software on RPM-based Linux distributions, a version mismatch between our different packages might occur (e.g., when upgrading or installing a previous version). This was caused by the fact that for dependencies on our own packages no explicit version was specified. This has now been fixed.
  • Impact: none other than as described.

• libfmp4: fixed channelcount in for DTS:X (#).
  • Fixes a small mistake in the implementation of support for the DTS:X codec, that caused the channel count to not be correctly signaled in the box of the MP4.
  • Impact: none other than as described.

• remix: fixed support for large gaps between subtitles (#).
  • When remixing clips, Remix will fill significant gaps on the timeline of a subtitles tracks to mitigate playback issues. It used to fill such gaps with a single empty cue. In edge cases where the gap on the timeline was a little over 20 minutes and the content used a high enough timescale, this caused problems. This issue has now been fixed by using multiple cues to fill larger gaps.
  • Impact: none other than as described.

• live: ignore Timed Metadata tracks when determining live edge (#).
  • In edge cases where Origin was configured to use a DVR window that wasn't much bigger than the break duration announced in the Timed Metadata track of a stream, Origin could sometimes return an empty MPD. This was caused by the fact that the timeline of the Timed Metadata track was taken into account when calculating the live edge of the stream. This has now been fixed by ignoring the Timed Metadata tracks when determining the live edge.
  • Impact: none other than as described.

Added¶

• libfmp4: added support for DTS-UHD / DTS:X profile 2 (#)
  • The DTS:X audio codec is now supported for DASH output from both Origin and Packager. Playback from other output formats like fMP4 HLS might work too, but is not supported, since DASH is the only format for which streaming DTS:X is actually specified.
  • Impact: none other than as described.

• origin: added --time_signal option (#).
  • The SCTE 35 is considered legacy and a better alternative is to use the SCTE 35 command to signal splice events. This is now supported and can be enabled using the option. Enabling the use of disables the use of , which is the default.
  • Documentation: --time_signal.
  • Impact: none other than as described, although thorough testing of any workflow that employs SCTE 35 functionality is highly recommended, since it offers such a wide variety of options.

• libfmp4: added cromwellpsi.comt_template option (#).
  • It is now possible to override Origin's default behavior regarding the 'SegmentTemplate' format it uses to signal the media's timeline in the MPD it generates. The main use case for this option is to be able to specify but still get a 'SegmentTemplate' using instead of (which Origin switches to by default when specifying a custom length for the DASH segments it outputs). In general, it is recommended to use for reasons described in Segment Timeline Article.
  • Documentation: cromwellpsi.comt_template.
  • Impact: none other than as described.

• origin: add elements to DASH output for tracks which have specified (#).
  • When the option is used to specify a 'description' for a track, Origin will now also add this information to its DASH output in the form of a element that signals the description for the track in the MPD. This description may be used by a player to more clearly distinguish between the different kinds of tracks that a users can choose between.
  • Documentation: --track_description.

• remix: added support for audio silence for ac3, ec3 and dts (core hd and dts:x) codecs (#).
  • When remixing content, Remix now automatically adds silent padding to audio tracks if any gaps occur in the audio timeline. This works for audio tracks encoded in AAC, AC3, EC3 or DTS (Core HD and UHD). It makes a Remix workflow more robust and should further minimize playback issues when concatenating clips.
  • Impact: none other than as described.

• remix: added s3 authorization command-line options.
  • Unified Remix' command-line interface () now supports authentication when making requests to S3. Enabling it works the same as for .
  • Documentation: :ref: Authenticate requests to AWS S3.
  • Impact: none other than as described.

• package_hls: set FORCED attribute for subtitles when packaging WebVTT and specifying --track_role=forced-subtitle (#).
  • In and as part of the previous GA, support was added to set the 'FORCED' attribute to equal 'YES' for output from Origin when a track's role was set to . However, this functionality did not work when statically packaging HLS using Packager. This has now been fixed.
  • Impact: none other than as described.

• origin: added serving of tiled thumbnail jpegs, and generation of dynamic DASH manifests including these (#).
  • After support for Tiled Thumbnails was added to Packager in , Origin now also supports it. This means that Origin can ingest a Tiled Thumbnails track and add it to its DASH output (as that's the only output format that support this specific implementation of trick play at the moment). In addition to support for Origin, several configuration options have been added as well, which allow to specify how you want Packager to create the Tiled Thumbnails track.
  • Documentation: --trickplay --fourcc=jpeg.
  • Impact: none other than as described.

• cpix: USP-specific attribute added to the element to select the Common Encryption scheme type for fMP4 HLS and DASH output (#).
  • Important: attribute name changed to in !
  • To override the default CENC encryption scheme that is used for Origin's fMP4 HLS ('cbcs') and DASH ('cenc') output, support for a USP-specific attribute for the element was added. However, note that this attribute's name was changed to in , after DASH-IF agreed on the use case of this attribute and added it to the CPIX specification under this new name.
  • Impact: not supported, use the updated implementation as added in

• remix: support for SCTE 35 Auto Return Mode. Auto Return Mode do not require cue messages at the end of the break with out_of_network_indicator set to 0.
  • It is now possible to use the SCTE 35 Auto Return Mode with Remix, which allows you to signal the start and end of a break in one SCTE 35 message.
  • Impact: none other than as described.

• remix: allow downward relative dref URL creation (#).
  • Before, when a SMIL playlist that was used as input for Remix would contain relative references to tracks, using downward paths, the remixed MP4 generated by Remix would not include the downward paths, only the filenames. This has been fixed, so that it is now possible to create a remixed MP4 from a SMIL playlist that references tracks in subdirectories.
  • Impact: none other than as described.

Fixed¶

• cpix: when statically packaging fMP4 HLS, playready and widevine signaling is retained when adding sample-aes with --encrypt-key-url (#).
  • This fixes a regression that made it impossible to statically package fMP4 HLS with a combination of PlayReady, Widevine and FairPlay protection. In such cases, the signaling for PlayReady and Widevine would not be present in the output. This has now been fixed.
  • Impact: none other than as described.

• libfmp4: fixed overflow when truncating a progressive MP4 with vbegin/vend values over 4GB.
  • Creating a virtual subclip from a progressive MP4 source did not work when the specified start time was located more than 4GB 'into' the source. This has now been fixed.
  • Impact: none other than as described.

• origin: allow for missing "mdat" when all data is referenced externally (#).
  • Origin no longer requires an "mdat" to be present alongside a "moov" in an MP4, as this is not a ISO BMFF requirement and it caused problems with dref MP4's generated with older versions of , which did not yet add an "mdat" when generating a dref MP4.
  • Impact: none other than as described.

• package_hls: changed the default generation of GROUP-ID for subtitles to exclude the codec fourcc code.
  • Prior to this change, Packager appended the codec's FourCC code to the 'GROUP-ID' it associates with each subtitles track, i.e., a WebVTT encoded subtitles track would be assigned as its 'GROUP-ID'. When statically packaging a HLS stream that combines differently encoded subtitles tracks (i.e., IMSC-1 and WebVTT), this lead to these tracks being in different 'groups'. This change results in all subtitles tracks being in associated with the same 'GROUP-ID', .
  • Impact: this may impact the way a player presents the selection of subtitles that are present in a statically packaged HLS stream. If this is the case and you're unhappy with the result, or if there are any other reasons why you want to override the default way in which Packager assigns a 'GROUP-ID' to tracks, you can make use of the option as described in: Overriding default playlist values.

• package_hls: fixed encrypting of AC3 tracks in .ac3 files (regression introduced in ) (#).
  • Fixed a regression that was part of the previous GA, which caused a precondition failed error message to be thrown when statically packaging an AC3 track for HLS TS with encryption. This use case now works properly again.
  • Impact: none other than as described.

• metadata: always passthru Timed Metadata when 'timed_metadata' is defined (even when it's not part of a ?filter= query (#)).
  • Using Using dynamic track selection it is possible to filter a stream so that it will only contain tracks that comply with a (set of) filter rule(s). The fact that any track that is not explicitly included by the filter, is excluded from the stream caused problems because the need to also explicitly include Timed Metadata tracks is less apparent than it is for audio, video and text tracks, breaking workflows that relying on Timed Metadata and including filter(s) to dynamically select tracks. To avoid these problems, Timed Metadata tracks are now always included.
  • Impact: dynamically excluding a Timed Metadata tracks using the Using dynamic track selection option is no longer possible. We recommend to use separate server manifests for such scenarios instead (e.g., using Dynamic manifests).

• libfmp4: changed schemeURI for binary SCTE 35 data to (#).
  • For inband event messages containing SCTE 35 messages in binary form, we used to mistakenly signal as the schemeURI. This has now been changed to instead, to comply with the SCTE 35 specification as well as DASH-IF IOP
  • Impact: none other than as described.

• libfmp4: correctly evaluate "und" systemLanguage when dynamically filtering (#).
  • Using Using dynamic track selection, it is now possible to filter tracks that have no specified 'systemLanguage' by filtering on .
  • Impact: none other than as described.

Fixed¶

• package_mpd: output SCTE 35 using scheme (#, #).
  • Before, when statically packaging DASH with SCTE 35 the MPD would signal as the scheme for the and use base64 encoding for the actual SCTE 35 message signaled in the event. This has now been changed to use the correct scheme with binary encoded SCTE 35 messages, as recommended in DASH-IF IOP
  • Impact: Although the updated implementation as described above is according to spec, workflows that depend on the SCTE 35 signaling in DASH as produced by Packager prior to this fix might break and should be tested.

• cpix: in accordance with version of the CPIX specification, the ContentProtectionData element is now interpreted as "the full well-formed standalone XML fragment to be added to the DASH manifest under the ContentProtection element". The 'name' attribute of the CPIX DRMSystem element may be used to specify the 'value' attribute in the DASH manifest's ContentProtection element (#).
  • Prior to this change, our implementation of the element differed from the CPIX specification. It used to be interpreted as the baseencoded, well-formed XML data to be added to the DASH manifest under the corresponding element. This has now been changed as described above to fully align with the CPIX specification.
  • Documentation: CPIX Document Requirements.
  • Impact: CPIX documents specifically prepared to be compatible with our previous implementation of this element will need to be updated.

• cpix: in accordance with version of the CPIX specification, the HDSSignalingData element is now interpreted as "the full drmAdditionalHeader element to be added to the HDS playlist (including the beginning and ending tags)" (#).
  • Prior to this change, our implementation of the element differed from the CPIX specification. It used to be interpreted as the baseencoded data that falls under the element to be added to the HDS playlist. This has now been changed as described above to fully align with the CPIX specification.
  • Documentation: CPIX Document Requirements.
  • Impact: CPIX documents specifically prepared to be compatible with our previous implementation of this element will need to be updated.

Fixed¶

• capture: fixed segfault on malformed media (#).
  • Using Capture to decrypt certain malformed, encrypted media resulted in a segmentation fault. This now results in an error message instead.
  • Impact: none other than as described.

• capture: insert edit list in metadata track when capturing archive with or option (#).
  • Before, capturing a stream with SCTE 35 markers while maintaining the original timestamps of the stream (i.e., using Capture's or option) would break the SCTE 35 markers in the captured clip because the offset that was added to the tracks for video, audio and text through an edit list, was not added to the Timed Metadata track. This has now been fixed for these scenarios, by also adding an edit list to the Timed Metadata track.
  • Impact: none other than as described.

Packager and Origin¶

• Implemented changes from DASH Amendment 5

Origin only¶

• Additional DRM use cases covered with CPIX
• Functionality to configure URL aliases based on Apache's Rewrite Map
• Improved caching header logic

Capture¶

• Improved clipping functionality

Packager¶

• When statically packaging fMP4 HLS content with multiple DRM systems, adding FairPlay leads to the signaling for the DRM systems not being included.

Capture¶

• When using the or option, capturing SCTE 35 messages is currently not supported.

Added¶

• capture: clipping in now uses Remix API (#).
  • Clipping of timespans is improved and now uses the same logic as Remix. This means that audio clipping is always right-aligned, while video clipping is always left-aligned on GOPs, or on frames when the option is enabled. That is, for video Capture will scan the timeline from the specified timestamp to the left until it arrives at the start of either the start of a GOP or a frame. While for audio it will scan to the right until the start of an audio frame. This is true for both the specified start and end time of a clip.
  • Impact: None other than as described.

Added¶

• packager: reduce memory consumption when decrypting (#).
  • Instead of decrypting a complete file at once, this is now done in chunks. This leads to a significant decrease in the memory that is required, especially when decrypting very large files.
  • Impact: None other than as described.

• packager: allow downward relative dref URL creation from file input (#).