Jump to content

findbuddha

Programmer
  • Posts

    267
  • Joined

  • Last visited

Posts posted by findbuddha

  1. For sale is one whole heap of midibox related stuff. I’ll try to describe what’s available but I’m not for example going to count ~500 LEDs to give an exact number. I’d love to sell this as a bulk pack and as such the price I’m asking is obviously considerably less than what I payed for everything. I’m happy to remove components eg. the motorfaders and LCDs from the chassis if you don’t want the chassis. Documentation and design files are available - the original plan was a SeqV4+16x16BLM on left, and motorised mixer section on right. Along with the main components listed below there is a plethora of connectors, resistors etc.

     

    Price is $300AUD for the lot, plus shipping.

     

    Highlights of what’s available include: 4x (2x used, 2x unopened) Optrex character LCD (805-51850NFQJLGACN); 16x RSAO11M9 motorfaders (installed in chassis, never soldered); 1x full LPC17 (kit+PCB+LPC17) (unopened); 2x MF_NG kits (unopened); 3x Core8 kits (various stage of completion, PICs unopened); 2x Core32 (completed / used); various DIN/DOUT/SDcard/ETH kits (various stages of completion).

     

    Thanks for looking, feel free to ask any questions :smile:

    post-6793-0-76457400-1405409068_thumb.jp

    post-6793-0-75401400-1405409075_thumb.jp

    post-6793-0-69092800-1405409082_thumb.jp

    post-6793-0-83718500-1405409089_thumb.jp

    post-6793-0-80632800-1405409095_thumb.jp

    post-6793-0-47027500-1405409102_thumb.jp

    post-6793-0-14272700-1405409108_thumb.jp

    post-6793-0-03466200-1405409114_thumb.jp

    post-6793-0-50067200-1405409165_thumb.jp

    post-6793-0-13933400-1405409170_thumb.jp

    post-6793-0-24240700-1405409176_thumb.jp

    post-6793-0-76328100-1405409181_thumb.jp

    post-6793-0-95274300-1405409187_thumb.jp

    post-6793-0-11264600-1405409193_thumb.jp

    post-6793-0-27842700-1405409205_thumb.jp

    post-6793-0-17209400-1405409212_thumb.jp

  2. Hey there, hope you saw this 

     

    - blm-scalar.* contain an error. Pins I4-I7 are mirrored. This is easily fixed with a connector modification, and the blm-scalar module seems to work as intended. A corrected but currently untested file is separately available below.

     

    on my wiki page before ordering  :happy: 

  3. Here's a nearly fully functional Seq remote control for Lemur. It's early days yet, but LED, encoder, button and LCD are all working acceptably. Encoders are set for drag up and down to change.

    This required some slight mods to the SeqV4 app. I have included a compiled .hex based on the latest svn, as well as the modified source files. My edits are marked: "edited" in a comment.

    Beyond the mods to get this to work I've also changed the BLM handler for Lemur-BLM users: shift+extra column now selects parameter layer in grid mode. I think this may clash with hardware BLM users' shift+extra column - there needs to be a reliable check for hardware vs. software BLM.

    Issues:

    - Special LCD characters from Seq are not available at current, they are replaced with an empty space.

    - Any UI page with high update rate + content (like exit page while playing) results in large sysex output -> increased CPU usage + bandwidth. I may have to reduce update rate similar to what I did with the LEDs.

    - LCD text is slightly misaligned, I've asked Liine if they can provide a monospace font option to solve this problem.

    Instructions:

    - Import the .jzlib files to your Lemur layout. seq.jzlib is mine, blm.jzlib is TK's BLM layout.

    - Requires a spare midi port to the Seq. I'm using USB3. Select appropriate midi port in Lemur ie. MIDIIN3/MIDIOUT3.

    -- Select the appropriate midi target number in Lemur. TK's BLM layout uses Midi target 0. This layout by default uses target 1.

    -- To alter: change variable midiTarget, and the target for both scripts onNRPN() and onSysex().

    -- You may need to reboot seq and lemur to get the setting to switch if it doesn't seem to be working.

    - The pins and shift registers need to be configured to match your MBSEQ_HW.V4 file. I have included mine for reference.

    -- Edit these in the receiveLED*() and initBtnPins*() functions.

    -- You can add your own LEDs/buttons as you wish. There is a limit to the length of a function in Lemur so you may need to add more receiveLED and initBtnPins functions.

    Future ideas:

    - Change encoder sensitivity?

    - New layouts, direct editing of parameters. This is a proof-of-concept mirroring my hardware as much as anything, and I'm sure it can be improved upon.

    -- I've developed a framework for direct editing of all the parameters of the tracks ie. channel, gate, note, velocity etc.

    -- I'm not quite sure, however, what the best way of laying that out in Lemur is. I'm yet to think of anything more functional than the BLM.

    --- Maybe a 'channel strip' beside the BLM?

    Enjoy! flowers.png

    fb-remote-seq-0.1.zip

  4. Hi, no luck with the MEC.

    There are some other quiet switches around available with proper caps from E-Switch and a few others, mostly orderable from Mouser. However, they are also very expensive.

    I ended up getting Alps SKPG switches. They are cheap, quiet, and have a nice feel I think. Unfortunately you have to DIY caps for them, which can make them a bit noisier (not to mention being difficult).

  5. TK, I think I have stumbled upon a bug during my lemur interface creating..... when accessing the BUTTON_DIRECT_TRACK1...16 feature the track would only change if the new one selected was in the already selected group. I assume this is not the correct behaviour - here is my fix I'm using in my local copy:

    static s32 SEQ_UI_Button_DirectTrack(s32 depressed, u32 track_button)
    
    {
    
      static u16 button_state = 0xffff; // all 16 buttons depressed
    
    
      if( track_button >= 16 ) return -2; // max. 16 direct track buttons
    
    
      if( depressed ) {
    
        button_state |= (1 << track_button);
    
        return 0; // no error
    
      }
    
    
      button_state &= ~(1 << track_button);
    
    
      if( button_state == (~(1 << track_button) & 0xffff) ) {
    
        // if only one select button pressed: radio-button function (1 of 16)
    
        ui_selected_tracks = 1 << track_button;
    
        ui_selected_group = floor(track_button/4); //<<<<added
    
      } else {
    
        // if more than one select button pressed: toggle function (16 of 16)
    
        ui_selected_tracks ^= 1 << track_button;
    
      }
    
    
      // set/clear encoder fast function if required
    
      SEQ_UI_InitEncSpeed(1); // auto config
    
    
      return 0; // no error
    
    }

  6. Hi, I've attached a pic, sorry about quality (from phone).

    The caps are 4.5mm, front panel is 3mm, button actuator is pretty much flush with base of front panel - so they stick out a nice amount. Many of them feel quite good. Some have suffered from excess glue which is blocking the motion - they are quite stiff but still successfully activate. The cap rubbing on the panel makes it noisier than the bare button, but I still prefer this to clicky buttons.

    I'm also not sure how long the glue will last.

    post-6793-0-07706400-1336637861_thumb.jp

  7. I have tried these buttons (though I'm not sure they're the same force). The ones I tried were nice feeling, quiet, but a little too much force required to push for my taste.

    A word of caution with your acrylic button caps. I have tried laser cut acrylic caps (with Alps SKPG buttons) and have found it quite difficult to get them to work well. The gluing is very tricky and time consuming, and the caps often do not track straight or get stuck on the front panel. You will probably find you need to glue the cap to the button actuator. Try a small cheap prototype first! :)

  8. I assume you will be submitting your files to Formulor through the Ponoko website?

    I recommend using Ponoko's design guide here: http://www.ponoko.co...r-kits/inkscape with http://inkscape.org/ Inkscape is free. I'm not sure if you're aware but the drawings you've made are not useable by the laser cutter, you must redo them with the proper format.

    It might also be a good idea to do a cheap test run on the P1 (smallest) size to check that your method is working before spending for the big job.

  9. Managed to accidentally delete my source containing my NRPN implementation. frantics.gifAt least I can reverse engineer from my Lemur patch.

    Been working on a different tangent. I found the Sysex remote feature already present in the Seq. I've got working button and encoder input from the Lemur, along with partly working LCD feedback. The Lemur app doesn't have some of the required characters for Seq display so I'll have to find a work around for that.

    So far I haven't been able to decode the LED stream coming from the Seq. It also seems to put out enough data to dramatically increase CPU usage on my laptop. I guess I'll need to slow down its output rate.

    Here's a copy of my current Lemur patch (caution, WIP, hacking needed for most functions to function whistle.png): MBSeq_Combined5.zip

    And an export of TK's BLM patch (in a container) as a .jzlib for easy importing into other Lemur patches: blm.zip

  10. ^^BUMP^^

    thumbsup.png

    I've been looking at some other step sequencers for workflow ideas (five12 Numerology and Sequencomat (a Lemur controller for a Max/MSP sequencer). I like particularly Numerology's ability to directly see/edit several 'parameter layers' from the same screen.

    Here's a rough idea how it might look in midibox/lemur land:

    post-6793-0-51885700-1334496239_thumb.jp

  11. Thanks TK,

    I've put a few hours in (noob here).

    I can successfully set and retrieve track CC info via SEQ_CC_MIDI_Set() and SEQ_CC_Get(), and it's also easy to utilize SEQ_UI_REMOTE_MIDI_Keyboard() for simple button functions like Play, Stop etc.

    I'm wondering how best to set and retrieve other data for which there is no established interface method. For example I tried to use SEQ_UI_Button_DirectTrack() to directly switch tracks but got strange results. (Also I feel nervous littering my code all through yours ...)

    Cheers :)

×
×
  • Create New...