[GH-ISSUE #47] Galactic2 outputs extremely hot signal in BespokeSynth #38

New issue

Open

opened 2026-05-05 22:02:54 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 22:02:54 -06:00

Owner

Originally created by @maxigaz on GitHub (Nov 28, 2023).
Original GitHub issue: https://github.com/airwindows/airwindows/issues/47

In certain Bespoke sessions, Galactic2 produces extremely loud audio. When it is connected to an output (directly or through a signal chain), Bespoke automatically detects clipping and so it mutes the output (most likely for safety reasons). If I connect it to Safety Limiter from nih-plug, Bespoke crashes.

I'm not sure what triggers this behaviour, but I can reproduce it with the precompiled Linux VST binary of Galactic2 and Bespoke Nightly, in Bespoke's example patch called example__arpeggiation.bsk. (For me, this is found in ~/Documents/BespokeSynth/savestate/example__arpeggiation.bsk on Linux, but you can also download it from here.)

When the patch is loaded, add Galactic2 and try dragging its cable at the bottom. For me, the cable becomes red all the time, which indicates the hot signal.

Originally created by @maxigaz on GitHub (Nov 28, 2023). Original GitHub issue: https://github.com/airwindows/airwindows/issues/47 In certain Bespoke sessions, Galactic2 produces extremely loud audio. When it is connected to an output (directly or through a signal chain), Bespoke automatically detects clipping and so it mutes the output (most likely for safety reasons). If I connect it to Safety Limiter from [nih-plug](https://github.com/robbert-vdh/nih-plug), Bespoke crashes. I'm not sure what triggers this behaviour, but I can reproduce it with the [precompiled Linux VST binary](https://www.airwindows.com/wp-content/uploads/LinuxVSTs.zip) of Galactic2 and Bespoke Nightly, in Bespoke's example patch called `example__arpeggiation.bsk`. (For me, this is found in `~/Documents/BespokeSynth/savestate/example__arpeggiation.bsk` on Linux, but you can also download it from [here](https://github.com/BespokeSynth/BespokeSynth/raw/main/resource/userdata_original/savestate/example__arpeggiation.bsk).) When the patch is loaded, add Galactic2 and try dragging its cable at the bottom. For me, the cable becomes red all the time, which indicates the hot signal.

gitea-mirror commented

2026-05-05 22:02:57 -06:00

Author

Owner

@baconpaul commented on GitHub (Oct 2, 2024):

@airwindows - we tracked this down to uninitialized memory in Galactic2.

@Xenakios reports that if you set the init line to this

iirA = iirB = iirC = iirD = iirE = iirF = iirG = iirH = 0.0;

theres no problem. (right now you do E - H).

Can you sweep this init fix when you next add an effect and then the update will catch it? I don't want to have to patch you when I build consolidated of course. And since you have a compile and build path with a few copies I'm not sure how to best send you a PR (although I could).

@baconpaul commented on GitHub (Oct 2, 2024): @airwindows - we tracked this down to uninitialized memory in Galactic2. @Xenakios reports that if you set the init line to this ``` iirA = iirB = iirC = iirD = iirE = iirF = iirG = iirH = 0.0; ``` theres no problem. (right now you do E - H). Can you sweep this init fix when you next add an effect and then the update will catch it? I don't want to have to patch you when I build consolidated of course. And since you have a compile and build path with a few copies I'm not sure how to best send you a PR (although I could).

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/airwindows#38

No description provided.

Rows
Columns