Skip to content

Commit d452d66

Browse files
committed
Headers
1 parent 90f41ed commit d452d66

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

decoder_native_transforms.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,6 @@
1+
# Decoder Native Transforms
2+
3+
## API
14
We want to support this user-facing API:
25

36
```python
@@ -29,6 +32,7 @@ What the user is asking for, in English:
2932
chosen randomly upon the creation of the Python `VideoDecoder` object. All decoded
3033
frames use the same values for x and y.
3134

35+
## Design Considerations
3236
These three transforms are instructive, as they force us to consider:
3337

3438
1. How "easy" TorchVision transforms will be handled, where all values are
@@ -43,6 +47,7 @@ These three transforms are instructive, as they force us to consider:
4347
TorchVision. In particular, FPS is something that multiple users have
4448
asked for.
4549

50+
## Implementation Sketch
4651
First let's consider implementing the "easy" case of `Resize`.
4752

4853
1. We add an optional `transforms` parameter to the initialization of
@@ -83,7 +88,7 @@ For the transforms that do not exist in TorchVision, we can build on the above:
8388
3. We implement the mimimum needed to hook the new transforms into the
8489
machinery defined above.
8590

86-
Open questions:
91+
## Open questions:
8792

8893
1. Is `torchcodec.transforms` the right namespace?
8994
2. For random transforms, when should the value be fixed?

0 commit comments

Comments
 (0)