[DesertDog]

Welcome to ezBEQ
ezBEQ is a program that works in conjunction with mindsp-rs to load BEQs into a miniDSP 2x4HD or a Monolith HTP-1.

Getting started Guide by @JoeNealIND

The guide has instructions for setting it up both on a Raspberry Pi (RPi) or a Windows box. Setting it up on a Mac or a Linux box is the same process as the RPI except for using the appropriate package manager for the platform. Using an RPi is the preferred method. Running it on Windows isn't as straightforward and has some potential issues that you may run into.

Upgrading
To upgrade a Windows install please see the Documentation.

To update a Raspberry Pi do the following command on the command line:
pi> sudo systemctl stop ezbeq.service
pi> cd ~/python
pi> rm -Rf ezbeq
pi> python3 -m venv ezbeq
pi> cd ezbeq/
pi> . bin/activate
pi> pip install -U ezbeq
pi> sudo systemctl start ezbeq.service

 

[DesertDog]

Raspberry Pi (RPi)

Adding an RPi to your system for ezBEQ is easy to do. Unless you're already familiar with them I suggest buying one of the all-in-one kits. They're have everything you need in it and are about the same price as if you bought all the parts separately. I've used both of the kits below and would recommend them. Their SD card also comes with NOOBS pre-installed which makes setup a breeze.

Canakit RPi 4 4G
Canakit RPi 3 B+

Between the two kits I'd lean towards the RPi 4 one. At time of writing it's $100 vs $80 and I've been a 10% coupon on Amazon multiple times for it. For that price difference I'd go for the newer model that's faster and has more ram.

 

[DesertDog]

Temp. Unavailable
In addition to the web interface that ezBEQ comes with mobile apps are being worked on as a front end to the server. Currently there's a beta build available for the iPhone and iPad. Follow the link below to sign up for it on TestFlight.

 

[DesertDog]

reserved

 

[DesertDog]

reserved

 

[Musty Hustla]

I'll ask a Q. I know that ezBEQ applies filters on the input side, but the output settings (compressor, gain, delay, PEQ) aren't included.

Can I get some guidance on how I can apply config XMLs to the output side using ezBEQ or minidsp-RS?

 

[MOberhardt]

I'll ask a Q. I know that ezBEQ applies filters on the input side, but the output settings (compressor, gain, delay, PEQ) aren't included.

Can I get some guidance on how I can apply config XMLs to the output side using ezBEQ or minidsp-RS?

You don't. You have to use the minidsp plugin that you get with the minidsp.

But it is a one and done now.

Possibly setting outputs may get added to minidsp-rs. I can't say.

 

[Musty Hustla]

You don't. You have to use the minidsp plugin that you get with the minidsp.

If I use the plugin app and add PEQ on the output side for my subs, do those get removed if I use ezBEQ?

 

[JoeNealIND]

If I use the plugin app and add PEQ on the output side for my subs, do those get removed if I use ezBEQ?

No, ezbeq will not overwrite any outputs.
However, if you use ezbeq to write your input configs, and THEN open the official plugin app, it will overwrite the inputs.

 

[JoeNealIND]

I have written an installation guide for minidsp-rs + ezbeq. Any suggestions on where to store it? I assume uploading it here isn't the best idea. I don't really want to share it out of my google drive.

 

[tbass2k]

I have written an installation guide for minidsp-rs + ezbeq. Any suggestions on where to store it? I assume uploading it here isn't the best idea. I don't really want to share it out of my google drive.

How big is it? You can share securely with Dropbox also.

 

[JoeNealIND]

How big is it? You can share securely with Dropbox also.

6 MB (has screenshots in it, etc).

 

[tbass2k]

6 MB (has screenshots in it, etc).

I suggest Dropbox then. Thanks for your work.

 

[giomania]

I have written an installation guide for minidsp-rs + ezbeq. Any suggestions on where to store it? I assume uploading it here isn't the best idea. I don't really want to share it out of my google drive.

Is there something wrong with Google Drive that I don’t know about? Because I use it for all the stuff I write up.

Thanks.

Mark


Sent from my iPad using Tapatalk Pro

 

[MOberhardt]

I have written an installation guide for minidsp-rs + ezbeq. Any suggestions on where to store it? I assume uploading it here isn't the best idea. I don't really want to share it out of my google drive.

Can it be converted / exported to HTML? When can just probalby add it as a page somewhere - like in the beqcatalog repo wiki?

 

