Project import generated by Copybara.

PiperOrigin-RevId: 254198377
This commit is contained in:
MediaPipe Team
2019-06-20 09:13:19 -07:00
committed by jqtang
parent 7ac795a621
commit 5687062d10
4 changed files with 4 additions and 5 deletions
+1 -1
View File
@@ -117,7 +117,7 @@ combination of tag name and index number. You can see some examples of input and
output identifiers in the example below. `SomeAudioVideoCalculator` identifies
its video output by tag and its audio outputs by the combination of tag and
index. The input with tag `VIDEO` is connected to the stream named
`video_stream`. The inputs with tag `AUDIO` and indices `0` and `1` are
`video_stream`. The outputs with tag `AUDIO` and indices `0` and `1` are
connected to the streams named `audio_left` and `audio_right`.
`SomeAudioCalculator` identifies its audio inputs by index only (no tag needed).
+2 -2
View File
@@ -20,7 +20,7 @@ process new data sets, in the [documentation](https://github.com/google/mediapip
1. Checkout mediapipe repository
```bash
git clone https://github.com/google/mediapipe/mediapipe
git clone https://github.com/google/mediapipe.git
cd mediapipe
```
@@ -115,7 +115,7 @@ python -m mediapipe.examples.desktop.media_sequence.demo_dataset \
### Preparing your own data set
The process for preparing your own data set is described in the [MediaSequence
documentation](https://github.com/google/mediapipe/tree/master/mediapipe/util/sequence/README.md).
documentation](https://github.com/google/mediapipe/blob/master/mediapipe/util/sequence/README.md).
The Python code for Charades can easily be modified to process most annotations,
but the MediaPipe processing warrants further discussion. MediaSequence uses
MediaPipe graphs to extract features related to the metadata or previously