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

BSS London DSP Family #1303

Open
baumannfl opened this issue Nov 6, 2023 · 6 comments
Open

BSS London DSP Family #1303

baumannfl opened this issue Nov 6, 2023 · 6 comments

Comments

@baumannfl
Copy link

BSS London BLU digital sound processors (DSPs) provide a feature-rich environment for processing audio and control in professional AV installations. The BLU DSP is programmed by using the Audio Architect (AA) software. A BLU can also be controlled remotely by sending hex strings to the DSP's IP address on port 1023. Both the audio and the logic sections of the DSP are fully configurable. Thus, there is no simple "switch from A to B" or anything of that kind. Instead, you identify the control that you want to address from the outside, and AA will provide you with the hex string that you must send to the DSP. The format of the string provided by AA is like this: 02,88,00,01,1B,82,00,00,01,00,01,00,00,00,01,8A,03. The existing generic tcp-udp module almost provides the needed functionality. However, it would be ideal if the string from AA could simply be pasted into a Companion button's command field, removing the need to reformat the string before pasting it. There is a PDF issued by Harman that shows a few more details helping the AA programmer understand the message structure. However, understanding the structure is not needed for the creation of the module because the strings are simply copied from AA and pasted into the module.

I have tried to use the generic tcp-udp module and it successfully connects to the BLU-100 that I am using in my test setup. However, I have not managed to send a string successfully.

@baumannfl
Copy link
Author

As an intermediate solution, how must I convert 02,88,00,01,1B,82,00,00,01,00,01,00,00,00,01,8A,03 to have tcp-udp send it successfully to the DSP?

@istnv
Copy link
Member

istnv commented Nov 6, 2023

Add '%' to the beginning and replace all commas ',' with '%'.
The '%' tells the module that the next 2 characters are Hex.

@baumannfl
Copy link
Author

Thanks. I had just discovered that by searching for "companion tcp-udp module" and reading the notes on V1.0.5. The help within Companion doesn't mention any of that.

@istnv
Copy link
Member

istnv commented Nov 6, 2023

It is on the (?) tooltip for the command string.

@baumannfl
Copy link
Author

baumannfl commented Nov 6, 2023 via email

@ethanmatthews
Copy link

Were you able to get the generic tcp module to work? can't seem to get it to work when I tried it and wanted to see if you had any issues getting it to work.

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

3 participants