# Stone Voices Plug-Ins
**URL:** https://iplug2.discourse.group/t/stone-voices-plug-ins/37
**Category:** Made with iPlug2
**Created:** [25 March 2020 04:47 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37 "2020-03-25T04:47:33Z")
**Posts on this page:** 20
**Page:** 2
### Author:  [@wcr\_hlo](https://iplug2.discourse.group/u/wcr_hlo)
#### Post date: [7 May 2022 13:13 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/21 "2022-05-07T13:13:30Z")
Wooooow it’s cool THAAANks!
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [2 October 2022 15:28 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/22 "2022-10-02T15:28:49Z")
Author VSTi plugin **“AlienBlockMachine"**
---
### Author:  [@olilarkin](https://iplug2.discourse.group/u/olilarkin)
#### Post date: [2 October 2022 17:14 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/23 "2022-10-02T17:14:45Z")
Nice! Where can we download it?
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [2 October 2022 23:37 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/24 "2022-10-02T23:37:47Z")
This plugin is designed to work with the author’s MIDI controller and is under testing.
---
### Author:  [@RexMartin2](https://iplug2.discourse.group/u/RexMartin2)
#### Post date: [27 October 2022 14:58 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/25 "2022-10-27T14:58:18Z")
> [@vasyan](#):
>
> I also emphasize that one of the features of this plugin is a real-time skin change. The selected skin is automatically installed in a new session with the plugin. It is enough to press the switch and change the skin. To do this, we had to add a style manager to the framework.
I am curious where you are saving the skin selection setting. Most times a skin choice applies to all instances of the plugin. In that case, I would think that the skin choice would have to be saved in a separate file somewhere and not as plugin parameter.
Other times I imagine a user might want choose the skin as part of the current project - in which case it _could_ be stored as a plugin parameter.
Which way did you choose/how did you implement this?
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [28 October 2022 17:06 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/26 "2022-10-28T17:06:00Z")
The plugin saves its settings in an ini file, just like the standalone version does.
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [19 July 2024 09:49 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/27 "2024-07-19T09:49:58Z")
[**DReverb 2.0**](https://stone-voices.ru/vst/dreverb) — is a free plugin for creating high quality algorithmic reverbs, the basis of which is modified Dattorro’s algorithm.
GUI - 100% vector graphics rendered by IPlug2 functions.
---
### Author:  [@RexMartin2](https://iplug2.discourse.group/u/RexMartin2)
#### Post date: [23 July 2024 15:32 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/28 "2024-07-23T15:32:21Z")
> [@vasyan](#):
>
> GUI - 100% vector graphics rendered by IPlug2 functions
Those knobs are vector graphics? How did you get the drop shadows beneath them and such?
My difficulty with using vector graphics is that we can’t see what it looks like until we build and run the plugin. How did you create such things as the “Space”, “Modulation”, “Filter” and “Damping” brackets, the little “clock” and “mix” symbols, non-linear meter scales, etc.?
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [24 July 2024 09:00 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/29 "2024-07-24T09:00:03Z")
> [@RexMartin2](#):
>
> How did you get the drop shadows beneath them and such?
ILayerPtr + ApplyLayerDropShadow
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [24 July 2024 09:07 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/30 "2024-07-24T09:07:34Z")
> [@RexMartin2](#):
>
> How did you create such things as the “Space”, “Modulation”, “Filter” and “Damping” brackets, the little “clock” and “mix” symbols, non-linear meter scales, etc
such things is a PathMoveTo, PathLineTo, PathArc and PathStroke metods of IGraphics class. The little “clock” and “mix” symbols is special Font.The non-linear meter scales also drawn using the line drawing methods of the IGraphics class.
---
### Author:  [@RexMartin2](https://iplug2.discourse.group/u/RexMartin2)
#### Post date: [24 July 2024 17:18 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/31 "2024-07-24T17:18:20Z")
Thank you for the insight. It still seems difficult to design a UI with vector graphics since we can’t see what we’re doing while doing it. It’s basically designing with math vs. designing with graphics. I’ve tried using vector graphics but it took so much iterating - tweaking, re-building and running to “get there” - that I gave up on it. I’ve been using bitmap graphics designed “WYSIWYG” in Photoshop instead. But your plugins demonstrate that vector graphics can yield a much sharper image, especially when scaled/resized - so I need to revisit vector.
How do you approach your UI layout given it’s “sight unseen” at coding time?
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [25 July 2024 01:30 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/32 "2024-07-25T01:30:54Z")
> [@RexMartin2](#):
>
> How do you approach your UI layout given it’s “sight unseen” at coding time?
To begin with, you can make a layout in any graphic editor, however, to develop the plugin interface, I developed a special editor - [IPlug Designer](https://iplug2.discourse.group/t/iplug-designer-designer-program-for-iplug2-framework/513). Then you can transfer graphic objects by defining their location and size into code that forms these graphic objects using drawing primitives - lines, rectangles, circles, arcs, Bezier curves and others.
---
### Author:  [@rramirez](https://iplug2.discourse.group/u/rramirez)
#### Post date: [8 September 2024 01:47 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/33 "2024-09-08T01:47:29Z")
Did you use a background png? or is it vector (iplug2 graphics)? I was wondering how did you manage to add noise to the background.
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [8 October 2024 05:17 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/34 "2024-10-08T05:17:33Z")
I created a layer on which the noise was generated. I already asked a question about layer manipulation once.
P.S. There are no PNG images in this plugin. Everything is drawn algorithmically.
> [@Extended ILayerPtr manipulation. Blur, desaturation etc](https://iplug2.discourse.group/t/extended-ilayerptr-manipulation-blur-desaturation-etc/763):
>
> In principle, various manipulations with the ILayer are possible, similar to the ApplyLayerDropShadow method? Interested in Gaussian blur, desaturation, noise addition, and other effects? Are there methods for directly accessing pixels?
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [20 January 2025 03:55 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/35 "2025-01-20T03:55:19Z")
A recently published plugin that was developed by order of **Wikisound**.
The details are [here](https://wikisound.store/product/wikisound_-_correction_2_podpiska)
GUI can be switched to a light and dark theme:
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [2 March 2025 12:27 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/36 "2025-03-02T12:27:58Z")
**Ambient Reverb 7**
[Homepage](https://stone-voices.ru/vst/ambient_reverb?lang=en)
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [25 February 2026 04:28 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/37 "2026-02-25T04:28:26Z")
With the free **Retro Radio** VST plug-in, you can simulate the sound of old AM radios with all the nuances, including noise, crackle, rattle, and Morse code inherent in this type of radio reception. As well as amplitude-frequency distortions and parasitic modulations. It is possible to emulate the acoustics of various models, from stationary to pocket radios.
The plug–in’s design is stylized like a tube radio receiver, where the so-called “magic eye” is used as a level indicator - an imitation of the 6E5C cathodoluminescent lamp, which was widely used in various radios in the good old days.
[homepage](https://stone-voices.ru/vst/retro_radio?lang=en)
---
### Author:  [@JohnCrosby](https://iplug2.discourse.group/u/JohnCrosby)
#### Post date: [15 March 2026 06:06 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/38 "2026-03-15T06:06:31Z")
No AudioUnits versions for Mac?
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [3 April 2026 09:47 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/39 "2026-04-03T09:47:02Z")
I’m still having trouble porting the plugin to mac. My new Macbook Pro with an M4 processor could not build a single plug-in built on the IPlug2 framework for the arm64 platform, however, when I build for x86\_64, for some reason the plug-ins do not run on the new Macbook Pro, although they work on the old Macbook Air. I’m dealing with this problem right now.
---
### Author:  [@vasyan](https://iplug2.discourse.group/u/vasyan)
#### Post date: [4 April 2026 11:26 UTC](https://iplug2.discourse.group/t/stone-voices-plug-ins/37/40 "2026-04-04T11:26:01Z")
Today I managed to build a plugin for macOS but for the x86\_64 architecture, however, I had to run the REAPER through an Rosetta, then the plugin worked. I have no idea how to create a plugin for the native arm 64 architecture, the iPlug 2 framework does not compile, there are many errors.
[Previous page](https://iplug2.discourse.group/t/stone-voices-plug-ins/37.md?page=1)
[Next page](https://iplug2.discourse.group/t/stone-voices-plug-ins/37.md?page=3)