monokinetic

Programmer
  • Content count

    301
  • Joined

  • Last visited

Community Reputation

4 Neutral

About monokinetic

  • Rank
    MIDIbox Tweaker
  • Birthday January 01

Profile Information

  • Gender Not Telling
  1. Heheh, define easier ;) I'm no Git expert, but if it helps, here's how I'd imagine doing things: Make a directory for this repo i.e. cd ~ mkdir mios_stuff cd mios_stuff Clone the repo to your local dir: git clone https://github.com/midibox/mios32.git Let's check to see which branches are available in the new repo: cd mios32/ ~/mios_stuff/mios32$ git branch -av * master                                      79292db corrected comments in source_me_* files   remotes/origin/HEAD                         -> origin/master   remotes/origin/feature/juce_5_4_3_migration 5e8148f MIOS Studio: updated release script   remotes/origin/feature/mcan                 b7b78c2 corrected mios32_* namespace   remotes/origin/master                       79292db corrected comments in source_me_* files I used the -av option to show all of the branches on the remote repo. Note the * by master, that shows which branch you have checked out at the moment. It looks like TK has set you up the feature/mcan branch. Let's assume you want to do some work on that, so switch to the MCAN branch like this: ~/mios_stuff/mios32$ git checkout feature/mcan Branch feature/mcan set up to track remote branch feature/mcan from origin. Switched to a new branch 'feature/mcan' Here is where things are a bit different to SVN. I'd try and explain it but you'd be better reading this: https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell Then basically you can do your work, doing regular commits. Those go in to the branch you have checked out currently. Then when you are ready to share them with others you push to the repo, ensuring that your push goes to the feature/mcan branch. Eventually, once we know that everything you have done in feature/mcan is OK to add to the full mios32 then someone has to merge the changes in feature/mcan branch into the master branch. Then finally everyone can use MCAN and blow their minds with so many MIDI ports to play with ;) I also recommend looking up how Git stash works (I find that invaluable) :) Sorry for the slightly long post, and apologies in advance for things that a Git expert would tell you are wrong. But that's how I plan to use it so far!
  2. Using AOUT with Buchla 1.2v/octave

    Hi folks, nice to know this info is of use to some! @Rowan I'm afraid both of my attempts at building an AOUT_NG failed so I gave up on that path. But yes to what Zam wrote, basically all I did was recalculate the opamp resistors. Don't know why it didn't occur to me years ago, but that's life :) Good luck with your builds!
  3. Using AOUT with Buchla 1.2v/octave

    As you probably know, the AOUT module is set up to support 1v/octave scaling, and that has been fine for me when I was using it with a Serge modular system. But I have been wondering how I could use my AOUTs with my Buchla-ish modular synth, which uses 1.2v/octave scaling. I contemplated building an opamp based solution, boosting the voltage a bit. But this seemed a bit of a hack to me, so I spent a bit of time understanding the opamp based outputs from the MAX525 DACs. I realised that by tweaking a resistor value I could get the AOUT to put out 1.2v/octave. I've tested this for a bit with two different oscillators (258r and 259r) and it seems fine for my uses. I'm no electrical engineer though, so if this mod blows up your rather expensive equipment I'm afraid you're on your own... That said, for any other Buchla users who want to use an AOUT to output 1.2v/octave, just change RY to 1.8K on any channels you want. That should give you the extra bit of gain required, and then you can trim it to 1.2v/octave. FWIW I usually use the MBSeqV4 app, then use the nice new calibration stuff to get things super accurate. I'm able to get submillivolt accuracy over the whole voltage range. Top voltage is obviously a bit higher in this case, almost 13v from my measurements. That seems to have been fine in my system, but YMMV. Also, I have set my AOUT so that V1-V4 have this tweak (1.8K for RY), and I use them for controlling Buchla oscillators. V5-V8 use the 2.2K resistor for RY still, and I use those channels for modulation CVs and to control the Serge oscillators which run at 1v/octave. All in all I'm most happy with this system and am glad I don't have to mess around with adding more circuitry. Hope that helps someone in the future!    
  4. [FS] MBSeq4 kit - incl. Heindrich case (price drop)

    Bump for the price drop to 325 Euros, that's a bargain!
  5. MIDIbox SEQ V4 Release + Feedback

    @TK: oh my, did Christmas just come early :) Excellent to see some updates, thank you! Will test over the coming days. re: the AOUT extended calibration, is there a chance to merge this into MBCV2.0 at some point? I would find it really useful in that app as well..... Just a thought! Warm and festive regards David
  6. MIDIbox SEQ V4 Release + Feedback

    @TK wow this works really quite nicely. FYI I tried v4_095_pre14 on my STM32F4 based MBSeq. I observed the following: - when scrolling through the options using ENC #7 it seems to go min/middle/max/wave. When set to wave there's a full voltage range triangle type wave coming out of CV, is that intended? - once I scroll through to the end of possible values using 7, the last value is Max:. That seems a bit weird over here. When I initially scroll to Max I get almost 0 volts out of the CV channel, then if I touch ENC #8 the offset value on screen jumps to -3700 ish! At that point I get the full voltage out of CV. I guess this might weird out the interpolation a bit? And I started to scroll ENC #8 to get it back to around 0 but it was taking ages and I gave up :) Otherwise, this change seems great. I have used it to play a couple of basic patches from MBSeq to my modular and it seems really accurate, excellent work, as usual! Tiny feature idea: could presses of GP8 cycle through min/0/max offset? for quick changes? Cheers David
  7. MIDIbox CV V2 Concept

    Not sure which type of MIDI control you mean. The Lemur interface is using NRPNs from memory, so any other interface could use that I guess. I'm not sure of the status of CC control, I've not got things hooked up at the moment, otherwise I'd check for you. Prob best to check the code if you want to be 100% sure...
  8. MIDIbox CV V2 Concept

    FWIW I use MBCV2 regularly on an STM32F4 core and an AOUT using MAX525s, and I have some DOUTs doing gates. It works great in my DIY modular synth. Everything you described in your post sounds like it is doable in my experience. Whether you even need the second core running NG is debatable, that'll depend on how you want to connect to the Behinger (which I'm not familiar with, so can't comment). I wouldn't say it's a dead project myself, super usable and the interfacing with Lemur is amazing. Good luck with your project!  
  9. dipCoreF4 and dipBoardF4, a compact Core.

    Great thanks for confirming. Now I know all about Micro-match :) I've added some value versions and luxury versions to my Mouser order for testing.
  10. dipCoreF4 and dipBoardF4, a compact Core.

    Hooray for rain! Looking good, the only thing I see in there which I don't recognise are these "micromatch" connectors. I guess any male 1.27 pitch connector with the right number of pins is suitable for making ribbon cables. I was thinking of using something like these, what do you think?
  11. mnmlCore

    Yeah, and the feature list makes me go whoa! Looking forward to this one 
  12. [FS] MBSeq4 kit - incl. Heindrich case (price drop)

    Adding some photos. As you can see, PCB is still in airtight shrink wrap, all kit components in sealed bags (packed by smashtv himself!!), Heindrich case sealed in plastic, LCD windows in nice tissue paper and unscratched! So everything is basically as new and ready to build, just add LCDs and your CORE and MIDI PCBs and you have a complete unit :)
  13. I've had this hoarded as a back up in case my seq went down. Now I want a V4+, so here's a good time for you to get an entire kit to build a seq V4.... Includes: MBSeq4 CS PCB + SmashTV full parts kit (PM me for exact contents) Beast panel (with minor defect, hence cheaper PM for details) Plastic LCD windows x 2 (super handy) Heindrich case (rare as hen's teeth ;))   Not willing to separate I'm afraid. Asking price = 400 euros  price reduction to 325 Euros, buyer pays shipping. Also available: OPL3 and 2x DAC chip set 15 euro MBCV 1 from sonicwarrior 10 euro PIC Burner + cable - 15 euro I'm located in Prague, the Czech Republic. Prefer bank transfer, but can do Paypal if you pay fees. IM me if you're interested in anything.
  14. OLRE16 with Lattice CPLD as Clocking/Addressing interface

    Looking great!
  15. Thanks for all the info on how to adapt pyBLM, that pretty much seals it for me!