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

[onerob]

What's the minimum OS for Mac? I'm on Catalina and can't run it in either Logic or Meta Plugin.

[Mayae]

What's the minimum OS for Mac? I'm on Catalina and can't run it in either Logic or Meta Plugin.

What seems to be your issue? Does it not show up? Minimum OS X for Signalizer is 10.7 (12 years ago).

The problem is that it resets back when I leave the window or switch to another plugin.

That's strange, of course it works fine here even when resetting/switching/closing etc. I'll have to think about how I can diagnose this.

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.

When you say "the default one", are you talking about this one (from the list of global defaults)?


Or the local ones?



I also noticed that the old preset does not set exactly the same colors, some are slightly off.

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.

If you double-click the knob and click on the triangle, there's a colour tool:

Well, I didn't have any Signalizer crashes since then ... EDIT: I got this crash again when starting Reaper:

Use the debug version please It's the same as the release, it just has symbols in a big file next to it.

[onerob]

What's the minimum OS for Mac? I'm on Catalina and can't run it in either Logic or Meta Plugin.

What seems to be your issue? Does it not show up? Minimum OS X for Signalizer is 10.7 (12 years ago).

I get a message saying that the plugin is damaged and the option to move it to the bin. (AU and VST version).

[Granata]

When you say "the default one", are you talking about this one (from the list of global defaults)?

Or the local ones?

Turns out I've been using this thing wrong. I've been accidentally saving old presets as local and assumed it didn't matter where you load them from, and it worked before due to pure chance.
The UI is however a bit confusing and inconsistent, it's not obvious when you're in global vs local panel, the only difference is the tab with the 'save' icon, but it contains the same functionalities as the 'wrench' tab in local panel.

If you double-click the knob and click on the triangle, there's a colour tool

I could swear I tried that and nothing happened, but now I realized that I probably wasn't clicking precisely on the triangle, I expected that the rectangle around the triangle was the button.
I feel relieved and stupid at the same time .

I will install the debug version.
Thank you so much for taking time!

[_Freeman_]

Hi Mayae,
been using Signalizer for quite some time as my main Analyzer and still find it to be the best one out there... with one drawback though.
Since you've now started to work on it again, I was wondering if you could have a look at the Save/Recall issue as shown here:
https://youtu.be/1NuWKBdHHcg

Signalizer 0.4.1 VST2 x64, Studio One v6.5.1, Win11

[Mayae]

I get a message saying that the plugin is damaged and the option to move it to the bin. (AU and VST version).

Yes, okay, now I've had multiple people reporting this. It's because of the Gatekeeper in newer versions of macOS that specifically bricks anything not downloaded and notarized from the app store - something Apple charges $99/year for.

There are ways around this if you want, I've added more thoughts and links here: https://bitbucket.org/Mayae/signalizer/ ... advice.txt

The UI is however a bit confusing and inconsistent ... it's not obvious when you're in global vs local panel.

I agree, it could use some love.

I will install the debug version.
Thank you so much for taking time!

Thank you for helping out

I was wondering if you could have a look at the Save/Recall issue as shown here

I'm aware of the issue, it bugs me as well. An early choice in how I (re)store presets causes loss of time information leading to issues when sample rate is changed and/or certain DAW behaviours that keep the plugin offline for a while.
Unfortunately it will break old projects / presets to change this, so I'm trying to think of a good way around this instead.

[Mayae]

Oh and before I forget, there's a new version out today - primarily a stability / workflow improvement release, so it comes recommended

Code: Select all

## 0.4.2 - 2023-12-21

### Added

- Further description and tips for dealing with "damaged" plugins that "can't be opened" on newer versions of macOS in the installation advice of the release folder.
- Button in the global settings by the presets to reveal the exception log
- Drop-down menu in the global settings by the presets to control how the sidechaining graph is saved when creating custom presets from within DAWs
- This file into releases

### Fixed

