Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


monokinetic last won the day on March 22

monokinetic had the most liked content!

Community Reputation

7 Neutral

About monokinetic

  • Rank
    MIDIbox Tweaker
  • 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.

  1. heheh, good to see you anti! Well I guess my point was: how come this bot, or person, is filling up the forum with sales stuff? Personally I object to it, there's a whole big internet to spam me in. Here I would like to be left alone!
  2. can you write something to prove you're not a bot? Like for example which ucapps schematic contains that part number for example? ;)
  3. 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!
  4. Good stuff, looking forward to it!
  5. 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 tri
  6. Still available, talk to me :)
  7. 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....
  8. 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
  9. @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=f
  10. 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 t
  11. 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.
  12. 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
  13. Hi there Thorsten, aha yes I remember the new calibration stuff, it'd would be great to have in MBCV as well..... If you would be able to do it that would be an amazing new year's present, I had a look last year and it seemed a bit complicated for my skills :) But I'd gladly do some testing on both apps! Cheers David
  • Create New...