I can’t be bothered to diverge from LMNC’s case spec. I plan to use solid wood in substitute to plywood.
-Fumu / Esopus
I can’t be bothered to diverge from LMNC’s case spec. I plan to use solid wood in substitute to plywood.
-Fumu / Esopus
I have gone with the solid wood substitute. One thing i will say is for sure research what your nominal lumber dimensions are beforehand.
Nominal | Actual | Actual - Metric |
---|---|---|
1 x 2 | 3/4 x 1-1/2 | 19 x 38 mm |
1 x 3 | 3/4 x 2-1/2 | 19 x 64 mm |
1 x 4 | 3/4 x 3-1/2 | 19 x 89 mm |
1 x 5 | 3/4 x 4-1/2 | 19 x 114 mm |
1 x 6 | 3/4 x 5-1/2 | 19 x 140 mm |
1 x 7 | 3/4 x 6-1/4 | 19 x 159 mm |
1 x 8 | 3/4 x 7-1/4 | 19 x 184 mm |
1 x 10 | 3/4 x 9-1/4 | 19 x 235 mm |
1 x 12 | 3/4 x 11-1/4 | 19 x 286 mm |
1-1/4 x 4 | 1 x 3-1/2 | 25 x 89 mm |
1-1/4 x 6 | 1 x 5-1/2 | 25 x 140 mm |
1-1/4 x 8 | 1 x 7-1/4 | 25 x 184 mm |
1-1/4 x 10 | 1 x 9-1/4 | 25 x 235 mm |
1-1/4 x 12 | 1 x 11-1/4 | 25 x 286 mm |
1-1/2 x 4 | 1-1/4 x 3-1/2 | 32 x 89 mm |
1-1/2 x 6 | 1-1/4 x 5-1/2 | 32 x 140 mm |
1-1/2 x 8 | 1-1/4 x 7-1/4 | 32 x 184 mm |
1-1/2 x 10 | 1-1/4 x 9-1/4 | 32 x 235 mm |
1-1/2 x 12 | 1-1/4 x 11-1/4 | 32 x 286 mm |
2 x 2 | 1-1/2 x 1-1/2 | 38 x 38 mm |
2 x 4 | 1-1/2 x 3-1/2 | 38 x 89 mm |
2 x 6 | 1-1/2 x 5-1/2 | 38 x 140 mm |
2 x 8 | 1-1/2 x 7-1/4 | 38 x 184 mm |
2 x 10 | 1-1/2 x 9-1/4 | 38 x 235 mm |
2 x 12 | 1-1/2 x 11-1/4 | 38 x 286 mm |
3 x 6 | 2-1/2 x 5-1/2 | 64 x 140 mm |
4 x 4 | 3-1/2 x 3-1/2 | 89 x 89 mm |
4 x 6 | 3-1/2 x 5-1/2 | 89 x 140 mm |
I use solid pine for my cases. I like the looks better than plywood. There’s also less cutting involved if you design it using the standard dimensions.
Just thought I’d throw this out there, as a heads up. The current spec for mounting holes is incompatible with threaded strips for the metal rail systems used for eurorack. I’m having some Kosmo format side plates made and was made aware of this.
I’m probably going to go to slotted holes on my panels to avoid this problem in the future.
Well, yes, the threaded strips are HP spacing, not metric.
This repo
includes footprints for slotted mounting holes. I’ve been using them in my panels lately. I’ve centered the outer semicircle at 3 mm from side and top/bottom edges. I don’t use threaded strips, but I think they’re compatible that way.
yeah, I sent him a slot over last night to play with…
I take it back, in order to guarantee a threaded strip hole is exposed, the slot (unless its position is constrained) would have to be about 1 HP + 3.2 mm = 8.28 mm wide, the slots I’ve been using are only 6.4 mm.
Is a trigger signal a control voltage and what is the Kosmo specification if any has been before? I’m assuming that triggers although rising and falling sharper than most control voltages do have a difference to audio and gate and being the last category are the one they fit in, correct? It doesn’t really matter to me except I’m trying to code my hook up wire to the jacks and the switches. There’s not so many colors and I’m trying to stick with audio, gate and control voltage as the only three. When I come across a trigger jack I’m going to treat it as one of the three. Am I correct in assuming trigger is control voltage? I don’t need to know if there’s a Kosmo specification of trigger voltage but it would be one thing I don’t think was mentioned.
-Fumu / Esopus
I think of a trigger as being most like a gate with (near) zero width. Not a CV because (like a gate) its amplitude doesn’t matter as long as it goes high and then low. Really it’s a fourth thing, although in many cases a gate can be used as a trigger.
As I said I’m running with a limited amount of hook up wire codes so more so I have to pick a code for trigger. It’s running in my head as gates being the one thing of digital logic whereas I’ve not seen triggers coming across ever in logic situations. What I wonder is in the Ken Stone and Serge Tcherepnin specification would trigger have been audio, control or logic because I saw only three mentioned. To me it’s a control voltage that happens to have a very brief moment of being a pulse of enough volts to turn something on but I guess it’s a bit like sandwich internet discourse.
edit: they do mention sync at a point of being a fourth but this is quickly left out because there hasn’t been spec for in or out between the three and there’s only three proceeding
-Fumu / Esopus
A control voltage controls the amount of something, some continuous parameter from 0 through maximum (or -maximum to +maximum) — VCO pitch, VCA gain, VCF cutoff frequency, etc.
A gate controls when something occurs, from when it starts to when it ends — ADSR envelope generator attack and release for example.
And a trigger also controls when something occurs, but only a momentary thing rather than an extended time thing, or the start of something that ends on its own — AD envelope generator attack for instance.
Another way to look at it is, both a gate and a trigger indicate a binary condition: Key is down or it is not down (gate), key has been pressed or it hasn’t (trigger). CV indicates an analog value: Key is this one or that one or that one or…
So a trigger is much more like a gate than a CV.
Some of that is right in my own opinion. The fault I see is that a mixer could be interesting doing a sum of control voltages and triggers and treating them like control voltages while doing any logic gate processes purely in a digital logic of triggers and gates would have very weird jumps or nothing worth using coming out and little of it interesting. I still feel like coloring my control voltages and triggers by the same hook up wire code. I guess that’s how my modules will be different.
-Fumu / Esopus
Gate is a digital signal that is only 0V or minimum +4V or possibly +5V and is meaning a value of 0/off or 1/on. To clarify if it is used for a note remains at ‘on’ for the duration of the note and then is ‘off’ when the note turns off.
Trigger is known as a signal short enough to call it a ping. Different triggers are positive voltage or negative voltage when triggered and there are different durations and different voltages required for specifications. It is used at some beginnings of events or some ending of events but doesn’t stay for more than a ping. It’s different from a gate or a control voltage but provided maximum voltages aren’t surpassed there shouldn’t be anything wrong plugging a trigger into a jack for a gate or control voltage and experimenting.
Control voltage is a continuous signal that is doesn’t deal in events but in the analog and can be positive voltage and negative voltage. It’s sometimes specified between a positive voltage and a negative voltage but in other cases is specified to rest at neutral voltage and goes to a positive voltage. Generally it does maximum +10V.
There’s fun in trying things that aren’t going to risk having an explosion. I’ve not said I thought of something as “fundamentally” defined any way. I said it felt closer to something. As I’ve decided I’m going to go with go with making my hook up wire code put audio in one color group and gate, trigger and control voltages in another color group. No one has offered even a definition of a Kosmo trigger by timing and voltages on and off so it the fundamentals were meant to be learned then I’m open however mostly what I’ve learned is playing by ear so I’m doing that.
-Fumu / Esopus
I am going to raise the question R.E triggers and gates again, not looking for a description, but would it be possible to be more descriptive in the initial post, please. I like specifications, they mean all our modules can play together.
I can see we have a spec for gates
Reading the above, all signals < 4V should not be treaded as On gates. This threshold is higher than any logic levels I am aware of, CMOS, TTL, Arduino. This has been brought to my attention today when trying to use a 3.3V clock from the Arturia products, where some modules react to the clock, while others don’t. The main culprit was one of my own modules, using a comparator. Now while it is easy as a designer to simply use a lower reference voltage, that would not comply with the specification.
May I propose adding a line such as input: On, minimum 2V
as this would cover interfacing with microcontrollers, 5v CMOS levels, and would also respond to logic levels from 3.3v devices. This would not change the current specification as the output voltage requirement could remain the same.
It would also be nice if triggers were listed, even if the entry currently says See Gates
and mentioned V-Triggers, as this is one of the few details given by Sam on the kosmo page of his site.
Yes, there should be a distinction between the minimum voltage accepted as an “on” gate and the minimum voltage generated as an “on” gate. For maximum compatibility with non Kosmo equipment the former should be low, while the latter should be higher.
There also should be more on the subject of “off” gates than “0 V” — maximum input and output levels.
I’d say the input HIGH state should be one diode drop (0.7V) above GND, and the output HIGH state one more diode drop above that (1.4V), to allow signals to be passively OR’ed.
For the LOW state… input LOW below 0.7V, output LOW 0V?
disregard {{{{Hey I also want to add that the taydas push buttons in analogoutput’s footprints are about half the diameter as the arcade push buttons used in the original lmnc sequencer for anyone designing panels in kicad}}}}
edited: my bad i got some things mixed up
What footprint are you talking about? Which module?
Not sure what you are objecting to or commenting on. This is a footprint which is specified as for the Tayda A-3487 SKU, Dailywell PAS6B3M1CESA2-5, which does indeed use a 15 mm panel hole. It’s not an arcade button. The footprint comes from my own Kosmo panel holes library. There’s nothing particularly standard about it, the “Specification” discussed here doesn’t have anything to say about which push buttons to use, it’s just the size and style I’ve been using. When you say “twice as large as here” what are you referring to? It’s bigger than the little A-5050 ones, but those aren’t particularly standard either.