- An assertion when loading a preset through a DAW on a Signalizer that is in an alias state of another (or having become one as a part of loading the preset)
- Recoverability and notification for a situation where the mixgraph completely detaches from itself, previously leading to an assertion about "command.stream.get() != self->source.lock().get()"
- A division by zero under certain channel configurations in specific timing scenarios
- A crash when inserting Signalizer on a mono track in Studio One

As always, downloads are here in the repo: https://bitbucket.org/Mayae/signalizer/downloads/

[Granata]

I updated to the new versioon yesterday, it worked but today I'm getting this error every time I reload it:

Screenshot 2023-12-22 160244.png

I haven't used the 0.4.1, and I think those crashes I had were specific to a project, I haven't had them since. They still happen on that same project with the new version in addition to the error.

Code: Select all

----------------22/12/2023, 15:16:32----------------
- Exception in "Signalizer" v."0.4.2"
Handler: Main window procedure
- SEH exception description: 
Non-software exception at 0x0000000000000000 (at image base 0x00007FFB7F9C0000 - 0x00007FFB7F9C0000)
Exception code: 0, actual code: 7ffc, extra info: b015c53f
Formatted message:  Unknown exception (BAD!).
- Stack backtrace: 
Signalizer: 0x00007FFB7F9C0000 + 0x00000000003D1000 + 0x1f0 | fmod
Signalizer: 0x00007FFB7F9C0000 + 0x0000000000203000 + 0x417 | cpl::rendering::CDisplaySetup::update
Signalizer: 0x00007FFB7F9C0000 + 0x0000000000203B10 + 0x8e | cpl::rendering::CDisplaySetup::instance
Signalizer: 0x00007FFB7F9C0000 + 0x0000000000217E50 + 0x7b | cpl::CLookAndFeel_CPL::createGraphicsContext
Signalizer: 0x00007FFB7F9C0000 + 0x000000000013DF30 + 0x3a7 | juce::HWNDComponentPeer::performPaint
Signalizer: 0x00007FFB7F9C0000 + 0x000000000013DE30 + 0x9c | juce::HWNDComponentPeer::handlePaintMessage
Signalizer: 0x00007FFB7F9C0000 + 0x0000000000140190 + 0x90 | juce::HWNDComponentPeer::peerWindowProc
Signalizer: 0x00007FFB7F9C0000 + 0x000000000014AAD0 + 0x78 | cpl::CProtected::internalCxxTraceInterceptor<<lambda_388c96f69b0c59465ccf375221a2e99f> &>
Signalizer: 0x00007FFB7F9C0000 + 0x000000000014AAB0 + 0xe | cpl::CProtected::internalSEHTraceInterceptor<<lambda_388c96f69b0c59465ccf375221a2e99f> &>
Signalizer: 0x00007FFB7F9C0000 + 0x000000000013FF30 + 0x114 | juce::HWNDComponentPeer::windowProc
0x00007FFB7F9C0000 + 0x000000012EDF5860 + 0x3bd | CallWindowProcW
0x00007FFB7F9C0000 + 0x000000012EDF5420 + 0x3cc | DispatchMessageW
0x00007FFB7F9C0000 + 0x000000012EE01DE0 + 0x1a3 | IsWindowVisible
0x00007FFB7F9C0000 + 0x0000000130820BF0 + 0x24 | KiUserCallbackDispatcher
0x00007FFB7F9C0000 + 0x000000012D851750 + 0x14 | NtUserDispatchMessage
0x00007FFB7F9C0000 + 0x000000012EDF5420 + 0x2dc | DispatchMessageW
0x00007FFB7F9C0000 - 0x00007FFA3F52ACCC
0x00007FFB7F9C0000 - 0x00007FFA3EF5ECCF
0x00007FFB7F9C0000 + 0x000000012F687C10 + 0x14 | BaseThreadInitThunk
0x00007FFB7F9C0000 + 0x00000001307ED700 + 0x21 | RtlUserThreadStart


