Hi Chris, hi list!!
I think that would be great and i was hoping for something like this since that very post came up.
my idea is to implement ngspice as a pd object, or, on the long run, as a set of objects representing the parts.
I think one object, possibly with inlets for certain values like C, R would be a great thing.
for a start i think it would be sufficient
to have a single object that loads a netlist. that netlist has to be generated in en external tool, preferably from the gEDA suite http://gnuwin.epfl.ch/apps/geda/
after that it would be great to split up the rather big ngspice package into serveral objects, and eventually integrating a way to use a pd patch as a netlist source for it. that way, a circuit could be drawn as kind of subpatch.
I did't have a look at the ngspice package yet, but i think if it's not too complicated to create circuits in that, one could do fine with a single object and spend time on optimizing performance.
also i think that for the purpose of making it a pd object, some things could be simplified regarding the math to calculate the net's. any math-heads around that like to help with that? trading accuracy for speed, in this case.
Either by specifying accuracy/resolution/sampling interval as an argument to that object, or by precalculating static parts of the circuit (hard to find though) in advance?
what do you think? anyone like to participate in such a project? for me alone that would be bit to much right now, but i think it would be a nice thing to be able to emulate real synth/filter/etc. circuits in pd and mix that with the realtime audio capabilities ....
Oh, this would be great!
I have some background in electrical engineering, but i am not really a math-head. I'd be able to help, give feedback, or "write the docs(TM)".
Thanks again for this great idea popping up!
cheerio,
Peter