Jump to content

Psykhaze

Members
  • Posts

    311
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by Psykhaze

  1. 2. Find here two schematics of Power Supply, one schematic for the negative voltage (-5 V to -18 V so ok for -15v):http://www.sonelec-musique.com/electronique_realisations_alim_simple_010.html Edit: I found a better schem for a +15/-15V symetric alim : it says +16,5/-16,5 but you can correct it by using a 230VAC>15VDC Transformer in input, and as well as +Vout (positive) = 1,25 * (1 + (R3 / R2)) -Vout (negative) = 1,25 * (1 + (R7 / R6)) You have here, R2=R6=120 ohms and R3=R7=1320 ohms (1100 + 220) for good values. The total Current is 4A so the transformer needs to be 90VA. Quite nice power supply=) And for the positive part from +2,0 V to +28 V (ok for +5V and +15V) :http://www.sonelec-musique.com/electronique_realisations_alim_ajust_011.html Edit : this schematic is better for +5V : Input Transformer 230VAC>9VDC,U1=LM7805 and R1=220 ohms Current Output : 1A He tells the resistor value to have depending on the current output voltage you need.The current output is 2A /3A per supply,should be good Hope it will help, feel free to ask questions 3. Yes Like That 4. Yup 5. Seems a good answer to me too. Knew we should ask him =) . Aout_ng is the most efficient module to deal with analog signals outs ,it has a higher resolution and that will avoid things like splitting signal on two register =D
  2. That was my point about the KiCAD section. First, having a custom central shared midibox library would be a really good thing. Why? That would avoid problems on default unconnected pins for example,or errors on footprints used (thanks to @Sauraen that explained me why he recreated his libraries each time due to some default pin errors on KiCAD librairies) . A common shared library is a good thing. That allow peoples not to loose hours searching for the good footprint and selecting the wrong one or recreating pin layouts. And that will allow people to correct the library by parts if we are some to deal with. To me, it sounds a bit essential and a good practice to do not loose time doing the things twice. If the Library part we all deal with at the start should be reduced, could be good =) Maybe some peoples who find PCB Design too hard could get into it if they can open a specific KiCAD library with all components used in the midibox project at the current time, and check some right designed Video Tutorials (There is already a lot,but a midibox sized thing could be good) I am wondering more and more about making some MidiBoxHowTo Youtube videos about KiCAD and FreeCAD . But my spoken english isn't as good as my writing... Text comments are ok? ^^
  3. Wouha, i was answering another thread and you answered while.=) cool to see that KiCAD is a point of interest ! That was a little troll , not to be psycho but to see if peoples are interested in the end. As well as tomorrow i will get into PCB design with TR-606 BD/SD modules, i could in parallel start filling a KiCAD Section on the wiki, SmashTV has made me an account. Filling this section will allow me to make the point about what i know and what i don't. My initial question was : Where to create this Wiki Section?
  4. I knew you would have some good news from your secret's bag @Latigid on :D Maybe you have a higher res schematic to share for your CV scaler? (maybe the design not all finished yet?) Always here for a good advice anyway =) ! . Personnally, my point is in here understanding deeper how analog drum modules works,not only saving money and time (That's kind of the contrary in fact ) This way i'll could reproduce some similar sound designs with my modular
  5. Gave a quick check about the schematics, didn't did it really yet. 2 pages are interesting to us from the TR-606 Manual So this is the global Schematics of TR-606.To summarize by concepts i've understood from now: BassDrum : Inputs : Accent + Trigger --- Concept : 2 oscillators mixed Snare Drum : Inputs : Accent + Noise + Trigger --- Concept : Envelope Generation to control Oscillator Attack and a VCA. This VCA, itself driven by the input noise drives a High Pass Filter. An oscillator got Attack modulated by the envelope and we mix Oscillator output with Noise Modulated HighPass Filter HighTom/LowTom : Inputs :2 accents + 2 trigger + Same Noise as Snare Drum --- Concept : 2 Oscillators driven by the same Trigger,wich also drives an envelope generator. This envelope generator modulates each oscillator attack to get the high and the low tom. Low tom oscillator output is mixed with a VCA low noise modulated (through a Low Pass Filter wich got the noise source on input) Does not plan to make the High Tom /Low Tom with Snare and Bass Drum but that will give me some challenge to add it later .Not add so much more difficulty expected as well it already share some with snare drum like the noise source ^^ So here is my parts concepts. Quite simple compared to yours @Phatline , the Cymbal and Closed Hat are quite more complex and you already did like almost the big part =): Cymbal : Inputs: Trigger mixed with Common Accent to OH/CH . Concept : 6 mixed Oscillators driving 2 BandPass Filters.These Bandpass Filters are driving 2 VCA. These VCA outs got High Pass Filtered and mixed. Closed/Open HiHat : Inputs : Trigger mixed with Common Accent to CY + Bandpass filtered out of the 6 Cymbal Osc. Concept : A VCA got twice envelope modulated by the outputs of the 2 envelope generator and the output of the VCA got High Pass filtered. I'll print this pic to first get my BD/SD colored each one with a different colored stylo.That will allow me to isolate only the needed circuitry and understand better the how of these explanations, eg to link the components wich are from my BD/SD parts and the others... And as well as we are going to make 2 PCB, one for CY / CH / (OH?) and another PCB for BD / SD, we will have to buld a noise source for each PCB. Maybe it will allow to explore new things with a different noise for these 2 parts.Or if we want these parts to work together,we could link the second PCB to the first PCB Noise Source,if we want to get close to the original sounds while playing BD/CY at the same time for example (ok it is a noise source but in the original concept the noise is shared) I'll make a list of nice parameters to modulate to explore new sounds and link it to the schematics. But tomorrow, it's becoming late ^^
  6. Everybody don't care about KiCAD, so let's delete this thread ^^
  7. i re quote here =) From Core32 Ucapps Page : So using on board DAC will cause conflicts with SD/ Midi Interface. We can don't care about it , or using serial registers. It sounds better to me,moreover for this resolution =) 74HC595 & 74HC165 have a 8 bit-wide resolution, wich give you from 0 up to 254 value per adress, so twice more we need =) if still steppy, we can use 2 registers adresses instead of one per parameter to increase definition : the trick is filtering/mixing signals to keep each register working with a half (high or low) range part of the signal. If Amplitude scaling necessary to bring back the signals to the correct voltage , could be done trough a classic amplifying OpAmp setup (like mcp6004) Hope it helped
  8. @Phatline Ok , just downloaded the latest 606-cymbal.zip ,i give it a review tomorrow. 1. Original Mixer with output stage sounds good =) 2. I have few bipolar +15/-15v power supply schematics. and circuitry to convert +15V>+5V . Tell me exactly what you need and i'll send you some by PM if needed to let you have a review. =) 3. After making my mind, i think modular things is about keeping the range of possibilities opened. Using a stereo jack would mean having Y Stereo to Mono to control both BD&Snare. Not quite easy in all configuration. So i think having 2 jacks to connect to pinheaders would keep the modularity at it's best. There are 90° angled pinheaders for Perpendicular assembly on Female DIL Sockets if we need/make a small pcb for "each drum" Panel , that would allow to keep the analog drum circuirty away from the front panel ( i mean not having them in a same PCB) and keep the zero-top the direction you want. Or we could go on Panel-Mounted Potentiometers, but the trick with these components is having the zero-middle on the right direction. I mean if things are vertical, "Potentiometer's Top" will be on side (get it?). To me the easiest way is to have a tiny PCB for each drum part, with trough hole potentiometers soldered on it. Then having a DIL female socket on the back of this little Control Surface PCB, and the analog drum circuirty connected to it with angled Pinheaders on the back. It will allow small width modules for each part,like the Tiptop Modules, if you are in eurorack size. 4. I was just wondering about the idea of using something simple - in a brainstorming mode . Midi triggering has been done few times using serial registers and a core8, so in order to do not "recreate the wheel" (that's a french expression) i just told about it. Maybe there is no work in programming : This case using a core8 could be fine. But using a Core8 isn't easy. The best solution , even in rate of quality, price and programming is the new Core32 .I need to dig about it as well as i only cloned mios32 to my github. But i expect we won't find what we need exactly and will have to code. If some new programming has to be done,i've been proven many times that Core32 is really more usable in the end. Moreover, It will allows other users to eventually add new features etc... 5. I've been told that the On-board DAC are not quite on top. I think using Serial Register ICs could be a good solution (to me), having a "fixed register" table sounds more easy to handle in programming . From Core32 Page : So using the on board DAC will make conflict with MIDI/SD Interface. Really think using serial registers at this level will be clearer @latigid on has a concept for scaling CV signals to TTL levels by the way( >0-5V) . that's Here : CV scaling Concept by Latigid . He apparently works hard (when he has time) with TK on the CV concepts V2 from what i understood. He looks quite skilled in electronics , maybe his advice would be a good point as well as he already got me back in the right direction few times, which I thank him for it. Let's ask him for some piece of advice =)
  9. Hallo, ich spreche kein Deutsch , außer mit Google-Übersetzung . Gibt es ein Thema in englischer Sprache auf diesem Avr Wave1 Synthesizer ?
  10. Thanks @Hawkeye . This time it is not only for audio signals, it is to extends my electronics instruments and do real work with it. So if it needs the money to be correct, it's ok to me. May you to advice me a double trace oscilloscope kit like the DSO 138 in size , at the best quality/price rate you think? To make my 2*3 inputs display (synced),i will go on my idea doing this with midibox and my MCP3428 :p But i need correct instruments for troubleshooting my audio signals and some basic digital signals first. Edit : For real work oscilloscope , the DSO203 is going to be my next tool !
  11. Hello ! I am thinking about buying a double-trace oscilloscope kit DSO138-like to extend my Single Trace Vacuum tube Oscilloscope. Will be useful for a lot of debugging ,including this 3inputs+1sync midibox scope viewer :D @Hawkeye May you advice me? @latigid on Maybe you have something to advice from your secret's bag?
  12. That's was more about the song lyrics , "it's a love story between my genesis and me"
  13. I couldn't Resist posting this, find this is quite in the subject =)
  14. @Phatline You are reproducing TR-606 ? Wich modules ? I am interested in working on 606 BD/Snare/Cymbal/HH schematics even if my level in KiCAD should be inferiror to yours. Have you got a link with original Roland 606 schematics? please contact me via PM =)
  15. @latigid on Hey, this is a quick out-of-the-box design but sounds cool for CV scaling. Thanks for sharing ! Keep me tuned about your tests.An amplifying-alike design would have to be made to adjust Audio inputs. I will try to design something with 8 inputs (4*Audio+4*CV) / 2 ADC (ADC Audio + ADC CV). I thought about I2C because i did not see why a MIDI I/O should be useful for this app . The point about using midibox in here is the big display size option / using a custom multi-inputs ADC / Building a Control surface on a known platform wich could suit. @lis0r Using multi input may allow to be able to sync with fundamentals i think Once Again,thanks for your interest ! Greets, Jerome
  16. Hi guys ! @Hawkeye This DSO138 kit is really great for the price! Just it only has 1 input.. But should do the trick in many situations , i will think about ordering one at least for electronic troubleshooting . @latigid on First, zeroScope sounds nice ! But did not found the schematics :( I've been looking a bit on mouser about ADC at a reasonnable price and , even if not PDIP , found this one : MCP3428 (it's a quad input one with correct definition and trough I2C should be quite quick) Was thinking about normalizing input levels trough an OpAmp setup with adujstable gain (from dividing to multiplying). To offset the signal , mixing(adding) it with an OpAmp to a DC signal sounds ok? Thanks again for your advices ! Jerome
  17. Hello everybody, These are some design Questions! I was wondering about assembling some midibox modules to achieve a little graphical ocilloscope to watch my audio/CV like in this vid : https://www.youtube.com/watch?v=utr23hp2nRM (like on the 4 OLED screens) - I think a great part the work is already accomplished if TK already realized that. Am I Wrong? - What is the exact voltage range of the Core32 DACs ?. Edit : From The Ucapps Page STM32F4 Core module : 0-3.3V for native ADC From AINSER Module Page : 0-5V - Audio Inputs Should be ok for Core32 DACs/AINSER? What about bipolar voltage?And if i have "high" voltages like for example +15/-15v , is an OpAmp setup with dividing gain of 3 ok to reduce voltage range to -5v/+5V? - What is the biggest resolution and screen size that MIOS32 already supports? (i was expecting a 5cmx5cm wide 256px*256px monochrome display or something like that) - Is the combination of Core32+AINSER8 is modules enough to support 8 analog inputs (audio/CV)? I also thought Few DIN/DOUT Serial Registers may allow to have a little Control Surface to switch between inputs and make few changes about display calibration. Please correct me if i am going in a dead end way =) Thanks in advance for your advices! Greets, Jerome
  18. Wow @Hawkeye didn't knew about your musical work and setup. oO Very cool ! Keep it going =) greets Jerome
  19. @Sauraen Juce API www.juce.org is really nice about handling MIDI. Maybe with http://www.vgmusic.com/ you could find your midi files? Regards, JK
  20. @Sauraen Your leviathan control surfaces are really awesome =)
  21. Psykhaze

    RGB hue sweep

    My words were confusing, i now understand better the principle of serial chain color driving through the code. So to drive for example 64 LEDs you just need a chain linking them to CORE32 J4B.SC! Wonderful =) That's pretty nice for PCB routing ^^ I talked about matrixes because that's the way i am going to dispose my LEDs physically. And the current most efficient way to drive an amount of monochrome LEDs is matrix shift register design. At the beginning thought there would have kind of differents buses to handle or similar things to shift register design. And that is very good about default params i was planning to use 64 RGBs APA 106 LEDs =D Thanks for your answer Thorsten =) Best Regards, Jérôme
  22. Psykhaze

    RGB hue sweep

    So, how to connect these WS2812/ APA106 leds to CORE32? is it possible to drive a rgb matrix ? best regards, JK
  23. Wow cool job you've done here @Ixox . Pretty nice design, from the PCBs to the Case . +10 ! regards, JK
  24. I admit 16x8 may sound big,. But what can do most can do less ? And this chip is DIP, that's kinda difficult to find CP switches in this DIY-friendly format working with 5v. Matrix would allow to make like some "patching fun" by routing the signals in different inputs/outputs, driven by core. On some matrix outputs you could have some traditional filter design like HP/LP/BP and on other one outputs some mixing setups. Plug your audio synth modules outputs to this and reroute/filter your signals in the funny ways you want, that was the "concept". If you think this chip may sound ok, i could start a raw design upon this. (Still making my mouser order list, think will order one of these CP switches to experiment on the protoboard =) ) Thanks for answering, Best regards , JK
  25. Hi @Phatline and thanks for the answers. The piezo linked and was choosen to fit as possible to the hardware you have choosen in your bongo trigger design. But your size sounds better ^^ as well as akai pads are 30mm wide. This way we could exchange about hardware design notes and experiments. I was wondering about some piezo , because i am making a mouser order list. The feedback loop was choosen to give more hardware designs possibles, and you mentionned one =) Stand base will , as you said, have to be heavy like in reals akai. But about vibration management, i think silicon could really help. In back like in front ^^. I'll keep you tuned about my expermients in silicon buttons moulding and velocity sensoring with piezo . good evening, regards, JK
×
×
  • Create New...