release notes - DAVID Systems

Transcription

RELEASE NOTES
2010.1.0
DAVID Systems
Page 2 of 33
Content
1.
General ........................................................................................4
1.1
Document information .................................................................................................... 4
1.2
DigaSystem Releases ....................................................................................................... 4
1.2.1.
Release .................................................................................................................... 4
1.2.2.
Patch ........................................................................................................................ 5
1.2.3.
Service Release ........................................................................................................ 5
1.2.4.
Release names ......................................................................................................... 5
2.
Content Management & Distribution...........................................6
2.1
Admin & DigaSQL ............................................................................................................ 6
2.2
DBM ................................................................................................................................. 6
2.2.1 Known issues ............................................................................................................... 6
2.3
DigAlign / DigAlignV / WebAlign / DigErase .................................................................... 7
2.4
DigaReplicator/ DigaReplicatorVideo 7.0........................................................................ 7
2.5
DigaTransferSystem 4.0................................................................................................... 7
2.6
DigaPorter 4.0 ................................................................................................................. 8
2.7
DigaMailboxIP Import ..................................................................................................... 9
2.8
DigaFTP 4.0 ...................................................................................................................... 9
2.9
SAF Server & Admin ........................................................................................................ 9
2.10
ReplMon WebService .................................................................................................... 10
2.11
ReplOrder WebService .................................................................................................. 10
3.
Broadcast...................................................................................11
3.1
DigAIRange 3.1 .............................................................................................................. 11
3.2
BUS 3.1 .......................................................................................................................... 12
3.2.1 New synchronization task ......................................................................................... 12
3.2.2 New ShowInsert task ................................................................................................. 13
3.2.3 Other BUS modifications ........................................................................................... 14
3.3
DigaMOS 3.0 .................................................................................................................. 14
3.4
TurboPlayer 3.1 ............................................................................................................. 15
3.4.1 CartBeat ..................................................................................................................... 15
3.4.2 New or enhanced macros ......................................................................................... 15
3.4.3 MiniDBM.................................................................................................................... 16
3.4.4 MusicMaster.............................................................................................................. 17
3.4.5 CartColor ................................................................................................................... 18
3.4.6 CFM............................................................................................................................ 18
DAVID Systems
Page 3 of 33
3.4.7 Dockable windows .................................................................................................... 18
3.4.8 New showlist mode ................................................................................................... 19
3.4.9 Jingles ........................................................................................................................ 20
3.4.10
Rundown lists ........................................................................................................ 20
3.4.11
General .................................................................................................................. 20
3.5
MultiPlayer 3.1 .............................................................................................................. 22
3.6
BCSMirror 3.0 ................................................................................................................ 22
3.7
DigaIndeX 3.0 ................................................................................................................ 22
4.
Media Production ......................................................................23
4.1
QuickIngest 1.0 .............................................................................................................. 23
4.2
DigaBurnDVD 2.0 ........................................................................................................... 24
4.3
Media Component Library (MCL) .................................................................................. 25
4.3.1 About ......................................................................................................................... 25
4.3.2 Supported A/V Formats............................................................................................. 25
4.3.3 Supported OS ............................................................................................................ 26
4.3.4 Features ..................................................................................................................... 26
4.3.5 Supported Programming Languages ......................................................................... 27
4.3.6 Basic Concept ............................................................................................................ 27
4.3.7 Layers......................................................................................................................... 28
4.3.8 Modules ..................................................................................................................... 29
4.3.9 Components .............................................................................................................. 29
4.3.10
Using the MCL ....................................................................................................... 29
4.3.10.1 Application Development.................................................................................. 29
4.3.10.2 Deployment ....................................................................................................... 29
4.3.10.3 Known Issues ..................................................................................................... 30
4.4
MTE 4 ............................................................................................................................. 31
4.5
MTE 5 ............................................................................................................................. 31
4.6
CartBeat ......................................................................................................................... 31
4.7
MetadataGenerator ...................................................................................................... 32
DAVID Systems
Page 4 of 33
1. General
1.1 Document information
This document provides information about the new features and enhancements of
the 2009.2.0 DigaSystem software release.
1.2 DigaSystem Releases
DAVID Systems will issues two main releases per year going forward. These
releases include all core products and are targeted for April/May and
September/October.
In-between these two main releases
- Service releases will be issued to cover cumulated bug fixes
- Patches will be released to address high priority problems in the field
This allows:
- Scheduled roadmap aligned to releases
- Clear assignment and schedules of features
The following chapters describe the type of releases to be issued.
1.2.1. Release
Cycle starts with a scheduled release “Release1”
- Covers core products
- Full testing coverage
DAVID Systems
Page 5 of 33
1.2.2. Patch
If problems arise which forces us to do a fix, they are issued as “Patch”
- Covers only specific problem/product
- Built on “Release” code branch
- Punctual testing of the specific problem
1.2.3. Service Release
- Depending on the needs, a defined “Service Release” will be issued
- Covers defined core products
- Includes all previously issued patches
- Built on “Release” code branch
- Integration tests
Other patches and service releases may be issued following the scheme
described above.
1.2.4. Release names
Releases are named and identified by:
<Year>.<Count>[.<Type>]
Year:
Count:
Type:
The year of the release (4 digits)
The release count (2 digits)
If set, the release is a service release
DAVID Systems
Page 6 of 33
2. Content Management & Distribution
2.1 Admin & DigaSQL
•
•
Database version 5 introduced containing the following changes:
o Database version is now stored in the database.
o Several new fields are added to the extended information table (_X)
in order to support NTSC. For complete list of changed, refer to
DigaTech.doc.
o Several new fields are added to the extended information table (_X)
for the features upcoming in the next releases. For complete list of
changed, refer to DigaTech.doc.
o New data structures and functions are added for accessing newly
added fields.
Number of changes and improvements addressing incorrect behavior,
stability and performance of Admin and DigaSQL.
2.2 DBM
•
•
•
•
•
•
•
•
•
•
[4.1 only] NTSC support. Requires database version 5.
[4.1 only] Audio normalization functionality for audio templates. Can be
used during import (for example, per drag & drop or from audio editors) or
during converting audio using “Convert Audio” dialog.
[4.1 only] LinkIn field editing.
[4.1 only] Possibility to start QuickIngest from the toolbar / menus.
[4.1 only] Possibility to create text entries from the toolbar / menus.
[3.5 and 4.1] New fields for filtering entries using selection toolbar:
Department, Sub-department, Speaker, Intensity.
[3.5 and 4.1] Possibility to keep previous state of selection toolbar if no
DefinitionToolbar parameter is defined.
[3.5 and 4.1] Minor bug fixes affecting functionality of selection toolbar.
[3.5 and 4.1] Number of changes and improvements addressing incorrect
behavior, stability and performance of DBM.
2.2.1
Known issues
MultiTable search does not work with the DefinitionToolbar
Copy Data dialog does not detect RTF file of elements which were generated by Copy
Data dialog
MultiRec2: Surroundfiles with Stereomix plays mixdown anyway! (existing Stereo
channels ignored)
DAVID Systems
Page 7 of 33
2.3 DigAlign / DigAlignV / WebAlign / DigErase
•
•
•
Support for Windows VISTA, Windows 7 and Server 2008 R2
Support for video conversion using the MCL:
DigAlignV can now use the MCL for file conversions. Conversion parameters
are all specified in the MCL templates, and the target format configuration in
DigAlignV is therefore reduced to selection of the MCL template. For the
naming of the created files, DigAlignV’s multiple naming options and the MCL
templates’ filename formatting schemes are merged in a consistent way.
RWW (“Read-While-Write”) support for video conversions:
When converting video files with MCL, VCL or MR3, DigAlignV now supports
conversion while the source file is still being recorded. Note that RWW
conversion jobs are run sequentially, just like all other conversions in
DigAlignV. Therefore each instance of DigAlignV runs not more than one
video conversion at any time.
2.4 DigaReplicator/ DigaReplicatorVideo 7.0
•
Support for Windows VISTA, Windows 7 and Server 2008 R2
2.5 DigaTransferSystem 4.0
•
Windows Vista /Windows 7 support:
Operations requiring administrative rights and approval by the UAC
(user access control) are marked with the UAC shield icon. The
required UAC elevation for those operations is achieved on-demand
by starting the application temporarily with elevation.
•
Configuration and other files created or changed during run-time aren’t
stored in the application folder anymore, but in the LocalAppData folder.
Windows Server 2008 R2 support:
Applications always run under windows-on-windows subsystem as 32bit
process.
HD support:
HD support is provided through MCL (MediaComponentLibrary).
[TT#23750] Session login to HTML status pages fixed
•
•
•
DAVID Systems
2.6 DigaPorter 4.0
•
•
•
Windows Vista /Windows 7 support
Windows Server 2008 R2 support
HD support (through MediaComponentLibrary)
•
[TT#23278] Memory folder can be specified now
Page 8 of 33
DAVID Systems
Page 9 of 33
2.7 DigaMailboxIP Import
•
•
•
•
Task policy is visible now
Destination extension selector is visible now allowing importing to other
destinations than DigaSystem database
•
•
Hash password before sending it to Depots with version >= 1.90
2.8 DigaFTP 4.0
•
•
•
2.9 SAF Server & Admin
•
•
•
Assembly install behaviour can be set in main menu and assembly cache can
be cleared from menu
DAVID Systems
•
•
•
•
•
[TT#23555] User abort sets module to new state
DisabledUntilSafServerRestarted to ensure stability.
[TT#23548] Lost message email was sent on change of hour even no email
limit was set.
[TT#23471] Path to SAF server protocol can be specified now on installer
GUI and as command-line option[TT#23648] SAF Server could be started more than once in
TerminalServer/RemoteDesktop sessions.
[TT#22977] Scheduler for “list of intra-day cycles” did niot serialize
configuration correctly.
2.10 ReplMon WebService
•
•
Various bugfixes
Project specific enhancements (FESAD)
2.11 ReplOrder WebService
•
Page 10 of 33
Various bugfixes
DAVID Systems
Page 11 of 33
3. Broadcast
3.1 DigAIRange 3.1
•
An auto-logout has been implemented. DigAIRange will logout the current
user after a definable time of inactivity.
•
The color of cart elements can be changed by the new service parameter
"AssignedProgram". This allows to give cart elements an appearance which
is different from the cart settings for the service (=program) which is
currently used. It also allows to group services: e.g. if you have a "real"
service and a training service, you can have identical cart settings for both
by assigning the real service to the training service.
•
The number of BroadcastServers DigAIRange could handle was limited to
40. This has been increased to an unlimited amount.
•
Show templates can now be declared as "master template" – one of them as
standard. Master templates can be used as template when a new show is
being created in a day or in a day template. The show data copied is: the
ACL, the team list, the class flag and a remote link. In addition the show
pool and all tracks are copied (including remote links). Besides, it is possible
now to set remote links for show templates or their tracks. They are not
active within the show template but if the template is becoming a real show
or a show in a day template the remote links can become active.
•
The database field [PROGRAM] can now be generated in different ways when
transferring elements from DigAIRange to DBM. The behavior is defined by
the parameter Digas\Planserver\...\...\DigAIRange\ProgramFieldGeneration.
DAVID Systems
Page 12 of 33
•
The DB field [PROGRAM] can be generated in different ways now. This field
is generated by DigAIRange when a section string is created. This happens
e.g. in drag&drop operations from DigAIRange to the DatabaseManager.
•
There were some small adjustments of the handling of times in the import.
•
Some small bugfixes - see DigAIRange_Changes.doc for more information.
3.2 BUS 3.1
3.2.1
New synchronization task
The synchronization task was completely rewritten. It is intended to duplicate
rundowns for two special purposes. First, it can generate an identical show
structure on a second place. This can be helpful for the administration of
multiple locations from a single place. Second, the task is intended to
duplicate the full rundown to enable the simultaneous playout of two
TurboPlayers for safety reasons. The second purpose cannot be handled by
the task so far, but this feature will be available with one of the next builds.
In every case the task works in a master -> slave relation only.
Here is the configuration dialog of this task:
The task can synchronize shows and tracks without groups and items or
complete shows with tracks, groups and items. The task is completely based
on events from BCS to avoid a too high load of the BCS. Remote links of
tracks can be modified during the copy process:
DAVID Systems
3.2.2
Page 13 of 33
New ShowInsert task
There is a new task: "ShowInsert". It allows to insert new database entries
directly to shows. (Hint: the old "AutoInsert" task has been renamed and is
called "PoolInsert" task now.) Here is the configuration dialog of
theShowInsert task:
See the BCSTechManual for more information about this task and its settings
DAVID Systems
3.2.3
Page 14 of 33
Other BUS modifications
•
The file check task has a new option to perform an analysis for silence
and to correct the mark values if necessary.
•
Support for new field <File_Converted> in Check task. This flag is set
when the file was converted and therefore file 0 differs from the other
files.
•
The import task has a new option to set the last element of each show
to FixedEnd / EndOnTime with the end time of the show. In addition
there is a new option to set the mute-start flag for these elements too.
•
The import task has a new option to ignore the times in the import
when performing a full insertion of the whole list.
3.3 DigaMOS 3.0
•
•
•
•
•
•
•
Windows Vista /Windows 7 support.
Supports MOS protocol version 2.8.3
Supports BC Server and NewsSchedulerX
broadcast lists
3 modes for accessing DigaSystem tables
o Ignore
o Read at start only
o Real time polling for changes
User defined destination in BC Server for
data from NCRS
o Show pool
o Show track
o Main track
o User defined track
o New created show
o Already existing show (time range for start and end time is user
defined, too)
User defined metadata for all available XML tags in DigaSystem broadcast
list for direction from DigaMOS to NCS
User defined metadata for all available XML tags for direction from NCS to
DigaMOS
DAVID Systems
Page 15 of 33
3.4 TurboPlayer 3.1
3.4.1
CartBeat
TurboPlayer supports beat-exact transitions now. This feature is called
"CartBeat". To perform these transitions elements must be tagged with beat
markers. This is done in a new page within MultiTrack editor (see below). The
CartBeat feature handling within TurboPlayer is described in TurboPlayerTechManual in the concepts chapter.
3.4.2
New or enhanced macros
TP_ChangeWndState ( GuiNo, Action, Sub window )
for dockable windows
Sub window:
CFM, Infotxt, Modtxt, MiniDBM
Action:
Dock, Undock, ToggleDock, Hide, Show, ToggleShow,
ToggleMinimizeOnCaptionBar (works only in undocked state)
TP_ExecuteStackButton ( GuiNo, StackButton ID )
Acts like the stack button click; for stack button ID see stack button settings;
TP_Prelisten ( GuiNo, MoveSoundhead, time in [msec] )
Moves the current prelisten position by the given time towards begin for a
neg. time value and towards end for a pos. time value. If no prelisten is
running and this macro is executed with neg. time value prelisten starts at the
end (MarkOut).
This command is handled for MultiPlayer, EasyPlayer (EP) and CFM
prelistening, depends on main settings | shortcuts > Prelisten keys refer to …
TP_MiniDBM ( Prelisten, Exit )
Exit parameter is new.
New: If successively press of TP_MiniDBM( Prelisten, End ) shortcut the
MiniDBM prelisten position is set continuously farther away the end.
DAVID Systems
Page 16 of 33
TP_MiniDBM ( Selection, Left/Right )
Left, Right parameters are new.
It moves the cart selection to the left/right; only valid for MiniDBM’s cart
view.
The existing macro command TP_MiniDBM( Selection, Up/Down ) now moves
the cart selection (cart view mode) one line up/down (before: to the
left/right).
TP_StartApp ( CommandLine, Verb, Flags )
Can be used to start a Windows application or a command line batch, or you
can perform a shell-execute on files. The command is handled in background
to avoid that such a long-time operation interferes with the real-time handling
of TurboPlayer.
3.4.3
MiniDBM
Prelisten
Repeatedly pressing of TP_MiniDBM(Prelisten,End) shortcut will set the
prelisten position of miniDBM successively further away from the end.
Selection toolbar (filters):
New selection criteria: ‘Department’, ‘Sub department’, ‘Speaker’,
‘Intensity’
Sub department values depend on selected 'Department' value, they are
linked.
Multiple department criteria are allowed, but only one department and its sub
departments can be active at the same time.
Maximum entries
Turbo uses its own defined value of maximum entries to show for database
queries; see settings | Columns > Max. items. Before the value
\Digas\Database\<database>\<table>\DBMLines were used by default.
Results can be restricted considering the sort order, e. g. Show the latest 100
results or first 50 in alphabetical order, etc.
Selection visibility
Improved the visibility of the selected table and selected entry (list view, not
cart view). Before visibility was poor if the background color of the MiniDBM
was set close to the default selection color of the list.
New option ‘Disable multi table mode’ hides the multi table icon; see settings.
Fasten up cart view (recognizable if many cart results (>5000)).
DAVID Systems
Page 17 of 33
Bugfixes
Crashed at startup if any selection value of the selection toolbar (saved in DS
at last runtime) contained a comma, e. g. Presenter: “surname, first name”.
Sometimes crashed if changed from multi to single table mode and v. v.
ODBC error ‘Column is ambiguously defined’ if using Oracle (10g) database
and table has cart view and \Digas\Settings\UsePrivacy = No”; using
DigaSQL.DLL >= 3319 will solve the problem (also with older TurboPlayer
versions).
Table view: Click or double click in empty area (outside tables area) and the
current selected table kept its visual selection state all the time.
Cart view: sort field and descending/ascending order was not saved in DS
registry.
Replace option 'Ask before replace' was not saved if this value was changed
within the enquiry dialog.
If database results were restricted (see Settings | Columns > Max. items) and
not all results were shown (more results than the allowed ‘Max. items’ value)
some items were missed in the sorted order.
3.4.4
MusicMaster
Update to new MusicMaster interface (SR-18) for replacing elements and
Unicode support; use DIMusicMaster.DLL >= 114.
The configuration file DIMusicMaster.xml moved to another folder (reason:
restricted write permission under Vista/Win7) to
%ALLUSERSPROFILE%\DigaSystem\DIMusicMaster\ (%ALLUSERSPROFILE%
Win7: C:\ProgramData; WinXP: C:\Documents and Settings\All
Users\Application Data\).
The xml file is automatically copied by the new DIMusicMaster.DLL.
On server side use HTTPPostServer.exe (no more MMServer.exe); it supports
UTF-8.
MusicMaster button of type ‘Metadata’ (filters for replacement song search):
More DS metadata fields can be queried to fill
the box (if 'same as song' is not active) that
shows the available values of the metadata field
in that table.
DAVID Systems
Page 18 of 33
New metadata fields are: SPEAKER,
INTENSITY, CUSTOMER, LANGUAGE,
PRESENTER, PRODUCT, PRODUCTGROUP,
PROGRAM, PROJECT, TYPE, CARRIER (the
Label). It’s the same amount of metadata fields
as in MiniDBM’s selection tool bar (except
'Department', 'Sub department').
The available metadata values are now
alphabetical sorted;
Bugfixes
MusicMaster button of type ‘Metadata’:
Box that shows the available metadata values of the specified metadata field
in that table ('Same as song' is not active) caused for some fields an ODBC
error box.
MusicMaster button of type ‘Length’ and option ‘Fit to gap’:
A sometimes wrong gap calculation in case of gaps in front of the
considered element, e. g. element is in a fixed end group or is in a backward
floating chain with fixed end.
3.4.5
CartColor
Considers the DS registry value in
Digas\PlanServer\<BCS>\<Program>\AssignedProgram (String) which
defines the cart color set used to draw the carts in the rundown lists and
MiniDBM; e. g. two programs of a BCS can use the same color set for their
carts (set the same ‘AssignedProgram’).
3.4.6
CFM
New icon for
Save and Exit
New option for two track mode applied at startup, see settings > Show
initial 2-tracks
New option to hide the undocked CFM after Exit or Save+Exit (via buttons or
shortcut); see settings > 'Hide undocked CFM after Exit'
3.4.7
Dockable windows
DAVID Systems
Page 19 of 33
New buttons in caption bar of the undocked
window: ‘Hide’ and ‘Dock window’ (to the
existing ‘Minimize on caption bar’). Last
states saved in DS registry (hidden,
undocked, minimized on caption bar) are
restored next run.
The close button/menu item hides the
undocked window (formerly used to dock the
window).
If the window becomes hidden it can be
shown again clicking on the corresponding
icon – that is highlighted upon hide.
Adjust which buttons (minimize on caption
bar / hide / dock) appear in caption bar of the
undocked windows, see Settings of the icon
bar (FastPrelisten, CFM, TXTs, MiniDBM);
Bugfixes
Mouse wheel in undocked text windows could sometimes not work (if lying
over a rundown list or overlapping with another undocked window);
3.4.8
New showlist mode
New mode button ‚Free showlist‘. If
this mode is activated, clicking the
old show selection button will open
the new show composition dialogue.
Create a composition of shows,
independently from date. Only the
shows contained in the composition
will be loaded in TurboPlayer.
DAVID Systems
3.4.9
Page 20 of 33
Jingles
Progress bar option for jingles; see settings, color of remain part adjustable.
Increased maximum number of jingle tabs to 100 (before: 20)
3.4.10 Rundown lists
Bugfixes
Drag & Drop at the end of a show in a rundown list was not possible if the show
titles were hidden (Settings | show title > ‘Hide show titles’ is activated).
Now a smooth divider between the shows visualizes the separation. [Note] If the
rundown background is set to transparent (Settings | Colors > Transparent) the
divider color is the background color used if not transparent.
3.4.11 General
Startup box: option to close the box also
if errors occurred
TurboPlayer supports multiple configurations in DS registry now. These are
top-level keys with a full set of settings which can be chosen during startup. See
TurboPlayer-TechManual chapter "concepts" and the parameter description for
"TurboPlayer\Configurations" for more information.
Filename: releasenotes_2010.1.0.doc
DAVID Systems
Page 21 of 33
A new parameter allows to prefer system elements when starting the next
element. This can be used to skip external elements you do not want to play and
to start the next internal element without explicitly calling the skip function - it is
sufficient to open one of the internal faders.
A new parameter allows to skip the previous elements when a mute-start
element starts. By default previous elements are not skipped.
A logic has been implemented to handle the beat-exact start of sequenced
elements. It allows to do beat-exact transitions without the need to schedule all
transitions beat-exact. This feature must be activated with a new parameter.
Bugfixes
Hanging Prelisten: Prelisten by engine (MultiPlayer) could hang – is then
blocking other prelisten by CFM or EasyPlayer – if a shortcut or middle mouse
button click should start this prelisten type, but no prelisten channel (see
Lines\Line-x\Channel-y\RundownListType = Prelisten ) is defined or the \GUI
parameter does not match this GUI’s number. This is checked now and in case of
incorrectness a hint 'Prelisten is not possible: No prelisten channel was assigned
to this GUI.' is shown in the status bar.
Player: corrected a jitter of the intro, outro times and their progress bars. This
occurred sometimes for certain intro/outro values.
Shortcuts like 'Alt' + another key did not work as shortcut.
Shortcuts can always be created using main settings | shortcuts > create a new
command. For more detailed description see also Turbo tech manual.
Buttons/boxes which are overlapped by another window still react on mouse
input (click) if mouse moves from none overlapped to the overlapped button
area. This concerned filter-, mode-, stack-, trash- and update start times-buttons
and the selection boxes (program, show, date, jinglegroup).
The internal socket routines could come into a state in which the connection
seemed to be o.k. (ping worked) but no "real" data could be transferred from
BCS to TurboPlayer. This state should be avoided now.
Reloading of elements in MultiPlayer was rewritten. This should avoid multiple
problems which could occur when an element was reloaded immediately before
its start.
DAVID Systems
Page 22 of 33
Sometimes TurboPlayer did not detect open GPIO faders during startup. This was
caused by internal timing problems and caused strange errors.
3.5 MultiPlayer 3.1
•
MultiPlayer AV supports playout of HD video (MPEG2) since version 3.1
3.6 BCSMirror 3.0
•
Windows Server 2008 R2 support.
3.7 DigaIndeX 3.0
•
Windows Server 2008 R2 support.
DAVID Systems
Page 23 of 33
4. Media Production
4.1 QuickIngest 1.0
DAVID QuickIngest gives you the possibility to quickly ingest all or selected clips from
XDCAM devices to DigaSystem tables. Currently the following models are tested:
•
•
•
PDW-HD1500 (FTP only)
PDW-U1
PDW-V1 (FTP only)
Following XDCAM devices use the same Sony drivers and software as tested devices
and are probably compatible, but are mentioned as untested:
•
•
•
•
PDW-530P
PDW-F350
PMW-EX1
XDZ-1
DAVID Systems
Page 24 of 33
Most metadata fields of DigaSystem can be edited before ingest. Read the
documentation for more details about how to customize the metadata area.
4.2 DigaBurnDVD 2.0
•
•
•
•
MCL based on the fly conversion for non mpeg II video files to a DVD
compatible mpeg II format. For supported video formats see MCL
documentation. AVI format is currently not supported.
MCL based logo insertion for branding video files. For supported formats see
MCL release notes. If logo has an alpha channel, than logo will be inserted
transparently.
New generic section LENGTH_FRAMES to see length of burned files as
HH:MM:SS:FF (hours, minutes, seconds, frames)
Known Issues:
•
•
•
Lack of file size estimation before MCL conversion.
16:9 DVD menue not supported.
DVD-R Dual Layer not supported by Nero api.
DAVID Systems
Page 25 of 33
4.3 Media Component Library (MCL)
4.3.1
About
This software is used to analyse and to convert A/V streams supporting a wide range of in
and output A/V formats. The implemented core components mainly meet the requirements for
broadcast industry applications rather than for customer products. On the one hand the MCL
can be used for rapid application development using the build-in components without having
a detailed knowledge about the various A/V formats and on the other hand you will be able to
easily extend the MCL framework by writing your own plug-in modules supporting a A/V
format, a specialized transformation or an I/O device which is not included in the standard
framework.
4.3.2
Supported A/V Formats
The following A/V formats are supported by the standard MCL framework for both video
systems PAL and NTSC.
Video
-
DV (consumer DV)
-
DVCPro25/50
-
MPEG-1/2 ES and PS streams ( separate audio Wave(PCM) )
-
XDCAM HD 422 720p/1080i
-
WMV
-
MXF (IMX/ DVCPro25/50)
Audio
-
PCM
-
AES3 331/ AES3 302
-
Mpeg-1 Layer 2
-
MP3
-
WMA
-
WAVE
DAVID Systems
4.3.3
Page 26 of 33
Supported OS
Currently the following OS are supported (included 64 bit systems):
-
Windows XP
-
Window Vista
-
Windows Server 2003
-
Windows Server 2008
-
Windows 7
4.3.4
Features
Feature
Description
Image overlay
RGBA images can be blend into the video stream at a
certain position (png, bmp, jpeg)
Auto field swapping
Recognize the input field order and adopt them to the
output format
Recognize the input resolution and adopt them to the
output format
Recognize the input aspect ratio and adopt them to the
output format or forces a given aspect ratio within a
template
Recognize the input frame rate and adopt them to the
output format
Recognize a IMX input format and crops the first 32
lines if the output format is not IMX
Recognize if the output format is IMX and the input
format is not – 32 black lines will be added on the top
Recognize the input audio sample rate and adopt them
to the output format
Recognize the bit depth of the input format and adopt
them to the output format (24 bit -> 16 bit)
Generates a multi channel audio stream from various
inputs
Generates multiple audio output streams containing a
certain number of channels from various inputs and is
able to switch the channel order
Generates a *_info.xml file according to DigaCut
ST/MT and DigaClip Player
Generates a video index files in case of writing mpeg
ES or PS streams
E.g. XDCAM HD 422 1080i to XDCAM HD 720p; MXF
Auto scaling
Auto aspect ration
Auto frame rate conversion
Auto cropper
Auto expander
Audio resampler
Audio bit depth converter
Audio stream muxer
Audio channel router
Metadata writer
Mpeg index file creation (*.vdx)
Creation of multiple clips from
DAVID Systems
Page 27 of 33
Feature
Description
one input in one turn
DVCPro50; WMV (LowRes/Web) this will save
bandwidth and decreases the transcoding time
dramatically
Easy configuration of ordinary format conversions up
to complex workflow templates
Support for MXF, Mpeg and DVCPro files
Can be used as data source and/ or data sink
Increases the robustness of applications according to
run time errors
XML Transcoding Templates
Read While Write (RWW)
Named pipes
External conversion processes
4.3.5
Supported Programming Languages
The MCL framework is written in C++ and so all the plug-in modules need to be written in
C++ as well. The API of the MCL is written in C++ and C# and you can use it in any .NET
language you want use to code your application with. It is possible to implement your own
API by using the MCL core component (MclKernel) directly. Doing that, you’ll be able to
support other programming languages for your applications like Visual Basic or even Java.
4.3.6
Basic Concept
Since a transcoding software is very complex, rich in configuration parameters and does
never stop growing, the basic idea of the MCL is to have a modular well structured framework
with less dependencies as possible. The framework is organized in various software
components which are hosted in dynamic link libraries (*.dll). Each component will process a
certain task and exposes common interfaces to interact with other components. Within a
component it is possible to warp anything else to get it into the framework and make it
available to other components. All components are registered in a own registry file
(MclRegistry.xml) and connected to certain A/V format. The registry is used to load a module
which hosts a desired component from a specified location for a defined format or operation
(transformation) respectively.
From an application point of view the MCL provides an API either for .NET or
C/C++ applications. Within the API the application doesn’t need to distinguish
between various A/V formats and knows only converter or player objects. Every
converter instance will run in an external process which will be controlled through
the API by every single instance separately. This will increase the robustness of
conversion applications since the application process won’t be affected by run
time errors occurred during a certain task. A conversion task can be configured
within a template XML file which describes the:
-
Input source (file or named pipe)
-
output format (container/essence)
DAVID Systems
Page 28 of 33
- transformations on audio and/or video streams (image overlay, audio channel
routing)
-
data sinks (file or named pipes).
4.3.7
Layers
The implementation of the MCL framework is based on software components which are
spread into three layers. The layers are divided into a control-, a processing- and an I/O
layer. Each component exposes at least one or in most cases multiple interfaces to interact
with others. As you can see the interfaces are always consumed in only one direction.
Because of that a component never knows the one uses it. Also the context in which a
component will be used is transparent to the component itself.
Application Layer
WebService
RenderService
Player
.NET
Archive
C/C++
Control Layer
MclController
IMclKernel
M clKernel
IMclMediaStreamReader
IMclTransformer
IMclMediaStreamWriter
Processing Layer
MclReaderXXX
IMclSplitter
MclSplitterXXX
IMclStreamReader
M clTransformerXXX
IMclDecoder
MclDecoderXXX
IMclEncoder
MclEncoderXXX
MclWriterXXX
IMclMuxer
MclM uxerXXX
IMclStreamWriter
I/O Layer
M clStreamReaderXXX
MclStreamWriterXXX
DAVID Systems
4.3.8
Page 29 of 33
Modules
The physically entities of the MCL framework are module. A module in this context is nothing
more than a pluggable dll. Each module implements a MCL dll interfaces to become a valid
MCL plug-in module. A module will host at least one MCL component and is commonly
rd
connected to a certain 3 party SDK. The components hosted in the same module should
logically fit in the same layer. For example, a MclReaderDV.dll hosts a DV splitter and a DV
decoder component but not a stream reader.
4.3.9
Components
In terms of the MCL framework a component is a logically entity exposing one or
more interfaces to get used by other components. A component is always
implemented and hosted by a module. If one component needs to consume
others it is not necessary to know in which module they are implemented. The
framework will take care about and you will always get the right instance of a
component you will need (see chapter MCL Registry).
4.3.10 Using the MCL
4.3.10.1 APPLICATION DEVELOPMENT
The MCL framework provides a small easy to use high level API for .NET and C/C++
applications or .NET services respectively. The most powerful feature of the API are
the XML transcoding templates providing a small bunch of XML tags. Within these
templates you are able to setup a wide range of different workflows without write any
additional line of code.
4.3.10.2 DEPLOYMENT
To install the MCL run time you just need to copy all folders and files to a location
where your application (service) can find it. All needed binaries the MCL needs either
ship with the MCL itself or they are included in the OS anyway. The default run time is
structured as follows:
DAVID Systems
Page 30 of 33
4.3.10.3 KNOWN ISSUES
-
-
ASF reader and writer need an installed Windows Media Player (consider
Windows Server has not installed Windows Media Player by default. You have to
install "Desktop Experience" tools first)
No timecode is written to DVCPro and IMX
ASF is not RWW capable
AVI is not supported yet
No ADX will be written
NTSC MXF are not fully IRT compliant
DAVID Systems
Page 31 of 33
4.4 MTE 4
Some bugfixes including problems when trimming different formats, zero detection on
timestretched objects and realtime volume modifications on copied objects.
4.5 MTE 5
Besides the bugfixes already listed for MTE 4 there are some new features and other
bugfixes:
• various shortcuts for different paste commands (ripple, ripple all etc.)
• possibility to reduce timebar above tracks and switch off time positions
• possibility to use standard windows project handling (Save, Save as ...) when
working without DBM
• supports VST effects
• supports definable samplerate conversion methods
• supports CartBeat (BPMScreen.ocx) as plugin screen for defining beats and
saving/restoring to/from the Digas database
• saving multiple clips as takes sometimes failed due to certain characters inside
the clipnames
4.6 CartBeat
The CartBeat or BPMScreen.ocx is a plug in for the MTE 5 editor, which is used for
defining beats inside audiofiles, that are needed for seamless audio mixing on air.
DAVID Systems
Page 32 of 33
The BPMScreen.ocx supports definable beat types and different BPM values for the start and the
end of an audiofile. A metronome click can be added during playback, which makes it easier to
check the exact position of a beat mark. The quantize function spreads all markers or all
markers inside the given range to equal distances, so after a rough input of beatmarkers by
typing the corresponding keys, it's easy to improve their positions. When you already know the
BPM value, as you are perhaps working on predefined jingles, you can simply place the
soundhead to the first click and fill the marked range according to the BPM value.
4.7 MetadataGenerator
•
•
•
Windows Vista/Windows 7 support
DAVID Systems
Page 33 of 33
Head Office:
Ridlerstrasse 31 b
80339 Munich - Germany
Phone
+49 89 540 139 0
Fax +49 89 540 139 50
[email protected]
Specifications and preliminary specifications are subject to change at any
time without prior notice.
© 2010, DAVID Systems GmbH

release notes - DAVID Systems

Transcription

Similar documents

The Mount Chacaltaya Laboratory: past, present and - Ev-K2-CNR

Aneel Paulus MD. MS1, Sharoon Akhtar MPhil1, Kelara

Turning the - Incriminator Audio

Ranking and community detection in unweighted networks

trigger point injections with traumeel® injection solution

April • 2015 - Pagoda Pacers

Wire Diagram

File

Stallions are Sons of Doc O Lena, Smooth as a Cat, Peptoboonsmal

your report here