Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Making network auto activate doesn't work #38

Closed
swesterfeld opened this issue Mar 15, 2018 · 0 comments
Closed

Making network auto activate doesn't work #38

swesterfeld opened this issue Mar 15, 2018 · 0 comments
Labels
🐛 Bug 💔 Regression

Comments

@swesterfeld
Copy link
Collaborator

@swesterfeld swesterfeld commented Mar 15, 2018

To get an out activate network in BEAST, I do the following steps:

  • project - add custom synthesizer
  • add Standard OSC
  • add PCM Output
  • connect output of Standard OSC to PCM Output
  • go to properties and check auto activate
  • hit play

expected: sawish sound on my speakers
actual result: no sound

@swesterfeld swesterfeld added 🐛 Bug 💔 Regression labels Aug 14, 2018
tim-janik added a commit that referenced this issue Aug 20, 2018
* aida-getset-identifier:
  BEAST-GTK: bstparam: convert pspec name to C++ identifier for aida_set/get and notify
  BSE: bsesong: fix missing notification for SongImpl::musical_tuning
  BSE: bsestorage: issue a warning if aida_set fails
  BSE: bsesnet: add missing "auto_activate" notification
  BEAST-GTK: bstparam: issue a warning if aida_get/aida_set fail
  BSE: bseobject: allow '_' as event detail
  BSE: bseobject: use typesafe {un}set_flag() method instead of BSE_OBJECT_*FLAGS()

Signed-off-by: Tim Janik <timj@gnu.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug 💔 Regression
Projects
None yet
Development

No branches or pull requests

1 participant