Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


monokinetic last won the day on March 22 2021

monokinetic had the most liked content!

About monokinetic

  • Birthday January 1

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

monokinetic's Achievements

MIDIbox Tweaker

MIDIbox Tweaker (3/4)



  1. wow that setup with multiples looks truly phat :D congrats on a great build, and respect for documenting it so well for the community
  2. @Phatline cool OK, sure no worries to do my own order. But yes, good idea to wait until design is confirmed!
  3. Oh that's a good idea. And by coincidence I'm just stuffing one of those boards! Thanks for sharing your work. DM me if you want to share a PCB order :)
  4. That behaviour could be explained by PSU being overloaded (i.e. box runs, functions OK, but then stops as PSU can't handle the overload). How are you powering things? Does the regulator get hot (careful when touching, they can get very hot!)? etc Also, it might be useful to provide info like: - which bootloader you have on the PIC? - which operating system are you using on your computer? - which version of MIOS studio are you running? and so on. Good luck!
  5. Good stuff, looking forward to it!
  6. Darn, I was hoping to do the same. Shame to hear it's not working with the updated firmware. I don't have any Launchpads, yet. But as a matter of interest I had a quick look at the code. At a guess, this line here: seqregex = re.compile("MIDIbox SEQ V4:MIDIbox SEQ V4 MIDI ([1-4]) [0-9]") Needs to be updated for the new v4+ firmware. Have you tried editing it to: seqregex = re.compile("MIDIbox SEQ V4+:MIDIbox SEQ V4+ MIDI ([1-4]) [0-9]") i.e. just add the + symbol two times to match the updated name you posted in the output of mido.get_input_names(). Not sure how you tried to modify the regex, but that would be my first thing to try! Oh and you might find that the + character confuses the regex, so if that doesn't work, try using a \ before each + which you add. So it looks like this: seqregex = re.compile("MIDIbox SEQ V4\+:MIDIbox SEQ V4\+ MIDI ([1-4]) [0-9]") Hope you get it up and running....
  7. Still available, talk to me :)
  8. Do you mean the original STM32F1 based core: http://ucapps.de/mbhp_core_stm32.html or the more recent STM32F4 based core? Compare: http://ucapps.de/mbhp_core_stm32f4.html I maybe have one of the STM32F1 boards, not stuffed, available. I can only confirm on Friday this week as I'm travelling....
  9. Hi there, no sorry, this is the stuff which is specific to building the MBSeq. If you would like to discuss maybe send me a direct message? Cheers, David
  10. @TK. thanks for the tip re: storing the values in the DEFAULT.CV2 file, yes that is much easier. My encoders thank you :) FWIW I tried this calibration stuff a bit more: something really seems weird with the way values are entered. For example, if I set cali to 5V and try to set the offset, I can scroll up to 255 and then it jumps down to -3840. I see the same with changing the value to 0xffff in the defaults file. Is that expected? If it helps, this is what MIOS_Studio shows during those 3 clicks of the encoder to the right: [1164.130] value=f000 (with x0=d800 x1=f000 y0=d800 y1=f000) -> result=ffe0 (offset value shows 254) [1164.690] value=f000 (with x0=d800 x1=f000 y0=d800 y1=f000) -> result=fff0 (offset value shows 255) [1165.852] value=f000 (with x0=d800 x1=f000 y0=d800 y1=f000) -> result=0000 (offset value shows -3840) I have done quite a bit of testing now with Cali out, I can provide more info but I don't want to bombard you all the numbers I measured if this is expected behaviour :) In the meantime, I have now found a way to get the output I expected from MBCV. My steps were: on Default page, channel type must be set to something other than Note, in my case I use CC. Otherwise it impacts on the output, regardless of any MIDI note ever being actually received. This really got me for a while :) on CV out set LFO1 to Sine, reasonably slow rate, with amp 127. Only then can I get reliable level, i.e. 0 to ~10V. I have various other notes from my studies of MBCV recently. I will write them up more once I'm sure of some things.... Cheers, I'm having a blast with this so far. Can't wait to get my scope LCDs hooked up so I can put my multimeter away ;)
  11. Using a fresh compile of master from Github to try out that amazing v4.96 feature set, I tried to set a track to control an AOUT using the LFO as mentioned recently. Indeed assigning the extra out sends the LFO to the AOUT, excellent another source of modulation! But on my set up (unipolar original AOUT) the output seemed weird. For example, when I first turn on the LFO effect, and set the output to sine I get a triangle. Then changing through the waveforms gave me just lower volume versions of the wave, it seems to be a saw. Having seen this on the scope, this made me go back and check the output via MIDI CC and it seems the same. If it helps, I have experimented with amp and offset. I expected that with both set to 64 I should see the full waveform, i.e. triangle going from 0 to 127. But what I see seems weird to me! FWIW both the AOUT and the CC seemed to have same behaviour. Let me know if you need more info or the session sending :)
  12. Follow up having used the same hardware using MBSeq4 app: I'm not totally sure the calibration process will solve this. I tried the MBSeq outputting CC0 to 127 to an AOUT channel. That generates the expected voltage, without me changing the calibration of the AOUT at all. It feels to me more like I need a way to tell MBCV to double the final level of the CV output. In the process I also found something new, which I will post in the MBSeq main thread.
  13. Excellent TK! Many thanks for taking this on :) I have pulled from Gihub, compiled and had a bit of a play with it. So far I see some things which seem weird to me: the "Cali" list of options seems in the wrong order. For me it goes - Off, Min, Middle, Max, Wave, -4V, -3V, -1V, 3V, -5V (at this point offset becomes editable), -4V, -3V, -2V, -1V, 0V, 1V, 2V, 3V, 4V, 5V, Max: (with offset, unlike earlier Max value). Is that expected behaviour? When I select 5V from above list and try to change offset, as I scroll up it seems to jump down to -3840. Which is not within the range you mentioned (between -2048 and 2047 right?) Anyway, seems like it's close. If it helps, my testing process is to set a CV channel to output the triangle from LFO 1, set the rate reasonably slow and then the -CV output of LFO1 to 127. Also, how do you recommend to set the offset values if I want say the triangle wave LFO sent to CV with level 127 to range between 0 and max voltage (i.e. ~10V)? I had planned to set 5V to maximum offset, but wasn't sure how to proceed after that! My guess is that I set -5V with offset to output 0V, 0V to output ~5V and 5V to output 10V. Is that the idea? Oh and final suggestion: would it be possible to support the new caliaout at the Mios terminal i.e. in MIOS Studio? I ask because the way the offset jumped, now to reset I have to scroll a long way. From memory, MBSEQ stores these calibration values on the SD card. Does MBCV do the same i.e. could I just tweak the values on the SD? Thanks muchly in advance :) David
  • Create New...