Signalizer: Sidechaining update! Open-source & free audio visualization plugin (v. 0.4.3)

[Mundano]

When you say grid, do you mean like what you have for the spectrum (just flipped axis)? I can add the hover tool for static x,y information but it's a bit more complex to add peak detection for every 2d position in the spectrogram - it's a lot of information that is already offloaded to the GPU.

Yes like in the spectrum, but axis would stay as in the Spectrogram already. The frecuency tracker would act only on the graphic, not on real audio signal thus spectrum pictures are already past signal representations. Like in Sonic Visualiser from Queen Mary University London. But on the graphic flow or in the freeze mode, if possible. For GPU overload maybe take a look at the Sonic Visualiser code as a reference? (In Sonic Visualiser you can play the file and hover with mouse at the same time)
https://github.com/sonic-visualiser/

GIF-SonicVisualiser.gif

It would be trivial to select the starting decade, eg. 100 Hz / 10 Hz / 1 Hz / 0.1 Hz if that's what you're looking for. The upper bound is given by half of the sampling rate of the host program.

1.00 Hz would be great for whales! (for sismic explorations 0.01 Hz are currently useful)

Magnifying glass - you imagine that as something local besides the normal zoom utilities?

Something like drawing a box and having it magnified.

The spectrogram does have a primitive frequency grid on the left side by the gradient if you give the grid a colour - I think it's off by default.

Got it, thank you! Would be nice to have the time (min.,sec.) on the x axis below for measurements.

I did get your e-mail btw, I just cannot always make timeline responses but I usually never forget! (otherwise, shoot me down on multiple forums )

Thank you for your efforts! Am not the guy coding all of this... I understand everybody is working hard and time is sparse

And last observation, in Reaper I can't change window size without losing the left menu icons near spectrum tab (full screen, info, freeze). Don't know if it is Reaper thing or other DAWs behave the same?
An idea would be to swap tabs if desired, like having spectrum tab first and vectorscope tab last. Would work like having tab swaped in any internet browser....

Thank you again Janus and keep the excellent work!

[Granata]

No problem! I'll look into the reaper thing. The spectrum has a cursor tracker, try the options in the dropdown on the first settings page called "Frequency tracker". Or perhaps you meant the spectrogram mode? It's not yet available there.

I assumed I was just too dumb to see it, so I tried harder and found it eventually , that is an overwhelmingly detailed tracker!
Many thanks!

[Granata]

My Reaper problems continue - Since the Reaper 7 update, it's not loading the analyser on startup anymore, only the top menu bar:

Untitled.png

Now I have to reload the Signalizer every time I open Reaper .

[AlQuzMar]

Love this plugin. Love this plugin.
been searching for years for this very thing.

i did run into some things however.

originally downloaded 2.7
spectrum worked like a dream
oscilloscope "no view selected"

downloaded 3.2
spectrum glitching and no longer displaying audio info
oscilloscope works though!

i went through almost every setting i could before coming to say anything.
i turned diagnostics on and only when i was absolutely pushing with refresh did it seem to stress the cpu.

OSX 11
Ableton 10
32gb
3.6 ghz 8 core i7
radeon rx 570 8gb

If you change the waterfall spectogram plot from fft to resonator it starts working for both modes.

[Mayae]

Hello good people!

So the new update is finally here. It really only has one new feature - global sidechaining - which by far was the most requested feature:

https://www.youtube.com/watch?v=TORrFOlvaHQ

It required a rearchitecture that took a few years, but since it’s so tricky and outside of the plugin spec, I took the time to do it well and bash all the bugs reported thus far.

Thank you to everyone who wrote to me over the years, I promise I have recorded all feature suggestions and issues!

If no immediate support release is necessary - next I will need to spend some time upgrading frameworks and the build system to natively support macOS arm, Ubuntu and high DPI on Windows. And then we can do another general feature release.

Here’s the release notes for this version:

Code: Select all

## 0.4.0 - 2023-11-24

### Added

