jamie/ptulsconv
1
0
Fork 0
mirror of https://github.com/iluvcapra/ptulsconv.git synced 2025-12-31 08:50:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

Hard wrap text

Browse Source
This commit is contained in:
Jamie Hardt
2021-10-02 16:26:56 -07:00
parent d0da79b31b
commit 68969e77e2
1 changed files with 43 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

76
README.md
View File

@@ -8,8 +8,9 @@ Read Pro Tools text exports and generate JSON, PDF reports.
## Notice! ## Notice!
At this time there are a lot of changes in the HEAD of this package and you should use the last posted Pypi package. At this time there are a lot of changes in the HEAD of this package and you
New features and much better reporting, including native PDF reports, are coming soon! should use the last posted Pypi package. New features and much better
reporting, including native PDF reports, are coming soon!
## Installation ## Installation
@@ -17,40 +18,43 @@ The easiest way to install on your site is to use `pip`:
% pip3 install ptulsconv % pip3 install ptulsconv
This will install the necessary libraries on your host and gives you command-line access to the tool through an This will install the necessary libraries on your host and gives you
entry-point `ptulsconv`. In a terminal window type `ptulsconv -h` for a list of available options. command-line access to the tool through an entry-point `ptulsconv`. In a
terminal window type `ptulsconv -h` for a list of available options.
## Theory of Operation ## Theory of Operation
[Avid Pro Tools][avp] exports a tab-delimited text file organized in multiple parts with an uneven syntax that usually [Avid Pro Tools][avp] exports a tab-delimited text file organized in multiple
can't "drop in" to other tools like Excel or Filemaker. This tool accepts a text export from Pro Tools and produces an parts with an uneven syntax that usually can't "drop in" to other tools like
XML file in the `FMPXMLRESULT` schema which Filemaker Pro can import directly into a new table. Excel or Filemaker. This tool accepts a text export from Pro Tools and produces
an
...
In the default mode, all of the clips are parsed and converted into a flat list of events, one Filemaker Pro row per
clip with a start and finish time, track name, session name, etc. Timecodes are parsed and converted into frame counts
and seconds. Text is then parsed for descriptive meta-tags and these are assigned to columns in the output list.
[avp]: http://www.avid.com/pro-tools [avp]: http://www.avid.com/pro-tools
### Fields in Clip Names ### Fields in Clip Names
Track names, track comments, and clip names can also contain meta-tags, or "fields," to add additional columns to the Track names, track comments, and clip names can also contain meta-tags, or
output. Thus, if a clip has the name: "fields," to add additional columns to the output. Thus, if a clip has the
name:
`Fireworks explosion {note=Replace for final} $V=1 [FX] [DESIGN]` `Fireworks explosion {note=Replace for final} $V=1 [FX] [DESIGN]`
The row output for this clip will contain columns for the values: The row output for this clip will contain columns for the values:
|...| PT.Clip.Name| note | V | FX | DESIGN | ...| |...| PT.Clip.Name | note | V | FX | DESIGN | ... |
|---|------------|------|---|----|--------|----| |---|--------------------|-------------------|---|----|--------|-----|
|...| Fireworks explosion| Replace for final | 1 | FX | DESIGN | ... | |...| Fireworks explosion| Replace for final | 1 | FX | DESIGN | ... |
These fields can be defined in the clip name in three ways: These fields can be defined in the clip name in three ways:
* `$NAME=VALUE` creates a field named `NAME` with a one-word value `VALUE`. * `$NAME=VALUE` creates a field named `NAME` with a one-word value `VALUE`.
* `{NAME=VALUE}` creates a field named `NAME` with the value `VALUE`. `VALUE` in this case may contain spaces or any * `{NAME=VALUE}` creates a field named `NAME` with the value `VALUE`. `VALUE`
character up to the closing bracket. in this case may contain spaces or any character up to the closing bracket.
* `[NAME]` creates a field named `NAME` with a value `NAME`. This can be used to create a boolean-valued field; in the * `[NAME]` creates a field named `NAME` with a value `NAME`. This can be used
output, clips with the field will have it, and clips without will have the column with an empty value. to create a boolean-valued field; in the output, clips with the field will
have it, and clips without will have the column with an empty value.
For example, if two clips are named: For example, if two clips are named:
@@ -68,30 +72,36 @@ The output will contain the range:
### Fields in Track Names and Markers ### Fields in Track Names and Markers
Fields set in track names, and in track comments, will be applied to each clip on that track. If a track comment Fields set in track names, and in track comments, will be applied to each clip
contains the text `{Dept=Foley}` for example, every clip on that track will have a "Foley" value in a "Dept" column. on that track. If a track comment contains the text `{Dept=Foley}` for
example, every clip on that track will have a "Foley" value in a "Dept" column.
Likewise, fields set on the session name will apply to all clips in the session. Likewise, fields set on the session name will apply to all clips in the session.
Fields set in markers, and in marker comments, will be applied to all clips whose finish is *after* that marker. Fields Fields set in markers, and in marker comments, will be applied to all clips
in markers are applied cumulatively from breakfast to dinner in the session. The latest marker applying to a clip has whose finish is *after* that marker. Fields in markers are applied cumulatively
precedence, so if one marker comes after the other, but both define a field, the value in the later marker from breakfast to dinner in the session. The latest marker applying to a clip
has precedence, so if one marker comes after the other, but both define a
field, the value in the later marker prevails.
An important note here is that, always, fields set on the clip name have the highest precedence. If a field is set in a clip An important note here is that, always, fields set on the clip name have the
name, the same field set on the track, the value set on the clip will prevail. highest precedence. If a field is set in a clip name, the same field set on the
track, the value set on the clip will prevail.
### Using `@` to Apply Fields to a Span of Clips ### Using `@` to Apply Fields to a Span of Clips
A clip name beginning with "@" will not be included in the CSV output, but its fields will be applied to clips within A clip name beginning with "@" will not be included in the CSV output, but its
its time range on lower tracks. fields will be applied to clips within its time range on lower tracks.
If track 1 has a clip named `@ {Sc=1- The House}`, any clips beginning within that range on lower tracks will have a If track 1 has a clip named `@ {Sc=1- The House}`, any clips beginning within
field `Sc` with that value. that range on lower tracks will have a field `Sc` with that value.
### Using `&` to Combine Clips ### Using `&` to Combine Clips
A clip name beginning with "&" will have its parsed clip name appended to the preceding cue, and the fields of following A clip name beginning with "&" will have its parsed clip name appended to the
cues will be applied (later clips having precedence). The clips need not be touching, and the clips will be combined preceding cue, and the fields of following cues will be applied (later clips
into a single row of the output. The start time of the first clip will become the start time of the row, and the finish having precedence). The clips need not be touching, and the clips will be
time of the last clip will become the finish time of the row. combined into a single row of the output. The start time of the first clip
will become the start time of the row, and the finish time of the last clip
will become the finish time of the row.