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

More of a question: Seeing a large (6-9dB) difference in low frequency gain on the inputs between v3.8h and v3.8a #106

Open
exitrip opened this issue Apr 12, 2024 · 3 comments

Comments

@exitrip
Copy link

exitrip commented Apr 12, 2024

Our supercollider patch is a whole lot more sensitive to our pickup on v3.8a (PGA set to +5dB) than the exact same deployment on v3.8g/h (Input Gain at +10dB).

I haven't done a full frequency test, but it's very noticeable sub 400Hz. What changed? I'd like to stay up to date, but my client definitely can't afford the debugging.

Any leads would be helpful. What can I use en lieu of alsamixer/ctrl to inspect lower level driver settings?

@giuliomoro
Copy link
Contributor

Did you try both versions on the exact same Bela cape? I.e.: is it a software or hardware difference?

@exitrip
Copy link
Author

exitrip commented Apr 13, 2024

I did A/B testing swapping SD-Cards between two different Bela Mini's in the exact same hardware and multiple re-installations. The issue was first noticed "following the SD CARD" and the only thing I can trace it to is image version.

@giuliomoro
Copy link
Contributor

giuliomoro commented May 2, 2024

thing is image version doesn't really mean anything in terms of supercollider version. Each image will come with a default supercollider version, but that can be upgraded at any time later when updating the Bela core code. What may be happening is that the input gain handling in the Bela core code has been updated at the end of 2021, and Sc hasn't been updated to follow it and isn't working as expected.
I think if you create a file /root/.bela/belaconfig on the board and place this line in it: CL=--verbose , this may add (a lot) of debugging prints when scsynth starts, which may help narrowing down the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants