Leaderboard

Hi all! I finally finished my V4+ build, and just wanted to thank everyone in here, I've been studying the manual for a few days and also trying to find a good config with my synths/samplers setup, and so far it seems that it's simply the best sequencer in the world :) Huge thanks to TK, Peter, Andy and everyone who helped troubleshooting. I have to that I had barely touched a soldering iron before, so without help from the community and Peter's great tutorial, I wouldn't have been able to finish the build. I'm the living proof that anyone with a few basic tools, motivation and organization can build a working V4+, thanks to Midibox awesome users (beers are coming up!). About the build, I also agree with everything that has been said in the previous page concerning cable lengths adjustments and loose 3M shrouded headers, and I can't think right now about anything else than that could be improved, as I don't have much experience (I'll edit my post if anything comes to mind). I already have a few suggestions and questions about the firmware, but I'm saving that for later :) Also, I'm actually working as an artist but I've been trained as a graphic and type designer, so I'd be glad to help on anything related to that, if that comes handy at any point. Thanks everyone again! Best, K

aha excellent, I agree that this should make collaboration easier.... 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!