----------------22/12/2023, 15:18:11----------------
- Exception in "Signalizer" v."0.4.2"
Runtime exception (ExhaustedException) in Signalizer (0.4.2): "CSerializer exhausted; probably incompatible serialized object." in C:\Code\Signalizer\External\cpl\state\CSerializer.h:836 -> cpl::CSerializer::operator >>

[onerob]

I get a message saying that the plugin is damaged and the option to move it to the bin. (AU and VST version).

Yes, okay, now I've had multiple people reporting this. It's because of the Gatekeeper in newer versions of macOS that specifically bricks anything not downloaded and notarized from the app store - something Apple charges $99/year for.

There are ways around this if you want, I've added more thoughts and links here: https://bitbucket.org/Mayae/signalizer/ ... advice.txt

It's an interesting one as I have Gatekeeping disabled and never normally have to go through and de-quarantine any files when installing non-notarized plugins. But this time I tried it and it did stop the 'move to the bin' warning. I then needed to rescan the plugin in Logic's plugin manager, which produced a warning I've never seen before which said:

Error serializing state information:
Runtime exception (ExhaustedException) in Signalizer (0.4.2): "CSerializer exhausted; probably incompatible serialized object." in ../../External/cpl/state/CSerializer.h:836 -> operator>>

But the plugin does now function after restarting Logic, so thanks for the suggestion.

[Mayae]

today I'm getting this error every time

... a warning I've never seen before ...

Sorry about these, I ran a better battery of tests this time. Fixed in new release 0.4.3:

Code: Select all

## 0.4.3 - 2023-12-22

### Fixed

- Exception "CSerialized exhausted; probably incompatible serialized object" upon restoring a project.
- System exception in "main window procedure" during `cpl::rendering::CDisplaySetup::update()`
- Resilience when concurrently writing exceptions to the log file

[Mayae]

It's an interesting one as I have Gatekeeping disabled and never normally have to go through and de-quarantine any files when installing non-notarized plugins. But this time I tried it and it did stop the 'move to the bin' warning.

Can you describe the process and what you had to do in a bit more detail? It might help anyone else with this problem who hasn't tried above yet

(I can't update my macOS development setup far enough to provoke this issue without losing the ability to build for older versions )

[onerob]

It's a terminal command. There are a few slight variations of it reported on the web, but the way I do it is to paste

sudo xattr -rds com.apple.quarantine

into Terminal and then drag the relevant plugin file (i.e. Signalizer.component) onto the window at the end of the command as a quick way of appending the file path. Once this is entered, and after my admin password is supplied to run the command, the file no longer gets binned.

But this may be something that each end user has to do because the mere act of creating an installer or zip archive may cause the quarantine attribute to be added back into the file. I'm not really sure as I'm not a dev and so haven't had to face the issue from that perspective.

More info here:

https://apple.stackexchange.com/questio ... t-to-the-t
https://www.barebones.com/support/bbedi ... ntine.html

[onerob]

today I'm getting this error every time

... a warning I've never seen before ...

Sorry about these, I ran a better battery of tests this time. Fixed in new release 0.4.3:

Code: Select all

## 0.4.3 - 2023-12-22

### Fixed

- Exception "CSerialized exhausted; probably incompatible serialized object" upon restoring a project.
- System exception in "main window procedure" during `cpl::rendering::CDisplaySetup::update()`
- Resilience when concurrently writing exceptions to the log file

Thanks. No errors reported now.

[catmakinbizkitz]

I just migrated to an M1 mac and am having trouble getting it to show up for me... i did the de-quarantine step. xcode is intalled... not sure how to further troubleshoot this. anyone else got it working on an M1 or is it just unsupported at this point? is there a beta i can test or something?

[AlQuzMar]

Glad to see that Signalizer is worked on again. Thank you Mayae!