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
New firmware hack version v3.01
  • Hi, I just put a new firmware version v3.01 for Meeblip SE V2 and Meeblip Micro in my github repository at https://github.com/ataweg/meeblip-synth. The most interesting features are:

    • Much more of the sound parameters can be controlled via MIDI. The extended MIDI mapping is based on the knobs and sliders of a QX49 keyboard.
    • 48 byte patches to support more midi parameter and switches.
    • More "hidden" knobs and switches controlled thru MIDI.
      • ADSR parameter for VCA- and VCF-envelop generators can be set directly thru MIDI (8 "hidden" knobs).
      • Add switches used in previous versions of meeblip (switch 3 and 4).
      • Master volume control via MIDI. It can also be raised the volume.
    • Noise generator now makes more or less white noise - new algorithm.
    • Ring modulator for metallic sounds.
    • Control mixer balance thru MIDI.
    • Some predefined patches.
    • Patch 1 has a default setting and can not be overwritten.
    • New mapping tables for various parameters.
    • Some code optimizations.

    The code was originally built for my version of a virtual analog synthesizers based on the Meeblip hardware. My source code, schematics and a little bit documentation can be found at https://github.com/ataweg/aweAvrSynth.

    Feel free to take a look into my hack and give me your feedback.

    Viele Gruesse Axel

  • Hi,

    I added a arpeggiator to my meeblip firmware hack.

    • new switches: DISTORTION => LFO_ENABLE, ARP_REPEAT => DISTORTION, ARP_ENABLE => FILTER_MODE

    • new knobs: ARP_RATE => upper OSC_B_DETUNE, ARP_THRESHOLD => PWM_WITDH

    Feel free to checkout the source from https://github.com/ataweg/aweAvrSynth.

    Prebuilds are available.

    Viele Gruesse Axel

  • Great! This seems to call for an extended interface, or would you rather build the Meeblip into your QX49?

  • to control the extra switches and knobs I extended the python program meeblip-control of Bitrex. See https://github.com/ataweg/meeblip-control/tree/master/meeblipcontrol.

  • I've never used Python before, but this seems interesting. Could you make a screenshot of the GUI?

  • Here some screenshots for the meeblip control GUI

    image

    image

    image

  • I borrowed and tweaked some of your code to try to make a MIXER_BALANCE slider, but I can't get it working right. I was wondering if you could take a look and tell me if there are obvious errors in it? I am an ASM newbie.

    The symptom is that while one end of the (midi) slider correctly gives me 100%A and 0%B, the opposite end of the slider seems to still give 100%A with some of B mixed in.

    Here are the relevant chunks of code: https://gist.github.com/wbajzek/5044513

  • in the code sniplet I missed a branch after line 15

        cpi r17, 0x29   ; MIXER_BALANCE
        brne    INTRX_CCEND
    

    see also https://github.com/ataweg/aweAvrSynth/blob/master/Firmware/aweMeeblipSE-v3.asm line 3129

    add the branch destination after line 35 in your code sniplet

        sts DCOB_LEVEL, r16 ; Store DCOB level(0..254)
    INTRX_CCEND:
        pop r27 ; reload old contents of r27 and r26
        pop r26
        rjmp    INTRX_EXIT
    
  • It's not working, but thanks for the help. I am sure I screwed something else up and will just have to dig into it more.

  • if you send me your source code and the original code as private mail, can I try to find the problem. You can exclude the possibility that it is a hardware problem?

  • Thanks. I sent you a message.

  • I got it, thanks. The control doesn't do anything now and I didn't have time over the weekend to look into it farther. I appreciate the help but I think maybe I just need to figure it out for myself rather than having you spend too much of your time on my problem.

    I do have one last question, though; what is the reason for this part? Why trim off the bottom range of the control?

    cpi    r17, $02
    BRSH   SET_DCOA     ; skip if knob value >= 2
    ldi   r17, $0