dB Value issue

[oleamundsen]

Hi!

Happy with the module. Have just encountered one problem I can't resolve.

I have set the full parameter value which controls gain in channel 3 of an Automixer in Audio Architect. When I try to control the gain fader it refuses to go below 0.00dB. Same with the feedback. Above 0.00dB all works fine.

Is there something Im missing?

[oleamundsen]

Hi again.

After some troubleshooting it seems this issue is only present when converting tcp to rs232. We have an old "atop se5002" which allow us to use then com-port in our blu-160. When reading the HARMAN blu-160 manual it states that ethernet and rs232 should behave the same.

Could it be the se5002 converter? Or some settings I've missed?

[AndyFug]

Hi. Apologies I have only just seen this. I have been away on holidays etc. Is this still an issue?

Unfortunately this may be hard for me to reproduce because I don't think I have a serial adaptor. It would be great if you can reproduce it over TCP.

It does sound a little odd. Can you send screenshots of your settings on the button action/feedback in Companion?

[oleamundsen]

No worries. The issue persists. I'm almost certain that the serial adapter is the problem - although I do not know why. Just tried it on a blu-80 in a test-lab and it refuses to go below 0dB. When using the module over TCP it works fine. Even tried sending HEX with the generic TCP/UDP module and it works fine too.. I'm baffled..

[AndyFug]

Thanks for the feedback.

Few questions:

1. So when you send hex with the generic TCP/UDP module via your serial adaptor it works fine and can set the value below 0dB?
2. Is it the same behaviour when setting the value with an 'absolute' rather than 'relative' value. Ie. Can you set an absolute value of -1dB?
3. Is it the same behaviour when setting with percent and raw units?
4. Is it the same behaviour when using a normal Gain object and using the "Gain N-Input:Gain" action?

So I can dig into this a bit more, can you open the module logging page with debug messages enabled and send across the logs under two scenarios:

1. When trying to set below 0dB via the serial adaptor
2. When trying to set below 0dB directly via TCP.

Make sure you are using exactly the same action config etc and same context/starting position on the fader.

[oleamundsen]

1. No. I've tried sending HEX via USB-RS232 and that works fine. Sending HEX via the serial adapter (se5002) does not work. Using the generic TCP/UDP module.

2. I've tried a bunch of different combinations but it responds very unstable. When using Absolute and RAW it can suddenly fall way below 0dB, but not consistently. It's like the value differs from each button click.

3. Like above - it behaves unstable. When I try different combinations it mostly don't act. And when clicking in frustration it suddenly generates a (random(?)) value.

4. Yes, same behavior when using the "Gain N-Input:Gain" action via the serial adapter.

Via serial:

Via TCP:

It's quite obvious that its the serial adapter that's the problem, but I dont know the reason. The com-port settings matches the blu-80 and all other functions seems to work. Just not to juggle the damn dB below 0. Its perplexing!

Appreciate you taking your time to troubleshoot this!

[AndyFug]

Thanks for the above... I think your response to point 1 definitely suggests this is an issue with your adaptor (like you say).

The Companion logs you've sent aren't the ones I meant (sorry.. I probably should have been more precise). The module/connection logs are found under the connections list as shown here:

They will hopefully show us the raw hex that the module is sending and receiving. It may shed some light on what the adaptor is doing.

I had a look online at the SE5002. There are quite a few settings to configure that may need careful consideration to make sure they are compatible with the device. Can you send across a screen grab of the settings... I'm no expert on serial adaptors, but something may jump out. Do you have 'flow control' (Xon/Xoff etc) switched off?

[oleamundsen]

VIAETHERNET-dB_blu-80:

VIASERIAL-dB_blu-160:

VIASERIAL+dB_blu-160:

I only used the BSS-module in companion in the pictures above. Due to network constrictions I didn't have time to test with HEX today.

[AndyFug]

Apologies for the slow response... It's been a busy couple of weeks. Thanks for the screen grabs.

So this definitely suggests that it is something to do with the serial adaptor. (Assuming everything else is the same... the type of object you are controlling, the serial settings on the BLU-80 and BLU-160 etc).

It appears to be a function of trying to set a negative number, which suggests it may be a hex value that your serial adaptor is replacing when it sees it. Negative numbers are represented using twos complement, which, from memory, I think will result in quite a few 0xFF values. Like I mentioned before, it would be interesting to review your settings on the serial adaptor (SE50002).

Based on the evidence above (Particularly that negative values sent using the generic TCP/UDP module via this particular serial adaptor also exhibit the same symptoms), I think we should close this as an issue with the Soundweb Companion module. Would you agree?

Happy to continue the discussion because it may be helpful to others if we find a solution.

[oleamundsen]

No problem. And thanks for clearing things up. Close the issue as I feel we got a solid conclusion.

Tanks again!