Tascam MMR-8 Instruction Manual

TimeLine EDL Format Addendum 1.0
To support Version 3.0 of the MX-2424, some additions have been made to the
OpenTL specification. With the way OpenTL rules are defined, and its parser
implemented, older parsers / implementations should have no problem
automatically dicarding the unknown attributes and continuing on with a good
read. The additions described in this section only affect the project file.
1) New Project Simple property attribute: Tape Mode State
TPMD Tape Mode State Integer (0 = Off, 1 = On)
example: TPMD(1) -- TapeMode State requested to be on
2) New Project complex value attribute: Virtual Track Table
This new attribute must optionally be placed before the TrackList
(TKLS) in the project file. Track indexes used by the virtual tracks
are always larger than the highest track supported by the generating
device. A new range of indexes is defined by the Virtual track table
to represent tracks that are editable, but not playable. Therefore,
this should not affect any prior compatibility. Previuos versions of
OpenTL implementations from Tascam represented virtual tracks by using
track indexes greater than or equal to 8192. Those virtual tracks will
remain virtual and non-editable (unless first explicitly loaded to
another slot). The table itself defines what index to start interpreting
tracks as virtual and editable, and the number of supported virtual
tracks (i.e. the max number of virtual tracks supported by the creator
of the OpenTL file). This defines the exact range of track indexes to be
treated as virtual and editable. For OpenTL files generated from Tascam
products, the start index for the first virtual track index will be set to
64, regardless of how many tracks that a given machine actually supports
for playback. That means for an MMR-8, indexes 8 through 63 will not be
used; for an MX-2424, indexes 24 through 63 will not be used. This may
change in the future, but not in the near future (only when a product that
records and plays more than 64 tracks is developed).
<VirtualTrackTable> = 'VTTB' '{' <VTableProp>+ '}'
<VTableProp> = ( <VirtualTrackStartIndex> | <NumVirtualTracks> | <GroupTable> )
<VirtualTrackStartIndex> = 'VTSI' '(' Integer ')'
<NumVirtualTracks> = 'VNUM' '(' Integer ')'
<GroupTable> = 'VTGR' '{' <GroupTableProps> '}'
<GroupTableProps> = <VirtualGroupNum> <CollapsedGroup> <TrackIndex>*

<VirtualGroupNum> = 'VGRP' '(' Integer ')'
<CollapsedGroup> = 'VCLP' '(' Integer ')'
<TrackIndex> = 'TKIN' '(' Integer ')'
Virtual Track Table FieldNames
VTTB Virtual Track Table Complex Value
VTSI Virtual Track Start Index Integer
VNUM Max Number Virtual Tracks Integer
VTGR Virtual Table Group Complex Value
VGRP Virtual group number Integer (group number representing the physical
track number)
(if a group entry is not present, then
it is assumed to
have no virtual tracks assigned to
it.)
VCLP Collapsed Virtual Group Integer (0, or 1; 1 meaning collapsed))
TKIN Track Index Integer (reference to the TKIN found
in the track list (TKLS))
3) New Project complex value attribute: User Groups Table
This new attribute must optionally be placed before the TrackList
(TKLS) in the project file. User groups are added to define groups of
tracks for editing or selection. A User group has a name attribute,
a group id, and contain a uniques list of track indexs (TKIN) to define
the tracks associated with a particluar group. It is incorrect to have a
track assigned to more than one group (if encountered, the first assignment
will hold). The track indexes can be any track defined in the project,
but is not meant to be used with non-editable virtual tracks, but is meant
to be used with editable virtual tracks.
<UserGroupsTable> = 'UGTB' '{' <UserGroup>+ '}'
<UserGroupTable> = 'UGRP' '{' <UserGroupProps> '}'
<UserGroupProps> = <UserGroupNum> <UserGroupName> <TrackIndex>*
<UserGroupNum> = 'UGNM' '(' Integer ')'
<UserGroupName> = 'UGNA' '(' String ')'
<TrackIndex> = 'TKIN' '(' Integer ')'

User Groups Table FieldNames
UGTB User Groups Table Complex Value
UGRP User Group Complex Value
UGNM User Group number Integer
UGNA User Group Name String
4) Summary
The updated definition of a project file is now:
(remember, everything between [ and ] is optional )
Definition of a ProjectFile
PJNM '(' "string" ')'
<SimpleProperty>*
[
VTTB
'{'
<VTableProp>+
'}'
]
[
UGTB
'{'
<UserGroup>+
'}'
]
TKLS
'{'
( TRAK <ComplexValue> )*
'}'
[
MKLS
'{'
( MARK <ComplexValue> )*
'}'
]
'#'

Example ProjectFile with Virtual Track Table And User Group Table:
PJNM ("MMR Project")
SMRT (4)
SASI (2)
SNTY ("SDII")
FRRT (0)
PUSQ (2)
TKSQ (2)
VTTB
{
VTSI(64)
VNUM(128)
VTGR
{
VGRP(0)
VCLP(0)
TKIN(0)
TKIN(64)
TKIN(65)
}
VTGR
{
VGRP(1)
VCLP(1)
TKIN(66)
TKIN(1)
TKIN(67)
}
}
UGTB
{
UGRP
{
GRNM(0)
GRNA("Take 1")
TKIN(0)
TKIN(1)
}
UGRP
{
GRNM(1)
GRNA("Take 2")
TKIN(64)
TKIN(66)
}
UGRP
{
GRNM(2)
GRNA("Take 3")
TKIN(65)
TKIN(67)
}
}
TKLS

{
TRAK
{
TKNM ("Track 1")
TKIN (1)
TKDS
{
FILE
{
VLTY ("HFS")
VLNM ("b4028aef-2")
DSNM ("14:Track1.trk")
}
}
}
TRAK
{
TKNM ("Track 1")
TKIN (2)
TKDS
{
FILE
{
VLTY ("HFS")
VLNM ("b4028aef-2")
DSNM ("14:Track2.trk")
}
}
}
}
MKLS
{
MARK
{
MKNB(1)
MKPT(172800000)
MKNM("Marker 1")
}
MARK
{
MKNB(2)
MKPT(175680000)
MKNM("Marker 2")
}
}
#