Jump to content

chriss

Members
  • Posts

    140
  • Joined

  • Last visited

Posts posted by chriss

  1. Hi.
    Has anyone a working mb909 firmware (the one from jef) for the lpc17 Core. I found the directory on Github but i am Not able to compile. ( If its compilable anyway!).
    There must be a hex file on someone’s harddrive out there. 
    thanks Chris’s 

  2. Nice work. I like that you can switch between different input voltages. Very cool.

    Last week I stumbled over the mutable instrument schematics as well. I prefer the the attenuverting scaler from the braids schematic. Should work with a MCP6002.

    Christoph.

    post-3513-0-14000100-1417112801_thumb.jp

  3. Hi guys. After some rather long baby and buchla absence I am starting slowly to collect info about my midi2cv module. Some nice progress here the last month. Has anyone build a box with a CS PCB with led rings and oleds? One question occurred yesterday when I wanted to check out the clock divider function. But I couldn't find it in the lemur template. Since I am not able to test this with the real core (and the minimal CS) at the moment, I wanted to ask if this will be implemented in the lemur CS. Or when it's already there where to find it. As you might know one of my most wanted wishes is to integrate the midi2cv into modular land. Clock input is already on the request list. Another one would be cc implementation. Then one could control the module with a cv2cc interface. (Clock speed, clock divide...... Can this be done? Does it make sense? Christoph.

  4. Hi there.

    Just wanted to report. After a heavy week and finally upgrading my seq3 with a lpc17 board, I could test this feature. I works like Thorsten described. I took an old pic8 core and installed mb64 on it, which has the 8 analog ins ready to use. Then I took a simple pot and could control the steps of the track.

    I can not say how stable but it is pretty awesome to have an analog Lfo controlling the seq4.

    Next for me is to build a proper PIC protection/scaling circuit, so that a 0-10 voltage (alternative -5/+5 volt) is controlling step 1-16.

    For the trigger inputs START and STOP it should work already with a proper transistor circuit (pulling the appropriate DIN to ground). This should work in parallel to the CS Button?

    DIN input: For the external step inputs 1-16. For example: high voltage on DIN input corresponding to step 7 jumps right to step 7. Shouldn't this work already in manual step mode? Ah. Ok only for the steps which are active on the CS. I am still thinking in 16 step sequences. So we would need extra DINs as stated before.

    Some things in my mind.

    - External clock input.

    - It would be cool to jump to an specific step and tell the Aout to update the voltage while turning the knob. Without triggering the gate output.

    - clock divider outputs.

    This is all so exiting and cool. Sadly I don't have more time and things go very slowly.

    Thanks Thorsten. Incredible features for people with analog gear.

    Christoph.

  5. it should update automatically on CV channel changes.

    Are you using the MIDI or OSC option?

    Could you please try the latest .jzml file in the SVN repository? I adapted it to the latest Lemur version, the old one wasn't 100% compatible.

    It seems that I just have one way communication. I tried the latest software yesterday and still no update. Than I thought, maybe the lemur needs the information from the core to update? But I couldn't find any info on that. And I couldn't manage to send anything from the core to the lemur.

    I am using OSC by the way. With a dedicated router. And without a computer.

    Christoph

  6. In fact I prefer Mouser to Reichelt now as with them I know what I get. Especially the handling of ICs is much better. And the orders sometimes even arrive faster than from Reichelt although they are shipped from the USA.
    I can absolutely confirm this. Just happened last week. And parts are cheaper and you have no shipping cost. (my orders usually go beyond the 65.- euro).

    There are several mini-router available at Reichelt for around 25..30 EUR

    To people who want to use the (preferred) MBHP_CORE_STM32F4: it won't provide an ethernet port anymore.

    Thanks I already have something like that. I thought there might be something really small....

    I don't think building it into the CS box makes any sense.

    You simply don't want up to 16 CV/gates from a desktop unit extending all the way to your modular. Please trust me on this. I've been building my DIY-modular for 10 years now and as your modular grows (which it inevitably does!), you'll see what I mean.

    I was building the aout in my seq3, with the jacks on top of everything (8cv/4gate). I always and still love the fact that everything is in one case and the feeling that the sequencer is controlling my synth is more intense for me. I just like compact things. And I know this is luxury but I want a dedicated aout in every midi box controller I build.

    But I didn't want to distract you from this beautiful case design. It is definitely is a strong argument to have the Aout somewhere behind the desk or in the modular and only on big data cable from the midibox to there. And to have one slick desktop case for tweaking. I am looking forward building this thing.

    I had always something like an euro/4u/5u modular module in mind. Direct put in my modular. I think it depends on how much/what you want to control with lemur and how much/what with the CS case. At the moment I am overwhelmed by the devices/boxes involved. iPad goes-> midibox cv goes-> Aout goes-> analog synth.

    Buchla is always good for inspiration post-3513-0-83042700-1387570489_thumb.jppost-3513-0-53869000-1387570545_thumb.jp

    Christoph.

  7. Crazy!!!
    That looks fantastic. There is nearly no progress in two years and then this!!!! Incredible job from all of you. 
    I really like the CS design. Well done...
    Here are my thoughts.
    - My experiences with the lemur control surface where similar to Thorsten. It is nice but not intuitive enough. And in the end it distracts you from tweaking. 
    - the main fun for me is the physical separation from iPad and midibox cv (wifi router).
    - the second main fun with lemur are the bouncing balls, the x/y pad (I did implement them in the lemur program), the motion sensor (i wanted to implement but got distracted), and of course the graphical envelope/Lfo. Drawing on the iPad is fun, turning knobs not. 
    - one thing I don't like with the lemur and I think it is implemented that way. When changing cv channels the display is not updating. 
     
    But I'm sure that people would also like to have dedicated buttons for
    - a "fast" button (for the encoders)
    - encoder bank +/- (for the case that they don't have inbuilt switches)
    - patch +/- buttons
    - Start/Stop sequencer (and arpeggiator)
    - store button to save the current patch
    - change directly to certain menu pages
     

    - definitely buttons for the 8 cv channels. 

    - standard scenario for me: do the setup and all the routings (Lfo -> envelope etc..) and save it. then play around with levels of the various function generators. 
    - so the lemur is good for setup and as a performing tool with the motion sensor and the big X/Y pad. 
    - the CS Box is good for tweaking and fine control of the levels. And we have visual feedback of the outputs via the graphical displays. The Aout needs to be close or inbuilt to the CS. 
    - Does anybody know of a small wifi - router to be build in the CS Box? 
    - CV in and Gate/Pulse in would be a nice enhancement. To sync lfo´s or trigger Envelopes from extern. CV in could be used to quantize voltages... I need to test this with an cv to midi interface...
    - And the last: Patch Morph? 
     
    Might these thoughts be helpful for someone. 
    Christoph. 
  8. Great, Great, Great. I was hoping that something like this is going to be implemented.

    Trank you so much Thorsten.

    Cool. I will either try it with MBCV2 on LPC and AINSER8, or would a PIC core also be suitable?
    Acsensorizer?..

    16 DIN pins to step the 16 tracks individually, right?
    Super. I totaly forgot that we have 16 tracks!!!

    If it's ok to assign a whole DOUT SR (= 8 outputs) for this function, I could easily add this.

    What type of clock outputs would be for interest?

    - PPQN/24 (DIN clock)

    - 64th

    - 32th

    - 16th

    - 8th

    - 4th (1 clock per bar)

    - 1/2

    - 1 (4 bars)

    Since PPQN/24 is redundant (already available at J28), it could be replaced by another interesting clock - any proposal?

    Perfect. Is this planned to be fixed or editable in UI.

    If editable I would say everything from 1,2,3,4,5,6,7.....like in the divider menu right now.

    If not I am very happy with your proposal.

    Christoph.

  9. Ha funny I was searching the whole day to get analog control over the midibox seq. but didn't found a suitable solution.

    So we need a acsensorizer hooked up to the seq. generating the CCs. Right?

    And I am with lukas412: both options would be nice. But option 1 would be preferred.

    If the trigger pulse is > 2 mS, this is feasible
    Yeah this should be possible. Running the seq from an external analog clock signal is great.

    One thing I will try next time my seq is open, is to add a analog clock to the tap tempo button.

    While we are here: multiple clock/divider outputs independent from the tracks would be awesome. Maybe some day....

    Christoph.

  10. Hi Thorsten and all others,

    thanks for your answer and help.

    during the week i managed to work on my code every day for a few hours. I found out a couple of things. First thing i wanted to build was this standard keyboard:

    http://midibox.org/forums/uploads/post-3513-0-50648300-1348235779.png

    post-3513-0-50648300-1348235779.png

    Since i could`t find anything about note_on and NRPN a tried the: Note Events: /<chn>/note <key-number> <velocity> line found at the "MIDIO128 V3" under "Supported OSC Packet Formats" page.

    oscout(0, /1/note, {value, value2}); --> sends out a noteon with the note (value) and velocity (value2)

    oscout(0, /1/note, {48, x}); --> sends out a noteon with the note 48 and x = (1) button pressed: velocity (1) (Gate high) () and x=0 button depressed: velocity (0) (Gate low). As long as the script is connected to "On Expression" and (x).

    With this i managed to get to this code for the white and black keys. It is heavily copied from the Sequencer keys and i guess is too complicated. But it works. Only drawback so far is that there is sometimes no Note_off and the gate stays high. But so far i am very satisfied by this.

    On the weekend i will scale it down for the iPhone.

    Next will be the Multiball elements.

    Christoph

    decl changes = nonnull(x - last_x);

    decl i;

    decl cv_2 = '/8/note';

    if( selectedCvChannels & (1 << 6) )

    cv_2 = '/7/note';

    if( selectedCvChannels & (1 << 5) )

    cv_2 = '/6/note';

    if( selectedCvChannels & (1 << 4) )

    cv_2 = '/5/note';

    if( selectedCvChannels & (1 << 3) )

    cv_2 = '/4/note';

    if( selectedCvChannels & (1 << 2) )

    cv_2 = '/3/note';

    if( selectedCvChannels & (1 << 1) )

    cv_2 = '/2/note';

    if( selectedCvChannels & (1 << 0) )

    cv_2 = '/1/note';

    decl value;

    decl whiteKeys = {0, 2, 4, 5, 7, 9, 11};

    for(i=0; i<sizeof(changes); ++i) {

    decl ix = changes;

    if( x[ix] ) {

    decl oct = floor(127*StepValue.x / 12);

    decl value = 12*oct + whiteKeys[ix];

    StepValue.x = value / 127.0;

    oscout(0, cv_2, {{value}, x[ix]});

    }

    else {

    decl oct = floor(127*StepValue.x / 12);

    decl value = 12*oct + whiteKeys[ix];

    StepValue.x = value / 127.0;

    oscout(0, cv_2, {value, 0});

    }

    }

    last_x = x;

    post-3513-0-50648300-1348235779_thumb.pn

  11. Hi all,

    since on year I try to get some buchla modules done, but unfortunately things go slow. One module will be a midi2cv module. So I follow this thread since the beginning with a lot of pleasure.

    Last Christmas I got the iPad2 and I use it a lot for music and all sort of things.

    Since I got an lpc17 core module for my seq4 and an old aout cv interface ( max525) I was very happy to see this development here with the new midi2cv module.

    I bought lemur (most expensive app ever) and tried the new midi2cv v2 app trough the websvn. It worked very unstable like described in an other topic, because of an broken aout driver. I waited a couple of month (went to china in the summer) and then Since the last update it works beautyfull and it is absolutely incredible to sit in front of my modular and have my iPad in my hand and control CVs, without any cable. Very nice. Thank you Thorsten for that experience.

    After some time playing around I thought it would be nice to play with the multiball object which is inside lemur and to have a simple keyboard.

    I looked at the code inside the lemur midi2cv file and figured out some things. But as so often not enough. Multiball is sending data to the same address as the octave knob for example. I works but not nice.

    I am absolutely at he beginning to dig in but I don't understand this whole OSC NRPN thing. I just don't know what the core understand. And because i have a hard time scripting as well we understand each other not so good.

    I found nothing in the forum about this so I need to ask here and hope for support. At the moment I am really stuck at the point to program a button in lemur which sends a note_on to the core which updates the cv of channel 1 and sets the gate1 high.

    Thanks for all your enlightment in this matter.

    Chris

  12. Hi Thorsten and all other midibox addicts,

    I just wanted to report that after one year I am still in the planning phase of this thing. I did some tests with the switching and got some nice results with simple fet circuits. All other tests (CMOS) always did some nice klick. Klick less switching is really not easy. Still a little bit frighted by the amount of switches this thing need.

    Unfortunately my plans got crossed by another project (buchla clone) witch need all of my small amount of time right now. (besides money jobs, child's and girlfriend).

    So I have not killed this project. Just to let you know.

    chriss

  13. Hi Thorsten,

    thanks for your help and code. Thats absolutly awsome.

    I did a quick compile yesterday, but could not test the J5 port. Need to solder the pins for the J5 and the switches. And then my little daughter woke up....

    So next days i will order at reichelt and mike. In the meantime i can test more.

    And i will create a blog on midibox.org.

    thanks again.

    chriss

  14. Hello all,

    I am trying to build a stereo synth with analog oscillators and filters based on the Midibox SID V2 synth.

    To get all the required CVs i use the mbnet buildi n function of V2. I know this is quite unusual and maybe too much around the corner....

    So Core1 handels the VCF (L/R) and VCA(L/R) CVs. Core2 handles the pitch and PW of OSC123 LEFT, Core3 the pitch and PW of Osc123 RIGHT. The cores are always selected and run from the same patch. I have tested this with two AOUT modules and it works very well.

    The only thing what spins through my head since 1 month is to get the state of the filters (LP, BP, HP), the state if OSC 123 are routet through the filter and the waveform of the oscillators out to the J5 Port. So i can add digital controled switches.

    i know that it is already possible to access the J5 through the EXT menu

    o 8 external switches can now be connected to

    - DOUT shift register (-> DEFAULT_EXT_SWITCH_DOUT != 0)

    - port J5 of the core mode (-> DEFAULT_J5_FUNCTION == 3)

    The switch states are stored in the patch structure, and

    can be accessed via Control Surface (EXT menu) or via Parameter Change

    (NRPNs/Knobs/Wavetables)

    But that would make it impossible to have control over the waveform from six oscillators from different cores.

    I also know that it is possible to get the slide and accent flag out to the J5 and that this is done in the main setup and is unique for every core.

    But looking in the code i can not figure out how to do. I am just not skilled enough.

    The question is if this is even possible?

    Maybe someone can help me.

    thanks so much

    chriss

  15. Hi Thorsten,

    thanks for the fix.

    In the meantime (actually yesterday) i swapped pics and tried it with v1.0.

    And there it worked.

    But compiling the software for my CS without the magic "make" took some time.

    Now i am very happy.

    And thanks for this wonderfull piece of software, hardware and community.

    Chriss

×
×
  • Create New...