Apologies for spam; we've changed our policy by requiring approval for accounts, and deleted all existing spam and user - thanks for your help flagging content. We continue to test our forums and Vanilla software, aiming for release early in 2013. If you need to give us feedback outside the forum, contact us via http://createdigitalmusic.com/contact/ or on Facebook
MeeBlip Micro preset patches?
  • peanutismintpeanutismint

    This is probably a given but just to set my mind at ease - the micro MeeBlips don't have the ability to save presets like their bigger brothers, do they??

  • meeblipmeeblip
    Accepted Answer

    The Micro doesn't have enough I/O pins to add save/load buttons.

  • peterpeter
    Accepted Answer

    I can add a little bit to this, too - remember that every parameter on the MeeBlip has an associated MIDI Control Change message. So, while there's not preset storage, the assumption is that you're driving the MeeBlip micro with some sort of external MIDI input. That means you could store "presets" simply by saving banks of MIDI. It depends on how you intend to use the feature - we'd be interested to hear that, actually.

  • peanutismintpeanutismint

    Yep I thought as much.

    I am already trying to work out how to store 'presets' by using different midi 'scenes' on my controller keyboard. I've managed to change all my controller CCs to change the various parameters of the MeeBlip, but as a relative synth newbie I'm finding it a bit laborious working out what exactly each parameter does to the sound (especially as some parameters will only result in an obvious audible change when changed in conjunction with others....)

    One more question - I addressed my MIDI controllers in the order that the CC values were listed on the website, but I'm wondering if this is the most logical order, i.e. most-conspicuous controls listed first, then less altered ones listed next etc....?? Or can anyone suggest a different order, with the most 'basic' controls (that I would presumably assign to the 'top level' pots/faders) first and then the less important ones after.....??

  • orangebugorangebug

    I've noticed when comparing the schematic of the micro with the standard meeblip that the micro has 1 unused pin (pin "(OC2PD7" on the mega32-p). This pin is used on the standard meeblip as part of it's 5x4 switch matrix.

    Could one feasibly run a hard wire to this unused pin on the micro and recreate those missing 4 buttons? As far as I can tell once you do that, you just have to load the SE firmware into the micro and you would essentially have a MeeBlip SE.

  • meeblipmeeblip

    Yes, you could use that pin and add a switch matrix. You would also have to add 20 diodes.

  • peanutismintpeanutismint

    Hahah okay so I guess you're saying that's probably not a worthwhile 'hack'...... ;)

  • meeblipmeeblip

    It'd be a cool hack. The reason there are only 8 switches on the micro is that I wanted to avoid the torture of having to solder all those diodes. The first couple are ok, but it gets a bit tedious.

Add a Comment