[JoeNealIND]

Can it be converted / exported to HTML? When can just probalby add it as a page somewhere - like in the beqcatalog repo wiki?

Theoretically... not sure how good Word's export is now a days. I could potentially rewrite to basic HTML as well, or in wiki format.

 

[MOberhardt]

Theoretically... not sure how good Word's export is now a days. I could potentially rewrite to basic HTML as well, or in wiki format.

Web page is so much easier. Dealing with documents is a bit archaic, and something targeted at printing, to paper, which isn't what the guide is needed for.

 

[Musty Hustla]

I performed the latest update and now I have the following error:

Feb 06 10:55:56 raspberrypi systemd[1]: Started ezbeq.
Feb 06 10:55:56 raspberrypi ezbeq[1112]: Loading config from /home/pi/.ezbeq/ezbeq.yml
Feb 06 10:55:56 raspberrypi ezbeq[1112]: Traceback (most recent call last):
Feb 06 10:55:56 raspberrypi ezbeq[1112]:   File "/home/pi/python/ezbeq/bin/ezbeq", line 6, in <module>
Feb 06 10:55:56 raspberrypi ezbeq[1112]:     from ezbeq.app import main
Feb 06 10:55:56 raspberrypi ezbeq[1112]:   File "/home/pi/python/ezbeq/lib/python3.7/site-packages/ezbeq/app.py", line 26, in <module>
Feb 06 10:55:56 raspberrypi ezbeq[1112]:     'device_bridge': DeviceBridge(cfg),
Feb 06 10:55:56 raspberrypi ezbeq[1112]:   File "/home/pi/python/ezbeq/lib/python3.7/site-packages/ezbeq/device.py", line 145, in __init__
Feb 06 10:55:56 raspberrypi ezbeq[1112]:     raise ValueError('Must have minidsp or HTP1 in confi')
Feb 06 10:55:56 raspberrypi ezbeq[1112]: ValueError: Must have minidsp or HTP1 in confi
Feb 06 10:55:56 raspberrypi systemd[1]: ezbeq.service: Main process exited, code=exited, status=1/FAILURE
Feb 06 10:55:56 raspberrypi systemd[1]: ezbeq.service: Failed with result 'exit-code'.

 

[JoeNealIND]

Web page is so much easier. Dealing with documents is a bit archaic, and something targeted at printing, to paper, which isn't what the guide is needed for.

Agreed. Should be posted shortly!

 

[JoeNealIND]

I performed the latest update and now I have the following error:

Feb 06 10:55:56 raspberrypi systemd[1]: Started ezbeq.
Feb 06 10:55:56 raspberrypi ezbeq[1112]: Loading config from /home/pi/.ezbeq/ezbeq.yml
Feb 06 10:55:56 raspberrypi ezbeq[1112]: Traceback (most recent call last):
Feb 06 10:55:56 raspberrypi ezbeq[1112]:   File "/home/pi/python/ezbeq/bin/ezbeq", line 6, in <module>
Feb 06 10:55:56 raspberrypi ezbeq[1112]:     from ezbeq.app import main
Feb 06 10:55:56 raspberrypi ezbeq[1112]:   File "/home/pi/python/ezbeq/lib/python3.7/site-packages/ezbeq/app.py", line 26, in <module>
Feb 06 10:55:56 raspberrypi ezbeq[1112]:     'device_bridge': DeviceBridge(cfg),
Feb 06 10:55:56 raspberrypi ezbeq[1112]:   File "/home/pi/python/ezbeq/lib/python3.7/site-packages/ezbeq/device.py", line 145, in __init__
Feb 06 10:55:56 raspberrypi ezbeq[1112]:     raise ValueError('Must have minidsp or HTP1 in confi')
Feb 06 10:55:56 raspberrypi ezbeq[1112]: ValueError: Must have minidsp or HTP1 in confi
Feb 06 10:55:56 raspberrypi systemd[1]: ezbeq.service: Main process exited, code=exited, status=1/FAILURE
Feb 06 10:55:56 raspberrypi systemd[1]: ezbeq.service: Failed with result 'exit-code'.

Work around.... add "minidspExe: minidsp" to the config file in /home/pi/.ezbeq/ezbeq.yml.

It appears that needs to be defined now, or it fails. I'm not sure if that's the expected behavior or not (but was added when supporting the HTP-1).