You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the use case for your proposed feature? Please describe.
I am attempting to parse (in near real time) a KLV bytestream coming out of an external ffmpeg process. I'd like to parse the InputStream directly with KlvParser without needing to figure out the message lengths myself.
Describe the solution you'd like
Add a KlvParser.parseStream(InputStream is) method.
Describe alternatives you've considered
Given the unknown aspect of message lengths, and that KlvParser.parseBytes doesn't tell me how many bytes have been read, I'd have to implement my own stream processing logic, and feed the byte[] into parseBytes().
The text was updated successfully, but these errors were encountered:
ruckc
pushed a commit
to ruckc/jmisb-streaming-klv
that referenced
this issue
Dec 16, 2022
What is the use case for your proposed feature? Please describe.
I am attempting to parse (in near real time) a KLV bytestream coming out of an external ffmpeg process. I'd like to parse the InputStream directly with KlvParser without needing to figure out the message lengths myself.
Describe the solution you'd like
Add a
KlvParser.parseStream(InputStream is)
method.Describe alternatives you've considered
Given the unknown aspect of message lengths, and that KlvParser.parseBytes doesn't tell me how many bytes have been read, I'd have to implement my own stream processing logic, and feed the byte[] into parseBytes().
The text was updated successfully, but these errors were encountered: