Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P purr-data
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 363
    • Issues 363
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 53
    • Merge requests 53
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Jonathan Wilkes
  • purr-data
  • Issues
  • #260
Closed
Open
Issue created Feb 16, 2017 by Albert Gräf@aggraefDeveloper

Reloading the device tables in the prefs

I'm fairly sure that there's already code for that in the engine, so we might just have to expose that via the prefs dialog, by adding corresponding buttons on the Audio and MIDI tabs (something like "Rescan devices" in Reaper). Currently the user must relaunch Purr after connecting external audio and MIDI gear like in good ol' vanilla, which is inconvenient.

Assignee
Assign to
Time tracking