What are normal env~ values for no audio input?

spDuchamp

I have a simple test patch here that sends the 2 channels of ADC to the DAC and outputs the values of env~ for both channels to the console.

I'm curious what your env~ values hover around with no audio fed into the inputs.

Mine are overing around 19-21 on channel 1 and 22-25 on channel 2. Are these normal values?

2ch-inout-test.zip

2kB

giuliomoro

They seem reasonable values, but it all depends on what you set your gains to.

spDuchamp

OK. Thanks. The reason I'm asking is that I'm trying to figure out why a patch of mine is going a bit crazy.
Everything was working perfectly last week as seen in this video...
When I came in to do work this week, my patch is spewing out values that don't make any sense and I don't understand why it would all just sort of change behaviour. I've checked all my wiring and everything checks out.

Basically, I'm taking the env~ of the six string signals and for now, I'm passing those direct to touchout. Starting this week, it just kept spewing the number 92. I made all sort of addition test patches and was not seeing this same behavior. env~ was just not working properly on my guitar project, but working fine on the other test patches.

Just now I deleted the settings.json file, from my project, and uploaded a setting.json file from one of my test patches and then adjusted the settings. Now the system is behaving more normally, but not quite the same as it was last week.

Here's how it's working now...

pxl-20260716-1715514102.mp4

17MB

This is all getting redone and ported over to a Bela Gem next week, but I still want to keep this original Bela working for dev work. I just need some guidance on why it has gone all whacko and how I might better diagnose the issue.

giuliomoro

spDuchamp Here's how it's working now...

What are we listening to here? An audio output from Bela? Or is it the result of the MIDI being sent to the host?

I'd start by looking at the inputs into Bela on the Bela scope, to see any obvious issues there.

What block size are you using on Bela? Does changing that affect the result? Is there any error message getting printed on Bela?

spDuchamp

That was output from Ableton from the MIDI being send from Bela and chord adjusted along the way in Plugdata.

I managed to get my prototype working again. I had added -npts 256 -hop 32 to my bonk~ (block size 32) and that seemed to maybe cause some of the weird triggering I was getting. I changed back to a previous patch that has plain bonk~ with no extra parameters and I pass it [thresh 4 8 , minvel 20( and all is good with it now.

I dunno what all when on this week, but I'm just deeply relieved that this demo is working again. Now I'm not going to touch it, and work on the next iteration on the new Bela Gem version.

Thanks for the help!