- Graph editor window that can be opened through a new global button in the upper right. From here you can sidechain any Signalizer into another, freely routing channels to at most 16 inputs. This configuration is saved in the project and presets as well.
- All views can now visualize up 8 channel pairs (16 channels in total), colours beyond the first pair are automatically distinct but based on the primary pair
- Signalizer will now utilize more CPU cores when processing more than one stereo pair
- VST3 support and builds on Windows
- Ask to prune the exception log file if it is becoming large
- Option to enable Legends in the views displaying the source name and colour used to draw it
- A control for changing what channel the Oscilloscope triggers on

### Fixed

- Crash in Oscilloscope when running in mono
- Spurious crash in Oscilloscope on startup
- Spurious crash when channel layout changes
- Class of hangs or crashes complaining about "Acquired non-recursed mutex had non-zero ref count!"
- Class of hangs or crashes complaining about "Unsafe writer created, while reader exists!"
- Bug where stereo filters in Vectorscope would not update when "Peak" mode was selected for envelopes
- Bug where vector scope channels would go out of sync and looks noisy
- Bug where graphical glitches would happen when switching to spectrogram mode
- Decay rate in the spectrogram that was incorrectly affected by the frame rate
- Issue where discontinuities would be present in the spectrogram under heavy usage
- Issue with latency in the spectrogram when frame smoothing was enabled
- Issue where the spectrum would produce a slightly out of data view
- Flicker when reducing the window size in the spectrum
- Graphical issue when the Spectrum has a dB range of zero (there's now a small minimum enforced)
- Graphical stutter or lag in hosts on Windows 10 and 11
- Issue where wireframe in the vectorscope would be rendered with jagged lines

### Changed

- Polar mode in Vectorscope fills the whole screen instead of being incorrectly scaled (going forward)
- Optimized wireframe drawing code
- Further optimized Vectorscope DSP code 
- Constant angular resolution for arcs
- Spectrum is now computed in 32-bit instead of 64-bit
- All frequency domain math is now considerably faster
- Dramatically reduced drawcalls using batching instead, vastly improving performance and responsiveness especially on less capable hardware
- Ultimately hide tabs after 7 seconds, hiding a problem where they would not auto-hide anyway
- Reduced scale of scrolling when altering gain in multichannel viewing mode of the Oscilloscope
- Improved treshold offset for trigger detection in spectral mode when analysing harmonic but sinusoidal signals

Thanks & best regards,
Janus

[Kott]

Hi,

what build system are you planing to use in Linux, the same Code::Blocks?

[lolilol1975]

My Reaper problems continue - Since the Reaper 7 update, it's not loading the analyser on startup anymore, only the top menu bar:
Untitled.png
Now I have to reload the Signalizer every time I open Reaper .

Same under Reaper 6.89, and random crash too (v0.4.1)

[Mayae]

Hi,

what build system are you planing to use in Linux, the same Code::Blocks?

Hello. I plan to migrate to cmake instead, so I'm no longer responsible for maintaining terrible build scripts and broken projects

My Reaper problems continue - Since the Reaper 7 update, it's not loading the analyser on startup anymore, only the top menu bar:
Untitled.png
Now I have to reload the Signalizer every time I open Reaper .

Same under Reaper 6.89, and random crash too (v0.4.1)

Odd, I just verified with the newest build of Reaper and I'm not seeing any issues. Is this on Windows or macOS?

If you get any crashes, I would appreciate if I could get the "Signalizer exceptions.log" file that should be produced next to the plugin file. In macOS, you need to open the bundle by right clicking and finding the "Resources" subfolder.

[Granata]

Hi,

what build system are you planing to use in Linux, the same Code::Blocks?

Hello. I plan to migrate to cmake instead, so I'm no longer responsible for maintaining terrible build scripts and broken projects

My Reaper problems continue - Since the Reaper 7 update, it's not loading the analyser on startup anymore, only the top menu bar:
Untitled.png
Now I have to reload the Signalizer every time I open Reaper .

Same under Reaper 6.89, and random crash too (v0.4.1)

Odd, I just verified with the newest build of Reaper and I'm not seeing any issues. Is this on Windows or macOS?

For me it's not happening every time, haven't had it lately... but I should also add that more and more plugins are having grapgics issues in Reaper,maybe something to do with its OpenGL support. For example, the last time I tried iZotope's Insight, it was unusable.
The window size reseting issue still persists, but I have experienced the same with another analyzer I tried recently (forgot the name).

The new Signalizer is a huge improvement in many aspects, however, it's now next to impossible to set the colors. Due to old presets not working in the new version, I had to copy and paste each color value, and for some elements like Vectorscope axis and grid, it just doesn't work.

I had one crash while editing colors:

----------------26/11/2023, 20:20:3----------------
- Exception in "Signalizer" v."0.4.0"
Runtime exception (cpl::CPLAssertionException) in Signalizer (0.4.0): "Runtime assertion failed: command.stream.get() != self->source.lock().get()" in C:\Code\Signalizer\Source\Common\MixGraphListener.cpp:506 -> Signalizer::MixGraphListener::updateTopologyCommands

----------------26/11/2023, 21:26:14----------------
- Exception in "Signalizer" v."0.4.0"
Handler: Main window procedure
- SEH exception description:
Non-software exception at 0x0000000000000000 (at image base 0x00007FFEF9190000 - 0x00007FFEF9190000)
Exception code: 0, actual code: 7ff8, extra info: 57d1c53f
Formatted message: Unknown exception (BAD!).
- Stack backtrace:
0x00007FFEF9190000 + 0x00000000003B6F30 + 0x17960 | VSTPluginMain
0x00007FFEF9190000 + 0x00000000002022F7
0x00007FFEF9190000 + 0x0000000000202A7E
0x00007FFEF9190000 + 0x0000000000216DAB
0x00007FFEF9190000 + 0x000000000013D417
0x00007FFEF9190000 + 0x000000000013D00C
0x00007FFEF9190000 + 0x000000000013F360
0x00007FFEF9190000 + 0x0000000000149C88
0x00007FFEF9190000 + 0x0000000000149BFE
0x00007FFEF9190000 + 0x000000000013F184
0x00007FFEF9190000 - 0x00000006A2AAA7A0 + 0x3bd | CallWindowProcW
0x00007FFEF9190000 - 0x00000006A2AAABE0 + 0x3cc | DispatchMessageW
0x00007FFEF9190000 - 0x00000006A2A9E220 + 0x1a3 | IsWindowVisible
0x00007FFEF9190000 - 0x00000006A13EF410 + 0x24 | KiUserCallbackDispatcher
0x00007FFEF9190000 - 0x00000006A434E8B0 + 0x14 | NtUserDispatchMessage
0x00007FFEF9190000 - 0x00000006A2AAABE0 + 0x2dc | DispatchMessageW
0x00007FFEF9190000 - 0x00007FFDB8CFDC00
0x00007FFEF9190000 - 0x00007FFDB8736B6F
0x00007FFEF9190000 - 0x00000006A17083F0 + 0x14 | BaseThreadInitThunk
0x00007FFEF9190000 - 0x00000006A1422900 + 0x21 | RtlUserThreadStart


----------------26/11/2023, 21:32:59----------------
- Exception in "Signalizer" v."0.4.0"
Handler: Main window procedure
- SEH exception description:
Non-software exception at 0x0000000000000000 (at image base 0x00007FFEF9340000 - 0x00007FFEF9340000)
Exception code: 0, actual code: 7ff8, extra info: 57d1c53f
Formatted message: Unknown exception (BAD!).
- Stack backtrace:
0x00007FFEF9340000 + 0x00000000003B6F30 + 0x17960 | VSTPluginMain
0x00007FFEF9340000 + 0x00000000002022F7
0x00007FFEF9340000 + 0x0000000000202A7E
0x00007FFEF9340000 + 0x0000000000216DAB
0x00007FFEF9340000 + 0x000000000013D417
0x00007FFEF9340000 + 0x000000000013D00C
0x00007FFEF9340000 + 0x000000000013F360
0x00007FFEF9340000 + 0x0000000000149C88
0x00007FFEF9340000 + 0x0000000000149BFE
0x00007FFEF9340000 + 0x000000000013F184
0x00007FFEF9340000 - 0x00000006A2C5A7A0 + 0x3bd | CallWindowProcW
0x00007FFEF9340000 - 0x00000006A2C5ABE0 + 0x3cc | DispatchMessageW
0x00007FFEF9340000 - 0x00000006A2C4E220 + 0x1a3 | IsWindowVisible
0x00007FFEF9340000 - 0x00000006A159F410 + 0x24 | KiUserCallbackDispatcher
0x00007FFEF9340000 - 0x00000006A44FE8B0 + 0x14 | NtUserDispatchMessage
0x00007FFEF9340000 - 0x00000006A2C5ABE0 + 0x2dc | DispatchMessageW
0x00007FFEF9340000 - 0x00007FFDB8EADC00
0x00007FFEF9340000 - 0x00007FFDB88E6B6F
0x00007FFEF9340000 - 0x00000006A18B83F0 + 0x14 | BaseThreadInitThunk
0x00007FFEF9340000 - 0x00000006A15D2900 + 0x21 | RtlUserThreadStart

[Mayae]

e2: I might as well chuck this in here - I released a small new update specifically because it can bring projects with old versions of Signalizers into an annoying state (not damaging or irreparable)

Code: Select all

## 0.4.1 - 2023-11-26

### Fixed

- Issue where loading old Signalizer presets (or opening old projects) would not connect the input to the output in the graph editor
- Crash when sustaining Signalizer on a non-playing track in the Oscilloscope when loading an old preset or project

The window size reseting issue still persists, but I have experienced the same with another analyzer I tried recently (forgot the name).

This resetting, does it still happen even when only dragging within Signalizer (and not using Reaper's window resize)?

Due to old presets not working in the new version

This is surprising to hear, because I spent quite a lot of time on backwards compatibility. What sort of issues are you seeing? (e: I should add I already released an update (0.4.1) that fixes one particular issue with old presets, see above)

I had to copy and paste each color value, and for some elements like Vectorscope axis and grid, it just doesn't work.

How do you copy/paste - the colour hex value? What do you mean when you say it doesn't work?

I had one crash...

Thanks, that one is new. Will investigate. While editing colours, that's really odd. Crash location has nothing to do with that.

[Granata]

This resetting, does it still happen even when only dragging within Signalizer (and not using Reaper's window resize)?

I can only drag the Signalizer's window since it is not expanding with the Reaper's window beyond 1080 px height, and that is the height it keeps resetting to.

This is surprising to hear, because I spent quite a lot of time on backwards compatibility. What sort of issues are you seeing? (e: I should add I already released an update (0.4.1) that fixes one particular issue with old presets, see above)

I should clarify - I can't load the old presets, the new Signalizer doesn't see them.

EDIT: I found that I can load the old default preset, so if saved as default, presets are indeed compatible .

How do you copy/paste - the colour hex value? What do you mean when you say it doesn't work?

Yes, the hex values.
For some elements like the vectorscope axis even when I paste the hex value, the element gets a completely different color.
In addition to color selector being oversensitive, the wheel and color selection behaves inconsistently depending on whether I drag within the knob or the colored rectangle next to it, or when I use the scrollwheel.

While editing colours, that's really odd. Crash location has nothing to do with that.

Nothing would surprize me, weird things happen in my DAW.

[Mayae]

I can only drag the Signalizer's window since it is not expanding with the Reaper's window beyond 1080 px height, and that is the height it keeps resetting to.

So to confirm, you're unable to resize the window like I'm doing here?

https://www.youtube.com/watch?v=NylsOxe5UqU

EDIT: I found that I can load the old default preset, so if saved as default, presets are indeed compatible .

What about in general? It only works for the old default, or will any work?

For some elements like the vectorscope axis even when I paste the hex value, the element gets a completely different color.

Are you able to select the correct colour within the expanded colour control?

Nothing would surprize me, weird things happen in my DAW.

Since you're so good at making odd crashes, can I convince you to run with the debug version that's also found in the .zip instead? It adds more context for me. I can only account for 1 of your 3 crashes with the log.

[Granata]

So to confirm, you're unable to resize the window like I'm doing here?

https://www.youtube.com/watch?v=NylsOxe5UqU

That is how I'm resizing, but I am able to resize it. The problem is that it resets back when I leave the window or switch to another plugin.
And this is happening in the docker where my monitor fx channel is, so the Reaper's window is not changing sizes when switching plugins in the chain like it would in an undocked fx chain window (in case it matters).
My Screen has 1440px height. Signalizer window always returns to 1025px height according to diagnostics (I guess 1080 minus the Reaper window's top bar).

EDIT: I found that I can load the old default preset, so if saved as default, presets are indeed compatible .

What about in general? It only works for the old default, or will any work?

Like I said, when I try to load presets, it only sees the default one, I can't load other old presets as they are not shown.
I also noticed that the old preset does not set exactly the same colors, some are slightly off.

Are you able to select the correct colour within the expanded colour control?

I don't know what the expanded colour control is, but I'm not able to dial in the exact color, and for the said axis, even the selected color appears different.

To me it seems that when I drag within the colored rectangle next to the knob, it shifts the hue, when I drag the knob, it goes through very short cycles of hues while going from darker to brighter (apparently no grays). If I use mouse-wheel to move the knob clockwise it shifts briteness of full blue hue from black to white, but when I scroll back counter-clockwise it switches to some tan hue, and then after I reach the end and scroll back clockwise it goes blue again and so on...
That's very weird behaviour.

Since you're so good at making odd crashes, can I convince you to run with the debug version that's also found in the .zip instead? It adds more context for me. I can only account for 1 of your 3 crashes with the log.

Well, I didn't have any Signalizer crashes since then, so I doubt it would be useful unless I would do some active testing. I'm also done with customizing where I already spent a lot of time.
I did however get this error few times while dialing colors, although I think it might not be the Signalizer issue:

Screenshot 2023-11-28 035522.png

EDIT: I got this crash again when starting Reaper:

----------------28/11/2023, 19:55:57----------------
- Exception in "Signalizer" v."0.4.0"
Handler: Main window procedure
- SEH exception description:
Non-software exception at 0x0000000000000000 (at image base 0x00007FFB802F0000 - 0x00007FFB802F0000)
Exception code: 0, actual code: 7ffc, extra info: dbc7c53f
Formatted message: Unknown exception (BAD!).
- Stack backtrace:
0x00007FFB802F0000 + 0x00000000003B6F30 + 0x17960 | VSTPluginMain
0x00007FFB802F0000 + 0x00000000002022F7
0x00007FFB802F0000 + 0x0000000000202A7E
0x00007FFB802F0000 + 0x0000000000216DAB
0x00007FFB802F0000 + 0x000000000013D417
0x00007FFB802F0000 + 0x000000000013D00C
0x00007FFB802F0000 + 0x000000000013F360
0x00007FFB802F0000 + 0x0000000000149C88
0x00007FFB802F0000 + 0x0000000000149BFE
0x00007FFB802F0000 + 0x000000000013F184
0x00007FFB802F0000 + 0x0000000159A35860 + 0x3bd | CallWindowProcW
0x00007FFB802F0000 + 0x0000000159A35420 + 0x3cc | DispatchMessageW
0x00007FFB802F0000 + 0x0000000159A41DE0 + 0x1a3 | IsWindowVisible
0x00007FFB802F0000 + 0x000000015BA10BF0 + 0x24 | KiUserCallbackDispatcher
0x00007FFB802F0000 + 0x00000001588E1750 + 0x14 | NtUserDispatchMessage
0x00007FFB802F0000 + 0x0000000159A35420 + 0x2dc | DispatchMessageW
0x00007FFB802F0000 - 0x00007FFA3FE5DC00
0x00007FFB802F0000 - 0x00007FFA3F896B6F
0x00007FFB802F0000 + 0x000000015B7B7C10 + 0x14 | BaseThreadInitThunk
0x00007FFB802F0000 + 0x000000015B9DD700 + 0x21 | RtlUserThreadStart

Works normally when I load a new project.

[jamcat]

Looking forward to trying Signalizer out once it's Apple Silicon native.

[Kott]

Hi,

what build system are you planing to use in Linux, the same Code::Blocks?

Hello. I plan to migrate to cmake instead, so I'm no longer responsible for maintaining terrible build scripts and broken projects

That's great!