Signalizer: Sidechaining update! Open-source & free audio visualization plugin (v. 0.4.3)
-
- KVRian
- Topic Starter
- 573 posts since 1 Jan, 2013 from Denmark
Thanks!!
?What else?
-
- KVRist
- 33 posts since 5 Sep, 2018
i only use 2 plugins atm:
blue cat plug'n script and
signalizer
thank you for providing 50% of all plugins i'm using!
blue cat plug'n script and
signalizer
thank you for providing 50% of all plugins i'm using!
- Banned
- 559 posts since 9 Sep, 2019
-
Guillermo Luijk Guillermo Luijk https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=453015
- KVRer
- 9 posts since 13 Dec, 2019
Although Janus (Mayae) kindly explained to me that he is now focused on other projects, I have been testing Signalizer for a while now. I had some stability issues (W10) at the beginning, but after setting clearly the presets to use everytime the software seems quite stable. I miss the UI was a bit more intuitive, and the colour specifications more flexible. Also miss more standard axis gridding and scaling.
I find it a tremendously educative tool working in conjuntion with synthesis VST's to learn a lot about what's really going on under the hood (basic waveforms, armonics, filtering, modulation, DAC theory) and not just learning by ear and test/error. The ability to freeze periodical signals and the hyper fast visual renderings make it a joy to use.
Regards
I find it a tremendously educative tool working in conjuntion with synthesis VST's to learn a lot about what's really going on under the hood (basic waveforms, armonics, filtering, modulation, DAC theory) and not just learning by ear and test/error. The ability to freeze periodical signals and the hyper fast visual renderings make it a joy to use.
Regards
-
- KVRAF
- 14658 posts since 19 Oct, 2003 from Berlin, Germany
So the software is now declared "abandoned"?
Pity... I really enjoyed using it (on Windows at least, the times I used it on a friends rig in LPX, it did crash hard macOS several times - even sometimes corrupting projects) and it had a lot(!) of potential with so much more room for more (see FRs from previous pages).
Pity... I really enjoyed using it (on Windows at least, the times I used it on a friends rig in LPX, it did crash hard macOS several times - even sometimes corrupting projects) and it had a lot(!) of potential with so much more room for more (see FRs from previous pages).
- KVRist
- 470 posts since 11 Mar, 2007 from Portugal
I use it everyday, since it's on my default project/initial template and usually kept in mostly when dealing with external gear
-
- KVRist
- 46 posts since 6 Dec, 2004
Hi, came across this great free software. It's great ! You should keep developing it. i understand other priorities for your life. That is really important but try to keep this gem. it´s really good.
All the best
All the best
-
- KVRer
- 6 posts since 18 Jul, 2015
Greetings! Has anyone had any luck recently getting this to work on Bitwig + Linux?
I tried adding the most recent Linux VST binary (v0.3.2) to the relevant directory monitored by Bitwig.
Initially Bitwig appeared to detect that the plugin was a VST3 plugin, and tried to load it as a VST2 plugin, and failed.
I reorganized the directory structure a bit to mirror other working VST3 plugins, e.g.:
Now, Bitwig successfully detects that it is a VST3 plugin, however, it still fails to load successfully:
System Info:
- Arch Linux 5.5.7 64-bit
- Bitwig Studio 3.1.2
- Jack2 1.9.14
And the output from `ldd Signalizer.so`:
Any thoughts?
I tried adding the most recent Linux VST binary (v0.3.2) to the relevant directory monitored by Bitwig.
Initially Bitwig appeared to detect that the plugin was a VST3 plugin, and tried to load it as a VST2 plugin, and failed.
I reorganized the directory structure a bit to mirror other working VST3 plugins, e.g.:
Code: Select all
~.vst3/Signalizer.vst3
└── Contents
├── Build.log
├── licenses
│ ├── dustfft.txt
│ ├── LICENSE.txt
│ ├── nonspecific
│ │ ├── CC BY 3.0.txt
│ │ ├── CC BY 4.0.txt
│ │ ├── GPL v3.txt
│ │ └── MIT.txt
│ ├── octave.txt
│ ├── readerwriterqueue.txt
│ └── resources
│ └── map.txt
├── presets
│ ├── analytical.spectrum.sgn
│ ├── beats.oscilloscope.sgn
│ ├── cycles.oscilloscope.sgn
│ ├── default.main.sgn
│ ├── free.oscilloscope.sgn
│ ├── impulse.oscilloscope.sgn
│ ├── impulse.spectrum.sgn
│ ├── init.oscilloscope.sgn
│ ├── nautical.spectrum.sgn
│ ├── oscilloscope.vectorscope.sgn
│ ├── polar.vectorscope.sgn
│ ├── spectrogram.spectrum.sgn
│ ├── standard.vectorscope.sgn
│ └── sub investigation.oscilloscope.sgn
├── READ ME.txt
├── Resources
│ └── icons
│ └── svg
│ ├── brush.svg
│ ├── errorcross.svg
│ ├── error.svg
│ ├── formulae.svg
│ ├── freeze.svg
│ ├── fullscreen.svg
│ ├── Gears.svg
│ ├── gear.svg
│ ├── graph.svg
│ ├── help.svg
│ ├── idle.svg
│ ├── map.txt
│ ├── save.svg
│ ├── successtick.svg
│ ├── sync.svg
│ └── wrench.svg
└── x86_64-linux
└── Signalizer.so
Code: Select all
[2020-03-04 20:32:11 float-library-metadata error] Plugin host error Failed to load VST 3 plug-in /home/xx/.vst3/Signalizer.vst3: /home/xx/.vst3/Signalizer.vst3/Contents/x86_64-linux/Signalizer.so: undefined symbol: snd_pcm_hw_params_test_rate
[2020-03-04 20:32:11 float-library-metadata info] Closing connection with plugin host: The connection should not be kept alive at the end of the command
[2020-03-04 20:32:11 indexer error] Could not read metadata for Signalizer.vst3:
java.io.IOException: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Failed to load VST 3 plug-in /home/xx/.vst3/Signalizer.vst3: /home/xx/.vst3/Signalizer.vst3/Contents/x86_64-linux/Signalizer.so: undefined symbol: snd_pcm_hw_params_test_rate
at Yev.rLY(SourceFile:45)
at Yev.CRd(SourceFile:21)
at kRs.Stj(SourceFile:840)
at kRs.aXe(SourceFile:771)
at qhN.aXe(SourceFile:591)
at hEI.aXe(SourceFile:44)
at hEI.preVisitDirectory(SourceFile:16)
at java.base/java.nio.file.Files.walkFileTree(Unknown Source)
at BCX.Stj(SourceFile:622)
at BCX.aXe(SourceFile:604)
at Esm.aXe(SourceFile:276)
at IHA.aXe(SourceFile:881)
at kRs.aXe(SourceFile:565)
at kRs.Stj(SourceFile:189)
at kRs.aXe(SourceFile:139)
at twA.aXe(SourceFile:573)
at OGK.aXe(SourceFile:1025)
at OGK.Stj(SourceFile:897)
at yXq.Stj(SourceFile:110)
at yXq.run(SourceFile:91)
at d1z.run(SourceFile:20)
Caused by: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Failed to load VST 3 plug-in /home/xx/.vst3/Signalizer.vst3: /home/xx/.vst3/Signalizer.vst3/Contents/x86_64-linux/Signalizer.so: undefined symbol: snd_pcm_hw_params_test_rate
at q3v.aXe(SourceFile:163)
at q3v.CRd(SourceFile:30)
at N3q.CRd(SourceFile:14)
at Yev.rLY(SourceFile:41)
... 20 more
Caused by: java.io.IOException: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Failed to load VST 3 plug-in /home/xx/.vst3/Signalizer.vst3: /home/xx/.vst3/Signalizer.vst3/Contents/x86_64-linux/Signalizer.so: undefined symbol: snd_pcm_hw_params_test_rate
at ynS.aXe(SourceFile:94)
at ynS.aXe(SourceFile:80)
at KU.Stj(SourceFile:186)
at KU.aXe(SourceFile:286)
at q3v.aXe(SourceFile:159)
... 23 more
Caused by: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Failed to load VST 3 plug-in /home/xx/.vst3/Signalizer.vst3: /home/xx/.vst3/Signalizer.vst3/Contents/x86_64-linux/Signalizer.so: undefined symbol: snd_pcm_hw_params_test_rate
at TYn.aXe(SourceFile:44)
at TYn.CRd(SourceFile:10)
at ynS.aXe(SourceFile:86)
... 27 more
Caused by: IFF: Failed to load VST 3 plug-in /home/xx/.vst3/Signalizer.vst3: /home/xx/.vst3/Signalizer.vst3/Contents/x86_64-linux/Signalizer.so: undefined symbol: snd_pcm_hw_params_test_rate
at Whd.bUZ(SourceFile:1375)
at Whd.aXe(SourceFile:444)
at Whd.Stj(SourceFile:430)
at Whd.aXe(SourceFile:1183)
at Whd.aXe(SourceFile:430)
at fkj.aXe(SourceFile:139)
at fkj.aXe(SourceFile:126)
at TYn.aXe(SourceFile:32)
... 29 more
[2020-03-04 20:32:11 base-util info] Updating index /home/xx/.vst3 for phase vst3_plugins_64: time=41.566803
[2020-03-04 20:32:11 indexer error] Could not read metadata for Signalizer.vst3:
java.io.IOException: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Failed to load VST 3 plug-in /home/xx/.vst3/Signalizer.vst3: /home/xx/.vst3/Signalizer.vst3/Contents/x86_64-linux/Signalizer.so: undefined symbol: snd_pcm_hw_params_test_rate
at Yev.rLY(SourceFile:45)
at Yev.CRd(SourceFile:21)
at kRs.Stj(SourceFile:840)
at kRs.aXe(SourceFile:771)
at qhN.aXe(SourceFile:591)
at hEI.aXe(SourceFile:44)
at hEI.preVisitDirectory(SourceFile:16)
at java.base/java.nio.file.Files.walkFileTree(Unknown Source)
at BCX.Stj(SourceFile:622)
at BCX.aXe(SourceFile:604)
at Esm.aXe(SourceFile:276)
at IHA.aXe(SourceFile:881)
at kRs.aXe(SourceFile:565)
at kRs.Stj(SourceFile:189)
at kRs.aXe(SourceFile:139)
at twA.aXe(SourceFile:573)
at OGK.aXe(SourceFile:1025)
at OGK.Stj(SourceFile:897)
at yXq.Stj(SourceFile:110)
at yXq.run(SourceFile:91)
at d1z.run(SourceFile:20)
Caused by: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Failed to load VST 3 plug-in /home/xx/.vst3/Signalizer.vst3: /home/xx/.vst3/Signalizer.vst3/Contents/x86_64-linux/Signalizer.so: undefined symbol: snd_pcm_hw_params_test_rate
at q3v.aXe(SourceFile:163)
at q3v.CRd(SourceFile:30)
at N3q.CRd(SourceFile:14)
at Yev.rLY(SourceFile:41)
... 20 more
Caused by: java.io.IOException: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Failed to load VST 3 plug-in /home/xx/.vst3/Signalizer.vst3: /home/xx/.vst3/Signalizer.vst3/Contents/x86_64-linux/Signalizer.so: undefined symbol: snd_pcm_hw_params_test_rate
at KU.aXe(SourceFile:157)
at KU.Stj(SourceFile:178)
at KU.aXe(SourceFile:286)
at q3v.aXe(SourceFile:159)
... 23 more
[2020-03-04 20:32:11 base-util info] Updating index /home/xx/.vst3 for phase vst3_plugins_32: time=2.653275
[2020-03-04 20:32:11 base-util info] Updating index /home/xx/.vst3 for phase vst2_plugins_64: time=0.238637
[2020-03-04 20:32:11 base-util info] Updating index /home/xx/.vst3 for phase vst2_plugins_32: time=0.134983
[2020-03-04 20:32:11 base-util info] Updating index /mnt/music/bitwig/library for phase content: time=3.373796
[2020-03-04 20:32:11 base-util info] Updating index /home/xx/.u-he for phase content: time=49.008255
[2020-03-04 20:32:15 base-util info] Updating index /mnt/music/Splice/Samples/packs for phase content: time=3980.6328
[2020-03-04 20:32:29 base-util info] Updating index /mnt/music/User Library/samples for phase content: time=13931.933
[2020-03-04 20:32:29 base-util info] Updating index /mnt/music/bitwig/library for phase plugin_presets: time=1.268128
[2020-03-04 20:32:29 base-util info] Updating index /home/xx/.u-he for phase plugin_presets: time=26.581484
[2020-03-04 20:32:32 base-util info] Updating index /mnt/music/Splice/Samples/packs for phase plugin_presets: time=2911.9895
[2020-03-04 20:32:45 base-util info] Updating index /mnt/music/User Library/samples for phase plugin_presets: time=13584.037
- Arch Linux 5.5.7 64-bit
- Bitwig Studio 3.1.2
- Jack2 1.9.14
And the output from `ldd Signalizer.so`:
Code: Select all
linux-vdso.so.1 (0x00007fff331b5000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f9481f4f000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007f9481e09000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f9481def000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f9481c29000)
/usr/lib64/ld-linux-x86-64.so.2 (0x00007f9482ef1000)
- KVRist
- 428 posts since 30 Jan, 2015
-
- KVRian
- 502 posts since 1 Jul, 2009
-
- KVRian
- 680 posts since 18 Sep, 2010
Just tried it a bit. It looks nice.
One question, though (probably just something I overlooked):
- On the scope, what is the best way to capture the leading edge (the attack) of a sound?
One question, though (probably just something I overlooked):
- On the scope, what is the best way to capture the leading edge (the attack) of a sound?