Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
purr-data
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 268
    • Issues 268
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 16
    • Merge Requests 16
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Jonathan Wilkes
  • purr-data
  • Issues
  • #575

Closed
Open
Opened Jan 23, 2020 by Dave Riedstra@driedstr

Help files that make sound

Many of the help files make sound (eg, the one for [notch]). Some of these make sound as soon as you open them if DSP is on. Some turn on the DSP when loaded which can cause any patch you're working on to make sound. This can result in a very surprising experience with unpleasant side effects like heart attacks or drinks spilled on hardware.

This is probably low priority but it would be nice to have the assurance that opening a help file won't suddenly switch on full-volume noise. This could be accomplished just by replacing [dac~] with [output~] in help patches and removing any logic which engages DSP on init.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: jwilkes/purr-data#575