It’s clear it’s a chip that’s best used with a microcontroller. It even has line output you don’t have to kludge from a speaker output, but you need a controller to enable that.
1 Like
I have buy this cheap china module few years ago:
I have an ISD1730 and 1932 too, but I have never test them…
I had begin DIY with the famous Isd1820 in hope to build a great sampler/Looper, but the result was only a funny Lo-Fi thing… ahah
Now, for a better quality, I need to use my Tsunami Wave Trigger from sparkfun, the possibilities of this board look great !
1 Like
Yeah, I’m not that much interested in hi fi samplers. More interested in sounds that don’t sound like something else. So funny lo fi things are more my speed.
4 Likes
its right too ! I need the two things ! 
2 Likes
I am still at a very early stage (started with modular a couple of weeks ago) but I thought I show it, even if it’s so basic 
From left to right: 3340 LMNC VCO, Attenuator/Mixer, Twin ADSR based on 7555, Passive Attenuator, double VCO, MS-20
The four strip boards are: 3340 LMNC VCO, 2x snare/hi-hat, Roland System 100 LFO
here are a few other pics:
Today I made a simple 2399 which I love!
23 Likes
Lovely to see some colorful Kosmo! Welcome!
1 Like
Very nice, These module panels would suite my case(s) very well!! I’ve affectionately called them NeonKosmo Case1/2/3. Since i painted them all with Neon spray paints.
Pics…
11 Likes
welcome, this is really a good beginning high of colors !!
2 Likes
All that in your first couple weeks? Watch out, @Dud!
No offense to black panel lovers, but I think it’s great seeing something different…
11 Likes
Yeah my panels are a contradiction to the theme.
So far they’re all black and 3D printed grey, with no labels haha.
I think dud is safe… for about a month =P
2 Likes
More drum contact micing. Assisted a build of a 4-mono to 2-stereo contact mic mixer for the drum kit. Sounds way, way better than I was expecting, super heavy lo-fi drums, but very responsive.
2 Likes
Finished building my new oscillator module based around a CD40106. All oscillators have their own CV. The outputs can be switched to a mult out also. Nice little module. Enjoy.
7 Likes
@tamasgal , it’s really not my taste but very nice work, and like @analogoutput said i also like to see different things, recognizable between 1000
with @willow2x 's case you have made a nice rainbow modular 
HEY OOHH ! slowly man (lol) my 1st case (case + power supply + 16 modules) was completed in 3 weeks, now i’m much slower but a little respect for the elders 
7 Likes
Thanks for all the positive feedback 
all this would not have been possible without all the great content and discussions here!
Yeah, @willow2x’s case is awesome! I am currently building a new case due to space problems and my first one was also just a placeholder. I think the cases will be less colourful though 
I cannot compete with @Dud, that’s just insane, from what I have seen so far 
let alone the tracks he shows on YT!
…also my progress will now slow down since I have to spend a significant amount of time on work and finalising my PhD. 
But it’s a lot of fun and I’m very glad I found this nice hobby to consolidate many of my interests 
4 Likes
Good luck with the man! Just finished mine, one hell of a job
5 Likes
a module per Day
A Fixed Bandpass Filter Bank based on the Buchla #194, this tool is really good for audio mastering applications; we can use 4 individual outputs to filtering and treating an audio signal, and a mixed output who can use like a Comb filter or a 4 Band EQ for exemple.
https://electro-music.com/wiki/pmwiki.php?n=Schematics.Buchla194FixedFilterRedrawnByMarjanUrekar
7 Likes
I have had a couple of deliveries over the past couple of weeks, and finally got some time to get on with building, Two Frequency Central Micro Bus power supplies, a LMNC 1222 VCO, A couple of mini mixers.
A new PCB revision on Brenn a quad slow LFO with durations between 6 seconds and about 15 minutes, The previous board required a cutout for one of the jacks and had the inputs on one of the opamps reversed. It appears to be all working now, but I shall test for a bit longer before I make the design public.
I have also been working on a voltage controllable ADSR module. I had just sent to gerbers for fabrication when I watched one of Sam’s videos where he talked about a similar module for an upcoming project. I was really enjoying this module last night, so much so I make a second, this also confirmed that I have made a mistake translating between breadboard and kicad on the AD/ADSR switch. I am also debating the usefulness of the trigger button, but that could be to do with it looking out of place on the panel. I am going to use this as if for a while, before deciding how to proceed.
I do have a question for the community, I have always enjoyed sharing my creations with the community, up till now this has always been open source audio software. I would like to publish my finished modules on github and add them to Kosmo-modular grid. My question is what makes a verified design?
In the software domain finding testers, and implementing feedback was an importatant phase of the development cycle, and this could be done quickly. I also had automated unit tests that gave me confidence. This is not so simple with hardware, how are other module developers implementing this?
Anyway, enough words, top row 2 x Frequency central PSU, bottom row left to right, LMNC 1222 VCO, Farini Voltage controlled ADSR, Brenn slow LFO, 2 x mini mixer.
5 Likes
For me, it starts with the schematic and checking whether all inputs and outputs are well protected etc. When I receive the hardware, I build the module (check whether that goes smoothly), and then plug in the signal generator and the scope to see whether results match my expectations. Then, I plonk it into the system and do everything to it which I can imagine, and again see if results make sense.
I never publish anything without building and testing the hardware myself.
5 Likes
Fruitful weekend - a successful build of the Teensy Midi Audio board that I have installed MicroDexed on.
Now to explore the patches and see if I can make sense of FM synthesis…
4 Likes
We have seen various people post schematics in the past whether they designed them or found them somewhere on the net. These were sometimes built by the posters but often they were not. So whether the designs were actually sound and would work in practice for quite a few schematics was still undecided. Given that search engines find all kind of schematics publishing or republishing untested or unverified schematics would only make it more difficult to find a schematic that would work. Especially for people new to electronics it may be difficult or impossible to see whether a schematic when built is likely to work. Therefore in the past I amongst others have asked people to either put a remark ‘working/verified/untested’ or similar in the images of schematics they publish.
I would be happy when the person publishing a schematic has built the circuit and checked whether it was working the way it was meant to.
I wouldn’t make this ‘the way it was meant to [work]’ too complicated though. Obviously it would be great if as @TimMJN suggest all inputs and outputs are protected, but that in a lot of cases is not central to the working of a module (it makes it more durable of course, and is nice to have) and only necessary when used in situations where inputs and outputs may be overloaded (which may never happen) AND I/O protection can often be added to a module.
To make this short I would suggest: verified/tested means the publisher built the circuit from the schematic and found it to be working.
7 Likes