corinfinite / brp-pacu Goto Github PK

The JACK callback should return as fast as possible but there is buffer filling and shuffling that occurs. This should be moved into the main thread or a new thread, along with the other processing tasks.

Averaging on the output trace is done when the GUI updates. If the GUI updates more frequently the trace will appear smoother. If the GUI updates less frequently the trace will appear less well behaved. This is not desirable.

Averaging should be done as part of calculating the auto spectra and cross spectrum. Resolving this will be part of resolving #18

This will make getting started a little easier

This error appears after trying to run the BRP_PACU executable after the initial build (sans "sudo make install"). Running "sudo make install" fixes this, but means that after any UI changes, "sudo make install" must be run.

https://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html

Preparation steps done in 0ed157d and 92f2ae3

Any checked items without a bullet point below them were not used/applicable

• Replace size_request by get_preferred_width/height
• Replace GdkRegion by cairo_region_t
• Replace GdkPixmap by cairo surfaces
• Removed in 92f2ae3
• Removed commented out code involving Pixmaps
• Replace GdkColormap by GdkVisual
• GdkDrawable is gone
• Event filtering
• Backend-specific code
• GtkPlug and GtkSocket
• The GtkWidget::draw signal
• GtkProgressBar orientation
• Check your expand and fill flags
• Scrolling changes
• GtkObject is gone
• Unsure exactly how to resolve, for the time being changing GTK_OBJECT to G_OBJECT
• GtkEntryCompletion signal parameters
• Resize grips
• Prevent mixed linkage
• It may be an issues that the latest gtkdatabox release (0.9.3.0) uses gtk2 and the release suggested in our current readme is 0.9.2.0
• The master branch on the sourceforge repo advertises gtk3 support
• This github repo advertises gtk3 support
• It appears there may be gtk3 versions in newer Ubuntu repositories: https://packages.ubuntu.com/zesty/libgtkdatabox-0.9.3-0-glade
• Further investigation is needed
• Install GTK+ modules in the right place

A while ago I tried to test BRP-PACU on a live system and myself and a colleague observed that the pink noise generator seemed to be lacking in the high end when compared to the pink noise generated by a Yamaha LS-9. The audio interface was a Digidesign MBox2.

Added from TODO

The user must be able to specify what windowing function they wish to be applied to the input audio through the GUI.
The user must have at least two window functions to choose from. Currently Blackman is implemented and Hanning should be added. More functions would be nice.

Added from TODO

Currently sample rate is printed to console, which is of no use to the average users.

Added from TODO

Added from TODO

Added from TODO.

Added from TODO.

Added from TODO. I assume this refers to the message displayed when the program is first run.

Hi, and thanks for adopting BRP-PACU! I've been playing around with it many years ago, and when I wanted to resurrect it this week, I found it still required FFTW2... so I was more than happy to stumble upon your fork! It works very well for me so far. I would love to see a "coherence" graph (I think this is what most dual-FFT tools call it) that indicates how reliable each part of the computed transfer frequency response is based on if those frequencies are actually in the reference signal and how much correlation there is to the measured signal in that bin. At the moment, I frequently see a slight artefact at the HF end, which appears as if it's shelved up by about 10dB above 16k (disappears of course when using pink noise).
Additionally, having a way to display the phase portion of the FFT would be a great aid in tuning crossovers and time-alingning subwoofer stacks.
All the best, and thanks for sharing your work! Jörn