Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ketos ketos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • public_projects
  • ketosketos
  • Merge requests
  • !229

Merged
Created Feb 03, 2022 by Oliver Kirsebom@kirsebomOwner

Batch audio loading

  • Overview 1
  • Commits 13
  • Pipelines 4
  • Changes 4

This merge request resolves this issue: #157 (closed)

To achieve this I have cleaned up and refactores the classes in the audio_loader module somewhat. The changes are almost but not fully backward compatible.

In particular, these are the non-backward compatible changes:

  1. The __next__ method of the AudioLoader classes now issues a StopIteration when all segments have been loaded once, whereas before it would just keep going. This behaviour can be controlled with the new stop argument.

  2. The AudioLoader classes now all have the argument batch_size whereas previously this argument was only available for AudioFrameStepper and had a different meaning.

  3. There is a new AudioFrameEfficientLoader which essentially does what AudioFrameStepper(batch_size > 1) used to do.

@bpadovese , given the non-backward compatibility, should we save these changes for v3.0? On the other hand, I think very few users if any will notice any of this, so perhaps we can just add it to v2.5?

Edited Feb 03, 2022 by Oliver Kirsebom
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: batch_audio_loading