Notice: Subscribe to the mailing list for Signalizer to get updates and discuss development of Signalizer here:
http://jthorborg.com/mailman/listinfo/s ... orborg.com
- I'm looking for feedback on my new alpha plugin, see links at end of post.
- Here's a new demo of the oscilloscope:
- Here's a tour around the rest of the plugin:
Some of you may have seen me hanging around in the dsp-devs forums, where I maintained my last public project, Audio Programming Environment.
I study sound design with a heavy emphasis on dynamic and interactive audio design. This led me down the path of programming plugins to accomodate my personal needs in production. Once in a blue moon, I produce something I consider to be usable by other people.
I really enjoy the act of programming creative tools - but it takes time to learn to do properly. Signalizer, the plugin in question, has been my testbed for developing algorithms, methods, UI and whatnot needed for having a base for audio programs.
About this project
Signalizer is all about engineering-grade and -customization visualization of audio in real-time, with very fast response and frame rates. This allows immediate intuitive feel & look of audio, as well as very precise measurements for analysis.
Now, there are a lot of signal analyzers out there. What differentiates this project?
- Interactive displays
- All UI and graphics colours changeable
- Vector graphics all the way
- Everything is smoothly variable and zoomable, no more fixed block sizes etc.
- Fullscreen hardware-accelerated graphics
- Being open source, the developer is mostly interested in implementing user feedback and requests
- Completely free & redistributable, no license/user sign-up, no e-mail spam
- no installation packages, completely self-contained
- A focus on creating general purpose visualizations without too much jazz, for i.e. VJ'ing
- All-in-one package for all your analysis needs (at some point)
- No load on the main thread
Some feature highlights
- Built in 3D transformation
- Classic X/Y vectorscope ('lissajous') or 'polar' projections
- Balance and stereo correlation meters
- Standard fft
- Custom developed filter bank with 'minimum Q' tuning, ie. optimizes frequency/time tradeoffs to something akin to constant-Q transforms, but much more natural
- Projections on to graphs or spectrograms
- Can design own dsp windows
- Together with all the classic channel modes (side/mid/left/parallel etc.), it shows precise phase cancellations in the spectrum as well
- Inter-sample interpolation in different modes, including fluid lanczos
- Assortment of triggering methods like zero-crossing, spectral harmonic analysis, peak/enveloping and timing windows
- Time, cycles or beat/tempo mode
- Overlaid or separate scopes for each channel
- Waveform can be painted spectrally with custom colours for each band, with per-sample in-phase precision
- Adaptive grid adjustable in density
- Freely zoomable infinitely
What I'm interested in
One thing is feedback about the usability and purpose of the program, which is of course very welcomed - but also UI design, practices and the program as a package. Is there anything missing? Is the program easily usable? Is the text readable? Does the UI work as you expect, is it confusing to navigate - etc?
Bug reports (stability is #1 concern right now) and feature requests is also very welcome. I developed the set of features I needed the most, but what do you guys need in this sort of program?
Other than that, I hope you enjoy the program and are willing to contribute back or support the open source community with experience, code (or comments on) or feedback. I strive to program best practices, so if you notice something bogus let me know.
Also, if anyone programs a cool preset please do share it
End notes, links etc.
You can find more information, source code and binaries on Signalizer's dedicated home page.
Here's a direct link to an auto updated page of release binaries. The releases contain x32 and x64 versions of VST, VST3 and AudioUnits for OS X and Windows, as well as debug versions of previous. The debug versions contain additional info, that generates better debug output for reporting back bugs.
The project is a massive WIP, but I wanted to get it out now to test out the UI and get some feedback on directions.
I usually update and release fixes a couple of times a week, if I have the time. Inside the release you will find a small version log that lists the most recent changes. Otherwise, you can check out the revision history.
Thank you for any interest