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
  • Issues
  • #157

Closed
Open
Created Jan 28, 2022 by Oliver Kirsebom@kirsebomOwner

Audio batch loading

Currently, the AudioFrameLoader provides the option to specify a batch_size. However, the behaviour is perhaps a bit counterintuitive. The loader does load several waveform segments in one go (and converts them to spectrograms in one go too), which tends to be computationally more efficient than loading and converting them one at the time, but it only returns one segment at a time (the loaded batch is kept in a class attribute). Would it be more useful and intuitive to have it return the entire batch at every call to next()?

@bpadovese , your thoughts?

Also, from the point of code structure, I think the code could be improved by creating another class called AudioSingleFramerLoader and have the AudioFrameLoader delegate work to this helper class.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking