Jump to content

jrp

Members
  • Posts

    199
  • Joined

  • Last visited

Posts posted by jrp

  1. Yes, this is a good idea. ok, full level controll is a nice thing to have, but in most cases it´s not really needed.

    What i don´t like about the two bit solution is the handling. Programming would have to be done with a combination of different note ons for each sound and volume. Not that intuitive.

    When playing the drumbox from a midi keyboard or pads it´s much more handy to have it respond to one (or two) note-ons and the midi-velocity data.

    So the midibox-cv is the most flexible solution.

  2. Been reading about the midibox fm

    nice project! Like the idea of recycling old soundcards.

    Like to recycle all kinds of parts from old broken stuff.

    Now for those of you who don´t have smd skills, like me:

    Instead of desoldering the chips it is often possible to use a saw and cut out the whole chunc of pcb together with the chip.

    This will not always be possible, but it has already worked for me in some cases.

    If the pcb has many layers that can be a problem, as you want the traces correspunding to the pins on the top. have to measure to see if and where that´s the case.

    Soldering wires to the pcb traces also isn´t that easy, but there is no danger of damaging the chip, so you get a few tries. Of course, if they are really close this won´t work.

    Maybe it´s even possible to cut the part of the pcb that contains the fm and dac chip in one, maybe even with the output opamp. They are propably already connected the right way.

    Often complete circuit blocks can be recycled, like output jacks with opamp drivers, input buffer/amplifieres, filters, etc. I have already used this methode to saw out a complete discrete psu- voltage reulator from an big pcb. Worked perfect!

  3. took another look at the core schematic. For the lcd only 11 of the 16 pins need to be switched.

    no need to switch power, ground, brightness.

    Still that doesn´t change the general problem...

    Ok, the easiest would be to have a configuraten for the cvs that rarely needs changing. Guess that´s the case for most users, but i´m not sure about that.

    Then it´s within reason to open the box from time to time when something needs to be adjusted,

    and switch the connectors by hand. no soldering, no cost.

  4. Do you think there is a reasonable way to do this?

    I´m planning a seq3 and two midibox cvs.

    Since the cvs don´t need to be configured often, since it should all be housed in one box, share one psu, since lcds are expensive, since panellspace is limited, i had the idea to share one of the 40*2 lcds, two buttons and an encoder from the seq.

    Have a button to switch them to one of the midibox cvs when i need to configure them.

    Only way i can think of is to use lots of transistor switches or and gates...

    Don´t know if it´s reasonable or even possible.

    It would certainly lead to a lot of soldering, but if it´s managed i imagine this to be very handy.

    What do you think about this?

    Can a lcd be driven from a transistor switch instead of the core itself?

    Is there a more elegant way than soldering 60 transistors (16 for the lcd, 4 for the buttons * 3 core modules)?

    How about cmos and gates?

    Say we look at the first pin of j15. It goes to an and gate. The outputs of 3 andgates (from the three first j15 pins of the three cores) are diode ored with a pulldown r and drive the lcd.

    Would lead to 15 quad and gates. Also quite some effort, but the frontpanell would be much more handy - and that´s what counts in the long run!

  5. the midi2sds is just perfect for the job, problem is the controller...

    On the other hand, a midibox cv can be configured to do the same (i think).

    On one midi chanell you would have to set split zones for one key each (or two keys, it´s easier to play say an hihat on the keyboard if you have two keys for the same sound - play with two fingers)

    Guess i´ll build two midibox cvs for my setup.

    But thanks a lot to all of you for giving me some thoughts on this!

    cheers

  6. On the midicv project page it sais under note handeling:

    MIDIbox CV provides an individual note stack for each channel

    It´s not clear to me if those are midi channels or output (cv) channels.

    Eg, it could be useful to assign two cv outs with different note handling to the same midi channel.

    Take the egs from music from outer space - they have gate and retrigger ins. So one cv channel can be assigned to mono - going to retrigger,

    the other channel in legato mode providing the gate.

    i guess this is possible..?

    cheers

  7. Hi

    silly question, but i admit i don´t know how this is best done:

    For easy assembly and troubleshooting it´s propably a good idea to connect modules with plugs, instead of soldering directly.

    Never done this, though.

    Any hint what type of connectors will fit on the little sil headers on the core or the other modules?

    thanks!

  8. I have been reading through the manual again.

    As faar as i understand, it would be possible, without changing any code, to get the desired effect. 3bit velocity controll. Or 1bit, anyway, those 48 triggers are more than enough to "do something"

    A Track running in mode3 - predefined chords (can be user defined, right?)

    That track is routed to Aout, ch16.

    Just as an example, lets say the first 3 triggersnotes of the 48trigger dout chain are midinote 10,11,12

    A chord of these three notes will make the lodest hit, a chord of say 8,9,10 with note 8,9 not defined will make the softest note.

    I´ll have to see how good or bad, how intuitive the handling of this method is in reall live.

    If we take a step back and say two trigger levels are enough it should really be ok.

    Two midikeys for each sound, one hard, one soft.

    And thgen there still are the cvs, so if a sound "needs" more controll i can always plog in another vca (in a semimodular systerm)

  9. That sounds like a cool idea. Yes, two or three levels would be enough. Easiest would be to just hit two notes at the same time, or build the drummodules so that they have different trigger ins, for different levels.

    Thorsten, I can really understand what you are saying. I was more or less thinking loud - hoping that some other people share the same interest.

    Of course i wouldn´t expect someone to write me a personall version.

    And i also see that most of the troubleshooting, adding new features and stuff ends up with you doing the writing.

    My biggest respect for that, for this webpage. For sharing all of this. Your DIY Philosophy is really great.

    Again, i can understand that posts like this sound to you like: Hey, i´m new, i have a special problem, please tk do the coding for me...

    Nix für ungut!

    BTW, it´s not about saving a euro, but about saving the cvs for where they are really needed: Controlling filters, vcos, etc

  10. As described in my other posts, i want to use the seq3 for my analog drumbox (and more, of course).

    The drums are to be triggered and velocity controlled.

    Do you think there is a (reasonable) way to do velocity controll with the trigger signal itself?

    Instead using a logic trigger and a cv for velocity im thinking of pwm to get different voltage levels of the triggers.

    I have no idea if this is possible. The trigger is short, so the pulsing would have to be fast.

    Say velocity 128 gives you a full positive 10ms trigger.

    Velocity 64 gives you a trigger with an 50/50 pulsing (for 10ms). When charging a cab (in an release envelope generator) the resulting cv would have half the level of the first case. This would make velocity controlled drums possible, without the need of an aout.

    This could work i think (it´s like in the switched cab filters, eg) but i´m no programmer. I don´t know if this would lead to changing one line in the code, or reprogramming 1000s of lines...

    Cheers, jens

  11. Hi together,

    just wondering if this is possible. Maybe it´s already discussed or already a feature, but i didn´t see this anywhere: In the manual is said that a pattern can be dumped as sysex. Is it also possible to dump the "whole thing", patterns, configuarion, midi routing etc into the (PC)sequencer as one single dump? Without affecting internally stored patterns?

    This could be useful to save everything with say an cubase song, without the need of placing the patterns on a bankstick. I would save those possitions for the good beats i want to take with me when playing live, or when jamming without the pc.

    In the studio it´s quite handy to have it all stored in one file (of the audio-sequencer)

    cheers

  12. Hallo Thorsten

    Vielen Dank! Yes, this is what i´ll do. I already thought about that it would be nice to have a midibox-cv with the possibility to generate gate and trigger signals for legato mode.

    Yes, this will be the best solution for my setup.

    Changing the code to velocity is good when it comes to controlling the drumbox from a keyboard or midi-drumset.

    BTW, the more i read around here the more excited i get! What you have created here is one of the most fantastic pages i ever discovered!

  13. Yes, i can imagine this. First thing i would try is making the resistors a lot bigger than 47k. Don´t know..

    As about the code, i´m sorry, but if not in this forum i will never find out what changes have to be done.

    The only programming i ever did was with gw-basic about 15-20 years ago...,

  14. and another thing i couldn´t find out:

    for 16 cvs, do i really have to build a complete midicv box and make the connection via midi?

    No way of adressing a Aout module instead of one of the 4 IIC Midi?

    Or build a midi cv with a second core and connect it to the seq core directly, without the midiout module, without a midi cable?

    Can´t wait to finally placing my order of pcbs...

  15. Those are many questions, yes, and some i could answer to myself with a little effort.

    ´Right now i´m trying to get through the Aout behavior explained in the user manual.

    As i said above i want to trigger gates and velocity to controll a drumbox.

    If i got this right it would work to set the event to 1= single note, the chanell to 1-8 and the output to aout.

    Then i could use the triggers to trigger the drums and the keyvalue to generate a cv that controlls the volume of the analog drum.

    Right?

    In the aout midi encoding table:

    When event is set to cc, what does "gate ... always set" mean?

    thanks!

  16. Hi

    I´m thinking about doing my own touch sensors instead of buttons for my yet to build seq3.

    I guess it should work here, but i´m not sure so i´m asking.

    The type i´m thinking of is like this: The Din has a pullup R. The "button" is nothing but a smaal pice of copperboard with a very tiny cut between it´s upper and lower half. One half is connected to the input, the other is connected to ground. A finger touching this sensor will close the switch.

    Anyone tried this with the din module?

    The pullup resistors should be larger than the 10k on the board. Maybe 500k. Is that a problem to the module?

    Will it start to get unstable?

    do i need cabs to protect the switch against multiple trigger? i noticed that the layout for normal buttons doesn´t have any cabs.

    If worked nicely this could be a cool, futuristic way of playing the sequencer, and it costs almost nothing.

  17. Hi together

    It´s great that all the parts for the projects are neatly listed in txt files.

    It´s possible to save public baskets in reicheltl. I did this with 16 encoders in my basket, just to show those who don´t know. named it encoders an clicked public. I got this link:

    http://www.reichelt.de/?ACTION=20;AWKID=9667;PROVID=2084

    when you are logged in you can add these to your basket. If you are not logged in you can still order the saved basket, without being able to add more of those.

    Has anyone made such baskets for the modules from these pages?

  18. Hello Together!

    First of all, since this is my first post: This site is fantastic!!!! It´s a dream come true for the diy-er. And my biggest respect to your philosophy: Open source, non comercial, diy!!

    Ok, i´ll get it on and bring midi to my analog gear. I have been building compressors and a big modular synth till now. that´s me: http://www.myspace.com/petrolvendor 

    Right now i´m working on a nice drumbox.

    I read through most i could find, but some (propably obvious) questions remain...

    1. I would like to have more than 8CVs. I already found that you can have many gates, but with cvs this seems different. What i want to do: Controll my 8 Voice drumbox with trigger and volume (velocity)

    Controll a monosynth with pitch, cutoff and volume, gate

    Controll my modular with pitch, cutoff and volume, gate and trigger (for legato gate with env retrigger)

    That makes 14cvs and 11trigger/gates...  make that 16/16 - for the future...

    Would it work to build a midibox-cv around a second core? they could be just connected via midi. Or is this where core link comes in (have to read through those texts again - i don´t feel like an insider yet when it comes to digital electronics...)?

    I would like one AOut for the tuning critical voices and 4 AOut_LC for the velocity cv for the drums.

    2. Can the sequencer itself controll that many outs in the way i want it? i´m not sure how all those layers, tracks, etc are organized... 64 midi events in parallel, that´s a lot. I know this is propably all in the manual, but to the newbee the obvious may seem quite unobvious... sorry

    3. I would like to be able to controll the drumbox/synths from the seq, or from the computer via midi. Seems like this is possible.

    Is it possible to have one cv out controlled by the sequence, another one by the midi in? It is said somewhere that the seq can replace a midi-cv, but not if it can do both at the same time...

    What i mean is like having the 8 drums being played by the seq while playing another analog synth from a midi keyboard.

    Maybe i could then have a softsynth playing along - driven by the seq-midi out?

    So many wishes...

    4. I propably just overread this: The seq can sync to midiclock and output a sync signal (for my cmos analog sequencers). Does it also have a clock of it´s own, when running standalone? With shuffle? Oh god, this is so cool!!!

    If all this is possible, then i must say marry xmass! fantastic!

    If it isn´t i´ll have to arrange...

    Oh, ehh, i never did any programming... I´m going to by the pics preprogrammed from mike. So i have to tell him i need the gates on j5. Anything else? Do i have to consider anything when chaining a seq and a midi-cv?

    manny questions, i know...

    people, i´m excited, this will be my first steps to microcontroller land...

    Thank You for sharing this and helping!!!!

    jens

×
×
  • Create New...