[webrtc-insertable-streams] Does transform receive Frames or Chunks? (#47)

boulos has just created a new issue for https://github.com/w3c/webrtc-insertable-streams:

== Does transform receive Frames or Chunks? ==
Many of the examples here (as in the current explainer.md) have the signature:

 ```async transform(encodedFrame, controller)```

but assuming that this is really just Streams, isn't the original example from the slides (https://docs.google.com/presentation/d/1NIHzumglY9cYa4b7rcEbHGVsMam5BiY80VfFDB6cDjQ/edit#slide=id.g7eb1549726_1_10):

 ```async transform(chunk, controller)```

more accurate? That is, does InsertableStreams build up a full frame for arg0.data?

Nearly all online examples just overwrite / mess with all the bytes in a uniform way (e.g., bit complementing everything) that wouldn't whether arg0 was just a chunk or the full frame.

Maybe documenting what happens for a video stream in VP8 would be useful? https://github.com/w3c/webrtc-insertable-streams/issues/32#issuecomment-636032431 mentions that:

> It actually doesn't provide access to the full info of the RTP payload; the RTP headers and the segmenting that goes into putting frames into RTP packets isn't reflected in the Insertable Streams API.

But that note isn't reflected in either the spec (index.bs, correct?) nor explainer.md for "what actually goes into the ArrayBuffer data".

@alvestrand could you clarify this?

Please view or discuss this issue at https://github.com/w3c/webrtc-insertable-streams/issues/47 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 22 September 2020 01:41:42 UTC