(I converted this to a new topic as it’s quite a side-track from the other one)
It seems LiveSpice is C# based. Kind of surprised you can write VST3 plugins using C#, but if you’d want the same then you’ll need something just like GitHub - mikeoliphant/AudioPlugSharp: Easily create VST (VST3) audio plugins in C# .NET except for LV2.
(this does not exist yet, so someone with extensive C# and LV2 knowledge would have to write it)
Well, I’m definitely not qualified to replicate Oliphant’s work for LV2, but I definitely am qualified to build a circuit in a GUI—as I imagine many other members of the forum are. Should someone do that bit of heavy lifting one day, I bet there are plenty of us who would circuit-map our favorite but never-before-digitized amps. Not saying it’s anyone’s responsibility in particular, but definitely a nice thing for a wishlist.
I think @brummer can chime in regarding this.
As @dreamer mentioned, Guitarix has something along these lines and I remember that Hermann pulled off many plugins with such an approach.
As others have pointed out, LiveSpice is written in C#, so an LV2 version is unlikely. It is is also very CPU intensive.
What you can do, is to use LiveSpice (or LTspice, for that matter) to create a circuit, and then use the VST to create a “capture” file suitable for training a neural model. See here, for example.
That would certainly make sense—I use Hermann’s GxAlembic all the time and thought that maybe circuit-mapping other preamps might be a less-heavy way of replicating other preamps than using AIDA or NAM (disclaimer: I’ve yet to train a model) while still being able to adjust whatever potentiometer or switch appears in the schematic. But of course much of Hermann’s work existed before MOD and was ported over, not originally targeted to LV2.
Sorry for delay, I’m a bit busy with may day job right now. Yes, we’ve done something like that and I’ve published a overview to my workflow to use it here:
https://linuxmusicians.com/viewtopic.php?t=19586&hilit=dkbuilder
Just note that this is far from been perfect. But, it allows me to create a hole lot of plugs, many of them you’ll find in the MOD store.
Bloody day jobs eh!? lol x
there are many techniques indeed, some are cited as references, but require you to perform circuit analysis to some extent. The often cited reference is WDF, used in white box modeling, was known way long before ML based stuff arrived. I’ve also studied the tool used in Guitarix, which is simply great. Guitarix works with nodal analysis in a similar way as LiveSpice. But simply solving nodal equations as they are won’t make it run in RT, so you have to cut angles. Guitarix does this by introducing a technique where you will extract a table of points (a LUT) to be used in place of nonlinearities. LiveSpice is more advanced and simplifies the original equations with less CPU intensive math functions. Of course the more you know about the circuit and the more you are aware to where those approximations will be applied, the best sounding emulation you will obtain. Still, the problem of all those approaches is finding a proper way to measure how close you are to the original circuit, not necessarily using ears. And still, figure out how it will respond to real audio data. To me loss functions and Datasets used in ML techniques solved both issues. Also, ML scales from black box to white box modeling. If you are interested and you would like to collaborate just drop me a msg!
If it is helpful, our BigMuff and DS-1 plugins were modelled by @couts, who fully modelled the entire circuits manually, created the code and then spent a bunch of time making it run in real time.
The plugins are OSS, so you can check how he did it.
Really interesting topic!
I’ve looked at the code for DS1 and it’s not the same as bigmuff’s, can I ask the author what method he used to model ds1? (Sorry I can’t find the @author button)
@QuanHu, not sure if I understood your issue messaging the author of the plugins.
As Gianfranco said, it was @couts. I’m not sure how active he is nowadays here in the MOD forum, but if you hover over a tag of him (like I just did now), you should get a pop up window with a button that allows you to message him directly. No?
@QuanHu I’ll answer your question about modeling a diode clipper here.
You can either use:
I chose for a hyperbolic tangent approximation and tried to align the shape and frequency response with the lookup table implementation as much as possible. The output gain is also based on the lookup table. I halved that gain because it sounded better. I don’t know exactly how to convert amplitude to voltage and vice versa. Levels depend highly on how much pre-amp gain you apply in the first place.
Thank you! 
Dave
@brummer
Hi,brummer
I know from reading the forums that you have made a very interesting tool called dk-builder, but I have installed it many times on my PC without success.
I’m wondering if it’s not installed correctly on my computer system. If I’m going to buy a raspberry pi, will it be able to install dk-bulider?
Sorry I’m not familiar with linux, but I’ve touched sharc writing guitar effects, as well as making my own guitar pedals with some analog circuits. Now, I want to make more guitar pedals for mod dwarf, and it would be very convenient if I could use dk-bulider. 
Posting a question in
a forum thread would also allow more people with doubts like mine to get by with answers. Hopefully my foolish questions won’t take away from public resources.
Can I try to finish installing guitarix once as a way to install the dependencies needed for dk-bulider? I wonder if that would increase the success of my installation.
dkbuilder is very old by now, the used python version is outdated.
The only way to use it by now is to set it up in a docker container.
You’ll find a dockerfile in the DK folder which could setup a container based on debian10.
Hi @brummer ,
I set up the environment using Docker, but I’m encountering these errors. Could you please advise how to resolve this? Initially, FAUST was version 2.14.4 during installation. After checking the link provided above, I downgraded FAUST to 0.9.90, but I’m still unable to get it running.
mmm.
Works here as expected.
S = ((R(12), 'u11', 'u2',),
(R(11), GND, 'u10',),
(R('L'), 'u12', 'V6',),
(L(1), 'u8', 'u12',),
(R(3), 'u3', '+9V',),
(V('cc'), '+9V',),
(P(1), 'u10', 'u11', 'u9',),
(C(1), 'V2', 'V1',),
(R(10), GND, 'u6',),
(R(5), GND, 'V6',),
(R(7), 'u8', 'V6',),
(R(6), 'V6', 'u3',),
(R(8), 'u5', 'u3',),
(R(1), 'V1', 'u7',),
(C(4), 'u5', 'u9',),
(C(3), 'u6', 'u8',),
(R(4), GND, 'u4',),
(R(2), 'u8', 'V2',),
(C(2), 'V6', GND,),
(T(2), 'u1', 'u5', 'u6',),
(T(1), 'u3', 'V2', 'u4',),
(C(6), 'u2', 'u3',),
(R(9), 'u1', '+9V',),
(OUT, 'u2',),
(IN, 'u7',),
)
V = {C(1): 0.01e-6,
C(2): 4.7e-6,
C(3): 0.01e-6,
C(4): 0.22e-6,
C(6): 0.22e-6,
L(1): 0.5,
P(1): dict(value=80.e3, var='Wah', a=3),
R('L'): 60.,
R(1): 68.e3,
R(10): 10.e3,
R(11): 10.e3,
R(12): 10.e3,
R(2): 1.5e3,
R(3): 22.e3,
R(4): 510.,
R(5): 100.e3,
R(6): 470.e3,
R(7): 33.e3,
R(8): 470.e3,
R(9): 1.e3,
T(1): dict(Vt=26e-3, Is=20.3e-15, Bf=1430, Br=4),
T(2): dict(Vt=26e-3, Is=20.3e-15, Bf=1430, Br=4),
V('cc'): 9.,
}
build lv2_plugin from: ['VoxWahV847.sch']
VoxWahV847
Please select a Plugin type from the list
1) DelayPlugin 14) BandpassPlugin 27) FlangerPlugin
2) ReverbPlugin 15) CombPlugin 28) PhaserPlugin
3) DistortionPlugin 16) EQPlugin 29) ReverbPlugin
4) WaveshaperPlugin 17) MultiEQPlugin 30) SimulatorPlugin
5) DynamicsPlugin 18) ParaEQPlugin 31) ReverbPlugin
6) AmplifierPlugin 19) HighpassPlugin 32) SpatialPlugin
7) CompressorPlugin 20) LowpassPlugin 33) SpectralPlugin
8) EnvelopePlugin 21) GeneratorPlugin 34) PitchPlugin
9) ExpanderPlugin 22) ConstantPlugin 35) UtilityPlugin
10) GatePlugin 23) InstrumentPlugin 36) AnalyserPlugin
11) LimiterPlugin 24) OscillatorPlugin 37) ConverterPlugin
12) FilterPlugin 25) ModulatorPlugin 38) FunctionPlugin
13) AllpassPlugin 26) ChorusPlugin 39) MixerPlugin
I guess you’ve downloaded the latest source from guitarix github repository. Then point your terminal to the /trunk/tools/ampsim/DK/docker/ folder and run
‘./docker-dkbuilder’ /were/ever/you’ve/guitarix/downloaded/to/guitarix-git/
The important step is to point the docker script to the guitarix-git source code, otherwise it wouldn’t find them after the docker image is ready to use.
personality failure 1
This looks as if something goes wrong during build the docker image.
You could just run the ./docker-dkbuilder /with/path/to/guitarix-git/ again.
You could run that anytime you want to use the dkbuilder.
EDIT:/
I did some tests, and yes, it indicate that you miss the personality.json file which is needed for security settings.
Ensure you use the docker-dkbuilder script to build the image, and not try to build it directly from the Dockerfile.
docker-dkbuilder download the personality.json file and set it as --security-opt for guitarix-dkbuilder.
It should also be used to start the image, as it set all needed environment variables so that dkbuilder works.