1. 11 Dec, 2019 4 commits
  2. 10 Dec, 2019 1 commit
  3. 09 Dec, 2019 3 commits
    • MatroskaExtractor: Support lacing in full blocks · 914a8df0
      Caveats:
      
      - Block additional data is ignored if the block is laced
        and contains multiple samples. Note that this is not
        a loss of functionality (SimpleBlock cannot have block
        additional data, and lacing was previously completely
        unsupported for Block)
      
      - Subrip and ASS samples are dropped if they're in laced
        blocks with multiple samples (I don't think this is
        valid anyway)
      
      Issue: #3026
      PiperOrigin-RevId: 284545197
      olly committed
    • MatroskaExtractor: Constrain use of sample state member variables · 0065f63f
      This change constrains the use of sample state member variables to
      writeSampleData, finishWriteSampleData and resetWriteSampleData.
      Using them elsewhere gets increasingly confusing when considering
      features like lacing in full blocks. For example sampleBytesWritten
      cannot be used when calling commitSampleToOutput in this case
      because we need to write the sample data for multiple samples
      before we commit any of them.
      
      Issue: #3026
      PiperOrigin-RevId: 284541942
      olly committed
    • Fix Javadoc issues · 567f2a65
      PiperOrigin-RevId: 284509437
      olly committed
  4. 06 Dec, 2019 30 commits
  5. 27 Nov, 2019 2 commits
    • Remove stray release note · 9d9a2a68
      Oliver Woodman committed
    • Fix audio processor draining for reconfiguration · d30b0285
      When transitioning to a new stream in a different format, the audio
      processors are reconfigured. After this, they are drained and then
      flushed so that they are ready to handle data in updated formats for the
      new stream.
      
      Before this change, some audio processors made the assumption that after
      reconfiguration no more input would be queued in their old input format,
      but this assumption is not correct: during draining more input may be
      queued. Fix this behavior so that the new configuration is not referred
      to while draining and only becomes active once flushed.
      
      Issue: #6601
      PiperOrigin-RevId: 282515359
      andrewlewis committed