Difference between revisions of "Sei Media Formats"

imported>NelsonJenkins
imported>NelsonJenkins
Line 1: Line 1:
The Sei Media Formats are read-only text files designed to store audio/video content for playback on SAE/SAL and SVE/SVL compatible players. There are four types of formats, as listed below.
+
The Sei Media Formats are read-only text files designed to store audio/video content for playback on SVE/SVL and SAE/SAL compatible players. There are four types of formats, as listed below.
 +
 
 +
==Sei Video Embedded (.SVE)==
 +
This format is designed for audio/video files with UUIDs and tag data directly embedded into the file. This is used primarily for short video clip distribution, although it is also the format used internally for NTBI Group Media Database storage.
 +
 
 +
File format:
 +
SVE2$5.000000$[tagdata]$[strippedkeyA1][strippedkeyV1][strippedkeyA2][strippedkeyV2]
 +
  1 2    3        4          5
 +
* 1 = Filetype header (SVE)
 +
* 2 = Data packet count
 +
* 3 = Final packet duration
 +
* 4 = Raw embedded tag data (see Tagging Format)
 +
* 5 = Compiled [strippedkey]s (UUIDs without dashes), alternating between audio and video (64 bytes per 10 second packet)
 +
 
 +
.SVE files are only ideal for distribution in situations where all of the following criteria apply:
 +
* Content is public-domain (e.g. you, nor anyone else, will care if the individual UUIDs and/or content itself are given away)
 +
* Content is short (under 4 minutes, as longer content will exceed 1024 bytes, causing media loading problems in some cases)
 +
* Tag data is short (under 100 characters total)
 +
* The file needs to be played if the NTBI Group Media Database is down (not planned, but if you're paranoid or during rare service interruptions)
 +
** It should be noted that if the Media Database ever ''were'' to disappear, most media using this format (as well as [[BTN]]) would break anyway, so there is no real need to "outlive" the database
 +
In all other cases, using the .SVL format is '''highly''' recommended.
 +
 
 +
==Sei Video Linked (.SVL)==
 +
This format is designed for audio/video files indirectly hosted on the NTBI Group Media Database.
 +
 
 +
File format:
 +
SVL[linkkey]
 +
  1    2
 +
* 1 = Filetype header (SVE)
 +
* 2 = A 20-character reference to the .SVE database entry (essentially the first 8 and last 12 characters of a generated UUID, to keep the file within 32 bytes)
 +
 
 +
.SVL files are better for distribution in that they are:
 +
* Smaller - a single file would look like "SVL550e8400446655440000" and would fit within 32 bytes, the default file block size for the [[Mark I]], and easily transferable
 +
* Private - none of the raw content is ever shown to the user (''however'', note that obviously UUIDs are still visible to users who know how to view playing sound UUIDs)
 +
* Secure - files can have passive DRM that limits their use to certain player/receiver owners
 +
* Indirectly loaded - content and tags can be longer because players have far lower restrictions due to the content being downloaded in the background
 +
* Deletable - if you don't want the file to be played anymore (or you uploaded something copyrighted), the file can be deleted and will not be able to play
 +
* Chainable - multiple files can be chained together in a .SVD file for sequential playback
  
 
==Sei Audio Embedded (.SAE)==
 
==Sei Audio Embedded (.SAE)==
This format is designed for chained audio files with UUIDs directly embedded into the file. This is used primarily for short audio clips.
+
This format is designed for audio-only files with UUIDs and tag data directly embedded into the file. This is used primarily for short audio clip distribution, although it is also the format used internally for NTBI Group Media Database storage.
 +
 
 +
File format:
 +
SAE2$5.000000$[tagdata]$[strippedkey1][strippedkey2]
 +
  1 2    3        4          5
 +
* 1 = Filetype header (SAE)
 +
* 2 = Data packet count
 +
* 3 = Final packet duration
 +
* 4 = Raw embedded tag data (see Tagging Format)
 +
* 5 = Compiled [strippedkey]s (UUIDs without dashes)
 +
 
 +
.SAE files are only ideal for distribution in situations where .SVE files would be also ideal (see above).
  
 
==Sei Audio Linked (.SAL)==
 
==Sei Audio Linked (.SAL)==
This format is designed for chained audio files indirectly hosted on the NTBI Group Media Database. This is used for longer audio clips, music, etc.
+
This format is designed for audio-only files indirectly hosted on the NTBI Group Media Database.
 +
 
 +
File format:
 +
SAL[linkkey]
 +
  1    2
 +
* 1 = Filetype header (SVE)
 +
* 2 = A 20-character reference to the .SAE database entry (essentially the first 8 and last 12 characters of a generated UUID, to keep the file within 32 bytes)
 +
 
 +
.SAL files are better for distribution for basically the same reasons as .SVL files.
 +
 
 +
==Sei Video Disk (.SVD)==
 +
This format is designed to compile multiple .SVL files into a single "disk". When played, .SVD files can give the user the option to choose between the included .SVL files or play all, depending on the playback profile flag.
 +
 
 +
File format:
 +
SVD02$[disktitle]$[linkkey][tracktitle]&[linkkey][tracktitle]
 +
  1 23      4          5
 +
* 1 = Filetype header (SVD)
 +
* 2 = Playback profile (see Disk Playback Profiles)
 +
* 3 = Link packet count
 +
* 4 = Disk title (shown during track selection)
 +
* 5 = Series of link packets (a .SVL [linkkey] followed by the track title) separated by &
 +
 
 +
==Sei Audio Disk (.SAD)==
 +
This format is designed to compile multiple .SAL files into a single "disk". When played, .SAD files can give the user the option to choose between the included .SAL files or play all, depending on the playback profile flag.
  
The advantages to using link-hosted files is that it dramatically decreases the filesize - while .SAE files take up 32 bytes for every 10 seconds of audio, .SAL files only take up 32 bytes for the reference link and do not expand based on file length. This only affects the length of the .SAL file itself - when played, the equivalent .SAE file is internally generated anyway in the player. Note that the resulting file will still be greater than 32 bytes due to header information.
+
File format:
 +
SAD02$[disktitle]$[linkkey][tracktitle]&[linkkey][tracktitle]
 +
  1 23      4          5
 +
* 1 = Filetype header (SAD)
 +
* 2 = Playback profile (see Disk Playback Profiles)
 +
* 3 = Link packet count
 +
* 4 = Disk title (shown during track selection)
 +
* 5 = Series of link packets (a .SAL [linkkey] followed by the track title) separated by &
  
==Sei Video Embedded (.SVE)==
+
==Disk Playback Profiles==
This format is designed for chained audio/video files with UUIDs directly embedded into the file. This is used primarily for short video clips.
+
For .SVD and .SAD formats, these are the playback profiles available:
 +
* 0 = CD-like, ideal for a music CD or other basic sequential loopable media
 +
** On load, first track is started
 +
** When track is finished, follow player option on whether to repeat track or move to next track (default is no repeat, so move to next track)
 +
** When disk is finished, follow player option on whether to return to first track or stop (default is no repeat, so stop)
 +
** Allow user to select track to move to a specific track
 +
* 1 = DVD-like separate tracks, ideal for a package of separate videos
 +
** On load, open track selection menu
 +
** When track is finished, return to track selection menu (cannot play tracks sequentially)
 +
* 2 = DVD-like sequential tracks, ideal for a movie or other long video ''note that loading tracks may be delayed in some players, so this may not be a smooth transition!''
 +
** On load, open track selection menu
 +
** When track is finished, move to next track
 +
** When disk is finished, return to track selection menu (cannot return to first track)
 +
However, note that these profiles can be overridden in advanced players.
  
==Sei Video Linked (.SVL)==
+
'''IF YOU HAVE SUGGESTIONS FOR OTHER PROFILES, LET NELSON JENKINS KNOW'''
This format is designed for chained audio/video files indirectly hosted on the NTBI Group Media Database. This is used for longer video clips.
 
  
Like .SAL files, .SVL files benefit greatly due to less space required in the file itself. This is especially useful for video, since .SVE files take up 64 bytes for every 10 seconds due to having an audio and video stream, while .SVL files only take up 32 bytes for the reference link.
+
==Tagging Format==
 +
TBA

Revision as of 16:53, 14 February 2013

The Sei Media Formats are read-only text files designed to store audio/video content for playback on SVE/SVL and SAE/SAL compatible players. There are four types of formats, as listed below.

Sei Video Embedded (.SVE)

This format is designed for audio/video files with UUIDs and tag data directly embedded into the file. This is used primarily for short video clip distribution, although it is also the format used internally for NTBI Group Media Database storage.

File format:

SVE2$5.000000$[tagdata]$[strippedkeyA1][strippedkeyV1][strippedkeyA2][strippedkeyV2]
 1 2    3         4          5
  • 1 = Filetype header (SVE)
  • 2 = Data packet count
  • 3 = Final packet duration
  • 4 = Raw embedded tag data (see Tagging Format)
  • 5 = Compiled [strippedkey]s (UUIDs without dashes), alternating between audio and video (64 bytes per 10 second packet)

.SVE files are only ideal for distribution in situations where all of the following criteria apply:

  • Content is public-domain (e.g. you, nor anyone else, will care if the individual UUIDs and/or content itself are given away)
  • Content is short (under 4 minutes, as longer content will exceed 1024 bytes, causing media loading problems in some cases)
  • Tag data is short (under 100 characters total)
  • The file needs to be played if the NTBI Group Media Database is down (not planned, but if you're paranoid or during rare service interruptions)
    • It should be noted that if the Media Database ever were to disappear, most media using this format (as well as BTN) would break anyway, so there is no real need to "outlive" the database

In all other cases, using the .SVL format is highly recommended.

Sei Video Linked (.SVL)

This format is designed for audio/video files indirectly hosted on the NTBI Group Media Database.

File format:

SVL[linkkey]
 1     2
  • 1 = Filetype header (SVE)
  • 2 = A 20-character reference to the .SVE database entry (essentially the first 8 and last 12 characters of a generated UUID, to keep the file within 32 bytes)

.SVL files are better for distribution in that they are:

  • Smaller - a single file would look like "SVL550e8400446655440000" and would fit within 32 bytes, the default file block size for the Mark I, and easily transferable
  • Private - none of the raw content is ever shown to the user (however, note that obviously UUIDs are still visible to users who know how to view playing sound UUIDs)
  • Secure - files can have passive DRM that limits their use to certain player/receiver owners
  • Indirectly loaded - content and tags can be longer because players have far lower restrictions due to the content being downloaded in the background
  • Deletable - if you don't want the file to be played anymore (or you uploaded something copyrighted), the file can be deleted and will not be able to play
  • Chainable - multiple files can be chained together in a .SVD file for sequential playback

Sei Audio Embedded (.SAE)

This format is designed for audio-only files with UUIDs and tag data directly embedded into the file. This is used primarily for short audio clip distribution, although it is also the format used internally for NTBI Group Media Database storage.

File format:

SAE2$5.000000$[tagdata]$[strippedkey1][strippedkey2]
 1 2    3         4          5
  • 1 = Filetype header (SAE)
  • 2 = Data packet count
  • 3 = Final packet duration
  • 4 = Raw embedded tag data (see Tagging Format)
  • 5 = Compiled [strippedkey]s (UUIDs without dashes)

.SAE files are only ideal for distribution in situations where .SVE files would be also ideal (see above).

Sei Audio Linked (.SAL)

This format is designed for audio-only files indirectly hosted on the NTBI Group Media Database.

File format:

SAL[linkkey]
 1     2
  • 1 = Filetype header (SVE)
  • 2 = A 20-character reference to the .SAE database entry (essentially the first 8 and last 12 characters of a generated UUID, to keep the file within 32 bytes)

.SAL files are better for distribution for basically the same reasons as .SVL files.

Sei Video Disk (.SVD)

This format is designed to compile multiple .SVL files into a single "disk". When played, .SVD files can give the user the option to choose between the included .SVL files or play all, depending on the playback profile flag.

File format:

SVD02$[disktitle]$[linkkey][tracktitle]&[linkkey][tracktitle]
 1 23      4          5
  • 1 = Filetype header (SVD)
  • 2 = Playback profile (see Disk Playback Profiles)
  • 3 = Link packet count
  • 4 = Disk title (shown during track selection)
  • 5 = Series of link packets (a .SVL [linkkey] followed by the track title) separated by &

Sei Audio Disk (.SAD)

This format is designed to compile multiple .SAL files into a single "disk". When played, .SAD files can give the user the option to choose between the included .SAL files or play all, depending on the playback profile flag.

File format:

SAD02$[disktitle]$[linkkey][tracktitle]&[linkkey][tracktitle]
 1 23      4          5
  • 1 = Filetype header (SAD)
  • 2 = Playback profile (see Disk Playback Profiles)
  • 3 = Link packet count
  • 4 = Disk title (shown during track selection)
  • 5 = Series of link packets (a .SAL [linkkey] followed by the track title) separated by &

Disk Playback Profiles

For .SVD and .SAD formats, these are the playback profiles available:

  • 0 = CD-like, ideal for a music CD or other basic sequential loopable media
    • On load, first track is started
    • When track is finished, follow player option on whether to repeat track or move to next track (default is no repeat, so move to next track)
    • When disk is finished, follow player option on whether to return to first track or stop (default is no repeat, so stop)
    • Allow user to select track to move to a specific track
  • 1 = DVD-like separate tracks, ideal for a package of separate videos
    • On load, open track selection menu
    • When track is finished, return to track selection menu (cannot play tracks sequentially)
  • 2 = DVD-like sequential tracks, ideal for a movie or other long video note that loading tracks may be delayed in some players, so this may not be a smooth transition!
    • On load, open track selection menu
    • When track is finished, move to next track
    • When disk is finished, return to track selection menu (cannot return to first track)

However, note that these profiles can be overridden in advanced players.

IF YOU HAVE SUGGESTIONS FOR OTHER PROFILES, LET NELSON JENKINS KNOW

Tagging Format

TBA